LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 10-22-2007, 11:09 AM   #1
Hewson
Member
 
Registered: Feb 2007
Location: /home
Distribution: Kubuntu and CentOS
Posts: 214

Rep: Reputation: 32
how do i tell what driver is being used for NIC


on fc6 i need to know the driver of one of my NICs. I plugged it in and it works fine, but i would like to know what driver is being used all the same.

'lspci' lists some info, but i'm not sure if there are other cmds that will give me more.

Thanks,

Steve
 
Old 10-22-2007, 11:34 AM   #2
farslayer
LQ Guru
 
Registered: Oct 2005
Location: Northeast Ohio
Distribution: linuxdebian
Posts: 7,249
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
Well a combination of tools it looks like..

lspci to determine the chipset..
lsmod to list the loaded modules
modinfo <modulename> to get information about the module..


Code:
mail:~# lspci | grep -i eth
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)


mail:~# lsmod
.
.

bnx2                   76272  0
.
.


mail:~# modinfo bnx2
filename:       /lib/modules/2.6.18-4-686/kernel/drivers/net/bnx2.ko
author:         Michael Chan <mchan@broadcom.com>
description:    Broadcom NetXtreme II BCM5706/5708 Driver
license:        GPL
version:        1.4.44
vermagic:       2.6.18-4-686 SMP mod_unload 686 REGPARM gcc-4.1
depends:
alias:          pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i*
alias:          pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i*
alias:          pci:v000014E4d0000164Asv*sd*bc*sc*i*
alias:          pci:v000014E4d0000164Csv*sd*bc*sc*i*
alias:          pci:v000014E4d000016AAsv0000103Csd00003102bc*sc*i*
alias:          pci:v000014E4d000016AAsv*sd*bc*sc*i*
alias:          pci:v000014E4d000016ACsv*sd*bc*sc*i*
srcversion:     2AE4E6CC6B4C08FD7809E3A
parm:           disable_msi:Disable Message Signaled Interrupt (MSI) (int)

Scratch all that use ethtool instead.. much easier to link the driver to the Ethernet interface..

Code:
it-etch:~# ethtool -i eth0
driver: b44
version: 1.01
firmware-version:
bus-info: 0000:02:09.0
Code:
mail:~# ethtool -i eth0
driver: bnx2
version: 1.4.44
firmware-version: 1.9.6
bus-info: 0000:03:00.0

Last edited by farslayer; 10-22-2007 at 11:37 AM.
 
Old 10-22-2007, 01:40 PM   #3
Hewson
Member
 
Registered: Feb 2007
Location: /home
Distribution: Kubuntu and CentOS
Posts: 214

Original Poster
Rep: Reputation: 32
Thanks so much.


One more question, purely academic, how could I figure out what lspci output is connected to which Ethernet interface? (I just used the GUI network tool to figure this out, but I'm sure theres a way to do it via the CLI) In other words how would I know that lspci output "ADMtek NC100" is related to eth1.

[root@basil ~]# lspci | grep -i eth
03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
03:02.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)
03:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller (rev 04)

[root@basil ~]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:12:17:5B:7F:05
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51007487 errors:0 dropped:0 overruns:0 frame:0
TX packets:23787035 errors:820963 dropped:0 overruns:0 carrier:1641481
collisions:0 txqueuelen:1000
RX bytes:476910570 (454.8 MiB) TX bytes:467538115 (445.8 MiB)
Interrupt:20 Base address:0xec00
[root@basil ~]# ethtool -i eth1
driver: tulip
version: 1.1.14
firmware-version:
bus-info: 0000:03:02.0
[root@basil ~]# modinfo tulip
filename: /lib/modules/2.6.20-1.2962.fc6/kernel/drivers/net/tulip/tulip.ko
version: 1.1.14
license: GPL
description: Digital 21*4* Tulip ethernet driver
author: The Linux Kernel Team
srcversion: EADF7CED2EDFDF71BF91658
 
Old 10-22-2007, 02:45 PM   #4
farslayer
LQ Guru
 
Registered: Oct 2005
Location: Northeast Ohio
Distribution: linuxdebian
Posts: 7,249
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
Compare the bus ID from the output of lspci to the bus info from ethtool -i <interface>

Code:
mail:~# lspci | grep -i eth
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)

Code:
mail:~# ethtool -i eth0
driver: bnx2
version: 1.4.44
firmware-version: 1.9.6
bus-info: 0000:03:00.0



mail:~# ethtool -i eth1
driver: bnx2
version: 1.4.44
firmware-version: 1.9.6
bus-info: 0000:05:00.0

you could probably also grep the dmesg output..


Code:
mail:~# cat /var/log/dmesg | grep -i eth
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.44 (August 10, 2006)
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 169, node addr 0019bb2e8126
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem fa000000, IRQ 169, node addr 0019bb2e8188
bnx2: eth0: using MSI

mail:~# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:19:BB:2E:81:88
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:169 Memory:fa000000-fa011100
Obviously if the cards were different types it would be easier to tell them apart in dmesg but the MAC address should work too..

Last edited by farslayer; 10-22-2007 at 02:50 PM.
 
Old 10-22-2007, 02:55 PM   #5
inspiron_Droid
Member
 
Registered: Dec 2006
Distribution: Debian (Wheeze)
Posts: 391

Rep: Reputation: Disabled
It looks to me like you have three network Controllers betwee the Intel PCI Add in card, AMD Net (on board Net work interface card) and the RealTalk PCI Add in card. To check you NIC driver ctrl+alt+f1 to inter in to a command line interface and enter root for your user name and the administrative password you selected in the installation process hitting the return key after you enter each credential.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
NIC Driver Help OldManRiver Red Hat 3 11-29-2006 10:38 AM
NIC Driver for NVidia NForce onboard NIC. rajjpajj Linux - Software 9 09-28-2004 03:54 PM
NIC Driver need Neb Linux - Hardware 3 08-11-2003 09:41 PM
nic driver sharrej Slackware 2 06-09-2003 01:22 PM
Switched Nics, new NIC has old driver, how to reinstall driver? Passive Linux - Hardware 3 04-29-2002 06:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 12:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration