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!
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!
FS#16508 - [netcfg] 2.2.1 causes connection failure on boot
Attached to Project:
Arch Linux
Opened by steve (steve___) - Wednesday, 07 October 2009, 22:54 GMT
Last edited by James Rayner (iphitus) - Saturday, 30 January 2010, 23:41 GMT
Opened by steve (steve___) - Wednesday, 07 October 2009, 22:54 GMT
Last edited by James Rayner (iphitus) - Saturday, 30 January 2010, 23:41 GMT
|
DetailsDescription: After upgrading to netcfg 2.2.1 the network failed to come
up with an error 'No Connection' on boot. Once booted I would '/etc/rc.d/net-profiles restart' and the network would come up. I added this to /etc/rc.local until I had time to dig into it. Today I was reading this thread: http://bbs.archlinux.org/viewtopic.php?id=79685 I changed the sleep value on line 22 to 2,5,10 and 60 with no result. I removed v2.2.1 and installed v2.1.3 and it worked. Additional info: * package version(s) v2.1.3 * config and/or log files etc. # cat /etc/network.d/ethernet CONNECTION="ethernet" DESCRIPTION="A very basic ethernet profile, using dhcp" INTERFACE=eth0 IP="dhcp" DHCP_TIMEOUT=10 DHCLIENT="yes" # lspci |grep ethernet 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 22) Which uses the 'sky2' module. |
This task depends upon
Closed by James Rayner (iphitus)
Saturday, 30 January 2010, 23:41 GMT
Reason for closing: No response
Additional comments about closing: probably fixed - no response to confirm the applied fix.
Saturday, 30 January 2010, 23:41 GMT
Reason for closing: No response
Additional comments about closing: probably fixed - no response to confirm the applied fix.
Comment by James Rayner (iphitus) -
Wednesday, 18 November 2009, 03:00 GMT
Please try with 2.5.0rc1 in [testing]