Funny enough, I finally got another ethernet daughtboard for my
laptop, and this is apparently the chip (combo?) it has. I've found it
hasn't worked for me yet. I will look into it in the coming days!
Aidan
Quoth tlaro...@kergis.com:
> On Fri, Mar 28, 2025 at 07:24:28PM +1100, Oliver Lowe wrote:
> > Thanks for the tip!
> >
> > > I got a fanless mini PC with N100, Plan 9 installed no problem and
> > > recognised the network right away.
> >
> > What model NIC? I'm typing this from a N100 mini PC (running OpenBSD).
> > dmesg(8) reports the 2 network interfaces as:
> >
> > "Realtek 8168" rev 0x15: RTL8168H/8111H (0x5400)
> >
> > which I'm hoping should be supported based on my very non-expert
> > reading of /sys/src/9/pc/ether8169.c
>
> It is or will be supported since it is probably (from 0x5400) Macfg_68
> or Macfg_69:
>
> { 0x54000000, Macfg_68, Jmb9k, Fdesc2 | Fphywk | F8168gplus | Fmagicpkt2,
> 0x8F00 },
> { 0x54000000, Macfg_69, Jmb9k, Fdesc2 | Fphywk | F8168gplus | Fmagicpkt2,
> 0x8F00 },
>
> You can already verify the PCI vendor Id and the device Id. Should be
> one of these:
>
> enum { /* PCI vendors of */
> VRtl = 0x10EC, /* Realtek */
> VNcb = 0x10FF, /* NCube */
> VDlk = 0x1186, /* D-LINK */
> VAlt = 0x1259, /* Allied Telesis Inc */
> VUsr = 0x16EC, /* USRobotics */
> VLnk = 0x1737, /* Linksys */
>
> };
>
> And for the device:
>
> { VRtl, 0x8136, Rtl810x, Fpcie },
> { VRtl, 0x8161, Rtl8168, Fpcie }, /* RTL8168 add-on */
> { VRtl, 0x8162, Rtl8168, 0 }, /* RTL8168KB */
> { VRtl, 0x8168, Rtl8168, Fpcie }, /* RTL8168B */
> { VNcb, 0x8168, Rtl8168, 0 },
>
> --
> Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
> http://www.kergis.com/
> http://kertex.kergis.com/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
------------------------------------------
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T25f54f1e44602c84-Mc42bcd76f32e7787773925e7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
