FreeBSD 9.2 - does not appear to support the 'dc' PCMCIA NIC driver
I have a Netgear FA511 PCMCIA NIC that worked fine under 9.1. Under 9.2 I get the following message: Oct 6 21:38:11 monitor4 kernel: dc0: port 0x1100-0x11ff irq 19 at device 0.0 on cardbus0 Oct 6 21:38:11 monitor4 kernel: dc0: attaching PHYs failed This used to work under 9.1, does anyone know what happened? Thanks. Kent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ascertaining NIC Driver Version
On Jan 7, 2011, at 11:12 AM, Robert Huff wrote: >> "uname -a" is probably the most general answer, as most FreeBSD >> NIC drivers don't have individualized version #s, aside from the >> OS version itself. > > That is not my understanding. > To the OP: FreeBSD NIC drivers can and do have version numbers: > > huff@>> grep \$FreeBSD /sys/dev/e1000/if_em.c > /*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.64 2010/12/04 06:38:21 jfv Exp $*/ Um, that's the CVS revision number for that particular file. It should be obvious that it has nothing whatsoever to do with a human-assigned driver version #, if one even exists, such as em "v6.9.21" for: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=839&DwnldID=17509&ProductFamily=Network+Connectivity&ProductLine=Intel%C2%AE+Server+Adapters&ProductProduct=Intel%C2%AE+PRO%2f1000+F+Server+Adaptereng Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ascertaining NIC Driver Version
Chuck Swiger writes: > > Is there a command line utility, a la ethtool or the like, that > > can be used to query the NIC driver version? > > "uname -a" is probably the most general answer, as most FreeBSD > NIC drivers don't have individualized version #s, aside from the > OS version itself. That is not my understanding. To the OP: FreeBSD NIC drivers can and do have version numbers: huff@>> grep \$FreeBSD /sys/dev/e1000/if_em.c /*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.64 2010/12/04 06:38:21 jfv Exp $*/ The system in question: FreeBSD 9.0-CURRENT #0: Sat Oct 23 08:15:53 EDT 2010 amd64 Obviously, the driver and OS version have nothing to do with each other. And the FreeBSD driver version will probably have nothing to do with any other driver version, especially one provided by the manufacturer. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re: Ascertaining NIC Driver Version
Thanks, Chuck! I Googled for an answer for a while and didn't find much. I did find that the particular driver I was interested did have a version number in the source, but the question actually came from a user who doesn't have source trees on their hosts. On Jan 7, 2011 1:45pm, Chuck Swiger wrote: On Jan 7, 2011, at 10:33 AM, vrwmil...@gmail.com wrote: > Is there a command line utility, a la ethtool or the like, that can be used to query the NIC driver version? "uname -a" is probably the most general answer, as most FreeBSD NIC drivers don't have individualized version #s, aside from the OS version itself. The sysctl tree under dev for a particular device, ie, "sysctl dev.bce", "sysctl dev.em", etc will return more information which might include a vendor-specific driver version #... Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ascertaining NIC Driver Version
On Jan 7, 2011, at 10:33 AM, vrwmil...@gmail.com wrote: > Is there a command line utility, a la ethtool or the like, that can be used > to query the NIC driver version? "uname -a" is probably the most general answer, as most FreeBSD NIC drivers don't have individualized version #s, aside from the OS version itself. The sysctl tree under dev for a particular device, ie, "sysctl dev.bce", "sysctl dev.em", etc will return more information which might include a vendor-specific driver version #... Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Ascertaining NIC Driver Version
HI All, Is there a command line utility, a la ethtool or the like, that can be used to query the NIC driver version? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Realtek 3-port NIC driver not loading
I have two Realtek cards in my box - one single port 8619, and one 3-port 8619 (Jetway AD3RTLANG). FreeBSD loads the driver for the single port, but not the other three. It does list them all in pciconf with the same chipset, output below: [EMAIL PROTECTED]:8:0: class=0x02 card=0x816910ec chip=0x816910ec rev=0x10 hdr=0x00 class= network subclass = ethernet [EMAIL PROTECTED]:9:0: class=0x02 card=0x10ec16f3 chip=0x816910ec rev=0x10 hdr=0x00 class= network subclass = ethernet [EMAIL PROTECTED]:11:0:class=0x02 card=0x10ec16f3 chip=0x816910ec rev=0x10 hdr=0x00 class= network subclass = ethernet [EMAIL PROTECTED]:12:0:class=0x02 card=0x10ec16f3 chip=0x816910ec rev=0x10 hdr=0x00 class= network subclass = ethernet The strange thing is - when I loaded FreeNAS 0.671 (6.1 based), it works perfectly. When I use any other 6.1 or 6.2 installation, it displays the following messages on boot for the 3-port card: pci0: at device 9.0 (no driver attached) pci0: at device 11.0 (no driver attached) pci0: at device 12.0 (no driver attached) I'm somewhat new to BSD. Can someone point me in the right direction? -- Jeremy Jongsma <[EMAIL PROTECTED]> Traders Media ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NIC driver question
U can always add additional Intel/3COM NIC, in case the builtin card is not recognized. -- Aftab Jahan Subedar CEO/Software Engineer Subedar Technologies Ltd Soubedar Baag Bibir Bagicha #1 North Jatra Bari Dhaka 1204 Bangladesh http://www.DhakaStockExchangeGame.com Frank Bonnet wrote: Hello I will receive in few days my new mail server the machine will be an IBM X3650 bi xeon. I wonder what would be the "best" network interface to plug in (if necessary) as I don't know for now what is the builtin interfaces in this machine. To be clear I'm asking gurus on what is the "best FreeBSD supported" NIC driver to avoid eventual perfomances problems. Thanks a lot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NIC driver question
El Mar 21 Nov 2006 09:57, Peter A. Giessel escribió: > man em: > *** QUOTE *** > AUTHORS > The em driver was written by Intel Corporation > <[EMAIL PROTECTED]>. > *** END QUOTE *** > > man bge: > *** QUOTE *** > AUTHORS > The bge driver was written by Bill Paul <[EMAIL PROTECTED]>. > *** END QUOTE *** Hi: Forget about bge, since Bill Paul do not support this driver anymore! Here is the mail that he send me some months ago. - El Mar 14 Mar 2006 22:22, escribió: > Of all the gin joints in all the towns in all the world, Martin Alejandro > > Paredes Sanchez had to walk into mine and say: > > Hi: > > > > The problem is that the network card is not detected, is a network card > > Boradcom in the mother board. I see a chip with this numbers: > > > > Broadcom > > BCM5751FKFB > > HS0521 P21 > > 744910 N > > > > Whit "dmesg | grep -i ethe" I got: > > > > pci2: at device 0.0 (no driver attached) > > > > With "pciconf -lv" I got: > > > > [EMAIL PROTECTED]:0:0: class=0x02 card=0x02f71014 chip=0x167e14e4 > > rev=0x11 > > hdr=0x00 > > vendor = 'Broadcom Corporation' > > device = 'BCM5751F NetXtreme Fast Ethernet PCI Express' > > class= network > > subclass = ethernet > > > > The manual for bge(4), says: > > > > bge -- Broadcom BCM570x/5714/5721/5750/5751/5789 PCI Gigabit Ethernet > > adapter driver > > > > is this nic supported? > > > > TIA > > Oh for crap's sake. How many people are going to keep bothering me with > this. For the umpity-umpth time, I do not support this driver anymore! > > Why don't you make a tiny bit of effort and find out for yourself if the > NIC is supported! Edit /sys/dev/bge/if_bgereg.h, and change this: > > #define BCOM_DEVICEID_BCM5751M 0x167D > > to this: > > #define BCOM_DEVICEID_BCM5751M 0x167E > > Then recompile your kernel and find out for yourself it it works. Then mail > all your findings to the freebsd-current mailing list and ask for someone > to update the driver. > > -Bill > > -- > === >== -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu > [EMAIL PROTECTED] | Wind River Systems > === >== "Ignorance may be bliss, but delusion is ecstasy!" -Perki > === >== ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Adding NIC driver
Using FreeBSD 4.11, suppose I wanted to use a different NIC, say, an Intel one, from my motherboard's built-in SysKonnect SK-984x and SK-982x gigabit ethernet (sk0) I use now. Can I add/compile a driver for such a device, without having to recompile the kernel? Thanks, - Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EM Nic driver not up to date
Hi, I just did a makeworld and I notice that the em drivers of the distribution is now version 2.1.7 On intel's website, the sources of em version 3.2.15 for freebsd are available, can someone update the sources so that people can benefit from it ? (not sure where to ask for this) For now, I will just recompile them myself... Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
88E8053 Gigabit NIC driver install problem
I have MSI 915P MB with integrated Marvell Youkon 88E8053 Gigabit NIC on FreeBDS 5.3 and tried to install a driver sk98bsd52x86-6.05.tgz for this NIC by following the instructions from syskonnect http://www.syskonnect.com/syskonnect/support/driver/d0102_driver.html but when i typekldload if_yk.ko i get error "link_elf: symbol m_gethdr underfined" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NIC Driver Hacking
Since so many people gave me on -mobile and -questions gave me so much help, I'd like to *TRY* to continue working on adding support for the Broadcom 4401-B0 to FreeBSD. Here's where I came from: None of my CardBus, NIC, WiFi, etc devices were getting register memory: http://phpbootcamp.com/articles/inspiron700m/dmesg_verbose.txt All hardware worked fine under Windows. Well, as fine as anything works under Windows. :-) Here's where I am: I can use "allow_unsupported_io_range" and all my devices get identified and assigned what look like valid memory ranges: http://www.phpbootcamp.com/articles/inspiron700m/hw.pci.allow_unsupported_io_range/dmesg.txt Attempting to configure the NIC using ifconfig or the sysinstall GUI locks up the machine completely. So, which of the following most likely describes my current status: A) The unsupported_io_range is fine, but the driver source needs hacking B) I really haven't solved the device register memory issues -- they just *SEEM* to be okay. If it's A) I can start mucking with C code and hopefully not damage my hard drive too much in the process... If it's B) I'm still at a complete loss how to compute valid io_range... Use the Windows numbers, since they work? Use the Linux numbers, since they work? Some kind of tool/monitor to compute a base offset? If it's A) I can also start playing with the CardBus and WiFi with some hope of it working. If it's B) there's not much point in my buying a PCM/CIA WiFi card, now is there, as the Cardbus io_range ain't gonna be any good either, is it?... -- Like Music? http://l-i-e.com/artists.htm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Where does NIC driver lies in freebsd kernel ?
manish gautam <[EMAIL PROTECTED]> writes: > 1. Where does source code of NIC driver lies on my freebsd 4.7 kernel ? That depends on which driver you're using. I have an Intel Pro/100 card, so I use the fxp driver, for which the device-specific driver is at /usr/src/sys/dev/fxp, and the miibus generic support is at /usr/src/sys/dev/mii. > 2. Can you please provide me some examples of implementing netgraph > nodes ( if possible send some helpful links also ) /usr/share/examples/netgraph ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Where does NIC driver lies in freebsd kernel ?
Hello Sir ! Sir i facing some silly problems , problems are :: 1. Where does source code of NIC driver lies on my freebsd 4.7 kernel ? 2. Can you please provide me some examples of implementing netgraph nodes ( if possible send some helpful links also ) Please reply soon... best regards manish Yahoo! India Mobile: Ringtones, Wallpapers, Picture Messages and more.Download now. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nic driver
Is there ed1 driver support in FBSD 4.7? i have a PCMCIA NIC that needs that driver. The driver is in FBSD 5.0 and the NIC works great in FBSD 5.0. can i just add a line for the driver into the kernel config file or do i need to do something else to get it to work? thanks, brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
