On Mon, Apr 13, 2020 at 12:42:20PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> 
> > On Sun, Apr 12, 2020 at 07:37:39PM +0200, Mathieu Othacehe wrote:
> >> 
> >> > Apr 12 16:35:35 localhost vmunix: [   48.124498] uvesafb: fb0: VESA VGA frame buffer device
> >> > Apr 12 16:35:35 localhost vmunix: [   48.129053] shepherd[1]: Service uvesafb has been started.
> >> > Apr 12 16:35:40 localhost shepherd[1]: Service dbus-system could not be started. 
> >> > Apr 12 16:35:40 localhost shepherd[1]: Service networking depends on dbus-system. 
> >> > Apr 12 16:35:40 localhost shepherd[1]: Service networking could not be started. 
> >> 
> >> I suspect something is going wrong here. The 'networking' service is
> >> indeed not started, probably because 'dbus-system' could not be started.
> >> 
> >
> > That may be the case.  Note dbus-system was started later on, but
> > networking was not.
> 
> Did /var/log/messages have additional hints as to why dbus-system was
> not started?
> 

Nothing.  However, by now I burned a new image to DVD with the
attached patch.  But I realize my mistake now; due to dbus-daemon
eventually starting after networking failed, the logs are lost.

I inserted the DVD in an external drive for my slightly faster Macbook
(but the DVD drive seems much slower) and (realizing unlike USB I
needed to add nomodeset) I got the same error.  So the error occurs
when booting any computer from DVD, it seems.

I attach the unhelpful logs, even though I believe the dbus-daemon log
got overwritten by a subsequent successful start …

I do not know how to keep earlier logs.  Maybe I need to pipe it in a
custom gexp?

Regards,
Florian