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#9398 - iwl3945 vs kernel-2.6.24.2 = Randomly Disconnects

Attached to Project: Arch Linux
Opened by Alper Kanat (T-u-N-i-X) - Tuesday, 29 January 2008, 23:20 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 08 April 2008, 16:44 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hey There,

I'm using testing/core/extra/community repositories and I'm having this problem for almost 1 week since one of the latest upgrades.. After the iwlwifi driver is embedded to the kernel, I started having this problem (as far as I can guess)

The amazing part is that I don't have this problem at the office (using WEP authentication) but I do have it at home where I use WPA authentication with a US Robotics 9106 wifi adsl modem..

I'm attaching dmesg and daemon.log outputs..

Thanks for your great work..
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 08 April 2008, 16:44 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Upstream issue
Comment by Alper Kanat (T-u-N-i-X) - Tuesday, 29 January 2008, 23:23 GMT
Attaching the files..
   daemon.log (589.6 KiB)
   dmesg.txt (30.3 KiB)
Comment by Tobias Powalowski (tpowa) - Wednesday, 30 January 2008, 07:54 GMT
you can still use the ipw3945 module instead if iwlwifi is broken for you.
you need to blacklist iwlwifi then.
Comment by Alper Kanat (T-u-N-i-X) - Wednesday, 30 January 2008, 08:12 GMT
I tried that but that also didn't work for me.. Network Manager doesn't work with ipw3945 for me.. I tried netcfg, nothing solved.. There were some errors saying that it couldn't connect to wpa_suplicant despite it's installed.. iwlwifi never showed me that error..

A new kernel with the newest iwlwifi would also do fine (maybe)
Comment by Tobias Powalowski (tpowa) - Wednesday, 30 January 2008, 08:14 GMT
that will happen with .25 kernel not before
Comment by Roman Kyrylych (Romashka) - Wednesday, 30 January 2008, 12:53 GMT
This was reported to Intel by brain0, they said they cannot reproduce this bug. >:(
Comment by Alper Kanat (T-u-N-i-X) - Wednesday, 30 January 2008, 12:59 GMT
:( I have HP dv2580et laptop computer with:

07:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

on it.. The details:

07:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
Subsystem: Hewlett-Packard Company Unknown device 135c
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at f4100000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <64us
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Device Serial Number 94-e4-c6-ff-ff-77-1b-00
Comment by Alper Kanat (T-u-N-i-X) - Wednesday, 30 January 2008, 13:02 GMT
I just downgraded to kernel-2.6.23 in core repository and installed iwlwifi package in extra.. I should try these configuration at home since I have the problem there.. When it disconnects randomly, I can't reconnect for some time.. Sometimes it doesn't even find my wireless router whereas my router is inches away that I can touch it.. Sometimes it list my router but it can't connect to it due to timeouts... :(
Comment by Thomas Bächler (brain0) - Wednesday, 30 January 2008, 16:46 GMT
The problem is that the iwlwifi version in extra is newer than the one in kernel26. However, the latest version from their website doesn't build against 2.6.24. Complain to Intel about it.
Comment by Alper Kanat (T-u-N-i-X) - Wednesday, 30 January 2008, 17:01 GMT
Kernel 2.6.24 includes iwlwifi package inside.. Maybe that is the reason why it doesn't get built ? Of course, I assume that the iwlwifi package just provides the modules iwl3945 and iwl4965.. If so, which version of the iwlwifi package the kernel includes is important..
Comment by Alois Nespor (anespor) - Thursday, 03 April 2008, 06:50 GMT
iwl3945 in 2.6.24.x kernel is very, very old (1.1.17) and not stable for WPA etc.. Stable WPA support is from version 1.2.+ . Please be patient for new kernel 2.6.25, will latest driver version (at moment 1.2.26).
Comment by Alois Nespor (anespor) - Thursday, 03 April 2008, 06:53 GMT
This is transition, and is not without problems.
Comment by Alois Nespor (anespor) - Thursday, 03 April 2008, 07:01 GMT
The kernel driver of iwl3945 is not good :-( I have also big, big problems, i use driver from http://linuxwireless.org/en/users/Download - is latest.
Comment by Thomas Bächler (brain0) - Thursday, 03 April 2008, 07:41 GMT
2.6.25 should be there shortly, so I think we should wait for that, it includes a much newer version of the iwl drivers.

That said, I have no problems using iwl3945 now, but I think I only tried WPA2, no WPA.
Comment by Alois Nespor (anespor) - Thursday, 03 April 2008, 10:50 GMT
if i say WPA think of course WPA/WPA2... we can wait, but this is not problem Archlinux, this is driver problem. :-)

Loading...