This bug report unfortunately appears to have been co-opted for a couple different issues, spread across two releases. I'm going to focus here on the issues that apply to intrepid.
I've recently (post-beta) patched hal in intrepid to support the kernel's new generic rfkill interface, to address bug #267875 - I wasn't aware that this bug was also open at the time. Could the users who are seeing this problem please re-test with the latest hal package version to verify whether this problem is resolved for you? If there is really a bug in the kernel driver then of course it will not, but I haven't seen any bugs in the kernel driver here - the "bug" may simply be that the backported iwlwifi drivers were using the generic rfkill interface which wasn't supported yet in 2.6.24.
This bug report unfortunately appears to have been co-opted for a couple different issues, spread across two releases. I'm going to focus here on the issues that apply to intrepid.
I've recently (post-beta) patched hal in intrepid to support the kernel's new generic rfkill interface, to address bug #267875 - I wasn't aware that this bug was also open at the time. Could the users who are seeing this problem please re-test with the latest hal package version to verify whether this problem is resolved for you? If there is really a bug in the kernel driver then of course it will not, but I haven't seen any bugs in the kernel driver here - the "bug" may simply be that the backported iwlwifi drivers were using the generic rfkill interface which wasn't supported yet in 2.6.24.