Kernel 3.5.0 Available for F17

[dcharlespyle]

Originally Posted by ferry

After updating to kernel 3.5.0 booting stops after grub. The last output is: Loading initial ramdisk ...
There is only black screen after this. I do not see any action and I have to make hard restart.
Previous kernel 3.4.6 is working without any problem.

I have notebook HP Compaq 6820s (Intel Core Duo T2410, graphic card ATI Mobility Radeon X1350)

Did you have any customizations in the kernel line in your grub configuration, such as nomodeset, modeset, or the like? Running fglrx?

If so, try putting those customized kernel parameters and so forth that worked for the previous kernel in your /etc/default/grub file and run:

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

Then, reboot your machine and see what happens then.

You might also want to rebuild initramfs. An easy way to do this is to set the default plymouth theme to the one that you had before and make sure to use the -R parameter, which will force a rebuild of initramfs:

sudo plymouth-set-default-theme -R <your chosen theme name>

Afterwards follow that up with a rebuild of your grub2 configuration file before rebooting again. Does the kernel work for you afterwards and do you get to gdm?

I usually run the above two above mentioned commands in a terminal window after every kernel installation just to make sure everything got updated correctly. Sometimes the installation of a new kernel does not do that as it should. I suspect that this might have been part of the problem for you since you mention the last thing you see involving the initial ramdisk. Let us know what results.

---------- Post added at 02:27 PM ---------- Previous post was at 02:25 PM ----------

Originally Posted by wneumann

Same problem as Ferry: Boot of kernel 3.5.0-2 stops after message "loading initial ramdisk" and screen goes blank with no hard disk action. Computer responds to ctl-alt-del to restart, and 3.4 kernels boot fine.

Dell Latitude D410

Try what I suggested above. What happens for you after you do that?

---------- Post added at 02:41 PM ---------- Previous post was at 02:27 PM ----------

Originally Posted by rich1974

unfortunatelly, today i update the kernel to 3.5 and my gnome-shell is broken. the screen is flickering or is all blank. when it is flickering, i can enter the tty and reboot, but in blank screen, i can do nothing, only hard shutdown.
using the kernel 3.4 the machine works fine.
my hardware is a dell inspirion 1521 with ATI mobility radeon X1270.

Use the prior kernel to boot up and log on. Do what I suggest above afterwards. Alternatively, you can try to get to a tty and do what I suggested above there. If you logon as root you won't have to use sudo before the commands on the command line.

I think that might help you. At least, I hope it will.

[ferry]

Originally Posted by dcharlespyle

Did you have any customizations in the kernel line in your grub configuration, such as nomodeset, modeset, or the like?

No. I did not customize anything.

[dcharlespyle]

Originally Posted by ferry

No. I did not customize anything.

OK. But still do what I suggested above and let me know what happens.

[ferry]

Originally Posted by dcharlespyle

OK. But still do what I suggested above and let me know what happens.

I did as root:
grub2-mkconfig -o /boot/grub2/grub.cfg
plymouth-set-default-theme -R charge

But without success.

[Dutchy]

You could try to boot with some verbose output and see if it mentions something:
- in grub press "e" on the troublesome kernel
- find the line that starts with linux /vmzlinux-3.5...
- remove “rhgb” (Red Hat graphical boot) to disable the graphical bootsplash
- remove "quiet" which suppresses many kernel messages
- append “rd.info” to get a more verbose output from dracut (probably unnecessary when "quiet" is not set)
- press "F10" to boot

[fishears]

don't know if its the same for you guys but my system showed the same symptoms with this kernel. I think due to virtualbox. When I removed the virtualbox kmod for 3.5.0-2 the system booted fine.
HTH

[ferry]

Originally Posted by fishears

don't know if its the same for you guys but my system showed the same symptoms with this kernel. I think due to virtualbox. When I removed the virtualbox kmod for 3.5.0-2 the system booted fine.
HTH

I use VMware Player. And booting is OK with kernel 3.4.6.

[fishears]

Originally Posted by ferry

I use VMware Player. And booting is OK with kernel 3.4.6.

What I mean is this:

I can only get kernel 3.5.0-2 to boot if I do not install the virtualbox kmod for 3.5.0-2
All previous kernels (including 3.4.6) have booted just fine with their respective virtualbox kmod installed.

That's why I think there is a problem with the 3.5.0-2 kernel and virtualbox... I could be wrong but this is my experience

[ferry]

Originally Posted by Dutchy

You could try to boot with some verbose output and see if it mentions something:
- in grub press "e" on the troublesome kernel
- find the line that starts with linux /vmzlinux-3.5...
- remove “rhgb” (Red Hat graphical boot) to disable the graphical bootsplash
- remove "quiet" which suppresses many kernel messages
- append “rd.info” to get a more verbose output from dracut (probably unnecessary when "quiet" is not set)
- press "F10" to boot

I did according your instructions. Booting stopped at this step (last 3 lines)

[   5.907859] [drm] radeon defaulting to kernel modesetting.
[   5.981456] [drm] radeon kernel modesetting enabled.
[   5.981547] fb: conflicting fb hw usage radeondrmfb vs. VESA VGA - removing generic driver.

[dcharlespyle]

Originally Posted by ferry

I did as root:
grub2-mkconfig -o /boot/grub2/grub.cfg
plymouth-set-default-theme -R charge

But without success.

If the above is the actual order in which you ran the commands, you did it in the wrong order.

Can you boot into the 3.5.0 kernel at all at either init 3 or single user mode? Also, check the /boot directory and make sure that there is an initramfs file that matches the 3.5.0 kernel. What did you find?

---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------

Originally Posted by ferry

I did according your instructions. Booting stopped at this step (last 3 lines)

[   5.907859] [drm] radeon defaulting to kernel modesetting.
[   5.981456] [drm] radeon kernel modesetting enabled.
[   5.981547] fb: conflicting fb hw usage radeondrmfb vs. VESA VGA - removing generic driver.

I often see this same message but it does not stop me from booting and logging in. It may be the command that follows that does it. Also, the kmod package version must match the version of the kernel for which it was intended. Is there an akmod package for the vbox that you could use instead?

[SiriusStarr]

Originally Posted by rich1974

unfortunatelly, today i update the kernel to 3.5 and my gnome-shell is broken. the screen is flickering or is all blank. when it is flickering, i can enter the tty and reboot, but in blank screen, i can do nothing, only hard shutdown.
using the kernel 3.4 the machine works fine.
my hardware is a dell inspirion 1521 with ATI mobility radeon X1270.

I have the same issue, as detailed here: http://forums.fedoraforum.org/showthread.php?t=283009. I have a Mobility Radeon X1600, and 3.5.0 left my system completely unusable graphically. Booting 3.4.6 works fine.

[ferry]

Originally Posted by dcharlespyle

If the above is the actual order in which you ran the commands, you did it in the wrong order.

Can you boot into the 3.5.0 kernel at all at either init 3 or single user mode? Also, check the /boot directory and make sure that there is an initramfs file that matches the 3.5.0 kernel. What did you find?

I often see this same message but it does not stop me from booting and logging in. It may be the command that follows that does it. Also, the kmod package version must match the version of the kernel for which it was intended. Is there an akmod package for the vbox that you could use instead?

So I did it in this order:

plymouth-set-default-theme -R charge
grub2-mkconfig -o /boot/grub2/grub.cfg

No success.


When I added nomodeset between boot parameters, I managed boot with kernel 3.5.0 but without correct display resolution.
There is appropriate initramfs-3.5.0-2.fc17.i686.PAE.img in /boot directory.

I do not use VirtualBox. So I do not need akmod for vbox.

[dcharlespyle]

Originally Posted by ferry

So I did it in this order:

plymouth-set-default-theme -R charge
grub2-mkconfig -o /boot/grub2/grub.cfg

No success.


When I added nomodeset between boot parameters, I managed boot with kernel 3.5.0 but without correct display resolution.
There is appropriate initramfs-3.5.0-2.fc17.i686.PAE.img in /boot directory.

....

Were you booted into the 3.5.0 kernel before running the above commands? Also, for future reference, the correct syntax in newer kernels for the radeon driver is radeon.modeset=0 to have no kernel modesetting and radeon.modeset=1 to enable kernel modesetting.

If I recall correctly, enabling full pcie 2.0 lane width is done by adding radeon.pcie_gen2=1 to your kernel line.

---------- Post added at 06:55 PM ---------- Previous post was at 12:00 PM ----------

Just a heads up. Watch out for kernel 3.5.0-4. That one did some really strange things on my system. It reports itself as 3.5.1-4, and tries to load those modules but can't because they don't exist, although the kernel is 3.5.0-4 in the /boot directory, and there were two initramfs files in /boot, one for version 3.5.0-4 and one for 3.5.1-4. I lost networking, proper video, other filesystems mounting and other things. I ended up having to remove that kernel for the time being, just so I could tell people about what it might do.

[zuchov]

Originally Posted by wneumann

Same problem as Ferry: Boot of kernel 3.5.0-2 stops after message "loading initial ramdisk" and screen goes blank with no hard disk action. Computer responds to ctl-alt-del to restart, and 3.4 kernels boot fine.

Dell Latitude D410

Confirming same behaviour.'Failed to start lsb'. Running AMD, 870G, nvidia and KDE. Can not boot earlier kernels either.

[dcharlespyle]

Update on kernel 3.5.0-4: Just for fun I reinstalled that kernel and renamed the kernel to its reported version, renamed the 3.5.0-4 directory in the /lib/modules directory to 3.5.1-4, renamed other files in /boot to match the kernel's reported version, modified the grub2.cfg file to show it as 3.5.1-4 and point to it and to the initramfs file matching the reported version/name, and rebooted. Works fine now!

It will probably play havoc with yum when the time to upgrade it comes but for now it is working. :-)

---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------

Originally Posted by zuchov

Confirming same behaviour.'Failed to start lsb'. Running AMD, 870G, nvidia and KDE. Can not boot earlier kernels either.

Boot into your 4.6 kernel. Check the /boot directory for the presence of the initramfs img file matching the name and version of the new kernel. If it not present, that is the cause of the error that you are seeing. You will need to remove that kernel and install it again.

$ su
# yum remove kernel-3.5.0-2
# yum update kernel

A new initramfs file to match the kernel will then be created in /boot and you should be good to go. Let me know one way or the other.