Bug 259005

Summary: wrong ipw3945.ucode and ipw3940d versions on openSuse 10.2
Product: [openSUSE] openSUSE 10.2 Reporter: Antenore Gatta <antenore>
Component: NetworkAssignee: Joachim Gleissner <joachim.gleissner>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: aj, antenore, behlert
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Package with updated 3945 ucode
Package with updated ipw3945d (i586)
Package with updated ipw3945d (x86_64)

Description Antenore Gatta 2007-03-29 18:43:56 UTC 
It seems that the wireless card "Intel PRO/Wireless 3945ABG" on Lenovo T60p notebook, doesn't work with the standard installation of openSuse 10.2 (with right packets from non-oss repositories).

I followed advice from http://en.opensuse.org/HCL/Network_Adapters_%28Wireless%29 but without good results.

So, looking for errors in the log files I found this:

ipw3945: Can't stop Rx DMA.
ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
ipw3945: 3945ABG card ucode DOWNLOAD FAILED
ipw3945: Unable to load firmware: -110
ipw3945: 3945ABG card ucode DOWNLOAD FAILED
ipw3945: Unable to load firmware: -110
ipw3945: 3945ABG card ucode DOWNLOAD FAILED
ipw3945: Unable to load firmware: -110
ipw3945: 3945ABG card ucode DOWNLOAD FAILED
ipw3945: Unable to load firmware: -110
ipw3945: 3945ABG card ucode DOWNLOAD FAILED
ipw3945: Unable to load firmware: -110
ipw3945: Unable to initialize device after 5 attempts.
ipw3945: Microcode SW error detected.  Restarting.

So I've updated both ipw3945d and ipw3945.ucode (from http://bughost.org/ipw3945/ ) resolving the problem.

The old installed versions were:

ipw-firmware: 7.31 (ipw3945-ucode ???)
ipw3945d: 1.7.18-29

I've fixed the problem with:

ipw3945-ucode: 1.14.2
ipw3945d: 1.7.22

Finally... Maybe I made some errors during the installations but in any case firmware and ipw3945d daemon should be updated in the repository.

As I don't have enough expertize, is there anybody that can do it for me?

Thanks a lot.
Best Regards

Antenore.
Comment 1 Antenore Gatta 2007-03-30 21:48:19 UTC 
Just to confirm...

I made some tests.

1. Restore the default configuration with non-oss repositories, and I confirm, it doesn't work.

2. Uninstall non-oss ipw3945d, install the latest one from Intel (see above) and update the ipw3945-ucode as well (1.14.2)... To fix the problem.

This resolve also bugs #230920 , #225604 and maybe all the others.

#255666
#249872 	
#197098 	
#232420
Comment 2 Cristian Rodríguez 2007-03-31 09:44:35 UTC 
if this bug happends to you, does not meant it is Blocker .

assigned to the person I "suspect" shoudl know about this problem ( as nobody still allow us to see the assignees list **sigh** )
Comment 3 Joachim Gleissner 2007-04-19 06:50:22 UTC 
The subject is misleading, for most people the packaged versions seem to work. Maybe the newer firmware image is needed for recent ipw3945 devices, that's possible. However, I'd have no problem with updating these packages, it won't harm probably. Andreas, what do you think?
Comment 4 Andreas Jaeger 2007-04-19 07:08:12 UTC 
I agree, the subject is misleading.

If the new package really fixes those 6 bugs as mentioned in #1, let's do an update.

Could you provide a package for testing first to the reporters mentioned?
Comment 5 Joachim Gleissner 2007-04-19 07:38:23 UTC 
Sure.
Comment 6 Joachim Gleissner 2007-04-19 07:39:41 UTC 
Created attachment 132354 [details]
Package with updated 3945 ucode
Comment 7 Joachim Gleissner 2007-04-19 07:40:51 UTC 
Created attachment 132355 [details]
Package with updated ipw3945d (i586)
Comment 8 Joachim Gleissner 2007-04-19 07:41:45 UTC 
Created attachment 132356 [details]
Package with updated ipw3945d (x86_64)
Comment 9 Stefan Behlert 2007-08-01 10:01:29 UTC 
Ok, this is quite old. No response regarding tests, so - should we update, AJ, or simply close this?  I guess this is no problem on 10.3.
Comment 10 Andreas Jaeger 2007-08-01 12:43:28 UTC 
Close it as fixed for 10.3.