Hi On Thursday 13 May 2010, Miguel J. Jiménez wrote: > Hi, > > lsusb shows: > > Bus 001 Device 006: ID 050d:815f Belkin Components Realtek RTL8192SU > [F5D8053 N Wireless USB Adapter v6000] > > while "dmesg" shows: > > [ 1.232523] usb 1-6: new high speed USB device using ehci_hcd and address 4 > [ 1.366483] usb 1-6: New USB device found, idVendor=050d, idProduct=815f > [ 1.366486] usb 1-6: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 1.366489] usb 1-6: Product: RTL8191S WLAN Adapter
Interesting, so it's a 300 MBit/s variant (RTL8188S is n-lite/ 150 MBit/s);
also no USB ID overlap with rtl8192u.
> [ 1.366492] usb 1-6: Manufacturer: Manufacturer Realtek
> [ 1.366494] usb 1-6: SerialNumber: 00e04c000001
> [ 29.913647] usb 1-6: firmware: requesting RTL8192SU/rtl8192sfw.bin
No error message.
> When connecting with wicd, /var/log/kern.log show:
[...]
> rtl819xU:--->FirmwareCheckReady(): LoadStaus(2),
> May 13 19:42:06 localhost kernel: [ 5673.604165]
> rtl819xU:-->FirmwareEnableCPU()
> May 13 19:42:06 localhost kernel: [ 5673.604166]
> May 13 19:42:06 localhost kernel: [ 5673.605912] rtl819xU:IMEM Ready after
> CPU has refilled.
> May 13 19:42:06 localhost kernel: [ 5673.605915]
> May 13 19:42:06 localhost kernel: [ 5673.605917]
> rtl819xU:<--FirmwareEnableCPU(): rtStatus(0x0)
> May 13 19:42:06 localhost kernel: [ 5673.605919]
> May 13 19:42:06 localhost kernel: [ 5673.605921]
> rtl819xU:<---FirmwareCheckReady(): LoadFWStatus(2), rtStatus(0)
> May 13 19:42:06 localhost kernel: [ 5673.605923]
> May 13 19:42:06 localhost kernel: [ 5673.605926]
> rtl819xU:--->FirmwareDownloadCode()
> May 13 19:42:06 localhost kernel: [ 5673.605927]
> May 13 19:42:06 localhost kernel: [ 5673.605933]
> rtl819xU:--->FirmwareCheckReady(): LoadStaus(3),
> May 13 19:42:06 localhost kernel: [ 5673.606161] rtl819xU:DMEM code download
> success, CPUStatus(0x3f)
> May 13 19:42:06 localhost kernel: [ 5673.606163]
> May 13 19:42:06 localhost kernel: [ 5673.607536] rtl819xU:Polling Load
> Firmware ready, CPUStatus(ff)
> May 13 19:42:06 localhost kernel: [ 5673.607537]
> May 13 19:42:06 localhost kernel: [ 5673.608537]
> rtl819xU:FirmwareCheckReady(): Current RCR settings(0x157e20e)
> May 13 19:42:06 localhost kernel: [ 5673.608538]
> May 13 19:42:06 localhost kernel: [ 5673.608664]
> rtl819xU:<---FirmwareCheckReady(): LoadFWStatus(3), rtStatus(0)
> May 13 19:42:06 localhost kernel: [ 5673.608666]
> May 13 19:42:06 localhost kernel: [ 5673.608668] rtl819xU:Firmware Download
> Success!!
> May 13 19:42:06 localhost kernel: [ 5673.608669]
> May 13 19:42:09 localhost kernel: [ 5676.323590] ADDRCONF(NETDEV_UP): wlan0:
> link is not ready
The firmware seems to have uploaded correctly to the device.
> May 13 19:42:09 localhost kernel: [ 5676.385425] ADDRCONF(NETDEV_UP):
[...]
> ===>ieee80211_associate_procedure_wq(), chan:1
> May 13 19:42:14 localhost kernel: [ 5681.312842]
> rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
scanning
> May 13 19:42:14 localhost kernel: [ 5681.312844]
> May 13 19:42:14 localhost kernel: [ 5681.326998]
> rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
> May 13 19:42:14 localhost kernel: [ 5681.327003]
> =================>ieee80211_authentication_req():auth->algorithm is 0
> May 13 19:42:14 localhost kernel: [ 5681.327787] Linking with
> JIMENEZ,channel:1, qos:0, myHT:1, networkHT:0, mode:6
> May 13 19:42:14 localhost kernel: [ 5681.327813] Linking with
> JIMENEZ,channel:1, qos:0, myHT:1, networkHT:0, mode:6
> May 13 19:42:14 localhost kernel: [ 5681.327872] =====>rtl8192SU_link_change 1
> May 13 19:42:14 localhost kernel: [ 5681.328885] <=====rtl8192SU_link_change 2
> May 13 19:42:14 localhost kernel: [ 5681.328888]
> ===>ieee80211_associate_procedure_wq(), chan:1
> May 13 19:42:14 localhost kernel: [ 5681.378091]
> rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
> May 13 19:42:14 localhost kernel: [ 5681.378093]
> May 13 19:42:14 localhost kernel: [ 5681.392250]
> rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
> May 13 19:42:14 localhost kernel: [ 5681.392254]
> =================>ieee80211_authentication_req():auth->algorithm is 0
> May 13 19:42:14 localhost kernel: [ 5681.392279] Linking with
> JIMENEZ,channel:1, qos:0, myHT:1, networkHT:0, mode:6
> May 13 19:42:14 localhost kernel: [ 5681.392298] =====>rtl8192SU_link_change 1
> May 13 19:42:14 localhost kernel: [ 5681.393249] <=====rtl8192SU_link_change 2
> May 13 19:42:14 localhost kernel: [ 5681.393253]
> ===>ieee80211_associate_procedure_wq(), chan:1
> May 13 19:42:14 localhost kernel: [ 5681.442809]
> rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
> May 13 19:42:14 localhost kernel: [ 5681.442812]
> May 13 19:42:14 localhost kernel: [ 5681.456999]
> rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
> May 13 19:42:14 localhost kernel: [ 5681.457003]
> =================>ieee80211_authentication_req():auth->algorithm is 0
> May 13 19:42:14 localhost kernel: [ 5681.465010]
> rtl819xU:rtl8192_qos_association_resp: network->flags = 2,0
> May 13 19:42:14 localhost kernel: [ 5681.465012]
> May 13 19:42:14 localhost kernel: [ 5681.465023] rtl819xU:qos active process
> with associate response received
> May 13 19:42:14 localhost kernel: [ 5681.465025]
> May 13 19:42:14 localhost kernel: [ 5681.465033] Associated successfully
> May 13 19:42:14 localhost kernel: [ 5681.465035] Using G rates:108
> May 13 19:42:14 localhost kernel: [ 5681.465037] Successfully associated, ht
> not enabled(0, 0)
seems to associate correctly
> May 13 19:42:14 localhost kernel: [ 5681.465040] =====>rtl8192SU_link_change 1
> May 13 19:42:14 localhost kernel: [ 5681.467626]
> =============>ARFR0+rate_index*4:0xfff
> May 13 19:42:14 localhost kernel: [ 5681.475624] <=====rtl8192SU_link_change 2
> May 13 19:42:14 localhost kernel: [ 5681.475626] ============>normal associate
> May 13 19:42:14 localhost kernel: [ 5681.476344] ADDRCONF(NETDEV_CHANGE):
> wlan0: link becomes ready
> May 13 19:42:14 localhost kernel: [ 5681.484084] alg name:TKIP
> May 13 19:42:14 localhost kernel: [ 5681.484100]
> rtl819xU:EnableHWSecurityConfig8192:, hwsec:1, pairwise_key:2, SECR_value:c
> May 13 19:42:14 localhost kernel: [ 5681.484102]
> May 13 19:42:14 localhost kernel: [ 5681.484259] rtl819xU:====>to setKey(),
> dev:ffff88004bfb0000, EntryNo:4, KeyIndex:0, KeyType:2,
> MacAddr64:68:0c:2f:71:0a
> May 13 19:42:14 localhost kernel: [ 5681.484261]
> May 13 19:42:14 localhost kernel: [ 5681.488260] alg name:TKIP
> May 13 19:42:14 localhost kernel: [ 5681.488275] rtl819xU:====>to setKey(),
> dev:ffff88004bfb0000, EntryNo:1, KeyIndex:1, KeyType:2,
> MacAddrff:ff:ff:ff:ff:ff
> May 13 19:42:14 localhost kernel: [ 5681.488277]
> May 13 19:42:16 localhost kernel: [ 5683.169621] dm_check_edca_turbo():iot
> peer is 0x0:unknown, bssid:64:68:0c:2f:71:0a
> May 13 19:42:24 localhost kernel: [ 5691.936010] wlan0: no IPv6 routers
> present
Now it even got an IPv4 address.
> Hope it helps a bit.
Judging from the log, the firmware uploads and works correctly up to the
point of obtaining an IPv4 address - nothing unexpected to be seen.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
