Hi, I have a fedora27 system that boots to a blank screen with the latest kernels. This has been happening since the system was at least a fedora26 system.
If I boot to multi-user first, then switch to graphical boot, it works fine.
Adding "3" to the grub command-line ("e" then append "3" to linux16 line, then ctrl-x to boot) does not work to boot the system to multi-user as per the documentation. However, adding "systemd.unit=multi-user.target" does.
Also, the rescue kernel also works, but lacks networking. What's the difference between these two kernels or these two grub invocations? Notice I've also disabled selinux for now.
Any ideas why the system would become unresponsive and boot to a blank screen with the latest kernels?
menuentry 'Fedora (4.13.13-300.fc27.x86_64) 27 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.13.13-300.fc27.x86_64-advanced-dedb2196-1933-4fa3-b8bd-5123930308b9' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 --hint='hd0,msdos1' 9522bf8d-db18-48e9-a7d9-ae9c52d4343d else search --no-floppy --fs-uuid --set=root 9522bf8d-db18-48e9-a7d9-ae9c52d4343d fi linux16 /vmlinuz-4.13.13-300.fc27.x86_64 root=UUID=dedb2196-1933-4fa3-b8bd-5123930308b9 ro security=0 initrd16 /initramfs-4.13.13-300.fc27.x86_64.img } menuentry 'Fedora (0-rescue-4289f41d85794f5ebc59779ac5cdcc51) 27 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-4289f41d85794f5ebc59779ac5cdcc51-advanced-dedb2196-1933-4fa3-b8bd-5123930308b9' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 --hint='hd0,msdos1' 9522bf8d-db18-48e9-a7d9-ae9c52d4343d else search --no-floppy --fs-uuid --set=root 9522bf8d-db18-48e9-a7d9-ae9c52d4343d fi linux16 /vmlinuz-0-rescue-4289f41d85794f5ebc59779ac5cdcc51 root=UUID=dedb2196-1933-4fa3-b8bd-5123930308b9 ro security=0 initrd16 /initramfs-0-rescue-4289f41d85794f5ebc59779ac5cdcc51.img }
On Sun, 3 Dec 2017 10:23:54 -0500 Alex mysqlstudent@gmail.com wrote:
Hi, I have a fedora27 system that boots to a blank screen with the latest kernels. This has been happening since the system was at least a fedora26 system.
Any ideas why the system would become unresponsive and boot to a blank screen with the latest kernels?
I don't know, but you could try rebuilding the initramfs with dracut. In /boot run
/usr/bin/dracut -f -H -v --debug initramfs-4.13.13-300.fc27.x86_64.img 4.13.13-300.fc27.x86_64 > dracut_output 2> dracut_error
Then reboot, and see if the custom build from a running system will find everything.
On 12/03/17 23:23, Alex wrote:
If I boot to multi-user first, then switch to graphical boot, it works fine.
Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Hi,
On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko ed.greshko@gmail.com wrote:
On 12/03/17 23:23, Alex wrote:
If I boot to multi-user first, then switch to graphical boot, it works fine.
Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Is startx different from "systemctl isolate graphical.target"?
I believe I've used both, but don't remember what I did last or if both of them produce the same results.
(I'm new to Wayland but not Xorg or X11)
On 12/04/17 08:13, Alex wrote:
Hi,
On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko ed.greshko@gmail.com wrote:
On 12/03/17 23:23, Alex wrote:
If I boot to multi-user first, then switch to graphical boot, it works fine.
Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Is startx different from "systemctl isolate graphical.target"?
Yes. With startx you don't start a display manager (gdm, sddm, or whatever you've chosen). You won't have a login screen.
I believe I've used both, but don't remember what I did last or if both of them produce the same results.
(I'm new to Wayland but not Xorg or X11)
It sounds as if you have a standard Workstation installation and as such gdm will be the DM. And, it sounds as if gdm isn't starting.
When you boot and get to the blank screen you should be able to get to a Virtual Terminal (ctrl-alt-F2) and login to see what is going on.
Hi,
On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko ed.greshko@gmail.com wrote:
On 12/03/17 23:23, Alex wrote:
If I boot to multi-user first, then switch to graphical boot, it works fine.
Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Is startx different from "systemctl isolate graphical.target"?
Yes. With startx you don't start a display manager (gdm, sddm, or whatever you've chosen). You won't have a login screen.
Sure, I just meant is it the same X server.
I believe I've used both, but don't remember what I did last or if both of them produce the same results.
(I'm new to Wayland but not Xorg or X11)
It sounds as if you have a standard Workstation installation and as such gdm will be the DM. And, it sounds as if gdm isn't starting.
When you boot and get to the blank screen you should be able to get to a Virtual Terminal (ctrl-alt-F2) and login to see what is going on.
Yes, that I know, and it does not work. The HDD light goes on occasionally, but the system is unresponsive.
On 12/04/17 09:01, Alex wrote:
Hi,
On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko ed.greshko@gmail.com wrote:
On 12/03/17 23:23, Alex wrote:
If I boot to multi-user first, then switch to graphical boot, it works fine.
Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Is startx different from "systemctl isolate graphical.target"?
Yes. With startx you don't start a display manager (gdm, sddm, or whatever you've chosen). You won't have a login screen.
Sure, I just meant is it the same X server.
Then I suppose you should have asked that question. :-)
Yes.
I believe I've used both, but don't remember what I did last or if both of them produce the same results.
(I'm new to Wayland but not Xorg or X11)
It sounds as if you have a standard Workstation installation and as such gdm will be the DM. And, it sounds as if gdm isn't starting.
When you boot and get to the blank screen you should be able to get to a Virtual Terminal (ctrl-alt-F2) and login to see what is going on.
Yes, that I know, and it does not work. The HDD light goes on occasionally, but the system is unresponsive.
OK. You'd not mentioned before now that you've tried getting to a Virtual Terminal. A system booted to a blank screen can be viewed as unresponsive. So, there's a bit of ambiguity in what you're writing.
Maybe try removing rhgb and quiet from the boot params to see maybe see where the hangup is.
If you're running rsyslog, try adding this to rsyslog.conf: # All messages on last terminal *.* /dev/tty12 Switch to tty12 (Ctrl+Alt+F2) to see all messages.
Bill
On 12/3/2017 8:18 PM, Ed Greshko wrote:
On 12/04/17 09:01, Alex wrote:
Hi,
On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko ed.greshko@gmail.com wrote:
On 12/03/17 23:23, Alex wrote:
If I boot to multi-user first, then switch to graphical boot, it works fine.
Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Is startx different from "systemctl isolate graphical.target"?
Yes. With startx you don't start a display manager (gdm, sddm, or whatever you've chosen). You won't have a login screen.
Sure, I just meant is it the same X server.
Then I suppose you should have asked that question. :-)
Yes.
I believe I've used both, but don't remember what I did last or if both of them produce the same results.
(I'm new to Wayland but not Xorg or X11)
It sounds as if you have a standard Workstation installation and as such gdm will be the DM. And, it sounds as if gdm isn't starting.
When you boot and get to the blank screen you should be able to get to a Virtual Terminal (ctrl-alt-F2) and login to see what is going on.
Yes, that I know, and it does not work. The HDD light goes on occasionally, but the system is unresponsive.
OK. You'd not mentioned before now that you've tried getting to a Virtual Terminal. A system booted to a blank screen can be viewed as unresponsive. So, there's a bit of ambiguity in what you're writing.
Maybe try removing rhgb and quiet from the boot params to see maybe see where the hangup is.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 12/04/17 13:38, Bill Shirley wrote:
If you're running rsyslog, try adding this to rsyslog.conf: # All messages on last terminal *.* /dev/tty12 Switch to tty12 (Ctrl+Alt+F2) to see all messages.
He seems to be saying he can't do "Ctrl+Alt+F2" as the system is "unresponsive".
Bill
On 12/3/2017 8:18 PM, Ed Greshko wrote:
On 12/04/17 09:01, Alex wrote:
Hi,
On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko ed.greshko@gmail.com wrote:
On 12/03/17 23:23, Alex wrote: > If I boot to multi-user first, then switch to graphical boot, it works fine. Are you saying that after you get to multi-user mode you do something like "init 5" to get t a GUI login or you use startx?
Is startx different from "systemctl isolate graphical.target"?
Yes. With startx you don't start a display manager (gdm, sddm, or whatever you've chosen). You won't have a login screen.
Sure, I just meant is it the same X server.
Then I suppose you should have asked that question. :-)
Yes.
I believe I've used both, but don't remember what I did last or if both of them produce the same results.
(I'm new to Wayland but not Xorg or X11)
It sounds as if you have a standard Workstation installation and as such gdm will be the DM. And, it sounds as if gdm isn't starting.
When you boot and get to the blank screen you should be able to get to a Virtual Terminal (ctrl-alt-F2) and login to see what is going on.
Yes, that I know, and it does not work. The HDD light goes on occasionally, but the system is unresponsive.
OK. You'd not mentioned before now that you've tried getting to a Virtual Terminal. A system booted to a blank screen can be viewed as unresponsive. So, there's a bit of ambiguity in what you're writing.
Maybe try removing rhgb and quiet from the boot params to see maybe see where the hangup is.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 12/04/17 09:01, Alex wrote:
Yes, that I know, and it does not work. The HDD light goes on occasionally, but the system is unresponsive.
Along with the rhgb and quiet suggestions you can also do the following.....
1. Boot normally and get to the "blank screen - unresponsive" condition.
2. Wait a bit, maybe 5 minutes, since you said you see some disk activity at times.
3. Reboot to run multi-user mode.
4. Run "journalctl -b -1 > failed-boot"
5. Check the file failed-boot to see if you find something that points in the direction. If not, upload it to a place where others can examine it.
-
Alex -
Bill Shirley -
Ed Greshko -
Ed Greshko -
stan