I started another install, had the same problem not detecting my WPA network. It still couldn't detect either of the two unprotected networks, even when I specified their ESSIDs.
Pulled from the syslog, here you see it finding the firmware: Aug 12 20:49:41 check-missing-firmware: missing firmware files (iwlwifi-3945-2.ucode iwlwifi-3945-1.ucode) for iwl3945 iwl3945 Aug 12 20:49:55 check-missing-firmware: installing firmware package /media/firmware-iwlwifi_0.28_all.deb Aug 12 20:49:56 kernel: [ 78.904299] iwl3945 0000:0c:00.0: PCI INT A disabled Aug 12 20:49:56 kernel: [ 78.950751] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks Aug 12 20:49:56 kernel: [ 78.950754] iwl3945: Copyright(c) 2003-2009 Intel Corporation Aug 12 20:49:56 kernel: [ 78.950813] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Aug 12 20:49:56 kernel: [ 78.950832] iwl3945 0000:0c:00.0: setting latency timer to 64 Aug 12 20:49:56 kernel: [ 79.006469] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels Aug 12 20:49:56 kernel: [ 79.006472] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG Aug 12 20:49:56 kernel: [ 79.006611] iwl3945 0000:0c:00.0: irq 29 for MSI/MSI-X Aug 12 20:49:56 kernel: [ 79.007201] phy0: Selected rate control algorithm 'iwl-3945-rs' Aug 12 20:49:56 kernel: [ 79.009064] iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode Aug 12 20:49:56 kernel: [ 79.012391] iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9 Aug 12 20:49:56 kernel: [ 79.079937] Registered led device: iwl-phy0::radio Aug 12 20:49:56 kernel: [ 79.080154] Registered led device: iwl-phy0::assoc Aug 12 20:49:56 kernel: [ 79.080305] Registered led device: iwl-phy0::RX Aug 12 20:49:56 kernel: [ 79.080457] Registered led device: iwl-phy0::TX Aug 12 20:49:58 kernel: [ 81.003877] Registered led device: iwl-phy0::radio Aug 12 20:49:58 kernel: [ 81.004125] Registered led device: iwl-phy0::assoc Aug 12 20:49:58 kernel: [ 81.004278] Registered led device: iwl-phy0::RX Aug 12 20:49:58 kernel: [ 81.004429] Registered led device: iwl-phy0::TX Aug 12 20:50:02 kernel: [ 85.367923] Registered led device: iwl-phy0::radio Aug 12 20:50:02 kernel: [ 85.368183] Registered led device: iwl-phy0::assoc The last 6 lines above repeated at least a dozen times in the syslog. then later when I'm trying the different networks: Aug 12 20:54:08 kernel: [ 330.522097] ADDRCONF(NETDEV_UP): wlan0: link is not ready Aug 12 20:54:09 kernel: [ 331.595802] Registered led device: iwl-phy0::radio Aug 12 20:54:09 kernel: [ 331.596049] Registered led device: iwl-phy0::assoc Aug 12 20:54:09 kernel: [ 331.596197] Registered led device: iwl-phy0::RX Aug 12 20:54:09 kernel: [ 331.596343] Registered led device: iwl-phy0::TX Aug 12 20:54:09 kernel: [ 331.597972] ADDRCONF(NETDEV_UP): wlan0: link is not ready Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc (v1.17.1) started Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Received SIGTERM Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc (v1.17.1) started Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: has been called with an unknown param: leasefail Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: Network is down, reopening socket Aug 12 20:54:13 main-menu[430]: (process:5459): Sending discover... Aug 12 20:54:13 main-menu[430]: (process:5459): udhcpc: sendto: Network is down Aug 12 20:54:13 main-menu[430]: (process:5459): Read error: The first six lines above repeated about a dozen times, don't know if that's related to the other repeating lines earlier. From Camaleón's comment, it sounds like using a wireless network to do an install is generally a problem, has anyone had success with a wireless install? I'm worried if I ever need to reinstall when I'm not in my home, it would not work. I don't know if I could get a wired network port away from home. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1313184640.63377.yahoomai...@web180609.mail.sp1.yahoo.com
