Am 12.11.2010 23:31, schrieb Stefan G. Weichinger:
Am 12.11.2010 22:12, schrieb Etaoin Shrdlu:
On Fri, 12 Nov 2010 21:01:50 + Etaoin Shrdlushr...@unlimitedmail.org
wrote:
Also modprobe -k
I obviously meant lspci -k, though probably rereading the question, it's
not what he wanted.
Am 15.11.2010 10:39, schrieb Steffen Loos:
Maybe a little bit late but:
As a summary-tool all the info is gattered and shown by lshw.
yep, thanks.
Although it should be possible to just ask the kernel somehow, shouldn't it?
On Mon, Nov 15, 2010 at 12:35:35PM +0100, Stefan G. Weichinger wrote:
Am 15.11.2010 10:39, schrieb Steffen Loos:
Maybe a little bit late but:
As a summary-tool all the info is gattered and shown by lshw.
yep, thanks.
Although it should be possible to just ask the kernel somehow,
Maybe stupid question:
How to find out which physical NIC is for example eth0 ?
If I have 2 NICs in the box, for example one e1000 and one from 3com,
how to find out which one is eth0 ?
I looked up /etc/udev/rules.d/70-persistent-net.rules where the MAC is
determining the devicefile ...
Is
I usually do one of two things. Depending on the situation.
If both NICs are from the same vendor I install mii-tool and only plug in
one port. mii-tool will show link state. This when it negotiates it will
show output like:
eth0: negotiated 1000baseT-FD flow-control, link ok
eth1: no link
If
On Fri, Nov 12, 2010 at 10:51 AM, Stefan G. Weichinger li...@xunil.at wrote:
How to find out which physical NIC is for example eth0 ?
If I have 2 NICs in the box, for example one e1000 and one from 3com,
how to find out which one is eth0 ?
I looked up
Am 12.11.2010 17:41, schrieb Tom H:
Is there another way? on non-udev-systems?
dmesg | grep ethX
I looked that up, there was nothing!
Could be that I someday back then did a dmesg -c (I have an issue on
that server that triggered quite many lines in dmesg).
Thanks, S
Am 12.11.2010 16:57, schrieb Colt Jones:
I usually do one of two things. Depending on the situation.
If both NICs are from the same vendor I install mii-tool and only plug
in one port. mii-tool will show link state. This when it negotiates it
will show output like:
eth0: negotiated
On Fri, 12 Nov 2010 16:51:58 +0100 Stefan G. Weichinger li...@xunil.at
wrote:
Maybe stupid question:
How to find out which physical NIC is for example eth0 ?
If I have 2 NICs in the box, for example one e1000 and one from 3com,
how to find out which one is eth0 ?
I looked up
Am 12.11.2010 18:51, schrieb Etaoin Shrdlu:
mii-tool -w eth0
Also look at ethtool -p (details in the man page).
Yep, thanks. Maybe I haven't explained exactly what I mean:
I want to somehow find out the relation between loaded kernel-module and
ethernet-devicefile. Without physical access
On Fri, Nov 12, 2010 at 21:14, Stefan G. Weichinger li...@xunil.at wrote:
I want to somehow find out the relation between loaded kernel-module and
ethernet-devicefile. Without physical access ...
In another way: Which kernel-module is in use for /dev/ethX ?
# ethtool -i eth1
driver:
On Fri, 12 Nov 2010 22:31:09 +0200 Fatih Tümen fthtmn+gen...@gmail.com
wrote:
On Fri, Nov 12, 2010 at 21:14, Stefan G. Weichinger li...@xunil.at
wrote:
I want to somehow find out the relation between loaded kernel-module and
ethernet-devicefile. Without physical access ...
In another
On Fri, 12 Nov 2010 21:01:50 + Etaoin Shrdlu shr...@unlimitedmail.org
wrote:
Also modprobe -k
I obviously meant lspci -k, though probably rereading the question, it's
not what he wanted.
Am 12.11.2010 22:12, schrieb Etaoin Shrdlu:
On Fri, 12 Nov 2010 21:01:50 + Etaoin Shrdlu shr...@unlimitedmail.org
wrote:
Also modprobe -k
I obviously meant lspci -k, though probably rereading the question, it's
not what he wanted.
Thanks to all of you, I think I got it now!
14 matches
Mail list logo