You are not logged in.

#1 2013-03-21 00:19:33

infested999
Member
Registered: 2010-10-02
Posts: 48

Touchpad broken or just drivers?

I completely disassembled my Asus eee pc 1000HA and in the process broke the connector for the touchpad. When I first rebooted the touchpad stopped working. I tried to just use a piece of tape to fix the connector which should work.

The touchpad is connected with a ribbon cable to the motherboard and the left-click and right-click buttons are directly on the motherboard. Currently I have neither left/right click nor touchpad functionality. xev shows nothing also.

What is the correct way to test if a touchpad is connected?

Offline

#2 2013-03-21 01:19:56

Arogers10
Member
Registered: 2012-06-20
Posts: 68

Re: Touchpad broken or just drivers?

I would say check/post the output of

cat /proc/bus/input/devices | less

for an entry Name labeled "Touchpad" to determine if the touch pad is recognized at all by the computer

Offline

#3 2013-03-21 02:04:45

infested999
Member
Registered: 2010-10-02
Posts: 48

Re: Touchpad broken or just drivers?

Arogers10 wrote:

I would say check/post the output of

cat /proc/bus/input/devices | less

for an entry Name labeled "Touchpad" to determine if the touch pad is recognized at all by the computer

I looked through it and there was no touchpad. (input8 is the camera)

http://pastebin.com/EDiNprrt

Even if I did damage the connector to the touchpad, shouldn't I still be able to left-click and right-click as those buttons are soldered straight onto the motherboard?

Offline

#4 2013-03-21 02:27:15

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,428

Re: Touchpad broken or just drivers?

Okay, look through the output of journalctl| grep input:

Even if I did damage the connector to the touchpad, shouldn't I still be able to left-click and right-click as those buttons are soldered straight onto the motherboard?

Not necessarily.  It depends on where the chipset is.  It likely exists on the flex circuit or in the touch pad itself.  The buttons on the motherboard could route back out to the touch pad through the cable.  The serial link from the touch pad would then return to the main board over the same connector.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Online

#5 2013-03-21 02:42:50

infested999
Member
Registered: 2010-10-02
Posts: 48

Re: Touchpad broken or just drivers?

ewaller wrote:

Okay, look through the output of journalctl| grep input:

Even if I did damage the connector to the touchpad, shouldn't I still be able to left-click and right-click as those buttons are soldered straight onto the motherboard?

Not necessarily.  It depends on where the chipset is.  It likely exists on the flex circuit or in the touch pad itself.  The buttons on the motherboard could route back out to the touch pad through the cable.  The serial link from the touch pad would then return to the main board over the same connector.

journalctl doesn't give any output, even without grep. The cable from the touchpad to the motherboard was not connected to anything else.

Offline

#6 2013-03-21 03:07:30

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,428

Re: Touchpad broken or just drivers?

infested999 wrote:

journalctl doesn't give any output, even without grep.

Okay.  What if you try journalctl as root.

The cable from the touchpad to the motherboard was not connected to anything else.

I would not expect it to be.  What I meant was that (I think) the chip is in the touchpad.  All communication from the touchpad comes from that chip over a serial link.  The buttons on the motherboard could be routed to the touchpad connector where the signals go out to the chip, are encoded, and the status comes back over the serial link.  In this way, one could remove a Synaptics based touch pad with an Alps touchpad, and the controller would change along with the touchpad.  The touch pad identifies itself to the main board by an appropriate message sent over the serial link.

If that chip is not getting power, or if the serial link was severed, the motherboard will never see it.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Online

#7 2013-03-21 22:52:03

infested999
Member
Registered: 2010-10-02
Posts: 48

Re: Touchpad broken or just drivers?

I just noticed I didn't have systemd on that netbook.

journalctl works fine now:

http://pastebin.com/S17pshJu

Looks like the connector doesn't work at all.

Offline

#8 2013-03-22 01:44:25

cookies
Member
Registered: 2013-01-17
Posts: 253

Re: Touchpad broken or just drivers?

The output of "journalctl | grep input:" for my 1215 B looks like this

Mar 21 17:09:31 arch kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Mar 21 17:09:31 arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Mar 21 17:09:31 arch kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Mar 21 17:09:31 arch kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
Mar 21 17:09:31 arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Mar 21 17:09:33 arch kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Mar 21 17:09:33 arch kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
Mar 21 17:09:33 arch kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input7
Mar 21 17:09:34 arch kernel: input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input8
Mar 21 17:09:34 arch kernel: input: USB 2.0 UVC VGA WebCam as /devices/pci0000:00/0000:00:13.2/usb3/3-4/3-4:1.0/input/input9
Mar 21 17:09:34 arch kernel: input: HDA ATI SB Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input10
Mar 21 17:09:34 arch kernel: input: HDA ATI SB Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input11
Mar 21 17:09:34 arch kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12

ATI Chip for sound instead of Intel, but the rest is pretty much the same.

So, unless someone else with a 1000HA has trouble with the touchpad, I'd guess you successfully broke yours sad

Offline

#9 2013-03-22 03:02:59

infested999
Member
Registered: 2010-10-02
Posts: 48

Re: Touchpad broken or just drivers?

cookies wrote:

The output of "journalctl | grep input:" for my 1215 B looks like this

Mar 21 17:09:31 arch kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Mar 21 17:09:31 arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Mar 21 17:09:31 arch kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Mar 21 17:09:31 arch kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
Mar 21 17:09:31 arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Mar 21 17:09:33 arch kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Mar 21 17:09:33 arch kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
Mar 21 17:09:33 arch kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input7
Mar 21 17:09:34 arch kernel: input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input8
Mar 21 17:09:34 arch kernel: input: USB 2.0 UVC VGA WebCam as /devices/pci0000:00/0000:00:13.2/usb3/3-4/3-4:1.0/input/input9
Mar 21 17:09:34 arch kernel: input: HDA ATI SB Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input10
Mar 21 17:09:34 arch kernel: input: HDA ATI SB Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input11
Mar 21 17:09:34 arch kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12

ATI Chip for sound instead of Intel, but the rest is pretty much the same.

So, unless someone else with a 1000HA has trouble with the touchpad, I'd guess you successfully broke yours sad

If the cable connecting the touchpad to the motherboard is not plugged in, is it supposed to show up under journalctl?

Offline

#10 2013-03-22 03:33:49

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,428

Re: Touchpad broken or just drivers?

infested999 wrote:

If the cable connecting the touchpad to the motherboard is not plugged in, is it supposed to show up under journalctl?

That is my theory. (That it will not)

Last edited by ewaller (2013-03-22 03:34:18)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Online

#11 2013-03-22 04:03:13

cookies
Member
Registered: 2013-01-17
Posts: 253

Re: Touchpad broken or just drivers?

If the touchpad is connected and working you should see "SynPS/2 Synaptics TouchPad as ..." somewhere in your journal (last line of my journal output). If it's not connected, you don't see that message.

By the way, just before that "SynPS/2 Synaptics TouchPad" line I get the following line for my touchpad

Mar 21 17:09:34 arch kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1c0b1, caps: 0xd04733/0xa40000/0xa0400, board id: 3655, fw id: 650187

so you might try "journalctl | grep Touchpad" or "journalctl | grep synaptics" and see if that gives you any output.

Edit: Typo

Last edited by cookies (2013-03-22 04:06:07)

Offline

#12 2013-03-22 04:20:48

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,428

Re: Touchpad broken or just drivers?

Just for clarification: 

On my HP DV4, the order in which the events are numbered is nondeterministic from one boot to the next.  That is why the evdev configuration matches by attribute rather than by number.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Online

Board footer

Powered by FluxBB