Thanks for the update Rune. Since you are the original bug reporter,
I'm going to go ahead and close this report. For anyone else still
experiencing issues, please open a new bug report -
https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks.
** Changed in: linux (Ubuntu)
Status:
This bug is now solved for me !
I am using a Linksys WRT54Gv4 with DD-WRT v23 SP2 firmware, and have
been experiencing problems with assoicating with this AP as described in
the first comment in this bug report.
But after resetting the NVRAM of my router, I am able to associate with
my AP. This
@Alan
For me it has not worked since 2.6.24-19-generic, including 2.6.27-9,
with and without backport-modules, so I suspect that I am experiencing a
different bug than you.
Rune
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received
Leann,
Installing kernel 2.6.27-11-generic and linux-backport-modules for -11
from proposed does not solve my association problem.
Regards
Rune
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you
@Rune
It worked for me with -9-generic, but when I updated to -11 it broke
again.
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Leann,
Using kernel 2.6.27-7-generic I am affected by
https://bugs.launchpad.net/bugs/294667 when installing the backport
modules, so I am unable with this kernel and backport module version.
Using kernel 2.6.27-9-generic the backport modules loads fine, but I
cannot associate with my AP as
When testing with the Jantu 2.6.28 kernel, I am not able to connect to
my AP with my iwl3945 device as well as the Zydas USB device. I tested
with kernel https://edge.launchpad.net/ubuntu/jaunty/i386/linux-
image-2.6.28-3-generic/2.6.28-3.4
My wireless network is not listed in n-m under any of
** Attachment added: Excerpt of daemon log when using the iwl3945 chipset
http://launchpadlibrarian.net/20543509/daemon.log-iwl3945
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a
** Attachment added: ..using the zydas device
http://launchpadlibrarian.net/20543526/daemon.log-zydas
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
I installed linux-backports-modules-intrepid but same behavior: wlan0 do
not bekomes ready.
snip
kon...@amilo:~$ sudo dpkg-query -l linux-backports-modules-intrepid
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
|
I have installed linux-backports-modules-intrepid on my (pretty base
install) of Kubuntu intrepid which has resolved the issue of connecting
to WPA secured wireless networks with network manager and kernel
2.6.27-9-generic.
Thanks Leann!
--
iwl3945 not able to associate with kernel 2.6.26 and
For those still having issues, care to try installing the linux-
backports-modules-intrepid package to see if it helps. It contains and
updated compat-wireless stack. Please let us know your results.
Thanks.
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/ubuntu/+source/linux-backports-
modules-2.6.27/+bug/294667/
That might be not that easy...
Anyway, I tried 2.6.28-3 from jaunty -which I think still has an old
version of wireless-compat, as I only get mac80211 loaded and not those
lbm modules I saw in backports-, and
Hi all,
I run Intrepid with 2.6.27-9-generic kernel-image and have also trouble with
iwl3945.
I do not use network-manager so I try to connect to my home-wlan by
wpa_supplicant and /etc/network/interfaces fileconfigs.
But I think that makes nothing, because even when loading iwl3945 i see
Same as yours!
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
[Golan] Network Connection (rev 02)
Subsystem: Intel Corporation Device 1020
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+
Reloading iwl3945 module doesn't help for me.
Geek87,
did wireless work for you using 2.6.24-19-generic (in Hardy) ?
Wireless was working fine on my computer until 2.6.24-19-generic, after this
(in both Hardy and Intrepid) it has been completely broken. It does however
work fine with an Zydas
I have the problem since Hardy. It's normal before that the driver
wasn't iwl3945 but ipw3945.
Le samedi 06 décembre 2008 à 19:12 +, Rune Evjen a écrit :
Reloading iwl3945 module doesn't help for me.
Geek87,
did wireless work for you using 2.6.24-19-generic (in Hardy) ?
Wireless
I have similar issue using intrepid with last kernel 22.6.27-10-generic iwl3945
filename:
/lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
license:GPL
author: Copyright(c) 2003-2008 Intel Corporation
version:1.2.26ks
description:
Hi,
I can't connect at all with Network Manager on my home wifi protected by
personal WPA2.
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi all,
has anybody pursued this bug further?
I still have shaky wireless connection with Network Manager is the network
signal has a medium stregth (when its below 70% it disconnects happily and I
have to click it back!)
Thanks, Truxpin
--
iwl3945 not able to associate with kernel 2.6.26
Hi,
I have the same problem as Truxpin when testing from the release
candidate ISO. If I try to connect with the laptop sitting very close
from the AP I can not connect to a WPA2 Personal network. If I move the
laptop a couple of meters way from it, it starts working flawlessly.
Interesting
Rune,
the problems started after a recent upgrade, so I think it may happen to
others...
See my daemon.log from this morning bootup... I filtered out the NetworkManager
entries.
This is a successful connection. Also I'm now at near arm distance from my AP
antenna... it stays up this way.
Got very similar problem with nm but with 2.6.24-21.
It looks to me that it may be related to the signal strength and or the
proximity of another AP with signal level close to the one to which i'm
connected at the moment.
If I work at a couple of meter from my home AP nm seems to never lose
Truxpin,
My wireless connection worked fine until I upgraded to 24-21 in hardy,
and later all intrepid kernels.
Do you get similar errors in your syslog as I get ? See attached part of
syslog where I attempt to associate (at a distance of 1 m from the AP).
I can successfully associate with a
Also, using 2.6.27-7 I get a different dmesg output than XaRs and myself
(using 2.6.27-2, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264881/comments/3).
I get lots of
[12455.744842] iwl3945: No space for Tx
[12455.744846] iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd
I have the same problem in my house. I use Intrepid which I update
everyday, a IPW3945 with iwl3945 driver and NetworkManager to connect to
my home wifi which is protected with WPA2 personal. I can't connect and
obtain a line Link timed out and Association took too long at the
next line in the
Same here!
But only in a certain networks!
In my work, using WPA2 is working fine, (intrepid,2.6.27-4) but in my
house the problem is the same as sebastian.
Hardware and dmesg attached.
** Attachment added: lshw.txt
http://launchpadlibrarian.net/18103021/lshw.txt
--
iwl3945 not able to
SUCCESS CONNECTION DMESG
** Attachment added: dmesg_success.txt
http://launchpadlibrarian.net/18103029/dmesg_success.txt
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
I have a similar problem: The WLAN (iwl3945, Intel Corporation PRO/Wireless
3945ABG) associates, then disassociates about 5 seconds later, then associates,
then disassociates, and so on. Also, association takes very long (about 30
seconds).
This happens with linux-image-2.6.27-4-generic in
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Triaged
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug
I tested a bit further with as Wireless USB device, reported by lsusb as
a ZyDAS 802.11b/g USB2 WiFi.
With this device I can associate with my network using kernel 2.6.27-2.
Please note that nm-applet lists my network (with a bar of around 80%)
under the Zydas device, but the network is not
Leann,
I've attached various logs that I hope can support the debugging.
Some strange things (see nm-password.png):
1. When upgrading to intrepid, and booting into 27-2, nm-applet did not detect
my network, but when I chose connect to other wireless network it reasks for
the passphrase each
** Attachment added: dmesg-2.6.24-19-generic
http://launchpadlibrarian.net/17341654/dmesg-2.6.24-19-generic
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: syslog-2.6.24.19-generic
http://launchpadlibrarian.net/17341659/syslog-2.6.24.19-generic
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: nm-password.png
http://launchpadlibrarian.net/17341662/nm-password.png
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: syslog-2.6.27-2-generic
http://launchpadlibrarian.net/17341656/syslog-2.6.27-2-generic
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks Rune,
Can you attach your dmesg output after you've booted int 2.6.27-2
instead? Thanks.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
iwl3945 not able to associate with kernel 2.6.26 and 2.6.27
https://bugs.launchpad.net/bugs/264881
You received this bug
** Attachment added: syslog2
http://launchpadlibrarian.net/17295630/syslog2
** Tags added: linux-2.6.27
** Description changed:
My iwl3945 card works fine when using kernel 2.6.24-19-generic an
earlier, but after upgrading to 2.6.24-21-generic (on hardy) it is no
longer able to
38 matches
Mail list logo
