Re: Thinkpad Touchpad no longer works
On 16/10/09 22:30:54, Florian Kulzer wrote: On Fri, Oct 16, 2009 at 21:49:34 +0100, Barry Samuels wrote: SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing Just noticed something. On my desktop event0, event1, mice, mouse0 etc are in /dev/input but on the laptop they are in /dev and /dev/input has only by-id and by-path Is that significant? Yes, it is; it probably means that something goes wrong when udev creates the device node for the touchpad. My first guess is that you upgraded to a newer version of udev, and that it now expects some novel piece of information that your custom kernel does not provide. (IOW, I side with Celejar and Andrew in suspecting your kernel configuration is the cause of your problems.) Please install the newest stock kernel and boot into it; this will immediately tell us if we are on the right track. Once we have established that, we can delve into the details to find the relevant setting. Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On Sat, Oct 17, 2009 at 10:21:52 +0100, Barry Samuels wrote: On 16/10/09 22:30:54, Florian Kulzer wrote: On Fri, Oct 16, 2009 at 21:49:34 +0100, Barry Samuels wrote: SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing Just noticed something. On my desktop event0, event1, mice, mouse0 etc are in /dev/input but on the laptop they are in /dev and /dev/input has only by-id and by-path Is that significant? Yes, it is; it probably means that something goes wrong when udev creates the device node for the touchpad. My first guess is that you upgraded to a newer version of udev, and that it now expects some novel piece of information that your custom kernel does not provide. (IOW, I side with Celejar and Andrew in suspecting your kernel configuration is the cause of your problems.) Please install the newest stock kernel and boot into it; this will immediately tell us if we are on the right track. Once we have established that, we can delve into the details to find the relevant setting. Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. OK, we can stop worrying about the kernel configuration for the moment. Now I would be interested in some details about your misplaced event devices; please show me the output of: stat /dev/event7 Also, let's check what udev is doing, with this command: udevadm test /class/input/input7/event7 This will produce a lot of output; please make it available on http://debian.pastebin.com and post the link here. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 17/10/09 12:26:11, Florian Kulzer wrote: On Sat, Oct 17, 2009 at 10:21:52 +0100, Barry Samuels wrote: Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. OK, we can stop worrying about the kernel configuration for the moment. Now I would be interested in some details about your misplaced event devices; please show me the output of: stat /dev/event7 File: `/dev/event7' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: bh/11d Inode: 33604 Links: 1 Device type: d,47 Access: (0660/crw-rw) Uid: (0/root) Gid: (0/root) Access: 2009-10-17 12:38:41.209641864 +0100 Modify: 2009-10-17 12:38:41.209641864 +0100 Change: 2009-10-17 12:38:41.209641864 +0100 Also, let's check what udev is doing, with this command: udevadm test /class/input/input7/event7 There wasn't much output so I've included it here: run_command: calling: test udevadm_test: version 141 udev_rules_new: rule file basename '/etc/udev/rules.d/50-udev.rules' already added, ignoring '/lib/udev/rules.d/50-udev.rules' parse_file: reading '/etc/udev/rules.d/025_libgphoto2.rules' as rules file parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-gnupg.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane-extras.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file parse_file: reading '/dev/.udev/rules.d/61-dev-root-link.rules' as rules file parse_file: reading '/lib/udev/rules.d/62-bluez-hid2hci.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-persistent-net-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-alsa.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file parse_file: reading '/lib/udev/rules.d/85-hwclock.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file parse_file: reading '/lib/udev/rules.d/90-hal.rules' as rules file parse_file: reading '/lib/udev/rules.d/91-permissions.rules' as rules file util_lookup_group: specified group 'nvram' unknown util_lookup_user: specified user 'tss' unknown util_lookup_group: specified group 'tss' unknown util_lookup_group: specified group 'kvm' unknown util_lookup_group: specified group 'rdma' unknown parse_file: reading '/lib/udev/rules.d/95-late.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_gpsd.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_hdparm.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_libccid.rules' as rules file udev_rules_new: rules use 100692 bytes tokens (8391 * 12 bytes), 13475 bytes buffer udev_rules_new: temporary index used 30820 bytes (1541 * 20 bytes) unable to open device '/sys/class/input/input7/event7' -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 17/10/09 14:07:52, Barry Samuels wrote: On 17/10/09 12:26:11, Florian Kulzer wrote: On Sat, Oct 17, 2009 at 10:21:52 +0100, Barry Samuels wrote: Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. OK, we can stop worrying about the kernel configuration for the moment. Now I would be interested in some details about your misplaced event devices; please show me the output of: stat /dev/event7 File: `/dev/event7' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: bh/11dInode: 33604 Links: 1 Device type: d,47 Access: (0660/crw-rw) Uid: (0/root) Gid: (0/root) Access: 2009-10-17 12:38:41.209641864 +0100 Modify: 2009-10-17 12:38:41.209641864 +0100 Change: 2009-10-17 12:38:41.209641864 +0100 Also, let's check what udev is doing, with this command: udevadm test /class/input/input7/event7 /class/input/input7/event7 does not exist but /class/input/event7 does so I've done the same with that. Output below: run_command: calling: test udevadm_test: version 141 udev_rules_new: rule file basename '/etc/udev/rules.d/50-udev.rules' already added, ignoring '/lib/udev/rules.d/50-udev.rules' parse_file: reading '/etc/udev/rules.d/025_libgphoto2.rules' as rules file parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-gnupg.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane-extras.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-libsane.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file parse_file: reading '/dev/.udev/rules.d/61-dev-root-link.rules' as rules file parse_file: reading '/lib/udev/rules.d/62-bluez-hid2hci.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/75-persistent-net-generator.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-alsa.rules' as rules file parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file parse_file: reading '/lib/udev/rules.d/85-hwclock.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file parse_file: reading '/lib/udev/rules.d/90-hal.rules' as rules file parse_file: reading '/lib/udev/rules.d/91-permissions.rules' as rules file util_lookup_group: specified group 'nvram' unknown util_lookup_user: specified user 'tss' unknown util_lookup_group: specified group 'tss' unknown util_lookup_group: specified group 'kvm' unknown util_lookup_group: specified group 'rdma' unknown parse_file: reading '/lib/udev/rules.d/95-late.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_gpsd.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_hdparm.rules' as rules file parse_file: reading '/etc/udev/rules.d/z60_libccid.rules' as rules file udev_rules_new: rules use 100692 bytes tokens (8391 * 12 bytes), 13475 bytes buffer udev_rules_new: temporary index used 30820 bytes (1541 * 20 bytes) udev_device_new_from_syspath: device 0x8074d10 has devpath '/devices/ platform/i8042/serio1/input/input10/event7' udev_device_new_from_syspath: device 0x80747e8 has devpath '/devices/ platform/i8042/serio1/input/input10/event7' udev_device_read_db: device 0x80747e8 filled with db file data udev_device_new_from_syspath: device 0x8074a80 has devpath '/devices/ platform/i8042/serio1/input/input10' udev_device_new_from_syspath: device 0x8064318 has devpath '/devices/ platform/i8042/serio1' udev_device_new_from_syspath: device 0x80644c0 has devpath '/devices/ platform/i8042' udev_device_new_from_syspath: device 0x8064658 has devpath '/devices/ platform' udev_rules_apply_to_event: IMPORT 'path_id /devices/platform/i8042/serio1/ input/input10/event7' /lib/udev/rules.d/60-persistent-input.rules:45 util_run_program: 'path_id /devices/platform/i8042/serio1/input/input10/ event7' util_run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=platform-i8042- serio-1' util_run_program: '/lib/udev/path_id' returned with status 0 udev_rules_apply_to_event: LINK 'input/by-path/platform-i8042-serio-1- event-mouse' /lib/udev/rules.d/60-persistent-input.rules:49 udev_rules_apply_to_event: RUN 'socket:@/org/freedesktop/hal/udev_event' / lib/udev/rules.d/90-hal.rules:2 udev_event_execute_rules: no node
Re: Thinkpad Touchpad no longer works
On Sat, Oct 17, 2009 at 14:22:52 +0100, Barry Samuels wrote: On 17/10/09 14:07:52, Barry Samuels wrote: On 17/10/09 12:26:11, Florian Kulzer wrote: On Sat, Oct 17, 2009 at 10:21:52 +0100, Barry Samuels wrote: Installed linux-image-2.6.30-2-486 but sorry to report that there is no difference - the touchpad still doesn't work and the event nodes are still in /dev. OK, we can stop worrying about the kernel configuration for the moment. Now I would be interested in some details about your misplaced event devices; please show me the output of: stat /dev/event7 File: `/dev/event7' Size: 0 Blocks: 0 IO Block: 4096 character special file Device: bh/11d Inode: 33604 Links: 1 Device type: d,47 Access: (0660/crw-rw) Uid: (0/root) Gid: (0/root) Access: 2009-10-17 12:38:41.209641864 +0100 Modify: 2009-10-17 12:38:41.209641864 +0100 Change: 2009-10-17 12:38:41.209641864 +0100 That would be perfect if the device node were under /dev/input/. Also, let's check what udev is doing, with this command: udevadm test /class/input/input7/event7 /class/input/input7/event7 does not exist but /class/input/event7 does so I've done the same with that. Output below: run_command: calling: test udevadm_test: version 141 udev_rules_new: rule file basename '/etc/udev/rules.d/50-udev.rules' already added, ignoring '/lib/udev/rules.d/50-udev.rules' It seems that you have an outdated 50-udev.rules file in /etc/udev/rules.d/, which means that the up-to-date file in /lib/udev/rules.d/ is ignored. Quoting from udev's NEWS.Debian.gz: The default rules files have been moved to /lib/udev/rules.d/ and /etc/udev/rules.d/ is supposed to contain only generated files or custom directives. (starting udev version 0.140-1) [ snip: udev reads many more .rules files ] udev_rules_new: rules use 100692 bytes tokens (8391 * 12 bytes), 13475 bytes buffer udev_rules_new: temporary index used 30820 bytes (1541 * 20 bytes) udev_device_new_from_syspath: device 0x8074d10 has devpath '/devices/platform/i8042/serio1/input/input10/event7' udev_device_new_from_syspath: device 0x80747e8 has devpath '/devices/platform/i8042/serio1/input/input10/event7' udev_device_read_db: device 0x80747e8 filled with db file data Here is where things start to go wrong: At this point udev should apply two rules, LINK 'char/13:71' and NAME 'input/event7' from the file /lib/udev/rules.d/50-udev.rules. This does not happen because of what I pointed out above. I think you simply have to get rid of /etc/udev/rules.d/50-udev.rules. If you customized this file then you have to port your changes to the new file in /lib/udev/rules.d/. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works [Solved]
On 17/10/09 15:12:35, Florian Kulzer wrote: It seems that you have an outdated 50-udev.rules file in /etc/udev/rules.d/, which means that the up-to-date file in /lib/udev/rules.d/ is ignored. Quoting from udev's NEWS.Debian.gz: The default rules files have been moved to /lib/udev/rules.d/ and /etc/udev/rules.d/ is supposed to contain only generated files or custom directives. (starting udev version 0.140-1) Florian You are so right! Removing that file has cured the problem. All that file had in it was: KERNEL=='rtc0', SYMLINK+=rtc I can't honestly say now whether I put that there or not. Thank you so much for your help. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works [Solved]
On Sat, Oct 17, 2009 at 16:19:36 +0100, Barry Samuels wrote:
On 17/10/09 15:12:35, Florian Kulzer wrote:
It seems that you have an outdated 50-udev.rules file in
/etc/udev/rules.d/, which means that the up-to-date file in
/lib/udev/rules.d/ is ignored.
Quoting from udev's NEWS.Debian.gz:
The default rules files have been moved to /lib/udev/rules.d/ and
/etc/udev/rules.d/ is supposed to contain only generated files or custom
directives. (starting udev version 0.140-1)
Florian
You are so right! Removing that file has cured the problem.
All that file had in it was:
KERNEL=='rtc0', SYMLINK+=rtc
It seems a bit strange to me that an older version of 50-udev.rules
would only contain one line. (I just looked at this file for Lenny, udev
0.125-7+lenny3; it has 108 lines.) Did you check your filesystems and
the SMART information of your hard drive recently?
I can't honestly say now whether I put that there or not. Thank you so
much for your help.
I am glad to hear that the problem is solved. It might be a good idea to
check if you have other duplicate rules files on your system. The
following bash one-liner should list all files in /etc/udev/rules.d/
that also exist in /lib/udev/rules.d/:
for FILE in /etc/udev/rules.d/*; do [[ -a /lib/udev/rules.d/${FILE##*/} ]]
echo $FILE; done
--
Regards,| http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
Hi, On Fri, Oct 16, 2009 at 02:08:45PM +0100, Barry Samuels wrote: I have an IBM Thinkpad R61 running Debian Testing with kernel 2.6.30. After a recent system update the touchpad no longer works. The red button thing, whatever they call it, embedded in the keyboard and its associated buttons all work but the touchpad and its associated buttons don't. I have tried various xorg.conf configurations and no xorg.conf at all but it makes no difference. But I can not tell what you tried. I've tried booting from a Knoppix DVD v5.1 with a 2.6.19 kernel and it works with that. Did you copy xorg.conf from Knoppix? Can anyone suggest a reason for this? Did you install xfree86-driver-synaptics ? Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 14:31:33, Osamu Aoki wrote: Hi, On Fri, Oct 16, 2009 at 02:08:45PM +0100, Barry Samuels wrote: I have an IBM Thinkpad R61 running Debian Testing with kernel 2.6.30. After a recent system update the touchpad no longer works. The red button thing, whatever they call it, embedded in the keyboard and its associated buttons all work but the touchpad and its associated buttons don't. I have tried various xorg.conf configurations and no xorg.conf at all but it makes no difference. But I can not tell what you tried. I've tried booting from a Knoppix DVD v5.1 with a 2.6.19 kernel and it works with that. Did you copy xorg.conf from Knoppix? Yes - no difference. Can anyone suggest a reason for this? Did you install xfree86-driver-synaptics ? No but I do have xserver-xorg-input-synaptics. Let me stress that it was working perfectly before the update. I haven't changed anything directly myself. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On Fri, Oct 16, 2009 at 04:25:52PM +0100, Barry Samuels wrote: On 16/10/09 14:31:33, Osamu Aoki wrote: [...] Did you install xfree86-driver-synaptics ? No but I do have xserver-xorg-input-synaptics. Let me stress that it was working perfectly before the update. I haven't changed anything directly myself. can you get synclient to connect to the synaptics driver? Does Xorg.0.log show any reference to synaptics? A signature.asc Description: Digital signature
Re: Thinkpad Touchpad no longer works
On 16/10/09 16:59:55, Andrew Sackville-West wrote: On Fri, Oct 16, 2009 at 04:25:52PM +0100, Barry Samuels wrote: On 16/10/09 14:31:33, Osamu Aoki wrote: [...] Did you install xfree86-driver-synaptics ? No but I do have xserver-xorg-input-synaptics. Let me stress that it was working perfectly before the update. I haven't changed anything directly myself. can you get synclient to connect to the synaptics driver? Does Xorg.0.log show any reference to synaptics? I hadn't thought of looking in there but, yes, there is a line which says: SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing What would that mean? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On Fri, 16 Oct 2009 18:42:05 +0100 Barry Samuels ba...@beenthere.mail1.co.uk wrote: ... SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing What would that mean? Not sure, but in the kernel config, there's something called CONFIG_INPUT_DEV (Device Drivers / Input device support / Event interface). From its help: Say Y here if you want your input device events be accessible under char device 13:64+ - /dev/input/eventX in a generic way. To compile this driver as a module, choose M here: the module will be called evdev. Perhaps your kernel doesn't have this enabled? Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote: On Fri, 16 Oct 2009 18:42:05 +0100 Barry Samuels ba...@beenthere.mail1.co.uk wrote: ... SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing What would that mean? Not sure, but in the kernel config, there's something called CONFIG_INPUT_DEV (Device Drivers / Input device support / Event interface). From its help: Say Y here if you want your input device events be accessible under char device 13:64+ - /dev/input/eventX in a generic way. To compile this driver as a module, choose M here: the module will be called evdev. Perhaps your kernel doesn't have this enabled? from the tone of the prior thread, I assume it's a stock kernel, so, OP, let us know if it's not. Apropos the xorg log, if the synaptics module can't find the device then it won't work, I would assume :) Can you provide the logs of what packages you upgraded that brought about this failure? I'm thinking maybe this points to a hal problem, perhaps (but know nothing about hal...). A signature.asc Description: Digital signature
Re: Thinkpad Touchpad no longer works
On Fri, Oct 16, 2009 at 12:13:45 -0700, Andrew Sackville-West wrote: On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote: On Fri, 16 Oct 2009 18:42:05 +0100 Barry Samuels wrote: ... SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing What would that mean? Not sure, but in the kernel config, there's something called CONFIG_INPUT_DEV (Device Drivers / Input device support / Event interface). [...] Perhaps your kernel doesn't have this enabled? from the tone of the prior thread, I assume it's a stock kernel, so, OP, let us know if it's not. Apropos the xorg log, if the synaptics module can't find the device then it won't work, I would assume :) Can you provide the logs of what packages you upgraded that brought about this failure? I'm thinking maybe this points to a hal problem, perhaps (but know nothing about hal...). The output of the following command should tell us what HAL knows/thinks about the touchpad: lshal -u $(hal-find-by-capability --capability input.touchpad) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 20:13:45, Andrew Sackville-West wrote:
On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote:
On Fri, 16 Oct 2009 18:42:05 +0100
Barry Samuels ba...@beenthere.mail1.co.uk wrote:
...
SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem
to be missing
What would that mean?
Not sure, but in the kernel config, there's something called
CONFIG_INPUT_DEV (Device Drivers / Input device support / Event
interface). From its help:
Say Y here if you want your input device events be accessible
under char device 13:64+ - /dev/input/eventX in a generic way.
To compile this driver as a module, choose M here: the
module will be called evdev.
Perhaps your kernel doesn't have this enabled?
It is enabled.
from the tone of the prior thread, I assume it's a stock kernel, so,
OP, let us know if it's not.
No it's not. I compile my own kernels.
Apropos the xorg log, if the synaptics module can't find the device
then it won't work, I would assume :)
Seems fair.
Can you provide the logs of what packages you upgraded that brought
about this failure? I'm thinking maybe this points to a hal problem,
perhaps (but know nothing about hal...).
Is there a log for that? The last upgrade was a little overdue and I think
about 150 packages were upgraded.
The output of lshal -u $(hal-find-by-capability --capability
input.touchpad) is:
udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input'
info.capabilities = {'input', 'input.touchpad'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
info.product = 'SynPS/2 Synaptics TouchPad' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input' (string)
input.device = '/dev/event7' (string)
input.originating_device = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
input.product = 'SynPS/2 Synaptics TouchPad' (string)
input.x11_driver = 'synaptics' (string)
input.x11_options.SHMConfig = 'On' (string)
linux.device_file = '/dev/event7' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/class/input/input7/event7' (string)
I hope it means more to you than it does to me. :)
--
Barry Samuels
http://www.beenthere-donethat.org.uk
The Unofficial Guide to Great Britain
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On 16/10/09 21:22:22, Barry Samuels wrote:
On 16/10/09 20:13:45, Andrew Sackville-West wrote:
On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote:
On Fri, 16 Oct 2009 18:42:05 +0100
Barry Samuels ba...@beenthere.mail1.co.uk wrote:
...
SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem
to be missing
What would that mean?
Not sure, but in the kernel config, there's something called
CONFIG_INPUT_DEV (Device Drivers / Input device support / Event
interface). From its help:
Say Y here if you want your input device events be accessible
under char device 13:64+ - /dev/input/eventX in a generic way.
To compile this driver as a module, choose M here: the
module will be called evdev.
Perhaps your kernel doesn't have this enabled?
It is enabled.
from the tone of the prior thread, I assume it's a stock kernel, so,
OP, let us know if it's not.
No it's not. I compile my own kernels.
Apropos the xorg log, if the synaptics module can't find the device
then it won't work, I would assume :)
Seems fair.
Can you provide the logs of what packages you upgraded that brought
about this failure? I'm thinking maybe this points to a hal problem,
perhaps (but know nothing about hal...).
Is there a log for that? The last upgrade was a little overdue and I
think
about 150 packages were upgraded.
The output of lshal -u $(hal-find-by-capability --capability
input.touchpad) is:
udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input'
info.capabilities = {'input', 'input.touchpad'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
info.product = 'SynPS/2 Synaptics TouchPad' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port_logicaldev_input' (string)
input.device = '/dev/event7' (string)
input.originating_device = '/org/freedesktop/Hal/devices/
platform_i8042_i8042_AUX_port' (string)
input.product = 'SynPS/2 Synaptics TouchPad' (string)
input.x11_driver = 'synaptics' (string)
input.x11_options.SHMConfig = 'On' (string)
linux.device_file = '/dev/event7' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/class/input/input7/event7' (string)
I hope it means more to you than it does to me. :)
Just noticed something. On my desktop event0, event1, mice, mouse0 etc are
in /dev/input but on the laptop they are in /dev and /dev/input has only
by-id and by-path
Is that significant?
--
Barry Samuels
http://www.beenthere-donethat.org.uk
The Unofficial Guide to Great Britain
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thinkpad Touchpad no longer works
On Fri, Oct 16, 2009 at 21:49:34 +0100, Barry Samuels wrote: On 16/10/09 21:22:22, Barry Samuels wrote: On 16/10/09 20:13:45, Andrew Sackville-West wrote: On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote: On Fri, 16 Oct 2009 18:42:05 +0100 Barry Samuels wrote: [...] SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem to be missing [...] Not sure, but in the kernel config, there's something called CONFIG_INPUT_DEV (Device Drivers / Input device support / Event interface). [...] Perhaps your kernel doesn't have this enabled? It is enabled. from the tone of the prior thread, I assume it's a stock kernel, so, OP, let us know if it's not. No it's not. I compile my own kernels. [...] The output of lshal -u $(hal-find-by-capability --capability input.touchpad) is: udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input' [...] input.device = '/dev/event7' (string) [...] linux.sysfs_path = '/sys/class/input/input7/event7' (string) I hope it means more to you than it does to me. :) Just noticed something. On my desktop event0, event1, mice, mouse0 etc are in /dev/input but on the laptop they are in /dev and /dev/input has only by-id and by-path Is that significant? Yes, it is; it probably means that something goes wrong when udev creates the device node for the touchpad. My first guess is that you upgraded to a newer version of udev, and that it now expects some novel piece of information that your custom kernel does not provide. (IOW, I side with Celejar and Andrew in suspecting your kernel configuration is the cause of your problems.) Please install the newest stock kernel and boot into it; this will immediately tell us if we are on the right track. Once we have established that, we can delve into the details to find the relevant setting. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
