Date: Mon, 27 Mar 2000 12:49:46 -0500 From: Dennis <dennis@etinc.com> To: Essenz Consulting <john@athena.lightningone.net>, msmith@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC Message-ID: <200003271754.MAA18212@etinc.com> In-Reply-To: <Pine.BSF.4.10.10003271054590.35966-100000@athena.lightning one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I've asked about this several times and was beaten silly by Wes Peters and Co. . It seems that they dont like to be bothered by the thousands of people suffering from a driver that is not up to date (linux and netbsd were fixed months ago)......they are way too busy working on 5.0 or something else that about 1% of their user base is using to be bothered by routine driver maintenance. While the card "works" you wont be able to set media-related features..so you really do need the fix. I've successfully fixed our version and its working nicely.....I've forwarded the info to DG so hopefully it will be patched soon. DB At 11:08 AM 3/27/00 -0500, Essenz Consulting wrote: >Mike, > >I am sorry I was so jumpy with the description of my problem. Let me >elaborate some more. I have two NIC's, a PCI Card Intel PRO/100 and an >onboard Intel PRO/100. The onboard NIC is giving the following kernel >error: > >/kernel: fxp1: warning: unsupported PHY, type = 17, addr = 2 > >Yes, the card itself is still working, it actually works fine, but every >minute this error comes up. Since this is a firewall box, I dont want >hundreds of these errors in my log every day. > >I did a little investigating, I am no where near as knowledgable as soom >of the freebsd people, but I looked at the if_fxp.c driver src and saw >that PHY Media refered to the Media of your LAN. (simplex, duplex, >10Mbit, 100Mbit) In any case, this is a signifacant bug to be worked out. >David Greenman sent me an email with a little snipit of code to add the to >fxp src, I will try that today. He also voiced his opinion about trying to >fix this issue with onboard networking, because those supermicro boards >are rolling out quickly. > >Getting back to my idea of this problem being with media type, I did >ifconfig -a and got the following: > >fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 216.243.128.21 netmask 0xffffff80 broadcast 216.243.128.127 > ether 00:90:27:b0:39:9d > media: autoselect (100baseTX <full-duplex>) status: active > supported media: autoselect 100baseTX <full-duplex> 100baseTX > 10baseT/UTP <full-duplex> 10baseT/UTP >fxp1: flags=8806<BROADCAST,DEBUG,SIMPLEX,MULTICAST> mtu 1500 > inet 216.243.129.1 netmask 0xffffff00 broadcast 216.243.129.255 > ether 00:30:48:10:0a:2d > media: manual > supported media: manual > >Obviously, they do not match. For starters I dont even know how to set >these to be the same media. I tryed ifconfig fxp1 media 100BaseTX, but >that was met with the error: SIOCSIFMEDIA: Device not configured. > >Again, any help on this would be great. > >John > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003271754.MAA18212>