Comment 21 for bug 263106

Well, I compiled a custom 2.6.30.3 kernel, just to see if the current b43 driver works with the firmware Jaunty's fw-cutter downloads. It does work. Perfectly. As I've tried multiple other firmware sources, it seems evident to me this is an Intrepid and Jaunty bug -- I'll have to test a Karmic alpha one of these days to see if it's something which has been resolved. I'm running 32bit x86, P4 on a d865perl motherboard.

So here are some facts:

linux-image-2.6.24-24-generic ***works
linux-image-2.6.30.3-vanilla ***works

linux-image-2.6.28-11-generic ***flaky, and not usable
linux-image-2.6.28-13-generic ***flaky, and not usable
linux-backports-modules-jaunty ***completely broken, and b43 depends on pcmcia for this one?!

Next I'll try 2.6.28.10 vanilla and post logs. If you would prefer for me to test a different 2.6.28.xy please mention which revision.

Then I'll post logs for linux-image-2.6.28-13-generic with linux-backports-modules installed.
And then without. All comments will contain:

1. `uname -a`
2. `dmesg > dmesg.log`
3. `lspci -vvnn > lspci-vvnn.log` (as root)

'hopefully the logs from all of these will encircle and help us to isolate where exactly the problem is. Please advise me which debugging opions I ought to enable. A few backtraces would probably make it much easier, but I don't know anything about kernel-specific debugging...

bugs 405712, 297959, and 263106 all look like b43 kernel module problems (as opposed to firmware problems)
I'm not sure if they're simply duplicates, or some other type of relation...

At any rate...

1. 1. Linux DigitalMercury.dynalias.net 2.6.30.3-digitalmercury #1 Tue Jul 28 11:58:06 MDT 2009 i686 GNU/Linux
2. dmesg.log