Bug#503738: Correction: possibly an mii-tool bug
Josh Triplett
Followup-For: Bug #503738
mii-tool doesn't seem to detect link correctly on my system. With no
wire connected:
$ sudo mii-tool eth0
SIOCGMIIREG on eth0 failed: Input/output error
SIOCGMIIREG on eth0 failed: Input/output error
eth0: negotiated 100baseTx-FD flow-control, link ok
If it helps, my wired card uses the e1000e driver.
ethtool seems to work correctly:
$ sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: Unknown! (65535)
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbag
Wake-on: g
Current message level: 0x00000001 (1)
Link detected: no
However, wicd doesn't seem to obey the setting that tells it to use
ethtool explicitly rather than mii-tool (reported as bug 503745), so I
can't seem to force it to use ethtool.
if bug 503745 gets fixed, and making wicd use ethtool fixes my
problem, then this bug does not lie with wicd; however, wicd might
still want to use a more reliable mechanism for link detection. If
using ethtool does not fix the problem, then this bug still applies.
- Josh Triplett
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.27-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wicd depends on:
ii python 2.5.2-2 An interactive high-level object-o
ii python-dbus 0.83.0-1 simple interprocess messaging syst
ii python-glade2 2.12.1-6 GTK+ bindings: Glade support
ii python-gtk2 2.12.1-6 Python bindings for the GTK+ widge
ii python-support 0.8.6 automated rebuilding support for P
ii wireless-tools 29-1.1 Tools for manipulating Linux Wirel
ii wpasupplicant 0.6.4-2 Client support for WPA and WPA2 (I
wicd recommends no packages.
wicd suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Josh Triplett
> On Mon, 27 Oct 2008 17:21:08 -0700, Josh Triplett wrote:
> > mii-tool doesn't seem to detect link correctly on my system. With no
> > wire connected:
> >
> > $ sudo mii-tool eth0
> > SIOCGMIIREG on eth0 failed: Input/output error
> > SIOCGMIIREG on eth0 failed: Input/output error
> > eth0: negotiated 100baseTx-FD flow-control, link ok
>
>
> > If it helps, my wired card uses the e1000e driver.
>
>
> > ethtool seems to work correctly:
> >
> > $ sudo ethtool eth0
> > Settings for eth0:
>
>
> This seems like the best environment to do bug triaging! ;)
Yeah. :)
> > However, wicd doesn't seem to obey the setting that tells it to use
> > ethtool explicitly rather than mii-tool (reported as bug 503745), so I
> > can't seem to force it to use ethtool.
>
> I've set that to "Automatic".
Yeah, I started with it set to Automatic.
> > if bug 503745 gets fixed, and making wicd use ethtool fixes my
> > problem, then this bug does not lie with wicd; however, wicd might
> > still want to use a more reliable mechanism for link detection. If
> > using ethtool does not fix the problem, then this bug still applies.
>
> With "Automatic" set, I've just plugged in my eth cable: wicd switched to the
> wired network. I plugged the cable off, and it went to my wifi again. This is
> the expected behaviour, I suppose! :)
>
> Please, try these same steps with link detection set to "Automatic".
I originally tried these steps with link detection set to "Automatic"; I
only tried changing it to see if that would fix the problem.
If I plug in a wire, wicd doesn't notice; it just stays on wireless. If
I manually switch it to wired, it does connect. If I then unplug the
wire, wicd doesn't notice.
- Josh Triplett
David Paleino
thanks
Hello Josh,
On Tue, 04 Nov 2008 12:25:51 -0800, Josh Triplett wrote:
> If I plug in a wire, wicd doesn't notice; it just stays on wireless. If
> I manually switch it to wired, it does connect. If I then unplug the
> wire, wicd doesn't notice.
I just tried. I'm on wifi, plugged in the wire, it switched to "Wired network".
Unplugged it, it was back on wifi.
Marking this bug as fixed in 1.5.9-1, please try installing it (see
NEWS.Debian!) and report back if you're still having issues.
Ciao,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174