dCorePlus no ethernet but wifi works?

[PDP-8]

Yeah, it's me - *that* guy again.

Seems like the wired ethernet is not working, just the local loopback on dCorePlus-Stretch and dCorePlus-Stretch64.  This is the actual port, not just a gui thing.

Both picked up my wireless cards on different machines, and had no issues doing sce-import / loads of my favorite toys so I'm assuming dhcp is up and running with those.

But the ethernet thing has me looking around to see if I need to jump-start something on my end first...

[Jason W]

Hi PDP-8.  Try booting with a waitusb= boot code, waitusb=8 is a good one to start with.  Thanks.

[PDP-8]

Thanks Jason!  You'd think by now I would remember to put a wait-state in there.

So that fixed my usb <> ethernet dongle, when the REAL problem is that no Linux distro / toolkit recognizes my onboard ethernet card in my NUC.   I was conflicting two similar problems at the same time.  So at least one is fixed!  Thanks for the pointer.

Speaking of wait states, I found an interesting article about TC that introduces wait states when dealing with very fast storage, like SSD's and ethernet (not usb) not waking up fast enough seing stuff like this during boot:

Code: [Select]

ifconfig: SIOCSIFADDR: No such Device
route: SIOCADDRT: Network is unreachable
https://iotbytes.wordpress.com/assign-persistent-static-ip-address-to-microcore-tiny-linux/

It may not apply to my dhclient situation, but I'll explore it a bit later..

[Jason W]

I sometimes have to use a waitusb= bootcode when testing dCore ISOs in Virtualbox so my on board e1000e ethernet is found, I have posted about it somewhere here.  And I swear I remember having to use a waitusb= boot code at some point for my new SATA hard drive and that is why I think I have waitusb=5 in my grub boot command line for all my dCore port entries, but I can't confirm as I have tested now without waitusb and it is found.   In any case, waitusb is a good thing to use when we know the drivers are there but the hardware is not found on boot.