Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-10 Thread Florian Zieboll via Dng
On Sun, 7 Feb 2021 16:52:51 +0100
Florian Zieboll via Dng  wrote:

> I will leave the 'xinput' sources where they are and rather use some
> spare time to see if I can can get any useful information out of
> 'gdb'. If I succeed, I promise to report to the list



For the record, here the diff of gdb's (uniq'ed) output for enabling
resp. disabling my pointing device:


$ diff gdb_0-1.txt gdb_1-0.txt 
2c2
< Starting program: /usr/bin/xinput --set-prop 10 148 1
---
> Starting program: /usr/bin/xinput --set-prop 10 148 0
526c526
< __GI_atoi (nptr=0x7fffe4b4 "1") at atoi.c:27
---
> __GI_atoi (nptr=0x7fffe4b4 "0") at atoi.c:27
528c528
< __strtol (nptr=0x7fffe4b4 "1", endptr=endptr@entry=0x0, 
base=base@entry=10) at ../stdlib/strtol.c:106
---
> __strtol (nptr=0x7fffe4b4 "0", endptr=endptr@entry=0x0, 
> base=base@entry=10) at ../stdlib/strtol.c:106
530c530
< __GI_strtol_l_internal (nptr=0x7fffe4b4 "1", endptr=endptr@entry=0x0, 
base=base@entry=10, group=group@entry=0, loc=0x77825560 
<_nl_global_locale>) at ../stdlib/strtol_l.c:252
---
> __GI_strtol_l_internal (nptr=0x7fffe4b4 "0", endptr=endptr@entry=0x0, 
> base=base@entry=10, group=group@entry=0, loc=0x77825560 
> <_nl_global_locale>) at ../stdlib/strtol_l.c:252
771c771
< [Inferior 1 (process 18243) exited normally]
---
> [Inferior 1 (process 18210) exited normally] 


So Steve has been proven right, that 'xinput' acts directly on the RAM
- at least for my precious trackball -_- 

libre Grüße,
Florian

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-08 Thread Olaf Meeuwissen via Dng
Hi Didier, list,

Didier Kryn writes:

> Le 07/02/2021 à 16:27, Hendrik Boom a écrit:
>> I've had boot-to-boot persistence of a different setting -- for my wifi
>> device.  Ony it wasn't the device with the memory, it was the BIOS.  The
>> effect was very similar, though.
>>
>> When I entered an area where wifi was forbidden I turned off my laptop's
>> wifi using my OS's tool for doing so.
>>
>> The next time I turned on my laptop I couldn't turn it on again with
>> that tool.
>>
>> It turned out that my OS had turned off the wifi by changing a
>> BIOS-level setting, and when I turned it on the bios told the OS there
>> was no such device when it tried to turn it on again.
>>
>> Frustrating until I figured out I had to use the BIOS to turn it on
>> again.
>
> On my "Elitebook" (and on my previous "Latitude") there is (was) a hard
> button to toggle the wifi on/off.

Same thing on my Libreboot T400 (refurbished Lenovo T400).  Real nice to
have a physical kill switch if you want to turn of WiFi in a hurry.

> I'm surprised manufacturers hide this functionality in a BIOS menu.

Doing so via a BIOS menu is a bit cumbersome to say the least.  Perhaps
the `rfkill` package can help if you don't have a physical kill switch.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-08 Thread Rick Moen
Quoting Steve Litt (sl...@troubleshooters.com):
> On Sat, 6 Feb 2021 22:40:36 +0100
> Florian Zieboll via Dng  wrote:

> > libre Grüße,
> 
> And don't bring me down Bruce!
> 
> If you don't get the reference, that's OK, you need to be over 60 to
> get it.

I skipped that decade's pop music -- but, for the (33 1/3 rpm
long-playing vinyl album-rock) record:
https://ultimateclassicrock.com/electric-light-orchestra-dont-bring-me-down-bruce/

-- 
Cheers, "2021 showed up, and told 2020 'hold my beer.'"
Rick Moen   -- @justinaireland
r...@linuxmafia.com
McQ! (4x80)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-08 Thread Didier Kryn
Le 07/02/2021 à 16:27, Hendrik Boom a écrit :
> I've had boot-to-boot persistence of a different setting -- for my wifi 
> device.  Ony it wasn't the device with the memory, it was the BIOS.  The 
> effect was very similar, though.
>
> When I entered an area where wifi was forbidden I turned off my laptop's 
> wifi using my OS's tool for doing so.
>
> The next time I turned on my laptop I couldn't turn it on again with 
> that tool.
>
> It turned out that my OS had turned off the wifi by changing a 
> BIOS-level setting, and when I turned it on the bios told the OS there 
> was no such device when it tried to turn it on again.
>
> Frustrating until I figured out I had to use the BIOS to turn it on 
> again.

On my "Elitebook" (and on my previous "Latitude") there is (was) a hard
button to toggle the wifi on/off.

I'm surprised manufacturers hide this functionality in a BIOS menu.

--     Didier


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-07 Thread Florian Zieboll via Dng
Am 7. Februar 2021 14:45:22 MEZ schrieb Steve Litt
:
> On Sat, 6 Feb 2021 22:40:36 +0100
> Florian Zieboll via Dng  wrote:
> 
> > Supposing that "somewhere in xorg" means "under '/etc/X11/' or
> > under '/usr/share/X11/'", a configuration change definitely  would
> > not endure booting into another OS; under '/proc/' it wouldn't even
> > survive a reboot (would it even persist over a runlevel change
> > there?!). 
> 
> Hi Florian,
> 
> I meant stored in memory by xorg. I have no knowledge one way or
> another about boot-to-boot persistence of touchpad settings. My main
> point was a practical one: Whatever your touchpad's settings are, you
> can toggle it on and off with my script.
> 
> > 
> > The only possibility (which is accessible from within Linux and does
> > not require a "stateful" touchpad) coming to my mind to make such a
> > configuration persistent over a reboot AND across different OSes,
> > might be under '/sys/firmware/efi/' - which would presume a UEFI
> > system. 
> > 
> > I am seriously curious about more opinions on this!
> 
> I can tell.
> 
> Like I said, I have no knowledge about boot-to-boot persistence, but
> if I were just taking wild guesses, I'd guess that the touchpad
> itself has some non-volatile RAM to store its settings, and the OS,
> when it boots, reads those settings.
> 
> Keep in mind I've never noticed boot-to-boot persistence. In fact, if
> I remember correctly, my laptops have always booted up to a fully
> functional touchpad, which I had to suppress most of the time with my
> shellscript.
>  
> > libre Grüße,
> 
> And don't bring me down Bruce!
> 
> If you don't get the reference, that's OK, you need to be over 60 to
> get it.
> 
> SteveT



Hallo Steve,

thanks for your reply! As I am not yet even near 60 years old, I don't
get the reference. But I am old enough to sense, that I probably won't
get much deeper into C programming anymore, than wrapping shell commands
into the 'system()' function to make them setuid'able. Thus, I will
leave the 'xinput' sources where they are and rather use some spare
time to see if I can can get any useful information out of 'gdb'. If I
succeed, I promise to report to the list - although I don't own a
device with touchpad (which most likely would be the second thing to
permanently disable immediately - right after the system sounds, if my
OS had those preconfigured). 

Libre Grüße and best regards,
Florian


--
Together we stand - united we fall.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-07 Thread Hendrik Boom
On Sun, Feb 07, 2021 at 08:45:22AM -0500, Steve Litt wrote:
> On Sat, 6 Feb 2021 22:40:36 +0100
> Florian Zieboll via Dng  wrote:
> 
> > Supposing that "somewhere in xorg" means "under '/etc/X11/' or under 
> > '/usr/share/X11/'", a configuration change definitely  would not
> > endure booting into another OS; under '/proc/' it wouldn't even
> > survive a reboot (would it even persist over a runlevel change
> > there?!). 
> 
> Hi Florian,
> 
> I meant stored in memory by xorg. I have no knowledge one way or
> another about boot-to-boot persistence of touchpad settings. My main
> point was a practical one: Whatever your touchpad's settings are, you
> can toggle it on and off with my script.
> 
> > 
> > The only possibility (which is accessible from within Linux and does
> > not require a "stateful" touchpad) coming to my mind to make such a
> > configuration persistent over a reboot AND across different OSes,
> > might be under '/sys/firmware/efi/' - which would presume a UEFI
> > system. 
> > 
> > I am seriously curious about more opinions on this!
> 
> I can tell.
> 
> Like I said, I have no knowledge about boot-to-boot persistence, but if
> I were just taking wild guesses, I'd guess that the touchpad itself has
> some non-volatile RAM to store its settings, and the OS, when it boots,
> reads those settings.
> 
> Keep in mind I've never noticed boot-to-boot persistence. In fact, if I
> remember correctly, my laptops have always booted up to a fully
> functional touchpad, which I had to suppress most of the time with my
> shellscript.

I've had boot-to-boot persistence of a different setting -- for my wifi 
device.  Ony it wasn't the device with the memory, it was the BIOS.  The 
effect was very similar, though.

When I entered an area where wifi was forbidden I turned off my laptop's 
wifi using my OS's tool for doing so.

The next time I turned on my laptop I couldn't turn it on again with 
that tool.

It turned out that my OS had turned off the wifi by changing a 
BIOS-level setting, and when I turned it on the bios told the OS there 
was no such device when it tried to turn it on again.

Frustrating until I figured out I had to use the BIOS to turn it on 
again.

-- hendrik

>  
> > libre Grüße,
> 
> And don't bring me down Bruce!
> 
> If you don't get the reference, that's OK, you need to be over 60 to
> get it.
> 
> SteveT
> 
> Steve Litt 
> Autumn 2020 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/thrive
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-07 Thread Steve Litt
On Sat, 6 Feb 2021 22:40:36 +0100
Florian Zieboll via Dng  wrote:

> Supposing that "somewhere in xorg" means "under '/etc/X11/' or under 
> '/usr/share/X11/'", a configuration change definitely  would not
> endure booting into another OS; under '/proc/' it wouldn't even
> survive a reboot (would it even persist over a runlevel change
> there?!). 

Hi Florian,

I meant stored in memory by xorg. I have no knowledge one way or
another about boot-to-boot persistence of touchpad settings. My main
point was a practical one: Whatever your touchpad's settings are, you
can toggle it on and off with my script.

> 
> The only possibility (which is accessible from within Linux and does
> not require a "stateful" touchpad) coming to my mind to make such a
> configuration persistent over a reboot AND across different OSes,
> might be under '/sys/firmware/efi/' - which would presume a UEFI
> system. 
> 
> I am seriously curious about more opinions on this!

I can tell.

Like I said, I have no knowledge about boot-to-boot persistence, but if
I were just taking wild guesses, I'd guess that the touchpad itself has
some non-volatile RAM to store its settings, and the OS, when it boots,
reads those settings.

Keep in mind I've never noticed boot-to-boot persistence. In fact, if I
remember correctly, my laptops have always booted up to a fully
functional touchpad, which I had to suppress most of the time with my
shellscript.
 
> libre Grüße,

And don't bring me down Bruce!

If you don't get the reference, that's OK, you need to be over 60 to
get it.

SteveT

Steve Litt 
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-06 Thread Florian Zieboll via Dng
Am 6. Februar 2021 20:10:58 MEZ schrieb Steve Litt
:
> On Sat, 6 Feb 2021 15:09:33 +0100
> Florian Zieboll  wrote:
> 
> 
> > 
> > Hallo Steve,
> > 
> > after having had a look at your script and the 'xinput' manpage, I
> > still don't understand, where the information about the device's
> > state is stored. 
> 
> I assume it's stored somewhere in xorg.
> 
> > 
> > As the current state is preserved between different operating
> > systems: Do I assume correctly, that the touchpad is
> > "stateful" (enabled | disabled) and replacing a disabled one with
> > an identical one from another computer (where it had not been
> > disabled) would restore its functionality?
> 
> You're asking questions beyond my knowledge, but no matter what the
> state, you can always change it. You don't need to replace the
> touchpad. 
> Steve


Supposing that "somewhere in xorg" means "under '/etc/X11/' or under 
'/usr/share/X11/'", a configuration change definitely  would not endure
booting into another OS; under '/proc/' it wouldn't even survive a
reboot (would it even persist over a runlevel change there?!). 

The only possibility (which is accessible from within Linux and does
not require a "stateful" touchpad) coming to my mind to make such a
configuration persistent over a reboot AND across different OSes, might
be under '/sys/firmware/efi/' - which would presume a UEFI system. 

I am seriously curious about more opinions on this!


NB: Of course, the idea of swapping hardware was only meant to
illustrate the term "stateful".


libre Grüße,
Florian

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-06 Thread Florian Zieboll via Dng
On Fri, 5 Feb 2021 08:04:26 -0500
Steve Litt  wrote:

> On Fri, 05 Feb 2021 12:12:33 +0100
> Florian Zieboll via Dng  wrote:
> 
> > > By first installing Windows 7 and then the Synaptic drivers on an
> > > old HDD I was able to restore touchpad functionality with the
> > > Fn+F9 switching. This is a programmable multi-gesture touchpad
> > > which I guess may have flash memory.
> > > 
> > > There has got to be a better way  
> > 
> > 
> >  Hallo g4sra,
> > 
> > as you replied off-list and I don't know of any better way, I bring
> > the issue back to the list: Perhaps someone has a hint on resetting
> > the device, if you'd reveal its make and model?
> > 
> > Another idea out of thin air: Did you remove the CMOS battery - or
> > does the notebook provide a button (or pins) to reset the bios
> > password?
> > 
> > libre Grüße,
> > Florian
> > 
> 
> The following shellscript, called touchtoggle.sh, should do what you
> need.
> 
> ==
> #!/bin/sh
> 
> # touchtoggle.sh Copyright (C) 2019 by Steve Litt
> # All rights reserved.
> # Licensed via the 
> # Expat license: https://directory.fsf.org/wiki/License:Expat
> 
> # FIRST GET DEVICE'S DEVICE ID CONTAINING CASE INSENSITIVE "TOUCHPAD"
> devid=`xinput | grep -i touchpad | \
>   sed -e"s/.*id=//" | sed -e"s/\s.*//"`
> 
> # WITH THAT DEVICE ID, FIND EVERYTING ABOUT PROPERTY
> # CONTAINING CASE INSENSITIVE "DEVICE ENABLED"
> scratchline=`xinput --list-props 11 | \
>   grep -i "device enabled" | \
>   sed -e"s/^\s*//" | sed -e"s/\s*$//"`
> proptext=`echo $scratchline | sed -e"s/\s*(.*//"`
> propid=`echo $scratchline | sed -e"s/.*(//" | sed -e"s/).*//"`
> currstate=`echo $scratchline | sed -e"s/.*):\s*//"`
> 
> # DIAGNOSTICS, COMMENT OUT WHEN FULLY FUNCTIONAL
> echo diagnostic devid  =$devid
> echo diagnostic scratchline=$scratchline
> echo diagnostic proptext   =$proptext#
> echo diagnostic propid =$propid
> 
> # TOGGLE CURRSTATE VARIABLE
> echo -n "Current state of $currstate "
> if test "$currstate" = "1"; then
>   currstate=0
> else
>   currstate=1
> fi
> echo has been changed to $currstate.
> 
> # IMPLEMENT THE PROPERTY VALUE CHANGE
> xinput set-prop $devid $propid $currstate
> 
> # UNCOMMENT FOLLOWING LINE IF PROPERTY ID STOPS WORKING
> #xinput set-prop $devid "$proptext" $currstate
> 
> ==
> 
> I've had several versions of this shellscript, so please let me know
> whether it works for you.
>  
> SteveT



Hallo Steve,

[sorry, now to the list]

after having had a look at your script and the 'xinput' manpage, I
still don't understand, where the information about the device's state
is stored. 

As the current state is preserved between different operating systems:
Do I assume correctly, that the touchpad is "stateful" (enabled |
disabled) and replacing a disabled one with an identical one from
another computer (where it had not been disabled) would restore its
functionality?

Thank you and best regards,
Florian
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread Gabe Stanton via Dng
On Fri, 2021-02-05 at 13:23 +, g4sra via Dng wrote:
> Sent with ProtonMail Secure Email.
> ‐‐‐ Original Message ‐‐‐On Friday, February 5, 2021 11:12 AM,
> Florian Zieboll via Dng  wrote:
> > Am 4. Februar 2021 20:13:49 MEZ schrieb g4sra g4...@protonmail.com:
> > > ‐‐‐ Original Message ‐‐‐On Thursday, February 4, 2021
> > > 6:59 PM, Florian Zieboll via Dng dng@lists.dyne.org wrote:Thanks
> > > for the reply Florian
> > > > Am 4. Februar 2021 18:15:06 MEZ schrieb g4sra via Dng 
> > > > dng@lists.dyne.org:
> > > > > Does anyone know how to re-enable a Synaptics Touchpad in
> > > > > Linux after it has been turned off in Windows using Fn+F9 ?
> > > > 
> > > > If this key combo really changed something "in hardware", i
> > > > assume that a "hard reset" of the notebook(?!) should solve the
> > > > issue...Usually, this is accomplished by removing all power
> > > > sources and periphery, and then holding down the power button
> > > > for 15-20 seconds. The idea is to remove any stored electricity
> > > > (from ac adapter, battery, capacitors) to clear all non-
> > > > persistent storage.
> > > 
> > > That is what googling said too, unfortunately it didn't work.
> > > > Your devices miles may vary, the manual should mention it.
> > > 
> > > The manual is not much use at all, being digital it won't even
> > > serve purpose in the WC.
> > > > libre grüße,Florian
> > > 
> > > By first installing Windows 7 and then the Synaptic drivers on an
> > > old HDD I was able to restore touchpad functionality with the
> > > Fn+F9 switching. This is a programmable multi-gesture touchpad
> > > which I guess may have flash memory.There has got to be a better
> > > way
> > 
> > Hallo g4sra,
> > as you replied off-list and I don't know of any better way, I bring
> > the issue back to the list:
> 
> Thanks for that. This email client will not reply to the list. It
> considers to do so a security issue because of an authentication
> failure. If I post directly to the list then the message thread is
> lost.
> I have tried something new.. it will allow me to CC, so I have done
> that replying directly to you, deleted the To, and promoted the CC,
> so if the message id has remained intact this may be a way around the
> problem.
> 
> > Perhaps someone has a hint on resetting the device, if you'd reveal
> > its make and model?
> 
> Laptop make is mostly irrelevant as the hardware is self-contained as
> manufactured by Synaptics. I believe the communication is SMBus in
> this instance, I know of no way to interrogate the touchpad itself
> other than by what is reported using Synaptics drivers for Windows.
> > Another idea out of thin air: Did you remove the CMOS battery - or
> > does the notebook provide a button (or pins) to reset the bios
> > password?
> 
> Yes, I did a thorough cold power-up.
> 
> > libre Grüße,Florian
> 
> I am looking for a 'Linux software' solution to this
> problem.Currently grepping the kernel source to see if any giveaways
> in the DTB sources.
> 
> 
> 
> 
> ___Dng mailing 
> list...@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Sorry if I missed it, but did you ever just boot into the bios and look
for the toggle there?

I know you said you're looking for a linux software solution to this,
but I thought I'd mention this since I hadn't seen it mentioned. My
apologies if I missed it somewhere.

According to a web search about the subject (serverfault I believe)
bios makers sometimes work with microsoft to provide limited api type
functionality (for things like the f9 you mentioned I assume). 

In my case, I can turn off the touchpad through the bios under config >
keyboard/mouse.

Gabe



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread Rick Moen
Quoting Steve Litt (sl...@troubleshooters.com):

> > as you replied off-list and I don't know of any better way, I bring
> > the issue back to the list: Perhaps someone has a hint on resetting
> > the device, if you'd reveal its make and model?
> > 
> > Another idea out of thin air: Did you remove the CMOS battery - or
> > does the notebook provide a button (or pins) to reset the bios
> > password?
> > 
> > libre Grüße,
> > Florian
> > 
> 
> The following shellscript, called touchtoggle.sh, should do what you
> need.
> 
> ==
> #!/bin/sh
> 
> # touchtoggle.sh Copyright (C) 2019 by Steve Litt
> # All rights reserved.
> # Licensed via the 
> # Expat license: https://directory.fsf.org/wiki/License:Expat
[...]

It's a useful script, and thanks -- but I suggest you immediately
add a second line below that 'Licensed via the Expat license' one:

# Expat license's requirement to include permission notice text is waived.

Otherwise, anyone seeking to redistribute your script is committing the
tort of copyright violation unless he/she provides with it a copy of 
the ~20 lines of Expat License text.  I'm pretty sure you were not
meaning to impose such a legal obligation on redistributors.


BTW, it's some weird FSF fetish to refer to it as "Expat License".
Everyone else on planet Earth (including OSI:
https://opensource.org/licenses/MIT) refers to it as MIT License.

To be tiresomely pedantic, what you used is the commendably minimalist
form of MIT's licence that it issued for the Expat graphics library.  
MIT's slightly longer wording issued attached to the X Consortium
software and used (e.g.) for X.org code to this day differs only in
having a sentence prohibiting users from mentioning X Consortium in
advertising or promotion without written permission, and one stating
that "X Window System" is a trademark of X Consortium, Inc.  There is no
_functional_ difference.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread ael
On Fri, Feb 05, 2021 at 01:23:16PM +, g4sra via Dng wrote:
> 
> 
> > Perhaps someone has a hint on resetting the device, if you'd reveal its 
> > make and model?
> 
> Laptop make is mostly irrelevant as the hardware is self-contained as 
> manufactured by Synaptics. I believe the communication is SMBus in this 
> instance, I know of no way to interrogate the touchpad itself other than by 
> what is reported using Synaptics drivers for Windows.

Doesn't the xserver-xorg-input-synaptics package do that and more?

ael

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread g4sra via Dng



Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Friday, February 5, 2021 11:12 AM, Florian Zieboll via Dng 
 wrote:

> Am 4. Februar 2021 20:13:49 MEZ schrieb g4sra g4...@protonmail.com:
>
> > ‐‐‐ Original Message ‐‐‐
> > On Thursday, February 4, 2021 6:59 PM, Florian Zieboll via Dng 
> > dng@lists.dyne.org wrote:
> > Thanks for the reply Florian
> >
> > > Am 4. Februar 2021 18:15:06 MEZ schrieb g4sra via Dng dng@lists.dyne.org:
> > >
> > > > Does anyone know how to re-enable a Synaptics Touchpad in Linux after 
> > > > it has been turned off in Windows using Fn+F9 ?
> > >
> > > If this key combo really changed something "in hardware", i assume that a 
> > > "hard reset" of the notebook(?!) should solve the issue...
> > > Usually, this is accomplished by removing all power sources and 
> > > periphery, and then holding down the power button for 15-20 seconds. The 
> > > idea is to remove any stored electricity (from ac adapter, battery, 
> > > capacitors) to clear all non-persistent storage.
> >
> > That is what googling said too, unfortunately it didn't work.
> >
> > > Your devices miles may vary, the manual should mention it.
> >
> > The manual is not much use at all, being digital it won't even serve 
> > purpose in the WC.
> >
> > > libre grüße,
> > > Florian
> >
> > By first installing Windows 7 and then the Synaptic drivers on an old HDD I 
> > was able to restore touchpad functionality with the Fn+F9 switching. This 
> > is a programmable multi-gesture touchpad which I guess may have flash 
> > memory.
> > There has got to be a better way
>
> Hallo g4sra,
>
> as you replied off-list and I don't know of any better way, I bring the issue 
> back to the list:

Thanks for that. This email client will not reply to the list. It considers to 
do so a security issue because of an authentication failure. If I post directly 
to the list then the message thread is lost.

I have tried something new.. it will allow me to CC, so I have done that 
replying directly to you, deleted the To, and promoted the CC, so if the 
message id has remained intact this may be a way around the problem.


> Perhaps someone has a hint on resetting the device, if you'd reveal its make 
> and model?

Laptop make is mostly irrelevant as the hardware is self-contained as 
manufactured by Synaptics. I believe the communication is SMBus in this 
instance, I know of no way to interrogate the touchpad itself other than by 
what is reported using Synaptics drivers for Windows.

>
> Another idea out of thin air: Did you remove the CMOS battery - or does the 
> notebook provide a button (or pins) to reset the bios password?
>

Yes, I did a thorough cold power-up.


> libre Grüße,
> Florian
>

I am looking for a 'Linux software' solution to this problem.
Currently grepping the kernel source to see if any giveaways in the DTB sources.





___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread d...@d404.nl
On 05-02-2021 12:12, Florian Zieboll via Dng wrote:
> Am 4. Februar 2021 20:13:49 MEZ schrieb g4sra :
>> ‐‐‐ Original Message ‐‐‐
>> On Thursday, February 4, 2021 6:59 PM, Florian Zieboll via Dng 
>>  wrote:
>>
>> Thanks for the reply Florian
>>
>>> Am 4. Februar 2021 18:15:06 MEZ schrieb g4sra via Dng dng@lists.dyne.org:
>>>
 Does anyone know how to re-enable a Synaptics Touchpad in Linux after it 
 has been turned off in Windows using Fn+F9 ?
>>> If this key combo really changed something "in hardware", i assume that a 
>>> "hard reset" of the notebook(?!) should solve the issue...
>>>
>>> Usually, this is accomplished by removing all power sources and periphery, 
>>> and then holding down the power button for 15-20 seconds. The idea is to 
>>> remove any stored electricity (from ac adapter, battery, capacitors) to 
>>> clear all non-persistent storage.
>> That is what googling said too, unfortunately it didn't work.
>>
>>> Your devices miles may vary, the manual should mention it.
>> The manual is not much use at all, being digital it won't even serve purpose 
>> in the WC.
>>> libre grüße,
>>> Florian
>>>
>> By first installing Windows 7 and then the Synaptic drivers on an old HDD I 
>> was able to restore touchpad functionality with the Fn+F9 switching. This is 
>> a programmable multi-gesture touchpad which I guess may have flash memory.
>>
>> There has got to be a better way
>
>  Hallo g4sra,
>
> as you replied off-list and I don't know of any better way, I bring the issue 
> back to the list: Perhaps someone has a hint on resetting the device, if 
> you'd reveal its make and model?
>
> Another idea out of thin air: Did you remove the CMOS battery - or does the 
> notebook provide a button (or pins) to reset the bios password?
>
> libre Grüße,
> Florian
>
>
It depends how it is governed in Windows but you could try to load a WIN
PE iso and press  Fn+F9.

Grtz.

Nick

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread Steve Litt
On Fri, 05 Feb 2021 12:12:33 +0100
Florian Zieboll via Dng  wrote:

> > By first installing Windows 7 and then the Synaptic drivers on an
> > old HDD I was able to restore touchpad functionality with the Fn+F9
> > switching. This is a programmable multi-gesture touchpad which I
> > guess may have flash memory.
> > 
> > There has got to be a better way  
> 
> 
>  Hallo g4sra,
> 
> as you replied off-list and I don't know of any better way, I bring
> the issue back to the list: Perhaps someone has a hint on resetting
> the device, if you'd reveal its make and model?
> 
> Another idea out of thin air: Did you remove the CMOS battery - or
> does the notebook provide a button (or pins) to reset the bios
> password?
> 
> libre Grüße,
> Florian
> 

The following shellscript, called touchtoggle.sh, should do what you
need.

==
#!/bin/sh

# touchtoggle.sh Copyright (C) 2019 by Steve Litt
# All rights reserved.
# Licensed via the 
# Expat license: https://directory.fsf.org/wiki/License:Expat

# FIRST GET DEVICE'S DEVICE ID CONTAINING CASE INSENSITIVE "TOUCHPAD"
devid=`xinput | grep -i touchpad | \
  sed -e"s/.*id=//" | sed -e"s/\s.*//"`

# WITH THAT DEVICE ID, FIND EVERYTING ABOUT PROPERTY
# CONTAINING CASE INSENSITIVE "DEVICE ENABLED"
scratchline=`xinput --list-props 11 | \
  grep -i "device enabled" | \
  sed -e"s/^\s*//" | sed -e"s/\s*$//"`
proptext=`echo $scratchline | sed -e"s/\s*(.*//"`
propid=`echo $scratchline | sed -e"s/.*(//" | sed -e"s/).*//"`
currstate=`echo $scratchline | sed -e"s/.*):\s*//"`

# DIAGNOSTICS, COMMENT OUT WHEN FULLY FUNCTIONAL
echo diagnostic devid  =$devid
echo diagnostic scratchline=$scratchline
echo diagnostic proptext   =$proptext#
echo diagnostic propid =$propid

# TOGGLE CURRSTATE VARIABLE
echo -n "Current state of $currstate "
if test "$currstate" = "1"; then
currstate=0
else
currstate=1
fi
echo has been changed to $currstate.

# IMPLEMENT THE PROPERTY VALUE CHANGE
xinput set-prop $devid $propid $currstate

# UNCOMMENT FOLLOWING LINE IF PROPERTY ID STOPS WORKING
#xinput set-prop $devid "$proptext" $currstate

==

I've had several versions of this shellscript, so please let me know
whether it works for you.
 
SteveT

Steve Litt 
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-05 Thread Florian Zieboll via Dng
Am 4. Februar 2021 20:13:49 MEZ schrieb g4sra :
> ‐‐‐ Original Message ‐‐‐
> On Thursday, February 4, 2021 6:59 PM, Florian Zieboll via Dng 
>  wrote:
> 
> Thanks for the reply Florian
> 
> > Am 4. Februar 2021 18:15:06 MEZ schrieb g4sra via Dng dng@lists.dyne.org:
> >
> > > Does anyone know how to re-enable a Synaptics Touchpad in Linux after it 
> > > has been turned off in Windows using Fn+F9 ?
> >
> > If this key combo really changed something "in hardware", i assume that a 
> > "hard reset" of the notebook(?!) should solve the issue...
> >
> > Usually, this is accomplished by removing all power sources and periphery, 
> > and then holding down the power button for 15-20 seconds. The idea is to 
> > remove any stored electricity (from ac adapter, battery, capacitors) to 
> > clear all non-persistent storage.
> 
> That is what googling said too, unfortunately it didn't work.
> 
> >
> > Your devices miles may vary, the manual should mention it.
> 
> The manual is not much use at all, being digital it won't even serve purpose 
> in the WC.
> >
> > libre grüße,
> > Florian
> >
> 
> By first installing Windows 7 and then the Synaptic drivers on an old HDD I 
> was able to restore touchpad functionality with the Fn+F9 switching. This is 
> a programmable multi-gesture touchpad which I guess may have flash memory.
> 
> There has got to be a better way


 Hallo g4sra,

as you replied off-list and I don't know of any better way, I bring the issue 
back to the list: Perhaps someone has a hint on resetting the device, if you'd 
reveal its make and model?

Another idea out of thin air: Did you remove the CMOS battery - or does the 
notebook provide a button (or pins) to reset the bios password?

libre Grüße,
Florian


-- 

ooops...

[message sent otg]

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Synaptics Touchpad Fn+F9

2021-02-04 Thread Florian Zieboll via Dng
Am 4. Februar 2021 18:15:06 MEZ schrieb g4sra via Dng :
> Does anyone know how to re-enable a Synaptics Touchpad in Linux after it has 
> been turned off in Windows using Fn+F9 ?

If this key combo really changed something "in hardware", i assume that a "hard 
reset" of the notebook(?!) should solve the issue...

Usually, this is accomplished by removing all power sources and periphery, and 
then holding down the power button for 15-20 seconds. The idea is to remove any 
stored electricity (from ac adapter, battery, capacitors) to clear all 
non-persistent storage.

Your devices miles may vary, the manual should mention it.

libre grüße,
Florian


-- 
Florian Zieboll
Hauptstraße 6a
D-68535 Edingen

Telefon: +49 6203 925 78 36
Mobil: +49 160 690 15 87
E-Mail: f.zieb...@web.de
PGP keyID: 0xEE454979FE441FD6
Chat / xmpp: f.zieb...@xabber.de
Chat / matrix: @florian_zieboll:feneas.org
WWW: https://www.zwischenspeicher.info

[message sent otg]

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng