My SMP (2x886 MHz PIII) "build" machine has a RealTek 8129 NIC; I generally track -CURRENT (on slice 4) on a daily basis. Until yesterday (08 Sep, as I write this), it had worked adequately for my purposes. After the build & reboot yesterday (and again today), the NIC does not seem to have been probed during the boot process. However, pciconf sees and recognizes it OK; here's its output (cut/paste, since all I have is a serial console for access to the machine while I'm running -CURRENT): freebeast(5.1-C)[3] sudo pciconf -l -v Password: hostb0_at_pci0:0:0: class=0x060000 card=0x00000000 chip=0x30911106 rev=0x01 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8633 Apollo Pro 266 CPU to PCI Bridge' class = bridge subclass = HOST-PCI pcib1_at_pci0:1:0: class=0x060400 card=0x00000080 chip=0xb0911106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'VT8633 Apollo Pro 266 CPU to AGP Controller' class = bridge subclass = PCI-PCI none0_at_pci0:9:0: class=0x020000 card=0x00d810ec chip=0x812910ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8129 10/100 Fast Ethernet Controller' class = network subclass = ethernet none1_at_pci0:14:0: class=0x040100 card=0x011113f6 chip=0x011113f6 rev=0x10 hdr=0x00 vendor = 'C-Media Electronics Inc.' device = 'CMI8738/PCI C3DX PCI Audio Chip' class = multimedia subclass = audio atapci0_at_pci0:15:0: class=0x010400 card=0x0649101e chip=0x06491095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'PCI-649 Ultra ATA/100 PCI to IDE/ATA Controller' class = mass storage subclass = RAID isab0_at_pci0:17:0: class=0x060100 card=0x00001106 chip=0x30741106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233 PCI to ISA Bridge' class = bridge subclass = PCI-ISA atapci1_at_pci0:17:1: class=0x01018a card=0x05711106 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' class = mass storage subclass = ATA none2_at_pci1:0:0: class=0x030000 card=0x8a135333 chip=0x8a135333 rev=0x02 hdr=0x00 vendor = 'S3 Incorporated' device = '86C362/86C368 Trio3D2x & Trio3D2x+ AGP' class = display subclass = VGA freebeast(5.1-C)[4] Now, I realize that there's a new re(4) driver; I have yet to see what changes might have caused a lack of probing, though. I don't really know a good way to show the lack of something during boot, though, so I've cut/pasted the rfelevant content of /var/lg/messages. I figured that if I posted that here, though, that postmaster_at_ might have an averse reaction [1], so it's at http://www.catwhisker.org/~david/FreeBSD/debug/boot-v.txt for your viewing pleasure. The kernel configuration is nearby, at http://www.catwhisker.org/~david/FreeBSD/debug/FREEBEAST. Here's output of uname: freebeast(5.1-C)[9] uname -a FreeBSD freebeast.catwhisker.org 5.1-CURRENT FreeBSD 5.1-CURRENT #50: Tue Sep 9 08:35:10 PDT 2003 root_at_freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/FREEBEAST i386 freebeast(5.1-C)[10] And here's a log showing recent CVSup history: freebeast(5.1-C)[10] tail /var/log/cvsup-history.log CVSup begin from cvsup10.freebsd.org at Sat Sep 6 03:47:18 PDT 2003 CVSup begin from cvsup7.freebsd.org at Sat Sep 6 03:47:20 PDT 2003 CVSup begin from cvsup2.freebsd.org at Sat Sep 6 03:47:23 PDT 2003 CVSup ended from cvsup2.freebsd.org at Sat Sep 6 03:55:10 PDT 2003 CVSup begin from cvsup13.freebsd.org at Sun Sep 7 03:47:19 PDT 2003 CVSup ended from cvsup13.freebsd.org at Sun Sep 7 03:54:37 PDT 2003 CVSup begin from cvsup13.freebsd.org at Mon Sep 8 03:47:15 PDT 2003 CVSup ended from cvsup13.freebsd.org at Mon Sep 8 03:54:51 PDT 2003 CVSup begin from cvsup13.freebsd.org at Tue Sep 9 03:47:15 PDT 2003 CVSup ended from cvsup13.freebsd.org at Tue Sep 9 03:54:53 PDT 2003 freebeast(5.1-C)[11] Sorry to be so clueless; thanks in advance for hints. Note 1: Familiarity with, if not appreciation of, the plot for "Iolanthe" helps in understanding this. Peace, david -- David H. Wolfskill david_at_catwhisker.org 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).Received on Tue Sep 09 2003 - 16:54:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:22 UTC