Attansic atl1e eeePC 1000 LAN Driver Compile Install

To install the the lan driver for the eeePC 1000 you need build dependencies. If you are using a usb cd then after installation just use:

sudo apt-get install build-essential linux-headers-$(uname -r) unrar

If you don’t have anything you need to get the build dependencies onto your system the hard way. Luckily I spent 2 hours downloading every single package and associated dependencies from the Hardy repositories. The packages are for a default Hardy kernel 2.6.24 series straight off the CD. I also included the packages rerquired to build a kernel if you want to build the eeePC kernel provided at eeepc.asus.com.

hardy_i386_build_dep_with_Kernel_build_support.tar.bz2

Unzip the  package and use dpkg to take care of everything. Change to the directory:

cd Desktop/hardy_i386_build_dep_with_kernel_build_support

sudo dpkg -i *

You will have to flip back and forth with the following command:

sudo dpkg –configure -a

Lots of files require configuration prior to installation of subsequent files. This took some time, but most of the time was because the packages were bad downloads and I had to keep downloading them form different sources till they all worked. The folder contains the default kernel headers requires, and basically its an all in 1 package with everything you’ll need.

Now download the driver source direct from ASUS:

http://dlsvr04.asus.com/pub/ASUS/mb/socket775/P5KPL-CM/LinuxDrivers.zip

Unzip, and cd to the directory. Then cd to the src directory. Compile:

sudo KBUILD_NOPEDANTIC=1 make
sudo KBUILD_NOPEDANTIC=1 make install

After compilation and installation:

cd /lib/modules/2.6.24-19-generic/kernel/drivers/net/atl1e/atl1e.ko
sudo insmod ./atl1e.ko

Then run:

sudo depmod so modprobe knows the driver exists. If for some reason the driver
dousn't load automatically you can manually add it to /etc/modules.

Default Gateway Requirements

I recently had a server providing telnet service to a local area network. An external connection was required, and therefore port forwarding on the master router needed configuration. I forwarded telnet to the local IP of the server, but a telnet connection could not be established. This was because the server did not see the router as the default gateway.

The server must see the router, which requires the following command for a temporary solution:

route add default 192.168.0.1

Where 192.168.0.1 is the local IP address of the router. Depending on how often the server restarts you may have to set the default router permanently. Although if the server is never expected to restart then the temperatory solution will act as a pseudo permanent solution.

Hub Ethernal WAN Autodetect

On most all Ethernet hubs you can connection the WAN cable to any port. The same goes for your LAN cables. The hub almost always will automatically make the distinction between your LAN and WAN connections successfully providing internet access to your attached computers. Doesn’t everyone have a use for an eight (8) port hub?