So I got these two wireless devices and it would be great to get at least one of them running. Though YAST (openSUSE 12.1) seems to find them, I wasn’t able to connect. Any help about what I’m missing here very much appreciated!
/usr/bin/lsusb
Bus 001 Device 005: ID 148f:2570 Ralink Technology, Corp. RT2570 Wireless Adapter
Bus 001 Device 007: ID 0bc7:0006 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
dmesg
9.482602] input: X10 Wireless Technology Inc USB Receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.3/input/input6
9.796546] usbcore: registered new interface driver zd1211rw
10.108004] usbcore: registered new interface driver rt2500usb
10.576875] ifup[773]: Service network not started and mode 'auto' -> skipping
10.580903] ifup[777]: Service network not started and mode 'auto' -> skipping
230.237408] zd1211rw 1-7:1.0: firmware version 4725
230.277412] zd1211rw 1-7:1.0: zd1211b chip 1582:6003 v4810 high 00-11-f6 AL2230_RF pa0 g--N-
1183.640547] usb 1-7: Product: USB2.0 WLAN
1183.640550] usb 1-7: Manufacturer: ZyDAS
1183.860549] zd1211rw 1-7:1.0: phy2
/usr/sbin/iwconfig
wlan1 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
sudo /usr/sbin/iwlist scan
wlan1 Interface doesn't support scanning : Network is down
wlan0 Scan completed :
Cell 02 - Address: BC:05:43:12:8C:99
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=52/100 Signal level=52/100
Encryption key:on
ESSID:"Saustall"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000003b354ff85e
Extra: Last beacon: 98ms ago
Using the CODE tags around the computer text is fine. Thank you. But it can still be done more efficient (for you and us) when you copy/paste including the prompt and the command. You do not need to type the command outside the CODE box (and no need to make it bold).
And what we see is that both devicces are recocnised by the system and got names wlan0 and wlan1. Scanning shows that wlan1 even sees a Wifi access point (Saustall, I do not know if I would like to enter there wiyjout high boots and overalls ).
Now what is you problem? It is there and it works.
You do not say you use a desktop. When yes, please tell us which one (KDE, Gnome, …).
You also do not say if you want to connect to Saustall permanently (from boot to shutdow, using* ifup*) or if this is a t"traveling" system (like a laptop) where you want to access all sorts of access points. In the last case, use Network manager from the desktop you use.
Thank you for your comments. I’ll try and keep that in mind. I’m using KDE on a desktop computer and I want to connect to my Saustall permanently. The problem is that although the devices are detected I was unable to connect to the AP neither via Yast and ifup nor the Network Manager, both of which didn’t recognise any wireless networks in their environment.
In the meantime I got some idea about what’s wrong with the RaLink:
linux-ask7:/home/ktobi # ifup wlan1
wlan1 name: 802.11g WiFi
wlan1 starting wpa_supplicant
Could not set interface wlan1 flags: Operation not possible due to RF-kill
Could not set interface 'wlan1' UP
Failed to initialize driver interface
DHCP6 client is already running on wlan1
RTNETLINK answers: Operation not possible due to RF-kill
Starting DHCP4 client on wlan1. .
wlan1 DHCP4 client NOT running
wlan1 DHCP6 continues in background
RTNETLINK answers: Operation not possible due to RF-kill
Cannot enable interface wlan1.
interface wlan1 is not up
linux-ask7:/home/ktobi # rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: phy1: Wireless LAN
Soft blocked: no
Hard blocked: yes
So since it seems to be hard blocked and there’s no actual switch this is hopeless, right? I might have to turn to the other device, which is a no-name-stick possibly missing some firmware…?!
> So since it seems to be hard blocked and there’s no actual switch this
> is hopeless, right? I might have to turn to the other device, which is a
> no-name-stick possibly missing some firmware…?!
No, it is not hopeless for the Ralink device. If you really do not have an
rfkill switch, then you need to blacklist the driver for that second device
(Zydas?).
Thanks, I’ll keep that in mind. It’s just that, five minutes ago the Zydas device miraculously decided to start working after all. I don’t know what did the trick, the only thing I did before was delete the other network devices in Yast and remove the wicd program that I installed today but didn’t work.
So again, thanks and sorry to bother you guys. I don’t know much about this stuff and I’m just grateful it’s working now.
).