Puppy Linux Discussion Forum

[Joe Jasniewski]

I really like my Puppy 5.1.1 Linux! However I want to run it on a Toshiba 3500 AND make use of the Wacom pen based touch screen part of this tablet PC.

Now, I have read through many topics, links on the subject and the process seems like veritable HELL for someone at the level of editing an XORG startup file and getting lucky (once).

Also all the information seems to be centered around versions 4.X.X - how about a definitive setup for these machines (Usefull; Tablet.pet) or, step by step instructions for the neophyte.

By neophyte I mean; it's easier for me to just buy a tablet on Ebay with XP tablet already installed. However I hate XP yet want the tablet functionality. I guess the bottom line meaning is that this is worth money...probably to more people than myself!

By neophyte I also mean when I'm instructed to do something in a terminal like

$su
Password:
# xxd /dev/ttyS0

and I get something like BASH - xxd - command not found; I'm DONE at that point. I cant even find if my tablet's Wacom serial device is functional...

Thanks ahead for any assistance I can get with getting Wacom serial Toshiba tablet working on Puppy version 5.X.X! A .pet would be ideal!

Joe

[don570]

I wasn't able to get lupu to work with the wacom bamboo tablet either.

....but I was able to get lupq 5.1.1 to work and it is essentially the same
operating system ( just some locales and languages removed)

http://www.murga-linux.com/puppy/viewtopic.php?t=16491&start=135

http://www.murga-linux.com/puppy/viewtopic.php?search_id=1176557156&t=60199

________________________________________________________

[Joe Jasniewski]

I installed lupq, the suggested .pet and made the corresponding changes to the xorg.conf file to enable the Wacom. It works! ...Sort of...

Cursor tracking to the pen is great in some small areas of the screen, abysmal in others. It always goes to all parts of the screen...eventually. Some coordinates - such as the x-y frame where "plan" and "play" are - work perfectly. Others, such as where "connect" and "quickpet" are - I cant even get the cursor over the icons!

Do I assume my tablet's wacom screen is dead? the unit seems to be in very good shape; Toshiba Portege 3500 with zero scratches on the screen surface!

A pen from a different Toshiba behaves the same way...

How can I further diagnose?

Thanks and best regards,

Joe

[Joe Jasniewski]

I'm stuck on the "xxd" command again. If I could get this to run, I could see if my wacom is spitting out data consistently versus location on the screen.

My best friend Mr bash only says "bash: xxd: command not found"

The guys over at the Wacom Linux suggest using xxd like it's just a common part of the linux system. What do I need to do to get this to work in lupq?

Joe

[don570]

[don570]

An alternate way to create a new xorg.conf file is to delete your current
xorg.conf file and then reboot. The operating system will check
while booting up and run xorgwizard when it finds no file.

_______________________________________________________

[Joe Jasniewski]

Thanks so much for the .pet and assistance. All I did was install the .pet and make the appropriate additions to the xorg.conf file. My 3500 system had hardware issues which many of these do. Fixing it involved removing the screen bezel, the screen and wiggling / jiggling these small flat ribbon cables going to the Wacom board, which is affixed to the back of the LCD assy. The pen started responding smoothly at all parts of the screen after doing this!

Now I have a working tablet with lupq! Yay!

Unfortunately, the internal wireless has problems with lupq 5.1.1, as well as lupo 5.1.1. 4.3.1 it comes up immediately and every time. 5.1.1 I can get it sometimes, but on reboot it's lost again and often I cant get it back up at all.

I suppose something was done to improve the apparent lag in getting connected, to the detriment of slower hardware like this PIII machine. I'm asking about it in another thread.

Will the same .pet work in 4.3.1? I may be limited to it because of the wireless problem!

Thanks again!

Joe

[don570]

Is the tablet pressure sensitive? Test it with gimp.
Download gimp (this is just available from playdayz)
http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet-packages-lucid/Gimp-2.6.10-Lucid.pet

If you think puppy 4.3.1 is a better choice, then
I would recommend lighthouse 4.43 which is the exact same as 4.3.1
but has more apps pre-installed. It's easy to install the wacom
driver on it.
http://murga-linux.com/puppy/viewtopic.php?search_id=2040489355&t=47588

If you're more adventurous try lighthouse 5 . I was able to get the
wacom driver to install on it as well.


Just last night I was able to install the newest wacom driver on luci233
which is the beta of lucid puppy 5.2. The method I used was the same as
I described in the above post. So if you have the time try it out and report on
the thread
http://www.murga-linux.com/puppy/viewtopic.php?t=16491&search_id=149121592&start=150

______________________________________________________

[Joe Jasniewski]

I'm a bit disappointed. Maybe easy for you? But I used the same .pet as before, with the 5.1.1. I changed the xorg.conf to: [below] and the pen no longer works. Please help, as I'm lost at this point.

Thanks and best regards,

Joe

#Special base config file used in Puppy Linux.

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
Load "synaptics"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
Load "type1"
Load "freetype"

# This loads xtrap extension, used by xrandr
Load "xtrap"

# This loads the GLX module (if present)
Load "glx"

# This loads dri module (if present)
Load "dri"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R7/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

FontPath "/usr/X11R7/lib/X11/fonts/misc/"
FontPath "/usr/X11R7/lib/X11/fonts/Type1/"
FontPath "/usr/X11R7/lib/X11/fonts/TTF/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...

Option "RandR" "on"

EndSection

#everything past here is auto-generated by Puppy's Xorg Wizard...


Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "cursor" "SendCoreEvents"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "InputDevice"
Identifier "Synaptics Mouse"
Driver "synaptics"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "LeftEdge" "120"
Option "RightEdge" "930"
Option "TopEdge" "120"
Option "BottomEdge" "650"
Option "FingerLow" "14"
Option "FingerHigh" "15"
Option "MaxTapTime" "0"
Option "MaxTapMove" "110"
Option "VertScrollDelta" "20"
Option "MinSpeed" "0.3"
Option "MaxSpeed" "0.75"
Option "AccelFactor" "0.030"
Option "EdgeMotionMinSpeed" "200"
Option "EdgeMotionMaxSpeed" "200"
Option "UpDownScrolling" "1"
Option "CircularScrolling" "1"
Option "CircScrollDelta" "0.1"
Option "CircScrollTrigger" "2"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/ttyS0"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"
Option "Button2" "3"
Option "CursorProx" "256"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0"
Option "Type" "stylus"
Option "PressCurve" "50,0,100,50"
Option "ForceDevice" "ISDV4"
Option "Button2" "3"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/ttyS0"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"
Option "Button2" "3"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 31.5-48.5
VertRefresh 40-70
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection

Section "Monitor"
#DisplaySize 240 180 # mm
Identifier "Monitor0"
VendorName "TOS"
ModelName ""
Option "DPMS"
HorizSync 31.5-48.5
VertRefresh 40-70
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1024x768"
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "AccelMethod" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "PciRetry" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "SetMClk" # <freq>
#Option "MUXThreshold" # <i>
#Option "ShadowFB" # [<bool>]
#Option "Rotate" # [<str>]
#Option "VideoKey" # <i>
#Option "NoMMIO" # [<bool>]
#Option "NoPciBurst" # [<bool>]
#Option "MMIOonly" # [<bool>]
#Option "CyberShadow" # [<bool>]
#Option "CyberStretch" # [<bool>]
#Option "XvHsync" # <i>
#Option "XvVsync" # <i>
#Option "XvBskew" # <i>
#Option "XvRskew" # <i>
#Option "FpDelay" # <i>
#Option "Display1400" # [<bool>]
#Option "Display" # [<str>]
#Option "GammaBrightness" # [<str>]
#Option "TVChipset" # [<str>]
#Option "TVSignal" # <i>
Identifier "Card0"
Driver "trident" #card0driver
VendorName "Trident Microsystems"
BoardName "CyberBlade XPAi1"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubsection
EndSection

#PuppyHardwareProfile=Trident_CYBER_8820TOSHIBAInte

[don570]

Note to Joe Jasniewski

It seems like wacom-0.8.4-4_xorg_driver.pet is
the only version that will work with Puppy 4.3.1

It's easy to install drivers in Puppy 4.3.1
because it has a 'ServerLayout' section.

Download
http://www.browserloadofcoolness.com/software/puppy/PETget/wacom/wacom-0.8.4-4_xorg_driver.pet

[Frank Cox]

[don570]

Joe Jasniewski replied to me that he could get
Lucid Puppy QuickSet (lupq) to
run properly.. at least the stylus moved properly.

But he didn't reply back about Puppy 4.3.1

....but I don't see why not. However when I looked at his
xorg.conf file it was radically different from mine.
Tablet PCs are obviously very complex and they need a more
detailed xorg.conf . That subject is not something I know much about.
Sorry.

Best of Luck.

[Frank Cox]

[Frank Cox]

I have had no trouble getting my Gateway M275 Tablet working in Lubuntu 9,10, or 11 but never Puppy 431.