Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 76715 - ipw2200 >=17 firmware driver issue
Summary: ipw2200 >=17 firmware driver issue
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major
Assignee: Jeremy Maitin-Shepard
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-04 19:20 UTC by Dave Shanker
Modified: 2005-01-05 11:37 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Shanker 2005-01-04 19:20:12 UTC
It seems as though the ipw2200 driver project renamed the firmware files from ipw2200_ucode.fw, ipw2200_ibss.fw, ipw2200_bss.fw, ipw2200_boot.fw to ipw-2.2-bss_ucode.fw, ipw-2.2-ibss.fw, ipw-2.2-bss.fw, ipw-2.2-boot.fw, and ipw-2.2-ibss_ucode.fw. 

The issue is when loading the updated ipw2200 driver, it's still looking for the older file schema and then fails to load. The following error message is logged in dmesg:

ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200_boot.fw load failed
ipw2200: Unable to load firmware: 0xFFFFFFFE
ipw2200: failed to register network device
ipw2200: probe of 0000:02:03.0 failed with error -5
ieee80211_crypt: registered algorithm 'WEP'

Symlinking the files in /lib/firmware to the names used by the previous filename schema (ipw-2.2-ibss_ucode.fw was not present in previous versions) allows the driver to load.

This bug is present in all versions using the new firmware version (firmware version 2.2) which are ebuilds 17 and greater.

Reproducible: Always
Steps to Reproduce:
1.Upgrade to ipw2200 v17 or greater
2.Insert module
3.

Actual Results:  
Error is logged and device fails to come up properly

Expected Results:  
Device should have initialized properly
Comment 1 Jeremy Maitin-Shepard 2005-01-05 00:26:05 UTC
I do not have this problem.  Perhaps you are loading the old driver for some reason?
Comment 2 Dave Shanker 2005-01-05 11:37:57 UTC
You are correct.. I didn't notice I had /usr/src/linux symlinked to /usr/src/linux-2.4.9-r9-c1 instead of the kernel I was running. Portage would install the new modules in the lib directory of 2.4.9-r9-c1 instead of my current  kernel.

Changing status to INVALID.. sorry to waste your time :(