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 > (home@xxxxxxxxxxx(mailto:home@xxxxxxxxxxx)) 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 (dcbw@xxxxxxxxxx(mailto:dcbw@xxxxxxxxxx)) 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 >>>> (home@xxxxxxxxxxx(mailto:home@xxxxxxxxxxx)) wrote: >>>> >>>>> >>>>> >>>>> Sure, here are the results: >>>>> >>>>> http://termbin.com/e8e2 >>>>> >>>>> Christopher Williamson >>>>> >>>>> >>>>> On 21 July 2016 at 16:37:24, Dan Williams (dcbw@xxxxxxxxxx(mailto:d >>>>> cbw@xxxxxxxxxx)) 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 >>>>>>> (dcbw@xxxxxxxxxx(mailto:dcbw@xxxxxxxxxx)) 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 majordomo@xxxxxxxxxxxxxxx >>>>>>> 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 majordomo@xxxxxxxxxxxxxxx >>>> 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 majordomo@xxxxxxxxxxxxxxx >>> 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 majordomo@xxxxxxxxxxxxxxx > 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
