I am also experiencing this bug after upgrading from 10.04 to 11.10.
In 10.04 (fresh install) I did not had any problems, it started right
after upgrading. Tried all configs above, (and associate=0 was already
the default). Perhaps most people here upgraded their laptops and this
became quiet?
Sorry for the very late reply. Changing the module's roaming option
didn't change anything - I'm still resorted to using wicd (with no 3g
support...)
-Stian
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you
On Mon, Aug 31, 2009 at 04:30:17PM +0200, Stefan Bader wrote:
Stian Jordet wrote:
Here's mine:
/sys/module/ipw2200/parameters/associate:0
/sys/module/ipw2200/parameters/auto_create:1
/sys/module/ipw2200/parameters/roaming:1
Alexander, you mentioned that roaming probably should also be
Stian Jordet wrote:
Here's mine:
/sys/module/ipw2200/parameters/associate:0
/sys/module/ipw2200/parameters/auto_create:1
/sys/module/ipw2200/parameters/roaming:1
Alexander, you mentioned that roaming probably should also be turned off, righ?
Stian, you might try to add options ipw2200
As there has been a relationship to the modules options before, can one of you
add the output of grep . /sys/module/ipw2200/parameters/* (with the module
loaded)?
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification
Here's mine:
/sys/module/ipw2200/parameters/antenna:0
/sys/module/ipw2200/parameters/associate:0
/sys/module/ipw2200/parameters/auto_create:1
/sys/module/ipw2200/parameters/bt_coexist:0
/sys/module/ipw2200/parameters/burst_duration_CCK:0
/sys/module/ipw2200/parameters/burst_duration_OFDM:0
My laptop is currently having other technical issues (video card is
bad), but I'll attempt to give as much info as I can.
I started having this issue with kernel 2.6.27-7, and no kernel version
since has worked properly for me. See my bug report
Hmm. I've upgraded to karmic tonight (using dist-upgrade, did not do a
fresh install). That actually just made it worse. Now it's not usable
with network-manager even with my good, old 2.6.27-11-kernel. Or the new
2.6.31-5. Wicd still works fine with any kernel I've tried, so I can
still use my
Well, while my computer is pretty hot (It's a fanless Fujitsu-Siemens
P7120), I don't it's related.
sti...@chrysler:~$ cat /proc/acpi/thermal_zone/TZ00/temperature
temperature: 40 C
As I wrote earlier, I only have this problem when using Network Manager
with kernel 2.6.28 and later.
Just to make sure this does not miss some information, was the Intrepid
installation using the backports modules version or the in-kernel one?
This can be found out with modinfo ipw2200. Both drivers would also
be using different firmware.
--
ipw2200 driver no longer works with wpa2 network
Not sure what you need from modinfo, but does this help?
version:1.2.2kmprq
vermagic: 2.6.27-11-generic SMP mod_unload modversions 586
I don't think I had intrepid-backports, but I was probably using
intrepid-updates...
Thanks :)
--
ipw2200 driver no longer works with wpa2
I am curious if anyone who was experiencing this problem with the
ipw2200 module has noticed a relationship between CPU temp and driver
stability. (For laptops, that is. Probably no effect on desktops.)
I had been intermittently experiencing the problems described in this
thread, i.e. wifi
I'm also seeing this after the upgrade to Jaunty, it seems. It works
perfectly with 2.6.27-11-generic, but fails with 2.6.28-13-generic (I
have also tried 2.6.30 from http://kernel.ubuntu.com/~kernel-ppa)
As an additional datapoint, it works when I replaced Network-Manager
with Wicd. I really
I actually was connected to a WPA2 network a few weeks ago with no issues,
though I didn't think about it until I saw this e-mail.
I'm using Kubuntu Jaunty, up-to-date, with the Network Manager widget as the
front end for networkmanager.
On Sun, Jul 12, 2009 at 12:19 AM, Alsandair Sneachta
I was able to circumvent this issue by removing network-manager and
installing wicd. Could it be that network-manager really is the
culprit? This would coincide with findings at the beginning of the
comments on this report that network-manager and the driver are
tripping each other up.
Still,
urns out my bug report here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/303802 is a
duplicate of this one. None of the proposed fixes or workarounds in
this report solve the issue in my situation. Is anyone else from this
report still following the situation (or still having problems)?
Since Jaunty final it is solved for me.
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just uploaded the latest wireless-testing bits in linux-backports-
modules-intrepid last week. Give that a try. I'm also re-assigning this
issue to Stefan.
** Changed in: linux (Ubuntu Intrepid)
Assignee: Tim Gardner (timg-tpi) = Stefan Bader (stefan-bader-canonical)
** Changed in:
@Tim: sorry for my Nominated for Jaunty! It was a mistake! I am only
affected by this bug, but not involved in fixing or releasing.
The workarounds (associate=0 and/or debug=0x43fff) do not work for me.
The symptoms here are very similar: WPA2 generates frequent Firmware
error detected.
On Sun, Dec 07, 2008 at 12:25:20PM -, Eugene Pyvovarov wrote:
Alexander Sack, I tried to remove each parameter and check what
happens. I saw that complete line with hwcrypto on this page earlier and
just copypaste it. However, without hwcrypto wifi works as well, but
when I removed debug
Hi Alexander,
sure I can post the syslog.
I typed tail -f /var/log/syslog, turned off wireless and turned it on again.
There is the result from syslog
Dec 15 17:26:09 bsn-laptop kernel: [20963.045139] ipw2200: U ipw_wx_get_name
Name: unassociated
Dec 15 17:26:09 bsn-laptop kernel:
Alexander Sack, I tried to remove each parameter and check what
happens. I saw that complete line with hwcrypto on this page earlier and
just copypaste it. However, without hwcrypto wifi works as well, but
when I removed debug option - device became unmanaged again :-\
so now my working config
On Thu, Dec 04, 2008 at 01:22:43PM -, Eugene Pyvovarov wrote:
In my own situation if I remove debug parameter - nothing works and wifi
device shows like unmanaged, but with debug parameter wifi works but i
have about 20mb syslog each day because of debug messages from wifi
card.
this
On Thu, Dec 04, 2008 at 01:50:36PM -, Greg Taylor wrote:
This is all I need on my Toshiba Tecra A4 PTA40E:
options ipw2200 associate=0
This should be the default for ipw2200 since intrepid. Is that on
hardy?
- Alexander
--
ipw2200 driver no longer works with wpa2 network
On Mon, Dec 01, 2008 at 12:02:04PM -, Eugene Pyvovarov wrote:
My wifi card in Toshiva a105-s2712 broked started from 8.10 alhpa5, and works
only with
options ipw2200 hwcrypto=1 associate=0 debug=0x43fff line in
/etc/modprobe.d/ipw2200.
Hmmm ... so we need hwcrypto too here? or is the
In my own situation if I remove debug parameter - nothing works and wifi
device shows like unmanaged, but with debug parameter wifi works but i
have about 20mb syslog each day because of debug messages from wifi
card.
--
ipw2200 driver no longer works with wpa2 network
This is all I need on my Toshiba Tecra A4 PTA40E:
options ipw2200 associate=0
Recent kernels have improved wireless to the point where it can actually
be used for extended period of times before dropping, rather than every
other minute.
--
ipw2200 driver no longer works with wpa2 network
My wifi card in Toshiva a105-s2712 broked started from 8.10 alhpa5, and works
only with
options ipw2200 hwcrypto=1 associate=0 debug=0x43fff line in
/etc/modprobe.d/ipw2200.
But it seems that now i have a lot debug messages in syslog, like:
Dec 1 14:00:22 bsn-laptop kernel: [ 1045.122852]
Hi folks,
On my shiny new ubuntu 8.10 installation, I had this error as well on a
Toshiba Satellite laptop SA50-432.
Adding:
options ipw2200 hwcrypto=1 associate=0 debug=0x43fff
to /etc/modprobe.d/ipw2200
fixed it. This file, didn't exist, so I had to create it first.
I could not connect to
I posted a similar bug under bug #291711 Is this a duplicate?
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Tim Gardner [2008-11-05 0:31 -]:
No, its not harmful.
OK, thanks. Then let's skip that for intrepid-updates.
Won't this also reduce the number of differences that we carry from
version to version?
Yes, and that's why we should absolutely do it in Jaunty.
--
ipw2200 driver no longer
SRU Justification
Impact: module-init-tools has a superfluous option for ipw2200.
Patch Description: removed extra/modprobe.d/options:'options ipw2200
associate=0'
** Also affects: module-init-tools
Importance: Undecided
Status: New
--
ipw2200 driver no longer works with wpa2
Uploaded module-init-tools_3.3-pre11-4ubuntu17
** Changed in: module-init-tools
Assignee: (unassigned) = Tim Gardner (timg-tpi)
Status: New = Fix Committed
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification
Tim, does it actually have any adverse effect to have the extra option?
If it's just superfluous, but not harmful, then I don't see the
justification for doing an SRU of module-init-tools?
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received
No, its not harmful. I had an email exchange with Scott Remnant wherein
he convinced me that I should change the driver source instead of
putting options in a modprobe file. Therefore, I reasoned that I should
remove the modprobe option once the driver is propagated. Won't this
also reduce the
This bug was fixed in the package linux - 2.6.27-7.11
---
linux (2.6.27-7.11) intrepid; urgency=low
[ Amit Kucheria ]
* STABLE queue: mac80211: fix two issues in debugfs
- LP: #275227
* SAUCE: Adds support for COMPAL JHL90 webcam
[ Ben Collins ]
* SAUCE: (no-up) x86:
module-init-tools_3.3-pre11-4ubuntu15
** Changed in: linux (Ubuntu Intrepid)
Status: Triaged = Fix Committed
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you are a member of Ubuntu
Bugs, which is
milestoning.
** Changed in: linux (Ubuntu Intrepid)
Target: None = ubuntu-8.10
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
please confirm that associate=0 is the option needed to fix this.
assigning to rtg. If associate=0 fixes this for everyone we should
definitly consider to change our default.
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Tim Gardner (timg-tpi)
--
Seems associate is on be default:
$ modinfo ipw2200
...
parm: associate:auto associate when scanning (default on) (int)
...
I confirmed the default state of 'associate' by performing:
$ cat /sys/module/ipw2200/parameters/associate
1
Creating /etc/modprobe.d/foo with:
options ipw2200
After 7 reboots there were no problems with associate=0. 2 out of 7
attempts had the problem with associate=1.
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you are a member of Ubuntu
Bugs, which is
associate=0 helps for me; I still have a weird race condition when I first
boot up since the wpa2 and non-wpa networks are both visible, and it
initially connects to the wpa2 net, then drops for the unencrypted net,
then tries wpa2, then drops, then tries again. Changing freq on the wpa2
net
I just started seeing this after upgrading intrepid packages from the
last few days. After login, network-manager tries to connect to my WPA2
network. I can get things to work again if I uncheck 'Enable wireless'
in network-manager, and then do 'rmmod ipw2200'. It takes a few seconds
to be
I'm getting this on a formerly Canonical issued Toshiba Tecra A4 PTA40E.
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I had been using the Interpid kernel for a while, and it worked okay
with ipw2200. Problems coming back from hibernation, and NetworkManager
would have some issues, but it worked at least some of the time. Now the
card still seems to work, but I get this message a /lot/ (600 times in
about 30
I'm seeing the same error in dmesg with a non-encrypted network. I'm
connecting using NetworkManager and its vpnc plugin.
The first time I boot up, it connects fine to both and I'm able to use
the connection for a few minutes. Then the message:
ipw2200: Failed to send SYSTEM_CONFIG: Already
A further followup: trying to join WEP unencrypted networks via
command-line (sudo iwconfig eth1 ...) also does not work, so this is not
(just) a problem with knetworkmanager but with ipw2200 and/or the
kernel.
Unless I'm talking out of my [censored].
--
ipw2200 driver no longer works with
Actually now I'm back to having problem regardless of the options in the
ipw2200 driver. (I'm seriously considering just getting another minipci
card; I've never really loved the ipw2200; maybe atheros is better?)
I've been experimenting with various options of:
options ipw2200 hwcrypto=1
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
** Tags added: linux-2.6.27
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You received
I am also having this issue, except it appears to apply to ALL 802.11
networks, not just WPA. Some dumps:
[EMAIL PROTECTED]:~$ dmesg | grep ipw2200
[ 31.284166] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.2.2kmprq
[ 31.284174] ipw2200: Copyright(c) 2003-2006 Intel Corporation
Just tried creating an /etc/modprobe.d/ipw2200 with the line option
ipw2200 associate=0. I no longer get the Failed to send
SYSTEM_CONFIG errors, but neither does it connect (to anything).
The hardware I'm using, incidentally, is an HP/Compaq nc8230, and the
wireless radio status light doesn't
It appears the problem was the driver was trying to scan for networks
constantly, as well as Network Manager doing so, and the probes tripping
each other up in the driver.
Adding:
options ipw2200 hwcrypto=1 associate=0 debug=0x43fff
(relevant part being associate=0)
to /etc/modprobe.d/ipw2200
seems rather like a driver problem, not something we could fix in
wpasupplicant. I'm reassinging to the kernel therefore.
** Changed in: linux (Ubuntu)
Sourcepackagename: wpasupplicant = linux
--
ipw2200 driver no longer works with wpa2 network
https://bugs.launchpad.net/bugs/264104
You
53 matches
Mail list logo
