(please no top posting)
On 6/17/25 11:19, Greg Chandler wrote:
Hmm... I'm wondering if that means it's an alpha-only issue then, which would make this a much larger headache than it already is. Also thank you for checking, I appreciate you taking the time.
I assume the those interfaces actually work right? (simple ping over that interface would be enough) I posted in a subsequent message that mine do not appear to at all.
Oh yeah, they work just fine:
udhcpc: broadcasting discover [ 19.197697] net eth0: Setting full-duplex based on MII#1 link partner capability of cde1
# ping -c 1 192.168.254.123 PING 192.168.254.123 (192.168.254.123): 56 data bytes 64 bytes from 192.168.254.123: seq=0 ttl=64 time=2.902 ms
--- 192.168.254.123 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 2.902/2.902/2.902 ms
- - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.03 sec 39.6 MBytes 33.1 Mbits/sec 0 sender [ 5] 0.00-10.07 sec 39.8 MBytes 33.1 Mbits/sec receiver
My next step is to build that driver as a module, and see if it changes anything (I'm doubting it will). Then after that go dig up a different adapter, and see if it's the network stack or the driver.
I've been hard pressed over the last week to get a lot of diagnosing time.
Let me know if I can run experiments, I can load any kernel version on this Cobalt Qube2 meaning that bisections are possible.
Good luck!