I've just installed AntiX and can't get my WLAN working. Although System Information shows the WLAN card (Atheros AR2413/2414 - AR5005G(S) PCMCIA card) and says state: down, as it does for the unconnected Ethernet, wpa_gui doesn't list any adapters in the dropdown so I can't scan for networks.
RutilT WLAN Manager just opens tons of error boxes saying"Can't get frequency channel. Error 22" until the screen is full of them and I can't get rid of them!
Wicd just says"No Wireless networks found".
topic title: WLAN not working
4 posts
• Page 1 of 1
-
dovemanPosts: 14
- Joined: 05 Sep 2012
-
dovemanPosts: 14
- Joined: 05 Sep 2012
#3
No, I didn't see that. I'll go and try that, thanks.
-
masinickPosts: 1,139
- Joined: 26 Apr 2008
#4
That said, the wireless network interface on the vast majority of systems is now wlan0. In the past, sometimes it would be eth1, sometimes it would be wlan0, and on rare occasions, it would be something else. The information in the /proc file system ought to be sufficient for wicd to figure this out.
I'll see if I can find a wicd developer's forum or a place to make a feature request, and if so, I will make this suggestion to them. If anyone is clever enough in the meantime to write a script to scan for network devices and configure them in wicd (maybe even using the language and routines used in wicd, perhaps sending the wicd team a patch with the suggested coding change would get us this feature sooner rather than later). Alas, I have design ideas, but my coding techniques are not as sharp as they once were; not sure I'd know how to code this change, otherwise I'd gladly do it!
Yeah, wicd is great, and it is my preferred network manager, especially for wireless connections, but the one thing the developers could do to improve it would be to detect which network interfaces are present and at least attempt to configure them for the majority of use cases, and still allow the user to change any setting, including the network interfaces.Dave wrote:i am not sure how to use the first 2 wireless connection managers, but for wicd did you add wlan0 (or whatever card id you have) to the preferances -->wireless interface?
That said, the wireless network interface on the vast majority of systems is now wlan0. In the past, sometimes it would be eth1, sometimes it would be wlan0, and on rare occasions, it would be something else. The information in the /proc file system ought to be sufficient for wicd to figure this out.
I'll see if I can find a wicd developer's forum or a place to make a feature request, and if so, I will make this suggestion to them. If anyone is clever enough in the meantime to write a script to scan for network devices and configure them in wicd (maybe even using the language and routines used in wicd, perhaps sending the wicd team a patch with the suggested coding change would get us this feature sooner rather than later). Alas, I have design ideas, but my coding techniques are not as sharp as they once were; not sure I'd know how to code this change, otherwise I'd gladly do it!