|
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@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
