Error Message On Boot Up In Fedora 21

These instructions originate from https://www.linkedin.com/pulse/20140...nvidia-drivers, but I modified them slightly for my desktop environment (64-bit HP Envy Phoenix 810-135qe w/Intel i7-4770 and HP ZR2440w monitor, nVidia GeForce GTX645, Red Hat Enterprise Linux 7.1 w/Gnome3).

The following procedures replace the nouveau drivers with kmod-nvidia drivers from ElRepo.

Install the repository ElRepo from: http://elrepo.org/tiki/tiki-index.php

Install the package nvidia-detect from within Applications>SystemTools>Software

From within the terminal, enter the command nvidia-detect.
Example:
[anthony@hp810135qe ~]$ nvidia-detect
Output is...
Probing for supported NVIDIA devices...
[10de:11c4] NVIDIA Corporation GK106 [GeForce GTX 645 OEM]
This device requires the current 346.59 NVIDIA driver kmod-nvidia

For my system the following software packages will apply (yours maybe slightly different, the key is to note the ###.## version identified for your system using nvidia-detect as explained above): kmod-nvidia-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-32bit-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-346.59-1.el7.elrepo (64-bit)

Now do the following steps in the sequence indicated:

1. Disable X Windows

a) open a terminal and "su" or "sudo -i"

b) ln -fs /lib/systemd/system/multi-user.target /etc/systemd/system/default.target

Note: Another way to disable X Windows is to do the following from within the Terminal # systemctl set-default multi-user.target

To later change back to booting into graphical mode, substitute 'graphical.target' for 'multi-user.target' in the above commands.

c) reboot

2. Remove Nouveau

a) rpm -e xorg-x11-drivers xorg-x11-drv-nouveau

Note: Another way to remove Nouveau is to do the following from within the Terminal

$ yum remove xorg-x11-drivers xorg-x11-drv-nouveau xorg-x11-glamor

See http://elrepo.org/tiki/kmod-nvidia which discusses that glamor still causes a conflict with nVidia in RHEL 7

3. Blacklist Nouveau

a) edit /etc/modprobe.d/blacklist.conf and add line:

blacklist nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/modprobe.d/blacklist.conf
(use INSERT key to make changes in vi; add the line

blacklist nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

b) edit /etc/default/grub and append to GRUB_CMDLINE_LINUX:

rd.driver.blacklist=nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/default/grub and append to GRUB_CMDLINE_LINUX:
(use INSERT key to make changes in vi; add the line

rd.driver.blacklist=nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

IMPORTANT NOTE IF YOU HAVE AN ENCRYPTED BOOTUP DRIVE -

If you have an encrypted root drive, remove "rhgb" from GRUB_CMDLINE_LINUX. This will allow you to interact with the encryption passphrase prompt, since Plymouth doesn't seem to run without a framebuffer friendly video driver loaded. IF YOU DON'T THIS, WHEN YOU BOOTUP YOU WILL GET STUCK AT A BLINKING CURSOR AND BLACKSCREEN THAT HAS THE FOLLOWING ERROR MESSAGES:


[5.757276] scsi 7:0:0:0: alua: not attached
[5.759625] sd 7:0:0:0: [sdg] no caching made page found
[5.759668] sd 7:0:0:0: [sdg] assuming drive cache: write through

WHEN THIS HAPPENS IT MEANS PLYMOUTH IS NOT ABLE TO SHOW YOU THE PROMPT FOR ENTERING THE PASSPHRASE FOR THE ENCRYPTED DRIVES. WITHOUT THE PROMPT THE SYSTEM CAN'T ACCEPT THE PASSPHRASE AND YOU ARE STUCK. IF THIS HAPPENS TO YOU, YOU CAN DO CTRL-ALT-DELETE TO REBOOT - THIS ALLOWS YOU TO HIT 'e' AT THE KERNEL LINE IN GRUB TERMINAL TO EDIT (MOST LIKELY THE TOP KERNEL) AND THEN REMOVE 'rhgb' (which stands for Red Hat Graphical Bootsplashcreen or something like that). WHEN DONE HIT THE KEYS 'CTRL X' TO REBOOT - YOU'LL THEN SEE TEXT MESSAGES SCROLLING AND GET AN OPPORTUNITY TO ENTER THE PASSPHRASE. ENTER THE PASSPHRASE AND YOU SHOULD BE GOOD TO GO.

4. Reconfigure the grub.cfg files

Two options for booting nowadays are BIOS and EFI

-If you chose BIOS boot run this command:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Note: I also have this one being auto-updated-configured in my system (?why? It's EFI).

-If EFI boot on CentOS:
# grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

-If EFI boot on RHEL:
# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
Note: Mine is an EFI system. But I did both this and the BIOS grub.cfg above since it too is being updated by RHEL updates concurrently with the EFI grub.cfg

5. Reboot and Install NVidia Driver - I use ElRepo's kmod-nvidia for this step.

Steps by me to install ElRepo's kmod-nvidia (You should still be in Text mode at this time):

If in multi-user.target mode (text, runlevel 3), then do the following
$ su -
enter root password
# yum install kmod-nvidia - version from above
# yum install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
# yum install nvidia-x11-drv - version from above (this is for Open GL X11 display driver and to be done if kmod didn't already include doing it with the kmod-nvidia installation above)
# exit
$

If still in graphics.target mode (you shouldn't be but if you are) (GUI, runlevel 5),
Use Applications > Software > kmod-nvidia - version from above
Install kmod-nvidia - version from above
Install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
Install nvidia-x11-drv - version from above (this is for Open GL X11 display driver)

6. At this point rebuild initramfs. This recreates initrd w/o nouveau. The existing initrd still has the embedded nouveau drivers if this step is not performed) :

Back up the current initramfs keeping nouveau
# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
Build the new one without nouveau
# dracut /boot/initramfs-$(uname -r).img $(uname -r)

7. Re-Enable X Windows

# systemctl set-default graphical.target

8. Reboot

If you have an encrypted bootup drive, when you bootup you may notice that Plymouth doesn't look so good with its text in a lower resolution and you'll see lines of text scrolling until you get to a stopped cursor waiting for you to enter the passphrase to unencrypt your drive. Maybe eventually there'll be a solution for this to keep things moving with a graphical bootsplash all throughout. Until then, this is a minor inconvenience for me.

I am trying to move away from windows. Installed Dragora with lots of hitches I managed to fix until I booted from hard drive. on boot from hard drive I got a blank screen for over an hour. On my next look at the screen the next morning I have these 4 lines over and over.
ssb0:0 Missing Free firmware
"b43-phy0 ERROR:firmware file"/*(DEBLOBBED)*/"request failed (err=-22)

"b43-phy0 ERROR:firmware file"b43-open/ucode15.fw" not found

"b43-phy0 ERROR:/*(DEBLOBBED)*/
there is a curser flashing and I am able to type but unable to start a new line. I typed setup signed in and recieved
" No mail.
root@rafaela:~# " Am I in line edit mode? wha;t went wrong? how do I get the graphical interface? how do I install the missing files? Should I run screaming for the hills?

Hi I am taking a Linux class at my local community college, I have a laptop that I would like to use but don't want to delete the entire window OS. I have a usb harddrive that I can use at least 200GB off the hard drive. For class we are using "a practical guide to Fedora and Red Hat Enterprise Linux,which gives you a copy of Fedora 19. I have tried to load the disk onto the usb hard drive I which is no problem until I reboot. I get a "can not find tocblock. database may be corrupt" then feodra loads with no problem. I can login but after logging in the GNOME welcome page shows up and after that the video screen goes haywire and you cant see anything. any thougts?

I install fgrlx driver on vivid os the driver look like is istalled correct on system and built the necessary kernel modules because the dpkg log not report any errors, i configured the driver by simple commands like:

sudo aticonfig --initial

sudo aticonfig --screen-layout=on

i reboot the machine , but i face an strange issue the boot splash screen is hangup,i cant enter my lvm password to boot the system, i was have a chance to boot into rescue mode when boot to rescue mode the display not read by the system i try to export display by

export DISPLAY=:0

I try to configure /etc/X11/xorg.conf there is not good resaults the boot splash still hang up

I edited the grub , i uncomment "quiet splash" modified by "nomodeset"

i can boot without boot splash but im faced other issue i cant switch to virtual tty

i dont know is this a bug in the driver or in the kernel

any suggest

I want to change the menu on a Suse 12 Enterprise system.
I edit the /etc/default zip12grub.conf file execure grug2-mkconfig. Then reboot the system and no changes occur. The zip12grub.conf seems like the correct file to update so I am at a loss as to what the correct process would be.

cat zipl2grub.conf
## This is the template for '@zipldir@/config' and is subject to
## rpm's %config file handling in case of grub2-s390x-emu package update.

[defaultboot]
defaultmenu = menu

[grub2]
target = @zipldir@
ramdisk = @zipldir@/initrd,0x2000000
image = @zipldir@/image
parameters = "root=@GRUB_DEVICE@ @GRUB_EMU_CONMODE@ @GRUB_CMDLINE_LINUX@ @GRUB_CMDLINE_LINUX_DEFAULT@ initgrub quiet splash=silent "

[skip-grub2]
target = @zipldir@
ramdisk = @zipldir@/initrd,0x2000000
image = @zipldir@/image
parameters = "root=@GRUB_DEVICE@ @GRUB_CONMODE@ @GRUB_CMDLINE_LINUX@ @GRUB_CMDLINE_LINUX_DEFAULT@ "

[test-grub2]
target = @zipldir@
ramdisk = @zipldir@/initrd,0x2000000
image = @zipldir@/image
parameters = "root=@GRUB_DEVICE@ @GRUB_CONMODE@ @GRUB_CMDLINE_LINUX@ @GRUB_CMDLINE_LINUX_DEFAULT@ "

:menu
target = @zipldir@
timeout = 16
default = 1
prompt = 1
1 = grub2
2 = skip-grub2
3 = test menu grub2

grub2-mkconfig -o /boot/grub2/grub.cfg

Generating grub configuration file ...
Found linux image: /boot/image-3.12.39-47-default
Found initrd image: /boot/initrd-3.12.39-47-default
Found linux image: /boot/image-3.12.28-4-default
Found initrd image: /boot/initrd-3.12.28-4-default
done

reboot

Storage cleared - system reset.
zIPL v1.24.1-38.17 interactive boot menu

0. default (grub2)

1. grub2
2. skip-grub2

Note: VM users please use '#cp vi vmsg <input> <kernel-parameters>'

Please choose (default will boot in 16 seconds):
Booting default (grub2)

Hello
I installed fedora 18 on an older apple computer (i.e. replaced the operating system with eight cores). To make a long story short, I did a "yum update" which took hours to complete, but when I attempted to restart my system, I now get the Grub boot loader coming up and showing that the fedroa3-11.10-100fc18x86_64 OS is staring up, but then suddenly the screen goes black and I get a weird message:

" radeon 0000:02:0:Invalid Rom content
system[1]:Job multipathd.service/start deleted to bread in g cycle starting with basic./start"

So, I then place on a USB containing the original fedora 18 I installed earlier, but now, I cannot, using the Grub Menu, to locate the usb or the cd option.

I have tried looking at sites on line for help, but so far nothing has worked...

Can someone help me...I am a Newbie.
Thanks

I have DualBoot.odt
what i need is. "Fedora Live CD."
It would be wonderful if you could provide me with any advice om how to set up a Dual Boot
1) Windows 7 (x64)
2) Linux Fedora 21 (x64)
FYI: My O: drive is my DVD burner

Hello,
I am trying out a GNU-plus-Linux distribution called "Tails" for the first time. Tails is the distro that provides anonymity for the user by forcing all network traffic to go through the Tor network system. I am testing out Tails version 1.4.
Tails is a live DVD disc. It boots in live mode directly from the DVD and optical drive.
However, once I was booted into the desktop for the first time, it seems to not have been able to automatically find and configure my internet connection.
When I hover the pointer over the twin PC's icon in the system tray at the top right hand corner it says "No network connection".
Then, just to make sure, I opened the "Tor browser" and it gave me an error message that says "The proxy server is refusing connections".
Then to make triple sure, I opened the "Unsafe web browser" and it gave me the error message that says "Error No DNS server was obtained through DHCP or manualy configured in Network Manager".
So as a new user of this distro, I'm not sure on where to go and what to do. So any help would be greatly appreciated.
Thank you

What I need:
Linux Fedora Live CD
I also need Linux Fedora 21 (x64)
I have:
DUALBOOT.odt
i also have Windows 7 (x64)
That is why I need, "Linux Fedora Live CD"
So that I can setup dual Boot
I previously annoyed me with, "[Login/signup to post]"
At the top it says, "Welcome,Bakshara
You last visited: Today at 11:12 AM

Hello!

TL;DR: Deleted Linux partition from Windows. Stuck at Grub rescue prompt.

I'm sorry to trouble you guys, because I'm an idiot.

So I'm wanting to dual-boot Kalilinux and Windows 8.
I went through the steps such as creating a bootable USB, changing the
boot order and so on. I get into Kali, start Gparted and try to partition stuff.

I'm far from an expert, so I wasn't sure what to do. Long-story short, I
didn't seem to get Kali installed correctly, due to something with an EFI
drive being required. So I boot into windows and then stupidly, because it said in the guide,try to "uninstall" Kali by removing it's partition, inside Win8 haha... So I did.

Now I simply get the Grub rescue command prompt when I boot from the same
USB and I have no idea how to fix it. I've run bootrec.exe/fixmbr in Windows haha,
for what it's worth. However Grub can't find any partition it says.

In windows, I have like... 2-3 Recovery partitions. Does anyone know how to remove
them??? I've tried to clear as much as I can, besides the C drive and Auxillary D drive.

Any advice would be very appreciated.