'Network is down' - 'ifconfig wlan1 up' first...
also make sure NetworkManager/wpa_supplicant are down, as they interfere with
manual operation like these - you should do *either* iwconfig/iwlist *or*
networkmanger/wpa_supplicant but not both.
--- On Sat, 30/1/10, Dani Gutiérrez
'Network is down' - 'ifconfig wlan1 up' first...
also make sure NetworkManager/wpa_supplicant are down, as they interfere
with manual operation like these - you should do *either* iwconfig/iwlist
*or* networkmanger/wpa_supplicant but not both.
Thanks for your hack-help. Now everything is ok
--- On Sat, 30/1/10, Dani Gutiérrez jdani...@gmail.com wrote:
'Network is down'
- 'ifconfig wlan1 up' first...
also make sure NetworkManager/wpa_supplicant are down, as
they interfere with manual operation like these - you should
do *either* iwconfig/iwlist *or*
It isn't that much of a hack - the ifconfig is fairly standard for manually
starting a network interface - if you go manual, you have to do
ifconfig/iwconfig/iwlist all the way.
Sure ifconfig is a very usual command. But in this thread I've learned that
is ifconfig who, in some usb cards,
Hi,
I'm trying to use a wifi usb device in Kubuntu Karmic (9.10). Info of
the hardware system:
* lsusb ID 083a:e501 Accton Technology Corp. ZD1211B
* dmesg: zd1211rw 2-2:1.0: zd1211 chip 083a:e501 v4810 high 00-1a-2a AL223
* uname -a: 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC
2009
Hmm, do you really need the echo part? current wireless-testing/compat-wireless
already have the 083a:e501 id.
--- On Sun, 10/1/10, Dani Gutiérrez jdani...@gmail.com wrote:
Hi,
I'm trying to use a wifi usb device in Kubuntu Karmic
(9.10). Info of
the hardware system:
* lsusb ID 083a:e501
Hmm, do you really need the echo part? current
wireless-testing/compat-wireless already have the 083a:e501 id.
Well, I didn't find that ID in http://linuxwireless.org/en/users/Devices/USB.
Also if I do
modinfo zd1211rw | grep -i 083a
it doesn't appear. Maybe my module is a little bit old?
Apparently it was me who added that ID to wireless-testing 6 months ago, and it
entered mainline kernel at 2.6.32. (not in 2.6.31). Sorry I don't have data on
2.6.31.x, but you probably should just upgrade to 2.6.32+ .
--
commit 8f75e07aa14107668d33f60fa4d78afa2d7aa22b
Author:
