IWN_DEBUG worked, it's 'dev.iwn.0.debug', not 'debug.iwn.0.debug'. My bad.
Make sure you build the module by doing 'buildkernel', not 'cd
sys/modules/iwn && make', as (because reasons I want to grr) we don't
enforce that people put in a path to their kernel config .h directory,
so it defaults to "
On Wed, Aug 24, 2016 at 12:45 PM, Glen Barber <
g...@freebsd.org> wrote:
> On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote:
> >
> > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote:
> >
> > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote:
> > > > Not working rig
On Wed, Aug 24, 2016 at 03:21:12PM -0500, Kyle Evans wrote:
> On Wed, Aug 24, 2016 at 2:45 PM, Glen Barber wrote:
> > Dumb question, but with reason.
> >
> > Does ifconfig(8) actually show wlan0 'UP'?
> >
> > I'm asking this because I'm seeing something strange locally on one
> > machine.
> >
> >
On Wed, Aug 24, 2016 at 01:51:47PM -0700, Adrian Chadd wrote:
> On 24 August 2016 at 13:23, Glen Barber wrote:
> > On Wed, Aug 24, 2016 at 08:19:21PM +, Glen Barber wrote:
> >> On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote:
> >> > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote:
On Wed, Aug 24, 2016 at 2:45 PM, Glen Barber wrote:
> Dumb question, but with reason.
>
> Does ifconfig(8) actually show wlan0 'UP'?
>
> I'm asking this because I'm seeing something strange locally on one
> machine.
>
> Glen
Follow up dumb question, but I've very recently experienced (with ath(4)
hi
Would /someone/ pretty please fix this "run wpa_supplicant multiple
times at interface start" problem?
I'm sure it's screwing things up in a bad way, and trying to grovel
around and fix the way we do rc scripts is not my favourite thing in
the world.
Thanks,
-adrian
On 24 August 2016 at 1
On Wed, Aug 24, 2016 at 08:19:21PM +, Glen Barber wrote:
> On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote:
> > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote:
> >
> > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote:
> > > >
> > > > On Wed, Aug 24, 2016 at 12:03
On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote:
> On Aug 24, 2016 12:46 PM, "Glen Barber" wrote:
>
> > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote:
> > >
> > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote:
> > >
> > > > On Wed, Aug 24, 2016 at 11:55:13AM
I have been unable to catch it, so I don't know. I know the UP/DOWN
sequences in the first log showed many per second and all in the same
second. In this case it was UP for 13 seconds, so something was different.
I will try to test some more later, but I have to go out for a couple of
hours righ
On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote:
>
> On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote:
>
> > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote:
> > > Not working right. I do see 802.11 messages but nothing from iwn.
> > > Rebuilt with:
> > > options
On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote:
> On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote:
> > Not working right. I do see 802.11 messages but nothing from iwn.
> > Rebuilt with:
> > optionsIEEE80211_DEBUG
> > optionsIWN_DEBUG
> >
> > [...]
> >
> > An
On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote:
> Not working right. I do see 802.11 messages but nothing from iwn.
> Rebuilt with:
> optionsIEEE80211_DEBUG
> optionsIWN_DEBUG
>
> [...]
>
> Any idea what is going on?
Your original email mentions 11.0-BETA4. Are yo
On Tue, Aug 23, 2016 at 10:40 PM, Kevin Oberman <
kob6...@gmail.com> wrote:
> On Tue, Aug 23, 2016 at 11:48 AM, Adrian Chadd <
> adrian.ch...@gmail.com> wrote:
>
>> Hi,
>>
>> Compile in IWN_DEBUG and IEEE80211_DEBUG and then do:
>>
>> wlandebug +assoc +auth +state +rate
>> sysctl debug.iwn.0.deb
Hi,
Compile in IWN_DEBUG and IEEE80211_DEBUG and then do:
wlandebug +assoc +auth +state +rate
sysctl debug.iwn.0.debug=0x1
that's TX debugging, and it hopefully will show it trying to do
association and failing. My guess is that something changed when doing
the 11n bits for -11 and it's failing
On Mon, Aug 22, 2016 at 12:21 PM, VinÃcius Zavam <
egyp...@googlemail.com> wrote:
>
>
> 2016-08-20 23:07 GMT-03:00 Adrian Chadd :
>
>> On 20 August 2016 at 19:02, Kevin Oberman wrote:
>> > On Aug 20, 2016 6:29 PM, "Adrian Chadd" wrote:
>> >>
>> >> Hi,
>> >>
>> >> There have been some changes to
2016-08-20 23:07 GMT-03:00 Adrian Chadd :
> On 20 August 2016 at 19:02, Kevin Oberman wrote:
> > On Aug 20, 2016 6:29 PM, "Adrian Chadd" wrote:
> >>
> >> Hi,
> >>
> >> There have been some changes to the scan code and iwn scan timeout code.
> >> Andriy may have some ideas.
> >>
> >> Thanks!
> >>
On 20 August 2016 at 19:02, Kevin Oberman wrote:
> On Aug 20, 2016 6:29 PM, "Adrian Chadd" wrote:
>>
>> Hi,
>>
>> There have been some changes to the scan code and iwn scan timeout code.
>> Andriy may have some ideas.
>>
>> Thanks!
>>
>> A
>
> One more note. There are multiple "link up" messages
On Aug 20, 2016 6:29 PM, "Adrian Chadd" wrote:
>
> Hi,
>
> There have been some changes to the scan code and iwn scan timeout code.
Andriy may have some ideas.
>
> Thanks!
>
> A
One more note. There are multiple "link up" messages in the log. The LED
never stopped the flashing which indicates tha
Hi,
There have been some changes to the scan code and iwn scan timeout code.
Andriy may have some ideas.
Thanks!
A
On Aug 19, 2016 3:48 PM, "Kevin Oberman" wrote:
> Lately I have had serious issues with my system successfully associating.
> These were not present with 10.3.
>
> > uname -a
> F
Lately I have had serious issues with my system successfully associating.
These were not present with 10.3.
> uname -a
FreeBSD rogue 11.0-BETA4 FreeBSD 11.0-BETA4 #1 r303806: Sat Aug 6 18:50:50
PDT 2016 root@rogue:/usr/obj/usr/src/sys/GENERIC.4BSD amd64
iwn0@pci0:3:0:0:class=0x028000 ca
20 matches
Mail list logo
