With wireless-testing master-2008-12-23 (also plus 2.6.28-rc9-git4 patch) everthing OK in iwl3945-world. Both Linux kernel works fine. Thank you for the gift. -Sedat # env COLUMNS=250 dpkg -l | grep linux-image | grep 2.6.28-rc9 ii linux-image-2.6.28-rc9-git4-wl-gcc44 2.6.28~rc9+git4+wl~git20081223.fd1dae5~dileX+1 Linux kernel binary image for version 2.6.28-rc9-git4-wl-gcc44 ii linux-image-2.6.28-rc9-wl-gcc44 2.6.28~rc9+wl~git20081223.fd1dae5~dileX+1 Linux kernel binary image for version 2.6.28-rc9-wl-gcc44 On Tue, Dec 23, 2008 at 9:43 PM, Kalle Valo <kalle.valo@xxxxxx> wrote: > Zhu Yi <yi.zhu@xxxxxxxxx> writes: > >> On Mon, 2008-12-22 at 22:07 +0800, Kalle Valo wrote: >>> Yes, ifconfig up works but now iwlist wlan0 scan crashes. I just >>> tested this once due to lack of time. >>> >>> I hope I get my wifi working before Christmas ;) >> >> http://marc.info/?l=linux-wireless&m=123000088608330&w=2 should fix the >> problem. Thanks a lot for your testing. > > Yes, that patch fixed it. Now my wifi is working again, thank you for > the present! :) > > Just to be clear, these are the patches I have applied on top of > current wireless-testing: > > Revert "iwl3945: remove iwl-3945-led.[ch]" > iwl3945: use rx queue management infrastructure from iwlcore > iwlwifi: fix warning 'Should it be static' > iwlwifi: kill retry_rate sysfs for iwlagn > iwlwifi: move sysfs status entry to debugfs > iwl3945: use iwl3945_tx_cmd instead of iwl_tx_cmd > iwl3945: switch to the iwl-core send_card_state routine > iwl3945: remove iwl-3945-led.[ch] > iwl3945: sync tx queue data structure with iwlagn > iwl3945: adding utils ops > iwl3945: rearrange 3945 tfd > > If I spot any regressions, you will hear from me ;) > > -- > Kalle Valo > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html