Linux & Asus P5QL Pro

One of the more annoying things about new [stag]motherboards[/stag] and [stag]Linux[/stag] is that they sometimes does not work - that is they actually work, but then something does not work.

The most annoying thing for me is always the network card.....

In this case with the Asus P5QL Pro, the network card was not recognized by the Linux distribution I normally use for my server (CentOS), and after having spend a reasonable time using Google trying to find out what was going on - I successfully figured out:


  1. the driver is skge (skge.ko)

  2. the driver is not working (depends... on the version)

  3. the best way is to compile the driver from source



Steps required:


  1. install kernel-headers

  2. install development tools (gcc and make)

  3. get the source for the linux drivers here

  4. compile the driver
    # unzip LinuxDrivers.zip
    # cd LinuxDrivers/Lan/linux-v<version>/src
    # make

  5. and if no errors
    # make install



This will install 'atl1e.ko' which is the name of the driver Asus provides - see it's kind of different to the one which is in the kernel already (crap!)

Now the problem is that next time you update your kernel you need to compile the kernel module again to get networking running.

Until the driver in the kernel is updated, I can only see one solution - have two network cards.

The buildin (which is the primary), and then another one which will give access to the box so that it's possible to enable the driver again (crap! again!).

Comments

Shaarangapanaye said…
This may not be revelant but i figured i'd post this anyway. If you're using ubuntu 8.10 you may be in for some issues with the network manager. For some unknown reason it stops functioning. You will need to manually set you're resolv.conf with your ISP's DNS servers. That file is located in /etc/network/resolv.conf
casper said…
I'm not using Ubunto, and the issue is that the kernel with CentOS 5.2 does not include the kernel module for the network card on this MB.
memed said…
Thanks for this blog. I got the same problem with the driver and the DNS got messed up too. resolved by adding "nameserver XXX:XXX:XXX:XXX" where XXX stands for the IP address of the DNS server

Popular posts from this blog

Apple AirPort Express and Digital Jitter..

EIZO Colornavigator - Data Access Error

Using Borg backup across SSH with sshkeys