Is 802.11a supposed to work with wpi?
gavin.atkinson at ury.york.ac.uk
Wed Dec 30 11:22:10 UTC 2009
On Tue, 29 Dec 2009, Paul B Mahol wrote:
> On 12/29/09, Doug Barton <dougb at freebsd.org> wrote:
> > Paul B Mahol wrote:
> >> What are other debug printfs?
> > I sent everything that came out of 'grep -i wpi /var/run/dmesg.boot'
> >> # ifconfig wlan0 list chan
> > Channel 1 : 2412 Mhz 11g Channel 40 : 5200* Mhz 11a
> > Channel 2 : 2417 Mhz 11g Channel 44 : 5220* Mhz 11a
> > Channel 3 : 2422 Mhz 11g Channel 48 : 5240* Mhz 11a
> > Channel 4 : 2427 Mhz 11g Channel 52 : 5260* Mhz 11a
> > Channel 5 : 2432 Mhz 11g Channel 56 : 5280* Mhz 11a
> > Channel 6 : 2437 Mhz 11g Channel 60 : 5300* Mhz 11a
> > Channel 7 : 2442 Mhz 11g Channel 64 : 5320* Mhz 11a
> > Channel 8 : 2447 Mhz 11g Channel 149 : 5745* Mhz 11a
> > Channel 9 : 2452 Mhz 11g Channel 153 : 5765* Mhz 11a
> > Channel 10 : 2457 Mhz 11g Channel 157 : 5785* Mhz 11a
> > Channel 11 : 2462 Mhz 11g Channel 161 : 5805* Mhz 11a
> > Channel 36 : 5180* Mhz 11a Channel 165 : 5825* Mhz 11a
> While scanning does wpi0 uses 11a channels?
> How scan output should look like?
> Enable all wpi debug output (explore wpi source a little bit ... for
You need to set the tunable debug.wpi before loading the module. Set it
to 0x82, enable bootverbose and then load the module. I see you also
don't have the revision D hardware, which is the only one the driver
actively knows about.
It's also interesting that all the A channels are listed as being passive,
what regdomain do you have set (ifconfig wlan0 will say)? You could try
changing the regdomain (IANAL) and see what happens.
More information about the freebsd-current