ASUS DIGIMatrix

From LinuxMCE
Revision as of 08:35, 29 September 2006 by Wikiadmin (Talk | contribs) (HW clock problem)

Jump to: navigation, search
This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
Asus Digimatrix has pros and cons. Let me do initial evaluation...

I've also added Panel utility that lets you control LCD display...

Pros:
- small factor
- nice front panel
- integrated IR Remote
- Clock and Temp display (although Time under Pluto is not right at the moment)

Cons:
- cannot PXE boot (I simulate this with boot CD that is always in tray)
- Wake on Lan still doesn't work properly (but can be wrong on this one)...

Asus-fromt.jpg Asus back.jpg


HW clock problem

Digimatrix has nice little vfd screen that shows hardware clock. The problem is that when it is powered off that time is in GMT rather than local time (in my case this is two hours behind). This comes from default handling of time in Linux - HW clock keeps GMT time and software then handles it when powered on. But after powerdown it goes back to GMT.

Solution Entry UTC=yes in /etc/default/rcS (for that particular MD and not on the core) has to be changed to UTC=no.

I have no idea if this breaks any automatic daylight time saving feature or anything else, but works on my Digimatrix now - so I can see proper time when powered off

Adding remote control

It seems pretty straightforward, but I it seems it starts to work only after few hard reboots...

1. Add 'Digimatrix' remote control in the bottom of coresponding entry in Media directors web-admin page. 2. Select 'default' driver

Those actions will add two devices to Digimatrix MD parent device : 'Digimatrix' (remote) and 'default' which will start actual lircd daemon. Now some of buttons should work (left,right,up,down) but not all of them. There is another further step necessary :

3. Setting up remote mapping somewhere (where keys from lircd.conf on Digmatrix remote page have to be added to trigger proper DCE messages) (to be continued)