tmende
01-26-2007, 03:43 AM
Upgraded from Knoppix V4.0.2 to V5.0.1. Luckily I kept my old CD. Support for ipw2200 appears to have broken in V5.0.1 on an Thinkpad T42 normally running SuSE 10.1 dual booting Windows XP. Here are the dmesg outputs for dmesg | grep -i ipw
V4.0.2
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.1
ipw2200: Copyright(c) 2003-2004 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
..and it works fine
V5.0.1
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
ipw2200: probe of 0000:02:02.0 failed with error -5
...and it doesn't work not surprisingly
reloaded Knoppix V4.0.2 works fine again. Works fine under SuSE 10.1 as well and Windows XP.
Any ideas on this? Googling around doesn't seem to find any solutions but the problem is not unknown. No previous posts seem to suggest it worked fine in V4.0.2 though so I thought it worth confirming it does and noting the network driver version seems to have changed. Willing to run tests on my T42 if anyone thinks this would help.
Cheers,
V4.0.2
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.1
ipw2200: Copyright(c) 2003-2004 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
..and it works fine
V5.0.1
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
ipw2200: probe of 0000:02:02.0 failed with error -5
...and it doesn't work not surprisingly
reloaded Knoppix V4.0.2 works fine again. Works fine under SuSE 10.1 as well and Windows XP.
Any ideas on this? Googling around doesn't seem to find any solutions but the problem is not unknown. No previous posts seem to suggest it worked fine in V4.0.2 though so I thought it worth confirming it does and noting the network driver version seems to have changed. Willing to run tests on my T42 if anyone thinks this would help.
Cheers,