On 12/5/18 5:47 PM, Stewart Samuels wrote:
BTW, another issue I found, and I don't know if it has been fixed
or
not because my script does this automatically, is that with my odroid,
I begin my boot partition on disk block 3072 rather than the default
Fedorad disk block of 2048. The reason for this is that I found that
if I use the default 2048, flashing the u-boot information to the sd
or emmc cards would then corrupt the boot partition such that you can
get errors such as you are seeing now..."No block device". I have
never seen these problems since I started my partions from block 3072.
The "No block device" is the expected behavior. uboot cannot find a
partition on the uSD and then starts searching elsewhere.
I have never had a problem with the supplied images install as
provided. But then this is my 2nd non-cubieboard attempt and the other
(Linksprite_pcDuino3_Nano) which is also an Allwinner SOC.
And I have been using the install script since Paul provided it. In
fact I was STILL using his old one to my chagrin!
Stewart
On 12/5/18 2:40 PM, Robert Moskowitz wrote:
>
>
> On 12/5/18 5:15 PM, Peter Robinson wrote:
>>>>> U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1
>>>>>
>>>>> CPU: Exynos5422 @ 800 MHz
>>>>> Model: Odroid XU3 based on EXYNOS5422
>>>>> Board: Odroid XU3 based on EXYNOS5422
>>>>> Type: hc1
>>>>> DRAM: 2 GiB
>>>>> MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2
>>>>> Loading Environment from MMC... Card did not respond to voltage
>>>>> select!
>>>>> *** Warning - No block device, using default environment
>>>>>
>>>>> In: serial
>>>>> Out: serial
>>>>> Err: serial
>>>>> Net: No ethernet found.
>>>>> Hit any key to stop autoboot: 0
>>>>> MMC Device 1 not found
>>>>> no mmc device at slot 1
>>>>> Card did not respond to voltage select!
>>>>> switch to partitions #0, OK
>>>>> mmc2 is current device
>>>>> ** Invalid partition 1 **
>>>>> starting USB...
>>>>> USB0: USB EHCI 1.00
>>>>> USB1: Register 2000140 NbrPorts 2
>>>>> Starting the controller
>>>>> USB XHCI 1.00
>>>>> USB2: Register 2000140 NbrPorts 2
>>>>> Starting the controller
>>>>> USB XHCI 1.00
>>>>> scanning bus 0 for devices... 1 USB Device(s) found
>>>>> scanning bus 1 for devices... cannot reset port 1!?
>>>>> 2 USB Device(s) found
>>>>> scanning bus 2 for devices... 2 USB Device(s) found
>>>>> scanning usb for storage devices... 1 Storage Device(s)
>>>>> found
>>>>> scanning usb for ethernet devices... 1 Ethernet
>>>>> Device(s) found
>>>>> Waiting for Ethernet connection... done.
>>>>> BOOTP broadcast 1
>>>>> BOOTP broadcast 2
>>>>> DHCP client bound to address 192.168.192.15 (5004 ms)
>>>>> *** ERROR: `serverip' not set
>>>>>
>>>>> ==================================
>>>>>
>>>>> Setup was a 4GB uSD that only had the hardkernel bootloader and
>>>>> uboot.
>>>>> No partitions.
>>>> Well that bit seems to be working from the details above.
>>>>
>>>>> sata drive (SSD) had the image (all partitions) installed. Including
>>>>> changes to extlinux.conf
>>>> It finds the USB storage in the output above.
>>>>
>>>> Why do you need to change the extlinux.conf? It should just work no
>>>> matter what the storage. What changes did you make?
>>> Per
>>>
https://blog.christophersmart.com/2018/04/28/fedora-on-odroid-hc1-mini-na...
>>>
>>>
>>> "First things first, we need to enable the serial console, turn off
>>> cpuidle else it won’t boot, and fix a bug where USB doesn’t load in
>>> the
>>> right order. We do this by mounting the boot partition on the SD card
>>> and modifying the extlinux bootloader configuration."
>>>
>>> sed -i "s|append|& cpuidle.off=1 \
>>> console=tty1 console=ttySAC2,115200n8 \
>>> rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher|" \
>>> /run/media/rgm/__boot/extlinux/extlinux.conf
>>>
>>> But I don't see above where it is even getting to the boot
>>> partition on
>>> the sata drive. But you understand this much better than I, so all
>>> help
>>> appreciated!
>> So if you interrupt the boot process can you use the U-Boot ls command
>> to see if it can see the contents of the first partition on the disk?
>>
> How do I interrupt boot process at the right point (I assume at the
> bootp point)?
>
> thanks
> _______________________________________________
> 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
_______________________________________________
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