* Re: Problem bringing up wlan0 interface up with mainline wl1271 drivers
From: Elvis Dowson @ 2010-12-17 10:25 UTC (permalink / raw)
To: Arik Nemtsov
Cc: panduranga, Ohad Ben-Cohen, Linux Wireless Mailing List,
Jara, Pedro
In-Reply-To: <AANLkTikvk+AqKRr1VbKv9pSHicy7PAGu8GkdeZuvYwFh@mail.gmail.com>
Hi Arik,
On Dec 17, 2010, at 2:12 PM, Arik Nemtsov wrote:
>
> The firmware file should be called wl1271-fw.bin and the nvs file
> should be called wl1271-nvs.bin. Both should reside in /etc/firmware
> (if you're running a standard linux).
I got the files from this git repo
git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
and copied them over to /etc/firmware
/etc/firmware# ls -l
total 276
-r--r--r-- 1 root root 271712 Dec 17 2010 wl1271-fw.bin
-rw-rw-r-- 1 root root 912 Dec 17 2010 wl1271-nvs.bin
But I still get a error saying the the nvs file could not be found:
[ 63.852264] wl1271: ERROR could not get nvs file: -2
[ 63.906250] wl1271: loaded
[ 63.909271] wl1271: initialized
Best regards,
Elvis Dowson
^ permalink raw reply
* Re: Problem bringing up wlan0 interface up with mainline wl1271 drivers
From: Arik Nemtsov @ 2010-12-17 10:34 UTC (permalink / raw)
To: Elvis Dowson
Cc: panduranga, Ohad Ben-Cohen, Linux Wireless Mailing List,
Jara, Pedro
In-Reply-To: <397FC41E-7F1D-4AA8-9D09-6121BB0169E7@mac.com>
On Fri, Dec 17, 2010 at 12:25, Elvis Dowson <elvis.dowson@mac.com> wrote:
> Hi Arik,
>
> On Dec 17, 2010, at 2:12 PM, Arik Nemtsov wrote:
>>
>> The firmware file should be called wl1271-fw.bin and the nvs file
>> should be called wl1271-nvs.bin. Both should reside in /etc/firmware
>> (if you're running a standard linux).
>
> I got the files from this git repo
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
>
> and copied them over to /etc/firmware
>
> /etc/firmware# ls -l
> total 276
> -r--r--r-- 1 root root 271712 Dec 17 2010 wl1271-fw.bin
> -rw-rw-r-- 1 root root 912 Dec 17 2010 wl1271-nvs.bin
>
> But I still get a error saying the the nvs file could not be found:
>
> [ 63.852264] wl1271: ERROR could not get nvs file: -2
> [ 63.906250] wl1271: loaded
> [ 63.909271] wl1271: initialized
>
> Best regards,
>
> Elvis Dowson
>
Sorry Elvis I gave you the wrong path :)
Its /lib/firmware in a regular linux. Its /etc/firmware in android.
Regards,
Arik
^ permalink raw reply
* Re: Problem bringing up wlan0 interface up with mainline wl1271 drivers
From: Luciano Coelho @ 2010-12-17 10:38 UTC (permalink / raw)
To: ext Elvis Dowson
Cc: Arik Nemtsov, panduranga, Ohad Ben-Cohen,
Linux Wireless Mailing List, Jara, Pedro
In-Reply-To: <397FC41E-7F1D-4AA8-9D09-6121BB0169E7@mac.com>
Hi Elvis,
On Fri, 2010-12-17 at 14:25 +0400, ext Elvis Dowson wrote:
> Hi Arik,
>
> On Dec 17, 2010, at 2:12 PM, Arik Nemtsov wrote:
> >
> > The firmware file should be called wl1271-fw.bin and the nvs file
> > should be called wl1271-nvs.bin. Both should reside in /etc/firmware
> > (if you're running a standard linux).
>
> I got the files from this git repo
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
>
> and copied them over to /etc/firmware
>
> /etc/firmware# ls -l
> total 276
> -r--r--r-- 1 root root 271712 Dec 17 2010 wl1271-fw.bin
> -rw-rw-r-- 1 root root 912 Dec 17 2010 wl1271-nvs.bin
>
> But I still get a error saying the the nvs file could not be found:
>
> [ 63.852264] wl1271: ERROR could not get nvs file: -2
> [ 63.906250] wl1271: loaded
> [ 63.909271] wl1271: initialized
You need to start udevd. The driver gets the firmware via udev.
--
Cheers,
Luca.
^ permalink raw reply
* Re: Problem bringing up wlan0 interface up with mainline wl1271 drivers
From: Elvis Dowson @ 2010-12-17 10:37 UTC (permalink / raw)
To: Arik Nemtsov; +Cc: Linux Wireless Mailing List
In-Reply-To: <AANLkTimfNw7Lsp7vnLPt7SaC=SAg0ctMbunRBz4SybhD@mail.gmail.com>
Hi Arik,
On Dec 17, 2010, at 2:34 PM, Arik Nemtsov wrote:
>
> Sorry Elvis I gave you the wrong path :)
> Its /lib/firmware in a regular linux. Its /etc/firmware in android.
:-) Ok, that's understandable!! My final aim is to get this working with android-2.2.1. Have you done a port of the android kernel to 2.6.37 already ?
Best regards,
Elvis Dowson
^ permalink raw reply
* Re: Problem bringing up wlan0 interface up with mainline wl1271 drivers
From: Elvis Dowson @ 2010-12-17 11:12 UTC (permalink / raw)
To: Arik Nemtsov; +Cc: Linux Wireless Mailing List
In-Reply-To: <9B373863-A428-4A02-BFD2-DE5B5C914C48@mac.com>
Hi Arik,
Its working now.
[ 0.000000] wlan_mux_init: Configuring mux settings for wl1271 wlan module
[ 2.143035] mmc1: mmc_rescan: trying to init card at 400000 Hz
[ 2.292175] mmc1: card claims to support voltages below the defined range. These will be ignored.
[ 2.337158] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
[ 2.359710] mmc1: new SDIO card at address 0001
Starting udev
[ 3.948883] udev: starting version 151
[ 3.957519] udevd (550): /proc/550/oom_adj is deprecated, please use /proc/550/oom_score_adj instead.
[ 5.156890] wl1271: loaded
[ 5.159942] wl1271: initialized
# ifconfig -a
lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
# ifconfig wlan0 up
# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 68:7f:74:1c:e4:7c (SSID='Olympus2' freq=2437 MHz)
Associated with 68:7f:74:1c:e4:7c
WPA: Key negotiation completed with 68:7f:74:1c:e4:7c [PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 68:7f:74:1c:e4:7c completed (auth) [id=0 id_str=]
^Z[1] + Stopped wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
# ifconfig -a
lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:328 (328.0 b) TX bytes:288 (288.0 b)
# ifconfig wlan0 inet 192.168.1.105 netmask 255.255.255.0
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=66.1 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=27.8 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=34.7 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=37.7 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=31.2 ms
^Z[2] + Stopped ping 192.168.1.1
# [ 263.148956] cfg80211: Calling CRDA to update world regulatory domain
Best regards,
Elvis Dowson
^ permalink raw reply
* Re: [PATCH 04/17] rt2x00: fix hang when unplugging USB device in use
From: Walter Goldens @ 2010-12-17 11:56 UTC (permalink / raw)
To: Ivo Van Doorn; +Cc: js, linux-wireless, users
In-Reply-To: <AANLkTi=img36VOkKapcgZz54ZmtXRneai-W0bU_W5z=E@mail.gmail.com>
> Odd I have been testing this while stresstesting the card,
> and either
> unplugging, rmmod or ifdown, and I couldn't
> reproduce any crashes. Has the stacktrace changed after
> these patches?
Hi.
I can confirm when the rt2800usb is loaded and an rt3070 chip is connected to a network, running 'rmmod rt2800usb rt2x00lib rt2x00usb rt2800lib' causes immediate system hang (and hard-reset).
I was not able to retrieve any relevant error logs.
Walter
^ permalink raw reply
* Re: wimaxd daemon bug
From: Alexander Khryukin @ 2010-12-17 13:58 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <4D0A1DB8.7080108@mezon.ru>
16.12.2010 17:10, Alexander Khryukin пишет:
> Good day.
> I have
> 1.MeeGo 1.1
> 2.Intel Corporation WiMAX/WiFi Link 6050 Series (rev 2c)
> 3.Wimax network that named 'Yota'
>
>
> wimaxcu scan wide
> WARNING: Wide scan may take upto 2 minutes...
> NSP : Yota
> ID : 21
> Signal : Excellent
> RSSI : -62 dBm
> CINR : 29 dB
> Network Type: Home Network
> Activated.
>
>
>
> Then i try to connect with Yota-network
>
> wimaxcu connect network 21
> Connecting to Yota Network...
> Connection successful
>
> [root@meego-desktop ~]# /usr/bin/wimaxd -d -i wmx0
> Enter Command:
> q - Quit AppSrv
> t - Trace ReInit (ReLoads Registry Values)
> u - uplink(Apdo uplink event
> h - Help
> d - Toggle driver messages to display - debug & internal only
>
>
> AppSrv is ready !
> Act_FullRestart!
> Act_DriverDeviceStatus - DRIVER_UP
> CTRL-EVENT-EAP-STARTED EAP authentication started
> Sending EapResponse. Data size: 25
> CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
> CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
> Sending EapResponse. Data size: 60
> Sending EapResponse. Data size: 60
> Sending EapResponse. Data size: 6
> Sending EapResponse. Data size: 6
> Sending EapResponse. Data size: 1310
> Sending EapResponse. Data size: 1144
> Sending EapResponse. Data size: 6
> CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
> CTRL-EVENT-EAP-STARTED EAP authentication started
> Sending EapResponse. Data size: 17
> CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
> CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
> Sending EapResponse. Data size: 60
> Sending EapResponse. Data size: 6
> Sending EapResponse. Data size: 6
> Sending EapResponse. Data size: 1310
> Sending EapResponse. Data size: 1144
> Sending EapResponse. Data size: 6
>
>
> Then i try to reconnect
>
> [root@meego-desktop ~]# wimaxcu connect network 21
> Current Preferred Profile is:
> ID : 21
> Name: Yota
> Connecting to Yota Network...
> Connection failure
>
>
> Next i try to
>
> wimaxll -i wmx0 reset
> and start daemon again
>
> /usr/bin/wimaxd -d -i wmx0
>
> Connect to network
>
> imaxcu connect network 21
> Current Preferred Profile is:
> ID : 21
> Name: Yota
> Connecting to Yota Network...
> Connection successful
>
>
> Wimaxd version wimax-1.5.1-35.13.i586.rpm
> from Inaky Perez-Gonzalez repo.
> http://download.meego.com/live/home:/inaky:/pegatron-idf-2010/Trunk/i586/
>
>
> uname -a
> Linux meego-desktop 2.6.36-1.9_mezon.12.1-netbook #1 SMP PREEMPT Wed Dec
> 15 20:01:48 MSK 2010 i686 i686 i386 GNU/Linux
>
>
>
> steps to reproduce:
> 1.Plug on Intel Corporation WiMAX/WiFi Link 6050 Series (rev 2c)
> 2.Install any version on wimaxd
> 3.wimaxcu connect any_network_id
> 4.wait about 2 minutes
> 5.connection dropped.
> 6.try connect again, and see "connection failure"
> 7.wimaxll -i wmx0 rese
> 8.connect to network again (it will be succeeded)
> 9.Proceed to step 4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Additional report.
[root@meego-desktop ~]# /usr/bin/wimaxd -d -i wmx0
Enter Command:
q - Quit AppSrv
t - Trace ReInit (ReLoads Registry Values)
u - uplink(Apdo uplink event
h - Help
d - Toggle driver messages to display - debug & internal only
AppSrv is ready !
Act_FullRestart!
Act_DriverDeviceStatus - DRIVER_UP
/var/log/wimax/wimaxd.log
http://pastebin.ca/2022059
And wait for 2 minutes
Now connection dropped in log nothing interesting not dropped
[root@meego-desktop ~]# wimaxcu connect network 21
Current Preferred Profile is:
ID : 21
Name: Yota
Connecting to Yota Network...
Connection failure
In log
http://pastebin.ca/2022057
^ permalink raw reply
* [PATCH] rtl8192ce: Fix typo in Kconfig description
From: Anisse Astier @ 2010-12-17 10:45 UTC (permalink / raw)
To: Larry Finger; +Cc: John W. Linville, Anisse Astier
Signed-off-by: Anisse Astier <anisse@astier.eu>
---
drivers/net/wireless/rtlwifi/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/Kconfig b/drivers/net/wireless/rtlwifi/Kconfig
index d712026..7f6573f 100644
--- a/drivers/net/wireless/rtlwifi/Kconfig
+++ b/drivers/net/wireless/rtlwifi/Kconfig
@@ -7,7 +7,7 @@ config RTL8192CE
This is the driver for Realtek RTL8192CE/RTL8188CE 802.11n PCIe
wireless network adapters.
- If you choose to build it as a module, it will be calledrtl8192ce.
+ If you choose to build it as a module, it will be called rtl8192ce
config RTLWIFI
tristate
--
1.7.3.2
^ permalink raw reply related
* Re: [PATCH] mwifiex: use debugfs_remove_recursive()
From: John W. Linville @ 2010-12-17 14:26 UTC (permalink / raw)
To: Bing Zhao
Cc: linux-wireless, Johannes Berg, Amitkumar Karwar, Kiran Divekar,
Frank Huang
In-Reply-To: <1292558206-29423-1-git-send-email-bzhao@marvell.com>
On Thu, Dec 16, 2010 at 07:56:46PM -0800, Bing Zhao wrote:
> From: Amitkumar Karwar <akarwar@marvell.com>
>
> instead of keeping pointers to all entries.
>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> Signed-off-by: Kiran Divekar <dkiran@marvell.com>
Just for the record, I'm not tracking any of the mwifiex patches at
this time. Are you pushing them to a public git tree?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: [PATCH 04/17] rt2x00: fix hang when unplugging USB device in use
From: Johannes Stezenbach @ 2010-12-17 15:02 UTC (permalink / raw)
To: Walter Goldens; +Cc: Ivo Van Doorn, linux-wireless, users
In-Reply-To: <740412.10599.qm@web56806.mail.re3.yahoo.com>
On Fri, Dec 17, 2010 at 03:56:05AM -0800, Walter Goldens wrote:
>
> > Odd I have been testing this while stresstesting the card,
> > and either
> > unplugging, rmmod or ifdown, and I couldn't
> > reproduce any crashes. Has the stacktrace changed after
> > these patches?
>
> I can confirm when the rt2800usb is loaded and an rt3070 chip is connected to
> a network, running 'rmmod rt2800usb rt2x00lib rt2x00usb rt2800lib' causes
> immediate system hang (and hard-reset).
FWIW, I did not test this case. I only tested hot-unplug of the
USB device. However, I think usually when the network interface
is up the module use count should be incremented so that you
cannot unload the module.
Johannes
^ permalink raw reply
* [PATCH] ath9k: Properly initialize channel table for 2GHz
From: Mohammed Shafi Shajakhan @ 2010-12-17 15:14 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, lrodriguez, Mohammed Shafi Shajakhan
From: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
ath9k channel table for 2Ghz does not seems to initialize the 'band'
parameter.Though it does not seems to cause any visible issue it looks
odd when we initialize the 'band' parameter for 5Ghz channel table while
not so for 2Ghz.
Signed-off-by: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
---
drivers/net/wireless/ath/ath9k/init.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/init.c b/drivers/net/wireless/ath/ath9k/init.c
index 1238795..b0e5e71 100644
--- a/drivers/net/wireless/ath/ath9k/init.c
+++ b/drivers/net/wireless/ath/ath9k/init.c
@@ -48,6 +48,7 @@ MODULE_PARM_DESC(pmqos, "User specified PM-QOS value");
/* We use the hw_value as an index into our private channel structure */
#define CHAN2G(_freq, _idx) { \
+ .band = IEEE80211_BAND_2GHZ, \
.center_freq = (_freq), \
.hw_value = (_idx), \
.max_power = 20, \
--
1.7.0.4
^ permalink raw reply related
* Re: [PATCH 04/17] rt2x00: fix hang when unplugging USB device in use
From: Walter Goldens @ 2010-12-17 16:33 UTC (permalink / raw)
To: Johannes Stezenbach; +Cc: Ivo Van Doorn, linux-wireless, users
In-Reply-To: <20101217150206.GA6805@sig21.net>
> > > Odd I have been testing this while stresstesting
> the card,
> > > and either
> > > unplugging, rmmod or ifdown, and I couldn't
> > > reproduce any crashes. Has the stacktrace changed
> after
> > > these patches?
> >
> > I can confirm when the rt2800usb is loaded and an
> rt3070 chip is connected to
> > a network, running 'rmmod rt2800usb rt2x00lib
> rt2x00usb rt2800lib' causes
> > immediate system hang (and hard-reset).
>
> FWIW, I did not test this case. I only tested
> hot-unplug of the
> USB device. However, I think usually when the network
> interface
> is up the module use count should be incremented so that
> you
> cannot unload the module.
>
Hi, Johannes
I can rmmod the zd1211rw for example, even the interface is up and connected to a network, whereas the rt2800usb forces the system to freeze. Why the difference?
Walter
^ permalink raw reply
* rtl8192 does not see N networks in my building
From: Amos Blanton @ 2010-12-17 17:20 UTC (permalink / raw)
To: linux-wireless
Greetings. I have a rtl8192 in a Strata 13 laptop from Zareason
running Ubuntu 10.10, and I work in an environment with many Wifi
networks. With my previous laptop I was often able to see and
sometimes login to a local un-encrypted N network, the best we have
around here, but this one doesn't seem to find and display that
network via Network Manager.
I'm told my office has cisco ap1252s running the latest 7.0 code
release. There are B/G as well as N networks here, at least 10 that
Network manager will recognize.
Sorry, I'm not sure what the relevant DMSG info is, so I'll include
the latest swath. Please let me know if I should get additional info,
and if this is the right place to report these issues.
Thanks to everyone here who helps make Linux wireless work!
-Amos
359.748754] LPS leave: notify AP we are awaked ++++++++++ SendNullFunctionData
[ 359.749098] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 359.805892] =====>rtl8192_set_chan()====ch:1
[ 359.925611] =====>rtl8192_set_chan()====ch:2
[ 360.045465] =====>rtl8192_set_chan()====ch:3
[ 360.165430] =====>rtl8192_set_chan()====ch:4
[ 360.285243] =====>rtl8192_set_chan()====ch:5
[ 360.405139] =====>rtl8192_set_chan()====ch:6
[ 360.524976] =====>rtl8192_set_chan()====ch:7
[ 360.644919] =====>rtl8192_set_chan()====ch:8
[ 360.764741] =====>rtl8192_set_chan()====ch:9
[ 360.884613] =====>rtl8192_set_chan()====ch:10
[ 361.004666] =====>rtl8192_set_chan()====ch:11
[ 361.128624] =====>rtl8192_set_chan()====ch:12
[ 361.244226] =====>rtl8192_set_chan()====ch:13
[ 361.364079] =====>rtl8192_set_chan()====ch:11
[ 361.374946] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 361.374958] rtl8192_update_cap(): WLAN_CAPABILITY_SHORT_PREAMBLE
[ 361.380087] notify_wx_assoc_event(): Tell user space disconnected
[ 361.380131] Linking with MIT,channel:6, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 361.380217] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 361.380357] ===>rtllib_associate_procedure_wq(), chan:6
[ 361.380361] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 361.380366] =====>rtl8192_set_chan()====ch:6
[ 361.417746] Linking with MIT,channel:1, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 361.417778] ===>rtllib_associate_procedure_wq(), chan:1
[ 361.417785] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 361.417791] =====>rtl8192_set_chan()====ch:1
[ 363.921468] Linking with MIT,channel:1, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 363.921488] ===>rtllib_associate_procedure_wq(), chan:1
[ 363.921494] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 363.921500] =====>rtl8192_set_chan()====ch:1
[ 364.266878] rtl8192_SetWirelessMode(), wireless_mode:10, bEnableHT = 1
[ 364.334040] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:0:2b
[ 364.334044] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:1:4f
[ 364.334047] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:2:22
[ 364.334050] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:3:22
[ 364.334056] Associated successfully
[ 364.334058] normal associate
[ 364.334071] Using G rates:108
[ 364.334073] Successfully associated, ht enabled
[ 364.334076] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 364.334080] =====>rtl8192_set_chan()====ch:1
[ 364.344559] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 364.344570] rtl8192_update_cap(): WLAN_CAPABILITY_SHORT_PREAMBLE
[ 364.356664] ====>rx ADDBAREQ from :00:23:eb:d1:cd:02
[ 364.356684] ====>to send ADDBARSP
[ 372.032996] intel ips 0000:00:1f.6: MCP power or thermal limit exceeded
[ 397.106889] rtl8192_hw_wakeup(): RF Change in progress! schedule
wake up task again
[ 405.090729] rtl8192_hw_sleep_down(): RF Change in progress!
[ 419.074869] rtl8192_hw_sleep_down(): RF Change in progress!
[ 465.026504] MgntActSet_RF_State(): RF Change in progress! Wait to
set..StateToSet(0).
[ 479.622470] LPS leave: notify AP we are awaked ++++++++++
SendNullFunctionData
[ 479.622768] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 479.681548] =====>rtl8192_set_chan()====ch:1
[ 479.801523] =====>rtl8192_set_chan()====ch:2
[ 479.920546] =====>rtl8192_set_chan()====ch:3
[ 480.040420] =====>rtl8192_set_chan()====ch:4
[ 480.160316] =====>rtl8192_set_chan()====ch:5
[ 480.280181] =====>rtl8192_set_chan()====ch:6
[ 480.400039] =====>rtl8192_set_chan()====ch:7
[ 480.519937] =====>rtl8192_set_chan()====ch:8
[ 480.639949] =====>rtl8192_set_chan()====ch:9
[ 480.759647] =====>rtl8192_set_chan()====ch:10
[ 480.879483] =====>rtl8192_set_chan()====ch:11
[ 480.999424] =====>rtl8192_set_chan()====ch:12
[ 481.119290] =====>rtl8192_set_chan()====ch:13
[ 481.239199] =====>rtl8192_set_chan()====ch:1
[ 481.250154] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 481.250165] rtl8192_update_cap(): WLAN_CAPABILITY_SHORT_PREAMBLE
[ 481.255013] notify_wx_assoc_event(): Tell user space disconnected
[ 481.255044] Linking with MIT,channel:6, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 481.255108] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 481.255350] ===>rtllib_associate_procedure_wq(), chan:6
[ 481.255353] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 481.255357] =====>rtl8192_set_chan()====ch:6
[ 481.292927] Linking with MIT,channel:1, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 481.293782] ===>rtllib_associate_procedure_wq(), chan:1
[ 481.293791] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 481.293801] =====>rtl8192_set_chan()====ch:1
[ 481.528555] rtllib: received DELBA while QOS or HT is not supported(0, 1)
[ 483.796486] Linking with MIT,channel:1, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 483.796505] ===>rtllib_associate_procedure_wq(), chan:1
[ 483.796511] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 483.796517] =====>rtl8192_set_chan()====ch:1
[ 486.303883] Linking with MIT,channel:1, qos:1, myHT:1, networkHT:1,
mode:10 cur_net.flags:0x40e
[ 486.303895] ===>rtllib_associate_procedure_wq(), chan:1
[ 486.303899] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 486.303902] =====>rtl8192_set_chan()====ch:1
[ 486.356465] rtl8192_SetWirelessMode(), wireless_mode:10, bEnableHT = 1
[ 486.409854] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:0:2b
[ 486.409862] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:1:4f
[ 486.409867] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:2:22
[ 486.409873] SetHwReg8192SE():HW_VAR_AC_PARAM eACI:3:22
[ 486.409883] Associated successfully
[ 486.409887] normal associate
[ 486.409905] Using G rates:108
[ 486.409909] Successfully associated, ht enabled
[ 486.409914] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 486.409920] =====>rtl8192_set_chan()====ch:1
[ 486.420769] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 486.420779] rtl8192_update_cap(): WLAN_CAPABILITY_SHORT_PREAMBLE
[ 486.432060] ====>rx ADDBAREQ from :00:23:eb:d1:cb:e2
[ 486.432071] ====>to send ADDBARSP
[ 512.984431] rtl8192_hw_sleep_down(): RF Change in progress!
[ 518.981534] rtl8192_hw_wakeup(): RF Change in progress! schedule
wake up task again
^ permalink raw reply
* Re: rtl8192 does not see N networks in my building
From: Larry Finger @ 2010-12-17 18:36 UTC (permalink / raw)
To: Amos Blanton; +Cc: linux-wireless
In-Reply-To: <AANLkTikKtc4uiXN+oHwDr8sPFXZCe3HvTfYSvgZ8uYx0@mail.gmail.com>
On 12/17/2010 11:20 AM, Amos Blanton wrote:
> Greetings. I have a rtl8192 in a Strata 13 laptop from Zareason
> running Ubuntu 10.10, and I work in an environment with many Wifi
> networks. With my previous laptop I was often able to see and
> sometimes login to a local un-encrypted N network, the best we have
> around here, but this one doesn't seem to find and display that
> network via Network Manager.
> I'm told my office has cisco ap1252s running the latest 7.0 code
> release. There are B/G as well as N networks here, at least 10 that
> Network manager will recognize.
>
> Sorry, I'm not sure what the relevant DMSG info is, so I'll include
> the latest swath. Please let me know if I should get additional info,
> and if this is the right place to report these issues.
> Thanks to everyone here who helps make Linux wireless work!
This is the right place to ask. The driver you are using is from staging, and I
don't know much about it, but let's see what we can do.
Please provide the output of the command '/sbin/lspci -nn | grep Realtek'.
In addition, please post the output of the command 'sudo /usr/sbin/iwlist scan'.
I'm guessing at the location of iwlist on your distro. If the command is not
found, then the patch is wrong - change it to match your system.
Larry
^ permalink raw reply
* Re: [PATCH] rtl8192ce: Update MAINTAINERS
From: Hauke Mehrtens @ 2010-12-17 19:17 UTC (permalink / raw)
To: Larry Finger; +Cc: John W Linville, linux-wireless
In-Reply-To: <4d0a2c91.Nuemy+kBaD1fOuX+%Larry.Finger@lwfinger.net>
On 12/16/2010 04:13 PM, Larry Finger wrote:
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> ---
>
> Index: wireless-testing/MAINTAINERS
> ===================================================================
> --- wireless-testing.orig/MAINTAINERS
> +++ wireless-testing/MAINTAINERS
> @@ -5055,6 +5055,16 @@ T: git git://git.kernel.org/pub/scm/linu
> S: Maintained
> F: drivers/net/wireless/rtl818x/rtl8187*
>
> +RTL8192CE WIRELESS DRIVER
> +M: Larry Finger <Larry.Finger@lwfinger.net>
> +M: Chaoming Li <chaoming_li@realsil.com.cn>
> +L: linux-wireless@vger.kernel.org
> +W: http://linuxwireless.org/
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
> +S: Maintained
> +F: drivers/net/wireless/rtlwifi/
> +F: drivers/net/wireless/rtl8192ce/
This path is wrong, it should be drivers/net/wireless/rtlwifi/rtl8192ce/
at least the driver is not in rivers/net/wireless/rtl8192ce/.
Hauke
^ permalink raw reply
* RE: [PATCH] mwifiex: use debugfs_remove_recursive()
From: Bing Zhao @ 2010-12-17 19:23 UTC (permalink / raw)
To: John W. Linville
Cc: linux-wireless@vger.kernel.org, Johannes Berg, Amitkumar Karwar,
Kiran Divekar, Frank Huang
In-Reply-To: <20101217142653.GC2398@tuxdriver.com>
Hi John,
> -----Original Message-----
> From: John W. Linville [mailto:linville@tuxdriver.com]
> Sent: Friday, December 17, 2010 6:27 AM
> To: Bing Zhao
> Cc: linux-wireless@vger.kernel.org; Johannes Berg; Amitkumar Karwar; Kiran Divekar; Frank Huang
> Subject: Re: [PATCH] mwifiex: use debugfs_remove_recursive()
>
> On Thu, Dec 16, 2010 at 07:56:46PM -0800, Bing Zhao wrote:
> > From: Amitkumar Karwar <akarwar@marvell.com>
> >
> > instead of keeping pointers to all entries.
> >
> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> > Signed-off-by: Kiran Divekar <dkiran@marvell.com>
>
> Just for the record, I'm not tracking any of the mwifiex patches at
> this time. Are you pushing them to a public git tree?
I have pushed all mwifiex patches to Marvell public git tree:
git://git.marvell.com/mwifiex.git
http://git.marvell.com/?p=mwifiex.git;a=summary
I will let you know as soon as we finish all open items commented by you, Johannes and other reviewers.
Thanks,
Bing
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: [PATCH] rtl8192ce: Update MAINTAINERS
From: Larry Finger @ 2010-12-17 19:24 UTC (permalink / raw)
To: Hauke Mehrtens; +Cc: John W Linville, linux-wireless
In-Reply-To: <4D0BB739.3020700@hauke-m.de>
On 12/17/2010 01:17 PM, Hauke Mehrtens wrote:
> On 12/16/2010 04:13 PM, Larry Finger wrote:
>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> ---
>>
>> Index: wireless-testing/MAINTAINERS
>> ===================================================================
>> --- wireless-testing.orig/MAINTAINERS
>> +++ wireless-testing/MAINTAINERS
>> @@ -5055,6 +5055,16 @@ T: git git://git.kernel.org/pub/scm/linu
>> S: Maintained
>> F: drivers/net/wireless/rtl818x/rtl8187*
>>
>> +RTL8192CE WIRELESS DRIVER
>> +M: Larry Finger <Larry.Finger@lwfinger.net>
>> +M: Chaoming Li <chaoming_li@realsil.com.cn>
>> +L: linux-wireless@vger.kernel.org
>> +W: http://linuxwireless.org/
>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
>> +S: Maintained
>> +F: drivers/net/wireless/rtlwifi/
>> +F: drivers/net/wireless/rtl8192ce/
> This path is wrong, it should be drivers/net/wireless/rtlwifi/rtl8192ce/
> at least the driver is not in rivers/net/wireless/rtl8192ce/.
Yes, it should be drivers/net/wireless/rtlwifi/rtl8192ce/.
Thanks,
Larry
^ permalink raw reply
* Re: [RFC 3/8] cfg80211: pass DFS region to drivers through reg_notifier()
From: Luis R. Rodriguez @ 2010-12-17 19:38 UTC (permalink / raw)
To: Senthil Balasubramanian; +Cc: linux-wireless@vger.kernel.org, Luis Rodriguez
In-Reply-To: <20101217063957.GB1381@senthil-lnx.users.atheros.com>
On Thu, Dec 16, 2010 at 10:39 PM, Senthil Balasubramanian
<senthilkumar@atheros.com> wrote:
>> diff --git a/drivers/net/wireless/ath/regd.c b/drivers/net/wireless/ath/regd.c
>> index 2b14775..426b514 100644
>> --- a/drivers/net/wireless/ath/regd.c
>> +++ b/drivers/net/wireless/ath/regd.c
>> @@ -337,7 +337,8 @@ static void ath_reg_apply_world_flags(struct wiphy *wiphy,
>>
>> int ath_reg_notifier_apply(struct wiphy *wiphy,
>> struct regulatory_request *request,
>> - struct ath_regulatory *reg)
>> + struct ath_regulatory *reg,
>> + u16 dfs_region)
> may be we can maintain consistency of dfs_regsion type. It's u8 everywhere
> except here..???
Good catch yes, that was a typo.
Luis
^ permalink raw reply
* Re: rtl8192 does not see N networks in my building
From: Amos Blanton @ 2010-12-17 19:40 UTC (permalink / raw)
To: Larry Finger; +Cc: linux-wireless
In-Reply-To: <4D0BADBE.40101@lwfinger.net>
Here's lspci output:
$ lspci -nn | grep Realtek
01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
RTL8191SEvB Wireless LAN Controller [10ec:8172] (rev 10)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
03)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
06)
lightnin@Buford:~$
iwlist:
lightnin@Buford:~$ iwlist scan
lo Interface doesn't support scanning.
eth1 Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wlan0 No scan results
Here's iwconfig output, in case that is helpful:
wlan0 802.11bgn Nickname:"rtl8191SEVA2"
Mode:Managed Frequency=2.462 GHz Access Point: Not-Associated
Bit Rate:300 Mb/s
Retry:on RTS thr:off Fragment thr:off
Power Management:off
Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
On Fri, Dec 17, 2010 at 1:36 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> On 12/17/2010 11:20 AM, Amos Blanton wrote:
>> Greetings. I have a rtl8192 in a Strata 13 laptop from Zareason
>> running Ubuntu 10.10, and I work in an environment with many Wifi
>> networks. With my previous laptop I was often able to see and
>> sometimes login to a local un-encrypted N network, the best we have
>> around here, but this one doesn't seem to find and display that
>> network via Network Manager.
>> I'm told my office has cisco ap1252s running the latest 7.0 code
>> release. There are B/G as well as N networks here, at least 10 that
>> Network manager will recognize.
>>
>> Sorry, I'm not sure what the relevant DMSG info is, so I'll include
>> the latest swath. Please let me know if I should get additional info,
>> and if this is the right place to report these issues.
>> Thanks to everyone here who helps make Linux wireless work!
>
> This is the right place to ask. The driver you are using is from staging, and I
> don't know much about it, but let's see what we can do.
>
> Please provide the output of the command '/sbin/lspci -nn | grep Realtek'.
>
> In addition, please post the output of the command 'sudo /usr/sbin/iwlist scan'.
> I'm guessing at the location of iwlist on your distro. If the command is not
> found, then the patch is wrong - change it to match your system.
>
> Larry
>
^ permalink raw reply
* Re: [RFC 3/8] cfg80211: pass DFS region to drivers through reg_notifier()
From: Luis R. Rodriguez @ 2010-12-17 19:40 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
In-Reply-To: <1292579457.3715.2.camel@jlt3.sipsolutions.net>
On Fri, Dec 17, 2010 at 1:50 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Thu, 2010-12-16 at 19:23 -0800, Luis R. Rodriguez wrote:
>
>> /* Lets us get back the wiphy on the callback */
>> int (*reg_notifier)(struct wiphy *wiphy,
>> - struct regulatory_request *request);
>> + struct regulatory_request *request,
>> + u8 dfs_region);
>
> So does that mean we need to implement a reg_notifier if we want to have
> radar detection? Doesn't an empty reg_notifier already alter behaviour
An empty reg_notifier() should not do anything. Its either through the
reg_notifier() or we add a new callback specifically for DFS. A new
callback may give more flexibility later if we want to pass up more
data.
Luis
^ permalink raw reply
* Re: [PATCH] ath9k: Properly initialize channel table for 2GHz
From: Luis R. Rodriguez @ 2010-12-17 19:51 UTC (permalink / raw)
To: Mohammed Shafi Shajakhan; +Cc: linville, linux-wireless
In-Reply-To: <1292598876-8242-1-git-send-email-mshajakhan@atheros.com>
On Fri, Dec 17, 2010 at 7:14 AM, Mohammed Shafi Shajakhan
<mshajakhan@atheros.com> wrote:
> From: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
>
> ath9k channel table for 2Ghz does not seems to initialize the 'band'
> parameter.Though it does not seems to cause any visible issue it looks
> odd when we initialize the 'band' parameter for 5Ghz channel table while
> not so for 2Ghz.
>
> Signed-off-by: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
> ---
> drivers/net/wireless/ath/ath9k/init.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/init.c b/drivers/net/wireless/ath/ath9k/init.c
> index 1238795..b0e5e71 100644
> --- a/drivers/net/wireless/ath/ath9k/init.c
> +++ b/drivers/net/wireless/ath/ath9k/init.c
> @@ -48,6 +48,7 @@ MODULE_PARM_DESC(pmqos, "User specified PM-QOS value");
> /* We use the hw_value as an index into our private channel structure */
>
> #define CHAN2G(_freq, _idx) { \
> + .band = IEEE80211_BAND_2GHZ, \
> .center_freq = (_freq), \
> .hw_value = (_idx), \
> .max_power = 20, \
That's fine but its not needed at all as the band is already
kzalloc()'d so it gets zeroed out and the IEEE80211_BAND_2GHZ enum is
0, so its not required to be explicit and set it. But if it gives you
the warm fuzzies sure.
Luis
^ permalink raw reply
* Re: [RFC 2/8] cfg80211: process new country regulatory flags (DFS)
From: Luis R. Rodriguez @ 2010-12-17 19:34 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
In-Reply-To: <1292579343.3715.1.camel@jlt3.sipsolutions.net>
On Fri, Dec 17, 2010 at 1:49 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Thu, 2010-12-16 at 19:23 -0800, Luis R. Rodriguez wrote:
>
>> + * @NL80211_ATTR_REG_COUNTRY_FLAGS: Country specific regulatory flags.
>> + * These are @NL80211_CFLAG_DFS_FCC_*
>
> How many FCCs are there? ;-)
Heh, yeah thanks.
Luis
^ permalink raw reply
* Re: rtl8192 does not see N networks in my building
From: Larry Finger @ 2010-12-17 19:57 UTC (permalink / raw)
To: Amos Blanton; +Cc: linux-wireless
In-Reply-To: <AANLkTimvazto71m6SPMYtSAGuQkNpab+kMZcF4buNqYa@mail.gmail.com>
On 12/17/2010 01:40 PM, Amos Blanton wrote:
> Here's lspci output:
>
> $ lspci -nn | grep Realtek
> 01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
> RTL8191SEvB Wireless LAN Controller [10ec:8172] (rev 10)
> 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
> 03)
> 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
> 06)
> lightnin@Buford:~$
The report I have from Realtek is that a mac80211 driver for that device is
nearing completion. I originally thought that you were using a staging driver,
but you must be using a driver from Realtek's site. Do you have the latest? I
show it to be rtl8192se_linux_2.6.0018.1025.2010. As I recall, that one does not
work on a 64-bit system.
> iwlist:
> lightnin@Buford:~$ iwlist scan
> lo Interface doesn't support scanning.
>
> eth1 Interface doesn't support scanning.
>
> eth0 Interface doesn't support scanning.
>
> wlan0 No scan results
You need to run iwlist as root to get an active scan. That is why I specified
the "sudo iwlist scan". Your prompt above looks like the regular user one. If
I'm wrong there, then something is blocking transmission. Is the module rfkill
loaded?
Larry
^ permalink raw reply
* Compat-wireless release for 2010-12-17 is baked
From: Compat-wireless cronjob account @ 2010-12-17 20:04 UTC (permalink / raw)
To: linux-wireless
>From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
03f2848..c3a9014 history -> origin/history
+ 46f736e...e935fc8 master -> origin/master (forced update)
a4851d8..b3444d1 stable -> origin/stable
* [new tag] next-20101217 -> next-20101217
>From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
* [new tag] v2.6.37-rc6 -> v2.6.37-rc6
compat-wireless code metrics
753675 - Total upstream lines of code being pulled
^ permalink raw reply
* new iwlwifi 6030 uCode available
From: Guy, Wey-Yi @ 2010-12-17 21:08 UTC (permalink / raw)
To: linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Hi,
Version 17.168.5.1 of uCode for Intel Intel@ 6030 Series Wi-Fi Adapters
is now available for download from
http://intellinuxwireless.org/?n=Downloads
Wey
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox