Op vrijdag 26 februari 2016 10:57:02 schreef Freek de Kruijf: > Op donderdag 25 februari 2016 10:02:30 schreef Freek de Kruijf: > > Op zondag 21 februari 2016 23:07:19 schreef Dirk Müller: > > > Hi Freek, > > > > > > > After that it shows a number of messages typical ones one see during > > > > boot. > > > > There is an an error message about being not able to mount /boot/efi > > > > The system ends in an emergency state. > > > > > > Can you provide literal output / screenshot (send it off-list please)? > > > > > > > mount[5289]: mount: unknown filesystem type 'vfat', so apparently > > > > there > > > > is > > > > a missing module in the kernel. > > > > > > Thats a bit weird, vfat.ko is included in the initrd. can you provide > > > the actual output? > > > > > > Thanks, > > > Dirk > > > > Tried Build384.4: same result. > > Tried Build384.5: same result. Lines with red in output of command > "journalctl -C <path-to-journal-on-SD>": > feb 25 01:06:36 rpitest systemd[1]: Failed to start Load Kernel Modules. > feb 25 01:06:36 rpitest systemd-modules-load[5199]: Failed to find module > 'sg' feb 25 01:07:05 rpitest systemd[1]: Failed to mount /boot/efi. > feb 25 01:07:11 rpitest systemd[5327]: emergency.service: Failed at step > EXEC spawning /usr/bin/plymouth: No such file or directory > feb 25 01:07:58 rpitest systemd[1]: Timed out waiting for device sys- > subsystem-net-devices-eth0.device.
Tried Build385.1: same result. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
