On Tue 05 May 2015 at 22:02:42 -0500, David Wright wrote: > Quoting Charles Kroeger (ckro...@frankensteinface.com): > > > > root@mundo:/home/charles# ifconfig -a > > eth0 Link encap:Ethernet HWaddr 00:1b:21:4f:60:49 > > inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 > > inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1051 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:291611 (284.7 KiB) TX bytes:82072 (80.1 KiB) > > Interrupt:17 Memory:fbfe0000-fc000000 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:65536 Metric:1 > > RX packets:55 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:15256 (14.8 KiB) TX bytes:15256 (14.8 KiB) > > > > wlan0 Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 > > inet addr:169.254.10.111 Bcast:169.254.255.255 Mask:255.255.0.0 > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > > root@mundo:/home/charles# lsmod | grep ath > > ath9k_htc 52702 0 > > ath9k_common 12687 1 ath9k_htc > > ath9k_hw 341687 2 ath9k_common,ath9k_htc > > ath 21417 3 ath9k_common,ath9k_htc,ath9k_hw > > mac80211 358182 1 ath9k_htc > > cfg80211 319971 3 ath,mac80211,ath9k_htc > > usbcore 134993 6 > > usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc > > At this stage, I would run wicd-curses (not as root) and type P. > I would make sure the Wireless and Wired Interfaces were correctly > named wlan0 and eth0, set automatic reconnection and any other options > I wanted, save that, scan for APs with Fn5, select one and press -> > to configure it. I would remove the ethernet cable because I have > that set to take priority. After saving the configuration, I'd press > Return and hope to have a wireless connection come up.
The wireless interface *does* exist *and* is named wlan0. The modules for the chip are present, The firmware for the device is loaded. All the basic conditions to estabish a connection with e/n/i are met. If there is no connection (which does not happen here with a similar chipset) then there is a deeper problem. wpasupplicant (on which wicd depends for its operation) and four lines in /e/n/i is about as basic as it gets. wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 This also does not happen here. The OP's system has failed to get an IP address on the wlan0 interface and has been provided with one by avahi. Maybe the router and/or DHCP provision need exploring as a cause for this. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150506091517.gj3...@copernicus.demon.co.uk
