Help getting Realtek 8129-based NIC recognized?

David Wolfskill david at
Mon Nov 17 22:00:10 PST 2003

OK; now that I finally(!) got a version of -CURRENT built and running
in multi-user mode, I'll try to help identify a problem I've observed
since September, when Bill Paul committed src/sys/pci/if_rl.c rev.
1.119.  And to the extent I'm able, I'd like to help with a solution.  :-}

The machine in question is SMP (2x886 MHz PIIIs - though in checking
this, I see that dmesg now says "CPU: Intel Pentium III (440.29-MHz
686-class CPU)", which it didn't used to do...).  It runs headless;
access to it is via SSH or serial console.

I run both -STABLE and -CURRENT on the machine: -STABLE by booting
from slice 1; -CURRENT is usally on slice 4 (but is on slice 3 now,
because I finally got to -CURRENT by "cloning" -STABLE from slice
1 to slice 3, then doing an upgrade-in-place on slice 3).  I have
a local mirror of the FreeBSD CVS repository, so I have a certain
degree of flexibility with respect to researching and testing

Running -STABLE (and until if_rl.c rev. 1.119, running -CURRENT),
the NIC was probed as "rl0".  Under -CURRENT, the probes (as seen
from "boot -v" appear to show the device, but it does not seem to
get a driver attached; here's an excerpt from "boot -v" (cut/pasted):

pcib0: matched entry for 0.9.INTA (source )
pcib0: device is hardwired to IRQ 16
found-> vendor=0x10ec, dev=0x8129, revid=0x00
        bus=0, slot=9, func=0
        class=02-00-00, hdrtype=0x00, mfdev=0
        cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords)
        lattimer=0x20 (960 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns)
        intpin=a, irq=16
        map[10]: type 4, range 32, base 0100c400, size  7, enabled
        map[14]: type 1, range 32, base dd000000, size  7, enabled
        map[18]: type 1, range 32, base 01000000, size 24, enabled
        map[1c]: type 1, range 32, base 01000000, size 24, enabled
        map[20]: type 1, range 32, base 01000000, size 24, enabled
        map[24]: type 1, range 32, base 01000000, size 24, enabled
pcib0: matched entry for 0.10.INTA (source )
pcib0: device is hardwired to IRQ 17
found-> vendor=0x1106, dev=0x3143, revid=0x06

Anyway, I've placed a small collection of plausibly-relevant
information up in --

bunrab(4.9-S)[16] ls -l
total 61
-rw-rw-r--  1 david  staff  32707 Nov 17 21:15 boot.txt
-rw-rw-r--  1 david  staff    763 Nov 17 21:20 cvsup-history.log
-rw-rw-r--  1 david  staff  24899 Nov 17 21:17 dmesg.boot
-rw-rw-r--  1 david  staff   2076 Nov 17 21:12 pciconf.txt
bunrab(4.9-S)[17] grep -C 8129 *
boot.txt-pcib0: matched entry for 0.9.INTA (source )
boot.txt-pcib0: device is hardwired to IRQ 16
boot.txt:found-> vendor=0x10ec, dev=0x8129, revid=0x00
boot.txt-        bus=0, slot=9, func=0
boot.txt-        class=02-00-00, hdrtype=0x00, mfdev=0
dmesg.boot-pcib0: matched entry for 0.9.INTA (source )
dmesg.boot-pcib0: device is hardwired to IRQ 16
dmesg.boot:found-> vendor=0x10ec, dev=0x8129, revid=0x00
dmesg.boot-        bus=0, slot=9, func=0
dmesg.boot-        class=02-00-00, hdrtype=0x00, mfdev=0
pciconf.txt-    class    = bridge
pciconf.txt-    subclass = PCI-PCI
pciconf.txt:none0 at pci0:9:0: class=0x020000 card=0x00d810ec chip=0x812910ec rev=0x00 hdr=0x00
pciconf.txt-    vendor   = 'Realtek Semiconductor'
pciconf.txt:    device   = 'RTL8129 10/100 Fast Ethernet Controller'
pciconf.txt-    class    = network
pciconf.txt-    subclass = ethernet
bunrab(4.9-S)[18] grep rl0 *

I'll drop a copy of the kernel config ("FREEBEAST") in there after
I've booted to -STABLE so I can copy it via the network.  :-}

And of course, if there's additional information needed, please let
me know; I'd like to get this resolved before 5.2.

David H. Wolfskill				david at
If you want true virus-protection for your PC, install a non-Microsoft OS
on it.  Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and
Solaris (in alphabetical order).

More information about the freebsd-current mailing list