Hello,
I use Openmediavault for more than six months and I'm very happy about it.
I plan to install it on a CuBox http://www.solid-run.com/products/cubox, in order to transform any eSATA external hard-disk into a very capable NAS with Gigabit LAN (a thing the raspberry Pi does not have), and with DLNA over Wifi (with Android clients for example).
Having a TrendNet N150, which is one of the smallest and cheapest USB Wifi adapter available, I tried to experiment it on a PC from a openmediavault installation done on a USB stick. Note that this PC has a Zotac H55-ITX motherboard, so it has a built-in Atheros AR928X Wifi adapter, so I ail to have two wlan connection.
Both adapters are recognized by Ubuntu 12.04 with noting to do (just plug and enter passphrase on prompt)
Here is what i did :
I installed wpasupplicant
I protected /etc/network/interfaces as it will contain my Wifi passphrase
I added in /etc/network/interfaces the definition for wlan1 and wlan2
I rebooted, and from that point, wlan1 on the Atheros adapter went UP with an IP allocated by my ADSL box. But wlan2 cannot be up.
I found here http://bernaerts.dyndns.org/li…tu-trendnet-n150-tew648ub that the N150 would need a particular firmware. So I followed the instructions, creating a /lib/firmware/RTL8192SU directory with the rtl8192sfw74.bin, rtl8192sfw492.bin, rtl8192sfw.bin files. In fact, only the rtl8192sfw.bin is really used. wlan2 is now configured, but it can not connect.
I think the firmware is not correct.
I found here http://packages.debian.org/squ…firmware-realtek/download I could install a realtek firmware form Debian repository. So i updated /etc/apt/sources.list
and installed this firmware
I did not improve anything.
I also tried to build firmware from Realtek site on an Ubuntu 64 installation
http://218.210.127.131/downloa…Down=false&Downloads=true
But I have compiler errors (in french 'transtypage d'un pointeur vers un entier de taille différente [-Wpointer-to-int-cast]')
I do not know enough Linux, Debian and Ubuntu to cope with that.
However, I think that the resolution of this issue could be profiable to others.
So, if any of you could help ...
I kinow that, after having a working Wifi adapter on AMD64, I will have to make it work on ARM on the CuBox ... that's another story ...
I noted some interesting lines on syslog
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.406356] rtl819xU: --->FirmwareDownload92S()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.406359]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.406368] usb 1-4.3: firmware: requesting RTL8192SU/rtl8192sfw.bin
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.414125] rtl819xU:signature:8192, version:902b, size:30, imemsize:7408, sram size:9688
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.414126]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.414135] rtl819xU:--->FirmwareDownloadCode()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.414136]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.414159] rtl819xU:--->FirmwareCheckReady(): LoadStaus(1),
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.415089] rtl819xU:<---FirmwareCheckReady(): LoadFWStatus(1), rtStatus(0)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.415091]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.415093] rtl819xU:--->FirmwareDownloadCode()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.415095]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.415146] rtl819xU:--->FirmwareCheckReady(): LoadStaus(2),
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.416213] rtl819xU:-->FirmwareEnableCPU()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.416215]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418082] rtl819xU:IMEM Ready after CPU has refilled.
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418083]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418086] rtl819xU:<--FirmwareEnableCPU(): rtStatus(0x0)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418087]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418090] rtl819xU:<---FirmwareCheckReady(): LoadFWStatus(2), rtStatus(0)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418091]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418094] rtl819xU:--->FirmwareDownloadCode()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418095]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418100] rtl819xU:--->FirmwareCheckReady(): LoadStaus(3),
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418332] rtl819xU:DMEM code download success, CPUStatus(0x3f)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.418333]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.419579] rtl819xU:Polling Load Firmware ready, CPUStatus(ff)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.419581]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.420577] rtl819xU:FirmwareCheckReady(): Current RCR settings(0x157e20e)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.420579]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.420701] rtl819xU:<---FirmwareCheckReady(): LoadFWStatus(3), rtStatus(0)
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.420703]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.420705] rtl819xU:Firmware Download Success!!
Oct 7 02:11:37 fpabernard-omvb kernel: [ 38.420707]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 41.075885] ADDRCONF(NETDEV_UP): wlan2: link is not ready
Oct 7 02:11:37 fpabernard-omvb kernel: [ 42.074611] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 42.076005] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647910] Linking with FPABERNARDALICE,channel:11, qos:1, myHT:1, networkHT:1, mode:10
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647914] ============>HTIOTActIsForcedRTSCTS(), 0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647915] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!IOTAction = 00008400
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647920] Linking with FPABERNARDALICE,channel:11, qos:1, myHT:1, networkHT:1, mode:10
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647922] ============>HTIOTActIsForcedRTSCTS(), 0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647923] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!IOTAction = 00008400
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.647947] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.648937] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.648941] ===>ieee80211_associate_procedure_wq(), chan:11
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.686580] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.686581]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.700212] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.700217] =================>ieee80211_authentication_req():auth->algorithm is 0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710961] rtl819xU:rtl8192_qos_association_resp: network->flags = 10,1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710963]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710973] rtl819xU:qos active process with associate response received
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710975]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710981] Associated successfully
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710984] Using G rates:108
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.710986] Successfully associated, ht enabled
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.748833] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.748834]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.764335] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.764339] !!!!!!!!!!!!!!!!!!!!!!!!!!!IOTRaFunc = 00000000
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.764343] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.767081] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.773692] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.773694] ============>normal associate
Oct 7 02:11:37 fpabernard-omvb kernel: [ 48.774372] ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
Oct 7 02:11:37 fpabernard-omvb kernel: [ 49.058509] dm_check_edca_turbo():iot peer is 0x4:ralink, bssid:4a:39:bc:3d:ba:d0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.931607] ==========>received disassoc/deauth(c0) frame, reason code:f
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.931618] ===========>RemovePeerTS,4a:39:bc:3d:ba:d0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.931621] ====>remove Tx_TS_admin_list
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.931634] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.932439] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.932443] ===>ieee80211_associate_procedure_wq(), chan:11
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.969834] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.969835]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.983715] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 54.983720] =================>ieee80211_authentication_req():auth->algorithm is 0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007935] rtl819xU:rtl8192_qos_association_resp: network->flags = 10,1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007937]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007948] rtl819xU:qos active process with associate response received
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007950]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007957] Associated successfully
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007959] Using G rates:108
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.007961] Successfully associated, ht enabled
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.045961] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.045962]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.062310] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.062314] !!!!!!!!!!!!!!!!!!!!!!!!!!!IOTRaFunc = 00000000
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.062318] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.065180] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.071541] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.071544] ============>normal associate
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.071552] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.072289] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.078652] Scan in 40M, force to 20M first:3, 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.078655] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.078657]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 55.092500] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.630523] Scan in 20M, back to 40M
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.667865] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.667866]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.683367] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.688608] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.691477] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 56.698089] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.215714] ==========>received disassoc/deauth(c0) frame, reason code:f
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.215724] ===========>RemovePeerTS,4a:39:bc:3d:ba:d0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.215737] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.216441] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.216445] ===>ieee80211_associate_procedure_wq(), chan:11
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.254084] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.254085]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.267965] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.267970] =================>ieee80211_authentication_req():auth->algorithm is 0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280213] rtl819xU:rtl8192_qos_association_resp: network->flags = 10,1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280215]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280225] rtl819xU:qos active process with associate response received
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280227]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280233] Associated successfully
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280236] Using G rates:108
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.280238] Successfully associated, ht enabled
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.320080] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.320081]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.335583] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.335587] !!!!!!!!!!!!!!!!!!!!!!!!!!!IOTRaFunc = 00000000
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.335591] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.338326] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.344939] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.344941] ============>normal associate
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.344950] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.345687] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.352049] Scan in 40M, force to 20M first:3, 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.352052] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.352054]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 61.365648] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.902303] Scan in 20M, back to 40M
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.939903] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.939904]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.955891] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.961031] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.963752] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 62.970613] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.499734] ==========>received disassoc/deauth(c0) frame, reason code:f
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.499745] ===========>RemovePeerTS,4a:39:bc:3d:ba:d0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.499748] ====>remove Tx_TS_admin_list
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.499761] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.500567] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.500571] ===>ieee80211_associate_procedure_wq(), chan:11
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.537838] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.537839]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.551718] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.551723] =================>ieee80211_authentication_req():auth->algorithm is 0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565219] rtl819xU:rtl8192_qos_association_resp: network->flags = 10,1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565221]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565233] rtl819xU:qos active process with associate response received
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565235]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565241] Associated successfully
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565243] Using G rates:108
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.565245] Successfully associated, ht enabled
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.602959] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.602960]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.618711] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.618715] !!!!!!!!!!!!!!!!!!!!!!!!!!!IOTRaFunc = 00000000
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.618719] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.621456] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.630064] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.630066] ============>normal associate
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.630075] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.630811] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.637174] Scan in 40M, force to 20M first:3, 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.637177] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.637179]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 67.651022] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.186058] Scan in 20M, back to 40M
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.223767] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 40MHz bandwidth
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.223768]
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.239271] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.244385] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.247129] =============>ARFR0+rate_index*4:0x100ff015
Oct 7 02:11:37 fpabernard-omvb kernel: [ 69.253991] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 73.773858] ==========>received disassoc/deauth(c0) frame, reason code:f
Oct 7 02:11:37 fpabernard-omvb kernel: [ 73.773869] ===========>RemovePeerTS,4a:39:bc:3d:ba:d0
Oct 7 02:11:37 fpabernard-omvb kernel: [ 73.773881] =====>rtl8192SU_link_change 1
Oct 7 02:11:37 fpabernard-omvb kernel: [ 73.774588] <=====rtl8192SU_link_change 2
Oct 7 02:11:37 fpabernard-omvb kernel: [ 73.774592] ===>ieee80211_associate_procedure_wq(), chan:11
Alles anzeigen
And these lines repeat ...
The activation of the WLAN link is very different on Ubuntu :
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 1 of 5 (Device Prepare) scheduled...
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 1 of 5 (Device Prepare) started...
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 2 of 5 (Device Configure) scheduled...
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 1 of 5 (Device Prepare) complete.
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 2 of 5 (Device Configure) starting...
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2/wireless): connection 'FPABERNARDALICE 1' has security, and secrets exist. No new secrets needed.
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Config: added 'ssid' value 'FPABERNARDALICE'
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Config: added 'scan_ssid' value '1'
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Config: added 'auth_alg' value 'OPEN'
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Config: added 'psk' value '<omitted>'
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 2 of 5 (Device Configure) complete.
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> Config: set interface ap_scan to 1
Oct 8 01:53:04 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): supplicant interface state: disconnected -> scanning
Oct 8 01:53:09 fpabernard-SanDisk64 wpa_supplicant[1306]: Trying to associate with 4a:39:bc:3d:ba:d0 (SSID='FPABERNARDALICE' freq=2462 MHz)
Oct 8 01:53:09 fpabernard-SanDisk64 wpa_supplicant[1306]: Association request to the driver failed
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): supplicant interface state: scanning -> associating
Oct 8 01:53:09 fpabernard-SanDisk64 wpa_supplicant[1306]: Associated with 4a:39:bc:3d:ba:d0
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): supplicant interface state: associating -> associated
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): supplicant interface state: associated -> group handshake
Oct 8 01:53:09 fpabernard-SanDisk64 wpa_supplicant[1306]: WPA: Key negotiation completed with 4a:39:bc:3d:ba:d0 [PTK=CCMP GTK=TKIP]
Oct 8 01:53:09 fpabernard-SanDisk64 wpa_supplicant[1306]: CTRL-EVENT-CONNECTED - Connection to 4a:39:bc:3d:ba:d0 completed (auth) [id=0 id_str=]
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): supplicant interface state: group handshake -> completed
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'FPABERNARDALICE'.
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 3 of 5 (IP Configure Start) started...
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> dhclient started with pid 6486
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Beginning IP6 addrconf.
Oct 8 01:53:09 fpabernard-SanDisk64 avahi-daemon[1106]: Withdrawing address record for fe80::214:d1ff:feab:dcc9 on wlan2.
Oct 8 01:53:09 fpabernard-SanDisk64 avahi-daemon[1106]: Leaving mDNS multicast group on interface wlan2.IPv6 with address fe80::214:d1ff:feab:dcc9.
Oct 8 01:53:09 fpabernard-SanDisk64 avahi-daemon[1106]: Interface wlan2.IPv6 no longer relevant for mDNS.
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 3 of 5 (IP Configure Start) complete.
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R4
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: Copyright 2004-2011 Internet Systems Consortium.
Oct 8 01:53:09 fpabernard-SanDisk64 kernel: [ 5565.171443] r8712u: [r8712_got_addbareq_event_callback] mac = 4a:39:bc:3d:ba:d0, seq = 48, tid = 0
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: All rights reserved.
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient:
Oct 8 01:53:09 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): DHCPv4 state changed nbi -> preinit
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: Listening on LPF/wlan2/00:14:d1:ab:dc:c9
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: Sending on LPF/wlan2/00:14:d1:ab:dc:c9
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: Sending on Socket/fallback
Oct 8 01:53:09 fpabernard-SanDisk64 dhclient: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67 interval 3
Oct 8 01:53:11 fpabernard-SanDisk64 avahi-daemon[1106]: Joining mDNS multicast group on interface wlan2.IPv6 with address fe80::214:d1ff:feab:dcc9.
Oct 8 01:53:11 fpabernard-SanDisk64 avahi-daemon[1106]: New relevant interface wlan2.IPv6 for mDNS.
Oct 8 01:53:11 fpabernard-SanDisk64 avahi-daemon[1106]: Registering new address record for fe80::214:d1ff:feab:dcc9 on wlan2.*.
Oct 8 01:53:11 fpabernard-SanDisk64 dhclient: DHCPREQUEST of 192.168.0.17 on wlan2 to 255.255.255.255 port 67
Oct 8 01:53:11 fpabernard-SanDisk64 dhclient: DHCPOFFER of 192.168.0.17 from 192.168.0.254
Oct 8 01:53:11 fpabernard-SanDisk64 dhclient: DHCPACK of 192.168.0.17 from 192.168.0.254
Oct 8 01:53:11 fpabernard-SanDisk64 dhclient: bound to 192.168.0.17 -- renewal in 344806 seconds.
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): DHCPv4 state changed preinit -> bound
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> address 192.168.0.17
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> prefix 24 (255.255.255.0)
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> gateway 192.168.0.254
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> nameserver '212.27.40.240'
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> nameserver '212.27.40.241'
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct 8 01:53:11 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 5 of 5 (IPv4 Commit) started...
Oct 8 01:53:11 fpabernard-SanDisk64 avahi-daemon[1106]: Joining mDNS multicast group on interface wlan2.IPv4 with address 192.168.0.17.
Oct 8 01:53:11 fpabernard-SanDisk64 avahi-daemon[1106]: New relevant interface wlan2.IPv4 for mDNS.
Oct 8 01:53:11 fpabernard-SanDisk64 avahi-daemon[1106]: Registering new address record for 192.168.0.17 on wlan2.IPv4.
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[1882]: sortie sur réception du signal SIGTERM
Oct 8 01:53:12 fpabernard-SanDisk64 NetworkManager[1070]: <info> DNS: starting dnsmasq...
Oct 8 01:53:12 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): writing resolv.conf to /sbin/resolvconf
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: démarrage avec le cache désactivé (version 2.59)
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: options à la compilation : IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: utilise le serveur de nom 212.27.40.241#53
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: utilise le serveur de nom 212.27.40.240#53
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: utilise le serveur de nom 212.27.40.241#53
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: utilise le serveur de nom 212.27.40.240#53
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: utilise le serveur de nom 212.27.40.241#53
Oct 8 01:53:12 fpabernard-SanDisk64 dnsmasq[6490]: utilise le serveur de nom 212.27.40.240#53
Oct 8 01:53:12 fpabernard-SanDisk64 NetworkManager[1070]: <info> Policy set 'Connexion filaire 1' (eth4) as default for IPv4 routing and DNS.
Oct 8 01:53:12 fpabernard-SanDisk64 NetworkManager[1070]: <info> (wlan2): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct 8 01:53:12 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) successful, device activated.
Oct 8 01:53:12 fpabernard-SanDisk64 NetworkManager[1070]: <info> Activation (wlan2) Stage 5 of 5 (IPv4 Commit) complete.
Oct 8 01:53:12 fpabernard-SanDisk64 dbus[962]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Oct 8 01:53:12 fpabernard-SanDisk64 dbus[962]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 8 01:53:20 fpabernard-SanDisk64 kernel: [ 5575.940602] wlan2: no IPv6 routers present
Oct 8 01:53:20 fpabernard-SanDisk64 ntpdate[6524]: step time server 91.189.94.4 offset -0.951166 sec
Alles anzeigen
Best regards,
Fred