Comment 12 for bug 337929

OK, running Andy's deb, I see his printk, and things work (no oops).

Running lbm updated to master-2009-03-24 from ubuntu-jaunty-lbm.git without Andy's patch, things *also* work.

Regarding the comments on the the CRDA framework, I've now shifted my home AP to channel 13.

Using the master-2009-03-24 lbm build, without the module option, I *cannot* connect, and dmesg shows it going into the US regdom:
[ 14.740421] cfg80211: Using static regulatory domain info
[ 14.740445] cfg80211: Regulatory domain: US
[ 14.740451] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.740459] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 14.740466] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740473] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740481] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740488] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.740496] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 14.740609] cfg80211: Calling CRDA for country: US
[ 14.882164] cfg80211: Regulatory domain changed to country: US
[ 14.882175] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.882182] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 14.882188] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 14.882193] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.882199] (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.882205] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

So, then I *uninstalled* lbm completely to test the cfg80211 shipping in Jaunty's main kernel, removed the lbm modules and modprobed the older ones - and this *did* connect:
[ 374.154294] cfg80211: Calling CRDA to update world regulatory domain
[ 374.253460] cfg80211: World regulatory domain updated:
[ 374.253471] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 374.253480] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 374.253487] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 374.253495] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 374.253502] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 374.253509] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

Shall we proceed from here by leaving this bug for the oops, and I'll file another concerning the need to manually specify regulatory domain in the backports-modules, but not for the main kernel?

(The -2.6.28 bugtask here could then be marked "Fix Committed" on the strength of what's currently in ubuntu-jaunty-lbm.git, though the Intrepid/-2.6.27 one still needs attention.)