----- Original Message -----
On 3/7/19 5:48 PM, Paul Whalen wrote:
> Hi Robert,
>
> ----- Original Message -----
>> I just tested with Fedora-Minimal-armhfp-30-20190307.n.0-sda
>>
>> On a Cubieboard2:
>>
>> I installed the image on a 4GB uSD card and deleted all partitions.
>> I installed the image on a 240GB SSD drive and enlarged the rootfs
>> partition to about 6GB.
>>
>> I installed the cards on a Cubieboard2, attached the console and
>> booted. The boot failed. This process has been working for years, so
>> something serious has been broken in the uboot.
> Thanks for testing and reporting the issue. It seems to affect the
> allwinner
> boards (Cubietruck, Banana Pi etc).
I figured it would effect all Allwinner boards.
> Not fixed in uboot-tools-2019.04-0.4.rc3.fc30. You can use the F29
> builds to continue testing until we can get a fix in F30.
Have you tested with something after 2018-09 rc3? I am assuming that
the current F29 is later than this...
Yes, uboot-tools-2018.09-2.fc29 is the latest in F29 and working on
the Cubietruck and Banana Pi.
Paul
> >
> >
> >> U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000)
> >> DRAM: 1024 MiB
> >> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> >> Trying to boot from MMC1
> >>
> >>
> >> U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology
> >>
> >> CPU: Allwinner A20 (SUN7I)
> >> Model: Cubietech Cubieboard2
> >> I2C: ready
> >> DRAM: 1 GiB
> >> MMC: mmc@1c0f000: 0
> >> Loading Environment from FAT... ** No valid partitions found **
> >> In: serial
> >> Out: serial
> >> Err: serial
> >> SCSI: Target spinup took 0 ms.
> >> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> >> flags: ncq stag pm led clo only pmp pio slum part ccc apst
> >>
> >> Net: sunxi_set_gate: (CLK#66) unhandled
> >> eth0: ethernet@1c50000
> >> starting USB...
> >> USB0: USB EHCI 1.00
> >> USB1: USB OHCI 1.0
> >> USB2: USB EHCI 1.00
> >> USB3: USB OHCI 1.0
> >> scanning bus 0 for devices... 1 USB Device(s) found
> >> scanning bus 1 for devices... 1 USB Device(s) found
> >> scanning bus 2 for devices... 1 USB Device(s) found
> >> scanning bus 3 for devices... 1 USB Device(s) found
> >> scanning usb for storage devices... 0 Storage Device(s) found
> >> Hit any key to stop autoboot: 0
> >> switch to partitions #0, OK
> >> mmc0 is current device
> >> ** Invalid partition 1 **
> >> scanning bus for devices...
> >> data abort
> >> pc : [<7ef86b0e>] lr : [<7ef82d89>]
> >> reloc pc : [<4a01ab0e>] lr : [<4a016d89>]
> >> sp : 7af43ad0 ip : 0000001c fp : 000000c0
> >> r10: 00000000 r9 : 7af4bed8 r8 : 00000000
> >> r7 : 7af43d50 r6 : 7efc4894 r5 : 7efcc2f8 r4 : 7efcc2f8
> >> r3 : 00000000 r2 : 00000000 r1 : ea000016 r0 : 7efcc2f8
> >> Flags: nZcv IRQs off FIQs off Mode SVC_32
> >> Code: e92dbd10 f8d045f0 b0858080 1000f8d8 (f8d14604)
> >> Resetting CPU ...
> >>
> >> resetting ...
> >>
> >> U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000)
> >> DRAM: 1024 MiB
> >> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> >> Trying to boot from MMC1
> >>
> >>
> >> U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology
> >>
> >> CPU: Allwinner A20 (SUN7I)
> >> Model: Cubietech Cubieboard2
> >> I2C: ready
> >> DRAM: 1 GiB
> >> MMC: mmc@1c0f000: 0
> >> Loading Environment from FAT... ** No valid partitions found **
> >> In: serial
> >> Out: serial
> >> Err: serial
> >>
> >> and so forth.
> >>
> >> On 3/3/19 5:45 PM, Peter Robinson wrote:
> >>> On Sun, Mar 3, 2019 at 10:18 PM Robert Moskowitz
<rgm(a)htt-consult.com>
> >>> wrote:
> >>>> The environment is only the uboot on the uSD and all partitions on
the
> >>>> sata HD.
> >>>>
> >>>> I have been doing this for years now with no problem. uboot has
always
> >>>> switched to looking for the sata hd for partitions if no partitions
on
> >>>> the uSD:
> >>>>
> >>>> U-Boot SPL 2018.09-rc3 (Sep 05 2018 - 19:12:48 +0000)
> >>>> DRAM: 1024 MiB
> >>>> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> >>>> Trying to boot from MMC1
> >>>>
> >>>>
> >>>> U-Boot 2018.09-rc3 (Sep 05 2018 - 19:12:48 +0000) Allwinner
Technology
> >>>>
> >>>> CPU: Allwinner A20 (SUN7I)
> >>>> Model: Cubietech Cubieboard2
> >>>> I2C: ready
> >>>> DRAM: 1 GiB
> >>>> MMC: SUNXI SD/MMC: 0
> >>>> Loading Environment from FAT... ** No valid partitions found **
> >>>> In: serial
> >>>> Out: serial
> >>>> Err: serial
> >>>> SCSI: Target spinup took 0 ms.
> >>>> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> >>>> flags: ncq stag pm led clo only pmp pio slum part ccc apst
> >>>>
> >>>> Net: eth0: ethernet@01c50000
> >>>> starting USB...
> >>>> USB0: USB EHCI 1.00
> >>>> USB1: USB OHCI 1.0
> >>>> USB2: USB EHCI 1.00
> >>>> USB3: USB OHCI 1.0
> >>>> scanning bus 0 for devices... 1 USB Device(s) found
> >>>> scanning bus 2 for devices... 1 USB Device(s) found
> >>>> scanning usb for storage devices... 0 Storage Device(s)
found
> >>>> Hit any key to stop autoboot: 0
> >>>> switch to partitions #0, OK
> >>>> mmc0 is current device
> >>>> ** Invalid partition 1 **
> >>>> scanning bus for devices...
> >>>> Device 0: (0:0) Vendor: ATA Prod.: WDC WD800BEVS-75 Rev: 04.0
> >>>> Type: Hard Disk
> >>>> Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
> >>>> Found 1 device(s).
> >>>>
> >>>> Device 0: (0:0) Vendor: ATA Prod.: WDC WD800BEVS-75 Rev: 04.0
> >>>> Type: Hard Disk
> >>>> Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
> >>>> ... is now current device
> >>>> Scanning scsi 0:2...
> >>>> Found /extlinux/extlinux.conf
> >>>> Retrieving file: /extlinux/extlinux.conf
> >>>> 567 bytes read in 33 ms (16.6 KiB/s)
> >>>> Ignoring unknown command: ui
> >>>> Ignoring malformed menu command: autoboot
> >>>> Ignoring malformed menu command: hidden
> >>>> Ignoring unknown command: totaltimeout
> >>>> CentOS-Userland-7-armv7hl-generic-Minimal-1810 Boot Options.
> >>>> 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810
> >>>> (4.14.82-201.el7.armv7hl)
> >>>>
> >>>> Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810
> >>>> (4.14.82-
> >>>> 201.el7.armv7hl)
> >>>> Retrieving file: /initramfs-4.14.82-201.el7.armv7hl.img
> >>>>
> >>>> Yes, this particular event is with the current Centos arm image,
but
> >>>> that should not matter. I have to get this Centos image built and
> >>>> installed before I can test with Fedora arm image....
> >>>>
> >>>> I grabbed a more recent uboot via:
> >>>>
> >>>> Fedora-Minimal-armhfp-30-20190301.n.0-sda
> >>>>
> >>>> When I try booting with the uboot in that image I get:
> >>>>
> >>>> U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000)
> >>>> DRAM: 1024 MiB
> >>>> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> >>>> Trying to boot from MMC1
> >>>>
> >>>>
> >>>> U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner
Technology
> >>>>
> >>>> CPU: Allwinner A20 (SUN7I)
> >>>> Model: Cubietech Cubieboard2
> >>>> I2C: ready
> >>>> DRAM: 1 GiB
> >>>> MMC: mmc@1c0f000: 0
> >>>> Loading Environment from FAT... ** No valid partitions found **
> >>>> In: serial
> >>>> Out: serial
> >>>> Err: serial
> >>>> SCSI: Target spinup took 0 ms.
> >>>> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> >>>> flags: ncq stag pm led clo only pmp pio slum part ccc apst
> >>>>
> >>>> Net: sunxi_set_gate: (CLK#66) unhandled
> >>>> eth0: ethernet@1c50000
> >>>> starting USB...
> >>>> USB0: USB EHCI 1.00
> >>>> USB1: USB OHCI 1.0
> >>>> USB2: USB EHCI 1.00
> >>>> USB3: USB OHCI 1.0
> >>>> scanning bus 0 for devices... 1 USB Device(s) found
> >>>> scanning bus 1 for devices... 1 USB Device(s) found
> >>>> scanning bus 2 for devices... 1 USB Device(s) found
> >>>> scanning bus 3 for devices... 1 USB Device(s) found
> >>>> scanning usb for storage devices... 0 Storage Device(s)
found
> >>>> Hit any key to stop autoboot: 0
> >>>> switch to partitions #0, OK
> >>>> mmc0 is current device
> >>>> ** Invalid partition 1 **
> >>>> scanning bus for devices...
> >>>> data abort
> >>>> pc : [<7ef86b0e>] lr : [<7ef82d89>]
> >>>> reloc pc : [<4a01ab0e>] lr : [<4a016d89>]
> >>>> sp : 7af43ad0 ip : 0000001c fp : 000000c0
> >>>> r10: 00000000 r9 : 7af4bed8 r8 : 00000000
> >>>> r7 : 7af43d50 r6 : 7efc4894 r5 : 7efcc2f8 r4 : 7efcc2f8
> >>>> r3 : 00000000 r2 : 00000000 r1 : ea000016 r0 : 7efcc2f8
> >>>> Flags: nZcv IRQs off FIQs off Mode SVC_32
> >>>> Code: e92dbd10 f8d045f0 b0858080 1000f8d8 (f8d14604)
> >>>> Resetting CPU ...
> >>>>
> >>>> resetting ...
> >>>>
> >>>> U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000)
> >>>> DRAM: 1024 MiB
> >>>> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> >>>> Trying to boot from MMC1
> >>>>
> >>>>
> >>>> U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner
Technology
> >>>>
> >>>> CPU: Allwinner A20 (SUN7I)
> >>>> Model: Cubietech Cubieboard2
> >>>> I2C: ready
> >>>> DRAM: 1 GiB
> >>>> MMC: mmc@1c0f000: 0
> >>>> Loading Environment from FAT... ** No valid partitions found **
> >>>> In: serial
> >>>> Out: serial
> >>>> Err: serial
> >>>>
> >>>> and so forth....
> >>>>
> >>>> If there is a rc3 available, please tell me what image to grab for
it
> >>>> and I can test with that.
> >>> There should be a rc3 this week.
> >>>
> >> _______________________________________________
> >> arm mailing list -- arm(a)lists.fedoraproject.org
> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> >> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> >> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> >>
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> >>
>
>