On Thu, Mar 25, 2010 at 06:44:01PM -0400, Bob Copeland wrote: > On Thu, Mar 25, 2010 at 6:24 PM, nanok <rnanok@xxxxxxxxx> wrote: > > On Thu, Mar 25, 2010 at 05:04:02PM -0400, Bob Copeland wrote: > >> On Thu, Mar 25, 2010 at 5:02 PM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: > >> > >> > As you are using debian I have to ask: have you installed > >> > crda? ?Since 2.6.30 ath5k gained regulatory support which > >> > may cause certain channels to be disabled. > >> > >> By "since 2.6.30" I meant post-2.6.30, sorry for any > >> confusion. > >> > >> -- > >> Bob Copeland %% www.bobcopeland.com > >> > > > > hi Bob, > > > > no confusion, it's perfectly clear either way you state it. > > unfortunately, it's 2.6.3 > > 0 that "works" (not pre-2.6.30), or did you mean since 2.6.30, excluding > > 2.6.30? > > Right, that is what I tried to correct. _After_ 2.6.30, > ath5k began reporting the regdomain from the EEPROM which > means some channels (13 is a common case) are no longer > accessible whereas they were before with static reg domains > and no EEPROM support. That was the major change in the > driver. Most other changes since 2.6.30 were in the > upper-layers. I don't recall any changes to crypto in that > timeframe. > > WRT to the original report, is only WEP causing problems > (i.e. does WPA work?) > > -- > Bob Copeland %% www.bobcopeland.com > wpa works with wpa_supplicant, i haven't tested in a while, but i can as soon as i get home. plain also works (no encryption). iirc, the original "plaintif" experienced the same. to keep things accurate, i have experienced again a lock up (kernel panick) while i was trying to get the wlan0 up (ath5k), and getting errors, so now i have switched back to ath-pci (madwifi). there might be something wrong with my hardware (additionally). -- nanok -- 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
