← Back to team overview

sony-vaio-z-series team mailing list archive

Multi-touch ALPS Touchpad

 

Dear All

There is some discussion on the notebook review forums regarding multi-touch
(ie two-finger zooming and scrolling) capabilty with the ALPS touchpads in
the Vaio Z. I've been reading and I've been trying to get this working under
Ubuntu 10.10 x64 on a VGN-Z590, however, I haven't had much luck yet. Based
on some information on the web I've tried using the pressure reading to
emulate multitouch. Nothing seems to work and I'm not sure if these rules
are working, I cant seem to use the synclient -m 10 to work which seems to
imply the SHMConfig variable isn't being changed. Any help would be greatly
appreciated

I've tried creating a udev rule /etc/udev/rules.d (these seem the be the
replacement for the HAL fdi policy files in the newer ubunutu - but I could
be mistaken)

ACTION!="add|change", GOTO="xorg_local_end"

ATTR{name}=="AlpsPS/2 ALPS GlidePoint",
ENV{x11_options.VertTwoFingerScroll}="1", ENV{x11_options.SHMConfig}="1",
ENV{x11_options.HorizTwoFingerScroll}="1",
ENV{x11_options.EmulateTwoFingerMinW}="7",
ENV{x11_options.EmulateTwoFingerMinZ}="90"

LABEL="xorg_local_end"

And a xml HAL fdi policy in /etc/hal/fdi/policy/


<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.product" string="AlpsPS/2 ALPS GlidePoint">
            <merge key="input.x11_options.VertTwoFingerScroll"
type="string">1</merge>
         <merge key="input.x11_options.SHMConfig" type="string">On</merge>
            <merge key="input.x11_options.HorizTwoFingerScroll"
type="string">1</merge>
            <merge key="input.x11_options.EmulateTwoFingerMinZ"
type="string">90</merge>
    </match>
        <match key="input.x11_driver" string="synaptics">
                <merge key="input.x11_options.SHMConfig"
type="string">True</merge>
        </match>
  </device>
</deviceinfo>

Neither of these methods seem to work. It would be great to have two finger
scrolling working but I can't seem to get it working.

Thanks very much,
Lyle

--
Lyle Gordon
Department of Materials Science and Engineering
Northwestern University

2220 Campus Drive
Evanston, IL 60208

Tel: (847) 491-3584
Mobile: (847) 400-4071
lgordon@xxxxxxxxxxxxxxxxxx


On Tue, Dec 28, 2010 at 3:55 PM, Andreas Wittmann <a_wittmann@xxxxxx> wrote:

> Hi Shai,
>
> you'll find the files attached, hoping this helps...
>
> Andi
>
> Am Sonntag, den 26.12.2010, 11:20 -0800 schrieb
> shairemail-launchpad@xxxxxxxxx:
> > Andreas,
> >
> > Thank you for taking the time to check that out for me.
> >
> > The VPCZ1390x pointing device does work with the 2.6.37.6-vaioz kernel
> without the nopnp switch, so can probably remove it from the kernel
> commandline. However, on my machine, the lspci does not change, and the
> sound still does not work.
> >
> > Currently, here's what I see in my dmesg bootlog that seems audio
> related:
> >
> > [    7.797882] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low)
> -> IRQ 16
> > [    7.797953] HDA Intel 0000:00:1b.0: irq 44 for MSI/MSI-X
> > [    7.797981] HDA Intel 0000:00:1b.0: setting latency timer to 64
> > [    7.904513] hda_codec: ALC889: BIOS auto-probing.
> > [    7.904517] hda_codec: ALC889: SKU not ready 0x411111f0
> > [    7.912850] hda_codec: cannot build controls for #0 (error -16)
> > [    7.913851] input: HDA Intel Headphone as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
> > [    7.932230] pci_raw_set_power_state: 9 callbacks suppressed
> > [    7.932233] HDA Intel 0000:01:00.1: Refused to change power state,
> currently in D3
> >
> > I interpret this as follows:
> >
> > (1) The first three lines are related to the lspci -v lines, which
> describe
> >     00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
> High Definition Audio (rev 05)
> >
> > (2) the hda_codec lines start with:
> >   hda_codec: ALC889: BIOS auto-probing.
> > >From the HDA information in the snd-hda-tools file
> /usr/share/doc/snd-hda-tools/HD-Audio.txt.gz, this is explained as:"
> >     The driver checks PCI SSID and looks through the static configuration
> >    table until any matching entry is found.  If you have a new machine,
> >    you may see a message like below:
> >    --------------------------------------------------------------------
> >        hda_codec: ALC880: BIOS auto-probing.
> >    --------------------------------------------------------------------
> >    Even if you see such a message, DON'T PANIC.  Take a deep breath and
> >    keep your towel.  First of all, it's an informational message, no
> >    warning, no error.  This means that the PCI SSID of your device isn't
> >    listed in the known preset model (white-)list.  But, this doesn't mean
> >    that the driver is broken.  Many codec-drivers provide the automatic
> >    configuration mechanism based on the BIOS setup.
> > "
> > so this audio codec is not currently "known" in driver. The driver seems
> to mess up configuring it.
> >
> > (3) The final 2 lines are pci and HDA Intel errors generated in trying to
> properly power down the nVidia device reported by lspci -v as:
> >     01:00.1 Audio device: nVidia Corporation High Definition Audio
> Controller (rev ff) (prog-if ff)
> >
> > So it seems there are two separate problems:
> >
> > (1) The snd-hda-intel driver isn't managing to configure the audio codec
> correctly. This may be solvable given a sufficiently similar working
> configuration to use as a baseline.
> >
> > (2) The nVidia isn't properly powering down, for some unknown reason.
> >
> > Perhaps you, or someone on the list with working audio on a VPZ13* could
> send me a copy of the /proc/asound/card*/codec* files? these contain the
> "wiring" of the HDA codecs that I would need to try and get my audio
> working.
> >
> > Thanks again,
> > --Shai
> >
> >
> > --- On Sun, 12/26/10, Andreas Wittmann <a_wittmann@xxxxxx> wrote:
> >
> > > From: Andreas Wittmann <a_wittmann@xxxxxx>
> > > Subject: Re: [Sony-vaio-z-series] Vaio VPCZ1390x
> > > To: sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
> > > Date: Sunday, December 26, 2010, 3:12 AM
> > > Hi Shai,
> > >
> > > regarding your sound problem:
> > >
> > > I noticed that using i8042.nopnp=1 with Adam's 2.6.37.6
> > > gives me the
> > > same output of lspci as yours. My sound works anyway
> > > though.
> > >
> > > Booting on stamina without i8042.nopnp results in only the
> > > intel card in
> > > the output of lspci.
> > >
> > > Booting with speed, reboot-kernel first, then 2.6.37.6
> > > gives me intel
> > > and nvidia on lspci, but without "!!! Unknown header type
> > > 7f" on the
> > > nvidia card.
> > >
> > > Maybe just try without i8042.nopnp? Afaik it shouldn't be
> > > needed for
> > > 2.6.37.6 - I'm running fine without.
> > >
> > > Andi
> > >
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
> Post to     : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
> More help   : https://help.launchpad.net/ListHelp
>
>