Same problem here.
[ 6951.725704] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection
driver for Linux, 1.2.0
[ 6951.725713] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[ 6951.725875] ACPI: PCI Interrupt :03:00.0[A] - GSI 18 (level, low) -
IRQ 18
[ 6951.725902] PCI: Setting
Neither lbm's 1.2.25 nor lum 1.2.0 work for me when connecting to WEP
wireless when using hex/ascii key. Switching from iwlwifi to ipw3945 or
ndiswrapper solves this problem.
WPA has always worked and continues to do so. I am running kubuntu hardy
64 bit kde 3.5 edition. I can provide additional
Marking this Fix Released against the linux-backports-modules-2.6.24
package as there are multiple comments here verifying it resolves the
issue. Also Mathew, the original bug reporter, made a comment this was
resolved in Hardy for him. Thanks.
** Changed in: linux-backports-modules-2.6.24
For what it's worth, this problem has nothing to do with password
authentication. I had the same problem on a totally open network.
Fortunately the backports-modules fixed everything for me.
Obviously I'd like to nominate this fix for a mainline update.
--
Unable to connect to WEP encrypted
I can confirm that I am able to connect to a WEP64 encypted network
using the backports modules with Hardy.
Thanks.
--
Unable to connect to WEP encrypted network when using iwl3945 module (but
success when using ipw3945)
https://bugs.launchpad.net/bugs/176602
You received this bug notification
I used to be able to connect to a WEP wireless network with Gutsy. Hardy
simply does not work.
FIY:
Running Dell Inspiron 6400 with Hardy:
~ % sudo linuxinfo
Linux duo 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008
Two Intel Unknown 1000MHz processors, 6653.73 total bogomips, 1002M RAM
Hello again (I am the author of the last post),
Installing linux-backports-modules-2.6.24-16-generic solved the
problem.
The new version of the driver iwl3945 solved it.
~ % sudo modinfo iwl3945 | grep srcversion
srcversion: FDE2E62843DE3ED112A50C3
--
Unable to connect to WEP encrypted
Thank you, Thank you, Thank you Francisco!!!
I am able to connect now using WEP and the iwl3945 ver 1.2.25 that was
included in the solution you provided. I tried installing from
add/remove, but could not find the package. So I updated from the
command line:
sudo apt-get install
I am having the SAME problems attaching to a WEP 128 wireless network.
This all works fine with Fiesty, Gutsy and IPW3945 module. This has
NEVER worked for me with Hardy Heron 8.04 LTS beta or now the updated
release candidate updated and installed 4/19/2008. I have a Dell D520
and will provide
** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Triaged
--
Unable to connect to WEP encrypted network when using iwl3945 module (but
success when using ipw3945)
https://bugs.launchpad.net/bugs/176602
You received this bug
Did a dist-upgrade today and it doesn't work. relevant dmesg
[ 139.109142] wlan0_rename: Initial auth_alg=128
[ 139.109153] wlan0_rename: authenticate with AP 00:16:47:5c:e5:40
[ 139.109179] wlan0_rename: privacy configuration mismatch and
mixed-cell disabled - disassociate
[ 139.110764]
Hi Everyone,
An updated version of the iwlwifi drivers (version 1.2.25) was recently
added to the linux-backports-modules-2.6.24 package. It would be good
if you could retest with lbm once it is published and available:
https://edge.launchpad.net/ubuntu/+source/linux-backports-
modules-2.6.24/ .
** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) = Ubuntu Kernel
Team (ubuntu-kernel-team)
--
Unable to connect to WEP encrypted network when using iwl3945 module (but
success when using ipw3945)
[EMAIL PROTECTED]:~$cat /proc/version_signature
Ubuntu 2.6.24-12.22-generic
** Attachment added: dmesg
http://launchpadlibrarian.net/12923115/dmesg.log
--
Unable to connect to WEP encrypted network when using iwl3945 module (but
success when using ipw3945)
** Attachment added: lspci
http://launchpadlibrarian.net/12923118/lspci-vvnn.log
--
Unable to connect to WEP encrypted network when using iwl3945 module (but
success when using ipw3945)
https://bugs.launchpad.net/bugs/176602
You received this bug notification because you are a member of
** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu)
Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)
--
Unable to connect to WEP encrypted network when using iwl3945 module (but
success when using ipw3945)
https://bugs.launchpad.net/bugs/176602
You received this bug
Latest driver from http://linuxwireless.org/en/users/Download fix the
issue.
[ 108.302649] wlan0_rename: Initial auth_alg=0
[ 108.302659] wlan0_rename: authenticate with AP 00:30:bd:c3:c5:da
[ 108.304724] wlan0_rename: RX authentication from 00:30:bd:c3:c5:da (alg=0
transaction=2 status=0)
[
Hi Mackenzie, thanks for testing Hardy. For anyone else interested, the
Hardy Heron Alpha series is currently under development and contains an
updated version of the kernel. It would be helpful if everyone else
could test the latest Hardy Alpha release:
http://www.ubuntu.com/testing . You
This is also a problem in Hardy. I'm marking it as such. I've tried
two different networks and it just keeps asking for the password over
and over if it's WEP.
** Also affects: linux-ubuntu-modules-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
--
Unable to connect to WEP
I don't know if it is related to the iwl3945 or ipw3945, but I'm running
7.10 on a dell cpi d266xp with a 3com-card and it lights and blinks
quite a lot and almost connects to a non-secure network.
I agree with Goel that this is a critical bug, so I hope I am
contributing with dumps from dmesg,
Hello again,
(tried to edit the message above, but since that wasn't possible, I add a new
comment).
I noticed in the logs that there was a session running. I killed that one and
choose an open network again. This time it connected. So it seems that NM or
something does not kill connections to
This has been broken for a while and I do not see any feedback from the
maintainers and it looks like a critical bug to me. If you need any
additional information, I'll be more than happy to provide it but please
do provide some sense of what is being done to address this. Thanks.
--
Unable to
I can confirm a rather similar behaviour on my D630 with Gutsy. The
ip3845 does not work in a stable manner and the iwl3945 is not able to
join WEP protected access points.
Here is an excerpt form the syslog:
Jan 14 06:58:54 w2fz2wqq01 kernel: [ 626.90] wlan0: RX AssocResp from
It seems that there are issues connecting to a WPA (not WPA2) encrypted
network as well. On the off chance that the router(s) themselves have
something to do with it, the test configurations I've used are as
follows:
Linksys router using WPA2 encryption worked fine (albeit with reduced signal
It looks like a fix has been implemented in the modules in Hardy (alpha
2). I am posting this from the AMD64 live cd I just burned, on the
wireless network I have not been able to connect to while in my Gutsy
installation. Any chance this will find its way into backports (or a
more appropriate
I'm seeing the same thing as well with WEP 64 bit authentication. This is on a
Dell 1420 laptop.
ipw3945 works but the connection is prone to freezing as documented on Dell's
website. Below is the lspci and dmesg output. Please let me know if you need
any more information to debug this
26 matches
Mail list logo
