FS#7686 - iwl3945 doesn't work with network profiles for some reason

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Friday, 27 July 2007, 02:04 GMT
Last edited by James Rayner (iphitus) - Friday, 23 May 2008, 12:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
init scripts network profiles fails to function with my network card using the iwl3945 driver.

Additional info:
* package version(s)
* config and/or log files etc.

initscripts 0.8-12
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

Steps to reproduce:

Configure wifi settings in profile, start network.


Additional Information:

I've written this init script which will work around the problem, but it's quite the kludgy hack. the actual steps it performs are only slightly different from network profiles, but it works for some reason
   mywifi (0.8 KiB)
This task depends upon

Closed by  James Rayner (iphitus)
Friday, 23 May 2008, 12:53 GMT
Reason for closing:  None
Comment by Thomas Bächler (brain0) - Friday, 27 July 2007, 15:37 GMT
If you want something stable, use ipw3945 instead.

I can't tell what your script might do that netcfg wouldn't, except call iwconfig twice. I never tried WEP with the driver, as it is a security-nightmare and shouldn't be used by anyone for anything.
Comment by Christ Schlacta (aarcane) - Friday, 27 July 2007, 17:21 GMT
Unfortunately, all the documentation I've found says I need iwl for my card because it's so new. if you think ipw will work anyway, I'll try it.

I think the reason my script works is all the times I call iwconfig, all the time I sleep, and the fact that I bring the device up many times instead of just one. it took me 4 hours to tweak the order of the steps I perform to get the script to actually reliably bring the wlan up, and I can't even switch between wlans :-S
Comment by Christ Schlacta (aarcane) - Friday, 27 July 2007, 20:39 GMT
Unfortunately, all the documentation I've found says I need iwl for my card because it's so new. if you think ipw will work anyway, I'll try it.

I think the reason my script works is all the times I call iwconfig, all the time I sleep, and the fact that I bring the device up many times instead of just one. it took me 4 hours to tweak the order of the steps I perform to get the script to actually reliably bring the wlan up, and I can't even switch between wlans :-S
Comment by Christ Schlacta (aarcane) - Friday, 27 July 2007, 21:02 GMT
sorry for the double post.

After some time with you on irc, mr.Thomas, It works now using ipw instead of iwl. this seems like less of a hack, as it works well.

The only thing I can say more is that I think this bug should not be closed until it works as intended with iwl, but that means this should be forwarded to upstream.
Comment by Christ Schlacta (aarcane) - Saturday, 28 July 2007, 02:56 GMT
sorry for the double post.

After some time with you on irc, mr.Thomas, It works now using ipw instead of iwl. this seems like less of a hack, as it works well.

The only thing I can say more is that I think this bug should not be closed until it works as intended with iwl, but that means this should be forwarded to upstream.
Comment by Mike (shen) - Tuesday, 06 November 2007, 14:59 GMT
I had the very same issue. Now that the new netcfg2 has hit testing I think I will test this out with the iwl3945 driver and see what the outcome is.
Comment by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 17:25 GMT
status with the kernel 2.6.24.1 and iwl3945 from testing?
Comment by James Rayner (iphitus) - Friday, 23 May 2008, 12:52 GMT
closing, this is an old bug, with old drivers, and the old network profiles.

Loading...