Skip to contentSkip to conversation

network interface to driver and pci slot mapping

DISCUSSION Anthony Samsung 6 participants 6 messages Nov 11, 2004 – Nov 12, 2004

lore
Share & tools
lore
#0 lore raw

Given an interface name (like eth0), how do I determine:
The name of the driver (module) for this interface. The PCI address for this interface, if relevant.

?

I need something that works non-destructively on a live system, that isn't broken by nameif, and has a strong chance of producing a correct result. In particular, parsing syslog is out. There's no consistency in the format of messages and there's no guarantee the logs from bootup will still be around. And the interface may have been renamed since then.

#1 lore raw
Quoted 4 lines · Anthony Samsung

Given an interface name (like eth0), how do I determine:
The name of the driver (module) for this interface. The PCI address for this interface, if relevant.

Quoted 8 lines

?

I need something that works non-destructively on a live system, that isn't broken by nameif, and has a strong chance of producing a correct result. In particular, parsing syslog is out. There's no consistency in the format of messages and there's no guarantee the logs from bootup will still be around. And the interface may have been renamed since then.

If the eth0 device is a module, it's in /etc/modprobe.conf, previous versions used /etc/modules.conf.
Once you have its module name you can use other resources like

/sys/bus/pci/drivers/MODULENAME

Cheers,
Dick Johnson
Penguin : Linux version 2.6.9 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by John Ashcroft.
98.36% of all statistics are fiction.

#2 lore raw
Quoted 5 lines · linux-os

If the eth0 device is a module, it's in /etc/modprobe.conf, previous versions used /etc/modules.conf.
Once you have its module name you can use other resources like

/sys/bus/pci/drivers/MODULENAME

On my systems, hotplug loads the modules automatically, so there is no mention of them anywhere.

Signature · 2 lines
Måns Rullgård
[email protected]
#3 lore raw
Quoted 7 lines · Måns Rullgård
Quoted 4 lines · linux-os

If the eth0 device is a module, it's in /etc/modprobe.conf, previous versions used /etc/modules.conf.
Once you have its module name you can use other resources like

Quoted 5 lines
Quoted 1 line

/sys/bus/pci/drivers/MODULENAME

On my systems, hotplug loads the modules automatically, so there is no mention of them anywhere.

Use ethtool.

Jeff

#4 lore raw
In reply to Anthony Samsung
Quoted 3 lines · Anthony Samsung

Given an interface name (like eth0), how do I determine:
The name of the driver (module) for this interface. The PCI address for this interface, if relevant.

Use sysfs. All of this information is there (well, the driver link back to the module isn't there for most PCI drivers, but the functionality is there if the drivers are modified to support it...)

thanks,

greg k-h

#5 lore raw
Quoted 8 lines · Greg KH
Quoted 3 lines · Anthony Samsung

Given an interface name (like eth0), how do I determine:
The name of the driver (module) for this interface. The PCI address for this interface, if relevant.

Use sysfs. All of this information is there (well, the driver link back to the module isn't there for most PCI drivers, but the functionality is there if the drivers are modified to support it...)

If you're going to use sysfs, libsysfs can help. It can be found in the sysfsutils package here:

http://linux-diag.sourceforge.net/Sysfsutils.html

[stekloff@... stekloff]$ systool -c net eth0 -D
Class = "net"

Class Device = "eth0"

    Device = "0000:02:01.0"
    Driver = "e1000"
      Devices using "e1000" are:
        Device = "0000:02:01.0"

And more extended output:

[stekloff@... stekloff]$ systool -c net eth0 -v
Class = "net"

Class Device = "eth0"
Class Device path = "/sys/class/net/eth0"

    addr_len            = "6"
    address             = "00:0d:60:c9:42:06"
    broadcast           = "ff:ff:ff:ff:ff:ff"
    features            = "0x3a9"
    flags               = "0x1002"
    ifindex             = "6"
    iflink              = "6"
    mtu                 = "1500"
    tx_queue_len        = "1000"
    type                = "1"
    Device = "0000:02:01.0"
    Device path = "/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0"
      class               = "0x020000"
      config              =  86 80 1e 10 17 01 30 02  03 00 00 02 08 40
00 00
                             00 00 24 c0 00 00 20 c0  01 80 00 00 00 00
00 00
                             00 00 00 00 00 00 00 00  22 00 00 00 14 10
49 05
                             00 00 00 00 dc 00 00 00  00 00 00 00 0b 01
ff 00
      detach_state        = "0"
      device              = "0x101e"
      irq                 = "11"
      resource            = "0x00000000c0240000 0x00000000c025ffff

0x0000000000000200
0x00000000c0200000 0x00000000c020ffff 0x0000000000000200 0x0000000000008000 0x000000000000803f 0x0000000000000101 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x000000000000ffff 0x0000000000007200"

      subsystem_device    = "0x0549"
      subsystem_vendor    = "0x1014"
      vendor              = "0x8086"
    Driver = "e1000"
    Driver path = "/sys/bus/pci/drivers/e1000"
      new_id              = <store method only>
 
      Devices using "e1000" are:
        "0000:02:01.0"

Thanks,

Dan