Hi all,
I can confirm for the Gutsy LiveCD the same behavior for my Samsung X10,
which is having an Intel (R) PRO/Wireless 2100 LAN 3B MiniPCI Adapter. I
get the same Fatal interrupt message in my /var/log/messages.
I can also confirm, that the workaround given by Fabio M. works for me.
Close to
Has anyone tested this in hardy?
** Also affects: linux via
http://bughost.org/bugzilla/show_bug.cgi?id=1487
Importance: Unknown
Status: Unknown
** Changed in: linux
Importance: Unknown = Undecided
Bugwatch: Bughost.org tracker #1487 = None
Status: Unknown = New
**
still present in Hardy with ipw2200. could is possibly be an issue with
intel's non-gpl'ed firmware (I think the driver is open, but the
firmware is closed, right?)
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Thomas: Thanks for replying so quickly. Could you (on hardy) give us the
following files (as per https://wiki.ubuntu.com/KernelTeamBugPolicies):
uname -a uname-a.log
cat /proc/version_signature version.log
dmesg dmesg.log
sudo lspci -vvnn lspci-vvnn.log
--
ipw2100 error Fatal interrupt.
Which firmware are you using?
I've found loads of similar looking bugs:
http://bughost.org/bugzilla/show_bug.cgi?id=245
http://www.bughost.org/bugzilla/show_bug.cgi?id=329
https://bugzilla.redhat.com/show_bug.cgi?id=149968
Bug #18648
http://lists.opensuse.org/opensuse/2006-11/msg03571.html
--
argh. Bug #18648 is the old bugzilla name for this ancient bug.
https://lists.ubuntu.com/archives/kernel-bugs/2005-October/006000.html
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because you are a member
This bug is acknowledged upstream but doesn't seem to have been worked
on since Jan 2007.
** Changed in: intellinuxwireless
Bugwatch: Bughost.org tracker #1487 = Bughost.org tracker #329
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: New = Won't Fix
** Changed in:
I'm changing the upstream bug report to 329 as that is the one
referenced in the ISSUES file included with the latest ipw2100-1.2.2
tarball release from 2007-01-31. Incidentally the ISSUES file contains:
Firmware restart is detected randomly
--
After running one
@developers:
I have made other tests on several wifi-networks, reporting all the same
result. If the network is WPA-PSK I cannot connect to the AP if the
laptop is too close to it. Bringing the laptop far away from the AP (so
lowering the signal strenght) I can get connected. From that point on,
Hello,
I recently started seeing these errors in /var/log/messages which
correlated with a brief outage in my wireless signal. This error only
seemed to happen while downloading larger files for more than five
seconds:
ipw2100: Fatal interrupt. Scheduling firmware restart.
I'm running Gutsy on
Started seeing this bug on IBM T40 straight after installation of Gutsy
7.10 (kernel 2.6.22-14-generic using ipw2100 module). Confirmed card\AP
is OK using Windows. What's interesting is the bug seems to occur
straight from CD, I'm able to detect local SSID's but unable to get dhcp
response, on
I have an interesting behaviour to note here.
I have found that I can connect to my office wireless WPA-PSK Access Point ONLY
IF I put the laptop (IBM X31) close to a particular corner near the window
during boot and net access. This corner is the FAREST in the office from the
AP. Once
This seems to be reported:
http://bughost.org/bugzilla/show_bug.cgi?id=1487
I have the same problem on Gutsy with a Sony Vaio using WPA. Have not
tried WEP or plain yet for comparison. Card seems to fail when
large(ish) amounts of data are transferred and only a reboot will cure
it.
--
I have a similar problem with an ASUS centrino laptop.
Wireless networks are scanned OK and appear in NetworkManager, but
trying to connect to my AP (using WPA) doesn't work (no green lights
whatsoever, and the authentication dialog keeps reapearing). It's a
fresh install, made a few hours ago,
After yeasterday's kernel upgrade, it is even worse. I cannot use
anymore my laptop as I don't have any internet connection. Doesn't
matter the protocol, it can be WEP open or WPA/PSK I have the same
error.
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
Also seeing this problem on Gutsy. I agree that it seems to be provoked
by higher transfer rates. Removing and reloading the ipw2100 module
does not help.
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification
I got same error as Fabio Marzocca, on IBM X31
Inter PRO/Wireless 2100 centrino cpu
kernel: ubuntu 7.10 Gutsy 2.6.22-14-generic
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because you are a member of
confirmed here as well.
after several tries, sometimes it works.
appears to happen more often, when large amounts of data are transferred.
ubuntu 2.6.22-14-generic
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug
I did not mean Baltix but Ubuntu. Sorry.
Filed for Ubuntu as well.
** Also affects: linux-source-2.6.22 (Baltix)
Importance: Undecided
Status: New
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-source-2.6.22 (Baltix)
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Confirmed
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed = New
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because
Any temporary workaround available?
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I confirm this message on Gutsy too: ipw2100: Fatal interrupt.
Scheduling firmware restart.
Cannot connect to WPA-PSK wireless network. The card works fine in
windows. This is a serious bug, as my ThinkPad X31 does not have a
network capabilty with Ubuntu!
--
ipw2100 error Fatal interrupt.
Forgot to mention: I am using kernel 2.6.22
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Same here on gutsy with 2.6.22-14-generic. Blacklisting ipv6 helps
sometimes, but couldn't figure out why. Perhapps the ipw2200 is using
another accesspoint.
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification
I have the same problem on Feisty with 2.6.16-20-generic kernel. In my
case, I can associate with an access point, I can listen to traffic with
tcpdump(8), but my sent packets get dropped (dropped counter is increasing
in ifconfig) and therefore can't get a DHCP reply.
--
ipw2100 error Fatal
I am now getting this problem in gutsy.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Invalid = New
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
You received this bug notification because you are a member of Ubuntu
Bugs, which
completely out of the blue, thought it might be my hardware having
problems, but it works fine in windows.
** Attachment added: dmesg output
http://launchpadlibrarian.net/9021489/output.txt
--
ipw2100 error Fatal interrupt. Scheduling firmware restart.
https://bugs.launchpad.net/bugs/24776
28 matches
Mail list logo
