On Sun, Nov 16, 2008 at 10:52 AM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: > On Sun, Nov 16, 2008 at 10:38:39AM -0600, Dan McGee wrote: >> On Sun, Nov 16, 2008 at 10:20 AM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: >> > As you can see, the modules think "phy0" should be at offset 164, but >> > it's really at 160. >> >> > Also I noticed the original config had CONFIG_DYNAMIC_FTRACE=y, unfortunately >> > turning that off didn't seem to change anything (hmm, I didn't get a build >> > bug, was the breakage fixed in 2.6.27.y?) >> >> Note that HAVE is set if the architecture supports it; CONFIG_FTRACE >> itself was turned off (and CONFIG_DYNAMIC_FTRACE is not even present): >> $ grep FTRACE .config >> CONFIG_HAVE_FTRACE=y >> CONFIG_HAVE_DYNAMIC_FTRACE=y >> # CONFIG_FTRACE is not set > > Oh, you are right. Thanks. I probably won't be able to do any more > testing today but I would suggest trying to turn off wireless-related > options in the main kernel config and see if you can get it working > (start with cfg80211 and its dependencies...) The fun continues. If I rebuild the kernel with all wireless options turned off except WIRELESS_EXT, then build compat-wireless, our module appears to load without issues. .config: # # Wireless # # CONFIG_CFG80211 is not set CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y # CONFIG_MAC80211 is not set # CONFIG_IEEE80211 is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set dmesg: atl2: eth0 NIC Link is Up<100 Mbps Full Duplex> evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html <<< boot stopped here, then I modprobed ath5k >>> cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US ath5k_pci 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ath5k_pci 0000:01:00.0: setting latency timer to 64 ath5k_pci 0000:01:00.0: registered as 'phy0' phy0: Selected rate control algorithm 'pid' ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) wlan0: authenticate with AP 00:1c:10:21:f5:f4 wlan0: authenticated wlan0: associate with AP 00:1c:10:21:f5:f4 wlan0: RX AssocResp from 00:1c:10:21:f5:f4 (capab=0x411 status=0 aid=3) wlan0: associated I had not seen this cfg80211 stuff before when modprobing. I also see that cfg80211 is now loaded as a module- was the fact that it was built into the kernel before causing all these problems? That would be my strong suspicion, in which case this entire thread is really a bum bug report, except that compat-wireless should enforce that cfg80211 is a module just like it currently enforces that for mac80211, saving someone else this headache. -Dan -- 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
