]] Mark Brown > Attempting to boot systemd on this system by adding init=/bin/systemd to > the end of the kernel command line results in: > > - The output of the fsck processes for the disks being displayed > - The screen changes to a higher resolution console mode > > but no further output or disk activity. The system still appears to be > running and ctrl-alt-delete triggers a clean reboot so it's presumably > blocked on something. This did work at some point in the past but it > was months ago so not useful for bisection. > > Is there any way to get more diagnostics out of the system?
http://fedoraproject.org/wiki/How_to_debug_Systemd_problems has a bunch of help for debugging systemd problems. The first thing I'd do is make sure you do not include «quiet» on the command line, it should then output more than you list above. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
