[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#581554: firmware-realtek: Incorrect firmware



Hi

On Saturday 15 May 2010, Ben Hutchings wrote:
> On Fri, 2010-05-14 at 08:56 +0200, Miguel J.Jiménez wrote:
> > > The firmware seems to have uploaded correctly to the device.
> > 
> > My mistake... that was 68533bf8078a9e00966a78c9f2da4b9b firmware and
> > not the one provided with the deb package.
> [...]
> 
> OK, I've found this file - not on the Realtek site but on a random
> file-sharing site!  Since I've now collected quite a few Realtek driver
> packages which aren't easily available, I've uploaded all those that are
> redistributable to <http://people.debian.org/~benh/rtl-wlan/>.
> 
> Stefan, please download
> <http://people.debian.org/~benh/rtl-wlan/rtl8192su_linux_2.6.0002.0708.2009.tar.gz> and check whether the firmware blob in there (which should be the same one Miguel has used) works for you as well.

68533bf8078a9e00966a78c9f2da4b9b */lib/firmware/RTL8192SU/rtl8192sfw.bin

Does work for me as well:
[   69.922023] usb 1-3: new high speed USB device using ehci_hcd and address 4
[   70.038440] usb 1-3: New USB device found, idVendor=0bda, idProduct=8171
[   70.038443] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   70.038445] usb 1-3: Product: RTL8188S WLAN Adapter 
[   70.038447] usb 1-3: Manufacturer: Manufacturer Realtek 
[   70.038449] usb 1-3: SerialNumber: 00e04c000001
[   70.131710] r8192s_usb: module is from the staging directory, the quality is unknown, you have been warned.
[   70.135003] ieee80211_crypt: registered algorithm 'NULL'
[   70.135006] ieee80211_crypt: registered algorithm 'TKIP'
[   70.135007] ieee80211_crypt: registered algorithm 'CCMP'
[   70.135009] ieee80211_crypt: registered algorithm 'WEP'
[   70.135010] 
[   70.135011] Linux kernel driver for RTL8192 based WLAN cards
[   70.135012] Copyright (c) 2007-2008, Realsil Wlan
[   70.135274] ==>ep_num:4, in_ep_num:1, out_ep_num:3
[   70.135276] ==>RtInPipes:3  
[   70.135278] ==>RtOutPipes:4  6  13  
[   70.135281] ==>txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD, MGNT, HIGH, BEACON:
[   70.135282] 1  1  0  0  2  2  2  2  2  
[   70.345766] usbcore: registered new interface driver rtl819xU
[   84.803010] usb 1-3: firmware: requesting RTL8192SU/rtl8192sfw.bin
[   87.528569] ADDRCONF(NETDEV_UP): wlan2: link is not ready
[   87.802108] Linking with surveyor,channel:1, qos:1, myHT:1, networkHT:1, mode:10
[   87.802121] Linking with surveyor,channel:1, qos:1, myHT:1, networkHT:1, mode:10
[   87.863184] Associated successfully
[   87.863187] Using G rates:108
[   87.863189] Successfully associated, ht enabled
[   87.929515] ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[   88.053026] padlock: VIA PadLock not detected.
[   88.117882] Intel AES-NI instructions are not detected.
[   89.528564] dm_check_edca_turbo():iot peer is 0x0:unknown, bssid:00:27:19:fe:47:84
[   98.065009] wlan2: no IPv6 routers present

It is slightly slower though, ~5130 KB/s (a5ad703551efb108ba012b4b8a830d93)
compared to 4970 KB/s (68533bf8078a9e00966a78c9f2da4b9b) for a 65 MB kernel
tarball served by vsftpd from a local server (access point using Atheros 
AR9100 MAC/BB Rev:0 AR2133 RF Rev:a2 with ath9k, local server connected via
GBit/s ethernet).

Regards
	Stefan Lippers-Hollmann

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: