Comment 63 for bug 190664

Revision history for this message
Tomas Gustavsson (tomplast) wrote : Re: [Bug 190664] Re: [XPS M1530] Wireless don't work (need to use 'noapic' kernel boot param)

I did that as well (why I didn't report it I don't know) but it wasn't
even detected as remembered it. I didn't do any thorough test or
anything like that so perhaps a few reboots would solve it. By
unloading and loading the iwl3945 module I get the following message
in Intrepid:

[10865.482145] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network
Connection driver for Linux, 1.2.26ks
[10865.482158] iwl3945: Copyright(c) 2003-2008 Intel Corporation
[10865.482245] iwl3945 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[10865.482270] iwl3945 0000:0b:00.0: setting latency timer to 64
[10865.482301] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[10865.488018] iwl3945: Error: saturation power is -1, less than
minimum expected 40
[10865.488024] iwl3945: Invalid power index
[10865.488029] iwl3945: initializing regulatory failed: -5
[10865.498274] iwl3945 0000:0b:00.0: PCI INT A disabled
[10865.499581] iwl3945: probe of 0000:0b:00.0 failed with error -5

If my memory isn't failing on me then that's more or less identical to
the messages I got in Hardy.

Best regards

/Tomas "tomplast" Gustavsson

Btw, I'm currently running Ubuntu "Intrepid Ibex" 8.10 right now, no
wireless is detected there for me.
2008/9/18 Leann Ogasawara <email address hidden>:
> Hi Guys,
>
> Wow, you shouldn't need to do any sort of patching/building of custom
> kernels to test. The easiest way to test will be to burn a LiveCD of
> the latest alpha image which uses this newer 2.6.27 kernel.
> http://www.ubuntu.com/testing/intrepid/alpha5 . Alpha6 will come out
> likely today/tomorrow if you'd like to wait and test the most recent,
> just watch http://www.ubuntu.com/testing for Alpha6 to hit.
>
> --
> [XPS M1530] Wireless don't work (need to use 'noapic' kernel boot param)
> https://bugs.launchpad.net/bugs/190664
> You received this bug notification because you are a direct subscriber
> of the bug.
>