Jul 20 09:52:53 notebook-rhsoft kernel: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection Jul 20 09:52:53 notebook-rhsoft kernel: iwl3945: Unhandled INTA bits 0x04000000 Jul 20 09:52:53 notebook-rhsoft kernel: iwl3945: Disabled INTA bits 0x04000000 were pending Jul 20 09:52:53 notebook-rhsoft kernel: iwl3945: with FH_INT = 0x00000000 Jul 20 09:52:53 notebook-rhsoft kernel: iwl3945: Could not read microcode: -22 Jul 20 09:52:53 notebook-rhsoft kernel: iwl3945: probe of 0000:06:00.0 failed with error -22 BTW: With this kernel unter kde i could not change volume-level Have now running the kernel-2.6.21-1.3228.fc7 again on my hp-pavilion
Problem seems to be "iwlwifi-firmware.noarch 2.14.3-2" With iwlwifi-firmware.noarch 2.14.4-1 from testing it works with 2.6.22, but this firmware kills iwl3945 unter 2.6.21 iwl3945 is generally strange, if it connects while booting - all works perfect, if you lost your connection a rmmod/modprobe and restart auf wpa_supplicant in many cases will not bring back connection :-(
Yes, the firmware update is required for the later version of the driver. It will be pushed at the same time as the updated kernel. There are many open issues regarding iwl3945. Perhaps the 'lost connection' problem you report matches one of those? If not, feel free to open a new bug to cover that.
*** Bug 249131 has been marked as a duplicate of this bug. ***
*** Bug 249123 has been marked as a duplicate of this bug. ***
I see that kernel-2.6.22.1-27.fc7 has been pushed to stable, but the firmware hadn't been :-( I've just asked to have that done through bodhi now.
Mhh and it makes me angry Does the last time no one think before publishing kernels the last 2.6.21 with dependecies on new mkinitrd was published while mkinitrd was hanging in "updates-testing" This should not happen often because normal users have big troubles with such actions!
*** Bug 249170 has been marked as a duplicate of this bug. ***
*** Bug 249331 has been marked as a duplicate of this bug. ***
*** Bug 249386 has been marked as a duplicate of this bug. ***