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
March 16, 2009 at 6:09 AM
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.
March 16, 2009 at 12:05 PM
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
June 27, 2010 at 9:18 AM
Post a Comment

Popular posts from this blog

Apple AirPort Express and Digital Jitter..

I'm doing something which I can't really afford, but doing it anyway ... I'm upgrading my Stereo ... I like music, and  believe it should be played at the highest affordable quality. So after getting a new Stereo Amp (Creek Evolution 50A), I got a new Phono Amp. and then started looking for a DAC ... and after reading I do not know how many posts I decided to get an S.M.S.L M8 (from  Amazon  fro €249.99), not too expensive and according to what I can read very good. So I got it hooked it up to my amp, connected my Notebook (Macbook Air 11" / 2011) using USB ... sounded nice, then my Macbook Pro Retina with digital (fiber) in some way better than USB, slightly more air and openness. Then decided to use my old Apple Airport Express ( MB321LL/A  - 802.11n version 1) using it's digital output (I don't like the build in DAC - it's a bit too dark for me), and this is where I started having doubts about my buy. There was drop out, all the time. Right I changed, to
Read more

Kviknet and IPv6

Image
 I decided to switch ISP, mainly due to Hiper (Danish) was using a VLAN for their connection which made pfSense and my APU3 board require a reboot everytime I changed anything. Kviknet has a good reputation (wonder why) in Denmark, they are not cheap and they have the same opening hours as everyone else - meaning until 16:30 and closed during weekends. I sometimes wonder how companies who need 24/7 internet get on with that ... well it's Denmark. Kviknet has an interesting way to do IPv6, your router get and SLAAC assigned IPv6 address on the public side (wan) and you get a ::/48 network from Kviknet to use on your lan.  To some degree it does make sense, you can then configure your lan with static addresses as you see fit, and for dynamic assignment you use RA stateless dhcp *) ... which works for everything.  (I need to get my piHole configured with an static IPv6 so that I can use that ...). pfSense is a pain, I do like it, but they are light years behind their main competitor
Read more

MacOS Ventura: not able to ssh to ruckus switch (diffie-hellman-group1-sha1)

 I upgrade to Ventura and replaced my Intel MacMini with an M2 MacBook Air ... everything was working, then I wanted to ssh to my Ruckus ICX 7150-C12 (08.0.95fT211), and got an error: Unable to negotiate with my-switch port 22: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 Hummm, WTF.... I've seen similar things before when you upgrade FW or OS suddenly ssh will no longer work as a protocol or cipher have been deprecated. As I do not feel like upgrading my switch I had to do something else. I found this on serverfaul t, helped to a part of the way, and then a bit more googling I found the solution, which might be overkill. I ended up adding this in my ~/.ssh/config for the switch: Host my-switch KexAlgorithms=+diffie-hellman-group1-sha1 PubkeyAcceptedKeyTypes ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512 HostkeyAlgorithms +ssh-rsa    And now I can access my switch again. Yes, I know upgrading the firmw
Read more