Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386
Michael Biebl
biebl at debian.org
Sun Mar 18 23:28:45 GMT 2018
Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> I upgraded systemd, and after a failure to boot, realized it was on
> systemd:i386.
> I went into a recovery environment and removed systemd:i386 and
> installed systemd.
> After that It failed to boot at a different location.
> I was able to get it to boot by removing the kernel parameter
> for the nouveau driver to use the binary firmware.
Just to be clear: What is this bug report about?
About the first issue, where systemd:i386 was installed on a amd64
system (and you probably ran into #869719)
or the second issue? The log you posted, is that with systemd:amd64 or
systemd:i386?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180319/d2cbcaf0/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list