Date: Sat, 8 Mar 2003 00:02:12 -0500 From: Dexter McNeil <dexter@backtech.com> To: Brian O'Shea <b_oshea@yahoo.com> Cc: freebsd-stable@freebsd.org Subject: Re: Apparent problem with pcn driver on 5.0-RELEASE Message-ID: <20030308050212.GA3774@net-1.backtech.com> In-Reply-To: <20030308002639.91734.qmail@web10503.mail.yahoo.com> References: <20030307220431.75419.qmail@web10504.mail.yahoo.com> <20030308002639.91734.qmail@web10503.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems that the pcn driver has been broken sometime after 4.3 & before 4.4. I've got the same problems with the driver in 4.5 up to 4.8. I can make hardware available remotely via ssh over the internet if someone wants to work on it. Test box is an IBM Netfinity 5500 w/quad 550Mhz P-III Xeon, AMD 79C971 on m/b w/ Nat. Semi PHI, AMD 79C971 w/ LevelI PHY on PCI card, Intel 82559 for primary network connectivity as well for test system, and another machine to gain console access and reach the AMD test interfaces. Also a Cisco switch with console access to the switch to allow looking at the network. This is a copy of the message that I had posted to freebsd-net: - On the same basic subject - it seems that sometime after the release of - FreeBSD 4.3 the pcn ethernet driver was broken. I did find PR kern/34071 - which indicated that the driver was broken in 4.5RC2. I've tried the - following versions of FreeBSD from the fixit CDROMS: - - 4.3 - works fine - 4.4 - doesn't work - ping can't get to the outside world (host - unreachable - it's a directly connected machine I'm trying to ping...), - though interface status info appears good as reported by ifconfig. Media & - mediaopt options don't seem to make any difference. While the line will go - to half-duplex or 10baseT/UTP modes, it doesn't solve the problem of not - getting bits out the door... - - 4.5 - same as 4.4 - - 4.6.2 - doesn't work - after ifconfig'ing the interface with an IP - address & such, ifconfig reports that the interface is in hardware - loopback. This is confirmed by the loss of link status on the switch the - interface is connected to. Media & mediaopt options don't change this - state. - 4.7 - same as 4.6.2 - 4.8-prerelease - same as 4.6.2 - - 5.0 - has the same issues as 4.6.2. - - The main interest in this driver is that IBM uses the AMD 79C971 chip with - a National Semiconductor DP83840 PHY on the motherboard in the - Netfinity 5500 server. The 79C971 chip with a Level 1 PHY is used in their - fault tolerant 10/100 PCI NIC of the same vintage. I've got a number of - these machines that I need/want to run FreeBSD on. Cheers, Dexter McNeil On Fri, Mar 07, 2003 at 04:26:39PM -0800, Brian O'Shea wrote: > Here's some more background information, as requested by a private responder: > > # netstat -rn -f inet > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 15.0.71.254 UGSc 0 0 pcn0 > 15.0.64/21 link#1 UC 2 0 pcn0 > 15.0.64.12 link#1 UHRLW 0 12 pcn0 9 > 15.0.71.254 link#1 UHLW 1 0 pcn0 > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > > I don't know where the 15.0.64.12 route came from. It might be the IP > address of a DHCP server. I was using dhclient to configure the interface > initially but it would always time out, leaving the interface "UP" but > configured with 0.0.0.0 address. > > Rebooting the system without configuring the network interface resulted > in the same routing table except without the 15.0.64.12 entry. > > Thanks, > -brian > > --- Brian O'Shea <b_oshea@yahoo.com> wrote: > > I'm not sure if this is the correct place to post this since most > > discussion seems to be related to the 4-STABLE branch. Please feel > > free to redirect me if necessary. > > > > I am having problems with the pcn driver for the AMD PCnet fast ethernet > > chip on a PC (Intel PII 400MHz) running FreeBSD 5.0-RELEASE. I can configure > > the interface but it does not seem to work. I'm sorry that I don't have > > more diagnostic information, but I don't know what else to check. Here's > > what I have: > > > > From dmesg: > > > > pcib2: device pcn0 requested decoded I/O range 0x7ce0-0x7cff > > pcn0: <AMD PCnet/PCI 10/100BaseTX> port 0x7ce0-0x7cff mem > > 0xfdfff400-0xfdfff41f > > irq 9 at device 5.0 on pci2 > > pcn0: Ethernet address: 00:60:b0:3d:06:1e > > miibus0: <MII bus> on pcn0 > > > > > > Interface configuration: > > > > # ifconfig pcn0 inet 15.0.65.119 netmask 0xfffff800 > > # ifconfig pcn0 > > pcn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > inet6 fe80::260:b0ff:fe3d:61e%pcn0 prefixlen 64 scopeid 0x1 > > inet 15.0.65.119 netmask 0xfffff800 broadcast 15.0.71.255 > > ether 00:60:b0:3d:06:1e > > media: Ethernet autoselect (100BaseTX <full-duplex>) > > status: active > > > > I can ping the interface address, but can not ping other hosts on the > > same subnet. The hardware is known to work with other OS's. > > > > Any help would be much appreciated. > > Thanks, > > -brian > > > > > > __________________________________________________ > > Do you Yahoo!? > > Yahoo! Tax Center - forms, calculators, tips, more > > http://taxes.yahoo.com/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Tax Center - forms, calculators, tips, more > http://taxes.yahoo.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- The ultimate destination on the journey of life is a hole 6 feet deep. Enjoy the journey - the destination is nothing to write home about. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030308050212.GA3774>