On Tue, 2010-12-14 at 09:47 +0300, Jonathon Anderson wrote: > On Tue, Dec 14, 2010 at 4:51 AM, Ben Hutchings <email@example.com> wrote: > > A log with timestamps would be more helpful. > > I've attached a copy of log/messages that contains the error. It's a > different instance, but a reoccurrence of the same thing. > > You'll probably want to grep it for "b43", but I left the log intact > in case any of the surrounding context would be useful. Thank you. > Note that, though I had said this for the previous log: > > >>The preceding log was generated by 2.6.36. > >> 2.6.32 generated largely similar logs, except that it recommended PIO > >> mode, rather than purporting to switch to it. [...] Debian's package of Linux 2.6.32 includes all the later fixes that implement automatic switching to PIO mode. It is only missing the correction to that message. I don't if it will help, but you can force b43 to use PIO mode from the start by running: rmmod b43 modprobe b43 pio=1 If that helps, you can make this configuration persistent by running: echo >/etc/modprobe.d/b43.conf 'options b43 pio=1' Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part