Hiho, No Xmas-bells ringing here. I applied the patch-series 01/10 till 10/10 and afterwards I reverted 04_10_iwl3945-remove-iwl-3945-led.[ch].patch with Yi's revert-patch. On the first sight, everything seems OK. iwlist, wpa_cli gave the expected values back, but there is no DNS resolved properly, e.g. ping. This new state is also not usable for me :-). What does this mean? [...] /var/log/syslog:Dec 23 08:18:05 seduxbox kernel: mac80211-phy0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-22) [...] Do I need any mac80211-patches additionally? The file exists: $ ls -l /lib/modules/2.6.28-rc9-git3-wl-gcc44/kernel/drivers/crypto/padlock-aes.ko -rw-r--r-- 1 root root 11724 2008-12-23 07:46 /lib/modules/2.6.28-rc9-git3-wl-gcc44/kernel/drivers/crypto/padlock-aes.ko Kind Regards, Sedat ----- Investigations ----- [...] /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: EXT4-fs: mounted filesystem with ordered data mode. /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: kjournald starting. Commit interval 5 seconds /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: EXT3 FS on sda6, internal journal /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: EXT3-fs: mounted filesystem with ordered data mode. /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: iwl3945 0000:10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: iwl3945 0000:10:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006) /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: iwl3945 0000:10:00.0: irq 1274 for MSI/MSI-X /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: iwl3945 0000:10:00.0: loaded firmware version 15.28.2.8 /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: Registered led device: iwl-phy0:radio /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: Registered led device: iwl-phy0:assoc /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: Registered led device: iwl-phy0:RX /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: Registered led device: iwl-phy0:TX /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: NET: Registered protocol family 17 /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: NET: Registered protocol family 10 /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: lo: Disabled Privacy Extensions /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: wlan0: authenticate with AP 00:1c:4a:41:62:2e /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: wlan0: authenticated /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: wlan0: associate with AP 00:1c:4a:41:62:2e /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: wlan0: RX AssocResp from 00:1c:4a:41:62:2e (capab=0x411 status=0 aid=1) /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: wlan0: associated /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready /var/log/syslog-Dec 23 08:18:05 seduxbox kernel: padlock: VIA PadLock not detected. /var/log/syslog-Dec 23 08:18:05 seduxbox modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.28-rc9-git3-wl-gcc44/kernel/drivers/crypto/padlock-aes.ko): No such device /var/log/syslog:Dec 23 08:18:05 seduxbox kernel: mac80211-phy0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-22) [...] On Tue, Dec 23, 2008 at 3:58 AM, Zhu Yi <yi.zhu@xxxxxxxxx> wrote: > 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. > > Thanks, > -yi > > -- > 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
