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#15656 - [netcfg] Update to 2.2.1 causes connection failure
Attached to Project:
Arch Linux
Opened by Cody A. Taylor (code_m) - Thursday, 23 July 2009, 19:15 GMT
Last edited by James Rayner (iphitus) - Saturday, 30 January 2010, 23:42 GMT
Opened by Cody A. Taylor (code_m) - Thursday, 23 July 2009, 19:15 GMT
Last edited by James Rayner (iphitus) - Saturday, 30 January 2010, 23:42 GMT
|
DetailsDescription: I have two laptops, one i686, one x86_64, but both use netcfg and ndiswrapper to connect to wifi.
After the last system upgrades, both had netcfg go from 2.1.3 to 2.2.1 and they both stopped connecting. I tried both static and dynamic IPs, but failure to connect. I downgraded to 2.1.3 and everything worked again (and that was the only change) Additional info: Downgrade of netcfg 2.2.1 -> 2.1.3 fixed issues Steps to reproduce: 1. pacman -Syu 2. netcfg profile <!-- FAIL --> 3. pacman -U /var/cache/pacman/pkg/netcfg-2.1.3-3-i686.pkg.tar.gz 4. netcfg profile <!-- SUCESS --> |
This task depends upon
Closed by James Rayner (iphitus)
Saturday, 30 January 2010, 23:42 GMT
Reason for closing: No response
Additional comments about closing: probably fixed - no response to confirm the applied fix.
Saturday, 30 January 2010, 23:42 GMT
Reason for closing: No response
Additional comments about closing: probably fixed - no response to confirm the applied fix.
But once booted, I just do:
sudo netcfg -a
sudo netcfg <wired profile name>
for some reason the wireless profiles connect at boot.
The problem could also be seen here, http://bbs.archlinux.org/viewtopic.php?id=74887
Post #11 shows this problem with a "sleep 2" solution, I don't know if that is an ideal solution though.
- copy of your profile
- exact output of netcfg (this one is incredibly important, even if only 1 line)
/etc/network.d/profile:
-------------------------------------------------------------------
CONNECTION="wireless"
DESCRIPTION="A wep encrypted wireless connection using dhcp"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wep"
ESSID="-------------------"
KEY="s:-----"
IP="dhcp"
TIMEOUT=180
-------------------------------------------------------------------
I have tryed removing "SCAN", and "TIMEOUT" but had no luck.
stderr (this is a guess, as the one I'm using just stalls and does not
give errors):
-------------------------------------------------------------------
:: wireless up [BUSY]
-wireless assosiation failed {FAIL]
-------------------------------------------------------------------
... I'm sorry that isn't more helpful, but I'm not real good with bash,
now if it were python...
Also, I have changed my x86_64 machine to broadcom-wl, and 2.2.1 works there. Unfortionally, ndiswrapper has completely broken (at least it did for me, but I haven't found anyone else, and there didn't seem to be a reason). However my i686 machine is still using ndiswrapper, and still not able to connect with 2.2.1 ... Maybe the problem lies with ndiswrapper ?