Fwd: Kubic Arm64 Raspberry Pi Images
+Mailing list ---------- Forwarded message --------- From: Anthony J Rabbito <hello@anthonyrabbito.com> Date: Thu, Jan 14, 2021 at 8:33 PM Subject: Re: Kubic Arm64 Raspberry Pi Images To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Hello, Just a FYI it appears there's a regression in the latest Raspberry Pi firmware that came through with Micro-OS this week. Today I rebooted two of my nodes and they never came back online. I have tried using start.elf, fixup4.dat, and start4.elf from raspberry/firmware on master as an attempt to fix. For what it's worth I'm booting off SSDs. Tomorrow I'll hook up a screen as it's quite late and it's incredibly inconvenient. I also tried upgrading my eeprom from Sept release to December. Possibly related: https://github.com/raspberrypi/rpi-eeprom/issues/266 I'll post my findings tomorrow. Just giving a heads up to any MicroOS Pi users. Thanks, Anthony On Wed, Dec 16, 2020 at 9:51 AM Nicolas Saenz Julienne < nsaenzjulienne@suse.de> wrote:
On Tue, 2020-12-15 at 09:05 -0500, Anthony J Rabbito wrote:
Hi Nicolas,
I have never tested this board with a UEFI image though worked fine with for example Ubuntu's image. I have a heatsink and enclosure on this Pi so I'd prefer not taking that apart.
/proc/cpuinfo reads
Hardware : BCM2711 Revision : d03114 Serial : 1000000056af08e4 Model : Raspberry Pi 4 Model B Rev 1.4
Let me know if that's not sufficient.
I actually plan to compile edk2 today or tomorrow and see how it goes. Since it makes more sense to pass combustion/ignition via iPXE.
Some more useful information while I'm booted into raspbian.
BCM2711 detected VL805 firmware in bootloader EEPROM BOOTLOADER: up-to-date CURRENT: Tue 24 Nov 15:08:04 UTC 2020 (1606230484) LATEST: Tue 24 Nov 15:08:04 UTC 2020 (1606230484) FW DIR: /lib/firmware/raspberrypi/bootloader/beta VL805: up-to-date CURRENT: 000138a1 LATEST: 000138a1
https://github.com/raspberrypi/firmware/issues/1445#issuecomment-708822669 This issue is exactly what im facing and it looks like those patches have landed in the raspberry Pi firmware but not the
MicroOS images?
For clarity MicroOS boots fine on 4GB models just not 8GBs.
Thanks, I managed to reproduce the issue. It's a bug in rpi's firmware indeed. Sorry but there is no easy solution. I suggest you take the latest version of start4.elf and fixup4.dat from Tumbleweed's package an copy it into your SD card. Otherwise you can wait for MicroOS images to catch-up (I don't really know when will that happen). Sorry for the inconvenience.
@Guillaume I tend to trust RPi firmware but I guess we should be more careful. Specially as it's nice to be able to follow the master branch. I think it'd make sense to hook-up an 8GB RPi into openQA to catch such regressions early. The same goes for RPi400 and CM4. Would you be able to take care of setting things up if I managed to send you the boards?
Regards, Nicolas
On Thu, 2021-01-14 at 20:36 -0500, Anthony J Rabbito wrote:
+Mailing list ---------- Forwarded message --------- From: Anthony J Rabbito <hello@anthonyrabbito.com> Date: Thu, Jan 14, 2021 at 8:33 PM Subject: Re: Kubic Arm64 Raspberry Pi Images To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Hello,
Just a FYI it appears there's a regression in the latest Raspberry Pi firmware that came through with Micro-OS this week. Today I rebooted two of my nodes and they never came back online.
I have tried using start.elf, fixup4.dat, and start4.elf from raspberry/firmware on master as an attempt to fix. For what it's worth I'm booting off SSDs. Tomorrow I'll hook up a screen as it's quite late and it's incredibly inconvenient. I also tried upgrading my eeprom from Sept release to December.
Possibly related: https://github.com/raspberrypi/rpi-eeprom/issues/266
I'll post my findings tomorrow. Just giving a heads up to any MicroOS Pi users.
Thanks, Anthony
Hi Anthony, I appreciate the heads-up, but I would like to confirm that my RPi 3 B+ sitting on my desk has rebooted just fine as usual. So any issues you are having are likely a result of things you're specifically doing with your setup, probably booting from SSDs. Good luck with your investigation :) Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
Hi, On Fri, Jan 15, Richard Brown wrote:
I appreciate the heads-up, but I would like to confirm that my RPi 3 B+ sitting on my desk has rebooted just fine as usual.
Same for me, my RPi 4 did all reboot just fine after the update. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
Hi, Am Freitag, 15. Januar 2021, 02:36:39 CET schrieb Anthony J Rabbito:
+Mailing list ---------- Forwarded message --------- From: Anthony J Rabbito <hello@anthonyrabbito.com> Date: Thu, Jan 14, 2021 at 8:33 PM Subject: Re: Kubic Arm64 Raspberry Pi Images To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Hello,
Just a FYI it appears there's a regression in the latest Raspberry Pi firmware that came through with Micro-OS this week. Today I rebooted two of my nodes and they never came back online.
I have tried using start.elf, fixup4.dat, and start4.elf from raspberry/firmware on master as an attempt to fix. For what it's worth I'm booting off SSDs. Tomorrow I'll hook up a screen as it's quite late and it's incredibly inconvenient. I also tried upgrading my eeprom from Sept release to December.
Possibly related: https://github.com/raspberrypi/rpi-eeprom/issues/266
Might also be https://bugzilla.opensuse.org/show_bug.cgi?id=1180336, but that should only manifest itself in the kernel AFAICT, so u-boot and grub should still work and health-checker would trigger booting into an older snapshot. Apparently you already narrowed it down to https://github.com/raspberrypi/firmware/issues/1445 though, but then it should work with the latest firmware? Cheers, Fabian
I'll post my findings tomorrow. Just giving a heads up to any MicroOS Pi users.
Thanks, Anthony
On Wed, Dec 16, 2020 at 9:51 AM Nicolas Saenz Julienne < nsaenzjulienne@suse.de> wrote:
On Tue, 2020-12-15 at 09:05 -0500, Anthony J Rabbito wrote:
Hi Nicolas,
I have never tested this board with a UEFI image though worked fine with for example Ubuntu's image. I have a heatsink and enclosure on this Pi so I'd prefer not taking that apart.
/proc/cpuinfo reads
Hardware : BCM2711 Revision : d03114 Serial : 1000000056af08e4 Model : Raspberry Pi 4 Model B Rev 1.4
Let me know if that's not sufficient.
I actually plan to compile edk2 today or tomorrow and see how it goes. Since it makes more sense to pass combustion/ignition via iPXE.
Some more useful information while I'm booted into raspbian.
BCM2711 detected VL805 firmware in bootloader EEPROM BOOTLOADER: up-to-date CURRENT: Tue 24 Nov 15:08:04 UTC 2020 (1606230484) LATEST: Tue 24 Nov 15:08:04 UTC 2020 (1606230484) FW DIR: /lib/firmware/raspberrypi/bootloader/beta VL805: up-to-date CURRENT: 000138a1 LATEST: 000138a1
https://github.com/raspberrypi/firmware/issues/1445#issuecomment-708822669 This issue is exactly what im facing and it looks like those patches have landed in the raspberry Pi firmware but not the
MicroOS images?
For clarity MicroOS boots fine on 4GB models just not 8GBs.
Thanks, I managed to reproduce the issue. It's a bug in rpi's firmware indeed. Sorry but there is no easy solution. I suggest you take the latest version of start4.elf and fixup4.dat from Tumbleweed's package an copy it into your SD card. Otherwise you can wait for MicroOS images to catch-up (I don't really know when will that happen). Sorry for the inconvenience.
@Guillaume I tend to trust RPi firmware but I guess we should be more careful. Specially as it's nice to be able to follow the master branch. I think it'd make sense to hook-up an 8GB RPi into openQA to catch such regressions early. The same goes for RPi400 and CM4. Would you be able to take care of setting things up if I managed to send you the boards?
Regards, Nicolas
participants (4)
-
Anthony J Rabbito -
Fabian Vogt -
Richard Brown -
Thorsten Kukuk