[opensuse-arm] Newest image for Raspberry Pi 1 looks promising
Finished testing the newest image
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build377.2.raw.xz
from
http://download.opensuse.org/ports/armv6hl/tumbleweed/images/
for Raspberry Pi 1B
This image is much smaller than its predecessor: 160 MiB versus 230 MiB.
I test it with a HDMI device connected, so I can see the messages.
First it shows the u-boot messages, shows for a short while Tux and shows a
black screen for quite a while. Apparently during this time the SD card is
changed to have a swap partition at the end and the ROOT partition is enlarged
to cover the remaining space on the SD card.
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.
After power down and up it does not boot anymore but it looks the system is
trying to boot via the network.
One of the last messages is that one should run "journalct -xb" to see what
went wrong. I mounted the SD card, or rather the ROOT partition, on my desktop
and started the command "journalctl -D
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 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zaterdag 27 februari 2016 12:16:27 schreef Freek de Kruijf:
Tried Build385.1: same error result.
Tried JeOS Build388.1 from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/ works OK. We finally have a working Tumbleweed image for the Raspberry Pi 1. Many thanks!!!! -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 1. März 2016, 12:25:59 CET schrieb Freek de Kruijf:
[...]
Tried JeOS Build388.1 from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/
works OK. We finally have a working Tumbleweed image for the Raspberry Pi 1.
I tried Build 388.2 and it does not work for me. And I tried Build 388.1 from devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/ and it doesn't work either. minicom shows the following:
U-Boot 2016.03-rc2 (Feb 26 2016 - 21:24:17 +0000)
DRAM: 384 MiB RPI Model B rev2 (0xf) MMC: bcm2835_sdhci: 0 reading uboot.env
** Unable to read "uboot.env" from mmc0:1 ** Using default environment
In: serial Out: lcd Err: lcd Net: Net Initialization Skipped No ethernet found. starting USB... USB0: Core Release: 2.80a scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: 0 U-Boot>
Herbert -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 1. März 2016, 12:25:59 CET schrieb Freek de Kruijf:
[...]
Tried JeOS Build388.1 from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/
works OK. We finally have a working Tumbleweed image for the Raspberry Pi 1.
I tried Build 388.2 and it does not work for me. And I tried Build 388.1 from devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/ and it doesn't work either. minicom shows the following:
U-Boot 2016.03-rc2 (Feb 26 2016 - 21:24:17 +0000)
DRAM: 384 MiB RPI Model B rev2 (0xf) MMC: bcm2835_sdhci: 0 reading uboot.env
** Unable to read "uboot.env" from mmc0:1 ** Using default environment
In: serial Out: lcd Err: lcd Net: Net Initialization Skipped No ethernet found. starting USB... USB0: Core Release: 2.80a scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: 0 U-Boot>
Herbert
On 03/02/2016 11:30 PM, Herbert Graeber wrote:
Am Dienstag, 1. März 2016, 12:25:59 CET schrieb Freek de Kruijf:
[...]
Tried JeOS Build388.1 from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/
works OK. We finally have a working Tumbleweed image for the Raspberry Pi 1. I tried Build 388.2 and it does not work for me. And I tried Build 388.1 from devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/ and it doesn't work either.
minicom shows the following:
U-Boot 2016.03-rc2 (Feb 26 2016 - 21:24:17 +0000)
DRAM: 384 MiB RPI Model B rev2 (0xf) MMC: bcm2835_sdhci: 0 reading uboot.env
** Unable to read "uboot.env" from mmc0:1 ** Using default environment
In: serial Out: lcd Err: lcd Net: Net Initialization Skipped No ethernet found. starting USB... USB0: Core Release: 2.80a scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: 0 U-Boot>
Looks like U-Boot detected input. Maybe the serial cable is loose? Try to type "boot" and press enter here. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Alexander Graf -
Dirk Müller -
Freek de Kruijf -
Herbert Graeber -
Herbert Graeber