You are not logged in.
Pages: 1
Hi, I am running arch64 with testing enabled and have troubles getting a wireless device to run: The device is a
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8192] (rev 01)
There are quite some threads (especially on the ubuntuforums) flying around how to get this card running. Especially it is suggested to obtain a (not-officially downloadable )driver provided by realtek - rtl8192e_linux_2.6.0013.0127.2010.tar.gz - and install it.
This procedure worked for me (kind of) for kernel 2.6.32.x since I was able to get the device up, scan for networks and even connect (sometimes at least) using netcfg-profiles. However, the connection was very unstable, slow and not barely useable.
Upgrading to kernel 2.6.33 from testing, it is not possible to install the driver provided by realtek any longer ("make" works, but "make install" fails). I know that in the staging directory of the kernel exists a module r8192e which _should_ provide the kernel module for this device. My questions: How can I build this staging module within an official arch-kernel? Can I download the source somewhere and compile it? I didn't find anything in the wiki.
The other question, has anyone else trouble with this device (module r8192e_pci, NOT r8192se_pci or r8192_pci) under 64 bit and has some suggestions what to try? Any help is very appreciated.
Offline
a bump.
i still did not manage to get this device up and working with x64_86 and latest updates. according to the wiki (http://wiki.archlinux.org/index.php/Wir … p#rtl8192e) it should work:
The driver is part of the current kernel package. It can be configured using the standard wpa_supplicant and iwconfig tools.
I can get the device up and can scan for networks,but i just can't connect (not with netcfg, wpa_supplicant directly, wicd, networkmanager,...) Has anyone had success with this device with 64 bit?
Offline
rtl8192se here. In AUR theres a package for the latest release. works for me perfectly.
Offline
hi itman, thx for your answer.
do you mean i should try the rtl8192se driver, even though the device is clearly stated as r8192e?
Offline
it may be worth a try...
modinfo states:
description: Linux driver for Realtek RTL819x WiFi cards
then copy manually the firmware-directory to /lib/firmware
I didn't find any description on realtek's site regarding the differences between 8192e and 8192se...
edit: nachtrag: http://www.linuxforen.de/forums/showthread.php?t=264331 may be of interest too.
Last edited by itman (2010-09-28 10:20:18)
Offline
yesterday I tried your suggestion by using the rtl8192se module. unfortunately, i wasn't even able to get the device up and scan for networks with this kernel module.
out of curiosity i fired up a i686 installation of arch which i had a fsarchiver-backup of. i did a complete system upgrade and inserted r8192e_pci. surprisingly, the device worked with my netcfg-profiles.
i reverted then to x64_86 and was not able to connect to my network. so this seems to be a 64-bit bug in the r8192e_pci module.
does anyone know where to file bugs against this module which resides in the staging tree of gkh? any hints are very appreciated!
Offline
Having the same problem with this device too ... x86_64 actually causes a kernel panic where i686 works flawlessly.
Bus 002 Device 002: ID 0bda:8171 Realtek Semiconductor Corp. RTL8188SU 802.11n WLAN Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x8171 RTL8188SU 802.11n WLAN Adapter
bcdDevice 2.00
iManufacturer 1 Manufacturer Realtek
iProduct 2 RTL8188S WLAN Adapter
iSerial 3 00e04c000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0d EP 13 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Offline
Having the same problem with this device too ... x86_64 actually causes a kernel panic where i686 works flawlessly.
Hi synthead.
Did you manage to solve this? I am still struggeling and haven't found a solution yet. With 2.6.37-rcs it's the same as before btw...
Offline
Pages: 1