9front - general discussion about 9front
 help / color / mirror / Atom feed
From: adventures in9 <adventuresin9@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 7th gen Intel NUC ethernet troubles
Date: Sun, 3 Sep 2023 11:07:37 -0700	[thread overview]
Message-ID: <CAPfmpJCMH_0F+Q61CmmVHZnaOw2QOmk=q3-BikOBUOPZzAyvvg@mail.gmail.com> (raw)
In-Reply-To: <CAOr72mjQV__KRPkHOMuN6UxmGR+ouN=QE8n1-+o1aT6WCxn53Q@mail.gmail.com>

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

      reply	other threads:[~2023-09-03 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOr72mhw=MogupmE=wXRK8Dg+vu76WUDhODNyhwDCuJjDq8kFg@mail.gmail.com>
2023-09-02 18:27 ` Jeremy Jackins
2023-09-03 18:07   ` adventures in9 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPfmpJCMH_0F+Q61CmmVHZnaOw2QOmk=q3-BikOBUOPZzAyvvg@mail.gmail.com' \
    --to=adventuresin9@gmail.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).