On Tue, Jun 17, 2008 at 05:19:24PM +0200, Pietro Cerutti wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Andrew Thompson wrote: > | On Fri, Jun 06, 2008 at 12:58:32PM +0200, Pietro Cerutti wrote: > |> -----BEGIN PGP SIGNED MESSAGE----- > |> Hash: SHA512 > |> > |> | > |> | Does it still happen if you limit the channels, try > |> | > |> | ifconfig wlan0 chanlist 1-11 > |> > |> > |> !!!! No it doesn't, actually it works this way! > |> > |> So, it was a config problem at my side? > |> > |> Thanks a lot.. > | > | The eeprom on the card is meant to list the valid channels and the > | driver checks for this. I dont know why channel 13 is valid but the > | firmware borks on it. If you are feeling motivated you can add a few > | printfs in wpi_read_eeprom_channels() to try and see why. > > Ok I've added a few device_printf in that function, the output is here: > http://gahr.ch/FreeBSD/misc/wpi_chans.txt > I don't see anything wrong with that, do you? YEs, channel 13 which is the one causing the firmware error is showing as !VALID wpi0: adding chan 13 flags=0x21 maxpwr=15, offset 26 wpi0: READ_EEEPROM_CHANS: chan 13 on band 0 is UNKNOWN So it should not be added to the channel list. Can you show me a diff of your printf changes so I can see what the difference between VALID & UNKNOWN is. AndrewReceived on Tue Jun 17 2008 - 13:41:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:32 UTC