[Debian-eeepc-devel] Eeepc 1005HA: enabling network

Tim Legg kc0ofc at yahoo.com
Thu Dec 3 21:23:46 UTC 2009


Okay, It turns out that installing wicd from lenny-backports was not a dependency hell, but more like a mild purgatory.  I was very surprised that post of the wicd dependencies were already installed in the base install of debian.

So the wicd package is installed

The wifi howto does not apply to this wifi card because the 1005HA has the Atheros AR928X which is out of the scope of teh document.  Thanks for the link though.

My /etc/network/interfaces looks like

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback


So I added a few lines to see if that would make any difference:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wireless-essid router ID

When I run ifup ath0, I do get an error:

# ifup ath0
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device ath0 ; No such device.
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.

So anyway, I don't have wired ethernet working either, or at least not quite.  There is no eth device, but I am able to ping the router somehow.  God only knows how it can do that without any device in the /etc/network/interfaces file.  I didn't know that was even possible.

Here is some of the copnfiguration data you suggested for me to provide:

# /sbin/ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 90:e6:ba:54:40:a3  

          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)

          Interrupt:19 




# lsmod | grep atl1c

atl1c                  28736  0 



# uname -r 

2.6.31-1-686



# dmesg | egrep 'eth0|atl1c'

[   12.878441] atl1c 0000:01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19

[   12.878469] atl1c 0000:01:00.0: setting latency timer to 64

[   12.878544] atl1c 0000:01:00.0: PME# disabled

[   12.878557] atl1c 0000:01:00.0: PME# disabled

[   13.017985] atl1c 0000:01:00.0: version 1.0.0.1-NAPI

[  100.769267] atl1c 0000:01:00.0: PME# disabled

[  100.769279] atl1c 0000:01:00.0: PCI INT A disabled

[  103.365642] atl1c 0000:01:00.0: PME# disabled

[  103.365651] atl1c 0000:01:00.0: PME# disabled




I think we all learned a lesson in not buying a cutting edge machine and expecting everything to install as cleanly as on my 5 year old workstation.  I am starting to wonder if I should try again in 6 months when hardware support encompases the devices in this laptop.


--- On Wed, 12/2/09, Ben Armstrong <synrg at sanctuary.nslug.ns.ca> wrote:

> From: Ben Armstrong <synrg at sanctuary.nslug.ns.ca>
> Subject: Re: [Debian-eeepc-devel] Eeepc 1005HA: enabling network
> To: "Tim Legg" <kc0ofc at yahoo.com>
> Cc: debian-eeepc-devel at lists.alioth.debian.org
> Date: Wednesday, December 2, 2009, 7:30 AM
> On Tue, 1 Dec 2009 12:55:31 -0800
> (PST)
> Tim Legg <kc0ofc at yahoo.com>
> wrote:
> > So I have a kernel which supports the device according
> to the documentation above, but currently seems to not be
> enabled.
> > 
> > So here is what the interfaces file looks like:
> > 
> > % cat /etc/network/interfaces 
> > # This file describes the network interfaces available
> on your system
> > # and how to activate them. For more information, see
> interfaces(5).
> > 
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> > 
> > Aside from editing this file with an entry for eth0
> (for wired) and eth1 (for wireless), where else do edit in
> order turn use the ethernet card?  Is there a
> configuration script for helping setup the configuration for
> the netwrok devices?
> 
> That should be wlan0 for wireless, not eth1.  But if
> you use wicd to
> manage wireless and/or ethernet, you should not put
> anything
> in /etc/network/interfaces for any interface wicd manages.
> 
> For info on alternatives for setting up wireless, see:
> 
> http://wiki.debian.org/DebianEeePC/HowTo/Wifi
> 
> If you continue to have problems getting ethernet to work,
> please send
> us output from:
> 
> /sbin/ifconfig eth0
> 
> lsmod | grep atl1c
> 
> uname -r
> 
> dmesg | egrep '(eth[[:digit:]]|atl1c)'
> 
> as well as the contents of your /etc/network/interfaces and
> any other
> particulars you deem to be relevant.
> 
> Ben
> --
>  ,-.  nSLUG    http://www.nslug.ns.ca   synrg@sanctuary.nslug.ns.ca
>  \`'  Debian   http://www.debian.org    synrg at debian.org
>   `          [ gpg 395C F3A4
> 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]
> 


      



More information about the Debian-eeepc-devel mailing list