Nope, it's broadwell. On March 9, 2016 4:06:41 PM EST, Adrian Chadd <[email protected]> wrote: >if it's haswell, then it's likely related to drm. Try updating to the >latest -head and try again. > > > >-a > > >On 9 March 2016 at 12:52, Eric McCorkle <[email protected]> wrote: >> Thanks for the help. In the mean time, I'll see if I can diagnose the >resume issue. >> >> On March 9, 2016 1:40:43 PM EST, Adrian Chadd ><[email protected]> wrote: >>>Okm I bought a NIC and pigtails. I'll see what happens. >>>On Mar 9, 2016 9:41 AM, "Eric McCorkle" <[email protected]> wrote: >>> >>>> Yes. The log message showed up. >>>> >>>> On March 9, 2016 11:42:03 AM EST, Adrian Chadd >>><[email protected]> >>>> wrote: >>>>> >>>>> Ok, it may not be exactly the same as the WB222 module (that's in >>>the >>>>> chromebook c720.) I'll have to go poke around in ath9k to see how >>>>> they've set it up. >>>>> >>>>> When you added that hints entry, did it log what I said? >>>>> >>>>> >>>>> -adrian >>>>> >>>>> >>>>> On 9 March 2016 at 04:46, Eric McCorkle <[email protected]> >>>wrote: >>>>> >>>>>> I took off the back panel. There are three codes, aside from >the >>>MAC >>>>>> address: >>>>>> >>>>>> S/N WCBN802AAAC434007684 >>>>>> Atheros model QCNFA222 >>>>>> BD ID 3010B377E299 >>>>>> >>>>>> It's an NGFF (M.2) card. >>>>>> >>>>>> On Mar 9, 2016, at 00:16, Adrian Chadd <[email protected]> >>>wrote: >>>>>> >>>>>> Ok. I need to know the part number of the device and what >>>Bluetooth chip it >>>>>> has I can see what ath9k does for this part. >>>>>> >>>>>> If it's mini pcie then let's see if theyll send >>>>>> me just the NIC. >>>>>> >>>>>> Adrian >>>>>> >>>>>> On Mar 8, 2016 8:44 PM, "Eric McCorkle" <[email protected]> >>>wrote: >>>>>> >>>>>>> >>>>>>> Sadly, no effect. However, the Bluetooth system does seem to >>>timeout >>>>>>> shortly after detection, which lends support to your diagnosis. >>>>>>> >>>>>>> On Mar 8, 2016, at 20:56, Adrian Chadd <[email protected]> >>>wrote: >>>>>>>> >>>>>>>> Try setting this in /boot/<whatever>.hints : >>>>>>>> >>>>>>>> hint.ath.0.btcoex_profile="wb222" >>>>>>>> >>>>>>>> Then reboot. >>>>>>>> >>>>>>>> It should output this: >>>>>>>> >>>>>>>> ath0: Enabling WB222 BTCOEX >>>>>>>> >>>>>>>> .. during boot. Try that and see what happens! >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -adrian >>>>>>>> >>>>>>> >>>> -- >>>> Sent from my Android device with K-9 Mail. Please excuse my >brevity. >>>> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> _______________________________________________ >> [email protected] mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >"[email protected]"
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[email protected]"
