Re: NIC detected, but won't DHCP or configure
Thanks VERY much. The card works just fine now. Andrew - Original Message - From: [EMAIL PROTECTED] (Dag-Erling Smørgrav) Date: Wednesday, March 23, 2005 9:42 am Subject: Re: NIC detected, but won't DHCP or configure Andrew Robinson [EMAIL PROTECTED] writes: re_probe(): vid 10ec did 8169 hwrev 1000 That's an 8169SB, which is supported in -CURRENT. Try the attached patch. I'll try to get it merged before 5.4-RELEASE. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Excellent! The interface is now up: bash-2.05b$ ifconfig fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 02:90:f5:40:24:d8 ch 1 dma -1 re0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:90:f5:3f:08:d8 media: Ethernet autoselect (100baseTX) status: no carrier plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 And: bash-2.05b$ pciconf -lv [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet I am not able to check the viability of the network connection until tomorrow. I will report back. Again, thanks. Andrew - Original Message - From: [EMAIL PROTECTED] (Dag-Erling Smørgrav) Date: Wednesday, March 23, 2005 9:42 am Subject: Re: NIC detected, but won't DHCP or configure Andrew Robinson [EMAIL PROTECTED] writes: re_probe(): vid 10ec did 8169 hwrev 1000 That's an 8169SB, which is supported in -CURRENT. Try the attached patch. I'll try to get it merged before 5.4-RELEASE. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Thanks for the patch. This is the outcome: re_probe(): vid 10ec did 8169 hwrev 1000 Andrew - Original Message - From: [EMAIL PROTECTED] (Dag-Erling Smørgrav) Date: Tuesday, March 22, 2005 10:11 am Subject: Re: NIC detected, but won't DHCP or configure Daniel O'Connor [EMAIL PROTECTED] writes: On Tue, 22 Mar 2005 17:30, Andrew Robinson wrote: thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still Try if_rl.ko/rl0 No, if_rl will not attach to 8169 cards. Andrew, it seems you have a chip revision which isn't currently supported. Try applying the attached patch, and see if loading if_re.ko results in something like this: re_probe(): vid 10ec did 8169 hwrev 0080 the first two numbers should be exactly as shown, but the last number should be different; let me know what it is. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Can you give us the output of pciconf -r pci10:3:0 0:0xff ?
Certainly:
816910ec 02b7 0210
4001 b3004800
09001558
00dc 40200115
f7c20001
0003
Andrew
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Dan, thanks for your suggestion. I have now tried that, and, sadly, it does not change the output of pciconf or ifconfig. So, to sum up my understanding: the OS seems to detect the NIC correctly, but does not load the drivers. The NIC should be covered by the re drivers. What ought I do next? I would appreciate any further advice or thoughts. Thanks, Andrew On Tue, 22 Mar 2005 17:30, Andrew Robinson wrote: thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still Try if_rl.ko/rl0 -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
NIC detected, but won't DHCP or configure
Dear FreeBSD hackers, I posted the following question on freebsd-questions. Two kind souls kicked it around for a little and suggested that I pass it on to you. I have a laptop with a netowrk card that seems to be successfully detected under FreeBSD, Knoppix, and WinXP, but will only work under Knoppix and WinXP. I tender the following for your information. Windows identifies the card as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. scanpci and pciconf (see below) seem to agree. Under FreeBSD: dmesg: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #0: Mon Mar 21 17:27:06 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL Preloaded elf kernel /boot/kernel/kernel at 0xc0a22000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0a22294. Calibrating clock(s) ... i8254 clock: 1193250 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3391516719 Hz CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz (3391.52-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 snip Here is where the boot sequence detects the 10/100/1000 NIC: = pcib2: slot 3 INTA hardwired to IRQ 21 found- vendor=0x10ec, dev=0x8169, revid=0x10 bus=10, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) intpin=a, irq=21 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base b3006000, size 13, memory disabled pcib2: device (null) requested decoded memory range 0xb3006000-0xb3007fff pcib2: matched entry for 10.5.INTA Here is where the 802.11 device is detected: == pcib2: slot 5 INTA hardwired to IRQ 17 found- vendor=0x1814, dev=0x0201, revid=0x01 bus=10, slot=5, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0410, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=17 powerspec 2 supports D0 D3 current D0 cbb0: TI1410 PCI-CardBus Bridge at device 0.0 on pci10 pcib2: device cbb0 requested decoded memory range 0xb300-0xb30f cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xb3008000 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 pcib2: matched entry for 10.0.INTA pcib2: slot 0 INTA hardwired to IRQ 18 cbb0: [MPSAFE] ifconfig -a output is: == fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 02:90:f5:40:24:d8 ch 1 dma -1 plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 pciconf -lv output is: == [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class = network subclass = ethernet [EMAIL PROTECTED]:5:0: class=0x028000 card=0x68331462 chip=0x02011814 rev=0x01 hdr=0x00 vendor = 'Ralink Technology Corp' class = network scanpci output is: = pci bus 0x cardnum 0x00 function 0x00: vendor 0x8086 device 0x2580 Intel Corp. Device unknown pci bus 0x cardnum 0x01 function 0x00: vendor 0x8086 device 0x2581 Intel Corp. Device unknown pci bus 0x cardnum 0x1b function 0x00: vendor 0x8086 device 0x2668 Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x00: vendor 0x8086 device 0x2658 Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x01: vendor 0x8086 device 0x2659 Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x02: vendor 0x8086 device 0x265a Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x03: vendor 0x8086 device 0x265b Intel Corp. Device unknown pci bus 0x cardnum 0x1d function 0x07: vendor 0x8086 device 0x265c Intel Corp. Device unknown pci bus 0x cardnum 0x1e function 0x00: vendor 0x8086 device 0x244e Intel Corp. 82801BA/CA/DB/EB PCI Bridge pci bus 0x cardnum 0x1f function 0x00: vendor 0x8086 device 0x2640 Intel Corp. Device unknown pci bus 0x cardnum 0x1f function 0x01: vendor 0x8086 device 0x266f Intel Corp. Device unknown pci bus 0x cardnum 0x1f function 0x03: vendor 0x8086 device 0x266a Intel Corp. Device unknown pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x10de device 0x00c8 nVidia Corporation Device unknown pci bus 0x000a cardnum 0x00 function 0x00: vendor 0x104c device 0xac50 Texas Instruments PCI1410 PC card Cardbus Controller pci bus 0x000a cardnum 0x01 function 0x00: vendor 0x104c device 0x8023 Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) pci bus
Re: NIC detected, but won't DHCP or configure
Hi Jason, thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still [EMAIL PROTECTED]:3:0:class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet and ifconfig still lacks any reference to re. Many thanks, Andrew - Original Message - From: jason henson [EMAIL PROTECTED] Date: Monday, March 21, 2005 9:26 pm Subject: Re: NIC detected, but won't DHCP or configure Andrew Robinson wrote: Dear FreeBSD hackers, I posted the following question on freebsd-questions. Two kind souls kicked it around for a little and suggested that I pass it on to you. I have a laptop with a netowrk card that seems to be successfully detected under FreeBSD, Knoppix, and WinXP, but will only work under Knoppix and WinXP. I tender the following for your information. Windows identifies the card as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. scanpci and pciconf (see below) seem to agree. Under FreeBSD: dmesg: pciconf -lv output is: == [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class = network subclass = ethernet [EMAIL PROTECTED]:5:0: class=0x028000 card=0x68331462 chip=0x02011814 rev=0x01hdr=0x00 vendor = 'Ralink Technology Corp' class = network Try kldload if_re.ko, and man if_re. This means that you have no driver attached to it: [EMAIL PROTECTED]:3:0: See how I have the if_nv.ko loaded and working. [EMAIL PROTECTED]:4:0: class=0x02 card=0x10001695 chip=0x006610de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP-T Networking Adapter' class= network subclass = etherne ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
