Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12203 - [init-scripts][netcfg2] SIOCGMIIPHY on 'eth0' failed: Invalid argument

Attached to Project: Arch Linux
Opened by Mariusz GliwiƄski (shd) - Saturday, 22 November 2008, 00:21 GMT
Last edited by James Rayner (iphitus) - Monday, 16 February 2009, 11:00 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To James Rayner (iphitus)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After each boot-up with netcfg profiles set without link (ifconfig eth0 | grep RUNNING) I still have to wait for dhcp fail. It's very annoying so I decided to dig into. The reason of fail lays in /usr/lib/network/ethernet.subr: mii_check() which doesn't catch "no link" well. The reason is that mii-tool returns errors like
SIOCGMIIPHY on 'eth0' failed: Invalid argument

in case of interface is down (which is surely down at bootup time). Every next instruction fails then because of:

if echo $conn_state|grep "no link" &> /dev/null; then
#if
return 1
#fi
fi
return 0

Fixup:
The one of fixup schemas could be just ifconfig $INTERFACE up in network.subr or even better search for positive nor negative "no link". I'll recommend to add
PRE_UP="ifconfig $INTERFACE up"

in your each /etc/network.d/`profile-name` until clean fixup will be done.

Additional info:
* netcfg 2.1.2-1


Steps to reproduce:
Add profile to NETWORKS=() which configures unlinked interface such as not connected ether. Then reboot (i won't mention about DAEMONS(net-profiles)) and look that you have to wait until dhcp fails. Now try to add PRE_UP="ifconfig $INTERFACE up" into your profile and reboot one more time. Now you can see appropriate behaviour - fast "No connection available" message.
This task depends upon

Closed by  James Rayner (iphitus)
Monday, 16 February 2009, 11:00 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Sunday, 23 November 2008, 11:04 GMT
Why do we use mii-tool to check link status, doesn't "ip link" provide us with more generic ways of detecting link status? Not every interface is compatible with mii-tool.
Comment by James Rayner (iphitus) - Monday, 16 February 2009, 11:00 GMT
netcfg in git uses ip link.

Loading...