Difference between revisions of "User:Xgamer99"

From ArchWiki
Jump to: navigation, search
(Remote)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
=ASUS AT3IONT-I=
+
=Hello <nowiki>=3</nowiki>=
This page describes the step necessary to get all of the features of the ASUS AT3IONT-I [Deluxe] 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 {{filename|/etc/asound.conf}} (or, alternatively, on a per-user basis via {{filename|~/.asound.conf}}).
+
 
+
{{file|name=/etc/asound.conf|content=# Needed in order to get sound over HDMI to function
+
 
+
#$ aplay -l
+
# **** List of PLAYBACK Hardware Devices ****
+
# card 0: NVidia [HDA NVidia], device 0: ALC887 Analog [ALC887 Analog]
+
#  Subdevices: 1/1
+
#  Subdevice #0: subdevice #0
+
# card 0: NVidia [HDA NVidia], device 1: ALC887 Digital [ALC887 Digital]
+
#  Subdevices: 1/1
+
#  Subdevice #0: subdevice #0
+
'''# card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]'''
+
#  Subdevices: 1/1
+
#  Subdevice #0: subdevice #0
+
<nowiki>
+
pcm.!default {
+
  type plug
+
  slave.pcm "dmix:0,3"
+
}</nowiki>
+
}}
+
 
+
{{Note|Audio over HDMI is designated by <tt>S/PDIF 1</tt> channel in <tt>alsamixer</tt>. You will need to unmute that channel in addition to configuring {{filename|/etc/asound.conf}}.}}
+
 
+
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 [https://bbs.archlinux.org/viewtopic.php?pid=858686#p858686 this post] on the Arch Forums.
+
 
+
{{Tip|Please also see [[ALSA]] for more information}}
+
 
+
==Deluxe Edition==
+
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.
+
 
+
===Bluetooth===
+
The Bluetooth chip is an Atheros with a device ID of <tt>0cf3:3002</tt>. It uses the <tt>ath3k</tt> driver which has been included in the kernel since ~2.6.33 and works out of the box with the default Arch kernel.
+
 
+
{{Tip|Please see [[Bluetooth]] for more information.}}
+
 
+
===Wireless===
+
The wireless chipset is an Atheros AR9285.
+
{{Command|<nowiki>lspci | grep Net</nowiki>|05:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)}}
+
It uses the <tt>ath9k</tt> 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.
+
{{Tip|Please see [[Wireless_Setup#ath9k]] for more information}}
+
 
+
===RCA Stereo Output===
+
Untested.
+
 
+
===Remote===
+
<!-- the Asus remote has limited functionality out of the box. Everything except the eight 'special' media buttons at the bottom. Also, need to bliacklist the kernals mceusb module since is fails out. lirc's mceusb module is much better, but still doesn't support all the buttons on the Asus remote -->
+
 
+
Special thanks to [http://ubuntuforums.org/member.php?u=109915 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 [http://ubuntuforums.org/showpost.php?p=9293063&postcount=12 pj7's driver].
+
 
+
{{Tip|It might be easier to just buy a decent IR receiver/remote combo that is know to work well in Linux to get the most functionality. But if you're stubborn, read on!}}
+
 
+
; Note<nowiki>:</nowiki> : If you know more about the nitty gritty aspects of kernel driver development and IR remotes, please take a look at [http://ubuntuforums.org/showthread.php?t=1458300&page=4 this thread] to see if functionality can be added to this driver, especially for basic MCE remotes.
+
 
+
Download the source from [http://www.4shared.com/file/qU2eSziu/hid-philips-asus.html here], and then extract with {{codeline|tar -xvf hid-philips-asus.tar}}. 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 {{filename|mappings.h}}. 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 {{map_linux_to_x11.txt}} 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 <tt>BUTTON_NEXT</tt> in {{filename|mappings.h}} as <tt>KEY_NEXTSONG</tt> rather than <tt>KEY_NEXT</tt>. This is because <tt>KEY_NEXTSONG</tt> maps to "XF86AudioNext" (KEY_NEXT doesn't register as anything). <!-- A sample file is provided in the resources section -->
+
 
+
Once you've finished mapping the buttons, run {{codeline|make}}:
+
{{command|make|make -C /lib/modules/2.6.36-ARCH/build M=/home/user/hid-philips-asus modules
+
make[1]: Entering directory `/usr/src/linux-2.6.36-ARCH'
+
  CC [M]  /home/user/hid-philips-asus/hid-philips-asus.o
+
  Building modules, stage 2.
+
  MODPOST 1 modules
+
  CC      /home/user/hid-philips-asus/hid-philips-asus.mod.o
+
  LD [M]  /home/user/hid-philips-asus/hid-philips-asus.ko
+
make[1]: Leaving directory `/usr/src/linux-2.6.36-ARCH'
+
}}
+
 
+
Install the driver with {{codeline|make install}} (as root).
+
 
+
Now we must make sure the driver loads correctly. One thing that you must do is blacklist the <tt>mceusb</tt> driver that tries to load whenever the IR Reciever is detected. Then you must make sure that the new <tt>hid-philips-asus</tt> driver loads before <tt>usbhid</tt> as <tt>usbhid</tt> will try to take over the receiver. This can all be easilly accomplished by the <tt>MODULES</tt> line in {{filename|/etc/rc.conf}}:
+
{{file|name=/etc/rc.conf|content=...
+
MODULES=(... '''!mceusb hid-philips-asus usbhid''' ...)
+
...
+
}}
+
 
+
(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 {{filename|mappings.h}} file and {{codeline|make && make install}} again. Alternatively, you may be interested in [[Xmodmap]].
+
 
+
<!-- todo: create AUR package -->
+

Latest revision as of 02:25, 13 January 2011

Hello =3