I have updated to (from 3.19) to 3.20 on my X5000 but I get an "Device or unit failed to open" error and the network is down.

You can see the error here:

https://www.dropbox.com/scl/fi/rolnrjlcfkf9wu5u9nk3c/Network-error.jpeg?rlkey=rzi1m2zymykr4h2rf5ekfw4it&dl=0

I use DHCP and have never had any issues before. My - very straight forward - network settings are:

https://www.dropbox.com/scl/fi/7jne1n88239bd4sw4s8ab/Network-settings.jpeg?rlkey=nhcjtmrpjmp4pcfarjbtsyj26&dl=0

I have checked and it is not the cable There is also a green light on the ethernet port on the back so there is signal to it. I just will not open.

Any suggestions?


[ Edited by JohnFante 16.06.2026 - 17:51 ]

Had similar issue but it went away when I set the static IP.

Setting it to static IP gets rid of the error but still no connection in my end.

Maybe a buggy driver. Or?

Driver on its own is not buggy - qoriq_eth.device works very well on my Mirari.
There should be some isuue connected to X5000.

In Release notes there are:
Quote:
Try to check if you have right driver selected in settings.

[ Edited by sailor 17.06.2026 - 18:12 ]

There is some gateway checkmark in the ethernet settings somewhere. Give that a try.

Simply can not get it to work!

I have tried setting the IP as static with the settings attached. Dobbeltchecking my router. And switching back and forth between DHCP and static with reboots in between.

Settings like this: https://www.dropbox.com/scl/fi/7n1aohhjesrtr2vx37ucp/StaticIP.jpeg?rlkey=8lxfz34czolsllfxqdlorwsvk&dl=0

@sailor: The right driver is chosen - as far as I can see.

@skateman: There is a "gateway" setting on a second advanced page. Changes nothing.

I was thinking of going back to the old driver from 3.19. Does that still work on 3.20?

Adding edebugflags=init to your boot parameters and capturing a log may help.
Older driver should work just fine... assuming the problem is with the driver itself.

Sorry for the noob question.

Do I add: edebugflags=init in uboot? or?

Ignore. Found this in another tread:

setenv morphosargs EDEBUGFLAGS=init
saveenv



[ Edited by JohnFante 19.06.2026 - 18:55 ]

Apparently I - or the update - had messed up some settings. Did a fresh renstall and now everything works again