This page describes the steps necessary to get all of the features of the ASUS AT3IONT-I working correctly. It assumes you already successfully installed Arch Linux and installed the basic software (ALSA for audio, wireless_tools and wpa_supplicant packages for wireless in the Deluxe edition, etc.)
Audio over HDMI
Many ION boards exhibit problems when trying to play sound through HDMI. They usually require a custom ALSA configuration via Template:Filename (or, alternatively, on a per-user basis via Template:Filename).
Also, please note that audio over HDMI currently only works in an X session (graphical environment). If you are trying to get the sound to work when running on a virtual terminal, it won't work. Please see this post on the Arch Forums.
If you are loathe to mess with your pulseaudio settings in asound.conf, it might be enough to just unmute the S/PDIF 1 channel in alsamixer. It's hidden, as you need to press F6, then select "HDA NVidia" and scroll to the far right before you can find it. Highlight it, and then press "M" to unmute.
The deluxe edition comes with a few extra goodies, such as DC power on-board, mini-PCI WiFi, RCA stereo output, on-board Blutooth, and an included IR Remote.
The Bluetooth chip is an Atheros with a device ID of 0cf3:3002. It uses the ath3k driver which has been included in the kernel since ~2.6.33 and works out of the box with the default Arch kernel.
The wireless chipset is an Atheros AR9285. Template:Command It uses the ath9k driver, which has been included in the default kernel since 2.6.27. In other words, udev should load the driver without problems -- there should be no extra configuration to get wireless working on the ASUS AT3IONT-I.
RCA Stereo Output
Special thanks to pj7 of the Ubuntu forums for putting together a working driver for the receiver.
The included IR receiver requires a kernel module to be built to accommodate it. Apparently, it is a rather tricky little device. It seems to work best with the included remote -- it coverts the included remotes' button presses directly to keyboard keystrokes, but when using another MCE remote it reports to the system the raw code. It seems to understand other signals, but you will need a remote that sends the right signal. This results in limited functionality of the device where it can only use the included ASUS remote, a JP1 Programmable remote (to program the known signals), or a universal remote that has the ability to learn the IR signals of the ASUS remote.
As a result, this section will focus on getting the included remote working with the included receiver, based on pj7's driver.
- If you know more about the nitty gritty aspects of kernel driver development and IR remotes, please take a look at this thread to see if functionality can be added to this driver, especially for basic MCE remotes.
Download the source from here, and then extract with Template:Codeline. The resulting directory will include the source files, along with a Linux-to-X11 input key map. Before you build the source, you must edit Template:Filename. This file maps the button presses to Linux input keys. Be aware that Linux input does not equal X11 input. Graphical programs, such as media players, XBMC, and the like, are only aware of X11 inputs, and so you must match a X11 input with a Linux input to. That's what the Template:Filename file is for.
For example, if you wish to define the "Next Track" button as "XF86AudioNext" (which most programs will look for to play the next item in the playlist), you will need to define BUTTON_NEXT in Template:Filename as KEY_NEXTSONG rather than KEY_NEXT. This is because KEY_NEXTSONG maps to "XF86AudioNext" (KEY_NEXT doesn't register as anything).
Install the driver with Template:Codeline (as root).
Now we must make sure the driver loads correctly. One thing that you must do is blacklist the mceusb driver that tries to load whenever the IR Reciever is detected. Then you must make sure that the new hid-philips-asus driver loads before usbhid as usbhid will try to take over the receiver. This can all be easilly accomplished by the MODULES line in Template:Filename: Template:File
(rebooting the computer might be necessary)
After that, all the buttons on the Asus remote should work. If you find that you would rather assign different actions to button presses, it is easy to edit the Template:Filename file and Template:Codeline again. Alternatively, you may be interested in Xmodmap.