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#13569 - netcfg-git will prevent computer from booting up when interface is not connected at boot

Attached to Project: Arch Linux
Opened by janis (Stalafin) - Friday, 27 February 2009, 06:10 GMT
Last edited by James Rayner (iphitus) - Tuesday, 28 April 2009, 12:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To James Rayner (iphitus)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Using the latest git today I experienced a very inconvenient behaviour: while being in class where I only have a wireless connection (there is no physical connection between ethernet and my computer, i.e. there is no cable) I was not able to start my computer. In my NETWORKS line in rc.conf I have listed my 'ethernet' profile, which is a basic DHCP profile (like the ones in network.d/examples before iproute was introduced), and in my DAEMONS line i have 'net-profiles'.

Booting my computer it got stuck in the boot screen, showing that it tried to connect to the ethernet, which was not accomplished, nor was there an error message. It got simply stuck, I never reached the shell.

I have never experienced this behaviour with netcfg v2.1.2 when I did not have a LAN cable connected to my computer.


I think this is a dire problem!

Additional info:
* package version(s)
lates netcfg-git
This task depends upon

Closed by  James Rayner (iphitus)
Tuesday, 28 April 2009, 12:45 GMT
Reason for closing:  Fixed
Comment by James Rayner (iphitus) - Sunday, 01 March 2009, 09:46 GMT
Not good!

Could you give me the output of:
ip link show $interface

with a cable plugged in, and without. No need to run dhcp when it's plugged in.

Also, default DHCP_TIMEOUT is 10 seconds, odd that it didn't timeout. Can you add DHCLIENT="no" to your profile and test again?

Thanks!
Comment by Paride Legovini (torn) - Wednesday, 04 March 2009, 05:38 GMT
I noticed the same thing, except that here it DID timeout as expected. For me (e1000e), the problem is that 'ip link show' reports NO-CARRIER only if the interface is UP. If it is DOWN or UNKNOWN, no such information is reported.

ethtool(8) is able to report if a cable is plugged even it the interface is down. But while the interface is down, it WON'T report is the cable gets unplugged (i.e. while the interface is down, if I plug and unplug a cable ethtool will report "Link detected: yes").

IMHO the better solution is just the set the interface UP before using 'ip link show'.

p.

Loading...