[lug] debugging workstation issue

[Davide Del Vento]

Not sure I understand this suggestion.

When/how could I get to the GRUB command line? At boot I certainly can, but
the problem is way past that point, i.e. when running (or right before
starting) the GUI.
Or do you mean at the NEXT boot after the hang? How that would be different
than looking at journalctl as Zan suggested?

Thanks for keeping up with ideas!
Davide

On Fri, Apr 10, 2020 at 9:32 AM D. Stimits <stimits at comcast.net> wrote:

> If you can get to the GRUB command line, then  you could tell it to just
> boot to non-graphical mode and perhaps it would work better. Even if this
> does not work better, then I would expect you'd be able to see more of the
> boot log. Depending on which flavor and release of Linux you use, the
> following appended to the kernel command line might do this for you:
> systemd.unit=multi-user.target
>
> Even if this doesn't work, then I'd expect it is at least some debug info.
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20200410/eae6bd86/attachment.html>