kernel – Luxing Huang https://luxing.im Thoughs and things Tue, 11 Mar 2014 11:41:32 +0000 en-CA hourly 1 https://wordpress.org/?v=6.7.2 58771605 Fedora 20 Hangs on Booting screen on Lenovo IdeaPad Y510P https://luxing.im/fedora-20-hangs-on-booting-screen-on-lenovo-ideapad-y510p/ https://luxing.im/fedora-20-hangs-on-booting-screen-on-lenovo-ideapad-y510p/#respond Tue, 11 Mar 2014 11:41:32 +0000 http://blog.luxing.im/?p=312 Continue reading "Fedora 20 Hangs on Booting screen on Lenovo IdeaPad Y510P"

]]> This problem has been sometime for me. Bumblebee-nvidia is used for graphical applications. No matter what kernel version I use, the first boot after a complete shutdown the computer would freeze on plymouth screen, I’d have to manually hit ctrl+alt+del to reboot and then it could load into X.

During booting, you could press any arrow key to go to “noisy” screen to see live status of everything. There’s a message like this:

(6 of 8) A start job is running for Wait for Plymouth Boot Screen to Quit...

I noticed that it’s about the plymouth booting module which hangs at boot and maybe it’s that which causes kernel loops and gdm fails. Here is my solution of workaround.

sudo yum remove plymouth

Edit /etc/defaults/grub, remove “quiet” from “GRUB_CMDLINE_LINUX”, re-configure grub.cfg at /boot/efi/EFI/fedora by 

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Reboot.

Now you don’t see a plymouth booting screen, instead you see a lot of logs are generated it makes you look geeky. Booting doesn’t hang any more.

]]> https://luxing.im/fedora-20-hangs-on-booting-screen-on-lenovo-ideapad-y510p/feed/ 0 312 Boot into new kernel in Fedora 19 https://luxing.im/boot-into-new-kernel-in-fedora-19/ https://luxing.im/boot-into-new-kernel-in-fedora-19/#respond Fri, 04 Oct 2013 11:48:46 +0000 http://blog.luxing.im/?p=22 Continue reading "Boot into new kernel in Fedora 19"

]]> Since kernel 3.10, everytime I did a kernel upgrade, my fedora just wouldn’t boot into this new kernel. Also I have previously set my TIMEOUT to 0, which means I won’t have a choice during boot.

The problem is not big nor severe, but it did took me some time to figure how.

grub2 in Fedora is a little bit different with grub in CentOS. In CentOS you could upgrade your kernel and boot into this new kernel automatically after reboot, whereas in Fedora you need to adjust the grub.cfg file manually.

The step was simple enough but it took me some time to look for the documents.

All I needed was to change the default TIMEOUT to 5 and another line of command: Using root’s privilege and modify /etc/defaults/grub, set the timeout to 5 and do a grub2 reconfiguration:

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

And that’s it! Enjoy your new kernel!

You may need the same steps when you compile, upgrade and/or install your custom/new kernel.

]]> https://luxing.im/boot-into-new-kernel-in-fedora-19/feed/ 0 22