** Changed in: ipw3945
Status: Confirmed = Won't Fix
** Changed in: ipw3945
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/109887
Title:
ipw3945: Error
No longer valid as Ubuntu now ships with iwl3945 and not ipw3945.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Another update -- earlier I said that the problem went away when
switching to iwl3945 from ipw3945 on my Dell Inspiron 1420. Actually,
with the iwl3945 version included in the latest kernel for Ubuntu 7.10,
I still experienced periodic network lockups (on the order of once a
week or so), just not
Arthur, thanks for testing and the update. Glad to hear things are
working for you. Martin, since you are the original bug reporter, care
to comment if this is resolved for you with the latest Hardy Alpha
release?
Mikael, I assume you've been pulling in the latest updates periodically.
In which
Again, if you can please test with the latest 8.04 Hardy Alpha release
that would be great. The Hardy Heron Alpha 5 series was recently
released which contains an updated version of the kernel. You can
download and try the new Hardy Heron Alpha release from
Hardy Alpha works great. Wireless usually resumes just fine from suspend
(although once in a blue moon I have to modprobe it to get it to work).
I've not had a network lockup since Alpha 3.
On Wed, Feb 27, 2008 at 9:44 AM, Leann Ogasawara [EMAIL PROTECTED]
wrote:
Again, if you can please test
ons 2008-02-27 klockan 14:44 + skrev Leann Ogasawara:
Again, if you can please test with the latest 8.04 Hardy Alpha release
that would be great. The Hardy Heron Alpha 5 series was recently
released which contains an updated version of the kernel.
As I'm running Hardy from the repos, can
hi everyone:
i got some problems with my ipw3945. the wifi is working ok, but the
problem that i have is that the connection led (or the indicator that
the wifi is enable) it's not working! so i don't really know whats
happening. i don't know when the wifi is enable. i just depend on the
Using Gutsy on a D830, updated from all repositories (proposed,
universe, multi-universe, backports)
$ uname -a
Linux host 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux
$ lspci | grep -i wireless
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
HI Jens,
Your dmesg cache seems to have filled up and written over the initial
boot logs. Care to recapture it for Hardy? Also note that Hardy Alpha4
will be released in a few days so you may want to wait to test with the
newer release which will have an updated kernel. If the issue still
Care to test with a Hardy Alpha LiveCD?
http://cdimage.ubuntu.com/releases/hardy . Also, please use the iwlwifi
(iwl3945) driver rather than ipw3945. iwlwifi is included in Ubuntu
Hardy kernel. Thanks.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
Tried blacklisting ipw3945 and adding iwl3954 but now the network
doesn't work at all. Downloading Hardy for a Live test.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Brian Murray (brian-murray) = (unassigned)
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Changed in: ipw3945
Status: Unknown = Confirmed
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Well, it looks like this is an issue that others are having. I'll post
whatever relevant information I think you all might need.
First off, the description of what happened (this is the second time
this happened). I use a Gateway c-140xl with Gutsy. I had uptime for
something around 18-20hrs.
** Bug watch added: Bughost.org tracker #1260
http://bughost.org/bugzilla/show_bug.cgi?id=1260
** Also affects: ipw3945 via
http://bughost.org/bugzilla/show_bug.cgi?id=1260
Importance: Unknown
Status: Unknown
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
Just reporting the same bug in other trackers as well as the intel one.
http://bughost.org/bugzilla/show_bug.cgi?id=1260
http://bugs.archlinux.org/task/7709
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because
I get the same error with iwl3945.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Hardy Heron Alpha2 was recently released. It contains an updated
version of the kernel. You can download and try the new Hardy Heron
Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ .
You should be able to then test the new kernel via the LiveCD. If you
can, please verify
I also just wanted to add a note that the ipw3945 project has been
deprecated according to the following site:
http://ipw3945.sourceforge.net/
Development efforts have switched to the iwlwifi project:
http://intellinuxwireless.org/
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
I had this same problem on a 3945 on a Dell Inspiron 1420 notebook.
The fix suggested above worked, I added a line saying:
blacklist ipw3945
to the /etc/modprobe.d/blacklist file
and I added another line saying:
iwl3945
to /etc/modules
I would consistantly reproduce the crash within 10
I also have a Dell M6300. This is a show-stopper! It needs a higher
priority. (It's time to switch back to redhat!)
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which
Bug confirmed on a HP dv6500
gutsy, Intel wireless card
The syslog is exactly the same with the bug description above.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs,
Bug confirmed on a Dell M6300
I had this bug on a networks with static WEP, WPA-PSK and EAP-TTLS. It
seems to happen most often with heavy traffic, using a terminal server.
Also sometimes it crashes within 5 minutes and sometimes it keeps on
working for hours without any problem.
--
ipw3945:
and confirmed on another dell d830 with any ap. seems to happen more
often when heavy udp traffic is involved (streaming video for instance)
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member
bug confirmed on another dell D830.
Connected to a 802.11g ap with WPA protection, crashes occours every few (1-2)
hours and the only solution is to restart.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification
i replaced ipw3945 with iwl3945 and al is working 100% stable now.
blacklist ipw3945
/etc/modules iwl3945
use te following fix http://wiki.debian.org/iwl4965
more info on my blog
http://siegie.sin.khk.be/wordpress/2007/12/03/eindelijk-stabiel-draadloos-internet/
--
ipw3945: Error sending
I can confirm this bug on a Dell Vostro 1700 running Feisty.
It is definitely related with high network traffic, since it occurs
guaranteed within 40 minutes of remote X usage, whilst at other moments
it occurs only sporadicly.
This is the worst bug I have ever encountered in the 9 years I am
Same problem here. Im gonna try razboinik's suggestion next time the driver
crash (T - 3 h)
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
HAving the same problem on Sony vaio vgn-FE21h
Dmesg output:
ipw3945: Radio Frequency Kill Switch is On:
[117933.68] Kill switch must be turned off for wireless networking to work.
[117933.736000] usb 3-1: USB disconnect, address 90
[117934.408000] ipw3945: Detected geography ABG (13
This is by far the most annoying bug I have experienced in my 6 years as
a linux user, it's a bug the at random makes us need a reboot. I suggest
a higher priority.
Paul
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug
This happens with every AP I tried so far.
I will try to use the hardware switch and unloading the NIC next time,
hopefully it won't be for a couple of hours, since it just happend :-(
Looking forward to the next kernel update...
Paul
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
Same here... using wired network only now.
Makes my Ubuntu useless...
Developers say that this bug won't be fixed in Gutsy.
Because it is not release-critical.
I think it is
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug
Agreed. I have disabled wireless in BIOS and use wired network.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I can confirm that when using the hardware off switch for the card, then
stopping the network and unloading the module works.
The crash interval seems to be accelerated when using vpn, perhaps because the
nic is under heavier load? Crashed 3 times since my last post.
SunnyBug,
It is marked
razboinik writes that the following works:
/etc/init.d/networking stop ; modprobe -r ipw3945 ieee80211 ; sleep
2 ; modprobe ipw3945 ieee80211
I can confirm that this works -- but first I have to switch off the
wireless card using the hardware switch.
I repeat -- if you can't get the module
One more thing: These hangs seem to only happen at the office, where
our wireless infrastructure is built on Apple AirPorts. I can't recall
ever seeing this hang at home (non-Apple wireless).
How does this correlate with others' experiences?
--
ipw3945: Error sending LEDS_CMD. Random driver
I connect to a D-link DIR 655.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
For me this happens on all 3 APs I use
Apple AirPort Express
ZyXEL ADSL modem with builtin AP
D-Link
All 3 use WPA-PSK, so I belive it does not depend on manufacter,
but (MAYBE) on encryption used,
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
The router I connect to has no encryption at all, only MAC-address
filtering. (I tried to give the owner a lesson in wireless security, but
he wouldn't listen.)
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification
I also have this problem on a Dell D830
$ uname -r
2.6.22-14-generic
$ lspci | grep -i wireless
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
$
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You
Also discussed here :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/71510
This is driving me crazy. I need a reboot to reload the module.
This seems to be a ubuntu only kernel error... I wish I was a kernel dev.
Any suggestions?
--
ipw3945: Error sending LEDS_CMD. Random
Upgraded to Gutsy over the weekend and being driven nuts with this bug
I'm on a Dell Inspiron 9400
lspci | grep -i wireless
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
uname -r
2.6.22-14-generic
Fortunately I can restart the driver without
Running Gutsy with this driver on a Dell Inspiron 6400, never had this
bug occurring in a month or so, with heavy usage, and costant use of
suspend-to-ram, ecc. (I do have other issues with the driver, relating
to suspend-to-ram, but this is a whole another story). I do not know
what in my hw/sw
Can confirm the bug on a Dell D830. It is almost driving me back to
feisty.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I tried adding irqpoll as well. All it did was slow the machine to a
crawl and the error keeps occurring.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Try adding irqpoll to your kernel boot options. This seems to have
alleviated the problem for me. There should be a proper fix for this
though.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a
Tried that before already, nothing changed, still hardware lockups in 8-12h
of active use.
On 10/24/07, Ryan Novosielski [EMAIL PROTECTED] wrote:
Try adding irqpoll to your kernel boot options. This seems to have
alleviated the problem for me. There should be a proper fix for this
though.
I can confirm this error on a Lenovo Thinkpad X61s. The error occurs at
random intervals between 30 minutes and 12 hours after boot. It is
necessary to reboot the system to fix the lockup.
~$ lspci | grep -i wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Same for me (4-6 hours of running BitTorrent)
But in 1-2 minutes after this messages laptop completely locks up.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I haven't had this problem since, but what is the downside? I see a lot
of stuff related to IRQ's in 'top' (pretty sure that wasn't there
before).
Also, I see a new assignment and a confirmation. Curious what the
current status is.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
Ryan - It would be helpful if we could have your exact crash report too.
Additionally, are you using 802.11b or 802.11g to connect to your access
point? Thanks again.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug
I have two different crashes. One of these was recoverable, and one of
these was not (reboot required). I will note which is which where I can.
Note that I'm not 100% sure of this data and will try to capture it at
the time it happens next time, but I'm working from memory on what
happened in the
Forgot to address the first question -- my access point at home is a
Linux 2.4 PC with a Orinoco/WaveLAN 128-bit WEP card (802.11b).
Here is the common crash case that I was referring to earlier. The crash
starts, apparently, with the failure with command #07. This often
displays also on shutdown
Does anyone reading this know if any of my boot messages (unstable TSC,
etc.) or suggestions for boot parameters might affect this? The one
crash asked me to add irqpoll to my boot options. I've tried adding
stuff before that really had no effect, but I'd be happy to look also in
this case if it's
I think it would be worth trying as all the error messages deal with
interrupts or IRQ in the first crash. Thanks again.
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New =
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
My system's relevant information (this set of files does not contain the
wireless error, but it is identical to the other poster's).
I personally use 2.6.22-13-rt, but I suspect the -rt has nothing to do
with it. I had no problems with 2.6.17. 2.6.20 was bad for a myriad of
reasons, so I never
...next...
** Attachment added: version.log
http://launchpadlibrarian.net/9850046/version.log
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: dmesg.log
http://launchpadlibrarian.net/9850047/dmesg.log
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
...and the last file.
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/9850058/lspci-vvnn.log
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug does not meet the criteria for a stable release update and is
being marked as Won't Fix for this particular version of the kernel. You can
learn more about the stable release update process at
** Attachment added: dmesg output
http://librarian.launchpad.net/7404155/dmesg.log
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: lspci -nvv output
http://librarian.launchpad.net/7404156/lspci.log
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
65 matches
Mail list logo
