I did a dnf update, got the new kernel, uname -a Linux pauls-server 4.0.7-300.fc22.x86_64 #1 SMP Mon Jun 29 22:15:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22, x86_64. So I boot a boot-repair CD, redo the grub, and reboot with a grub menu. my F22 is /dev/sdb6, and when I do a grub2-mkconfig it finds all of my OSes on sda & sdb. once I manually do the grub2-mkconfig & grub2-install /dev/sda I can reboot & grub shows all of my OSes. But if I just do the dnf update, get a new kernel, and reboot.. blank. Not sure what the update does, but it obviously takes out my grub install, not sure what it replaces it with. what should I look for, or what am I doing wrong?
If you press CTRL-ALT-F2, do you get a text console login prompt? Can you ssh to the machine?
If you can get access to the machine through one of these methods, then look in /var/log/Xorg.0.log for errors. This sounds like a video driver/configuration problem.
--Greg
On Sun, Jul 12, 2015 at 4:43 AM, Paul Cartwright pbcartwright@gmail.com wrote:
I did a dnf update, got the new kernel, uname -a Linux pauls-server 4.0.7-300.fc22.x86_64 #1 SMP Mon Jun 29 22:15:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22, x86_64. So I boot a boot-repair CD, redo the grub, and reboot with a grub menu. my F22 is /dev/sdb6, and when I do a grub2-mkconfig it finds all of my OSes on sda & sdb. once I manually do the grub2-mkconfig & grub2-install /dev/sda I can reboot & grub shows all of my OSes. But if I just do the dnf update, get a new kernel, and reboot.. blank. Not sure what the update does, but it obviously takes out my grub install, not sure what it replaces it with. what should I look for, or what am I doing wrong?
-- Paul Cartwright Registered Linux User #367800 and new counter #561587
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 07/12/2015 09:45 AM, Greg Woods wrote:
If you press CTRL-ALT-F2, do you get a text console login prompt? Can you ssh to the machine?
I will have to check that next time.. I am back up now, with a useable grub.
If you can get access to the machine through one of these methods, then look in /var/log/Xorg.0.log for errors. This sounds like a video driver/configuration problem.
I am using the opensource video driver for my radeon card, I stopped using the catalyst driver long ago.. mesa-* installed..
On Sun, Jul 12, 2015 at 4:43 AM, Paul Cartwright pbcartwright@gmail.com wrote:
I did a dnf update, got the new kernel, uname -a Linux pauls-server 4.0.7-300.fc22.x86_64 #1 SMP Mon Jun 29 22:15:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22, x86_64. So I boot a boot-repair CD, redo the grub, and reboot with a grub menu. my F22 is /dev/sdb6, and when I do a grub2-mkconfig it finds all of my OSes on sda & sdb. once I manually do the grub2-mkconfig & grub2-install /dev/sda I can reboot & grub shows all of my OSes. But if I just do the dnf update, get a new kernel, and reboot.. blank. Not sure what the update does, but it obviously takes out my grub install, not sure what it replaces it with. what should I look for, or what am I doing wrong?
Chances are it's a bug. All you did was accept and update, and then the update broke boot.
At the GRUB menu instead of waiting for the timeout or hitting return on the default option, hit e to edit the entry, find the linux16 or linuxefi line, go to the end and remove quiet rhgb, and then F10 or Control-X to boot and see if you get some messages that make it more clear what's going on. From the description I can't even tell if the problem is a GRUB failure or a kernel or initramfs failure.
A kernel update runs grubby which modifies grub.cfg. There is nothing that grubby does that grub2-install would fix. Whereas grub2-mkconfig obliterates the grubby modified grub.cfg, and writes a new one from scratch in its place.
On 07/12/2015 10:24 AM, Chris Murphy wrote:
On Sun, Jul 12, 2015 at 4:43 AM, Paul Cartwright pbcartwright@gmail.com wrote:
I did a dnf update, got the new kernel, uname -a Linux pauls-server 4.0.7-300.fc22.x86_64 #1 SMP Mon Jun 29 22:15:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22, x86_64. So I boot a boot-repair CD, redo the grub, and reboot with a grub menu. my F22 is /dev/sdb6, and when I do a grub2-mkconfig it finds all of my OSes on sda & sdb. once I manually do the grub2-mkconfig & grub2-install /dev/sda I can reboot & grub shows all of my OSes. But if I just do the dnf update, get a new kernel, and reboot.. blank. Not sure what the update does, but it obviously takes out my grub install, not sure what it replaces it with. what should I look for, or what am I doing wrong?
Chances are it's a bug. All you did was accept and update, and then the update broke boot.
could very well be that..
At the GRUB menu instead of waiting for the timeout or hitting return on the default option, hit e to edit the entry, find the linux16 or linuxefi line, go to the end and remove quiet rhgb, and then F10 or Control-X to boot and see if you get some messages that make it more clear what's going on. From the description I can't even tell if the problem is a GRUB failure or a kernel or initramfs failure.
problem is, only a blinking cursor, no grub menu.. that's my problem. I know how to edit grub menus using e.. since I have multiple ( mostly linux) OSes, grub gets updated every now & then, and I use "e" to make sure I am booting the latest kernel.
A kernel update runs grubby which modifies grub.cfg. There is nothing that grubby does that grub2-install would fix. Whereas grub2-mkconfig obliterates the grubby modified grub.cfg, and writes a new one from scratch in its place.
after a kernel update, I always do : $ ls -l /boot ls -l /boot/grub2/
and they are always updated after the kernel install.. so it seems maybe grubby is screwing up..
On Sun, Jul 12, 2015 at 8:43 AM, Paul Cartwright pbcartwright@gmail.com wrote:
problem is, only a blinking cursor, no grub menu.. that's my problem. I know how to edit grub menus using e.. since I have multiple ( mostly linux) OSes, grub gets updated every now & then, and I use "e" to make sure I am booting the latest kernel.
kernel update RPMs call new-kernel-pkg which in turn call grubby, but none of that stuff ever touches any installed bootloader code. The only thing modified is the grub.cfg. I don't know how/why, but it's possible the modification of the grub.cfg is actually corrupting it but then GRUB should complain if it can't parse grub.cfg
Sounds like this is a computer with BIOS firmware. On BIOS, Fedora puts grub.cfg at /boot/grub2/, and on UEFI it's at /boot/efi/EFI/fedora/.
On 07/12/2015 11:31 PM, Chris Murphy wrote:
On Sun, Jul 12, 2015 at 8:43 AM, Paul Cartwright pbcartwright@gmail.com wrote:
problem is, only a blinking cursor, no grub menu.. that's my problem. I know how to edit grub menus using e.. since I have multiple ( mostly linux) OSes, grub gets updated every now & then, and I use "e" to make sure I am booting the latest kernel.
kernel update RPMs call new-kernel-pkg which in turn call grubby, but none of that stuff ever touches any installed bootloader code. The only thing modified is the grub.cfg. I don't know how/why, but it's possible the modification of the grub.cfg is actually corrupting it but then GRUB should complain if it can't parse grub.cfg
Sounds like this is a computer with BIOS firmware. On BIOS, Fedora puts grub.cfg at /boot/grub2/, and on UEFI it's at /boot/efi/EFI/fedora/.
mine was Windows 7, so it is BIOS.. I always do grub2-mkconfig -o /boot/grub2/grub.cfg
before I do the next update I'll copy grub.cfg, then run the update & diff.. now, waiting for the next new kernel:)
On 07/12/2015 03:43 AM, Paul Cartwright wrote:
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22
Next time you update, save a copy of /boot/efi/EFI/fedora/grub.cfg, then run "grub2-mkconfig".
You can compare them to see the changes: diff -u saved-grub.cfg /boot/efi/EFI/fedora/grub.cfg
That should tell you what's breaking when you update.
On 07/12/2015 10:47 PM, Gordon Messmer wrote:
On 07/12/2015 03:43 AM, Paul Cartwright wrote:
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22
Next time you update, save a copy of /boot/efi/EFI/fedora/grub.cfg, then run "grub2-mkconfig".
You can compare them to see the changes: diff -u saved-grub.cfg /boot/efi/EFI/fedora/grub.cfg
That should tell you what's breaking when you update.
there is no grub.cfg in fedora, only: ls BOOT.CSV gcdx64.efi grubx64.efi shim.efi fonts grubenv MokManager.efi shim-fedora.efi
grub.cfg is in /boot/grub2, but I will try that next time, thanks!
On 07/12/2015 10:47 PM, Gordon Messmer wrote:
On 07/12/2015 03:43 AM, Paul Cartwright wrote:
rebooted and... a blinking cursor on a black background.. this seems to happen everytime now when I get a new kernel in F22
Next time you update, save a copy of /boot/efi/EFI/fedora/grub.cfg, then run "grub2-mkconfig".
You can compare them to see the changes: diff -u saved-grub.cfg /boot/efi/EFI/fedora/grub.cfg
That should tell you what's breaking when you update.
ok, I got a new kernel today, 8-300 . so I copied the grub.cfg to grub.8-300 and did another grub2-mkconfig -o /boot/grub2/grub.cfg and the new grub.cfg is different that what the system made after it installed the new kernel.. I am not sure what the difference is..
-rw-r--r-- 1 root root 23880 Jul 19 07:45 grub.8-300 -rw-r--r-- 1 root root 25550 Jul 19 07:46 grub.cfg
[root@pauls-server grub2]# diff grub.8-300 grub.cfg diff grub.8-300 grub.cfg 72c72 < menuentry 'Fedora (4.0.8-300.fc22.x86_64+debug) 22 (Twenty Two)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.0.7-300.fc22.x86_64-advanced-a1f0e69f-f7b4-41b3-8a88-adbc6d59d957' { ---
menuentry 'Fedora (4.0.8-300.fc22.x86_64) 22 (Twenty Two)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.0.8-300.fc22.x86_64-advanced-a1f0e69f-f7b4-41b3-8a88-adbc6d59d957' { 84,85c84,85 < linux16 /boot/vmlinuz-4.0.8-300.fc22.x86_64+debug root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet LANG=en_US.UTF-8 < initrd16 /boot/initramfs-4.0.8-300.fc22.x86_64+debug.img ---
linux16 /boot/vmlinuz-4.0.8-300.fc22.x86_64
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet
initrd16 /boot/initramfs-4.0.8-300.fc22.x86_64.img
87c87 < menuentry 'Fedora (4.0.8-300.fc22.x86_64) 22 (Twenty Two)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.0.7-300.fc22.x86_64-advanced-a1f0e69f-f7b4-41b3-8a88-adbc6d59d957' { ---
menuentry 'Fedora (4.0.8-300.fc22.x86_64) 22 (Twenty Two) (recovery
mode)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.0.8-300.fc22.x86_64-recovery-a1f0e69f-f7b4-41b3-8a88-adbc6d59d957' { 99c99 < linux16 /boot/vmlinuz-4.0.8-300.fc22.x86_64 root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet LANG=en_US.UTF-8 ---
linux16 /boot/vmlinuz-4.0.8-300.fc22.x86_64
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro single rhgb quiet 114c114 < linux16 /boot/vmlinuz-4.0.7-300.fc22.x86_64 root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet ---
linux16 /boot/vmlinuz-4.0.7-300.fc22.x86_64
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet 144c144 < linux16 /boot/vmlinuz-4.0.6-300.fc22.x86_64 root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet ---
linux16 /boot/vmlinuz-4.0.6-300.fc22.x86_64
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet 161a162,191
menuentry 'Fedora (4.0.8-300.fc22.x86_64+debug) 22 (Twenty Two)'
--class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.0.8-300.fc22.x86_64+debug-advanced-a1f0e69f-f7b4-41b3-8a88-adbc6d59d957' {
load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd1,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6
--hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6' a1f0e69f-f7b4-41b3-8a88-adbc6d59d957
else search --no-floppy --fs-uuid --set=root
a1f0e69f-f7b4-41b3-8a88-adbc6d59d957
fi linux16 /boot/vmlinuz-4.0.8-300.fc22.x86_64+debug
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet
initrd16 /boot/initramfs-4.0.8-300.fc22.x86_64+debug.img} menuentry 'Fedora (4.0.8-300.fc22.x86_64+debug) 22 (Twenty Two)
(recovery mode)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.0.8-300.fc22.x86_64+debug-recovery-a1f0e69f-f7b4-41b3-8a88-adbc6d59d957' {
load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd1,msdos6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6
--hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6' a1f0e69f-f7b4-41b3-8a88-adbc6d59d957
else search --no-floppy --fs-uuid --set=root
a1f0e69f-f7b4-41b3-8a88-adbc6d59d957
fi linux16 /boot/vmlinuz-4.0.8-300.fc22.x86_64+debug
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro single rhgb quiet
initrd16 /boot/initramfs-4.0.8-300.fc22.x86_64+debug.img}
174c204 < linux16 /boot/vmlinuz-4.0.7-300.fc22.x86_64+debug root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet ---
linux16 /boot/vmlinuz-4.0.7-300.fc22.x86_64+debug
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet 204c234 < linux16 /boot/vmlinuz-4.0.6-300.fc22.x86_64+debug root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet ---
linux16 /boot/vmlinuz-4.0.6-300.fc22.x86_64+debug
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet 233c263 < linux16 /boot/vmlinuz-0-rescue-78db501f7f8d403c938e4d646de9a9c4 root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet ---
linux16 /boot/vmlinuz-0-rescue-78db501f7f8d403c938e4d646de9a9c4
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet 261c291 < linux16 /boot/vmlinuz-0-rescue-7a49ecb4c939408baf9f3ced07af2fe4 root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet ---
linux16 /boot/vmlinuz-0-rescue-7a49ecb4c939408baf9f3ced07af2fe4
root=UUID=a1f0e69f-f7b4-41b3-8a88-adbc6d59d957 ro rhgb quiet 278c308 < if [ "x$default" = 'Fedora (4.0.7-300.fc22.x86_64) 22 (Twenty Two)' ]; then default='Advanced options for Fedora>Fedora (4.0.7-300.fc22.x86_64) 22 (Twenty Two)'; fi; ---
if [ "x$default" = 'Fedora (4.0.8-300.fc22.x86_64) 22 (Twenty Two)' ];
then default='Advanced options for Fedora>Fedora (4.0.8-300.fc22.x86_64) 22 (Twenty Two)'; fi;
On 07/19/2015 03:39 PM, Gordon Messmer wrote:
Please use "diff -u". Standard diff format is mostly unreadable. Unified diff is much more comprehensible.
... and maybe output to a file and attach that file. Your client is wrapping lines, making it hard to read the output.
diff -u attached. It looks worse ( to me ) than the last one.
The diff isn't that useful because the old and new grub.cfgs are too different. They're different because grub.cfg is modified by grubby rather than being created from scratch everytime there's a new kernel install. So the more kernels are installed, the more different the grub.cfg becomes since grubby's modifications aren't the same as what grub2-mkconfig would produce.
Chris Murphy
On 07/19/2015 04:52 AM, Paul Cartwright wrote:
ok, I got a new kernel today, 8-300 . so I copied the grub.cfg to grub.8-300 and did another grub2-mkconfig -o /boot/grub2/grub.cfg and the new grub.cfg is different that what the system made after it installed the new kernel.. I am not sure what the difference is..
It looks like you have kernel-debug installed, and that is the default kernel immediately after an update, but not the default kernel after running grub2-mkconfig.
I'm not sure why the debug kernel would not run on your system, but that'd be the place to start looking. If you're not debugging your kernel, you could probably just remove the kernel-debug* packages.
On 07/20/2015 01:55 PM, Gordon Messmer wrote:
ok, I got a new kernel today, 8-300 . so I copied the grub.cfg to grub.8-300 and did another grub2-mkconfig -o /boot/grub2/grub.cfg and the new grub.cfg is different that what the system made after it installed the new kernel.. I am not sure what the difference is..
It looks like you have kernel-debug installed, and that is the default kernel immediately after an update, but not the default kernel after running grub2-mkconfig.
I'm not sure why the debug kernel would not run on your system, but that'd be the place to start looking. If you're not debugging your kernel, you could probably just remove the kernel-debug* packages.
I have booted debug kernels before, mostly in error, because it was the default:) it disables the network ( at least it did for me), so it was easy to sport that I was in the wrong place.
I understand it is different & sets the debug kernel as default, but IN THE PAST, when I just installed the new kernel & let grubby do it's thing, when I rebooted, all I got was a bouncing underscore, and no grub menu.. the fact that grubby does create a different grub.cfg than when I do grub2-mkconfig still bothers me.. shouldn't they be the same??
-
Chris Murphy -
Gordon Messmer -
Greg Woods -
Paul Cartwright