Re: NIC won't DHCP or configure
On Mar 21, 2005, at 9:31 PM, Kevin Kinsey wrote: *If I'm wrong, it's Chuck's fault, heh heh ?! It's always my fault, even when it's not my fault. (I must have done something. What did I do, again? :-) -- -Chuck guilty! Swiger PS: Kevin's suggestion is not a bad idea, either that or submitting the pciconf data as a PR, so it doesn't get lost ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Charles Swiger wrote: On Mar 21, 2005, at 9:31 PM, Kevin Kinsey wrote: *If I'm wrong, it's Chuck's fault, heh heh ?! It's always my fault, even when it's not my fault. (I must have done something. What did I do, again? :-) I can take the pressure off of you Chuck. Call 1-900-BLAME-ME. Fifty cents per minute to hear sincere apologies and promises to do better. Groveling at additional expense. ;) Robert P.S. please do not call the above number as I have no idea if it works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NIC won't DHCP or configure
Hello FreeBSD community, I'm trying to get my network card working under 5.3 Release. It won't DHCP. Configuring it using ifconfig doesn't permit any connection. (I also tried the February Stable, with no change as far as I can tell). WinXP identifies the NIC as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. Knoppix and WinXP both provide drivers that seem to work. Knoppix autodetects it without any (seeming) problem. My FreeBSD kernel is generic, and both the following lines are uncommented: device miibus # MII bus support device re # RealTek 8139C+/8169/8169S/8110S The output from ifconfig 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 and what I think is the relevant part of dmesg is: firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:40:24:d8 fwe0: Ethernet address: 02:90:f5:40:24:d8 fwe0: if_start running deferred for Giant It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Thanks much! Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Andrew Robinson wrote: Hello FreeBSD community, I'm trying to get my network card working under 5.3 Release. It won't DHCP. Configuring it using ifconfig doesn't permit any connection. (I also tried the February Stable, with no change as far as I can tell). WinXP identifies the NIC as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. Knoppix and WinXP both provide drivers that seem to work. Knoppix autodetects it without any (seeming) problem. My FreeBSD kernel is generic, and both the following lines are uncommented: device miibus # MII bus support device re # RealTek 8139C+/8169/8169S/8110S The output from ifconfig 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 and what I think is the relevant part of dmesg is: firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:40:24:d8 fwe0: Ethernet address: 02:90:f5:40:24:d8 fwe0: if_start running deferred for Giant It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Thanks much! It's not recognizing it at all. If (as I assume you do) have X installed could you supply the output of 'scanpci'. It will provide more information. -- Cheers, Kevin. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Hi, Andrew-- On Mar 21, 2005, at 1:54 PM, Andrew Robinson wrote: It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Take a look at the output of pciconf -v -l. The odds are that it lists a PCI ID for your NIC that the FreeBSD driver doesn't know about. Use that information to update /usr/src/sys/pci/if_rlreg.h and /usr/src/sys/dev/re/if_re.c, and see whether that gets you a working driver. If you're not sure how to do this, post the pciconf info for just your NIC so that others can try to update the code and get you a working driver... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2005-03-21, Kevin G. Eliuk scribbled these curious markings: It's not recognizing it at all. If (as I assume you do) have X installed could you supply the output of 'scanpci'. It will provide more information. Perhaps a better idea, which doesn't depend upon X, would be to use pciconf, which is in the base system. pciconf -lv (run as root) should give the details about the card. Best Regards, Christopher Nehren -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCPx0Zk/lo7zvzJioRAvatAJ9QGm6Hm3TAbOGb3pA11b1ujrbPLwCgoFNI krajXADlcfMUT2oFp37AqqQ= =6tuC -END PGP SIGNATURE- -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson If you ask the wrong questions, you get answers like 42 and God. Unix is user friendly. However, it isn't idiot friendly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Hi Kevin, It's not recognizing it at all. If (as I assume you do) have X installed could you supply the output of 'scanpci'. It will provide more information. Here it 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 0x000a cardnum 0x02 function 0x00: vendor 0x105a device 0x3373 Promise Technology, Inc. Device unknown pci bus 0x000a cardnum 0x03 function 0x00: vendor 0x10ec device 0x8169 Realtek Semiconductor Co., Ltd. RTL-8169 pci bus 0x000a cardnum 0x05 function 0x00: vendor 0x1814 device 0x0201 Device unknown I would appreciate any thoughts - thanks! Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Hi Chuck, Thanks for the suggestion - that's beyond my exerptise, but here is the (hopefully relevant) output of pciconf ### [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 ### I would appreciate any further advice or assistance, Andrew - Original Message - From: Charles Swiger [EMAIL PROTECTED] Date: Monday, March 21, 2005 11:12 am Subject: Re: NIC won't DHCP or configure Hi, Andrew-- On Mar 21, 2005, at 1:54 PM, Andrew Robinson wrote: It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Take a look at the output of pciconf -v -l. The odds are that it lists a PCI ID for your NIC that the FreeBSD driver doesn't know about. Use that information to update /usr/src/sys/pci/if_rlreg.h and /usr/src/sys/dev/re/if_re.c, and see whether that gets you a working driver. If you're not sure how to do this, post the pciconf info for just your NIC so that others can try to update the code and get you a working driver... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
Andrew Robinson wrote: Hi Chuck, Thanks for the suggestion - that's beyond my exerptise, but here is the (hopefully relevant) output of pciconf ### [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 ### I would appreciate any further advice or assistance, Andrew Hi, Andrew! Normally I wouldn't suggest this, but I'm thinking in this case you should trim all the really relevant bits of this conversation into one well-edited email with a proper introduction and send it over to [EMAIL PROTECTED], unless someone pipes up and helps you with this Real Soon Now(tm). I'm thinking that it would be fairly trivial*, and most of those fellas would love to have FreeBSD support another 1000Mbps NIC Kevin Kinsey *If I'm wrong, it's Chuck's fault, heh heh ?! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC won't DHCP or configure
On Mon, 21 Mar 2005 10:54:24 -0800, Andrew Robinson [EMAIL PROTECTED] wrote: Hello FreeBSD community, I'm trying to get my network card working under 5.3 Release. It won't DHCP. Configuring it using ifconfig doesn't permit any connection. (I also tried the February Stable, with no change as far as I can tell). WinXP identifies the NIC as Realtek RTL8169/8110 Family Gigabit Ethernet NIC. Knoppix and WinXP both provide drivers that seem to work. Knoppix autodetects it without any (seeming) problem. My FreeBSD kernel is generic, and both the following lines are uncommented: device miibus # MII bus support device re # RealTek 8139C+/8169/8169S/8110S The output from ifconfig 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 and what I think is the relevant part of dmesg is: firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:90:f5:40:24:d8 fwe0: Ethernet address: 02:90:f5:40:24:d8 fwe0: if_start running deferred for Giant It makes me wonder if FreeBSD is identifying the card as something different than it is. Is that possible? What next steps might be useful for me to take? Thanks much! Andrew My advice, try a different network switch / hub. Read on to find out why. Trying to do the poor man's Norton Ghost at a local school for a WinXP lab (using dd over ssh), I had some stupid issues. The NIC in question was an onboard SiS 900. Here's what I had using various live-cd distros: winxp (installed) - i got an IP address knoppix and DSL (both debian) - I got an IP address System Rescue CD (gentoo) - no address g4u and obsd live cd (obsd) - no address (never did try fbsd, but obsd is fairly close) When I moved a sample PC closer to the DHCP server, every distro above got an address. The lab has an older d-link 24 port switch. There are 4 switches total between the lab and the dhcp server. When I moved the PC, it was then connected to a netgear 5-port 100mb switch, still about 4 switches away from the dhcp server. I tried setting an address with ifconfig for each of the failing distros, with no success. I vaguely remember getting some weird issues reagarding the PHY in obsd... I have no idea what the cause is (just discovered this last week), but am strongly suspicious of the d-link switch. I'm going to replace it (assuming funds are available) soon. Just thought I'd pass it on, in case it helps. GS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
