cannot connect wirelessly via WPA after installing Ubuntu easy peasy for netbooks

Asked by Angie

I cannot connect wirelessly via WPA after installing Ubuntu easy peasy for netbooks the system changes my key to WEP.
I have downloaded the Atheros 242 drivers, but they will not install.

701 4G EEEPC
Ubuntu 8.10 Intrepid
Kernal Linux 2.6.27-8-eeepc
GNOME 2.24.1

Please help I have checked may forums but none of the fixes work.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Angie
Solved:
Last query:
Last reply:
Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#1

Hi,

Please follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->
Terminal"

Step 2: Run the following commands (type each then hit <enter>)

sudo iwlist scanning
nm-tool
iwconfig
ifconfig
sudo lshw -C network
lspci -nn
lsusb
uname -a
dmesg | grep ound

Step 3: Post results (cut/paste terminal output from each command) here

Regards,

Mark

Revision history for this message
peter b (b1pete) said :
#2

please run in a terminal

lsb_release -a

and post the output here; I strongly believe/suspect that you have hardy 804 distro installed; if that's the case then, in my case, it works out of the box. you can also go to System --> Admin --> Network and check/configure your interface; the wifi drivers in easy peasy ubuntu should be installed automatically; I have eeePC 900 and easy peasy v1 (formerly ubuntu eee 8041) works flawlessly.

peter b

Revision history for this message
Angie (amw3) said :
#3

I entered the first line command and got this:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

pan0 Interface doesn't support scanning.

angie@angie-laptop:~$
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

pan0 Interface doesn't support scanning.

angie@angie-laptop:~$

On Sat, 2009-01-17 at 13:30 +0000, Mark Rijckenberg wrote:
> Your question #57805 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/57805
>
> Status: Open => Needs information
>
> Mark Rijckenberg requested for more information:
> Hi,
>
> Please follow this procedure:
>
> Step 1: Open Terminal from "Applications->Accessories->
> Terminal"
>
> Step 2: Run the following commands (type each then hit <enter>)
>
> sudo iwlist scanning
> nm-tool
> iwconfig
> ifconfig
> sudo lshw -C network
> lspci -nn
> lsusb
> uname -a
> dmesg | grep ound
>
>
> Step 3: Post results (cut/paste terminal output from each command) here
>
> Regards,
>
> Mark
>

Revision history for this message
Angie (amw3) said :
#4

This is the return from that command:

angie@angie-laptop:~$ lsb__release -a
bash: lsb__release: command not found
angie@angie-laptop:~$

On Sat, 2009-01-17 at 14:53 +0000, peter b wrote:
> Your question #57805 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/57805
>
> Status: Needs information => Answered
>
> peter b proposed the following answer:
> please run in a terminal
>
> lsb_release -a
>
> and post the output here; I strongly believe/suspect that you have hardy
> 804 distro installed; if that's the case then, in my case, it works out
> of the box. you can also go to System --> Admin --> Network and
> check/configure your interface; the wifi drivers in easy peasy ubuntu
> should be installed automatically; I have eeePC 900 and easy peasy v1
> (formerly ubuntu eee 8041) works flawlessly.
>
> peter b
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#5

Hi,

Can you please send the output of the other 8 commands? We need the output of the other 9 commands in order to be able to analyze your wireless issue.

Please also send the output of

lsb_release -a

There is only one _ (underscore) in lsb_release -a , not two _ (underscores)

Thanks,

Regards,

Mark

Revision history for this message
Angie (amw3) said :
#6

Sorry,here are the results you need. I will say that the wifi light is
on, although FN F2 combo, neither turns it on or off.

angie@angie-laptop:~$ sudo iwlist scanning
[sudo] password for angie:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

pan0 Interface doesn't support scanning.

angie@angie-laptop:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0
----------------------------------------------------------------
  Type: Wired
  Driver: atl2
  State: connected
  Default: yes
  HW Address: 00:1E:8C:D3:DE:11

  Capabilities:
    Supported: yes
    Carrier Detect: yes
    Speed: 100 Mb/s

  Wired Settings

  IPv4 Settings:
    Address: 192.168.0.4
    Prefix: 24 (255.255.255.0)
    Gateway: 192.168.0.1

    DNS: 192.168.0.1

- Device: wlan0
----------------------------------------------------------------
  Type: 802.11 WiFi
  Driver: ath5k_pci
  State: disconnected
  Default: no
  HW Address: 00:00:00:00:00:00

  Capabilities:
    Supported: yes

  Wireless Settings
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  Wireless Access Points

angie@angie-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:""
          Mode:Managed Frequency:2.412 GHz Access Point:
Not-Associated
          Tx-Power=0 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

angie@angie-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1e:8c:d3:de:11
          inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::21e:8cff:fed3:de11/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:3877 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3534 errors:0 dropped:0 overruns:0 carrier:3
          collisions:0 txqueuelen:1000
          RX bytes:2598590 (2.5 MB) TX bytes:0 (0.0 B)
          Memory:fbfc0000-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:16436 Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:752 (752.0 B) TX bytes:752 (752.0 B)

angie@angie-laptop:~$ sudo lshw -C network
  *-network
       description: Ethernet interface
       product: L2 100 Mbit Ethernet Adapter
       vendor: Attansic Technology Corp.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: a0
       serial: 00:1e:8c:d3:de:11
       size: 100MB/s
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vpd bus_master cap_list ethernet
physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=atl2
driverversion=2.2.3 duplex=full firmware=L2 ip=192.168.0.4 latency=0
link=yes module=atl2 multicast=yes port=twisted pair speed=100MB/s
  *-network DISABLED
       description: Wireless interface
       product: AR242x 802.11abg Wireless PCI Express Adapter
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wmaster0
       version: 01
       serial: 00:15:af:77:a7:42
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list logical
ethernet physical wireless
       configuration: broadcast=yes driver=ath5k_pci latency=0
module=ath5k multicast=yes wireless=IEEE 802.11bg
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: 66:f6:07:0c:2b:33
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3
firmware=N/A link=yes multicast=yes
angie@angie-laptop:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML
Express Processor to DRAM Controller [8086:2590] (rev 04)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04)
00:02.1 Display controller [0380]: Intel Corporation Mobile
915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) High Definition Audio Controller [8086:2668] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 1 [8086:2660] (rev 04)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 2 [8086:2662] (rev 04)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 3 [8086:2664] (rev 04)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #1 [8086:2658] (rev 04)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #2 [8086:2659] (rev 04)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #3 [8086:265a] (rev 04)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB UHCI #4 [8086:265b] (rev 04)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev d4)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC
Interface Bridge [8086:2641] (rev 04)
00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA
Controller [8086:2653] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) SMBus Controller [8086:266a] (rev 04)
01:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x
802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
03:00.0 Ethernet controller [0200]: Attansic Technology Corp. L2 100
Mbit Ethernet Adapter [1969:2048] (rev a0)
angie@angie-laptop:~$ lsusb
Bus 005 Device 002: ID 0951:1606 Kingston Technology
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
angie@angie-laptop:~$ uname -a
Linux angie-laptop 2.6.27-8-eeepc #1 SMP Sun Nov 16 12:02:12 MST 2008
i686 GNU/Linux
angie@angie-laptop:~$ dmesg | grep ound
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working it
around.
[ 0.000000] found SMP MP-table at [c00ff780] 000ff780
[ 1.210381] pnp: PnP ACPI: found 13 devices
[ 3.395655] pcieport-driver 0000:00:1c.0: found MSI capability
[ 3.396305] pcieport-driver 0000:00:1c.1: found MSI capability
[ 3.396894] pcieport-driver 0000:00:1c.2: found MSI capability
[ 3.593136] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 6.332139] hub 1-0:1.0: USB hub found
[ 6.439898] hub 2-0:1.0: USB hub found
[ 6.541285] hub 3-0:1.0: USB hub found
[ 6.635355] No dock devices found.
[ 6.835455] hub 4-0:1.0: USB hub found
[ 6.959235] hub 5-0:1.0: USB hub found
[ 8.603719] usb-storage: device found at 2
[ 16.140675] iTCO_wdt: Found a ICH6-M TCO device (Version=2,
TCOBASE=0x0860)
[ 20.734176] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY:
0x70)
[ 28.918688] lp: driver loaded but no devices found
angie@angie-laptop:~$

On Sat, 2009-01-17 at 13:30 +0000, Mark Rijckenberg wrote:
> Your question #57805 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/57805
>
> Status: Open => Needs information
>
> Mark Rijckenberg requested for more information:
> Hi,
>
> Please follow this procedure:
>
> Step 1: Open Terminal from "Applications->Accessories->
> Terminal"
>
> Step 2: Run the following commands (type each then hit <enter>)
>
> sudo iwlist scanning
> nm-tool
> iwconfig
> ifconfig
> sudo lshw -C network
> lspci -nn
> lsusb
> uname -a
> dmesg | grep ound
>
>
> Step 3: Post results (cut/paste terminal output from each command) here
>
> Regards,
>
> Mark
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#7

Hi,

In this specific case, I suggest booting from the Ubuntu 8.10 LiveCD and then doing a clean install of Ubuntu 8.10 on your netbook.

Then connect your ethernet card to your wireless router using a LAN cable and then follow the instructions from forumuser "reasoner" at this location:

http://ubuntuforums.org/showthread.php?t=902860&highlight=AR242x

This wireless problem has been discussed on
https://answers.launchpad.net/ubuntu/+question/52089 and on
https://answers.launchpad.net/ubuntu/+question/46457

Regards,

Mark

Revision history for this message
peter b (b1pete) said :
#8

ok Angie, a little clarification - yes, the FORMER ubuntu eee is now called easy peasy; it happened apparently

AFTER ubuntu eee 8041 release that I have installed on my eeePC and is STILL called ubuntu eee but
BEFORE the NEW easy peasy v1 THAT is a ubuntu 810 release BUT patched; the FIRST easy peasy release as you could see is v1 and was released sometime after beginning of 2009

on my ubuntu eee 8041 installation

lsb_release -a

command outputs the following

Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy

and as I said, wifi (atheros interface) works out of the box. I would strongly suggest to get installed ubuntu eee 8041 release - it is v well tested and v solid compared with the newer release easy peasy that may still have some bugs, (the lack of output to lsb_release -a command explains also the change that happened described above) the decision is obviously yours. should you decide to install 8041 then the following url's will help you do that

 http://sourceforge.net/project/downloading.php?group_id=213463&filename=ubuntu-eee-8.04.1.iso&99571803

now, after install completed, I have installed the classic desktop instead of the Remix desktop; the url's that follow will show you how to do that

http://www.ubuntu-eee.com/wiki/index.php5?title=How_to_use_Ubuntu_Eee_8.04.1%27s_Regular_Desktop_mode_instead_of_the_Netbook_Remix_interface
http://ubuntu-eee.com/wiki/index.php5?title=User_Guides

so, it is up to you to decide; switching to 8041 will no doubt give you peace of mind so to speak, or continue with easy peasy v1 and see what other users experience is related to atheros wifi in easy peasy

hope that the above is if help

regards,
peter b

Revision history for this message
Angie (amw3) said :
#9

Well, after reinstalling Ubuntu Intrepid, I find I still cannot connect wirelessly.
However, it did connect to a friends wireless network, so I changed everything from WPA to WEP, and achieved a connection.
But when I rebooted later, I cannot see any wireless networks, and even if I create a new one I only receive a message saying "network connection disconnected".
Wireless adaptor is on, in fact if I disable it in the bios, it turns itself on once booted.

Please, if anyone has any ideas, they would be very welcome at this stage.

Angie

Revision history for this message
peter b (b1pete) said :
#10

ok Angie, if I understand it correctly, you have now ubuntu intrepid 810 installed so pls copy/paste here output of

lsb_release -a

in intrepid 810 you should see on the upper panel right hand side the connection applet. pls confirm this.

if you left click on it do you see any ssid listed ? or what do you see ?

if you right click on it you should see an entry Edit connections; select it --> a new window will open where you can see a tab called Wireless - open it , it'll have other tabs also that enables to configure the connection for any particular ap INCLUDING the encryption if any - see below discussion about encryption.

pls post here output of

iwconfig

it'll probably show the interface as ath0 or maybe wlan0 then pls run

sudo iwlist <interface name as defined above> scan

and post this output here too.

just for general knowledge - the ap administrator establishes whether the ap should or should not be encrypted; if he decides no encryption then in the pc interface should also be no encryption; conversly, if the ap is encrypted the pc interface MUST have THE SAME TYPE AND ENCRYPTION string entered otherwise there won't be any conn'n to that ap.

about encryption topic - let's first see the output of above commands and answers then we'll continue.

peter b

Revision history for this message
Angie (amw3) said :
#11

Hi Peter, I am at work, and again it is connecting fine, I cannot try your suggestions until I return home.
However it has been suggested to me that Linux does not like a Dynamic IP, so I am going to check that my Router is set to Static and see if this resolves the problem, as the rest of the settings are 100% accurate.

Will check this and try your suggestions and get back to you later.

Thanks

Angie

Revision history for this message
Angie (amw3) said :
#12

Hi Peter, Ok I have just spent 2 hours changing various settings on the eee and the Router, my Router (Sky supplied Netgear) is now reset to DHCP, I have changed to Wireless settings on the eee to manual, I had to tweak them a little, and reboot numerous times, but for now at least it is working.

So, although everbody but me was aware, it definately seems as though a static IP is what is required to resolve this problem.

Thank you for your help and input, lets hope this is a total fix and not a stop gap.

Angie

Revision history for this message
peter b (b1pete) said :
#13

Angie, about dynamic and static IP's - the ISP is the one that sets up HIS end to accommodate either one of them.; so, probably it would be quite all right to have a chat with your ISP and find out exactly what your account is set up as dynamic or static. then, you must set up your modem/router FIRST to same. now, router-pc connection, I would recommend to enable DHCP on the router and then obviously, your pc connection to the router to same.

ubuntu/linux has NO problem whatsoever to connect to either type; in my case I have a dynamic setup; the DHCP is enabled on my router so it assigns IP's automatically to the pc's connected AND the connection files on the pc's are set again to DHCP. I never have or had any problems with this set up.

so, as said, check your router settings to match what your ISP set up is. then act on the router and pc connections settings. if all above are observed then you should have no problems of connecting to any ap that have NO encryption set; for the ones that are encrypted, well, obviously you'd have to enter in the connection file the exact type and string given to you by the ap administrator (as discussed above).

pls carry out these checks and see how things go. if you need more help just let me know. if you're satisfied then pls close this ticket as solved.

peter b

Revision history for this message
Angie (amw3) said :
#14

Hi Peter, I will check with the ISP tomorrow, as now I have lost it AGAIN.

Will post there comments here for you and the close the thread.

Angie x

Revision history for this message
Angie (amw3) said :
#15

Ok quick update:

It appears that, if I want to connect wirelessly, I have to connect within about 6 feet from my Router, however once connected I can travel around the house, without losing the connection.

So whatever, the problem was or is, it is a least workable.

Many many thanks to all who have helped, especially Peter for yur time and patience.

Angie

Revision history for this message
peter b (b1pete) said :
#16

glad that I could be of help.

about the 6 ft thing - it happens to me sometimes with the pc connection from the living room to router/ap that is approx 40 ft away and on a different floor but if I try a second time the connection is always done. just guessing and speculating - probably in high rise bldgs where there is a lot of steel embedded in the walls floors and ceilings there may be some interference with the signal and that may cause some problems. in any rate, the way you speak it appears that there is nothing wrong as long as you can connect; I would as you say still talk with the ISP and check once more the modem/router settings just to be sure that everything is ok.

regards,
peter b