On Monday 09 May 2011 23:46:06 walt wrote: > On 05/09/2011 09:20 AM, John Nielsen wrote: > > I got it working like I want by: > > 1) Including RFKILL in my kernel config and 2) Building cfg80211, > > mac80211, rfkill, and all parts of the ath9k driver as modules > > > > Just adding RFKILL to a static (module-less) kernel didn't fix it, > > and just building cfg80211 and friends as modules without RFKILL also > > didn't fix it; I had to do both. > > Some drivers contains quite a few distinct subsystems, and I can > imagine a scenario where some section of code is executed only when > it gets loaded by another driver module. > > If my SWAG is correct, then I think a bug report would be appropriate. > Unfortunately I have no idea if I'm guessing right or wrong :) > > As Mick said, the same problem has been reported with alsa drivers, > and I would consider that to be buggy behavior as well and I would > file a bug report if I had the same problem. (But I don't.)
Funny you should say that ... I remember raising a bug at the time, only to be told by a dev that this is what alsactl expects (i.e. alsa modules to probe in a particular order). I was reluctant to engage in an argument with a dev about the logic of all this, so I left happy knowing that I could hear sound coming out of my machine again. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
