I realise this is very much an edge case but I am trying to run a Pi Compute Module 4 Lite through a CM4 - CM3 adapter in place of the CM3 on my USBridge Signature.
The hardware appears to be working fine and Ropieee actually boots up and runs through the first four configuration stages but then fails to find the network interface (just after to warning about making sure the system is connected to the internet). From reading around it seems that the CM4 grabs the eth0 interface which (presumably) is what Ropieee is looking for.
Is there anything I can do to sort this? It appears to be possible because at least one other system does find the network but I’d much prefer to use Ropieee.
Open the config.txt file in your MicroSD card /boot/ folder and add a line: otg_mode=1
If it still cannot find the network, then
You might need to add a noeth.dtbo device tree blob in the /boot/overlays/ folder to disable this CM4 PHY ethernet so that the ASIX Ethernet chip on board the USBridge Sig can be assigned to the eth0. After, that add 2 lines in your config.txt file: otg_mode=1 dtoverlay=noeth
I cannot attach the noeth.dtbo file here so you might need to download it from below post in other forum:
I suspect that this is the point where Spockfish pops up and points out (quite correctly) that the whole point of Ropieee was to be an appliance that you don’t fiddle about with.
I’ll try to go back to the CM3 and find another use for the CM4.
Have you tried the method I mentions above? I have been using that mehod successfully with Silent Angel VitOS for Raspberry Pi4, GentooPlayer64 Raspberry Pi4 image and currently HQPlayer NAA Raspberry Pi4 image. I stopped using Ropieee few years so not really sure if it works.
Have been using Raspberry CM4 on my USBridge Signature for almost 2 years and it works much better than the original CM3.