Re: Problem with the wifi
Arend van Spriel ha scritto: On 09-08-17 18:40, Larry Finger wrote: On 08/08/2017 04:10 AM, Arend van Spriel wrote: + linux-wireless + Larry please keep linux-wireless in this thread. On 08-08-17 08:21, Paolo Bettini wrote: Arend van Spriel ha scritto: + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 linux id or Broadcom AP6212 for windowsi installed deb package firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded bcrmfmac module but nothing the card seems invisible or dead i don't know if is a problem of firmware or my system cannot detect the sdio card ...do you know something about this problematic ? As always a kernel log could help or output from dmesg command. Also can you run following commands: $ ls /sys/bus/sdio/devices $ cat /sys/bus/sdio/devices/*/modalias Regards, Arend paolo@paolo:~$ ls /sys/bus/sdio/devices mmc1:0001:1 paolo@paolo:~$ paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 paolo@paolo:~$ sorry for previous mail ls was from another pc:-[ it seems the system see only the card where the system is installed Hi Paolo, Interesting. Now if Google search is correct the vendor id for this device indicates this is a Realtek (v024C) WLAN (c07) device. So what makes you say its linux id is 02d0:a9a6? In upstream linux I do not see any SDIO device drivers in realtek folder. Maybe Larry can provide clue/hint if a driver for this device is publicly available somewhere. Paolo, The only Realtek SDIO device in common distribution is the RTL8723BS, which has been packaged with some Intel processors, and may now be part of other SBC's. This driver has been in staging since V4.12. It handles SDIO Vendor code 0x024c with device codes 0x0523, 0x0623, 0x0626, and 0xb723. If your device is one of these, then you only need to build a kernel with this driver enabled. He has device id 0xb723: paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 So that driver should at least try to probe his device. Regards, Arend I built my own kernel in the debian way , very simple and amusing , i removed some modules not interesting , i set to M rtl8723bs and all ok !!! only a bit long the building with my dual core ,The bluetooth needs rtk_hciattach of Larry Finger , however strange the new debian kernels above all 4.13rc have not set rtl8723bs module. Best regards rtk_hciattach
Re: Problem with the wifi
Arend van Spriel ha scritto: On 09-08-17 18:40, Larry Finger wrote: On 08/08/2017 04:10 AM, Arend van Spriel wrote: + linux-wireless + Larry please keep linux-wireless in this thread. On 08-08-17 08:21, Paolo Bettini wrote: Arend van Spriel ha scritto: + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 linux id or Broadcom AP6212 for windowsi installed deb package firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded bcrmfmac module but nothing the card seems invisible or dead i don't know if is a problem of firmware or my system cannot detect the sdio card ...do you know something about this problematic ? As always a kernel log could help or output from dmesg command. Also can you run following commands: $ ls /sys/bus/sdio/devices $ cat /sys/bus/sdio/devices/*/modalias Regards, Arend paolo@paolo:~$ ls /sys/bus/sdio/devices mmc1:0001:1 paolo@paolo:~$ paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 paolo@paolo:~$ sorry for previous mail ls was from another pc:-[ it seems the system see only the card where the system is installed Hi Paolo, Interesting. Now if Google search is correct the vendor id for this device indicates this is a Realtek (v024C) WLAN (c07) device. So what makes you say its linux id is 02d0:a9a6? In upstream linux I do not see any SDIO device drivers in realtek folder. Maybe Larry can provide clue/hint if a driver for this device is publicly available somewhere. Paolo, The only Realtek SDIO device in common distribution is the RTL8723BS, which has been packaged with some Intel processors, and may now be part of other SBC's. This driver has been in staging since V4.12. It handles SDIO Vendor code 0x024c with device codes 0x0523, 0x0623, 0x0626, and 0xb723. If your device is one of these, then you only need to build a kernel with this driver enabled. He has device id 0xb723: paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 So that driver should at least try to probe his device. Regards, Arend Hi Arend on debian is avaible only an experimental trunk of mainline 4.12 and the RTL8723BS module is not activated i suppose , i tried this guide https://github.com/hadess/rtl8723bs/wiki/RTL8723BS-module-building-instruction-for-Debian-GNU-Linux but doens't NOTHING the make command ( obviously i installed all the necessary ) in the zip there are the firmware *.bin maybe i must wait the 4,12 backports i could compile my own kernel but in this moment ain't much time. Paolo
Re: Problem with the wifi
On 09-08-17 18:40, Larry Finger wrote: On 08/08/2017 04:10 AM, Arend van Spriel wrote: + linux-wireless + Larry please keep linux-wireless in this thread. On 08-08-17 08:21, Paolo Bettini wrote: Arend van Spriel ha scritto: + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 linux id or Broadcom AP6212 for windowsi installed deb package firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded bcrmfmac module but nothing the card seems invisible or dead i don't know if is a problem of firmware or my system cannot detect the sdio card ...do you know something about this problematic ? As always a kernel log could help or output from dmesg command. Also can you run following commands: $ ls /sys/bus/sdio/devices $ cat /sys/bus/sdio/devices/*/modalias Regards, Arend paolo@paolo:~$ ls /sys/bus/sdio/devices mmc1:0001:1 paolo@paolo:~$ paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 paolo@paolo:~$ sorry for previous mail ls was from another pc:-[ it seems the system see only the card where the system is installed Hi Paolo, Interesting. Now if Google search is correct the vendor id for this device indicates this is a Realtek (v024C) WLAN (c07) device. So what makes you say its linux id is 02d0:a9a6? In upstream linux I do not see any SDIO device drivers in realtek folder. Maybe Larry can provide clue/hint if a driver for this device is publicly available somewhere. Paolo, The only Realtek SDIO device in common distribution is the RTL8723BS, which has been packaged with some Intel processors, and may now be part of other SBC's. This driver has been in staging since V4.12. It handles SDIO Vendor code 0x024c with device codes 0x0523, 0x0623, 0x0626, and 0xb723. If your device is one of these, then you only need to build a kernel with this driver enabled. He has device id 0xb723: paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 So that driver should at least try to probe his device. Regards, Arend
Re: Problem with the wifi
On 08/08/2017 04:10 AM, Arend van Spriel wrote: + linux-wireless + Larry please keep linux-wireless in this thread. On 08-08-17 08:21, Paolo Bettini wrote: Arend van Spriel ha scritto: + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 linux id or Broadcom AP6212 for windowsi installed deb package firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded bcrmfmac module but nothing the card seems invisible or dead i don't know if is a problem of firmware or my system cannot detect the sdio card ...do you know something about this problematic ? As always a kernel log could help or output from dmesg command. Also can you run following commands: $ ls /sys/bus/sdio/devices $ cat /sys/bus/sdio/devices/*/modalias Regards, Arend paolo@paolo:~$ ls /sys/bus/sdio/devices mmc1:0001:1 paolo@paolo:~$ paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 paolo@paolo:~$ sorry for previous mail ls was from another pc:-[ it seems the system see only the card where the system is installed Hi Paolo, Interesting. Now if Google search is correct the vendor id for this device indicates this is a Realtek (v024C) WLAN (c07) device. So what makes you say its linux id is 02d0:a9a6? In upstream linux I do not see any SDIO device drivers in realtek folder. Maybe Larry can provide clue/hint if a driver for this device is publicly available somewhere. Paolo, The only Realtek SDIO device in common distribution is the RTL8723BS, which has been packaged with some Intel processors, and may now be part of other SBC's. This driver has been in staging since V4.12. It handles SDIO Vendor code 0x024c with device codes 0x0523, 0x0623, 0x0626, and 0xb723. If your device is one of these, then you only need to build a kernel with this driver enabled. I have had very little to do with this driver, other than posting the original version on GitHub. From there, many users have modified it until it was submitted to staging by Hans de Goede of RedHat. Larry
Re: Problem with the wifi
+ linux-wireless + Larry Jesus christ..grow some ears! On 08-08-17 11:21, Paolo Bettini wrote: > Arend van Spriel ha scritto: >> + linux-wireless >> + Larry >> >> please keep linux-wireless in this thread. >> >> On 08-08-17 08:21, Paolo Bettini wrote: >>> Arend van Spriel ha scritto: + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: > Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One > problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 > linux id or Broadcom AP6212 for windowsi installed deb package > firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded > bcrmfmac module but nothing the card seems invisible or dead i don't > know if is a problem of firmware or my system cannot detect the sdio > card ...do you know something about this problematic ? As always a kernel log could help or output from dmesg command. Also can you run following commands: $ ls /sys/bus/sdio/devices $ cat /sys/bus/sdio/devices/*/modalias Regards, Arend >>> paolo@paolo:~$ ls /sys/bus/sdio/devices >>> mmc1:0001:1 >>> paolo@paolo:~$ >>> >>> >>> paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 >>> paolo@paolo:~$ sorry for previous mail ls was from another pc:-[ >>> it seems the system see only the card where the system is installed >> Hi Paolo, >> >> Interesting. Now if Google search is correct the vendor id for this >> device indicates this is a Realtek (v024C) WLAN (c07) device. So what >> makes you say its linux id is 02d0:a9a6? >> >> In upstream linux I do not see any SDIO device drivers in realtek >> folder. Maybe Larry can provide clue/hint if a driver for this device is >> publicly available somewhere. >> >> Regards, >> Arend > Excuse me if i am boring you again , for me the wifi card of the ezbook2 > is a ghost ...but googling it is a broadcom infact with this command i have You are not boring anyone, but you really should ask the manufacturer. All I can say is your sysfs shows there is only one SDIO device with vendor id 0x024c (Realtek) and class 0x07 (WLAN) so brcmfmac will not be probed for that as all aliases below for brcmfmac are listing vendor id 0x02d0 (Broadcom). That is all the command below indicates. Regards, Arend > paolo@paolo:~$ grep sdio /lib/modules/`uname -r`/modules.alias > alias sdio:c*v0271d0418* ath6kl_sdio > alias sdio:c*v0271d0402* ath6kl_sdio > alias sdio:c*v0271d0401* ath6kl_sdio > alias sdio:c*v0271d0400* ath6kl_sdio > alias sdio:c*v0271d0301* ath6kl_sdio > alias sdio:c*v0271d0300* ath6kl_sdio > alias sdio:c*v02D0d4356* brcmfmac > alias sdio:c*v02D0d4354* brcmfmac > alias sdio:c*v02D0dA9BF* brcmfmac > alias sdio:c*v02D0d4345* brcmfmac > alias sdio:c*v02D0dA9A6* brcmfmac > alias sdio:c*v02D0d4339* brcmfmac > alias sdio:c*v02D0d4335* brcmfmac > alias sdio:c*v02D0dA962* brcmfmac > alias sdio:c*v02D0dA94D* brcmfmac > alias sdio:c*v02D0dA94C* brcmfmac > alias sdio:c*v02D0d4334* brcmfmac > alias sdio:c*v02D0d4330* brcmfmac > alias sdio:c*v02D0d4329* brcmfmac > alias sdio:c*v02D0d4324* brcmfmac > alias sdio:c*v02D0dA887* brcmfmac > alias sdio:c*v02DFd9104* libertas_sdio > alias sdio:c*v02DFd9103* libertas_sdio > alias sdio:c*v02DFd9141* mwifiex_sdio > alias sdio:c*v02DFd9139* mwifiex_sdio > alias sdio:c*v02DFd9135* mwifiex_sdio > alias sdio:c*v02DFd912D* mwifiex_sdio > alias sdio:c*v02DFd9129* mwifiex_sdio > alias sdio:c*v02DFd9119* mwifiex_sdio > alias sdio:c*v02DFd9116* mwifiex_sdio > alias sdio:c*v039Ad0800* smssdio > alias sdio:c*v039Ad0700* smssdio > alias sdio:c*v039Ad0600* smssdio > alias sdio:c*v039Ad0500* smssdio > alias sdio:c*v039Ad0302* smssdio > alias sdio:c*v039Ad0301* smssdio > alias sdio:c*v039Ad0300* smssdio > alias sdio:c*v039Ad0201* smssdio > alias sdio:c*v039Ad1100* smssdio > alias sdio:c*v039Ad5347* smssdio > alias sdio:c04v*d* sdio_uart > alias sdio:c01v*d* sdio_uart > alias sdio:c09v*d* btsdio > alias sdio:c03v*d* btsdio > alias sdio:c02v*d* btsdio > alias sdio:c*v02DFd9142* btmrvl_sdio > alias sdio:c*v02DFd912E* btmrvl_sdio > alias sdio:c*v02DFd9136* btmrvl_sdio > alias sdio:c*v02DFd912A* btmrvl_sdio > alias sdio:c*v02DFd911B* btmrvl_sdio > alias sdio:c*v02DFd911A* btmrvl_sdio > alias sdio:c*v02DFd9105* btmrvl_sdio > paolo@paolo:~$ >
Re: Problem with the wifi
+ linux-wireless + Larry please keep linux-wireless in this thread. On 08-08-17 08:21, Paolo Bettini wrote: > Arend van Spriel ha scritto: >> + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: >>> Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One >>> problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 >>> linux id or Broadcom AP6212 for windowsi installed deb package >>> firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded >>> bcrmfmac module but nothing the card seems invisible or dead i don't >>> know if is a problem of firmware or my system cannot detect the sdio >>> card ...do you know something about this problematic ? >> As always a kernel log could help or output from dmesg command. Also >> can you run following commands: $ ls /sys/bus/sdio/devices $ cat >> /sys/bus/sdio/devices/*/modalias Regards, Arend > paolo@paolo:~$ ls /sys/bus/sdio/devices > mmc1:0001:1 > paolo@paolo:~$ > > > paolo@paolo:~$ cat /sys/bus/sdio/devices/*/modalias sdio:c07v024CdB723 > paolo@paolo:~$ sorry for previous mail ls was from another pc:-[ > it seems the system see only the card where the system is installed Hi Paolo, Interesting. Now if Google search is correct the vendor id for this device indicates this is a Realtek (v024C) WLAN (c07) device. So what makes you say its linux id is 02d0:a9a6? In upstream linux I do not see any SDIO device drivers in realtek folder. Maybe Larry can provide clue/hint if a driver for this device is publicly available somewhere. Regards, Arend
Re: Problem with the wifi
+ linux-wireless On 07-08-17 21:38, Paolo Bettini wrote: > Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One > problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6 > linux id or Broadcom AP6212 for windowsi installed deb package > firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded > bcrmfmac module but nothing the card seems invisible or dead i don't > know if is a problem of firmware or my system cannot detect the sdio > card ...do you know something about this problematic ? As always a kernel log could help or output from dmesg command. Also can you run following commands: $ ls /sys/bus/sdio/devices $ cat /sys/bus/sdio/devices/*/modalias Regards, Arend
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Sat, 2016-07-23 at 06:26 -0700, Christopher Williamson wrote: > Quick follow-up - I suspected the issue may be with wpa_supplicant > rather than udev / kernel config. > > Since this does connect properly on open wireless networks the issue > is now only with WPA/WPA2. > > It seems even the latest dev builds of Ubuntu are still stuck using > wpa_supplicant 2.4.x rather than hopping over to 2.5 which I believe > contains a fix needed for the libertas chipset to properly > authenticate with WPA/WPA2 networks. > > I therefore decided to compile version 2.5 of wpa_supplicant myself > and install it on a Ubuntu 16.04.1 clean install - looks like that > actually fixed the problem. > > So the end result is - the ubuntu 2.4 wpa_supplicant doesn’t work > with > libertas+libertas_sdio but it *does* work properly with > wpa_supplicant > 2.5. Can you get supplicant logs for both 2.4 and 2.5 and we can maybe figure out what the difference is, just for the record? Dan > Christopher Williamson > > > On 23 July 2016 at 13:29:41, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > Just to follow up on this - I performed a minimal ubuntu server > > install (16.04.1), commented out the crda udev rule (since that was > > setting the weird country: 98 issue) and tried again and it still > > didn’t work. > > > > I did confirm that the md5 sums for the firmware included with Arch > > is the exact same as the firmware included for Ubuntu 16.04.1 so > > there was no difference there. > > > > At this point I’m thinking it’s either: > > > > - Some Ubuntu-specific udev rule breaking things or: > > - A difference in the kernel config between Arch and Ubuntu > > > > I think I’m going to forfeit for now and switch over to Arch - > > spent several days on this already. If anyone has any other ideas > > on what could be causing this please do let me know and I’ll follow > > up if I experiment this with again. > > > > Christopher Williamson > > > > > > > > > > On 22 July 2016 at 22:47:15, Christopher Williamson (home@chrisaw.c > > om(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > Hi all, > > > > > > So I decided to have another fiddle with this and managed to get > > > the WiFi working perfectly first time on an ArchLinux LiveCD so > > > it looks like this issue is Ubuntu specific. > > > > > > I’m going to copy the firmware files and check if they’re > > > responsible and work my way through the various differences but > > > at least I know this device can work properly on the Linux 4.6.3 > > > (which the livecd is based on.) > > > > > > I’ll follow up if and when I find out what the cause of the > > > problem was. > > > > > > Christopher Williamson > > > > > > > > > > > > > > > On 22 July 2016 at 22:42:50, Christopher Williamson (home@chrisaw > > > .com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > Hi all, > > > > > > > > So I decided to have another fiddle with this and managed to > > > > get the WiFi working perfectly first time on an ArchLinux > > > > LiveCD so it looks like this issue is Ubuntu specific. > > > > > > > > I’m going to copy the firmware files and check if they’re > > > > responsible and work my way through the various differences but > > > > at least I know this device can work properly on the Linux > > > > 4.6.3 (which the livecd is based on.) > > > > > > > > I’ll follow up if and when I find out what the cause of the > > > > problem was. > > > > Christopher Williamson > > > > www.chrisaw.com(http://www.chrisaw.com) > > > > > > > > > > > > > > > > > > > > On 22 July 2016 at 18:17:20, Christopher Williamson (home@chris > > > > aw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > > > > I haven’t managed to get connected to a WPA network either so > > > > > it looks like open only at the moment but I fear that may > > > > > just have been a fluke. > > > > > > > > > > A big problem I’m facing is that editing /etc/default/crda to > > > > > REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to > > > > > GB and I have to set it manually. This sometimes works and > > > > > sometimes reports the following: > > > > > > > > > > country 98: DFS-UNSET > > > > > (2402 - 2472 @ 40), (N/A, 20), (N/A) > > > > > (2457 - 2472 @ 15), (N/A, 20), (N/A), NO-IR > > > > > (5170 - 5250 @ 80), (N/A, 17), (N/A), NO-IR > > > > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR > > > > > (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR > > > > > (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR > > > > > (57240 - 63720 @ 2160), (N/A, 0), (N/A) > > > > > > > > > > At best this is simply an annoyance but at worst I’m thinking > > > > > this may be responsible for the issues I’m seeing. > > > > > > > > > > Is there anywhere else I can force this to be set to GB? > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > On 22 July 2016 at 17:54:40, Christopher Williamson (home@chr > > > > >
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Quick follow-up - I suspected the issue may be with wpa_supplicant rather than udev / kernel config. Since this does connect properly on open wireless networks the issue is now only with WPA/WPA2. It seems even the latest dev builds of Ubuntu are still stuck using wpa_supplicant 2.4.x rather than hopping over to 2.5 which I believe contains a fix needed for the libertas chipset to properly authenticate with WPA/WPA2 networks. I therefore decided to compile version 2.5 of wpa_supplicant myself and install it on a Ubuntu 16.04.1 clean install - looks like that actually fixed the problem. So the end result is - the ubuntu 2.4 wpa_supplicant doesn’t work with libertas+libertas_sdio but it *does* work properly with wpa_supplicant 2.5. Christopher Williamson On 23 July 2016 at 13:29:41, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > Just to follow up on this - I performed a minimal ubuntu server install > (16.04.1), commented out the crda udev rule (since that was setting the weird > country: 98 issue) and tried again and it still didn’t work. > > I did confirm that the md5 sums for the firmware included with Arch is the > exact same as the firmware included for Ubuntu 16.04.1 so there was no > difference there. > > At this point I’m thinking it’s either: > > - Some Ubuntu-specific udev rule breaking things or: > - A difference in the kernel config between Arch and Ubuntu > > I think I’m going to forfeit for now and switch over to Arch - spent several > days on this already. If anyone has any other ideas on what could be causing > this please do let me know and I’ll follow up if I experiment this with again. > > Christopher Williamson > > > > > On 22 July 2016 at 22:47:15, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > Hi all, > > > > So I decided to have another fiddle with this and managed to get the WiFi > > working perfectly first time on an ArchLinux LiveCD so it looks like this > > issue is Ubuntu specific. > > > > I’m going to copy the firmware files and check if they’re responsible and > > work my way through the various differences but at least I know this device > > can work properly on the Linux 4.6.3 (which the livecd is based on.) > > > > I’ll follow up if and when I find out what the cause of the problem was. > > > > Christopher Williamson > > > > > > > > > > On 22 July 2016 at 22:42:50, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > Hi all, > > > > > > So I decided to have another fiddle with this and managed to get the WiFi > > > working perfectly first time on an ArchLinux LiveCD so it looks like this > > > issue is Ubuntu specific. > > > > > > I’m going to copy the firmware files and check if they’re responsible and > > > work my way through the various differences but at least I know this > > > device can work properly on the Linux 4.6.3 (which the livecd is based > > > on.) > > > > > > I’ll follow up if and when I find out what the cause of the problem was. > > > Christopher Williamson > > > www.chrisaw.com(http://www.chrisaw.com) > > > > > > > > > > > > > > > On 22 July 2016 at 18:17:20, Christopher Williamson > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > I haven’t managed to get connected to a WPA network either so it looks > > > > like open only at the moment but I fear that may just have been a fluke. > > > > > > > > A big problem I’m facing is that editing /etc/default/crda to > > > > REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to GB and I > > > > have to set it manually. This sometimes works and sometimes reports the > > > > following: > > > > > > > > country 98: DFS-UNSET > > > > (2402 - 2472 @ 40), (N/A, 20), (N/A) > > > > (2457 - 2472 @ 15), (N/A, 20), (N/A), NO-IR > > > > (5170 - 5250 @ 80), (N/A, 17), (N/A), NO-IR > > > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR > > > > (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR > > > > (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR > > > > (57240 - 63720 @ 2160), (N/A, 0), (N/A) > > > > > > > > At best this is simply an annoyance but at worst I’m thinking this may > > > > be responsible for the issues I’m seeing. > > > > > > > > Is there anywhere else I can force this to be set to GB? > > > > > > > > Christopher Williamson > > > > > > > > > > > > On 22 July 2016 at 17:54:40, Christopher Williamson > > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > Disregard - I have actually managed to get this to connect to a open > > > > > network! > > > > > > > > > > # iw reg set GB > > > > > # iw reg get > > > > > country GB: DFS-ETSI > > > > > (2402 - 2482 @ 40), (N/A, 20), (N/A) > > > > > (5170 - 5250 @ 80), (N/A, 20), (N/A) > > > > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS > > > > > (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS > > > > > (57000 - 66000 @ 2160), (N/A, 40), (N/A) > > > > > # iwconfig wlan0 essid "shaunthesheep-guest” > > >
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Just to follow up on this - I performed a minimal ubuntu server install (16.04.1), commented out the crda udev rule (since that was setting the weird country: 98 issue) and tried again and it still didn’t work. I did confirm that the md5 sums for the firmware included with Arch is the exact same as the firmware included for Ubuntu 16.04.1 so there was no difference there. At this point I’m thinking it’s either: - Some Ubuntu-specific udev rule breaking things or: - A difference in the kernel config between Arch and Ubuntu I think I’m going to forfeit for now and switch over to Arch - spent several days on this already. If anyone has any other ideas on what could be causing this please do let me know and I’ll follow up if I experiment this with again. Christopher Williamson On 22 July 2016 at 22:47:15, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > Hi all, > > So I decided to have another fiddle with this and managed to get the WiFi > working perfectly first time on an ArchLinux LiveCD so it looks like this > issue is Ubuntu specific. > > I’m going to copy the firmware files and check if they’re responsible and > work my way through the various differences but at least I know this device > can work properly on the Linux 4.6.3 (which the livecd is based on.) > > I’ll follow up if and when I find out what the cause of the problem was. > > Christopher Williamson > > > > > On 22 July 2016 at 22:42:50, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > Hi all, > > > > So I decided to have another fiddle with this and managed to get the WiFi > > working perfectly first time on an ArchLinux LiveCD so it looks like this > > issue is Ubuntu specific. > > > > I’m going to copy the firmware files and check if they’re responsible and > > work my way through the various differences but at least I know this device > > can work properly on the Linux 4.6.3 (which the livecd is based on.) > > > > I’ll follow up if and when I find out what the cause of the problem was. > > Christopher Williamson > > www.chrisaw.com(http://www.chrisaw.com) > > > > > > > > > > On 22 July 2016 at 18:17:20, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > I haven’t managed to get connected to a WPA network either so it looks > > > like open only at the moment but I fear that may just have been a fluke. > > > > > > A big problem I’m facing is that editing /etc/default/crda to > > > REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to GB and I > > > have to set it manually. This sometimes works and sometimes reports the > > > following: > > > > > > country 98: DFS-UNSET > > > (2402 - 2472 @ 40), (N/A, 20), (N/A) > > > (2457 - 2472 @ 15), (N/A, 20), (N/A), NO-IR > > > (5170 - 5250 @ 80), (N/A, 17), (N/A), NO-IR > > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR > > > (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR > > > (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR > > > (57240 - 63720 @ 2160), (N/A, 0), (N/A) > > > > > > At best this is simply an annoyance but at worst I’m thinking this may be > > > responsible for the issues I’m seeing. > > > > > > Is there anywhere else I can force this to be set to GB? > > > > > > Christopher Williamson > > > > > > > > > On 22 July 2016 at 17:54:40, Christopher Williamson > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > Disregard - I have actually managed to get this to connect to a open > > > > network! > > > > > > > > # iw reg set GB > > > > # iw reg get > > > > country GB: DFS-ETSI > > > > (2402 - 2482 @ 40), (N/A, 20), (N/A) > > > > (5170 - 5250 @ 80), (N/A, 20), (N/A) > > > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS > > > > (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS > > > > (57000 - 66000 @ 2160), (N/A, 40), (N/A) > > > > # iwconfig wlan0 essid "shaunthesheep-guest” > > > > # dhclient wlan0 > > > > > > > > It’s good to have some progress - so it looks like the issue preventing > > > > the previous connection was the iw reg not being set properly (or > > > > possibly just wpa_supplicant borking the connection in some way. I > > > > stopped that this time around. I’ll try wpa1 now and report back. > > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > On 22 July 2016 at 17:39:50, Christopher Williamson > > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > > > > Ok so I created a guest wifi network without any encryption enabled > > > > > at all and the client still refuses to connect. > > > > > > > > > > Again, the connection is made perfectly using the USB dongle I have > > > > > but not the built in libertas sd8686 chipset. > > > > > > > > > > I do currently use pfSense as a firewall box behind my wireless > > > > > router (acting as an AP) and can see that no DHCP request is making > > > > > it to the pfSense box. I believe you are right in the point about the > > > > > firmware
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Hi all, So I decided to have another fiddle with this and managed to get the WiFi working perfectly first time on an ArchLinux LiveCD so it looks like this issue is Ubuntu specific. I’m going to copy the firmware files and check if they’re responsible and work my way through the various differences but at least I know this device can work properly on the Linux 4.6.3 (which the livecd is based on.) I’ll follow up if and when I find out what the cause of the problem was. Christopher Williamson On 22 July 2016 at 22:42:50, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > Hi all, > > So I decided to have another fiddle with this and managed to get the WiFi > working perfectly first time on an ArchLinux LiveCD so it looks like this > issue is Ubuntu specific. > > I’m going to copy the firmware files and check if they’re responsible and > work my way through the various differences but at least I know this device > can work properly on the Linux 4.6.3 (which the livecd is based on.) > > I’ll follow up if and when I find out what the cause of the problem was. > Christopher Williamson > www.chrisaw.com(http://www.chrisaw.com) > > > > > On 22 July 2016 at 18:17:20, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > I haven’t managed to get connected to a WPA network either so it looks like > > open only at the moment but I fear that may just have been a fluke. > > > > A big problem I’m facing is that editing /etc/default/crda to REGDOMAIN=GB > > wasn’t enough to set the wifi regulation mode to GB and I have to set it > > manually. This sometimes works and sometimes reports the following: > > > > country 98: DFS-UNSET > > (2402 - 2472 @ 40), (N/A, 20), (N/A) > > (2457 - 2472 @ 15), (N/A, 20), (N/A), NO-IR > > (5170 - 5250 @ 80), (N/A, 17), (N/A), NO-IR > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR > > (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR > > (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR > > (57240 - 63720 @ 2160), (N/A, 0), (N/A) > > > > At best this is simply an annoyance but at worst I’m thinking this may be > > responsible for the issues I’m seeing. > > > > Is there anywhere else I can force this to be set to GB? > > > > Christopher Williamson > > > > > > On 22 July 2016 at 17:54:40, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > Disregard - I have actually managed to get this to connect to a open > > > network! > > > > > > # iw reg set GB > > > # iw reg get > > > country GB: DFS-ETSI > > > (2402 - 2482 @ 40), (N/A, 20), (N/A) > > > (5170 - 5250 @ 80), (N/A, 20), (N/A) > > > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS > > > (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS > > > (57000 - 66000 @ 2160), (N/A, 40), (N/A) > > > # iwconfig wlan0 essid "shaunthesheep-guest” > > > # dhclient wlan0 > > > > > > It’s good to have some progress - so it looks like the issue preventing > > > the previous connection was the iw reg not being set properly (or > > > possibly just wpa_supplicant borking the connection in some way. I > > > stopped that this time around. I’ll try wpa1 now and report back. > > > > > > > > > Christopher Williamson > > > > > > > > > > > > On 22 July 2016 at 17:39:50, Christopher Williamson > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > Ok so I created a guest wifi network without any encryption enabled at > > > > all and the client still refuses to connect. > > > > > > > > Again, the connection is made perfectly using the USB dongle I have but > > > > not the built in libertas sd8686 chipset. > > > > > > > > I do currently use pfSense as a firewall box behind my wireless router > > > > (acting as an AP) and can see that no DHCP request is making it to the > > > > pfSense box. I believe you are right in the point about the firmware > > > > being the problem here. > > > > > > > > I should also confirm - the firmware in use is the latest from the > > > > linux-firmware Ubuntu 16.04 package. I did read around the net about > > > > being having various issues with various firmware sources and not > > > > others but despite trying firmware linked directly from Marvell I seem > > > > to always get one of two issues: > > > > > > > > 1.) I am unable to connect and keep getting asked for passphrases, or: > > > > 2.) The system completely freezes up (with the v8 firmwares I tried) > > > > > > > > I’m not really sure what else to try at this point. > > > > Christopher Williamson > > > > > > > > > > > > > > > > On 22 July 2016 at 17:24:52, Christopher Williamson > > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > > > > Hi Dan, > > > > > > > > > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > > > > > > > > > For now though - the iwlist scan results for both a USB device and the > > > > > libertas device: > > > > > > > > > > USB: http://termbin.com/hdwl > > > > > Libertas:
Re: Problem connecting to wifi on libertas_cpio (sd8686)
I haven’t managed to get connected to a WPA network either so it looks like open only at the moment but I fear that may just have been a fluke. A big problem I’m facing is that editing /etc/default/crda to REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to GB and I have to set it manually. This sometimes works and sometimes reports the following: country 98: DFS-UNSET (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2472 @ 15), (N/A, 20), (N/A), NO-IR (5170 - 5250 @ 80), (N/A, 17), (N/A), NO-IR (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR (57240 - 63720 @ 2160), (N/A, 0), (N/A) At best this is simply an annoyance but at worst I’m thinking this may be responsible for the issues I’m seeing. Is there anywhere else I can force this to be set to GB? Christopher Williamson On 22 July 2016 at 17:54:40, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > Disregard - I have actually managed to get this to connect to a open network! > > # iw reg set GB > # iw reg get > country GB: DFS-ETSI > (2402 - 2482 @ 40), (N/A, 20), (N/A) > (5170 - 5250 @ 80), (N/A, 20), (N/A) > (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS > (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS > (57000 - 66000 @ 2160), (N/A, 40), (N/A) > # iwconfig wlan0 essid "shaunthesheep-guest” > # dhclient wlan0 > > It’s good to have some progress - so it looks like the issue preventing the > previous connection was the iw reg not being set properly (or possibly just > wpa_supplicant borking the connection in some way. I stopped that this time > around. I’ll try wpa1 now and report back. > > > Christopher Williamson > > > > On 22 July 2016 at 17:39:50, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > Ok so I created a guest wifi network without any encryption enabled at all > > and the client still refuses to connect. > > > > Again, the connection is made perfectly using the USB dongle I have but not > > the built in libertas sd8686 chipset. > > > > I do currently use pfSense as a firewall box behind my wireless router > > (acting as an AP) and can see that no DHCP request is making it to the > > pfSense box. I believe you are right in the point about the firmware being > > the problem here. > > > > I should also confirm - the firmware in use is the latest from the > > linux-firmware Ubuntu 16.04 package. I did read around the net about being > > having various issues with various firmware sources and not others but > > despite trying firmware linked directly from Marvell I seem to always get > > one of two issues: > > > > 1.) I am unable to connect and keep getting asked for passphrases, or: > > 2.) The system completely freezes up (with the v8 firmwares I tried) > > > > I’m not really sure what else to try at this point. > > Christopher Williamson > > > > > > > > On 22 July 2016 at 17:24:52, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > Hi Dan, > > > > > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > > > > > For now though - the iwlist scan results for both a USB device and the > > > libertas device: > > > > > > USB: http://termbin.com/hdwl > > > Libertas: http://termbin.com/jxh7 > > > > > > Will follow up shortly with WPA and Open network configs. > > > > > > Christopher Williamson > > > > > > > > > > > > On 22 July 2016 at 17:16:29, Dan Williams > > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > > > Hi Dan, > > > > > > > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > > > > > > > For now though - the iwlist scan results for both a USB device and the > > > > libertas device: > > > > > > > > USB: http://termbin.com/hdwl > > > > Libertas: http://termbin.com/jxh7 > > > > > > > > Will follow up shortly with WPA and Open network configs. > > > > > > > > *Christopher Williamson* -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Disregard - I have actually managed to get this to connect to a open network! # iw reg set GB # iw reg get country GB: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A) # iwconfig wlan0 essid "shaunthesheep-guest” # dhclient wlan0 It’s good to have some progress - so it looks like the issue preventing the previous connection was the iw reg not being set properly (or possibly just wpa_supplicant borking the connection in some way. I stopped that this time around. I’ll try wpa1 now and report back. Christopher Williamson On 22 July 2016 at 17:39:50, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > Ok so I created a guest wifi network without any encryption enabled at all > and the client still refuses to connect. > > Again, the connection is made perfectly using the USB dongle I have but not > the built in libertas sd8686 chipset. > > I do currently use pfSense as a firewall box behind my wireless router > (acting as an AP) and can see that no DHCP request is making it to the > pfSense box. I believe you are right in the point about the firmware being > the problem here. > > I should also confirm - the firmware in use is the latest from the > linux-firmware Ubuntu 16.04 package. I did read around the net about being > having various issues with various firmware sources and not others but > despite trying firmware linked directly from Marvell I seem to always get one > of two issues: > > 1.) I am unable to connect and keep getting asked for passphrases, or: > 2.) The system completely freezes up (with the v8 firmwares I tried) > > I’m not really sure what else to try at this point. > Christopher Williamson > > > > On 22 July 2016 at 17:24:52, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > Hi Dan, > > > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > > > For now though - the iwlist scan results for both a USB device and the > > libertas device: > > > > USB: http://termbin.com/hdwl > > Libertas: http://termbin.com/jxh7 > > > > Will follow up shortly with WPA and Open network configs. > > > > Christopher Williamson > > > > > > > > On 22 July 2016 at 17:16:29, Dan Williams > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > Hi Dan, > > > > > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > > > > > For now though - the iwlist scan results for both a USB device and the > > > libertas device: > > > > > > USB: http://termbin.com/hdwl > > > Libertas: http://termbin.com/jxh7 > > > > > > Will follow up shortly with WPA and Open network configs. > > > > > > *Christopher Williamson* -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Ok so I created a guest wifi network without any encryption enabled at all and the client still refuses to connect. Again, the connection is made perfectly using the USB dongle I have but not the built in libertas sd8686 chipset. I do currently use pfSense as a firewall box behind my wireless router (acting as an AP) and can see that no DHCP request is making it to the pfSense box. I believe you are right in the point about the firmware being the problem here. I should also confirm - the firmware in use is the latest from the linux-firmware Ubuntu 16.04 package. I did read around the net about being having various issues with various firmware sources and not others but despite trying firmware linked directly from Marvell I seem to always get one of two issues: 1.) I am unable to connect and keep getting asked for passphrases, or: 2.) The system completely freezes up (with the v8 firmwares I tried) I’m not really sure what else to try at this point. Christopher Williamson On 22 July 2016 at 17:24:52, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > Hi Dan, > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > For now though - the iwlist scan results for both a USB device and the > libertas device: > > USB: http://termbin.com/hdwl > Libertas: http://termbin.com/jxh7 > > Will follow up shortly with WPA and Open network configs. > > Christopher Williamson > > > > On 22 July 2016 at 17:16:29, Dan Williams > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > Hi Dan, > > > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > > > For now though - the iwlist scan results for both a USB device and the > > libertas device: > > > > USB: http://termbin.com/hdwl > > Libertas: http://termbin.com/jxh7 > > > > Will follow up shortly with WPA and Open network configs. > > > > *Christopher Williamson* -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Hi Dan, I will check out the WPA2 vs WPA vs open wireless thing in a few mins. For now though - the iwlist scan results for both a USB device and the libertas device: USB: http://termbin.com/hdwl Libertas: http://termbin.com/jxh7 Will follow up shortly with WPA and Open network configs. Christopher Williamson On 22 July 2016 at 17:16:29, Dan Williams (d...@redhat.com(mailto:d...@redhat.com)) wrote: > Hi Dan, > > I will check out the WPA2 vs WPA vs open wireless thing in a few mins. > > For now though - the iwlist scan results for both a USB device and the > libertas device: > > USB: http://termbin.com/hdwl > Libertas: http://termbin.com/jxh7 > > Will follow up shortly with WPA and Open network configs. > > *Christopher Williamson* -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Fri, 2016-07-22 at 01:48 -0700, Christopher Williamson wrote: > Looking through the log lines I see gaps between what WPA is doing > and what > dmesg reports and figured this is because of the libertas debugging > level > so I’ve set that to 0xfff (for libertas) and created a combined > log of > the events from both sources labelled with either [wpa] or [dmesg] > and > timestamped which should help to give a much clearer combined > picture: > > http://termbin.com/sjqn > > I’ll have a look through and see if anything jumps out at me but I > wanted > to send it out to get expert eyes on it. Thanks. The ASSOC command looks OK, but do you have 'iw scan' output for shaunthesheep from a different card? Just to make sure that the passed-in rates and RSN IE is correct. The ASSOC command completes .5 seconds after it's sent, and the firmware returns a result that means "association response timeout". According to the API docs it doesn't look like this status code (1) comes from the AP, but from the firmware. I'm afraid at this point we'd need a second machine to listen on the channel and see if we can get the exchange between the marvell device and the AP. Can you test the device with a WPA-only AP, ie one that's not WPA2/RSN? Does it work with an open AP? Dan > As a side note - I really appreciate all of the help on this so far - > there’s a beer in it for all involved! :P > > Christopher Williamson > > > > On 22 July 2016 at 09:21:44, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > I was thinking about redirecting the wpa logging to syslog but > > figured I’d take the lazy way out by abusing curl: > > > > curl -s http://termbin.com/cx0e http://termbin.com/bvdj | sort > > > > Resulting combined log file: > > http://termbin.com/909y > > > > Christopher Williamson > > > > > > On 22 July 2016 at 09:09:59, Arend Van Spriel (arend.vanspriel@broa > > dcom.com(mailto:arend.vanspr...@broadcom.com)) wrote: > > > > > > > > On 22-7-2016 0:00, Christopher Williamson wrote: > > > > > > > > I’ve created cleaner logs (particularly the dmesg one) and have > > > > added > > > > timestamps line-by-line to both so it should be easier to track > > > > between the two log files: > > > > > > > > wpa_supplicant: > > > > http://termbin.com/cx0e > > > > > > > > dmesg | grep libertas: > > > > http://termbin.com/bvdj > > > You can make wpa_supplicant log to syslog. That way you get > > > kernel and > > > wpa_supplicant log in one file. > > > > > > Regards, > > > Arend > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > > > > > On 21 July 2016 at 22:00:02, Christopher Williamson > > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > > > > Sure! > > > > > > > > > > wpa_supplicant logs: > > > > > http://termbin.com/z1hg > > > > > > > > > > dmesg logs (grepped for libertas): > > > > > http://termbin.com/7rt5 > > > > > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > > > > > > > > > > On 21 July 2016 at 21:38:26, Dan Williams (d...@redhat.com(ma > > > > > ilto:d...@redhat.com)) wrote: > > > > > > > > > > > > > > > > > On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson > > > > > > wrote: > > > > > > > > > > > > > > Just to confirm - I can connect to the same network using > > > > > > > the same > > > > > > > configurations using a USB wifi adapter I tried. > > > > > > Can you grab simultaneous driver debug logging and > > > > > > supplicant debug > > > > > > logging? Unfortunately the 'status 1' is an unspecified > > > > > > failure, which > > > > > > could be from the AP or the firmware. > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > > > > > > > Unfortunately it’s not ideal since the point of the Viliv > > > > > > > N5 is that > > > > > > > it’s ultra portable so I would really like to get the > > > > > > > inbuilt wifi > > > > > > > card working. > > > > > > > > > > > > > > It seems odd that wpa_supplicant reports the connection > > > > > > > being > > > > > > > “rejected” as seen below: > > > > > > > > > > > > > > wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 > > > > > > > status_code=1 > > > > > > > > > > > > > > Most of the debug output sadly doesn’t mean a great deal > > > > > > > to me - wifi > > > > > > > isn’t really my area of expertise. > > > > > > > > > > > > > > On 21 July 2016 at 19:10:56, Christopher Williamson > > > > > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sure, here are the results: > > > > > > > > > > > > > > > > http://termbin.com/e8e2 > > > > > > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > > > > > > > > > On 21 July 2016 at 16:37:24, Dan Williams (dcbw@redhat. > > > > > > > > com(mailto:d > > > > > > > > c...@redhat.com)) wrote: > > > > > > > > > > > > > > > > > > > > > > >
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Looking through the log lines I see gaps between what WPA is doing and what dmesg reports and figured this is because of the libertas debugging level so I’ve set that to 0xfff (for libertas) and created a combined log of the events from both sources labelled with either [wpa] or [dmesg] and timestamped which should help to give a much clearer combined picture: http://termbin.com/sjqn I’ll have a look through and see if anything jumps out at me but I wanted to send it out to get expert eyes on it. As a side note - I really appreciate all of the help on this so far - there’s a beer in it for all involved! :P Christopher Williamson On 22 July 2016 at 09:21:44, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > I was thinking about redirecting the wpa logging to syslog but figured I’d > take the lazy way out by abusing curl: > > curl -s http://termbin.com/cx0e http://termbin.com/bvdj | sort > > Resulting combined log file: > http://termbin.com/909y > > Christopher Williamson > > > On 22 July 2016 at 09:09:59, Arend Van Spriel > (arend.vanspr...@broadcom.com(mailto:arend.vanspr...@broadcom.com)) wrote: > > > On 22-7-2016 0:00, Christopher Williamson wrote: > > > I’ve created cleaner logs (particularly the dmesg one) and have added > > > timestamps line-by-line to both so it should be easier to track > > > between the two log files: > > > > > > wpa_supplicant: > > > http://termbin.com/cx0e > > > > > > dmesg | grep libertas: > > > http://termbin.com/bvdj > > > > You can make wpa_supplicant log to syslog. That way you get kernel and > > wpa_supplicant log in one file. > > > > Regards, > > Arend > > > > > Christopher Williamson > > > > > > > > > > > > > > > On 21 July 2016 at 22:00:02, Christopher Williamson > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > >> Sure! > > >> > > >> wpa_supplicant logs: > > >> http://termbin.com/z1hg > > >> > > >> dmesg logs (grepped for libertas): > > >> http://termbin.com/7rt5 > > >> > > >> > > >> Christopher Williamson > > >> > > >> > > >> > > >> > > >> On 21 July 2016 at 21:38:26, Dan Williams > > >> (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > >> > > >>> On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote: > > Just to confirm - I can connect to the same network using the same > > configurations using a USB wifi adapter I tried. > > >>> > > >>> Can you grab simultaneous driver debug logging and supplicant debug > > >>> logging? Unfortunately the 'status 1' is an unspecified failure, which > > >>> could be from the AP or the firmware. > > >>> > > >>> Dan > > >>> > > >>> > > Unfortunately it’s not ideal since the point of the Viliv N5 is that > > it’s ultra portable so I would really like to get the inbuilt wifi > > card working. > > > > It seems odd that wpa_supplicant reports the connection being > > “rejected” as seen below: > > > > wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 > > > > Most of the debug output sadly doesn’t mean a great deal to me - wifi > > isn’t really my area of expertise. > > > > On 21 July 2016 at 19:10:56, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > Sure, here are the results: > > > > > > http://termbin.com/e8e2 > > > > > > Christopher Williamson > > > > > > > > > On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d > > > c...@redhat.com)) wrote: > > > > > >> > > >> On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > > >>> > > >>> I used NetworkManager in the previous test. > > >>> > > >>> This time around I have used wpa_supplicant directly and get > > >>> the > > >>> following results: > > >>> > > >>> http://termbin.com/j8ea > > >>> > > >>> Thought I’d throw them on a pastebin since it’s over 700 lines. > > >> Can you try with "-D nl80211" instead of using the WEXT > > >> supplicant > > >> driver? NM is likely going to use nl80211 since the driver has > > >> some > > >> support for cfg80211/nl80211 and only does WEXT through the glue > > >> layer. > > >> > > >> Dan > > >> > > >>> > > >>> Christopher Williamson > > >>> > > >>> > > >>> > > >>> > > >>> On 20 July 2016 at 22:50:34, Dan Williams > > >>> (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > >>> > > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson > > wrote: > > > > > > > > > Hi Dan, > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. > > > I’ve > > > now > > > built that and dmesg is a much more lively place! > > > > > > I’ve provided output logs for both when the device is > > > connected > > >
Re: Problem connecting to wifi on libertas_cpio (sd8686)
I was thinking about redirecting the wpa logging to syslog but figured I’d take the lazy way out by abusing curl: curl -s http://termbin.com/cx0e http://termbin.com/bvdj | sort Resulting combined log file: http://termbin.com/909y Christopher Williamson On 22 July 2016 at 09:09:59, Arend Van Spriel (arend.vanspr...@broadcom.com(mailto:arend.vanspr...@broadcom.com)) wrote: > On 22-7-2016 0:00, Christopher Williamson wrote: > > I’ve created cleaner logs (particularly the dmesg one) and have added > > timestamps line-by-line to both so it should be easier to track > > between the two log files: > > > > wpa_supplicant: > > http://termbin.com/cx0e > > > > dmesg | grep libertas: > > http://termbin.com/bvdj > > You can make wpa_supplicant log to syslog. That way you get kernel and > wpa_supplicant log in one file. > > Regards, > Arend > > > Christopher Williamson > > > > > > > > > > On 21 July 2016 at 22:00:02, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > >> Sure! > >> > >> wpa_supplicant logs: > >> http://termbin.com/z1hg > >> > >> dmesg logs (grepped for libertas): > >> http://termbin.com/7rt5 > >> > >> > >> Christopher Williamson > >> > >> > >> > >> > >> On 21 July 2016 at 21:38:26, Dan Williams > >> (d...@redhat.com(mailto:d...@redhat.com)) wrote: > >> > >>> On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote: > Just to confirm - I can connect to the same network using the same > configurations using a USB wifi adapter I tried. > >>> > >>> Can you grab simultaneous driver debug logging and supplicant debug > >>> logging? Unfortunately the 'status 1' is an unspecified failure, which > >>> could be from the AP or the firmware. > >>> > >>> Dan > >>> > >>> > Unfortunately it’s not ideal since the point of the Viliv N5 is that > it’s ultra portable so I would really like to get the inbuilt wifi > card working. > > It seems odd that wpa_supplicant reports the connection being > “rejected” as seen below: > > wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 > > Most of the debug output sadly doesn’t mean a great deal to me - wifi > isn’t really my area of expertise. > > On 21 July 2016 at 19:10:56, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > Sure, here are the results: > > > > http://termbin.com/e8e2 > > > > Christopher Williamson > > > > > > On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d > > c...@redhat.com)) wrote: > > > >> > >> On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > >>> > >>> I used NetworkManager in the previous test. > >>> > >>> This time around I have used wpa_supplicant directly and get > >>> the > >>> following results: > >>> > >>> http://termbin.com/j8ea > >>> > >>> Thought I’d throw them on a pastebin since it’s over 700 lines. > >> Can you try with "-D nl80211" instead of using the WEXT > >> supplicant > >> driver? NM is likely going to use nl80211 since the driver has > >> some > >> support for cfg80211/nl80211 and only does WEXT through the glue > >> layer. > >> > >> Dan > >> > >>> > >>> Christopher Williamson > >>> > >>> > >>> > >>> > >>> On 20 July 2016 at 22:50:34, Dan Williams > >>> (d...@redhat.com(mailto:d...@redhat.com)) wrote: > >>> > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson > wrote: > > > > > > Hi Dan, > > > > Ah - yeah I hadn’t thought it may be a kernel build option. > > I’ve > > now > > built that and dmesg is a much more lively place! > > > > I’ve provided output logs for both when the device is > > connected > > and > > when a connection attempt is made - hopefully this is > > useful. > > The card is scanning and only finds 'shaunthesheep' 20 > seconds > after > you "connect for the first time". The logs stop 3 seconds > later. > Are > you connecting with wicd or something else? > > Can you run wpa_supplicant with the "-dddtu" option so we can > get > debug > log output from it? > > Dan > >>> -- > >>> To unsubscribe from this list: send the line "unsubscribe > >>> linux- > >>> wireless" in > >>> the body of a message to majord...@vger.kernel.org > >>> More majordomo info at http://vger.kernel.org/majordomo-info.ht > >>> ml > -- > To unsubscribe from this list: send the line "unsubscribe linux- > wireless" in > the body of a message to majord...@vger.kernel.org > More majordomo info at
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On 22-7-2016 0:00, Christopher Williamson wrote: > I’ve created cleaner logs (particularly the dmesg one) and have added > timestamps line-by-line to both so it should be easier to track > between the two log files: > > wpa_supplicant: > http://termbin.com/cx0e > > dmesg | grep libertas: > http://termbin.com/bvdj You can make wpa_supplicant log to syslog. That way you get kernel and wpa_supplicant log in one file. Regards, Arend > Christopher Williamson > > > > > On 21 July 2016 at 22:00:02, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > >> Sure! >> >> wpa_supplicant logs: >> http://termbin.com/z1hg >> >> dmesg logs (grepped for libertas): >> http://termbin.com/7rt5 >> >> >> Christopher Williamson >> >> >> >> >> On 21 July 2016 at 21:38:26, Dan Williams >> (d...@redhat.com(mailto:d...@redhat.com)) wrote: >> >>> On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote: Just to confirm - I can connect to the same network using the same configurations using a USB wifi adapter I tried. >>> >>> Can you grab simultaneous driver debug logging and supplicant debug >>> logging? Unfortunately the 'status 1' is an unspecified failure, which >>> could be from the AP or the firmware. >>> >>> Dan >>> >>> Unfortunately it’s not ideal since the point of the Viliv N5 is that it’s ultra portable so I would really like to get the inbuilt wifi card working. It seems odd that wpa_supplicant reports the connection being “rejected” as seen below: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 Most of the debug output sadly doesn’t mean a great deal to me - wifi isn’t really my area of expertise. On 21 July 2016 at 19:10:56, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > Sure, here are the results: > > http://termbin.com/e8e2 > > Christopher Williamson > > > On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d > c...@redhat.com)) wrote: > >> >> On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: >>> >>> I used NetworkManager in the previous test. >>> >>> This time around I have used wpa_supplicant directly and get >>> the >>> following results: >>> >>> http://termbin.com/j8ea >>> >>> Thought I’d throw them on a pastebin since it’s over 700 lines. >> Can you try with "-D nl80211" instead of using the WEXT >> supplicant >> driver? NM is likely going to use nl80211 since the driver has >> some >> support for cfg80211/nl80211 and only does WEXT through the glue >> layer. >> >> Dan >> >>> >>> Christopher Williamson >>> >>> >>> >>> >>> On 20 July 2016 at 22:50:34, Dan Williams >>> (d...@redhat.com(mailto:d...@redhat.com)) wrote: >>> On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > > > Hi Dan, > > Ah - yeah I hadn’t thought it may be a kernel build option. > I’ve > now > built that and dmesg is a much more lively place! > > I’ve provided output logs for both when the device is > connected > and > when a connection attempt is made - hopefully this is > useful. The card is scanning and only finds 'shaunthesheep' 20 seconds after you "connect for the first time". The logs stop 3 seconds later. Are you connecting with wicd or something else? Can you run wpa_supplicant with the "-dddtu" option so we can get debug log output from it? Dan >>> -- >>> To unsubscribe from this list: send the line "unsubscribe >>> linux- >>> wireless" in >>> the body of a message to majord...@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.ht >>> ml -- To unsubscribe from this list: send the line "unsubscribe linux- wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>> the body of a message to majord...@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
I’ve created cleaner logs (particularly the dmesg one) and have added timestamps line-by-line to both so it should be easier to track between the two log files: wpa_supplicant: http://termbin.com/cx0e dmesg | grep libertas: http://termbin.com/bvdj Christopher Williamson On 21 July 2016 at 22:00:02, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > Sure! > > wpa_supplicant logs: > http://termbin.com/z1hg > > dmesg logs (grepped for libertas): > http://termbin.com/7rt5 > > > Christopher Williamson > > > > > On 21 July 2016 at 21:38:26, Dan Williams > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote: > > > Just to confirm - I can connect to the same network using the same > > > configurations using a USB wifi adapter I tried. > > > > Can you grab simultaneous driver debug logging and supplicant debug > > logging? Unfortunately the 'status 1' is an unspecified failure, which > > could be from the AP or the firmware. > > > > Dan > > > > > > > Unfortunately it’s not ideal since the point of the Viliv N5 is that > > > it’s ultra portable so I would really like to get the inbuilt wifi > > > card working. > > > > > > It seems odd that wpa_supplicant reports the connection being > > > “rejected” as seen below: > > > > > > wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 > > > > > > Most of the debug output sadly doesn’t mean a great deal to me - wifi > > > isn’t really my area of expertise. > > > > > > On 21 July 2016 at 19:10:56, Christopher Williamson > > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > > > > > Sure, here are the results: > > > > > > > > http://termbin.com/e8e2 > > > > > > > > Christopher Williamson > > > > > > > > > > > > On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d > > > > c...@redhat.com)) wrote: > > > > > > > > > > > > > > On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > > > > > > > > > > > > I used NetworkManager in the previous test. > > > > > > > > > > > > This time around I have used wpa_supplicant directly and get > > > > > > the > > > > > > following results: > > > > > > > > > > > > http://termbin.com/j8ea > > > > > > > > > > > > Thought I’d throw them on a pastebin since it’s over 700 lines. > > > > > Can you try with "-D nl80211" instead of using the WEXT > > > > > supplicant > > > > > driver? NM is likely going to use nl80211 since the driver has > > > > > some > > > > > support for cfg80211/nl80211 and only does WEXT through the glue > > > > > layer. > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 20 July 2016 at 22:50:34, Dan Williams > > > > > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Hi Dan, > > > > > > > > > > > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. > > > > > > > > I’ve > > > > > > > > now > > > > > > > > built that and dmesg is a much more lively place! > > > > > > > > > > > > > > > > I’ve provided output logs for both when the device is > > > > > > > > connected > > > > > > > > and > > > > > > > > when a connection attempt is made - hopefully this is > > > > > > > > useful. > > > > > > > > > > > > > > The card is scanning and only finds 'shaunthesheep' 20 > > > > > > > seconds > > > > > > > after > > > > > > > you "connect for the first time". The logs stop 3 seconds > > > > > > > later. > > > > > > > Are > > > > > > > you connecting with wicd or something else? > > > > > > > > > > > > > > Can you run wpa_supplicant with the "-dddtu" option so we can > > > > > > > get > > > > > > > debug > > > > > > > log output from it? > > > > > > > > > > > > > > Dan > > > > > > -- > > > > > > To unsubscribe from this list: send the line "unsubscribe > > > > > > linux- > > > > > > wireless" in > > > > > > the body of a message to majord...@vger.kernel.org > > > > > > More majordomo info at http://vger.kernel.org/majordomo-info.ht > > > > > > ml > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux- > > > wireless" in > > > the body of a message to majord...@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Sure! wpa_supplicant logs: http://termbin.com/z1hg dmesg logs (grepped for libertas): http://termbin.com/7rt5 Christopher Williamson On 21 July 2016 at 21:38:26, Dan Williams (d...@redhat.com(mailto:d...@redhat.com)) wrote: > On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote: > > Just to confirm - I can connect to the same network using the same > > configurations using a USB wifi adapter I tried. > > Can you grab simultaneous driver debug logging and supplicant debug > logging? Unfortunately the 'status 1' is an unspecified failure, which > could be from the AP or the firmware. > > Dan > > > > Unfortunately it’s not ideal since the point of the Viliv N5 is that > > it’s ultra portable so I would really like to get the inbuilt wifi > > card working. > > > > It seems odd that wpa_supplicant reports the connection being > > “rejected” as seen below: > > > > wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 > > > > Most of the debug output sadly doesn’t mean a great deal to me - wifi > > isn’t really my area of expertise. > > > > On 21 July 2016 at 19:10:56, Christopher Williamson > > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > > > > > Sure, here are the results: > > > > > > http://termbin.com/e8e2 > > > > > > Christopher Williamson > > > > > > > > > On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d > > > c...@redhat.com)) wrote: > > > > > > > > > > > On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > > > > > > > > > > I used NetworkManager in the previous test. > > > > > > > > > > This time around I have used wpa_supplicant directly and get > > > > > the > > > > > following results: > > > > > > > > > > http://termbin.com/j8ea > > > > > > > > > > Thought I’d throw them on a pastebin since it’s over 700 lines. > > > > Can you try with "-D nl80211" instead of using the WEXT > > > > supplicant > > > > driver? NM is likely going to use nl80211 since the driver has > > > > some > > > > support for cfg80211/nl80211 and only does WEXT through the glue > > > > layer. > > > > > > > > Dan > > > > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > > > > > > > > > > On 20 July 2016 at 22:50:34, Dan Williams > > > > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > > > > > > > > > > > > > > > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi Dan, > > > > > > > > > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. > > > > > > > I’ve > > > > > > > now > > > > > > > built that and dmesg is a much more lively place! > > > > > > > > > > > > > > I’ve provided output logs for both when the device is > > > > > > > connected > > > > > > > and > > > > > > > when a connection attempt is made - hopefully this is > > > > > > > useful. > > > > > > > > > > > > The card is scanning and only finds 'shaunthesheep' 20 > > > > > > seconds > > > > > > after > > > > > > you "connect for the first time". The logs stop 3 seconds > > > > > > later. > > > > > > Are > > > > > > you connecting with wicd or something else? > > > > > > > > > > > > Can you run wpa_supplicant with the "-dddtu" option so we can > > > > > > get > > > > > > debug > > > > > > log output from it? > > > > > > > > > > > > Dan > > > > > -- > > > > > To unsubscribe from this list: send the line "unsubscribe > > > > > linux- > > > > > wireless" in > > > > > the body of a message to majord...@vger.kernel.org > > > > > More majordomo info at http://vger.kernel.org/majordomo-info.ht > > > > > ml > > -- > > To unsubscribe from this list: send the line "unsubscribe linux- > > wireless" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote: > Just to confirm - I can connect to the same network using the same > configurations using a USB wifi adapter I tried. Can you grab simultaneous driver debug logging and supplicant debug logging? Unfortunately the 'status 1' is an unspecified failure, which could be from the AP or the firmware. Dan > Unfortunately it’s not ideal since the point of the Viliv N5 is that > it’s ultra portable so I would really like to get the inbuilt wifi > card working. > > It seems odd that wpa_supplicant reports the connection being > “rejected” as seen below: > > wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 > > Most of the debug output sadly doesn’t mean a great deal to me - wifi > isn’t really my area of expertise. > > On 21 July 2016 at 19:10:56, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > > > Sure, here are the results: > > > > http://termbin.com/e8e2 > > > > Christopher Williamson > > > > > > On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d > > c...@redhat.com)) wrote: > > > > > > > > On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > > > > > > > > I used NetworkManager in the previous test. > > > > > > > > This time around I have used wpa_supplicant directly and get > > > > the > > > > following results: > > > > > > > > http://termbin.com/j8ea > > > > > > > > Thought I’d throw them on a pastebin since it’s over 700 lines. > > > Can you try with "-D nl80211" instead of using the WEXT > > > supplicant > > > driver? NM is likely going to use nl80211 since the driver has > > > some > > > support for cfg80211/nl80211 and only does WEXT through the glue > > > layer. > > > > > > Dan > > > > > > > > > > > Christopher Williamson > > > > > > > > > > > > > > > > > > > > On 20 July 2016 at 22:50:34, Dan Williams > > > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > > > > > > > > > > > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi Dan, > > > > > > > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. > > > > > > I’ve > > > > > > now > > > > > > built that and dmesg is a much more lively place! > > > > > > > > > > > > I’ve provided output logs for both when the device is > > > > > > connected > > > > > > and > > > > > > when a connection attempt is made - hopefully this is > > > > > > useful. > > > > > > > > > > The card is scanning and only finds 'shaunthesheep' 20 > > > > > seconds > > > > > after > > > > > you "connect for the first time". The logs stop 3 seconds > > > > > later. > > > > > Are > > > > > you connecting with wicd or something else? > > > > > > > > > > Can you run wpa_supplicant with the "-dddtu" option so we can > > > > > get > > > > > debug > > > > > log output from it? > > > > > > > > > > Dan > > > > -- > > > > To unsubscribe from this list: send the line "unsubscribe > > > > linux- > > > > wireless" in > > > > the body of a message to majord...@vger.kernel.org > > > > More majordomo info at http://vger.kernel.org/majordomo-info.ht > > > > ml > -- > To unsubscribe from this list: send the line "unsubscribe linux- > wireless" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Just to confirm - I can connect to the same network using the same configurations using a USB wifi adapter I tried. Unfortunately it’s not ideal since the point of the Viliv N5 is that it’s ultra portable so I would really like to get the inbuilt wifi card working. It seems odd that wpa_supplicant reports the connection being “rejected” as seen below: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1 Most of the debug output sadly doesn’t mean a great deal to me - wifi isn’t really my area of expertise. On 21 July 2016 at 19:10:56, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > Sure, here are the results: > > http://termbin.com/e8e2 > > Christopher Williamson > > > On 21 July 2016 at 16:37:24, Dan Williams > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > > > I used NetworkManager in the previous test. > > > > > > This time around I have used wpa_supplicant directly and get the > > > following results: > > > > > > http://termbin.com/j8ea > > > > > > Thought I’d throw them on a pastebin since it’s over 700 lines. > > > > Can you try with "-D nl80211" instead of using the WEXT supplicant > > driver? NM is likely going to use nl80211 since the driver has some > > support for cfg80211/nl80211 and only does WEXT through the glue > > layer. > > > > Dan > > > > > Christopher Williamson > > > > > > > > > > > > > > > On 20 July 2016 at 22:50:34, Dan Williams > > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > > > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > > > > > > > > > > Hi Dan, > > > > > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. I’ve > > > > > now > > > > > built that and dmesg is a much more lively place! > > > > > > > > > > I’ve provided output logs for both when the device is connected > > > > > and > > > > > when a connection attempt is made - hopefully this is useful. > > > > > > > > > > > > The card is scanning and only finds 'shaunthesheep' 20 seconds > > > > after > > > > you "connect for the first time". The logs stop 3 seconds later. > > > > Are > > > > you connecting with wicd or something else? > > > > > > > > Can you run wpa_supplicant with the "-dddtu" option so we can get > > > > debug > > > > log output from it? > > > > > > > > Dan > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux- > > > wireless" in > > > the body of a message to majord...@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Sure, here are the results: http://termbin.com/e8e2 Christopher Williamson On 21 July 2016 at 16:37:24, Dan Williams (d...@redhat.com(mailto:d...@redhat.com)) wrote: > On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > > I used NetworkManager in the previous test. > > > > This time around I have used wpa_supplicant directly and get the > > following results: > > > > http://termbin.com/j8ea > > > > Thought I’d throw them on a pastebin since it’s over 700 lines. > > Can you try with "-D nl80211" instead of using the WEXT supplicant > driver? NM is likely going to use nl80211 since the driver has some > support for cfg80211/nl80211 and only does WEXT through the glue > layer. > > Dan > > > Christopher Williamson > > > > > > > > > > On 20 July 2016 at 22:50:34, Dan Williams > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > > > > > > > > Hi Dan, > > > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. I’ve > > > > now > > > > built that and dmesg is a much more lively place! > > > > > > > > I’ve provided output logs for both when the device is connected > > > > and > > > > when a connection attempt is made - hopefully this is useful. > > > > > > > > > The card is scanning and only finds 'shaunthesheep' 20 seconds > > > after > > > you "connect for the first time". The logs stop 3 seconds later. > > > Are > > > you connecting with wicd or something else? > > > > > > Can you run wpa_supplicant with the "-dddtu" option so we can get > > > debug > > > log output from it? > > > > > > Dan > > -- > > To unsubscribe from this list: send the line "unsubscribe linux- > > wireless" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote: > I used NetworkManager in the previous test. > > This time around I have used wpa_supplicant directly and get the > following results: > > http://termbin.com/j8ea > > Thought I’d throw them on a pastebin since it’s over 700 lines. Can you try with "-D nl80211" instead of using the WEXT supplicant driver? NM is likely going to use nl80211 since the driver has some support for cfg80211/nl80211 and only does WEXT through the glue layer. Dan > Christopher Williamson > > > > > On 20 July 2016 at 22:50:34, Dan Williams > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > > > > > > Hi Dan, > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. I’ve > > > now > > > built that and dmesg is a much more lively place! > > > > > > I’ve provided output logs for both when the device is connected > > > and > > > when a connection attempt is made - hopefully this is useful. > > > > > > The card is scanning and only finds 'shaunthesheep' 20 seconds > > after > > you "connect for the first time". The logs stop 3 seconds later. > > Are > > you connecting with wicd or something else? > > > > Can you run wpa_supplicant with the "-dddtu" option so we can get > > debug > > log output from it? > > > > Dan > -- > To unsubscribe from this list: send the line "unsubscribe linux- > wireless" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Tried a few more things worth mentioning: - Tried connecting with wpa_supplicant & dhclient only but sadly wpa_supplicant still cannot seem to hold a connection to the base station. It looks like the relevant errors here may be: ioctl[SIOCSIWENCODEEXT]: Invalid argument wlan0: Trying to associate with a0:63:91:1e:ee:43 (SSID='shaunthesheep' freq=2457 MHz) ioctl[SIOCSIWFREQ]: Device or resource busy wlan0: Association request to the driver failed - Tried NetworkManager again and also tried wicd - both have similar problems. I expect since they both use wpa_supplicant the issue was unlikely to not be there for either of these solutions but I figured it was worth experimenting with. - I also tried kernel 4.6.4 and noticed no difference there either so it looks like the same issue is present in the latest stable kernel as well as the latest longterm kernel (which Ubuntu uses for 16.04 LTS.) Christopher Williamson On 20 July 2016 at 23:16:41, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > I used NetworkManager in the previous test. > > This time around I have used wpa_supplicant directly and get the following > results: > > http://termbin.com/j8ea > > Thought I’d throw them on a pastebin since it’s over 700 lines. > > Christopher Williamson > > > > > On 20 July 2016 at 22:50:34, Dan Williams > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > > > Hi Dan, > > > > > > Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now > > > built that and dmesg is a much more lively place! > > > > > > I’ve provided output logs for both when the device is connected and > > > when a connection attempt is made - hopefully this is useful. > > > > > > > > The card is scanning and only finds 'shaunthesheep' 20 seconds after > > you "connect for the first time". The logs stop 3 seconds later. Are > > you connecting with wicd or something else? > > > > Can you run wpa_supplicant with the "-dddtu" option so we can get debug > > log output from it? > > > > Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
I used NetworkManager in the previous test. This time around I have used wpa_supplicant directly and get the following results: http://termbin.com/j8ea Thought I’d throw them on a pastebin since it’s over 700 lines. Christopher Williamson On 20 July 2016 at 22:50:34, Dan Williams (d...@redhat.com(mailto:d...@redhat.com)) wrote: > On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > > Hi Dan, > > > > Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now > > built that and dmesg is a much more lively place! > > > > I’ve provided output logs for both when the device is connected and > > when a connection attempt is made - hopefully this is useful. > > > > The card is scanning and only finds 'shaunthesheep' 20 seconds after > you "connect for the first time". The logs stop 3 seconds later. Are > you connecting with wicd or something else? > > Can you run wpa_supplicant with the "-dddtu" option so we can get debug > log output from it? > > Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote: > Hi Dan, > > Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now > built that and dmesg is a much more lively place! > > I’ve provided output logs for both when the device is connected and > when a connection attempt is made - hopefully this is useful. The card is scanning and only finds 'shaunthesheep' 20 seconds after you "connect for the first time". The logs stop 3 seconds later. Are you connecting with wicd or something else? Can you run wpa_supplicant with the "-dddtu" option so we can get debug log output from it? Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Hi Dan, Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now built that and dmesg is a much more lively place! I’ve provided output logs for both when the device is connected and when a connection attempt is made - hopefully this is useful. When I first connect the device: root@nano:~# dmesg |grep libertas [ 80.432144] libertas: module verification failed: signature and/or required key missing - tainting kernel [ 80.434563] libertas enter: lbs_init_module() [ 80.434600] libertas leave: lbs_init_module() [ 80.457044] libertas_sdio: Libertas SDIO driver [ 80.457062] libertas_sdio: Copyright Pierre Ossman [ 80.457782] libertas enter: lbs_add_card() [ 80.457801] libertas enter: lbs_cfg_alloc() [ 80.457875] libertas leave: lbs_cfg_alloc() [ 80.457890] libertas enter: lbs_init_adapter() [ 80.457905] libertas enter: lbs_allocate_cmd_buffer() [ 80.458005] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458022] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458034] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458047] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458058] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458072] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458083] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458098] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458110] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458124] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458137] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458151] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458164] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458179] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458191] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458205] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458216] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458231] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458244] libertas enter: __lbs_cleanup_and_insert_cmd() [ 80.458259] libertas leave: __lbs_cleanup_and_insert_cmd() [ 80.458273] libertas leave: lbs_allocate_cmd_buffer(), ret 0 [ 80.458290] libertas leave: lbs_init_adapter(), ret 0 [ 80.458333] libertas thread: Starting main thread... [ 80.458766] libertas enter: lbs_thread() [ 80.458785] libertas thread: 1: currenttxskb (null), dnld_sent 0 [ 80.458802] libertas thread: sleeping, connect_status 1, psmode 0, psstate 0 [ 80.458870] libertas leave: lbs_add_card(), priv f6700420 [ 81.020863] libertas enter: lbs_start_card() [ 81.020880] libertas enter: lbs_update_hw_spec() [ 81.020890] libertas enter: __lbs_cmd() [ 81.020898] libertas enter: __lbs_cmd_async() [ 81.020906] libertas enter: lbs_get_free_cmd_node() [ 81.020915] libertas leave: lbs_get_free_cmd_node() [ 81.020924] libertas host: PREP_CMD: command 0x0003 [ 81.020931] libertas enter: lbs_queue_cmd() [ 81.020941] libertas host: QUEUE_CMD: inserted command 0x0003 into cmdpendingq [ 81.020948] libertas leave: lbs_queue_cmd() [ 81.020976] libertas leave: __lbs_cmd_async(), ret f64fc000 [ 81.021001] libertas thread: 2: currenttxskb (null), dnld_send 0 [ 81.021014] libertas thread: 3: currenttxskb (null), dnld_sent 0 [ 81.021023] libertas thread: 4: currenttxskb (null), dnld_sent 0 [ 81.021032] libertas enter: lbs_execute_next_command() [ 81.021041] libertas host: EXEC_NEXT_CMD: sending command 0x0003 [ 81.021049] libertas enter: lbs_submit_command() [ 81.021059] libertas cmd: DNLD_CMD: command 0x0003, seq 1, size 46 [ 81.021089] libertas leave: lbs_submit_command() [ 81.021098] libertas leave: lbs_execute_next_command() [ 81.021107] libertas thread: 1: currenttxskb (null), dnld_sent 2 [ 81.021117] libertas thread: sleeping, connect_status 1, psmode 0, psstate 0 [ 81.021443] libertas enter: lbs_host_to_card_done() [ 81.021454] libertas leave: lbs_host_to_card_done() [ 81.021763] libertas enter: lbs_notify_command_response() [ 81.021786] libertas leave: lbs_notify_command_response() [ 81.021799] libertas thread: 2: currenttxskb (null), dnld_send 0 [ 81.021809] libertas thread: 3: currenttxskb (null), dnld_sent 0 [ 81.021818] libertas thread: 4: currenttxskb (null), dnld_sent 0 [ 81.021830] libertas enter: lbs_process_command_response() [ 81.021846] libertas cmd: CMD_RESP: response 0x8003, seq 1, size 46 [ 81.021869] libertas leave: lbs_process_command_response(), ret 0 [ 81.021879] libertas enter: __lbs_cleanup_and_insert_cmd() [ 81.021888] libertas leave: __lbs_cleanup_and_insert_cmd() [ 81.021897] libertas leave: __lbs_cmd(), ret 0 [ 81.021908] libertas enter: lbs_execute_next_command() [ 81.021922] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): 00:02:78:69:49:94, fw 9.70.20p0, cap 0x0303 [ 81.021932] libertas cmd: GET_HW_SPEC: hardware interface 0x2, hardware spec 0x0011 [ 81.021941] libertas leave: lbs_update_hw_spec() [ 81.021949] libertas enter: lbs_get_tx_power() [ 81.021957] libertas enter: __lbs_cmd() [ 81.021965] libertas enter: __lbs_cmd_async() [ 81.021973]
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Wed, 2016-07-20 at 02:53 -0700, Christopher Williamson wrote: > Just following up from my previous email: > > I am actually setting the reg domain using: iw reg set GB > (copy/pasted > the IN from elsewhere - oops!) > > As for progress, however, I have tried the following: > > - setting the debug level to 0xfff. This still produces no > additional output even with 8 set in printk. Yeah, looks like you'd need to rebuild the libertas driver with CONFIG_LIBERTAS_DEBUG set. Or just #define that to 1 in defs.h. Is that something you could do? Dan > - removing the v9 firmware - same result as before - system fully > locks up. > > - disabling ipv6 - gets rid of IPv6 interface not up warning but > that’s not causing any problems and this didn’t make any difference. > > It doesn’t seem to matter what I try at the moment - all attempts to > connect result in the system crashing which I guess is better than it > just asking me for a password over and over - it looks like it is > attempting association at this point which is good but I don’t know > why the box is crashing out and dmesg -w doesn’t show any additional > output before the freeze. > > If anyone has any more ideas I would be more than happy to try them! > Thanks for the help so far Dan! > > Christopher Williamson > > On 19 July 2016 at 18:41:34, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > > > So I’ve now disabled IPv6 and have set the GB (Great Britain) > > regulation code using: > > > > iw reg set IN > > > > Now when I try to connect to the network using wicd the system > > seems to crash - I guess at least it’s doing something more than > > just asking for the password again like it did with NetworkManager > > but so far no further progress on getting this working properly. > > > > Christopher Williamson > > > > > > > > On 19 July 2016 at 18:03:16, Christopher Williamson (home@chrisaw.c > > om(mailto:h...@chrisaw.com)) wrote: > > > > > > > > Absolutely! > > > > > > With the debug logging enabled I got the following: > > > > > > Connecting the device initially with debug enabled: > > > > > > [ 205.302685] libertas_sdio: Libertas SDIO driver > > > [ 205.302698] libertas_sdio: Copyright Pierre Ossman > > > [ 205.503465] cfg80211: World regulatory domain updated: > > > [ 205.503478] cfg80211: DFS Master region: unset > > > [ 205.503483] cfg80211: (start_freq - end_freq @ bandwidth), > > > (max_antenna_gain, max_eirp), (dfs_cac_time) > > > [ 205.503492] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), > > > (N/A, 2000 mBm), (N/A) > > > [ 205.503499] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), > > > (N/A, 2000 mBm), (N/A) > > > [ 205.503505] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), > > > (N/A, 2000 mBm), (N/A) > > > [ 205.503513] cfg80211: (517 KHz - 525 KHz @ 8 KHz, > > > 16 KHz AUTO), (N/A, 2000 mBm), (N/A) > > > [ 205.503522] cfg80211: (525 KHz - 533 KHz @ 8 KHz, > > > 16 KHz AUTO), (N/A, 2000 mBm), (0 s) > > > [ 205.503529] cfg80211: (549 KHz - 573 KHz @ 16 KHz), > > > (N/A, 2000 mBm), (0 s) > > > [ 205.503535] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), > > > (N/A, 2000 mBm), (N/A) > > > [ 205.503542] cfg80211: (5724 KHz - 6372 KHz @ 216 > > > KHz), (N/A, 0 mBm), (N/A) > > > [ 212.249171] gma500 :00:02.0: Backlight lvds set brightness > > > 7a127a12 > > > [ 212.324898] mmc1: new SDIO card at address 0001 > > > [ 212.921672] libertas_sdio mmc1:0001:1 (unnamed net_device) > > > (uninitialized): 00:02:78:69:49:94, fw 9.70.20p0, cap 0x0303 > > > [ 212.925774] libertas_sdio mmc1:0001:1 (unnamed net_device) > > > (uninitialized): PREP_CMD: command 0x00a3 failed: 2 > > > [ 212.936190] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN > > > 802.11 adapter > > > [ 213.053612] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > > > > > > > Strangely when I attempt to connect to the WiFi network I’m using > > > the only error I get is: > > > > > > [ 338.076632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > > > > I was expecting more output and am guessing I’ve missed something > > > here. > > > > > > Christopher Williamson > > > > > > On 19 July 2016 at 17:38:35, Dan Williams (d...@redhat.com(mailto > > > :d...@redhat.com)) wrote: > > > > > > > > > > > On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson > > > > wrote: > > > > > > > > > > Hi everyone! > > > > > > > > > > I’ve just got myself a Viliv N5 and am trying to get the > > > > > integrated > > > > > Wifi chipset working on it. > > > > > > > > > > I am able to see networks around me but any attempts to > > > > > connect them > > > > > appear to time out and fail. > > > > > > > > > > I have filed a linux kernel bug related to this issue: > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=135421goo > > > > > > > > > > I figured here may be a good place to ask about it and > > > > > hopefully to > > > > > get to the
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Just following up from my previous email: I am actually setting the reg domain using: iw reg set GB (copy/pasted the IN from elsewhere - oops!) As for progress, however, I have tried the following: - setting the debug level to 0xfff. This still produces no additional output even with 8 set in printk. - removing the v9 firmware - same result as before - system fully locks up. - disabling ipv6 - gets rid of IPv6 interface not up warning but that’s not causing any problems and this didn’t make any difference. It doesn’t seem to matter what I try at the moment - all attempts to connect result in the system crashing which I guess is better than it just asking me for a password over and over - it looks like it is attempting association at this point which is good but I don’t know why the box is crashing out and dmesg -w doesn’t show any additional output before the freeze. If anyone has any more ideas I would be more than happy to try them! Thanks for the help so far Dan! Christopher Williamson On 19 July 2016 at 18:41:34, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > So I’ve now disabled IPv6 and have set the GB (Great Britain) regulation code > using: > > iw reg set IN > > Now when I try to connect to the network using wicd the system seems to crash > - I guess at least it’s doing something more than just asking for the > password again like it did with NetworkManager but so far no further progress > on getting this working properly. > > Christopher Williamson > > > > On 19 July 2016 at 18:03:16, Christopher Williamson > (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > > > Absolutely! > > > > With the debug logging enabled I got the following: > > > > Connecting the device initially with debug enabled: > > > > [ 205.302685] libertas_sdio: Libertas SDIO driver > > [ 205.302698] libertas_sdio: Copyright Pierre Ossman > > [ 205.503465] cfg80211: World regulatory domain updated: > > [ 205.503478] cfg80211: DFS Master region: unset > > [ 205.503483] cfg80211: (start_freq - end_freq @ bandwidth), > > (max_antenna_gain, max_eirp), (dfs_cac_time) > > [ 205.503492] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 > > mBm), (N/A) > > [ 205.503499] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 > > mBm), (N/A) > > [ 205.503505] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 > > mBm), (N/A) > > [ 205.503513] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz > > AUTO), (N/A, 2000 mBm), (N/A) > > [ 205.503522] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz > > AUTO), (N/A, 2000 mBm), (0 s) > > [ 205.503529] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, > > 2000 mBm), (0 s) > > [ 205.503535] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 > > mBm), (N/A) > > [ 205.503542] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, > > 0 mBm), (N/A) > > [ 212.249171] gma500 :00:02.0: Backlight lvds set brightness 7a127a12 > > [ 212.324898] mmc1: new SDIO card at address 0001 > > [ 212.921672] libertas_sdio mmc1:0001:1 (unnamed net_device) > > (uninitialized): 00:02:78:69:49:94, fw 9.70.20p0, cap 0x0303 > > [ 212.925774] libertas_sdio mmc1:0001:1 (unnamed net_device) > > (uninitialized): PREP_CMD: command 0x00a3 failed: 2 > > [ 212.936190] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN 802.11 adapter > > [ 213.053612] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > > > > Strangely when I attempt to connect to the WiFi network I’m using the only > > error I get is: > > > > [ 338.076632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > > I was expecting more output and am guessing I’ve missed something here. > > > > Christopher Williamson > > > > On 19 July 2016 at 17:38:35, Dan Williams > > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > > > On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson wrote: > > > > Hi everyone! > > > > > > > > I’ve just got myself a Viliv N5 and am trying to get the integrated > > > > Wifi chipset working on it. > > > > > > > > I am able to see networks around me but any attempts to connect them > > > > appear to time out and fail. > > > > > > > > I have filed a linux kernel bug related to this issue: > > > > https://bugzilla.kernel.org/show_bug.cgi?id=135421goo > > > > > > > > I figured here may be a good place to ask about it and hopefully to > > > > get to the bottom of why it happens and how I can help to fix it. > > > > > > > > Happy to provide any information which may be helpful! :) > > > > > > Can you reload the driver stack: > > > > > > rmmod libertas_sdio > > > rmmod libertas > > > modprobe libertas libertas_debug=0x251e7ff > > > modprobe libertas_sdio > > > > > > and then reproduce the issue? The debug info should dump to 'dmesg' > > > and may tell us what's going on. > > > > > > Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to
Re: Problem connecting to wifi on libertas_cpio (sd8686)
So I’ve now disabled IPv6 and have set the GB (Great Britain) regulation code using: iw reg set IN Now when I try to connect to the network using wicd the system seems to crash - I guess at least it’s doing something more than just asking for the password again like it did with NetworkManager but so far no further progress on getting this working properly. Christopher Williamson On 19 July 2016 at 18:03:16, Christopher Williamson (h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote: > Absolutely! > > With the debug logging enabled I got the following: > > Connecting the device initially with debug enabled: > > [ 205.302685] libertas_sdio: Libertas SDIO driver > [ 205.302698] libertas_sdio: Copyright Pierre Ossman > [ 205.503465] cfg80211: World regulatory domain updated: > [ 205.503478] cfg80211: DFS Master region: unset > [ 205.503483] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp), (dfs_cac_time) > [ 205.503492] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 > mBm), (N/A) > [ 205.503499] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 > mBm), (N/A) > [ 205.503505] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 > mBm), (N/A) > [ 205.503513] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz > AUTO), (N/A, 2000 mBm), (N/A) > [ 205.503522] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz > AUTO), (N/A, 2000 mBm), (0 s) > [ 205.503529] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 > mBm), (0 s) > [ 205.503535] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 > mBm), (N/A) > [ 205.503542] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 > mBm), (N/A) > [ 212.249171] gma500 :00:02.0: Backlight lvds set brightness 7a127a12 > [ 212.324898] mmc1: new SDIO card at address 0001 > [ 212.921672] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): > 00:02:78:69:49:94, fw 9.70.20p0, cap 0x0303 > [ 212.925774] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): > PREP_CMD: command 0x00a3 failed: 2 > [ 212.936190] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN 802.11 adapter > [ 213.053612] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > Strangely when I attempt to connect to the WiFi network I’m using the only > error I get is: > > [ 338.076632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > I was expecting more output and am guessing I’ve missed something here. > > Christopher Williamson > > On 19 July 2016 at 17:38:35, Dan Williams > (d...@redhat.com(mailto:d...@redhat.com)) wrote: > > > On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson wrote: > > > Hi everyone! > > > > > > I’ve just got myself a Viliv N5 and am trying to get the integrated > > > Wifi chipset working on it. > > > > > > I am able to see networks around me but any attempts to connect them > > > appear to time out and fail. > > > > > > I have filed a linux kernel bug related to this issue: > > > https://bugzilla.kernel.org/show_bug.cgi?id=135421goo > > > > > > I figured here may be a good place to ask about it and hopefully to > > > get to the bottom of why it happens and how I can help to fix it. > > > > > > Happy to provide any information which may be helpful! :) > > > > Can you reload the driver stack: > > > > rmmod libertas_sdio > > rmmod libertas > > modprobe libertas libertas_debug=0x251e7ff > > modprobe libertas_sdio > > > > and then reproduce the issue? The debug info should dump to 'dmesg' > > and may tell us what's going on. > > > > Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
Absolutely! With the debug logging enabled I got the following: Connecting the device initially with debug enabled: [ 205.302685] libertas_sdio: Libertas SDIO driver [ 205.302698] libertas_sdio: Copyright Pierre Ossman [ 205.503465] cfg80211: World regulatory domain updated: [ 205.503478] cfg80211: DFS Master region: unset [ 205.503483] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 205.503492] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 205.503499] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 205.503505] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 205.503513] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 205.503522] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 205.503529] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 205.503535] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 205.503542] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 212.249171] gma500 :00:02.0: Backlight lvds set brightness 7a127a12 [ 212.324898] mmc1: new SDIO card at address 0001 [ 212.921672] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): 00:02:78:69:49:94, fw 9.70.20p0, cap 0x0303 [ 212.925774] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): PREP_CMD: command 0x00a3 failed: 2 [ 212.936190] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN 802.11 adapter [ 213.053612] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Strangely when I attempt to connect to the WiFi network I’m using the only error I get is: [ 338.076632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready I was expecting more output and am guessing I’ve missed something here. Christopher Williamson On 19 July 2016 at 17:38:35, Dan Williams (d...@redhat.com(mailto:d...@redhat.com)) wrote: > On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson wrote: > > Hi everyone! > > > > I’ve just got myself a Viliv N5 and am trying to get the integrated > > Wifi chipset working on it. > > > > I am able to see networks around me but any attempts to connect them > > appear to time out and fail. > > > > I have filed a linux kernel bug related to this issue: > > https://bugzilla.kernel.org/show_bug.cgi?id=135421goo > > > > I figured here may be a good place to ask about it and hopefully to > > get to the bottom of why it happens and how I can help to fix it. > > > > Happy to provide any information which may be helpful! :) > > Can you reload the driver stack: > > rmmod libertas_sdio > rmmod libertas > modprobe libertas libertas_debug=0x251e7ff > modprobe libertas_sdio > > and then reproduce the issue? The debug info should dump to 'dmesg' > and may tell us what's going on. > > Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem connecting to wifi on libertas_cpio (sd8686)
On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson wrote: > Hi everyone! > > I’ve just got myself a Viliv N5 and am trying to get the integrated > Wifi chipset working on it. > > I am able to see networks around me but any attempts to connect them > appear to time out and fail. > > I have filed a linux kernel bug related to this issue: > https://bugzilla.kernel.org/show_bug.cgi?id=135421 > > I figured here may be a good place to ask about it and hopefully to > get to the bottom of why it happens and how I can help to fix it. > > Happy to provide any information which may be helpful! :) Can you reload the driver stack: rmmod libertas_sdio rmmod libertas modprobe libertas libertas_debug=0x251e7ff modprobe libertas_sdio and then reproduce the issue? The debug info should dump to 'dmesg' and may tell us what's going on. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
