Op woensdag 11 september 2019 16:36:53 CEST schreef Guillaume Gardet: > > -----Original Message----- > > From: Michael Ströder <[email protected]> > > Sent: 11 September 2019 16:17 > > To: Guillaume Gardet <[email protected]>; openSUSE ARM ML > > <[email protected]> > > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > > > > > > > On 9/11/19 3:53 PM, Guillaume Gardet wrote: > > > > >> From: Michael Ströder <[email protected]> > > >> Sent: 11 September 2019 13:55 > > >> > > >> > > >> > > >> On 9/11/19 1:47 PM, Guillaume Gardet wrote: > > >> > > >>>> -----Original Message----- > > >>>> From: Michael Ströder <[email protected]> > > >>>> Sent: 11 September 2019 13:34 > > >>>> > > >>>> > > >>>> > > >>>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after last > > >>>> upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were > > >>>> no error messages. > > >>> > > >>> > > >>> > > >>> Did you update the kernel only, or the whole distribution (maybe > > >>> including > > >> > > >> firmware)? > > >> > > >> > > >> > > >> I did the usual full upgrade with > > >> zypper dup -l --no-allow-vendor-change --no-recommends > > > > > > > > > > > > Did you run out of space, maybe? > > > > > > > > No. There's plenty of space on the partitions: > > - The firmware partition still has 15MB available and 1.5M used. > > - On the OS partition (where's /boot) 4.9GB are still available. > > > > > > > > > If the rainbow screen is not display, this means that the firmware is > > > not > > > > loaded/started properly. > > > > > IIRC, there was a firmware update with latest snapshot. > > > > > > > > Can I check whether the firmware files are complete? > > > I read again your 1st email and it seems that you are missing the firmware > files on the 1st partition of your SD card. My list: > total 6340 > drwxr-xr-x 3 root root 2048 Sep 8 21:15 EFI > -rwxr-xr-x 1 root root 28432 Sep 7 13:21 bcm2708-rpi-b-plus.dtb > -rwxr-xr-x 1 root root 28173 Sep 7 13:21 bcm2708-rpi-b.dtb > -rwxr-xr-x 1 root root 27950 Sep 7 13:21 bcm2708-rpi-cm.dtb > -rwxr-xr-x 1 root root 28634 Sep 7 13:21 bcm2708-rpi-zero-w.dtb > -rwxr-xr-x 1 root root 27898 Sep 7 13:21 bcm2708-rpi-zero.dtb > -rwxr-xr-x 1 root root 29520 Sep 7 13:21 bcm2709-rpi-2-b.dtb > -rwxr-xr-x 1 root root 31325 Sep 7 13:21 bcm2710-rpi-3-b-plus.dtb > -rwxr-xr-x 1 root root 30706 Sep 7 13:21 bcm2710-rpi-3-b.dtb > -rwxr-xr-x 1 root root 29504 Sep 7 13:21 bcm2710-rpi-cm3.dtb > -rwxr-xr-x 1 root root 44472 Sep 7 13:21 bcm2711-rpi-4-b.dtb > -rwxr-xr-x 1 root root 52296 Sep 4 12:07 bootcode.bin > -rwxr-xr-x 1 root root 1476 Nov 30 2018 config.txt > -rwxr-xr-x 1 root root 6736 Sep 4 12:07 fixup.dat > -rwxr-xr-x 1 root root 6092 Sep 4 12:07 fixup4.dat > drwxr-xr-x 2 root root 16384 Sep 8 21:01 overlays > -rwxr-xr-x 1 root root 2877892 Sep 4 12:07 start.elf > -rwxr-xr-x 1 root root 2762820 Sep 4 12:07 start4.elf > -rwxr-xr-x 1 root root 8 Sep 8 21:16 startup.nsh > -rwxr-xr-x 1 root root 443036 Jul 18 12:21 u-boot.bin > > You can get them from the raspberrypi-firmware package: > http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/noarch/raspb > errypi-firmware-2019.09.04-1.1.noarch.rpm You can use ark or 7zip (any > other archive extractor) to extract the files from this RPM. > I tried the latest JeOS-raspberrypi image for RPi1 from > http://download.opensuse.org/ports/armv6hl/tumbleweed/images/openSUSE-Tumbl > eweed-ARM-JeOS-raspberrypi.armv6l-2019.09.04-Snapshot20190907.raw.xz and I > have no problem. > Cheers, > Guillaume
I did have the same problem as Michael. After a "zypper dup --no-r" the system did not boot anymore. I used the serial connection with the RPi1 and there was no output at all. So I did check the content of the first partition on the SD. It did lack the 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm On my desktop I unpacked these files and put them on the first partition. After that the system boots again. The question is: why were these files removed in the upgrade? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
