Bug 14873

Summary: iwl3945 no longer works since 2.6.33-rc1
Product: Drivers Reporter: Radek Pilar (rpilar)
Component: network-wirelessAssignee: drivers_network-wireless (drivers_network-wireless)
Status: CLOSED INVALID    
Severity: normal CC: linville, reinette.chatre, rjw
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: >=2.6.33-rc1 Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 14885    
Attachments: 2.6.33-rc2 config
Dmesg output
Dmesg - iwl3945 loaded with debug=0x43fff

Description Radek Pilar 2009-12-25 00:31:17 UTC
Created attachment 24300 [details]
2.6.33-rc2 config

After upgrading to 2.6.33-rc1 (and now -rc2) I can no longer  use my iwl3945 card.
There's nothing suspicious in dmesg. (But output attached for all cases).
iwconfig returns: wlan0     no wireless extensions.
iwlist: wlan0     Interface doesn't support scanning.
lspci output:
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Please contact me, if you need any additional info.
Thanks for assistance and merry Christmas!
Comment 1 Radek Pilar 2009-12-25 00:37:04 UTC
Created attachment 24301 [details]
Dmesg output
Comment 2 John W. Linville 2009-12-28 17:13:34 UTC
Did you do "ifconfig wlan0 up" first?
Comment 3 Radek Pilar 2009-12-28 18:06:04 UTC
Yes, of course.
Comment 4 Reinette Chatre 2010-01-05 00:11:34 UTC
could you please load module like "modprobe iwl3945 debug=0x43fff" and then send dmesg output from that as well as after you have run "ifconfig wlan0 up"
Comment 5 Radek Pilar 2010-01-05 00:49:56 UTC
Created attachment 24435 [details]
Dmesg - iwl3945 loaded with debug=0x43fff
Comment 6 Reinette Chatre 2010-01-05 17:22:04 UTC
Could you please set CONFIG_CFG80211_WEXT in your kernel config file?
Comment 7 Radek Pilar 2010-01-05 18:45:26 UTC
Weeell.. Sorry folks. I've apparently missed an API change... For the next time, I'll read the changelogs more carefully. With CFG80211_WEXT everything works fine (and I've found that "iw" works with CFG80211_WEXT disabled). So that's definitely my mistake.