Toshiba Satellite T215D

[Rich]

Hi MikeLockmoore
And the Xorg.0.log file doesn't report trying to load the Synaptics  driver or why it failed?

[MikeLockmoore]

Rich: Short answer: no.  The Xorg log file does not mention synaptics or touchpad at all. (Copy of it is attached).  However, I do see the touchpad in /proc/bus/input/devices:

Code: [Select]

...
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse0 event5
B: PROP=9
B: EV=b
B: KEY=6420 0 30000 0 0 0 0 0 0 0 0
B: ABS=2608000 11000003
...

Here is the output of xinput:

Code: [Select]

Virtual core pointer                    id=2 [master pointer  (3)]
Virtual core XTEST pointer              id=4 [slave  pointer  (2)]
<default pointer>                        id=6 [slave  pointer  (2)]
Virtual core keyboard                    id=3 [master keyboard (2)]
Virtual core XTEST keyboard              id=5 [slave  keyboard (3)]
<default keyboard>                      id=7 [slave  keyboard (3)]

This is all from a session where I booted with no external mouse... and the touchpad is working in the basic mouse-emulation mode.

My /usr/local/share/X11/xorg.conf.d contains:

Code: [Select]

10-evdev.conf
10-quirks.conf
50-fpit.conf
50-synaptics.conf
50-vmmouse.conf
50-wacom.conf

10-evdev.conf contains:

Code: [Select]

#
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

50-synaptics.conf contains:

Code: [Select]

Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
EndSection


# Quirks for special touchpads

# Some devices have the buttons as part of the lower edge of the
# touchpad.  Pressing a button moves the cursor, causing cursor jumps and
# erroneous clicks.
# Use the synaptics area property to work around this, udev labels these
# devices for us as touchpad_button_overlap.
# Affected: Dell Mini
Section "InputClass"
        Identifier "touchpad button overlap"
        MatchIsTouchpad "on"
        MatchTag "touchpad_button_overlap"
        Option "AreaBottomEdge" "4000"
EndSection

Ideas of extra things to try or check would be appreciated.

[Rich]

Hi MikeLockmoore
Personally I find this Xorg stuff confusing, so all I can offer is a few observations.
The log file indicates that Xorg is aware of the  /usr/local/share/X11/xorg.conf.d  directory, but don't you need to tell it
to use one or more of those files?
Alternatively, maybe you need to copy the contents of those files to xorg.conf, since the syntax appears to be the same.
I also notice that  evdev  is not mentioned in the log file, but is listed as driver in 10-evdev.conf. Just a shot in the dark,
but maybe adding the following to xorg.conf will help, or at least provide more information in the log file.

Code: [Select]

Section "InputClass"
        Identifier "evdev touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
EndSectionIt may try to act on one or both sections and then lodge its complaints in the log file.

[MikeLockmoore]

Rich: I understand "conf-less" Xorg 7.6 tries to self-configure, but if it detects certain devices, it will check for a matching configuration element stored in a file in the ... /xorg.conf.d directory and use it.  Somehow, the Xorg 7.6 self-configuration in my installation of Tiny Core does not seem to "see" the touchpad as a touchpad and configure it according to the 50-synaptics.conf file, but in Fedora it does.

I tried to use your example.  It still does not load the synaptics driver for the touchpad.  The only significant difference in the Xorg.0.log file is that the log shows that Xorg is "using" the xorg.conf file.  Maybe a complete xorg.conf that has all the sections would work, but I don't have one that would be compatible with Xorg 7.6.  My Fedora installation is conf-less and generating an xorg.conf file in Fedora (using Xorg :1 -configure) resulted in a xorg.conf that did not refer to the touchpad either. 

Thanks for a suggestion, but I think there is still a missing piece to this puzzle.

EDIT:  My Xorg.0.log file in TC has lines like this:
[    20.486] (==) Not automatically adding devices
[    20.486] (==) Not automatically enabling devices


But my Xorg.0.log file in Fedora has lines like this:
[    26.165] (==) Automatically adding devices
[    26.165] (==) Automatically enabling devices

WHY??? 

[Rich]

Hi MikeLockmoore
I found the following at this wiki  http://en.gentoo-wiki.com/wiki/Synaptics_Touchpad

Code: [Select]

Section "InputDevice"
    Driver         "synaptics"
    Identifier "TouchPad"
    Option         "SendCoreEvents"
    Option         "Protocol" "auto-dev"
    Option         "SHMConfig" "on"
 EndSectionThey also give the following advice:

If you use a mouse in parallel, you should only have one "CorePointer". For the other device put "SendCoreEvents". Add an input device section for the touchpad:

[MikeLockmoore]

Rich:  I think I tried experimenting with the SendCoreEvents adn CorePointer attributes but did not come up with a combo that worked in TC 4.3 in Xorg or Xvesa.

All: Created a Tiny Core 4.4 installation on the Toshiba.  Replaced all my kernel -3.0.3- specific extensions with their -3.0.21- counterparts, and updated all the other extensions using AppsAudit (not many).  Xvesa worked the same as before: no 1366x768 graphics mode.  915resolution.tcz did not help.  Xorg 7.6 works with the VESA driver, but now the Xorg-7.6-3d extension does not work, just get a black screen.  Same for the Xorg 7.5 and the Xorg-7.5-3d combo.  I think sound is problematic too.

Seems like Tiny Core 3.8 is the best option for this Toshiba T215.