Peter Chubb said:
as root, do
lspci -v
It'll tell you which driver module is associated with each PCI device.
Bikeshed issue, but can I suggest:
$ lspci -k
It also shows what kernel module is associated with the device, but
without all the other verbose fluff.
Case in point, this:
I know you found the answer already but ethtool -i interface can also work
and is very simple
Just thought I'd throw that in :)
On 14/02/2011, at 1:12 PM, DaZZa dagi...@gmail.com wrote:
On Mon, Feb 14, 2011 at 11:57 AM, Peter Hardy
pe...@hardy.dropbear.id.au wrote:
And in case this hasn't
On Mon, Feb 14, 2011 at 7:40 PM, Tony Sceats tony.sce...@gmail.com wrote:
I know you found the answer already but ethtool -i interface can also work
and is very simple
Just thought I'd throw that in :)
[root@dev-app01 ~]# ethtool -i seth0
Cannot get driver information: Operation not
On Monday 14 February 2011 12:01:57 DaZZa wrote:
snip
So, what's an seth0 device, and how do I get one? :-)
DaZZa
Perhaps ...
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551
might give a clue. It mentions Driver support for synthetic devices:
You can try to get the information from the sysfs.
[rmtzcx@armtzcx01 ~]$ ls -l /sys/class/net/{eth0,wlan0}/device/driver
lrwxrwxrwx 1 root root 0 Feb 14 19:54
/sys/class/net/eth0/device/driver - ../../../bus/pci/drivers/e1000e
lrwxrwxrwx 1 root root 0 Feb 14 19:02
Learned folks...
Can someone shed some light for me on finding which kernel module is
loaded/providing the eth0 interface?
Scenario: I have a several virtual machines in a test/developement
environment on a Microsoft HyperV (don't ask - just...don't!) server.
One box (dev) is built on CentOS
DaZZa == DaZZa dagi...@gmail.com writes:
DaZZa Learned folks... Can someone shed some light for me on finding
DaZZa which kernel module is loaded/providing the eth0 interface?
as root, do
lspci -v
It'll tell you which driver module is associated with each PCI device.
--
Dr Peter Chubb
Just in case you've got a usb device, or other hardware type device...
Running lshw as root (eg: sudo lshw), will provide you with the driver
name as well as most everything else.
Chris-
On Mon, Feb 14, 2011 at 11:23 AM, Peter Chubb peter.ch...@nicta.com.au wrote:
DaZZa == DaZZa
On Mon, Feb 14, 2011 at 11:23 AM, Peter Chubb peter.ch...@nicta.com.au wrote:
DaZZa == DaZZa dagi...@gmail.com writes:
DaZZa Learned folks... Can someone shed some light for me on finding
DaZZa which kernel module is loaded/providing the eth0 interface?
as root, do
lspci -v
It'll tell
And in case this hasn't been answered enough, yet, the kernel module
itself should log the interfaces it's handling when it loads. That will
turn up in the kernel logs (RH places kernel logs from the last boot
in /var/log/dmesg , or it'll be in /var/log/messages , or just run
`dmesg`); just grep
On Monday 14 February 2011 11:23:54 Peter Chubb wrote:
DaZZa == DaZZa dagi...@gmail.com writes:
DaZZa Learned folks... Can someone shed some light for me on finding
DaZZa which kernel module is loaded/providing the eth0 interface?
as root, do
lspci -v
It'll tell you which driver
Can someone shed some light for me on finding which kernel module is
loaded/providing the eth0 interface?
lsmod
dmesg | grep eth
HTH
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
On Mon, Feb 14, 2011 at 11:57 AM, Peter Hardy
pe...@hardy.dropbear.id.au wrote:
And in case this hasn't been answered enough, yet, the kernel module
itself should log the interfaces it's handling when it loads. That will
turn up in the kernel logs (RH places kernel logs from the last boot
in
13 matches
Mail list logo
