On 11/22/05, vincent wang <Vincent.Wang at sun.com> wrote: > Brendan Gregg wrote: > > >A cardbus wireless card detects ok, plumbs ok, has blinking lights ok, > >appears to be furiously scanning - but never detects anything. A > >"wificonfig -i ath0 scan" returns nothing, and syslog gets the following, > >Nov 20 03:04:03 laptop genunix: [ID 765170 kern.warning] WARNING: ath: > >ieee80211_end_scan(): no scan candidate > >? > > > > > > > It's an interrupt routing problem. > That message is usually because the ath driver recives no interrupt. (It > can transmit packets but receives nothing.) > We've seen this occasionally on some laptops. There can be two reasons: > 1) The driver fails to register its interrupt correctly (The interrupt > vector number could be wrongly translated) > 2) the interrupt is not in level-triggered mode.
I get the same thing sometimes, but my wireless card is mini pci. Nov 4 15:58:36 lw genunix: [ID 765170 kern.warning] WARNING: ath: ieee80211_end_scan(): no scan candidate Nov 4 16:05:14 lw last message repeated 181 times Other times it works beautifully: I'm writing this email with the laptop right now.. -- Eric Enright
