2015-07-25 19:34:28 -0500 commented question Version of Fedora for Opteron 4130 If you provide a little bit more info about the nature of the crash, how far into the boot sequence you get, if you can access bios/describing your settings, your video device, whether any other live images work or if there's been another OS on this system, etc. then that could help diagnose the problem. Sorry for quad post! I didn't have a proper answer for you. 2015-07-25 19:33:02 -0500 commented question Version of Fedora for Opteron 4130 If you can get to the live image boot menu, try pressing Tab on the Install Fedora option, and add the following options to the end of the boot command: xdriver=vesa acpi=off nonet nopcmcia noparport nofirewire nodmraid  That should rule out any faulty drivers. You can also run a memory test in the troubleshooting options. If none of that helps then there may be more options like installing to your hard drive using another system and then swapping it back in and booting with a generic initramfs, among other things, but those are the most obvious things to try first. 2015-07-25 19:18:12 -0500 commented question Version of Fedora for Opteron 4130 If that's the case, you'll need to reset your CMOS. There are guides available online, but the process can be different for some machines. You may want to find the manual for your motherboard online and see what it says about resetting your CMOS, and browse its BIOS help section find any other settings that stand out as relevant (I'm unfamiliar with Opteron systems). Another possibility is faulty RAM. Try booting with one module, swapping them out until one works. If none work, try a different memory slot, or if a second module breaks it again, put it in the same channel as the first module. 2015-07-25 19:06:11 -0500 commented question Version of Fedora for Opteron 4130 If you are installing via CD-ROM, try via flash drive or vice versa. Before burning the image, run an md5 checksum and verify that the image matches the checksum on the Fedora download page. If your burn utility has an option to verify the image integrity after burning, do that too. If you just received the system and haven't had an OS on it before, the BIOS could have some incorrect settings. If you can open the BIOS screen (often by pressing delete, F1, F8, F12 or something like that, it varies per system), ensure ACPI support is enabled. If you can't boot to BIOS, that is your problem. 2015-07-24 14:56:43 -0500 commented answer Annoying removable drive notification Unfortunately, there is no setting in GNOME to make removable drive notifications disappear like others. It seems to be a bug, but its several years old now and there have been a few bug reports filed about it already, so I'm not sure when it will be fixed, if GNOME is actually even planning to. There are no extensions that solve it either at the moment. Disabling the notifications for removable media is the only fix right now. You may be able to get around it by disabling all GNOME notifications and installing a separate notification system in its place. There are several in the repositories. 2015-07-24 02:59:43 -0500 received badge ● Editor (source) 2015-07-24 02:55:28 -0500 answered a question Annoying removable drive notification That's normal behaviour of the GNOME desktop, but if you don't like it, you can change it using the Settings program. Open the applications dashboard and scroll down, or type in 'settings' to find it. In that program, click on the Notifications entry, and then you can click the switch that says Show Popup Banners to disable those notifications globally, or you can scroll down to a specific program you want to disable them for and click the switch under its heading. You can still have other types of notifications with sliding notifications disabled, such as event sounds. I don't have a blank drive available so I can't say for sure, but I think disabling sliding notifications for the Files program entry will disable sliding notifications for blank drives. I unfortunately cannot test that possibility at the moment, maybe someone else can confirm. For CDs, DVDs, and removable drives with pictures, music, programs or live images on them, you can go to the Settings program again and click Details, then Removable Media, and choose the type of media you want and set the handler to "Do nothing", or click the "Never prompt on media insertion" checkbox to disable actions globally. If you don't already know, there are also alternative desktops available in the repositories such as KDE or Cinnamon that are more configurable than GNOME, and you may prefer the more traditional way they handle notifications, i.e. a small message near the system tray that shortly fades away. 2015-07-24 02:13:17 -0500 commented question Huge amount of Tracker-WARNING log lines upon login Depending on how journald is configured (specifically journal file size and log rotation settings), it can actually be filled up to a large size, and slow down certain actions if it gets out of control. Most distros like Fedora use sane defaults, so it's not a huge problem. Worst case is you will have your logs rotated too fast for you to inspect other entries when you have constant streams of errors. Still, best to always get rid of them somehow. Telling tracker to skip files will also save wasted disk reads/cpu cycles if you don't need them indexed and slightly speed up indexed searches. 2015-07-24 02:13:14 -0500 answered a question Huge amount of Tracker-WARNING log lines upon login I am not sure what is wrong with the metadata from that output, but if you just want to stop the error messages, it's easiest to use the package called tracker-preferences. It can be launched from a terminal using the command of the same name. With that program, you can choose to make tracker ignore specific directories when indexing, or you can exclude file types using * as a wildcard, for example *.jpg to exclude jpeg files from indexing. That will at least stop the error messages from filling up your journal needlessly. Alternatively, you can exclude files/directories by editing your dconf with either a terminal or a GUI program, and also change various other settings for tracker. If you use the program dconf-editor, you can navigate to org.freedesktop.tracker and change settings there. As always, be careful messing with settings that you don't understand, especially with dconf. There are many more settings possible using dconf compared with tracker-preferences though, so perhaps you would find something else useful for this problem there. 2015-07-24 01:20:45 -0500 received badge ● Teacher (source) 2015-07-24 01:16:05 -0500 answered a question How do you pre-set preferences when starting a program? You probably want to use bash aliases for this. They basically let you substitute a string for an arbitrary command. The string cannot have special characters that normally perform functions in it, but your command can have anything that would normally work in bash. They can be used in place of symlinks for what you were using those for, as well. To create a temporary alias that will last until the end of the session (useful for experimentation): alias my_alias_name="my_command"  If you think you might need to use the original, unaliased command in the future, you should name your alias something besides the original command name. Or, you can remove an alias until the session ends: unalias my_alias_name  To make your alias permanent so that it will persist after exiting your session, you need to edit the .bashrc file in your home directory and add your alias to the end of the file: nano ~/.bashrc  Scroll down to the end of the file and insert your aliases (under a new heading for clarity if you like), separated by newlines: ########### # Aliases # ########### alias my_alias_name_1="my_command_1" alias my_alias_name_2="my_command_2" ...  Save the file with Ctrl+x (answer yes to "Save modified buffer" and overwrite the original if it exists). The aliases will be applied at your next login, or you can run the following: source ~/.bashrc  That will initialize your aliases. If your command needs root, it's best to use su/sudo as usual after creating the alias instead of baking it into the command to be run. However, this will interfere with your aliases, since the shell only checks to see if the first part of a command is an alias, so it checks sudo, doesn't find an alias for it, and skips your intended aliases. To fix this, add another alias to your .bashrc: alias sudo='sudo '  If the last character of a command executed by an alias is a whitespace character like tab or space, then bash will remember to keep checking the commands after it for aliases. That lets you run your aliases safely as root or a normal user. If you want to make your life easier, instead of creating symlinks to executables, you can create aliases for them that include the path to the executable. Hope that is useful!