** Changed in: linux-restricted-modules (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/276445
Title:
Madwifi (atheros) driver malfunction induces a
See bug report #426130
As a workaround deinstalling gnome network manager and instead using
wicd seems to work fine.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs,
Please also see Bug #616947
I have a very similar problem as described in in this report as well as
in Bug #616947 which may be both related to each other.
When systems freezes, caps lock panel flashes, which refers to a kernel
panic. Screen gets blank and input of mouse and keyboard is not
Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug is still marked as confirmed in later versions of Ubuntu.
** Changed in: linux-restricted-modules (Ubuntu Intrepid)
Status: Confirmed = Invalid
--
Madwifi (atheros) driver malfunction induces a system
Well, it worked for two full days, but it's back to doing it again.
Here's another madwifi bug ticket that could be the cause of the problem:
http://madwifi-project.org/ticket/1903
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You
This is supposed to get fixed by the next madwifi release
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I built the latest madwifi source from their svn repository and it
solved the problem for me.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I do believe I'm getting something similar to this.
I don't have anything in logs that would suggest a fail, but after a
period of around 4-6 hours network inactivity, my system will freeze
once I start using the network device again (ie: checking for updates).
General Information:
cat
i never got back to it because i set my router to 802.11g in order to get a
freeze and try lamos' solution..
Strange thing though, i never got a freeze.. so, i don't know if something i
did accidentally fixed the problem, or if a fix was issued in an update..
i set it back to b and g to see if
I've been getting a very similar problem, but I've noticed something VERY
different. All of the temporary fixes in this thread do not work for me and
even if I disable my Wireless, I still get random freezes. BUT if I'm not
connected to the internet the:
wifi0: rx FIFO overrun; resetting won't
I have also good news: My system is up and running now for 8 days with a total
load of 4,0GB(Down) and 2,1GB(Up).
Solution by now was changing the driver to ath5k (for Atheros 9xxx use ath9k).
Be aware that it gives a new problem (see #291760), but it doesn't affect my
system much and
it's definitely related to 802.11g because i set my wireless router to only b
and haven't got a freeze since..
so there is a solution for those that have admin privileges on the router
they're connecting (there should be an option for that)..
i have yet to try lamos' solution to confirm..
care
alejaaandro, Sorry forgot to post the link. Found it in this forum post
at the bottom.
http://madwifi-project.org/ticket/1562
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of
After running this command:
iwpriv ath0 bgscan 0
My computer hasn't frozen once for in 3 days now.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm also having this problem after installing Intrepid. I downgraded to
Hardy for a week and had no problems. Now I'm back on Intrepid and I'm
experiencing freezing 2 to 3 times daily when running torrents. I have a
Netgear pci wireless adapter using the 5xxx series Atheros 802.11
driver. Also
cheers everybody.. i have good news...
after setting up everything with the new modem, i haven't had a kernel
panic the whole day (some serious traffic has been going on like p2p
more than 500 kBs, media streaming etc).. i sure hope it's not just
luck..
i did 2 things..
1) changed my wireless
sorry guys, bad news... it was probably wrong getting too excited and
posting without testing it longer..
i changed my router back to b and g to check if that was what fixed it and 10
min later i got a panic..
so that leaves me with either luck or the 801.11g being the problem.. i ll
report
unfortunatelly i have the same problem, and, i too, only got it after
upgrading to intrepid (even though i think it was already a known
problem)... same case, experiencing kernel panics mostly when doing
intense network stuff...
i installed linux-backports-modules thinking it might help.. nothing
I just experienced a freeze on Intrepid, this is the first time it's
happened on Intrepid. It also happened to me once under Hardy. It's
definitely a random thing. I think it has something to do with signal
strength and those wifi0: rx FIFO overrun; resetting messages. I only
get those when my
I'm afraid I have to confirm. My wifi runs a bit longer it seems, but at
the end it freezes the system again. Guess we don't have any other
chance as of waiting for some news from madwifi group. Except someone
here is used in driver programming.
--
Madwifi (atheros) driver malfunction induces a
So keep reporting motherboard/atheros chipsets :)
We might find a coincidence.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I dont't think that it is helpful because we both have already a
completely different kind of chipset. Also the bug was already found,
but this guy doesn't find an easy way of backporting. Maybe we better
should try an older version of madwifi and if that's working fine asking
the packager of
** Changed in: linux-restricted-modules (Ubuntu Intrepid)
Status: New = Confirmed
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Howdy. How can I do this? I am using Ubuntu 8.04 w/NetworkManager as
the wifi manager. Should I change this on the wireless access point or
on my internal wireless card? thanks.
On Thu, Dec 4, 2008 at 9:44 AM, Thomas Ohms [EMAIL PROTECTED] wrote:
As already said it isn't necessary to know the
Change it to the Access Point and your client will connect automatically
to the AP with its channel.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, thanks.
Well, as it turns out, I already have my access point -- a linksys
wrt54gl router, actually -- set to use Channel 1. And I always have,
even when I was having problems with this bug (which I am not having
anymore only because I disabled wireless :( )
Seeya...
On Fri, Dec 5, 2008
Thomas, In the bug you mentioned it says somewhere: Station mode (sta) on the
same Maschine runs very nice without any problems.
All the three of my links runs in station mode
The chipset that induces the freeze for me is:
Chipset: Intel® G31 + ICH7
Atheros: AR5212/AR5213
--
Madwifi
Ok, but give the channel workaround a try. My wifi is still working as I
can reach my PC.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
How can I determine what chipset?
On Thu, Dec 4, 2008 at 1:23 AM, Thomas Ohms [EMAIL PROTECTED] wrote:
Well, I don't think it's the be motherboard, but it needs to be something
specific. Else we would have even more people complaining about this. Let's
see: could everybody who has reported
As already said it isn't necessary to know the chipset. If you have this
bug, try changing your wifi channel to 1 and let us know the result.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are
I can`t change to channel 1 cause I am playing in the 5GHz band
As for the chipset I just read which one I have from the motherboard
specifications (use google for it).
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this
That was a good idea, but seems to be only a coincidence. As you can see
in attached file I only have wifi on the corresponding interrupt.
** Attachment added: interrupts.log
http://launchpadlibrarian.net/20188119/interrupts.log
--
Madwifi (atheros) driver malfunction induces a system freeze
So it is something with specific motherboard chipsets and the driver :(
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Well, I don't think it's the be motherboard, but it needs to be something
specific. Else we would have even more people complaining about this. Let's
see: could everybody who has reported this bug please tell us what chipset they
have!?
Here's my data:
Chipset: SiS 1039
Atheros: AR242x
--
Wait folks. I had a look on madwifis ticket system and found this:
http://madwifi-project.org/ticket/1903
It seems to be the same problem and they're already on it. I asked the assigned
guy if there is any update, but for now it seems using channel 1 should be a
workaround. I'll give it a try
After a long research I found that most probably there is a problem with
madwifi drivers and motherboard interrupts
check your /proc/interrupts to see if there is any conflict (wifi interface is
using the same interrupt with anything else).
I changed the motherboard (even if it was a brand
How would I go about doing that?
What am I looking for?
What can I do about it? ( I have a laptop -- Lenovo R61 -- and
replacing the mobo isn't really an option)
Here is my output from `cat /proc/interrupts`. Notice there is a line
with wifi0 in it that also lists usb4, ohci1394 and HDA Intel. Is
Just for a quick test
As I see your wifi0 is sharing the interrupt with usb, firewire and sound card..
21: 935070 930591 IO-APIC-fasteoi uhci_hcd:usb4, ohci1394, wifi0, HDA Intel
So try to disable from your BIOS the usb, firewire and sound card if possible.
Then boot again and check the
Confirmed because many people are having this problem and it is
reproducable.
** Changed in: linux-restricted-modules (Ubuntu)
Status: New = Confirmed
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification
Hello,
I have a similar problem, but it's even more annoying, because the
computer freeze when i try to connect in WPA. My wifi chipset is a
Atheros ar5008, and I'm trying to make it function on a clean and
updated install of Intrepid. If i should give more informations, please
tell me.
--
I just want to add that I have no others networs to try to connect
without protection to see if the freeze appears too.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
I fully aggree with Jeffrey. I have this problem only after torrents and
aMule have been running. Sometimes it freezes already after system
restart and immediatey starting of aMule.
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You
Hello,
I have exactly the same problem!
I have a wireless router with ubuntu 8.04.1 server amd64 installed in it.
linux-restricted-modules-server is installed and the three atheros cards I have
on the computer are working, but my logs are filled of the following messages.
As I realized, if
I am having a very similar problem. Random freezing, but it does seem to
be caused by high amounts of network traffic. For example, I can
consistently freeze my machine when I do an rsync backup of a large
directory (as in 50GB or so) over my LAN to a server machine.
I am *pretty* sure that I did
I also can confirm this bug. Because WLAN is not usable so long this
should be maintained more critical. Is there nothing we can do?
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member
I also can confirm this bug. Because WLAN is not usable so long this
should be maintained more critical. Is there nothing we can do?
--
Madwifi (atheros) driver malfunction induces a system freeze
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member
I've forgot: have a clean Intrepid installed!
** Summary changed:
- Madwifi (atheros) driver malfunction induces a system freeze (Hardy)
+ Madwifi (atheros) driver malfunction induces a system freeze
** Tags added: atheros freeze madwifi system
--
Madwifi (atheros) driver malfunction induces
i'll add this comment:
On a toshiba satellite m71 (iirc), internal atheros card.
Not only has this problem started in Linux, but in addition to THAT, the
bug carried on to Windows. The Windows OS started freezing/crashing
after I encountered this bug on Ubuntu Hardy Heron.
System with
This sounds like something I read on slashdot a few weeks ago - that the
driver was overwriting the flash RAM on the chip. I was in a rush, so did
not note the URL.
As an update, my wireless card stopped being detected a few weeks ago. I
simply found a way to used the wired network. Ever since I
I am seeing a similar issue where my machine will lock up randomly. It
is a T61 with an nvidia video card and atheros wireless.
I have installed the linux-backports-modules package to see if it helps
(since it worked for the intel cards,
https://bugs.launchpad.net/ubuntu/+source/linux-backports-
** Attachment added: lspci.log
http://launchpadlibrarian.net/18826020/lspci.log
--
Madwifi (atheros) driver malfunction induces a system freeze (Hardy)
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
i am running ibex with all updates btw.
** Attachment added: uname.log
http://launchpadlibrarian.net/18826023/uname.log
--
Madwifi (atheros) driver malfunction induces a system freeze (Hardy)
https://bugs.launchpad.net/bugs/276445
You received this bug notification because you are a member
I just discovered I do not have linux-restricted-modules installed, but
my kernel's version of that package is installed. Just a note to avoid
any confusion.
I have the following :
$ apt-cache policy linux-restricted-modules-2.6.24-20-generic
linux-restricted-modules-2.6.24-20-generic:
53 matches
Mail list logo
