Find the answer to your Linux question:
Results 1 to 2 of 2
Hi all. A few days ago, just after me updating to Wheezy and compiling the new 2.6.39 kernel, a very annoying problem occurred: each time I reboot, or just shutdown ...
  1. #1
    Just Joined!
    Join Date
    Jun 2011
    Posts
    2

    [ UDEV ] Input events number changes randomly

    Hi all. A few days ago, just after me updating to Wheezy and compiling the new 2.6.39 kernel, a very annoying problem occurred: each time I reboot, or just shutdown and turn on again, my pc ( an eeepc actually, asus 1000he ) the order of the input peripherals in /dev/input/ changes.

    As I obviously use an X server, it means I have to reconfigure it every time in order to match the new positions of the touchpad ( ETPS/2 Elantech Touchpad ).


    Code:
    root AT r4mp4g3 # cat /var/log/messages | grep ETPS
    
    May 31 14:06:23 r4mp4g3 kernel: [    4.977219] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    May 31 15:56:02 r4mp4g3 kernel: [    4.705204] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
    May 31 21:37:43 r4mp4g3 kernel: [    5.343306] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    May 31 21:41:11 r4mp4g3 kernel: [    5.761692] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    May 31 21:52:15 r4mp4g3 kernel: [    5.926064] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input9
    May 31 21:58:59 r4mp4g3 kernel: [    6.076515] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input3
    May 31 22:17:17 r4mp4g3 kernel: [    6.042610] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input3
    Jun  1 13:40:49 r4mp4g3 kernel: [    5.438608] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    Jun  1 16:11:18 r4mp4g3 kernel: [    5.209733] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    Jun  2 14:43:25 r4mp4g3 kernel: [    5.883634] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
    Jun  2 21:20:06 r4mp4g3 kernel: [    5.367956] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
    Jun  3 08:52:30 r4mp4g3 kernel: [    5.048471] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    Jun  3 21:11:02 r4mp4g3 kernel: [    5.499580] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    Jun  4 23:25:42 r4mp4g3 kernel: [    5.776980] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input9
    Jun  4 23:46:05 r4mp4g3 kernel: [    6.123490] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input9
    Jun  4 23:54:47 r4mp4g3 kernel: [    5.796949] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
    Code:
    root AT r4mp4g3 ~ # udevadm info -a -p /sys/class/input/event7
    
    custom logging function 0xb7aa9008 registered
    selinux=0
    runtime dir '/dev/.udev'
    calling: info
    device 0xb7aa90e0 has devpath '/devices/platform/i8042/serio1/input/input7/event7'
    
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    
      looking at device '/devices/platform/i8042/serio1/input/input7/event7':
        KERNEL=="event7"
        SUBSYSTEM=="input"
        DRIVER==""
    
    device 0xb7aa93e8 has devpath '/devices/platform/i8042/serio1/input/input7'
      looking at parent device '/devices/platform/i8042/serio1/input/input7':
        KERNELS=="input7"
        SUBSYSTEMS=="input"
        DRIVERS==""
        ATTRS{name}=="ETPS/2 Elantech Touchpad"
        ATTRS{phys}=="isa0060/serio1/input0"
        ATTRS{uniq}==""
        ATTRS{properties}=="0"
    
    device 0xb7aa9878 has devpath '/devices/platform/i8042/serio1'
      looking at parent device '/devices/platform/i8042/serio1':
        KERNELS=="serio1"
        SUBSYSTEMS=="serio"
        DRIVERS=="psmouse"
        ATTRS{description}=="i8042 AUX port"
        ATTRS{bind_mode}=="auto"
        ATTRS{reg_10}=="0x54"
        ATTRS{reg_11}=="0x88"
        ATTRS{reg_20}=="0x01"
        ATTRS{reg_21}=="0x60"
        ATTRS{reg_22}=="0x7f"
        ATTRS{reg_23}=="0x00"
        ATTRS{reg_24}=="0x00"
        ATTRS{reg_25}=="0x00"
        ATTRS{reg_26}=="0x00"
        ATTRS{debug}=="0x01"
        ATTRS{paritycheck}=="0x00"
        ATTRS{protocol}=="ETPS/2"
        ATTRS{rate}=="100"
        ATTRS{resolution}=="200"
        ATTRS{resetafter}=="5"
        ATTRS{resync_time}=="0"
    
    device 0xb7aaa308 has devpath '/devices/platform/i8042'
      looking at parent device '/devices/platform/i8042':
        KERNELS=="i8042"
        SUBSYSTEMS=="platform"
        DRIVERS=="i8042"
    
    device 0xb7aaa5a0 has devpath '/devices/platform'
      looking at parent device '/devices/platform':
        KERNELS=="platform"
        SUBSYSTEMS==""
        DRIVERS==""
    I tried to write a rule in udev in order to set a working symlink through a fixed location, such /input/touchpad, but with no luck.

    Code:
    root AT r4mp4g3 ~ # cat /etc/udev/rules.d/10-touchpad.rules
    #SUBSYSTEM=="input", ATTRS{phys}=="isa0060/serio1/input0", NAME="input/touchpad"
    
    SUBSYSTEM=="serio", ATTRS{description}=="i8042 Aux Port", KERNEL=="event?", SYMLINK="input/touchpad"
    I don't really know what to do. I even enabled udev logs during startup, but I found no trace of my rule, as It is ignored. But if I commit some syntax error, this is showed up.

    Any help? Thanks in advance

  2. #2
    Just Joined!
    Join Date
    Jun 2011
    Posts
    2
    nada?

    Does anyone know how to set up a working symlink?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •