Hello.
Yes, the boot completed on the Banana Pi M64.
This morning I tried upgrading my Orange Pi Zero Plus to the rc3 U-Boot, and before rebooting I added those options below. It booted successfully:
[ 0.000000] efi: RTPROP=0x58ef8040 SMBIOS 3.0=0x59f3f000 MOKvar=0x58ee1000 MEMRESERVE=0x58ed8040
[ 0.098941] SMBIOS 3.7.0 present.
[ 0.099009] DMI: xunlong Xunlong Orange Pi Zero Plus/Xunlong Orange Pi Zero Plus, BIOS 2024.10-rc3 10/01/2024
Then I reverted the kernel options back to their previous valuse and I haven't been able to get it to boot again.
I think I have to simply consider this device as unreliable.
My Raspberry Pi and my Rock Pi E have always upgraded fine at the first attempt. No more Allwinner devices for me.
BR
-----Original Message-----
From: Peter Robinson <pbrobinson@xxxxxxxxx>
To: Adrian Torregrosa <adrian.torregrosa@xxxxxxxxx>
Subject: Re: [fedora-arm] U-Boot 2024.10 testing
Date: 2024.09.03 19:37:56
On Tue, 3 Sept 2024 at 18:21, Adrian Torregrosa
<adrian.torregrosa@xxxxxxxxx> wrote:
After reverting back to 2023.07 on the Banana Pi M64 I booted and repeated the dd command. Before rebooting I took the time to read back from the MMC and compare its SHA256 checksum with that of the file /usr/share/uboot/bananapi_m64/u-boot-sunxi-with-spl.bin and that that appears in https://koji.fedoraproject.org/koji/fileinfo?rpmID=39921997&filename=/usr/share/uboot/bananapi_m64/u-boot-sunxi-with-spl.bin, and the three matched.Then I rebooted and the boot process completed successfully.
So it completed successfully on the Banana Pi M64?
One difference I observed was that when it failed it showed:
So on a clean system that hasn't booted previously (with the feature)
the OS hasn't updated the EFI entry.
*** U-Boot Boot Menu ***mmc 0whereas when it succeeded it showed*** U-Boot Boot Menu ***Fedorammc 0
That's post boot where the UEFI entry was updated for the OS.
Besides, this error that appears when it failed:error: ../../grub-core/disk/efi/efidisk.c:615:failure reading sector 0x1e6f80 from `hd0'.might be a transient one, I'm not sure about that.
That looks like a problem with an SD card, I wonder if there's a
failed sector or something.
I can't say much more about why the upgrade failed on the Banana Pi the first time while it succeeded the second time. I'll see what I can find with the Orange Pi.
Sometimes adding the following to the kernel command line can give you
a bunch of very early boot debug output which may shed more of a light
as to where the failure is "console=tty0 console=ttyS0,115200 earlycon
uefi_debug earlyprintk=serial,ttyS0,115200 debug"
Peter
BR-----Original Message-----From: Peter Robinson <pbrobinson@xxxxxxxxx>To: Adrian Torregrosa <adrian.torregrosa@xxxxxxxxx>Subject: Re: [fedora-arm] U-Boot 2024.10 testingDate: 2024.09.03 17:08:18On Tue, 3 Sept 2024 at 16:03, Adrian Torregrosa<adrian.torregrosa@xxxxxxxxx> wrote:The grub menu is reached in both cases. Then, the boot fails on the Banana Pi M64 just after a couple of seconds, whereas on the Orange Pi Zero Plus it simply does not complete the boot.Please debug it rather than just going straight out and givingnegative karma because I don't believe U-Boot is the problem here, andit's significantly better than the previous version....BR-----Original Message-----From: Peter Robinson <pbrobinson@xxxxxxxxx>To: Adrian Torregrosa <adrian.torregrosa@xxxxxxxxx>Subject: Re: [fedora-arm] U-Boot 2024.10 testingDate: 2024.09.03 16:49:21On Tue, 3 Sept 2024 at 15:42, Adrian Torregrosa<adrian.torregrosa@xxxxxxxxx> wrote:Hello.I'm afraid the new release did not work for any of my two Allwinner devices. The dd commands went through of course but upon rebooting the devices failed to reach the login; please see the console outputs attached.Those outputs look like I would expect for a working device, I wouldexpect the grub menu to come up shortly after that. What are youseeing?PeterBR-----Original Message-----From: Peter Robinson <pbrobinson@xxxxxxxxx>To: Adrian Torregrosa <adrian.torregrosa@xxxxxxxxx>Subject: Re: [fedora-arm] U-Boot 2024.10 testingDate: 2024.09.02 23:31:09Hi Adrian,I created Bug 2309138 - Allwinner A64 devices fail to boot once their uboot gets upgraded to 2024.04.So I think uboot-tools-2024.10-0.3.rc3.fc41 should fix the Allwinnerissues, if you could test it and provide karma on the update belowthat would be fab. I tested it on my Pine64+I upgraded mi Radxa Rock Pi E with the UBoot in the rc2 .rpm and as far as I can tell it works fine:U-Boot TPL 2024.10-rc2 (Aug 15 2024 - 00:00:00)DDR3, 333MHzBW=32 Col=10 Bk=8 CS0 Row=14 CS=1 Die BW=16 Size=512MBTrying to boot from BOOTROMReturning to boot ROM...U-Boot SPL 2024.10-rc2 (Aug 15 2024 - 00:00:00 +0000)Trying to boot from MMC2## Checking hash(es) for config config-1 ... OK## Checking hash(es) for Image atf-1 ... sha256+ OK## Checking hash(es) for Image u-boot ... sha256+ OK## Checking hash(es) for Image fdt-1 ... sha256+ OK## Checking hash(es) for Image atf-2 ... sha256+ OK## Checking hash(es) for Image atf-3 ... sha256+ OKNOTICE: BL31: v2.10.4(release):NOTICE: BL31: Built : 00:00:00, Jul 17 2024NOTICE: BL31:Rockchip release version: v1.2U-Boot 2024.10-rc2 (Aug 15 2024 - 00:00:00 +0000)Model: Radxa ROCK Pi EDRAM: 512 MiB (effective 510 MiB)PMIC: RK805 (on=0x40, off=0x01)Core: 244 devices, 29 uclasses, devicetree: separateMMC: mmc@ff500000: 1, mmc@ff520000: 0Loading Environment from MMC... Reading from MMC(1)... *** Warning - bad CRC, using default environmentIn: serial@ff130000Out: serial@ff130000Err: serial@ff130000Model: Radxa ROCK Pi ENet: eth0: ethernet@ff540000Found DTB: rockchip/rk3328-rock-pi-e.dtbCard did not respond to voltage select! : -110*** U-Boot Boot Menu ***Fedorammc 1ExitPress UP/DOWN to move, ENTER to select, ESC to quitBooting: FedoraFound DTB: rockchip/rk3328-rock-pi-e.dtbethernet@ff540000 Waiting for PHY auto negotiation to complete....... doneSpeed: 1000, full duplex...Best regards.-----Original Message-----From: Peter Robinson <pbrobinson@xxxxxxxxx>To: Adrian Torregrosa <adrian.torregrosa@xxxxxxxxx>Subject: Re: [fedora-arm] U-Boot 2024.10 testingDate: 2024.09.01 19:43:27Hi Adrian,A couple of weeks ago I upgraded my Orange Pi Zero Plus and my Sinovoip Banana Pi M64, both of which are based on Allwinner 64, from F39 to F40. That went fine so after that I attempted upgrading their UBoots and that did not work:I think I've got to the bottom of the issue, any chance you can do aF-41 bug report for me? Link below should go straight there for you.So I reverted back to U-Boot SPL 2023.07.This afternoon I tried upgrading the Banana Pi to this rc2 version and the result was quite similar:Yup, it's the same.For the record, I was able to upgrade my Raspberry Pi 3B's and my Radxa Rock Pi E's UBoots to 2024.04.What about to the 2024.10 RC builds in F-41? You can use the F-41U-Boot without having to upgrade the OS. Mostly interested in theRockPi as I can test the RPi3.Thanks,PeterBest regards.-----Original Message-----From: Peter Robinson <pbrobinson@xxxxxxxxx>Subject: [fedora-arm] U-Boot 2024.10 testingDate: 2024.08.16 12:45:29Hi Folks,I've started building the 2024.10 RCs in F-41+ so it would be great toget some testing.I found that at least the Allwinner a64 devices looked like theyregressed in F-40 and I've tested the Pine64+ with the rc2 build and Ithink they should be OK now.It would be great if people could test and provide some feedback onthese builds as we go towards F-41 beta freeze.Peter
-- _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
