NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Issues with rtk on NetBSD 10.1/i386 - phy? weird card?



I posted this before on Reddit, but didn't get much in the way of new information, so I figured that I should ask here.

I have a DFE-530TX+ NIC installed in an Intel BX-chipset Pentium II/III motherboard that I have been using to test older i386 cards and peripherals. I had been using a PCI NE2k 10M NIC, which works fine, but when I installed the Dlink card, I started to have issues.

On detection, the card first appeared with no MAC address:

Aug 24 23:49:51 p2 /netbsd: [   1.0084369] Skipping broken PCI header on 0:10:0
Aug 24 23:49:51 p2 syslogd[957]: last message repeated 7 times
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] rtk0 at pci0 dev 10 function 0: D-Link Systems DFE 530TX+ (rev. 0x10)
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] Skipping broken PCI header on 0:10:0
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] rtk0: interrupting at irq 6
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] Skipping broken PCI header on 0:10:0
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] rtk0: Ethernet address 00:00:00:00:00:00
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] rlphy0 at rtk0 phy 7: Realtek internal PHY
Aug 24 23:49:51 p2 /netbsd: [   1.0084369] rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 100baseT4, auto

Later, the MAC appeared, but I still get watchdog timeouts when the card attempts to negotiate via DHCP, even though the link seems fine:

Aug 25 00:21:44 p2 dhcpcd[588]: dhcpcd-9.4.1 starting
Aug 25 00:21:44 p2 dhcpcd[590]: DUID 00:01:00:01:2e:f2:eb:b7:00:00:b4:97:78:6b
Aug 25 00:21:44 p2 dhcpcd[590]: rtk0: waiting for carrier
Aug 25 00:21:44 p2 dhcpcd[590]: rtk0: carrier acquired
Aug 25 00:21:44 p2 dhcpcd[590]: rtk0: IAID 05:84:c5:37
Aug 25 00:21:44 p2 dhcpcd[590]: rtk0: adding address fe80::990f:c79f:9be9:2e24
Aug 25 00:21:45 p2 dhcpcd[590]: rtk0: soliciting an IPv6 router
Aug 25 00:21:45 p2 dhcpcd[590]: rtk0: soliciting a DHCP lease
Aug 25 00:21:50 p2 dhcpcd[590]: rtk0: probing for an IPv4LL address
Aug 25 00:21:51 p2 dhcpcd[590]: rtk0: using IPv4LL address 169.254.189.216
Aug 25 00:21:56 p2 dhcpcd[590]: rtk0: adding route to 169.254.0.0/16
Aug 25 00:21:57 p2 dhcpcd[590]: rtk0: adding default route
Aug 25 00:21:57 p2 dhcpcd[590]: rtk0: no IPv6 Routers available

I get watchdog timeout messages on the console, so the card clearly still isn't happy. I've tried with the PHY set to autonegotiate and with it forced to 100M/FDX, and neither seem to make a difference.

Has anyone else had similar experiences with a similar Realtek 8139 card?

Thanks for any and all help!
- Alex


Home | Main Index | Thread Index | Old Index