tl;dr version:
- Interface does not work at all in any to-date Hardy kernels without creating /etc/modprobe.d/iwl3945 with a line with "disable_hw_scan=0"
- Grabbing linux-backports-modules-2.6.24-16-generic makes it spam Microcode SW errors in dmesg.
- Upgrading to 2.6.24-17 makes it spam Microcode SW errors in dmesg.
- The interface *does* work with the modules provided with the 2.6.24-16 kernel and the file described above, but upgrading in any way breaks it. This includes the backported -17 kernel as well as all the backported module packages currently available to both -16 and -17.
I posted a bug earlier which, I see now, seems to be more or less a duplicate of this one.
https:/ /bugs.launchpad .net/ubuntu/ +source/ linux-backports -modules- 2.6.24/ +bug/226134
tl;dr version: d/iwl3945 with a line with "disable_hw_scan=0" -modules- 2.6.24- 16-generic makes it spam Microcode SW errors in dmesg.
- Interface does not work at all in any to-date Hardy kernels without creating /etc/modprobe.
- Grabbing linux-backports
- Upgrading to 2.6.24-17 makes it spam Microcode SW errors in dmesg.
- The interface *does* work with the modules provided with the 2.6.24-16 kernel and the file described above, but upgrading in any way breaks it. This includes the backported -17 kernel as well as all the backported module packages currently available to both -16 and -17.
See the link to my bug for logs.