From ArchWiki
Revision as of 07:14, 23 February 2010 by Unhammer (talk | contribs) (time, time, TIME to understand the world (monster monster monster monster))
Jump to: navigation, search

My setup

Mainboard: ASUS M4A785TD-M EVO, Socket-AM3 AMD 785G+SB710, DDR3, Firewire, GbLAN, m-ATX, HDMI, DVI, PCI-Ex(2.0)x16

Processor: Phenom II X3 720 Black

Power supply: Silver Power SP-400P2C 400W

Wifi: CNet CWP-854 RT2561T D-Link G-520


The card is an integrated Radeon HD4200.

I tried the proprietary catalyst drivers from AUR, worked OK. Neverball was fast and xvinfo showed a buncha stuff wot I don't understand so that seemed to work too. I had to set TerminateServer=True to get kdm to not freeze on logout, as described in the wiki on ATI.

I switched to the free drivers, here xvinfo and glxinfo say "Error: unable to open display", but I can select OpenGL for compositing and get the wobbly windows etc. I'm not running KMS yet.


The CNet card was problematic, but my new D-Link G-520 works great so far with ath_pci (putting !ath5k in MODULES in /etc/rc.conf) and netcfg2/net-profiles (net-auto-wireless).

Fan control

Had a bit of trouble at first, but it seems to work now. Unfortunately I have to reconfigure it on each update :-/


For some reason, time has been my most persistent problem… When I was having network problems, and openntpd had no chance of updating time on the web, the hwclock seemed to be set to whatever it was last boot, creating lots of "last mount date in the future" errors on startup, meaning I had to e2fsck 800GB on each boot if I wasn't careful about setting the hwclock manually. Not very user-friendly. At least with a better network, openntpd has a chance to keep the time up-to-date, but I still sometimes have to do that startup disk-check. I've put the following into the root crontab:

30 * * * * /etc/rc.d/openntpd restart
45 * * * * hwclock --systohc

in case the net connection drops, openntpd gets a chance to start up again, and the hwclock gets a chance to sync.