Re: wifi connect _FAILS_ - was [Re: FROZEN Wheezy netinst - Where to get?]
On Thu 26 Jul 2012 at 09:27:44 -0500, Richard Owlett wrote:
> Brian wrote:
> >
> >A possible failure to associate with the wireless access point. What
> >does lspci (or lsusb) say the card is?
>
> 03:00.0 Ethernet controller: Atheros Communications Inc. AR5212
> 802.11abg NIC (rev 01)
> >
> >Encouraging. The Debian Live connection was set up and established
> >after the OS had been booted?
>
> And happily connects after full install from liveCD - always has.
The AR5212 doesn't require non-free firmware so, at the 'Detect network
hardware' stage, eth0 and wlan0 should be found and presented to you
when the network is configured. You'll have chosen wlan0, put the type
of wireless network as 'Managed' and input an ESSID and WPA/WPA2 PSK.
When next you do this switch to console 4, where you should see
'authenticated', 'associated' and 'SUCCESS' as part of the output log.
If this succeeds you can look at console 4 while DHCP is set up. Watch
for ADDRCONF(NETDEV_CHANGE) and 'Got IP . . .' from udhcp. Reported
failure to get an address should have the log information with it.
Reply to: