Asus T91 linux installation

[Mizukusai]

Great how-to. Thx.
There is 2 Ubuntu Moblin editions (actually 3)
* by Dell, based on jaunty, with a different kernel
* By Ubuntu, based on karmic (no need to say warning : "beta")

I think, you'll be able to make the last one work properly, with this how-to. I'll try it myself.

[Jonathanius]

The brightness scripts aren't working for me in Karmic, here's what I did, maybe I'm making a mistake somewhere:
-created an /etc/acpi/brightness.sh
-pasted in bill's script:

#!/bin/bash

getXdisplay() {
  console=`fgconsole 2> /dev/null`
  DISPLAY=`ps ax | grep -m1 -e "[X] .* vt${console}" | sed -re "s,.*/X .*:([0-9]+).*,:\1,"`
  export DISPLAY
}

getXuser() {
  getXdisplay
  USER=`finger | grep -m1 "${DISPLAY}" | awk '{print $1}'`
  export USER
}

getBrightness() {
  getXuser
  sudo -u ${USER} dbus-send --session --type=method_call --print-reply --dest=org.freedesktop.PowerManagement /org/freedesktop/PowerManagement/Backlight org.freedesktop.PowerManagement.Backlight.GetBrightness | tail -n 1 | grep -ow "[[:digit:]]\+"
}

setBrightness() {
  brn=${1}
  [ ${brn} -ge   0 ] || brn=0
  [ ${brn} -le 100 ] || brn=100
  getXuser
  sudo -u ${USER} dbus-send --session --type=method_call --dest=org.freedesktop.PowerManagement /org/freedesktop/PowerManagement/Backlight org.freedesktop.PowerManagement.Backlight.SetBrightness uint32:${brn}
}

incBrightness() {
  level=`getBrightness`
  if [ ${level} -lt 100 ]; then
    setBrightness $((${level} + 5))
  fi
}

decBrightness() {
  level=`getBrightness`
  if [ ${level} -gt 0 ]; then
    setBrightness $((${level} - 5))
  fi
}

BRIGHTNESS_FILE="/var/lib/acpi-support/brightness"
if [ -f "${BRIGHTNESS_FILE}" ]; then
  BRIGHTNESS_OLD=`cat "${BRIGHTNESS_FILE}"`
fi

BRIGHTNESS_NEW=`echo "${3}" | tr "[a-f]" "[A-F]"`

if [ x"${BRIGHTNESS_OLD}" != x"" ]; then
  if [ x"${BRIGHTNESS_NEW}" = x"${BRIGHTNESS_OLD}" ]; then
    if [ x"${BRIGHTNESS_NEW}" = x"0000002F" ]; then
      incBrightness
    elif [ x"${BRIGHTNESS_NEW}" = x"00000020" ]; then
      decBrightness
    fi
  else
    res=`echo "ibase=16; ${BRIGHTNESS_NEW} > ${BRIGHTNESS_OLD}" | bc`
    [ ${res} -eq 1 ] && incBrightness || decBrightness
  fi
fi

echo "${BRIGHTNESS_NEW}" > "${BRIGHTNESS_FILE}"

-saved and exited
-made executable:

sudo chmod +x /etc/acpi/brightness.sh

-created a /etc/acpi/events/brightness
-paste in:

event=hotkey ATKD 0000002[0-9a-f]
action=/etc/acpi/brightness.sh

-save and exit
-reboot

I did the exact same thing with Leed's, (after deleting /etc/acpi/brightness.sh and /ect/acpi/events/brightness)

I tried:

dbus-send --session --type=method_call --dest=org.freedesktop.PowerManagement /org/freedesktop/PowerManagement/Backlight org.freedesktop.PowerManagement.Backlight.SetBrightness uint32:x

putting numbers between 0 and 100 in place of x, I also tried putting in the hexidecimals 00000020 and 0000002F as they were mentioned in bill's script, when testing leed's both a number that showed in the script (0,30,35...) and the corresponding hexidecimal.

also, I tried executing the following commands:

To increase the brightness:

sudo brightness.sh hotkey ATKD 0000002f

To decrease the brightness:

sudo brightness.sh hotkey ATKD 00000020

but both always returned "command not found " even if i was in the same directory.

There were two other events (with there corresponding .sh files) which I thought might conflict, the events were:
asus-brightness-up:

event=hotkey (ATKD|HOTK) 0000001[0123456789abcdef]
action=/etc/acpi/asus-brn-up.sh

and
asus-brightness-down:

event=hotkey (ATKD|HOTK) 0000002[0123456789abcdef]
action=/etc/acpi/asus-brn-down.sh

the .sh files (asus-brn-down.sh and asus-brn-up.sh):

#!/bin/sh

test -f /usr/share/acpi-support/key-constants || exit 0 
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_BRIGHTNESSDOWN

and

#!/bin/sh

test -f /usr/share/acpi-support/key-constants || exit 0 
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_BRIGHTNESSUP

executing:

acpi_fakekey 224

or

acpi_fakekey 225

had no noticeable effect
So I deleted them, but it still didn't work...

Anyone got any ideas? Is this a Karmic thing, or am I doing it incorrectly?

[davidjany]

Guys, have a look at http://www.ced-network.net/blog/2009...ntu-904jaunty/. It might worth it - but I can't try it:
- Installation Tips (Swap,...)
- Configure simulated right-click
- Configure laptop-mode with Asus's Super Hybrid Engine

I'm using WinXP again, because I wanted to have full-screen writing capabilities, a good virtual keyboard and some other things and could'nt get them quite as good as WinXP with Touch-It Virtual Keyboard and ritePen Pro (all commercial).

I'll switch back to linux when it has the same features...

[Jonathanius]

Hey guys, the davidjany's link (to Cedric's aka cdufour's) blog contained a command which worked to change my brightness:

xrandr --output LVDS0 --set BACKLIGHT x

where x is a number between 100 and 0
...now to make a script that can use it... I tried before to see if the script was triggered by setting the action in the /etc/acpi/events/brightness to launch a script that displayed one of those cool notification things, and the script worked when I executed it directly, but i never got it to launch when a key was pressed, even when trying keys that I knew worked (the rotate button). I don't know any shell so I wasn't surprised. So, could someone who knows what there doing give me a way to test if the event is being triggered? From there concocting a script should be trivial.

[Leed]

Nice work guys, guess I'll check back on that once I switch to Karmic by the End of the month. I read something in the updates, that brightness will be using xrandr. It already works in Jaunty by the way.


Jonathanius
You can type "acpi_listen" in the console to see what the keys trigger

as for the launched script, make sure you have the full path in the command line. The script must also be set as executable... or why not just post your event file

as to see if the script is launched, just place a notify-send command inside the script you want to launch, you don't need to make a new script for it.

[Mizukusai]

Just finished the installation of karmic beta, moblin remix.
Using your instructions. (Thx again!!)

It seems ok but :

Section "DRI"
Mode 0666
EndSection

This section makes Xorg crashes when mutter (moblin interace) starts
I think the problem is that one :

(EE) PSB(0): [dri] DRIScreenInit failed. Disabling DRI.

Without if, Xorg is o, but really really slow.

Any ideas, guys ?

[Jonathanius]

Mizukusai
Personally, I've only ever had crashes when compiz/compositing is on. The Moblin interface is built on Gnome, I believe that in standard Ubuntu Gnome interface, the Extra setting (in the Visual Effects tab of Appearance) uses Compiz - I installed Compiz Settings Manager and played with it a bit to see if I could get it to crash - it did. So, if the Moblin interface uses any fancy graphics it's probably using Compiz as well.
If you have a /usr/bin/compiz file, you need to whitelist psb by adding "psb" to the WHITELIST line.
When I was using Xfce I didn't even have a /usr/bin/compiz, but now that I've switched to Gnome I do. I had the Visual Effects set to "Normal" for a long time and I didn't ever have crash, currently I'm using "None" because when I rotate the screen the refresh rate was horrible.
One more thing, you can try to change the acceleration method from EXA to UXA, it's supposed to be faster and I remember reading that Karmic uses UXA by default now, but I have not tried it yet.

Leed
Thanks for the tip, the acpi_listen thing worked giving me:

hotkey ATKD 00000021 00000005

for brightness down, and

hotkey ATKD 00000022 00000005

for brightness up, note that the number 00000005 corresponds to how many times I have pressed each key. I tried replacing the asus-brightness-up and asus-brightness-down events that posted in last post, with:

event=hotkey ATKD 00000021
action=/etc/acpi/asus-brn-down.sh

in the /etc/acpi/asus-brn-down.sh I simple put:

#!/bin/sh

notify-send -i "/usr/share/icons/gnome/scalable/actions/down.svg", "Brightness" "down"

with identical files for brightness up, only with a different key(in the event) and icon and "up" instead of down(in the script).
But, like last time, if I double click the file or execute it, it does what it supposed to, but doesn't work when the key is pressed.
Any ideas? Thanks so much for all your help so far.

[Mizukusai]

So, if the Moblin interface uses any fancy graphics it's probably using Compiz as well.

I guess not.
I check in "system->pref->appearances". It is written "compiz is not installed".
Maybe I should try this one, and modify the WHITELIST variable.
I's worth the try.

[Mizukusai]

No luck.
Thinking about it, compiz and Mutter may use the same functions (3D accel), but they are different softwares.

[Jonathanius]

@Mizukusai
I started getting quite a few crashes, I'm testing a new config, not sure how stable it is, but will post when I have results. Basically, I disabled compositing in /etc/X11/x.org

Section "Extensions"
        Option "Composite" "off"
EndSection

Still, don't know if it will help...