Port-arm archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Orange Pi 5 weirdness
Hey,
I'm getting nearly the same results on another board running the EDK2
for the same chip. It is a FriendElec NanoPi R6C. I don't have it at
hand to copy the exact output.
I'm having both the network, and the SD issue, but other than that X,
and the SD card work well. I ended up placing an old, small in
capacity SD card with the EDK2 and basic EFI to boot to NVME, but
-did- have a time where it did that straight from the NVME once I
booted from another device, then flashed what I had onto the SD onto
the NVME... once EDK2 is on the NVME I was booting off of it fine.
==
>> Hi!
>>
>> I have NetBSD-current on the Orange Pi 5 *almost* working. Display and NVME are doing fine. However, there are a few showstoppers:
>>
>> 1. I boot from an SD card that has EDK2 for Orange Pi (version 0.9.1, from late 2023) and a NetBSD installation. The bootloader loads the kernel from the root partition but the booted kernel does not see the SD card at all. However, I can boot by passing root=NAME=nbroot (the name of the root partition on the SSD). (The kernel is a 10.99.11 from yesterday.)
>>
>> The built-in ethernet sees no medium, even when a cable is connected. During boot, it says
>>
>> eqos0 at acpi0 (MAC1, PRP0001-61): mem 0xfe1c0000-0xfe1cffff irq 266,265
>> eqos0: DesignWare EQOS ver 0x51 (0x30)
>> eqos0: hw features 1a1173f7 111e01e8 11041041 0c370031
>> eqos0: using 32-bit DMA
>>
>> eqos0: autoconfiguration error: Wrong MAC address. Clear the multicast bit.
>>
>> eqos0: Ethernet address c4:ab:14:c6:33:37
>>
>> There are two ukphy devices attaching to the eqos0.
>>
>> Any ideas? Should I use a newer EDK2? Can this board boot from NVME directly?
Home |
Main Index |
Thread Index |
Old Index