Re: Changing runlevels at boot time

2017-12-04 Thread Ed Greshko
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

Re: Changing runlevels at boot time

2017-12-03 Thread Ed Greshko
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+A

Re: Changing runlevels at boot time

2017-12-03 Thread Bill Shirley
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 wrote: On

Re: Changing runlevels at boot time

2017-12-03 Thread Ed Greshko
On 12/04/17 09:01, Alex wrote: > Hi, > >>> On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko 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

Re: Changing runlevels at boot time

2017-12-03 Thread Alex
Hi, >> On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko 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

Re: Changing runlevels at boot time

2017-12-03 Thread Ed Greshko
On 12/04/17 08:13, Alex wrote: > Hi, > > On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko 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" >

Re: Changing runlevels at boot time

2017-12-03 Thread Alex
Hi, On Sun, Dec 3, 2017 at 4:53 PM, Ed Greshko 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 start

Re: Changing runlevels at boot time

2017-12-03 Thread Ed Greshko
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? -- Fedora Users List - The place to go to speculate endlessl

Re: Changing runlevels at boot time

2017-12-03 Thread stan
On Sun, 3 Dec 2017 10:23:54 -0500 Alex 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

Changing runlevels at boot time

2017-12-03 Thread Alex
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 linu