BIGtec WLAN USB Stick install - problems with drivers rt73usb
I have some time ago a WLAN USB Stick BIGtec / Belkin purchased because I wanted to bring my computer via wireless to the router to the Internet and the use of this stick Ralink chipset very "Linux friendly". At the time of purchase there was an open source driver project and now the driver is moved in the kernel, ie at any modern distribution included. stick inserted so pure and behold, the knetworkmanager tells me that the wlan0 interface is added, great! When trying to connect with the router, but is no error message, however, is always "not connected" message and a ping is unsuccessful. Crap!
a look with dmesg
reveals that attempts to load the rt2500 module and it goes wrong, as expected, there is installed on the stick in chipset, which requires the rt73usb module. The solution: The rt2500 module - and if one is already times, all "similar" modules that control the Ralink chipsets - blacklist, making it by modprobe is not loaded. Here's the comment on my / etc / modprobe.d / blacklist.conf
:
Saturday, May 2, 2009
How Much Are Tickets Cineplex Tuesday
# blacklist for rt73usb WLAN stick 
blacklist rt2570
blacklist rt2500usb
blacklist rt2x00usb
In the future, just load the module and thus rt73usb the stick works fine, fast and very stable. My stick is identified by the way this:
lsusb-v
bLength 18
As you can see, is under the ID RT2501USB suspected chipset, but as mentioned above not already correct. Where was this is the problem, ie, whether registered in either the kernel sources for the wrong chipset that ID or WLAN USB sticks actually exist in the market to which it is vendor and device ID and use a RT2501USB chipset, I do not know. In the latter case, the fault would be the manufacturer.
it actually is because the manufacturer Sch ... built and has found same IDs with different chipsets, so that the appropriate module can not be determined automatically.
If I used the stick to a stationary PC, which anyway only to the same wireless network links, should dispense with the knetworkmanager and the whole story of
This is the first network-manager packages
,
network-manager-gnome and remove
network-manager-kde and install the package wpasupplicant .
order the password to connect in the clear of having to write purely in the configuration file, it means
wpa_passphrase MeineSSID MeinSchluessel
be converted to hexadecimal. Subsequently
the file / etc / wpa_supplicant / wpa_supplicant.conf
created (with root rights, mask-0600) and filled: ctrl_interface = / var / run / wpa_supplicant
eapol_version = 1
# 0: The driver of the interface takes care of the scanning of networks and the AP selection.
# This Mode should be used if you put an encryption on a cable network.
Depending on encryption have some options
the whole is wpa_supplicant-i wlan0 with
iwconfig
.
/ etc / network / interfaces
, so that the connection can be established already at boot time:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
iface wlan0 inet dhcp
From now on, the connection is independent of KDE, which can often be of advantage to such times in the text mode a file via Download wget needs.
blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib rt73 blacklist In the future, just load the module and thus rt73usb the stick works fine, fast and very stable. My stick is identified by the way this:
lsusb-v
Bus 001 Device 002: ID 148f: 2573 Ralink Technology, Corp.. RT2501USB Wireless Adapter Device Descriptor: bLength 18
bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x148f Ralink Technology, Corp. idProduct 0x2573 RT2501USB Wireless Adapter bcdDevice 0.01 iManufacturer a Ralink iProduct 2 802.11 bg WLAN iSerial 0 bNumConfigurations a As you can see, is under the ID RT2501USB suspected chipset, but as mentioned above not already correct. Where was this is the problem, ie, whether registered in either the kernel sources for the wrong chipset that ID or WLAN USB sticks actually exist in the market to which it is vendor and device ID and use a RT2501USB chipset, I do not know. In the latter case, the fault would be the manufacturer.
UPDATE (07:05:09): According Ubuntu bug tracker (see comment from Ben Hutchings) it actually is because the manufacturer Sch ... built and has found same IDs with different chipsets, so that the appropriate module can not be determined automatically.
If I used the stick to a stationary PC, which anyway only to the same wireless network links, should dispense with the knetworkmanager and the whole story of
wpa_supplicant can take over. This is the first network-manager packages
,
network-manager-gnome and remove
network-manager-kde and install the package wpasupplicant .
order the password to connect in the clear of having to write purely in the configuration file, it means
wpa_passphrase MeineSSID MeinSchluessel
be converted to hexadecimal. Subsequently
the file / etc / wpa_supplicant / wpa_supplicant.conf
created (with root rights, mask-0600) and filled: ctrl_interface = / var / run / wpa_supplicant
eapol_version = 1
# 0: The driver of the interface takes care of the scanning of networks and the AP selection.
# This Mode should be used if you put an encryption on a cable network.
# 1: wpa_supplicant take care of the scanning of networks and the AP selection. # 2: Almost like 0, but it will help with security policies and connected to the AP's SSID (BSSID is not supported) does # # Normally, either mode 1 or mode 2 ap_scan = 1 network = {ssid = "MeineSSID" here comes the SSID name purely scan_ssid = 1 proto = WPA key_mgmt = WPA-PSK # pairwise = TKIP # group = TKIP psk = 2a6aa # here comes the key in hex umgewantelte purely } Depending on encryption have some options
be adjusted. Tested the whole is wpa_supplicant-i wlan0 with
-c / etc / wpa_supplicant / wpa_supplicant.conf-d and iwconfig
.
Did you get everything you wear has a place in the wpa_supplicant / etc / network / interfaces
, so that the connection can be established already at boot time:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto wlan0 iface wlan0 inet dhcp
wpa-conf / etc / wpa_supplicant / wpa_supplicant.conf From now on, the connection is independent of KDE, which can often be of advantage to such times in the text mode a file via Download wget needs.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment