Comment 15 for bug 177624

Hi. I'm having the same problem as you, have you found a solution?

Thanks.

On Sun, Mar 23, 2008 at 4:54 AM, czk <email address hidden> wrote:

> I cannot use iwl3945 to connect an ap far away. even it can hardly be
> discovered.
> when i boot with a feisty cd, using ipw3945, it works fine. signal
> strength shows about 40/100.
> the problem not fixed yet.
>
> --
> iwl3945 has very poor signal reception, whereas ipw3945 works perfectly
> https://bugs.launchpad.net/bugs/177624
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Intel Linux Wireless project upstream project presentation in
> launchpad.: Fix Released
> Status in Source Package "linux" in Ubuntu: Fix Released
>
> Bug description:
> 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
> Connection (rev 02)
>
> With the ipw3945 module in the .22 kernel I had great reception, signal
> strength, and a stable connection. My Wifi here is pretty weak, since it
> needs to go through 3 walls and the sender is across the street (my shoe
> string internet), but it worked just fine with ipw3945 (Quality=38/100
> Signal level=-86 dBm Noise level=-86 dBm). On my previous laptop with a
> bcm43xx it also worked.
>
> Now, with iwl3945 it does not even detect the essid reliably. When I poll
> "iwlist scanning" I occasionally see it for a second, then it disappears
> again. I never see it in n-m.
>
> Maybe the replacement for the non-free HAL is too conservative about
> signal strenght?
>
> Any chance we could ship ipw3945 as an alternative until iwl3945 gets
> better?
>