Asus T91 linux installation

[kgingeri]

Hi kgingeri,
just out of interest what is the output of this command for you?

cat /proc/asound/version

i get

Advanced Linux Sound Architecture Driver Version 1.0.21.
Compiled on Dec 2 2009 for kernel 2.6.31-16-generic (SMP).

so it may be that you need to upgrade alsa, this will install the latest alsa

sudo add-apt-repository ppa:ricotz/unstable

sudo apt-get update && sudo apt-get upgrade

thanks to http://www.webupd8.org/2009/11/ubunt...1021-from.html
for the alsa instructions.

Sorry it wasn't working for you, as i said earlier i had been messing with the sound settings etc for a while before i got it working, thanks for the feedback, i'm considering doing another fresh install to figure out the exact steps i took. Let me know if the alsa upgrade makes any difference.

SWEET - it works fine after the ALSA upgrade!!!

here's my output - but I didn't even run pavucontrol after the upgrade.

Advanced Linux Sound Architecture Driver Version 1.0.21.
Compiled on Dec 11 2009 for kernel 2.6.31-17-generic (SMP).

Thanks James!!

[kgingeri]

I still have a few annoying things that don't work with my T91MT and UNR:

1. hangs when using the touch screen - only Alt-PrtSc+R+E+I+S+U+B gets me rebooted
2. I have to press the Fn+F2 to start wireless after every reboot - i've tried several things in rc.local to no avail.
3. brightness keys don't work (Fn+F3/F4) - xev doesn't even see them
4. can't assign the button under the screen (next to power) - no xev events here either

Is anyone else seeing any of these, or more importantly, any suggested work-arounds/fixes?!

EDIT: re the brightness keys - scripts in /etc/acpi don't line up with my system config - stuff they check for is either not found or in different places under /proc etc

[kgingeri]

Hey I got multi-touch working by install this fdi file and restarting, then going to System Prefs -> Mouse and clicking scrolling settings (these had no effect previously)

I don't have it working for the screen yet tho :/

UPDATE:
Not sure what happened to my attachments so I've attached both modified fdi files. Remove ".txt" and place in /usr/share/hal/fdi/policy/20thirdparty

EDIT: PLEASE NOTE! this is for the touchpad only

[jamespcole]

Thanks James!!

awesome glad it worked, still not sure if it was just the alsa upgrade or a combo of that and the backports though. did you remove the backports stuff before the alsa upgrade?

Either way i'll update my blog entry, i think i might do a fresh install next week to isolate the exact steps anyway.

[jamespcole]

I still have a few annoying things that don't work with my T91MT and UNR:

1. hangs when using the touch screen - only Alt-PrtSc+R+E+I+S+U+B gets me rebooted
2. I have to press the Fn+F2 to start wireless after every reboot - i've tried several things in rc.local to no avail.
3. brightness keys don't work (Fn+F3/F4) - xev doesn't even see them
4. can't assign the button under the screen (next to power) - no xev events here either

Is anyone else seeing any of these, or more importantly, any suggested work-arounds/fixes?!

EDIT: re the brightness keys - scripts in /etc/acpi don't line up with my system config - stuff they check for is either not found or in different places under /proc etc

In regards to number 4 i am using that to rotate the screen. to find out how check out this guy's blog, it's for 9.04 but the screen rotation is working for me.

http://www.ced-network.net/blog/2009...ntu-904jaunty/

From the blog

In order for ACPI to recognize the screen rotation button of the T91, you will need to add a new button configuration file:

/etc/acpi/events/asus-rotate-t91

event=hotkey (ATKD|HOTK) 0000007b
action=/etc/acpi/rotatescreen.sh
You may also want to edit the /etc/acpi/rotatescreen.sh script to rotate the screen to the left rather than from the (default) right.
You must restart /etc/init.d/acpid for that change to become effective.

as for the other stuff, yep it's happening to me too. The one that bothers me the most is the random crashes. The most annoying thing about it is that it just stops and i can't get any info on the error. If you find any solutions let me know because it's really annoying.

I am not experiencing the problem you mentioned with the wireless, it is enabled and on when i boot up.

[kgingeri]

Wow, the rotate trick was easy!!
Created the two line file and did a "# restart acpid" and it's live.
(Actually I think I prefer the right to left rotation, but the jury is still out on it )

As for my process to correct the mic in Skype; I didn't uninstall anything - just did the backports (it re-did grub and a bunch of stuff - if I remember right) and then the alsa upgrade as you outlined.

Thanks again James!!

[kgingeri]

James and others,

I've been trying also to find some log events or something on the freezes. It is evtouch, I'm very sure - I can run all day without using the touch screen. It doesn't matter what program I'm in and I have found no pattern other than maybe when you are dragging - scroll-bars, selections etc?

I wonder if there are anymore alternatives to the evtouch mods. I did find one called plpevtch, but no luck compiling yet. I did take a quick look at the source, but I'd have to get my 'head into it' to be able to check for mem leaks etc. I thought I might take debug stuff out as that may be a mem leak potential - certainly not necessary for functionality.

The freezes are one of the main ones I'm working on. I keep this thread up to date if I find a fix!

EDIT: The plpevtch stuff complains that xorg-server xproto and kbproto are not installed - when I try the "./configure --prefix=/usr" cmd

[jamespcole]

yeah i had figured it was something evtouch related, i've had the same problem on other touch screens too(WiBrain BL1) without finding a solution.

BTW another useful tip in the blog i mentioned earlier is the making a single click followed by a long click == to a right click. It makes using the touchscreen heaps easier and it definitely works on 9.10.

Thanks for the feedback, i'll look into the evtouch issue too, between us i'm sure we can figure something out.

Just out of interest has anyone got a way to consistently reproduce the bug? I can't figure out a way to crash it, it just seems to be random but it'll be a lot easier to test fixes if we can reproduce the bug at will.

[kgingeri]

...
BTW another useful tip in the blog i mentioned earlier is the making a single click followed by a long click == to a right click. It makes using the touchscreen heaps easier and it definitely works on 9.10.
...

Yeah, saw this one James, but can't get it to work. I have put everything in xorg.conf, and that may be why. I still don't understand the relationship of fdi files to devices for xorg yet. I need to play with it some more.

I currently have a udev rule file to create a sym link (I have seen the touchscreen on either event5 or event6 so hardcoding them isnt the best) for the /dev/input/event<n> device and then my xorg.conf section is as follows:

$ tail /etc/udev/rules.d/69-touchscreen.rules 

# Elo Touchscreen
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="04e7", ATTRS{idProduct}=="0020", SYMLINK+="input/evtouch_event"
#
# Asus multitouch & buttons 
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0486", ATTRS{idProduct}=="0185", SYMLINK+="input/asus_touchscreen_event"
# NOTE: the following never does register - proc/..devices report Vendor:Prod of 0000:0000!?
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="0B05", ATTRS{idProduct}=="B703", SYMLINK+="input/asus_buttons_event"
#

CSection "InputDevice"
    Identifier  "touchscreen"
    Driver      "evtouch"
    Option      "Device"                "/dev/input/asus_touchscreen_event"
                # ...set mod'd /etc/udev/rules.d/69-touchscreen.rules
    Option      "DeviceName"            "touchscreen"
    Option      "MinX"                  "0"
    Option      "MinY"                  "0"
    Option      "MaxX"                  "3475"
    Option      "MaxY"                  "3475"
    Option      "ReportingMode"         "Raw"
    Option      "SendCoreEvents"        "On"
    Option      "taptimer"              "200" 
    Option      "movelimit"             "15" 
    Option      "Emulate3Buttons"       "true"
    Option      "Emulate3Timeout"       "50"
    Option      "longtouchtimer"         "400" 
#    Option     "touched_button"        "1" 
#    Option     "touched_action"        "down"
    Option      "longtouched_button"    "3" 
    Option      "longtouched_action"    "down"
    Option      "oneandahalftap_button" "2" 
    Option      "oneandahalftap_action" "down"
    Option      "Calibrate"             "0"
EndSection

so how does an fdi associate to my /dev/input/asus_touchscreen_event device - through the evtouch driver? Anyway, none of the long or oneandahalf (short-then-held) clicks work.

My custom fdi is:

cat 10-asustouchscreen.fdi 

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->

<deviceinfo version="0.2">
  <device>
    <match key="info.name" contains="Asus">
      <match key="info.capabilities" contains="input.touchpad">
        <merge key="input.x11_options.taptimer" type="string">200</merge>
        <merge key="input.x11_options.movelimit" type="string">15</merge>
        <merge key="input.x11_options.emulate3buttons" type="string">true</merge>
        <merge key="input.x11_options.emulate3timeout" type="string">50</merge>
        <merge key="input.x11_options.longtouchtimer" type="string">400</merge>
        <merge key="input.x11_options.longtouched_action" type="string">down</merge>
        <merge key="input.x11_options.longtouched_button" type="string">1</merge>
        <merge key="input.x11_options.oneandahalftap_action" type="string">click</merge>
        <merge key="input.x11_options.oneandahalftap_button" type="string">3</merge>
        <merge key="input.x11_options.minx" type="string">0</merge>
        <merge key="input.x11_options.miny" type="string">0</merge>
        <merge key="input.x11_options.maxx" type="string">3475</merge>
        <merge key="input.x11_options.maxy" type="string">3475</merge>
      </match>
    </match>
  </device>
</deviceinfo>

This ISN'T in place at the moment. I believe it is BEST to have only a fdi or xorg.conf define params - not both.

and finally (did I do this all backwards?!)... /proc/bus/input/device Asus info is:

I: Bus=0003 Vendor=0486 Product=0185 Version=0100
N: Name="AsusTek, Inc. MultiTouch"
P: Phys=usb-0000:00:1d.2-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input6
U: Uniq=
H: Handlers=mouse2 event6 
B: EV=1b
B: KEY=403 0 30003 0 0 0 0 0 0 0 0
B: ABS=ffffff00 100003f
B: MSC=10

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Asus EeePC extra buttons"
P: Phys=eeepc/input0
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=rfkill kbd event7 
B: EV=3
B: KEY=100000 0 0 0 400b 400 0 1300000 e0000 0 0 0

EDIT: I forgot my xinput info, so doing a "$ xinput list --short" I get

"Virtual core pointer"	id=0	[XPointer]
"Virtual core keyboard"	id=1	[XKeyboard]
"touchscreen"	id=2	[XExtensionPointer]
"touchscreen"	id=3	[XExtensionPointer]
"Asus EeePC extra buttons"	id=4	[XExtensionKeyboard]
"USB 2.0 Camera"	id=5	[XExtensionKeyboard]
"Sleep Button"	id=6	[XExtensionKeyboard]
"Power Button"	id=7	[XExtensionKeyboard]
"AT Translated Set 2 keyboard"	id=8	[XExtensionKeyboard]
"Macintosh mouse button emulation"	id=9	[XExtensionPointer]
"SynPS/2 Synaptics TouchPad"	id=10	[XExtensionPointer]
"Microsoft Compact Optical Mouse 500"	id=11	[XExtensionPointer]

I only get the cursor jumping to the bottom right if I try using the touchscreen. I'm gonna fiddle some more...

[kgingeri]

Tried the fdi file again with none of the params in xorg.conf but no luck :v(

At least xorg.conf is working for me - just the long clicks do seem to register.

Interesting tho - it seems (see below) it is defaulting to Synaptics instead of evtouch - hmmmm - may have to play a little more with it...(from /var/log/Xorg.0.log)

...
(II) config/hal: Adding input device AsusTek, Inc. MultiTouch
(II) Synaptics touchpad driver version 1.1.2
(**) Option "Device" "/dev/input/event6"
(**) Option "SHMConfig" "On" 
(**) Option "EmulateTwoFingerMinZ" "40" 
(**) Option "VertTwoFingerScroll" "1"
(**) Option "HorizTwoFingerScroll" "1"
(**) Option "TapButton1" "1"
(**) Option "TapButton2" "3"
(**) Option "TapButton3" "2"
(--) AsusTek, Inc. MultiTouch: no supported touchpad found
(EE) AsusTek, Inc. MultiTouch Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "AsusTek, Inc. MultiTouch"
(II) UnloadModule: "synaptics"
(EE) config/hal: NewInputDeviceRequest failed (8)
...