Puppy Linux Discussion Forum

If you can't get any better advice and feel desperate you could try the following configuration change that may allow your operating system to detect the touch screen differently and add the correct driver (or at least it may offer some different clues to help a step forward):

But please note that if you try this config change there is a high likelihood that your touchpad or mouse will stop working (but if I understand correctly you are not relying a touchpad or mouse anyway...). If this happens you will have to hard power off (hold power button 10 seconds).

Anyway here is the config change:

Open the file /etc/X11/xorg.conf

Have a look at the section labelled:
#*******************************************
#Server flags section
#******************************************

You will probably see the following option:
Option "AutoAddDevices" "false"

Change this to:
Option "AutoAddDevices" "true"

Then save the file.

Now use the main menu to reboot.

Hopefully after the (soft) reboot the system will now detect the touchscreen more appropriately and load the correct driver module (or at least one of the other similar touchscreen drivers) instead of the generic "mouse" driver which is not calibratable.

If possible run lsmod again and see if there are different modules loaded.

Depending on which Puppy you try this config change on you may see the eGalax driver loaded - or instead there may be other drivers (such as evdev or similar) that interface the touchscreen. If eGalax loads then the xinput calibrator (or the TK cli version i posted about) may now help with calibration. Try various Puppies (including older ones like Lupu) with this technique and see what happens.

just logged in, yes, try the last of shinobar's builds first, he usually leaves added bits in, he wouldn't have built specifically for this netbook, we didn't then.

Left hinge of the device unexpectedly broke off into two pieces after your replies came through which has delayed this reply. Screen was hanging off by the display ribbons even. Fortunately superglue has figured it until a more permeant solution can be figured out.

@greengeek As a soft restart is required for your suggestion would it be necessary to install Puppy Linux to the device hard drive?

@scsijon Tried their latest PuppyLinux ISO, Tahrpuppy 5.9.3 (There is 6.0.5 but with something called PAE?). Strangely, not had to run through xorgwizard before but on the desktop the screen seems a lot brighter than other Puppies.

Installed xinput but this did not do anything unfortunately. No worry though will try some more of their ISOs just wanted to give an update.

PiZZa3 wrote: ↑Mon Aug 30, 2021 10:37 pm

@greengeek As a soft restart is required for your suggestion would it be necessary to install Puppy Linux to the device hard drive?

No, it should just restart I believe.
Some module, driver & device detection problems DO require an OS install/restart but often just a soft reboot after xorg.conf changes will suffice.

I seem to recall that there is a difference between kernel drivers (modules?) and xorg drivers (modules?) and that a full shutdown reboot is only necessary for the kernel ones.
(Here is some info about the different input/video/acceleration drivers that are part of xorg:
https://www.linuxfromscratch.org/blfs/v ... river.html
It's just indepth background that won't help you at this stage but gives an idea of what is built into xorg in terms of touchscreen interfacing. Xorg should re-detect input devices via a soft reboot)

So if you can - try the soft reboot after xorg.conf mods and see if there is any change in touchscreen behaviour.

@greengeek Cannot try this fix because the computer keeps saying ".sfs not found dropping out initial ramdisk console" every other boot. Two different USB sticks and two different versions of Puppy. Also having a sudden battery problem. Wits end..

Will try again sometime