touchpad driver - F32 - users - Fedora Mailing-Lists

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

1989

1988

1987

1986

1985

1984

1983

1982

1981

1980

touchpad driver - F32

Fonts "forgotten" on boot (changes...

SATA3 _A1, SATA3_ 2, etc. -

Geoffrey Leach

Monday, 27 July 2020 Mon, 27 Jul '20

4:44 p.m.

Touchpad stopped working with version 32 (perhaps earlier?) At one point there was an X.org configuration required, but that appears to have become irrelevant. Is there a FAQ?

Reply

Show replies by thread

Geoffrey Leach

Monday, 27 July Mon, 27 Jul

5:07 p.m.

Add'l info. Running XFCE. Touchpad is not listed in the Mouse page, so presumably the touchpad is broken? On Mon, 27 Jul 2020 14:44:09 -0700 Geoffrey Leach <geoff(a)hughes.net> wrote:

Touchpad stopped working with version 32 (perhaps earlier?) At one point there was an X.org configuration required, but that appears to have become irrelevant. Is there a FAQ?

Reply

Samuel Sieb

6:05 p.m.

On 7/27/20 3:07 PM, Geoffrey Leach wrote:

Running XFCE. Touchpad is not listed in the Mouse page, so presumably the touchpad is broken?

Check if your keyboard has a disable touchpad button. Check in the BIOS settings if there's a touchpad setting for smart. Sometimes that one doesn't work with Linux. Check in /proc/bus/input/devices to see if you can see your touchpad listed. Do you remember what the X config setting was that you had before?

Reply

Geoffrey Leach

Tuesday, 28 July Tue, 28 Jul

5:04 p.m.

On Mon, 27 Jul 2020 16:05:47 -0700 Samuel Sieb <samuel(a)sieb.net> wrote:

On 7/27/20 3:07 PM, Geoffrey Leach wrote: > Running XFCE. Touchpad is not listed in the Mouse page, so > presumably the touchpad is broken? Check if your keyboard has a disable touchpad button.

Verified

Check in the BIOS settings if there's a touchpad setting for smart. Sometimes that one doesn't work with Linux

No smart BIOS

Check in /proc/bus/input/devices to see if you can see your touchpad listed.

Directory is empty -- but also empty on similar system with working touchpad

Do you remember what the X config setting was that you had before?

Alas, no. I'll dig around, but I expect thst the bottom line is broken hardware. Thanks.

Reply

Samuel Sieb

5:25 p.m.

On 7/28/20 3:04 PM, Geoffrey Leach wrote:

On Mon, 27 Jul 2020 16:05:47 -0700 Samuel Sieb <samuel(a)sieb.net> wrote: > Check in /proc/bus/input/devices to see if you can see your touchpad > listed. Directory is empty -- but also empty on similar system with working touchpad

What do you mean it's empty? It's a "file", not a directory. And it has to be there.

Reply

Geoffrey Leach

6:31 p.m.

On Tue, 28 Jul 2020 15:25:56 -0700 Samuel Sieb <samuel(a)sieb.net> wrote:

On 7/28/20 3:04 PM, Geoffrey Leach wrote: > On Mon, 27 Jul 2020 16:05:47 -0700 > Samuel Sieb <samuel(a)sieb.net> wrote: >> Check in /proc/bus/input/devices to see if you can see your >> touchpad listed. > Directory is empty -- but also empty on similar system with working > touchpad What do you mean it's empty? It's a "file", not a directory. And it has to be there.

My bad. The file is empty.

Reply

Samuel Sieb

6:41 p.m.

On 7/28/20 4:31 PM, Geoffrey Leach wrote:

On Tue, 28 Jul 2020 15:25:56 -0700 Samuel Sieb <samuel(a)sieb.net> wrote: > On 7/28/20 3:04 PM, Geoffrey Leach wrote: >> On Mon, 27 Jul 2020 16:05:47 -0700 >> Samuel Sieb <samuel(a)sieb.net> wrote: >>> Check in /proc/bus/input/devices to see if you can see your >>> touchpad listed. >> Directory is empty -- but also empty on similar system with working >> touchpad > > What do you mean it's empty? It's a "file", not a directory. And it > has to be there. My bad. The file is empty.

How are you determining that? If you look with "ls", it has a length of 0, but you can read it with "less". There really is something there.

Reply

Ed Greshko

6:46 p.m.

On 2020-07-29 07:31, Geoffrey Leach wrote:

On Tue, 28 Jul 2020 15:25:56 -0700 Samuel Sieb <samuel(a)sieb.net> wrote: > On 7/28/20 3:04 PM, Geoffrey Leach wrote: >> On Mon, 27 Jul 2020 16:05:47 -0700 >> Samuel Sieb <samuel(a)sieb.net> wrote: >>> Check in /proc/bus/input/devices to see if you can see your >>> touchpad listed. >> Directory is empty -- but also empty on similar system with working >> touchpad > What do you mean it's empty? It's a "file", not a directory. And it > has to be there. My bad. The file is empty.

You think it is empty because [egreshko@meimei ~]$ ll /proc/bus/input/devices -r--r--r--. 1 root root 0 Jul 29 07:45 /proc/bus/input/devices But it isn't a file in the traditional sense. Do.... cat /proc/bus/input/devices -- The key to getting good answers is to ask good questions.

Reply

Geoffrey Leach

Wednesday, 29 July Wed, 29 Jul

10:37 a.m.

On Wed, 29 Jul 2020 07:46:24 +0800 Ed Greshko <ed.greshko(a)greshko.com> wrote:

On 2020-07-29 07:31, Geoffrey Leach wrote: > On Tue, 28 Jul 2020 15:25:56 -0700 > Samuel Sieb <samuel(a)sieb.net> wrote: > >> On 7/28/20 3:04 PM, Geoffrey Leach wrote: >>> On Mon, 27 Jul 2020 16:05:47 -0700 >>> Samuel Sieb <samuel(a)sieb.net> wrote: >>>> Check in /proc/bus/input/devices to see if you can see your >>>> touchpad listed. >>> Directory is empty -- but also empty on similar system with >>> working touchpad >> What do you mean it's empty? It's a "file", not a directory. And >> it has to be there. > My bad. The file is empty. You think it is empty because [egreshko@meimei ~]$ ll /proc/bus/input/devices -r--r--r--. 1 root root 0 Jul 29 07:45 /proc/bus/input/devices But it isn't a file in the traditional sense. Do.... cat /proc/bus/input/devices

Ah! Verrry interesting. No entry for TouchPad. Poor thing has died. So sad. Thanks to you and Samuel for the help.

Reply

1372

days inactive

1374

days old

users@lists.fedoraproject.org

Manage subscription

8 comments

3 participants

tags (0)

participants (3)

Ed Greshko
Geoffrey Leach
Samuel Sieb