From owner-freebsd-stable Sun Apr 9 19:23:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cc677580-a.sumt1.nj.home.com (cc677580-a.sumt1.nj.home.com [24.3.178.81]) by hub.freebsd.org (Postfix) with ESMTP id A58ED37B63E for ; Sun, 9 Apr 2000 19:23:36 -0700 (PDT) (envelope-from squirk@home.com) Received: from localhost (squirk@localhost) by cc677580-a.sumt1.nj.home.com (8.9.3/8.9.3) with ESMTP id WAA00627 for ; Sun, 9 Apr 2000 22:23:08 -0400 (EDT) (envelope-from squirk@home.com) X-Authentication-Warning: cc677580-a.sumt1.nj.home.com: squirk owned process doing -bs Date: Sun, 9 Apr 2000 22:23:08 -0400 (EDT) From: Steve Quirk X-Sender: squirk@cc677580-a.sumt1.nj.home.com To: freebsd-stable@freebsd.org Subject: Re: can't get fxp working on ca810 mobo In-Reply-To: <4.2.2.20000409214241.03311330@mail.sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I removed IPFIREWALL to get that out of the picture. The entry in rc.conf for fxp0 has "media 100baseTX". Here's the info: > ifconfig -a fxp0: flags=8843 mtu 1500 inet 192.168.2.110 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:90:27:f9:14:6d media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP xl0: flags=8843 mtu 1500 inet 192.168.1.110 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:10:4b:d2:b7:22 media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010 mtu 1280 gif1: flags=8010 mtu 1280 gif2: flags=8010 mtu 1280 gif3: flags=8010 mtu 1280 stf0: flags=8000 mtu 1280 faith0: flags=8000 mtu 1500 > > netstat -nra Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.1.1 UGSc 1 0 xl0 24.3.128.34 192.168.1.1 UGHW3 0 9 xl0 3382 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.168.1 link#2 UC 0 0 xl0 => 192.168.1.1 0:a0:c9:65:1c:a7 UHLW 5 42 xl0 905 192.168.1.22 0:50:e4:3a:be:16 UHLW 1 243 xl0 953 192.168.2 link#1 UC 0 0 fxp0 => 192.168.2.1 link#1 UHRLW 0 11 fxp0 => > > ipfw show ipfw: socket: Operation not permitted > > ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1): 56 data bytes ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ^C Steve On Sun, 9 Apr 2000, Mike Tancsa wrote: > At 06:06 PM 4/9/2000 -0400, Steve Quirk wrote: > >About the only symptom I can describe is that "ifconfig fxp0" reports > >"media: autoselect status: no carrier". If I use "media 100baseTX" with > >ifconfig, of course, it reports "media 100baseTX status: no carrier". > > > >The link light near the connector is on. I can see it flutter when I > >ifconfig/up or when I try to ping. Ping reports "sendto: Host is down". > > > Can you perhaps post to the list the results of > > ifconfig -a > ipfw show > netstat -nra > > > ---Mike > > > > > >I have other Intel NICs in other hosts on the same hub. Their rc.conf > >entries have "media 100baseTX" on them. No trouble with them. > > > >Sorry, I'm used to things working. If there's other info I can provide > >let me know. > > > >Steve > > > >On Sun, 9 Apr 2000, David Greenman wrote: > > > > > >Thanks for the replies. network_interfaces omission was a copy&paste > > > >error (sharp eye, though). > > > > > > > >fxp1 (mis)behaves the same way. > > > > > > > >I put a 3com 3c905b-TX in and it's working ok but this won't really do > > > >long-term (but at least I know the motherboard is ok). I need 2 > > > >interfaces on the box - it's a 2u rack mount and there's not enough > > > >available slots for another NIC. > > > > > > > >Are there any known issues with the fxp driver or any config flags or > > > >other magical incantations I can try? I upgraded the BIOS, I'll try > > > >switching PCI slots. > > > > > > > >Is there any other diagnostic information I could gather that would help? > > > > > > >> >ifconfig_fxp0="inet 192.168.1.100 netmask 255.255.255.0 media > > 100baseTX" > > > > > > Setting 100baseTX will disable autonegotiation, so half-duplex will > > also be > > > set. If the switch it is plugged into isn't set that way as well, then > > you'll > > > have a problem. > > > Actually, you haven't described the symptoms - you just say it doesn't > > > work, but the diagnostic info you've provided to this point doesn't > > indicate > > > a problem. Can you be more specific about what doesn't work, what happens > > > when you try to use the interface, etc.? > > > > > > -DG > > > > > > David Greenman > > > Co-founder/Principal Architect, The FreeBSD Project - > > http://www.freebsd.org > > > Creator of high-performance Internet servers - http://www.terasolutions.com > > > Pave the road of life with opportunities. > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message