Fedora 16 kernel 3.3.0.4 boot failure

[Beeblebrox]

Hello,

I am new to Fedora and I have been using it for a couple of months now without any problems. Today, I installed a bunch of updates including the update to kernel 3.3.0.4 with the gui and did the required restart. Now, I cannot boot Fedora anymore. It always stops at "Started Display Manager". I already tried to reinstall the kdm and the nvidia drivers.
I am using Fedora 16 KDE with an i5 64bit processor and the NVidia drivers because I had graphics issues when I tried to use the nouveau ones.

I would be happy if anybody can help me... Right now I am using one of the old 3.2 kernel versions.

Thanks.

[Mishka]

Hi,

This morning I could not boot either because of graphic issue. So I rebooted and chose the previous kernel in the grub, this one was fine, then I updated the package akmod-nvidia and tried again the kernel 3.3 which worked smoothly.
Do you have the akmod-nvidia package installed ?

Hope it helps.

[jbuckley2004]

This is starting to drive me crazy!

It's not really an issue in the sense that something's buggy. It's not. It's that not all the mirrors have been sync'ed up with the latest version of kmod and akmod to go with the new 3.3 kernel. (Even akmod, whose purpose is to generate kmod when the kernel is updated can't help because the kernel source isn't there yet to build it from.)

My rant is that the delays in getting kmod out have been long and seem to be getting longer. The situation is deteriorating.

But regardless, I'm hearing that you can successfully boot into your previous kernel (from grub). After that, the easiest course seems to be to just wait for TPTB to sync up the mirrors.

[Beeblebrox]

Hello,

and thanks for your answers. So did I understand you right that I can just wait until my Fedora updater tells me that there are updates again and hopefully the 3.3 kernel will work fine then?

@Mishka: I do have the nvidia drivers and they worked fine. There are no updates for them right now, at least that's what the yum installer says.

I have noticed that in both the working, old kernel and the non-working 3.3 kernel I get a fail message about akmods. So I am still slightly confused if this an akmod problem or if something else was going wrong during the updates...


Thanks.

[sidebrnz]

There's a known bug with akmods (Look in the rpmfusion BZ.) and an update should be ready RSN. Today's update included a kmod-nvidia for the newest kernel. I haven't had time to reboot, yet, but that should fix it. If not, I'll just reboot again into the previous kernel.

[jbuckley2004]

I'm troubled that I haven't gotten the the new kmod-nvidia yet, although many seem to have gotten it as early as yesterday.

[DBelton]

Originally Posted by jbuckley2004

This is starting to drive me crazy!

It's not really an issue in the sense that something's buggy. It's not. It's that not all the mirrors have been sync'ed up with the latest version of kmod and akmod to go with the new 3.3 kernel. (Even akmod, whose purpose is to generate kmod when the kernel is updated can't help because the kernel source isn't there yet to build it from.)

My rant is that the delays in getting kmod out have been long and seem to be getting longer. The situation is deteriorating.

But regardless, I'm hearing that you can successfully boot into your previous kernel (from grub). After that, the easiest course seems to be to just wait for TPTB to sync up the mirrors.

Now that is interesting. I have never had issues with the source needed to build the akmods not being available when the kernels are updated.

The kernel-devel and kernel-headers always are pushed to the repos at the same time as the kernel. (Those are all you need to build the akmod. You don't need the full kernel source, but it gets pushed to the repo at the same time the kernel does.

Now the issue with the kmod not being available when the kernel is released.. That is not a Fedora issue, and will always have some delay. Fedora does not control rpmfusion, and has no control over when they get the updated kmod into their repo. Rpmfusion and Fedora are two totally separate entities.

However, you do get the kmod faster if you have the rpmfusion testing repos enabled, since they get put in there first, then pushed into the regular updates repo.

[Beeblebrox]

Okay,

so I installed the drivers manually from the latest rpmfusion repo

http://download1.rpmfusion.org/nonfr...tes/16/x86_64/

and now I can boot the new kernel again :-) Let's see how it works with the next kernel update.


Thanks to everybody for helping me.

[sidebrnz]

I just rebooted into the latest kernel and kmod-nvidia loaded without any trouble. For me, at least, all's well again.

[rubensduarte13]

Hello.
After updating the kernel to version 3.4.2-1.fc16.x86_64 (Fedora 16 x64 bits) I got the same problem of not booting Fedora anymore, it freezes at "Started Display Manager".

I installed a fresh version of F16 64 bits and then I got some issues trying to install the NVIDIA official drivers for my GeForce GTX 550 Ti, and after successfully installing these video drivers everything was working fine. So I decided to update everything in my F16 including the kernel. After the update, I got the problem of freezing at "Started Display Manager".

I solved this by installing the kmod-nvidia package from the RPM Fusion repository. I did it automaticaly using yum:

1) Add RPM Fusion free in your repo list: go to http://rpmfusion.org/Configuration and click/download the "RPM Fusion free for Fedora 15, 16 and 17". After download double click the file and install it.

2) Add RPM Fusion nonfree in your repo list - click/download the "RPM Fusion nonfree for Fedora 15, 16 and 17". After download double click the file and install it.

3) Open a terminal, log in as root, and type:
yum update

4) Wait until yum updates your repo. After that, still logged as root, type:
yum install kmod-nvidia

5) Reboot.

That worked for me. I am not sure if step #2 is needed.

Rubens

[shayan]

Thanks rubensduarte13.
This solved my problem in Fedora 17.