Re: error loading rp1_eth - Re: Need testers for ALPHA RPi-5 fan control, GE NIC, WiFi drivers for FreeBSD-CURRENT

Mark Millard <[email protected]> Thu, 4 Jun 2026 17:15:54 -0700
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On 6/4/26 15:05, Jeremy McMillan wrote:
> I am booting via this UEFI
> https://github.com/NumberOneGit/rpi5-uefi/releases
> 
> Then I configured it to provide both ACPI+Devicetree
> 
> You will also need to be running a kernel with FDT support. The ofwdump
> utility is just dumping the FDT data. It's basically a map of all the
> hardware IO addressing. The RP1 chip that the Ethernet NIC is connected
> to doesn't provide the IO ports to ACPI, so DeviceTree is an alternative
> for the driver to find them.

I'll note that if the draft/partial EDK2 UEFI/ACPI for the D0 RPi5's
ever is updated to support the RP1 Ethernet NIC and expose it via ACPI,
that future update could lead to both attempted uses to be active at once.

I've no clue if that would ever happen. Similar points could apply to
other things that the EDK2 UEFI/ACPI has not, so far, attempted to handle.


Various folks have the older C1 stepping (original) vintage RPi5,
associated with what the D0 effort started from:

https://github.com/worproject/rpi5-uefi/releases

Are you intending on supporting both type of RPi5 contexts, so both
EDK2's? Even if not, you might want to let folks know one way vs. the other.

Note: As I remember, the RPi* folks firmware related files in the
msdosfs for the C1 RPi5's needs to be updated to be more recent than the
what is in the EDK2 releases.

> 
> 
> 
> -------- Original Message --------
> On Tuesday, 06/02/26 at 11:17 Ronald Klop <[email protected]> wrote:
> 
> 
>     *Van:* void <[email protected]>
>     *Datum:* dinsdag, 2 juni 2026 15:41
>     *Aan:* [email protected]
>     *Onderwerp:* Re: error loading rp1_eth - Re: Need testers for ALPHA
>     RPi-5 fan control, GE NIC, WiFi drivers for FreeBSD-CURRENT
> 
>         On Tue, Jun 02, 2026 at 03:22:12PM +0200, Ronald Klop wrote:
>         >
>         >I get this error loading the ethernet module:
>         >
>         ># kldload rp1_eth
>         >kldload: an error occurred while loading module rp1_eth. Please
>         check dmesg(8) for more details.
>         >
>         >dmesg shows:
>         >rp1_eth: root compatible does not match Pi 5 (raspberrypi,5-
>         model-b or raspberrypi,5-compute-module) — refusing attach
>         >module_register_init: MOD_LOAD (rp1_eth, 0xffff00012110d82c, 0)
>         error 6
> 
>         Hmm. My instance loads
> 
>         13    1 0xffff00011ed17000    2a000 rp1_eth.ko
> 
>         It was loaded like this:
> 
>         doas make load
> 
>         I used https://github.com/aphor/FreeBSD15-RPi5-modules.git
>         <https://github.com/aphor/FreeBSD15-RPi5-modules.git>
> 
>         OS is 16.0-CURRENT #0 n286096-490c53e9353f GENERIC-NODEBUG
> 
>         what does 'make status' show from where you compiled/installed it?
> 
>         here it says:
> 
>         $ make status
>         === Module Status ===
>         BCM2712 Common Hardware:
>             bcm2712 is loaded
>         RPi5 Board Support:
>             rpi5 is loaded
>         RP1 Ethernet (Milestone 1):
>             rp1_eth is loaded
> 
>         === sysctl Interface ===
>             hw.rpi5 sysctl available
>              hw.rpi5.fan.current_state: 2
>              hw.rpi5.fan.cpu_temp: 62800
>             hw.rp1_eth sysctl available
>              hw.rp1_eth.cfg.status_decoded: raw=0x00000000 link=DOWN
>         speed=10M duplex=half
> 
>         -- 
>          
>         ------------------------------------------------------------------------
> 
> 
>     I think this is an indication of what is wrong.
> 
>     # ofwdump -a
>     ofwdump: ioctl(..., OFIOCGETPROPLEN, ...) failed: Invalid argument
>     Node 0
> 
>     But I don't know why this happens.
> 
>     Regards,
>     Ronald.
>      


-- 
===
Mark Millard
marklmi at yahoo.com