[9front] 7th gen Intel NUC ethernet troubles

[9front] 7th gen Intel NUC ethernet troubles

[Jeremy Jackins]

I am trying to test 9front on a 7th gen Intel NUC which has an I219-V
ethernet card. I'm unskilled administrating Plan 9, but I did test the
process on a Raspberry Pi to confirm that I was able to get the
network working and I'm probably not just holding it wrong.

ip/config fails with "dhcprecv: read timed out", after which
/net/ether0/stats shows:
in: 0
link: 0
out: 7
crc errs: 0
overflows: 0
soft overflows: 0
framing errs: 0
buffer errs: 0
output errs: 0
prom: 0
mbps: 1000
addr: f44d306ee4a1

/dev/kmesg has this to say:
#l0: i219: 1000Mbps port 0xDC300000 irq 11 ea f44d306ee4a1
[...]
i219: phy 1 wedged 08210000
i219: phy 2 wedged 08410000
i219: no phy

pci -v gives:
0.21.6: net 02.00.00 8086/15d8 11 0:dc300000 131072
    Intel Corporation Ethernet Connection (4) I219-V

Any tips on what I can try next? Has anyone had success with this
device, or is it a lost cause for someone without network driver
hacking knowledge?

Jeremy

Re: [9front] 7th gen Intel NUC ethernet troubles

[adventures in9]

I have some Dells that use that driver.  They have vid/did 8086/15b7
and 8086/15b8, and both have worked flawlessly.

That wedged error comes from phyread in ether82563.c.

Does it work with other OS's?

On Sat, Sep 2, 2023 at 11:29 AM Jeremy Jackins <jeremyjackins@gmail.com> wrote:
>
> I am trying to test 9front on a 7th gen Intel NUC which has an I219-V
> ethernet card. I'm unskilled administrating Plan 9, but I did test the
> process on a Raspberry Pi to confirm that I was able to get the
> network working and I'm probably not just holding it wrong.
>
> ip/config fails with "dhcprecv: read timed out", after which
> /net/ether0/stats shows:
> in: 0
> link: 0
> out: 7
> crc errs: 0
> overflows: 0
> soft overflows: 0
> framing errs: 0
> buffer errs: 0
> output errs: 0
> prom: 0
> mbps: 1000
> addr: f44d306ee4a1
>
> /dev/kmesg has this to say:
> #l0: i219: 1000Mbps port 0xDC300000 irq 11 ea f44d306ee4a1
> [...]
> i219: phy 1 wedged 08210000
> i219: phy 2 wedged 08410000
> i219: no phy
>
> pci -v gives:
> 0.21.6: net 02.00.00 8086/15d8 11 0:dc300000 131072
>     Intel Corporation Ethernet Connection (4) I219-V
>
> Any tips on what I can try next? Has anyone had success with this
> device, or is it a lost cause for someone without network driver
> hacking knowledge?
>
> Jeremy