-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NetBSD 10-Stable RaspberryPi 4 and UEFI v.1.39 not working ok #267
Comments
Hello, I used an OCR app in my phone to convert the screen captures that I [1/4] SDL2-2.30.7nb1.tgz Kernel debbuger was alive but sorry, I was not able to issue useful [ 283.8386735] Regards. |
Hello
I have been using successfuly my RPi4 for months with UEFI firmware
v1.37 from https://github.com/pftf/RPi4. It is solid rock. I have
updated to NetBSD-10 Stable from source twice, one around october and
one time more at the end of november by using binary sysupgrade path
and appeared to be working fine.
netbsd-raspa4$ uname -a
NetBSD netbsd-raspa4 10.0_STABLE NetBSD 10.0_STABLE (GENERIC64) #0:
Thu Nov 28 16:37:05 UTC 2024
mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/evbarm/compile/GENERIC64
evbarm
I have just upgraded UEFI firmware to v1.39 by uncompressing it over
/boot and NetBSD does not work well with it. First time I booted into
the system it appeared to work but when I issued "reboot" kernel
paniced. I rebooted again and wanted to do a pkgin update and pkgin
upgrade and in the middle of firefox upgrading it paniced again. It
definitely does not work ok.
So I came back to UEFI v1.37 and it appears to be working fine again.
Also have noted some strange things that occured not frequently before
I did any firmware upgrade, also when using NetBSD-10.0 RELEASE.
Sometimes after the reboot command the RPI4 did not come to life. I
had to manually remove the power supply twice because it continued to
be stuck and never saw the raspberry image boot screen that usually
comes before the NetBSD loader comes.
Regards.
Ramiro.
The text was updated successfully, but these errors were encountered: