Summary

The only problem encountered is actually a known Ubuntu bug, which is triggered by this motherboard having two Ethernet ports. If you have the first port on Static IP with a specified DNS address, and the second port just on "Roaming" or DHCP, then every 10 minutes Ubuntu will try to get the DNS addresses from DHCP on the port you're not using, fail, and overwrite your existing DNS information with "192.168.1.1".

There is a workaround available online for it. With the workaround in place, everything works well. Note that most people will use DHCP on their networks anyway, or not use Ubuntu, so that's okay.

I haven't tried suspend and hibernate yet.

The issue listed with the dual ethernet ports was a reality with me. Fortunately I found the workaround and I don't use the ethernet ports anymore anyway.

The wireless works out-of-the-box on Gutsy, but there's a known bug with the driver; on rare occasions (most noticably with high CPU load + high upstream + downstream traffic) the driver stops working and you need to modprobe it out and back in again. Annoying, but I run into it rarely.

Works:

Wireless
Ethernet ports (both of them)
Firewire
USB
SATA
CPU scaling
Audio output through rear port

Doesn't work:

Suspend and hibernate (note: I don't have a swap partition and I'm running Nvidia, this could be the cause).
Audio input - possibly a later version of ALSA would do the trick.
Reported CPU temperature is way too low (18 Celcius at idle), but I believe it reports the correct temperature when under load. The new version of lm-sensors should detect it all correctly anyway once Gnome is switched over to use it.


This is a good choice of motherboard for a Linux machine. Later versions of the kernel, wireless drivers, ALSA and lm-sensors (already out) will improve compatibility, I'm sure.