From: Ben Hutchings <bhutchings@solarflare.com>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: 3.0.0rc6: ethtool not working without a cable
Date: Wed, 06 Jul 2011 15:28:04 +0100 [thread overview]
Message-ID: <1309962484.4280.25.camel@localhost> (raw)
In-Reply-To: <201107061338.08573.a.miskiewicz@gmail.com>
On Wed, 2011-07-06 at 13:38 +0200, Arkadiusz Miskiewicz wrote:
> 3.0.0rc6, thinkpad t400 notebook.
>
> If there is no cable then ethtool reports no device. It wasn't that before
> AFAIK.
>
> ethtool version 2.6.36
>
>
> cable disconnected:
>
> [root@t400 ~]# ethtool eth0
> Settings for eth0:
> Cannot get device settings: No such device
> Cannot get wake-on-lan settings: No such device
> Cannot get message level: No such device
> Cannot get link status: No such device
> No data available
> zsh: exit 75 ethtool eth0
> [root@t400 ~]# ethtool -i eth0
> Cannot get driver information: No such device
> zsh: exit 71 ethtool -i eth0
[...]
Then there really isn't a device under that name. Maybe the driver is
getting a bogus MAC address, so that the device is renamed by udev.
Check which devices do exist, and the MAC addresses they have, using 'ip
link'.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-07-06 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 11:38 3.0.0rc6: ethtool not working without a cable Arkadiusz Miskiewicz
2011-07-06 14:28 ` Ben Hutchings [this message]
2011-07-06 14:53 ` Arkadiusz Miskiewicz
2011-07-06 15:26 ` Ben Hutchings
2011-07-06 16:52 ` Brandeburg, Jesse
2011-07-06 16:57 ` Arkadiusz Miskiewicz
2011-07-07 16:47 ` Arkadiusz Miskiewicz
2011-07-07 17:03 ` Ben Hutchings
2011-07-20 17:53 ` Brandeburg, Jesse
2011-07-20 17:57 ` Arkadiusz Miskiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1309962484.4280.25.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=a.miskiewicz@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.