Hi, On Wed, Oct 29, 2008 at 12:38:41AM +0100, Dominik Brodowski wrote: > On Tue, Oct 28, 2008 at 04:32:40PM -0700, reinette chatre wrote: > > On Tue, 2008-10-28 at 16:15 -0700, Johannes Berg wrote: > > > On Tue, 2008-10-28 at 13:23 -0700, reinette chatre wrote: > > > > > > > (adding linux-wireless so I am keeping the log below) > > > > > > > > This helps a lot - thanks! > > > > > > > > Could you please recompile wireless with CONFIG_WIRELESS_OLD_REGULATORY? > > > > > > Btw, any idea why this helps? Shouldn't the driver just work, albeit > > > with a restricted channel set? Are we messing something up like no > > > usable channels at all? (I fixed a bug like that IIRC) > > > > > > > Without the regulatory information the number of 5G channels to scan is > > zero. > > But what about the 2.4G channels? This is the one I'd like to use here, and > this is the one which is used with the correct firmware... > > wlan0 IEEE 802.11abg ESSID:"<not reported on this list>" > Mode:Managed Frequency:2.417 GHz > Bit Rate=54 Mb/s Tx-Power=15 dBm > Retry min limit:7 RTS thr:off Fragment thr=2352 B > Power Management:off > Link Quality=96/100 Signal level:-31 dBm Noise level=-127 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > Will test with CONFIG_WIRELESS_OLD_REGULATORY soon. With CONFIG_WIRELESS_OLD_REGULATORY=y, both the old and the new firmware works. Without, only the old firmware works. I'd think that at least the error message could be clarified a bit (is it really a "Microcode SW error"?)... also, it might be a corner case whether the new firmware would better be called -2 because of this incompatibility? Best, Dominik -- 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
