Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29101 - [ipw2000-fw,linux] ipw2100 problem after upgrade to 3.3 kernel

Attached to Project: Arch Linux
Opened by Miroslaw Czachor (forest76) - Sunday, 25 March 2012, 07:15 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 26 March 2012, 06:48 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I have notebook vaio v505cp with Intel Wi-fi card so I use ipw2100 kernel driver. With bad (weak) signal I have got plenty "ipw2100 - Fatal interrupt. Scheduling firmware restart." messages but everything had worked fine.
Unlucky after 3.3 kernel upgrade module ipw2100 load fine, I manage to connect to Wi-Fi but after short time (few minutes) I get only one message: "ipw2100 - Fatal interrupt. Scheduling firmware restart.", connection lost and doesn't restart like on 3.2 kernels.
Manual restarting drive me crazy so please for help.

Greetings,
Miroslaw

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 26 March 2012, 06:48 GMT
Reason for closing:  Not a bug
Comment by Jelle van der Waa (jelly) - Sunday, 25 March 2012, 09:39 GMT
Is ipw2100 a kernel driver or do you use the ipw2100 package?
Comment by Miroslaw Czachor (forest76) - Sunday, 25 March 2012, 18:50 GMT
I am doing some deeper investigation and discover that the problem is not kernel but netcfg-2.7.1-1 package. After downgrade netcfg to 2.6.8-1 network card restarting fine, so this task may be close. Sorry for confusion.

Greetings,
Miroslaw
Comment by Jelle van der Waa (jelly) - Sunday, 25 March 2012, 18:53 GMT
Ok but it sounds like your config might be borked. So i advice you to update to the new netcfg release and check your config ;)

Loading...