Updated Fedora 13, now will not boot

SgtDilbert · #1 23rd October 2010, 03:12 AM

Today I upgraded a few applications per the package updater and now I cannot boot with the latest kernel.
It looks like the nvidia driver wouldn't work, I got a [FAILED] message, followed by two [WARNING] messages. Then the Starting atd message displayed and the screen flickered a few times, then froze. I reset with the button on the PC.
I was able to log in using an older kernel: 2.6.34.7-56.fc13.x86_64. The newer kernel that wouldn't load may have been 2.6.34.7-61.fc13.x86_64.

I looked in the boot log and it had the log from the successful log; but, not the one that failed.

Code:

[DnA@DellXPS ~]$ cat /var/log/boot.log
        Welcome to Fedora 
        Press 'I' to enter interactive startup.
Starting udev: udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:1

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:2

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:3

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:4

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:5

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:6

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:7

                                                           [  OK  ]
Setting hostname DellXPS.LososNetwork:                     [  OK  ]
Setting up Logical Volume Management:   No volume groups found
                                                           [  OK  ]
Checking filesystems
/dev/sda2: clean, 141042/786432 files, 1273490/3145728 blocks
/dev/sda3: clean, 19164/10887168 files, 26330708/43520000 blocks
                                                           [  OK  ]
Remounting root filesystem in read-write mode:             [  OK  ]
Mounting local filesystems:                                [  OK  ]
Enabling local filesystem quotas:                          [  OK  ]
Enabling /etc/fstab swaps:                                 [  OK  ]
Entering non-interactive startup
ip6tables: Applying firewall rules:                        [  OK  ]
ip6tables: Loading additional modules: nf_conntrack_netbios[  OK  ]onntrack_ftp 
iptables: Applying firewall rules:                         [  OK  ]
iptables: Loading additional modules: nf_conntrack_netbios_[  OK  ]nntrack_ftp 
Checking for module nvidia.ko:                             [  OK  ]
Enabling the nvidia driver:                                [  OK  ]
Starting auditd:                                           [  OK  ]
Starting portreserve:                                      [  OK  ]
Starting system logger:                                    [  OK  ]
Enabling p4-clockmod driver (passive cooling only):        [  OK  ]
Starting irqbalance:                                       [  OK  ]
Starting rpcbind:                                          [  OK  ]
Starting mdmonitor:                                        [  OK  ]
Starting system message bus:                               [  OK  ]
Setting network parameters...                              [  OK  ]
Starting NetworkManager daemon:                            [  OK  ]
Starting Avahi daemon...                                   [  OK  ]
Starting NFS statd:                                        [  OK  ]
Starting RPC idmapd:                                       [  OK  ]
Starting cups:                                             [  OK  ]
Starting acpi daemon:                                      [  OK  ]
Starting HAL daemon:                                       [  OK  ]
Retrigger failed udev events                               [  OK  ]
Starting PC/SC smart card daemon (pcscd):                  [  OK  ]
Enabling Bluetooth devices:
Starting sshd:                                             [  OK  ]
Starting vsftpd for vsftpd:                                [  OK  ]
Starting sendmail:                                         [  OK  ]
Starting sm-client:                                        [  OK  ]
Starting abrt daemon:                                      [  OK  ]
Starting crond:                                            [  OK  ]
Starting NMB services:                                     [  OK  ]
Starting SMB services:                                     [  OK  ]
Starting atd:                                              [  OK  ]

Can I simply continue to use this older kernel?
Will the bad kernel be repaired?
Do I need to be concerned about the failed Nvidia driver when using this older kernel?

Thanks very much,

lsatenstein · #2 23rd October 2010, 03:59 AM

I have the identical problem. Wish I had an answer.

SgtDilbert · #3 23rd October 2010, 05:02 AM

I did find a similar issue (if not the same one) on another forum.

It included the following in the startup log.

Code:

Checking for module nvidia.ko: [FAILED]
nvidia.ko for kernel 2.6.34.7-56.fc13.x86_64 was not found. [WARNING]
The nvidia driver will not be enabled until one is found. [WARNING]

it mentions the older kernel (the one that actually does work) which seems kind of peculiar.

I also don't know why this problem occurred as shown on this forums so long ago when the update that caused the problem for me was done today. (10-21-10)

I have not yet tried the yum update as directed by this thread:

Any thoughts?
http://www.nvnews.net/vbulletin/showthread.php?t=155532

marinestu · #4 23rd October 2010, 04:40 PM

Hello

I too have come across the same issue on both of my Fedora 13 installs. I am sure that there will be a fix out for this soon....will be keeping an eye on developments here now. For the time being all I done is remove the nvidia drives from my kernel line in /boot/grub/grub.conf. I can now boot into the latest kernel minus my nvidia drivers. You can always just boot into your old kernel if you want to keep compiz working.

From /boot/grub/grub.conf

Changed from

kernel /vmlinuz-2.6.34.7-61.fc13.x86_64 ro root=/dev/mapper/vg_horse13-L
ogVol00 rd_LVM_LV=vg_horse13/LogVol00 rd_LVM_LV=vg_horse13/LogVol01 rd_NO_LUKS r
d_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYT
ABLE=uk rhgb quiet rdblacklist=nouveau vga=0×318 nouveau.modeset=0

to

kernel /vmlinuz-2.6.34.7-61.fc13.x86_64 ro root=/dev/mapper/vg_horse13-L
ogVol00 rd_LVM_LV=vg_horse13/LogVol00 rd_LVM_LV=vg_horse13/LogVol01 rd_NO_LUKS r
d_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYT
ABLE=uk rhgb quiet

Hope that helps for now

Stu

Blind32 · #5 23rd October 2010, 10:24 PM

Hi,

I ran into this same issue last night. I figured I'd have to start all over again. Took a shower to take my mind off of it and remembered I had my nvidia driver install file still in my /home/ dir. I was getting ths same errors as you guys.

Code:

Checking for module nvidia.ko: [FAILED]
nvidia.ko for kernel 2.6.34.7-56.fc13.x86_64 was not found. [WARNING]
The nvidia driver will not be enabled until one is found. [WARNING]

Then the screen would flash a few time and nothing else. From there if you hit ctrl + alt + F2, you will be presented with a CLI login. I logged in and navigated to my NVIDIA-Linux-x86_64-256.53.run file and

Code:

sudo ./NVIDIA-Linux-x86_64-256.53.run

After installation, rebooted and was able to get into the GUI.

From there I still had the following errors:

Code:

        Welcome to Fedora 
        Press 'I' to enter interactive startup.
Starting udev: udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:1

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:2

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:3

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:4

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:5

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:6

udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:7

To fix these, navigate to your /etc/udev/rules.d/50-euvccam.rules file. I made a backup then changed the SYSFS to ATTR like it says.

Code:

cd /etc/udev/rules.d/
cp 50-euvccam.rule 50-euvccam.rule.orig
vi 50-euvccam.rule

Change each instance of SYSFS to ATTR, save it and reboot. After this my computer boots up to the gui with the nvidia driver running and everything but I still have some boot errors. Not sure how to fix them and it's how I found this post.

Code:

iptables: Applying firewall rules:     [  OK  ]
Checking for module nvidia.ko:     [FAILED]
nvidia.ko for kernel 2.6.34.7-61.fc13.x86_64 was not found.    [WARNING]
The nvidia driver will not be enabled until one is found.    [WARNING]
/etc/rc5.d/S08nvidia: line 42:  1259 Segmentation fault      $exec disable
Starting auditd:     [  OK  ]
Starting portreserve:     [  OK  ]

Anyone have any ideas on how to fix the boot errors I have? I think it is like leftovers from the previous kernel driver.

mdandrews3 · #6 23rd October 2010, 10:28 PM

I have a similar problem. FC 13 freezes as it is booting (before getting to the login screen). There seems to be an additional problem as well. I can go back to a prior release, but not Virtual Box will not run in the prior release. Any suggestions?

SgtDilbert · #7 24th October 2010, 03:37 AM

I am hoping that this will be fixed in updates to fc13.

ozjd · #8 24th October 2010, 04:19 AM

The updated nvidia drivers have been released by RPMFusion and are appearing on mirrors now. Try updating again.

You could avoid these problems in future by using the akmod and not the kmod. The akmod automatically creates the kmod if it doesn't exist for the kernel you are booting.

I still get the udevd messages but they don't cause problems, everything is working.

SgtDilbert · #9 24th October 2010, 05:14 AM

How would I go about installing the akmod as opposed to the kmod?

btw; just updated again, time for a reboot, let's see what happens this time....

---------- Post added at 12:14 AM GMT ---------- Previous post was at 12:06 AM GMT ----------

Ok, I'm running kernel 2.6.34.7-61.fc13.x86_64 again and it works; but, I also get the udev errors. Should I be concerned by these?

Code:

[DnA@DellXPS log]$ cat /var/log boot.log
cat: /var/log: Is a directory
        Welcome to Fedora 
        Press 'I' to enter interactive startup.
Starting udev: udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:1

udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:2

udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:3

udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:4

udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:5

udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:6

udevd[524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:7

                                                           [  OK  ]
Setting hostname DellXPS.LososNetwork:                     [  OK  ]
Setting up Logical Volume Management:   No volume groups found
                                                           [  OK  ]
Checking filesystems
/dev/sda2: clean, 141076/786432 files, 1279881/3145728 blocks
/dev/sda3: clean, 19341/10887168 files, 26334845/43520000 blocks
                                                           [  OK  ]
Remounting root filesystem in read-write mode:             [  OK  ]
Mounting local filesystems:                                [  OK  ]
Enabling local filesystem quotas:                          [  OK  ]
Enabling /etc/fstab swaps:                                 [  OK  ]
Entering non-interactive startup
ip6tables: Applying firewall rules:                        [  OK  ]
ip6tables: Loading additional modules: nf_conntrack_netbios[  OK  ]onntrack_ftp 
iptables: Applying firewall rules:                         [  OK  ]
iptables: Loading additional modules: nf_conntrack_netbios_[  OK  ]nntrack_ftp 
Checking for module nvidia.ko:                             [  OK  ]
Enabling the nvidia driver: Driver already enabled.
                                                           [  OK  ]
Starting portreserve:                                      [  OK  ]
Starting system logger:                                    [  OK  ]
Enabling p4-clockmod driver (passive cooling only):        [  OK  ]
Starting irqbalance:                                       [  OK  ]
Starting rpcbind:                                          [  OK  ]
Starting mdmonitor:                                        [  OK  ]
Starting system message bus:                               [  OK  ]
Setting network parameters...                              [  OK  ]
Starting NetworkManager daemon:                            [  OK  ]
Starting Avahi daemon...                                   [  OK  ]
Starting NFS statd:                                        [  OK  ]
Starting RPC idmapd:                                       [  OK  ]
Starting cups:                                             [  OK  ]
Starting acpi daemon:                                      [  OK  ]
Starting HAL daemon:                                       [  OK  ]
Retrigger failed udev events                               [  OK  ]
Starting PC/SC smart card daemon (pcscd):                  [  OK  ]
Enabling Bluetooth devices:
Starting sshd:                                             [  OK  ]
Starting vsftpd for vsftpd:                                [  OK  ]
Starting sendmail:                                         [  OK  ]
Starting sm-client:                                        [  OK  ]
Starting abrt daemon:                                      [  OK  ]
Starting crond:                                            [  OK  ]
Starting NMB services:                                     [  OK  ]
Starting SMB services:                                     [  OK  ]
Starting atd:                                              [  OK  ]

ozjd · #10 24th October 2010, 05:35 AM

If you read them you will see they are messages and not actual errors. More importantly there are only "OK"s and no "fail"s in the lower part of the report so I wouldn't worry.

Missed your first question. The method is the same as installing the kmod but as you have that installed all you need to do is
yum install akmod-nvidia

xKaosx · #11 24th October 2010, 09:45 AM

i have the same problem, after updating, Fedora just hangs after loading (before login screen). any suggestions?

Edit: nevermind i fixed it by removing the nvidia 260 drivers and rolling back to the 256 drivers. The 260 drivers aren't working for me.

lsatenstein · #12 24th October 2010, 03:44 PM

I have the same problems as those listed above. My system does not have any NVIDEO cards. It is a pure intel mother board, with the onboard video.

It runs well with the live CD, which I will use to revert back to the previous kernel version. Anyway, in less than a month, After backing up my critical data, I will wipe the system clean and do a fresh installation.

mdandrews3 · #13 24th October 2010, 08:21 PM

I updated with the latest video drivers and now it works. I still have the problem with Virtual Box, though. It doesn't seem to be working any more.

vfulco · #14 26th October 2010, 04:21 PM

mdandrews3-- was your solution found using the direct from NVIDIA drivers or the RPMfusion ones? As for the former, I've tried all three 260.xx kind released with no success. akmods also fails for me although I almost always prefer direct. Have spent 3 weeks trying to figure out the upgrade from a perfectly good working 256 driver setup. Even re-used the old xorg.conf to no avail. This is a great example why Linux for the desktop won't grab significant share from Windows I am afraid.

mdandrews3 · #15 27th October 2010, 01:26 AM

I just used the drivers that downloaded in the update via RPMFusion library. Mine seems to be working fine.