On Thu, Jan 23, 2014 at 2:57 PM, Emmanuel Grumbach <egrumbach@xxxxxxxxx> wrote: > On Thu, Jan 23, 2014 at 11:21 AM, Liu, Bopeng <Bopeng.Liu@xxxxxxxxxxxxx> wrote: >> >> >> So,it that mean: there is no way to fix this problem by modify the kernel and driver codes? > Yes > >> >> Though #iwconfig wlan0 shows there is modes a ? > > In client mode - not in AP mode >> Well in Us channel 149/36 is a valid channel for AP operation. So ideally it should work? Is there any specific feature blocking such in iwlwifi? can you try building iwlwifi with CONFIG_IWLWIFI_DEBUG from make menuconfig? It prints out the reg rules it read from eeprom? Also please post the full dmesg. >> iwconfig wlan0 >> wlan0 IEEE 802.11abgn ESSID:"IDPDK-169c" >> Mode:Managed Frequency:2.462 GHz Access Point: A0:88:B4:1E:16:9C >> Bit Rate=1 Mb/s Tx-Power=15 dBm >> Retry long limit:7 RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> Link Quality=60/70 Signal level=-50 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:14 Missed beacon:0 >> -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
