Re: udev question
On Sat, 01 Jan 2011 16:13:34 -0500, Thomas H. George wrote: On Sat, Jan 01, 2011 at 04:56:50PM +, Camaleón wrote: Those steps are about how to sync your music/photos, but I think the most important part is the ifuse package that allows the device to be mounted as a mass storage devices. If you already have it installed, plug the device and check if it is listed as external unit. When plugged in I get just the output shown in my original post which includes a 40 digit serial number so I tried ifuse /media/ipod -u The_40_digit_serial_number The device was not found. Then I dunno what can be failing... maybe you are facing some kind of bug? :-? ifuse: Fails to recognize connected iPod touch http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563011 Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.02.11.49...@gmail.com
Re: udev question
On Sun, Jan 02, 2011 at 11:49:06AM +, Camaleón wrote: On Sat, 01 Jan 2011 16:13:34 -0500, Thomas H. George wrote: On Sat, Jan 01, 2011 at 04:56:50PM +, Camaleón wrote: Those steps are about how to sync your music/photos, but I think the most important part is the ifuse package that allows the device to be mounted as a mass storage devices. If you already have it installed, plug the device and check if it is listed as external unit. When plugged in I get just the output shown in my original post which includes a 40 digit serial number so I tried ifuse /media/ipod -u The_40_digit_serial_number The device was not found. Then I dunno what can be failing... maybe you are facing some kind of bug? :-? ifuse: Fails to recognize connected iPod touch http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563011 This bug describes my problem exactly - I'll track it and await resolution. Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.02.11.49...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110102185657.ga3...@tomgeorge.info
Re: udev question
On Fri, Dec 31, 2010 at 08:54:28AM +, Camaleón wrote: On Thu, 30 Dec 2010 13:00:32 -0500, Thomas H. George wrote: For Christmas I was given an ipod. When connected to a usb port the system (Debian Squeeze, linux-2.6.32-5-amd64 stock kernel) gives the following response. (...) Apple products are special devices. You need more than magic to get them working. There is a Debian wiki page about the iphone/ipod: http://wiki.debian.org/iPhone This link got me a bit further but seems to apply just to the iPhone. I followed the instructions anyway but the result was a connection to the ipod as a camera (The instructions say decline this option and I did but got the camera connection anyway). As yet I have found no way to undo this in order to try again. Ensure you have all the required packages installed, specially ifuse which seems to be the one in charge in mounting the device. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.31.08.54...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110101142651.ga10...@tomgeorge.info
Re: udev question
On Sat, 01 Jan 2011 09:26:51 -0500, Thomas H. George wrote: On Fri, Dec 31, 2010 at 08:54:28AM +, Camaleón wrote: There is a Debian wiki page about the iphone/ipod: http://wiki.debian.org/iPhone This link got me a bit further but seems to apply just to the iPhone. It should be for both :-) *** This page is intend to describe how Apple's iPhone and iPod Touch are supported in Debian (DebianSqueeze). For simplicity, both devices will be referred to as an iPhone. *** I followed the instructions anyway but the result was a connection to the ipod as a camera (The instructions say decline this option and I did but got the camera connection anyway). As yet I have found no way to undo this in order to try again. Those steps are about how to sync your music/photos, but I think the most important part is the ifuse package that allows the device to be mounted as a mass storage devices. If you already have it installed, plug the device and check if it is listed as external unit. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.01.16.56...@gmail.com
Re: udev question
On Sat, Jan 01, 2011 at 04:56:50PM +, Camaleón wrote: On Sat, 01 Jan 2011 09:26:51 -0500, Thomas H. George wrote: On Fri, Dec 31, 2010 at 08:54:28AM +, Camaleón wrote: There is a Debian wiki page about the iphone/ipod: http://wiki.debian.org/iPhone This link got me a bit further but seems to apply just to the iPhone. It should be for both :-) *** This page is intend to describe how Apple's iPhone and iPod Touch are supported in Debian (DebianSqueeze). For simplicity, both devices will be referred to as an iPhone. *** Perhaps it should work with the ipod but this is not guaranteed I followed the instructions anyway but the result was a connection to the ipod as a camera (The instructions say decline this option and I did but got the camera connection anyway). As yet I have found no way to undo this in order to try again. Those steps are about how to sync your music/photos, but I think the most important part is the ifuse package that allows the device to be mounted as a mass storage devices. If you already have it installed, plug the device and check if it is listed as external unit. When plugged in I get just the output shown in my original post which includes a 40 digit serial number so I tried ifuse /media/ipod -u The_40_digit_serial_number The device was not found. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.01.16.56...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110101211334.ga11...@tomgeorge.info
Re: udev question
On Thu, 30 Dec 2010 13:00:32 -0500, Thomas H. George wrote: For Christmas I was given an ipod. When connected to a usb port the system (Debian Squeeze, linux-2.6.32-5-amd64 stock kernel) gives the following response. (...) Apple products are special devices. You need more than magic to get them working. There is a Debian wiki page about the iphone/ipod: http://wiki.debian.org/iPhone Ensure you have all the required packages installed, specially ifuse which seems to be the one in charge in mounting the device. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.31.08.54...@gmail.com
udev question
For Christmas I was given an ipod. When connected to a usb port the system (Debian Squeeze, linux-2.6.32-5-amd64 stock kernel) gives the following response. Dec 30 10:14:22 dragon kernel: [ 3706.552517] usb 1-2: new high speed USB device using ehci_hcd and address 10 Dec 30 10:14:23 dragon kernel: [ 3706.688694] usb 1-2: New USB device found, idVendor=05ac, idProduct=129e Dec 30 10:14:23 dragon kernel: [ 3706.689111] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 30 10:14:23 dragon kernel: [ 3706.689507] usb 1-2: Product: iPod Dec 30 10:14:23 dragon kernel: [ 3706.689980] usb 1-2: Manufacturer: Apple Inc. Dec 30 10:14:23 dragon kernel: [ 3706.690553] usb 1-2: SerialNumber: 66defc9e5b6eaf7ab9a52dbfc6f5bccc64c0ebe7 Dec 30 10:14:23 dragon kernel: [ 3706.691369] usb 1-2: configuration #1 chosen from 4 choices but no /dev assignment. gtkpod is installed and the documentation states udev will create an assignment. In contrast, when my SanDisk mp3 player is attached to the usb port the response is Dec 30 12:41:07 dragon kernel: [12511.248018] usb 1-2: new high speed USB device using ehci_hcd and address 11 Dec 30 12:41:07 dragon kernel: [12511.396024] hub 1-0:1.0: unable to enumerate USB device on port 2 Dec 30 12:41:09 dragon kernel: [12513.596016] usb 1-2: new high speed USB device using ehci_hcd and address 12 Dec 30 12:41:10 dragon kernel: [12513.729571] usb 1-2: New USB device found, idVendor=0781, idProduct=74c2 Dec 30 12:41:10 dragon kernel: [12513.729945] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 30 12:41:10 dragon kernel: [12513.730323] usb 1-2: Product: SanDisk Sansa Fuze Dec 30 12:41:10 dragon kernel: [12513.730741] usb 1-2: Manufacturer: SanDisk Dec 30 12:41:10 dragon kernel: [12513.731294] usb 1-2: SerialNumber: DE0FF5024426B6A8 Dec 30 12:41:10 dragon kernel: [12513.731984] usb 1-2: configuration #1 chosen from 1 choice Dec 30 12:41:10 dragon kernel: [12513.735569] scsi9 : SCSI emulation for USB Mass Storage devices Dec 30 12:41:10 dragon kernel: [12513.736186] usb-storage: device found at 12 Dec 30 12:41:10 dragon kernel: [12513.736188] usb-storage: waiting for device to settle before scanning Dec 30 12:41:15 dragon kernel: [12518.736254] usb-storage: device scan complete Dec 30 12:41:15 dragon kernel: [12518.738598] scsi 9:0:0:0: Direct-Access SanDisk Sansa Fuze 4GB v02. PQ: 0 ANSI: 0 Dec 30 12:41:15 dragon kernel: [12518.739584] scsi 9:0:0:1: Direct-Access SanDisk Sansa Fuze 4GB v02. PQ: 0 ANSI: 0 Dec 30 12:41:15 dragon kernel: [12518.740955] sd 9:0:0:0: Attached scsi generic sg5 type 0 Dec 30 12:41:15 dragon kernel: [12518.741654] sd 9:0:0:1: Attached scsi generic sg6 type 0 Dec 30 12:41:15 dragon kernel: [12518.742218] sd 9:0:0:0: [sdd] 7683072 512-byte logical blocks: (3.93 GB/3.66 GiB) Dec 30 12:41:15 dragon kernel: [12518.747481] sd 9:0:0:0: [sdd] Write Protect is off Dec 30 12:41:15 dragon kernel: [12518.747944] sd 9:0:0:0: [sdd] Mode Sense: 04 00 00 00 Dec 30 12:41:15 dragon kernel: [12518.747947] sd 9:0:0:0: [sdd] Assuming drive cache: write through Dec 30 12:41:15 dragon kernel: [12518.758713] sd 9:0:0:1: [sde] Attached SCSI removable disk Dec 30 12:41:15 dragon kernel: [12518.773461] sd 9:0:0:0: [sdd] Assuming drive cache: write through Dec 30 12:41:15 dragon kernel: [12518.773940] sdd: Dec 30 12:41:15 dragon kernel: [12518.786470] sd 9:0:0:0: [sdd] Assuming drive cache: write through Dec 30 12:41:15 dragon kernel: [12518.786963] sd 9:0:0:0: [sdd] Attached SCSI removable disk and a new set of entries sdd, sdd1, etc is added in /dev. As an mp3 player the SanDisk Sansa is excellent and meets all my needs but I promised the family member who gave me the ipod I would try to create an app. I'm not sure I can do that but first I must gain access to the thing. Any help? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101230180032.ga10...@tomgeorge.info
UDEV Question
Anyone here have a Microtek SCSI scanner? In the past I've used scsiadd -s which would add the new device, this still works with udev but the symbolic link/permissions/etc are never created correctly. When I run the udev scan utility, my model does not have a specific name, just Scanner - but I have tried out / followed all the howtos and cannot get it to work 'automatically' - instead I have to ln -s /dev/device /dev/scanner chmod 666 /dev/device manually. Anyone else have issues getting udev to support their scanner when they 'hot-add' it with scsiadd -s? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: UDEV Question
Justin Piszcz [EMAIL PROTECTED] writes: Anyone here have a Microtek SCSI scanner? In the past I've used scsiadd -s which would add the new device, this still works with udev but the symbolic link/permissions/etc are never created correctly. When I run the udev scan utility, my model does not have a specific name, just Scanner - but I have tried out / followed all the howtos and cannot get it to work 'automatically' - instead I have to ln -s /dev/device /dev/scanner chmod 666 /dev/device manually. Anyone else have issues getting udev to support their scanner when they 'hot-add' it with scsiadd -s? I don't have a scanner, but if you give me the output of the following command: udevinfo -a -p `udevinfo -q path -n /dev/device` I might be able to help you write the rule to create the link to the node -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
udev creates /dev/hdc(burner) with permissions 640 and with owner root.hal. Therefore hal group members cannot burn. And any change is reversed on reboot. How can I tell udev to create it with permissions 660? Or should I just put it in a script to chmod /dev/hdc on every boot? 1. Use configuration files under /etc/udev/ to fix permissions of created device node on your system. 2. Use reportbug to submit bug report to udev package maintainer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
Kudret Güler wrote: udev creates /dev/hdc(burner) with permissions 640 and with owner root.hal. Therefore hal group members cannot burn. And any change is reversed on reboot. How can I tell udev to create it with permissions 660? Or should I just put it in a script to chmod /dev/hdc on every boot? On my system /dev/hdc (my burner) has permissions 660 and ownership root.cdrom. What version of udev do you have? Have you modified any files under /etc/udev? Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
On Thu, 2004-12-09 at 02:37 -0500, Kudret Güler wrote: udev creates /dev/hdc(burner) with permissions 640 and with owner root.hal. Therefore hal group members cannot burn. And any change is reversed on reboot. How can I tell udev to create it with permissions 660? Or should I just put it in a script to chmod /dev/hdc on every boot? a script at boot should be the very last resort. look in /etc/udev/permissions.d/ also at /etc/udev/udev.rules -- matt zagrabelny -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
On Thu, 09 Dec 2004 08:48:04 -0500, Adam Aube [EMAIL PROTECTED] wrote: root.cdrom. What version of udev do you have? Have you modified any files under /etc/udev? I hadn't modified any files then. udev version is 0.046-6 Maintainer informed me that it was a bug resolved in the next version. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284866 His work around worked for me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
Kudret Güler [EMAIL PROTECTED] writes: udev creates /dev/hdc(burner) with permissions 640 and with owner root.hal. Therefore hal group members cannot burn. And any change is reversed on reboot. How can I tell udev to create it with permissions 660? Or should I just put it in a script to chmod /dev/hdc on every boot? I think I actually just figured this out today. Check /etc/udev/rules.d. If there's only one file there, a soft link entitled z_hal_plugdev.rules or something (I'm away from my computer right now), there's your problem. Just copy (or, even better, link) udev.rules from the /etc/udev/ directory into the rules.d directory and run invoke-rc.d udev restart. Remember, though, you need to be in the plugdev group for this to work properly. I have no idea why udev.rules isn't in the rules directory to begin with. But moving it in there should do the trick. Best, Jesse -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
udev question
udev creates /dev/hdc(burner) with permissions 640 and with owner root.hal. Therefore hal group members cannot burn. And any change is reversed on reboot. How can I tell udev to create it with permissions 660? Or should I just put it in a script to chmod /dev/hdc on every boot? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
Sorry it took so long to get back to you, but I've been somewhat busy. Sam Halliday [EMAIL PROTECTED] writes: Sam Halliday writes: however... there is one major problem! instead of creating the link to /dev/input/mouseX, it is creating to the link to /dev/input/ts2, which does not appear to be a valid mouse device. how can i fix it? (ts2 appears only when the usb mouse is plugged in) Does ts2 appear when you are not using the udev rule you created? From what I can see from the udevinfo you posted, /dev/input/ts2 and /dev/input/mouse2 are the same exact device. I have no idea why the kernel would create the ts2 node (udev doesn't create /sys entries, only /dev entries, and ts2 is a /sys entry). How did you decide that /dev/input/ts2 is not a mouse device? Did you try to cat it and move the mouse around? -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
Derrick 'dman' Hudson [EMAIL PROTECTED] writes: Alternatively use /dev/input/mice and your application will receive input from all attached mice. Simple. :-) (with kernel 2.6 that includes USB -and- PS/2 mice) Interesting. I didn't know this. Just used the section that worked when I used 2.4. How do you differentiate between the two devices, though? For instance, my usb mouse has three buttons and my mousepad has only two. Right now I can set up the mousepad emulate 3-button mouse, but usb mouse doesn't. -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
Sam Halliday [EMAIL PROTECTED] writes: however... there is one major problem! instead of creating the link to /dev/input/mouseX, it is creating to the link to /dev/input/ts2, which does not appear to be a valid mouse device. how can i fix it? (ts2 appears only when the usb mouse is plugged in) Please post your udev rule. Also, post the output of udevinfo -p `udevinfo -q path -n /dev/input/ts2` -a and udevinfo -p `udevinfo -q path -n /dev/input/mouseX` -a where X is the number for the usb mouse. -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
John L Fjellstad wrote:
Sam Halliday writes:
however... there is one major problem! instead of creating the link to
/dev/input/mouseX, it is creating to the link to /dev/input/ts2, which
does not appear to be a valid mouse device. how can i fix it? (ts2
appears only when the usb mouse is plugged in)
Please post your udev rule.
BUS=usb, SYSFS{idProduct}=0201, SYSFS{product}=PS/2+USB Mouse,
NAME=input/%k, SYMLINK=usbmouse
Also, post the output of
udevinfo -p `udevinfo -q path -n /dev/input/ts2` -a
#
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/class/input/ts2':
SYSFS{dev}=13:130
follow the class device's device
looking at the device chain at
'/sys/devices/pci0001:01/0001:01:1b.0/usb2/2-1/2-1:1.0':
BUS=usb
ID=2-1:1.0
SYSFS{bAlternateSetting}= 0
SYSFS{bInterfaceClass}=03
SYSFS{bInterfaceNumber}=00
SYSFS{bInterfaceProtocol}=02
SYSFS{bInterfaceSubClass}=01
SYSFS{bNumEndpoints}=01
SYSFS{detach_state}=0
SYSFS{iInterface}=00
looking at the device chain at
'/sys/devices/pci0001:01/0001:01:1b.0/usb2/2-1':
BUS=usb
ID=2-1
SYSFS{bConfigurationValue}=1
SYSFS{bDeviceClass}=00
SYSFS{bDeviceProtocol}=00
SYSFS{bDeviceSubClass}=00
SYSFS{bMaxPower}=100mA
SYSFS{bNumConfigurations}=1
SYSFS{bNumInterfaces}= 1
SYSFS{bcdDevice}=0001
SYSFS{bmAttributes}=a0
SYSFS{detach_state}=0
SYSFS{devnum}=3
SYSFS{idProduct}=0201
SYSFS{idVendor}=1267
SYSFS{maxchild}=0
SYSFS{product}=PS/2+USB Mouse
SYSFS{speed}=1.5
SYSFS{version}= 1.10
looking at the device chain at '/sys/devices/pci0001:01/0001:01:1b.0/usb2':
BUS=usb
ID=usb2
SYSFS{bConfigurationValue}=1
SYSFS{bDeviceClass}=09
SYSFS{bDeviceProtocol}=00
SYSFS{bDeviceSubClass}=00
SYSFS{bMaxPower}= 0mA
SYSFS{bNumConfigurations}=1
SYSFS{bNumInterfaces}= 1
SYSFS{bcdDevice}=0206
SYSFS{bmAttributes}=c0
SYSFS{detach_state}=0
SYSFS{devnum}=1
SYSFS{idProduct}=
SYSFS{idVendor}=
SYSFS{manufacturer}=Linux 2.6.7-ibookg4-bootsplash ohci_hcd
SYSFS{maxchild}=3
SYSFS{product}=NEC Corporation USB
SYSFS{serial}=0001:01:1b.0
SYSFS{speed}=12
SYSFS{version}= 1.10
looking at the device chain at '/sys/devices/pci0001:01/0001:01:1b.0':
BUS=pci
ID=0001:01:1b.0
SYSFS{class}=0x0c0310
SYSFS{detach_state}=0
SYSFS{device}=0x0035
SYSFS{devspec}=/[EMAIL PROTECTED]/[EMAIL PROTECTED]
SYSFS{irq}=63
SYSFS{subsystem_device}=0x0035
SYSFS{subsystem_vendor}=0x1033
SYSFS{vendor}=0x1033
looking at the device chain at '/sys/devices/pci0001:01':
BUS=
ID=pci0001:01
SYSFS{detach_state}=0
#
udevinfo -p `udevinfo -q path -n /dev/input/mouseX` -a
where X is the number for the usb mouse.
#
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/class/input/mouse2':
SYSFS{dev}=13:34
follow the class device's device
looking at the device chain at
'/sys/devices/pci0001:01/0001:01:1b.0/usb2/2-1/2-1:1.0':
BUS=usb
ID=2-1:1.0
SYSFS{bAlternateSetting}= 0
SYSFS{bInterfaceClass}=03
SYSFS{bInterfaceNumber}=00
SYSFS{bInterfaceProtocol}=02
SYSFS{bInterfaceSubClass}=01
SYSFS{bNumEndpoints}=01
SYSFS{detach_state}=0
SYSFS{iInterface}=00
looking at the device chain at
'/sys/devices/pci0001:01/0001:01:1b.0/usb2/2-1':
BUS=usb
ID=2-1
SYSFS{bConfigurationValue}=1
SYSFS{bDeviceClass}=00
SYSFS{bDeviceProtocol}=00
SYSFS{bDeviceSubClass}=00
SYSFS{bMaxPower}=100mA
SYSFS{bNumConfigurations}=1
SYSFS{bNumInterfaces}= 1
SYSFS{bcdDevice}=0001
SYSFS{bmAttributes}=a0
SYSFS{detach_state}=0
SYSFS{devnum}=3
SYSFS{idProduct}=0201
SYSFS{idVendor}=1267
SYSFS{maxchild}=0
SYSFS{product}=PS/2+USB Mouse
SYSFS{speed}=1.5
SYSFS{version}= 1.10
looking at the device chain at '/sys/devices/pci0001:01/0001:01:1b.0/usb2':
BUS=usb
ID=usb2
SYSFS{bConfigurationValue}=1
SYSFS{bDeviceClass}=09
SYSFS{bDeviceProtocol}=00
SYSFS{bDeviceSubClass}=00
SYSFS{bMaxPower}= 0mA
SYSFS{bNumConfigurations}=1
SYSFS{bNumInterfaces}= 1
SYSFS{bcdDevice}=0206
SYSFS{bmAttributes}=c0
SYSFS{detach_state}=0
Re: udev question
On Wed, Jul 07, 2004 at 12:24:39PM -0400, Derrick 'dman' Hudson wrote: On Wed, Jul 07, 2004 at 03:09:31AM +0100, Sam Halliday wrote: [...] | i want to DISABLE the touchpad when the usb mouse is plugged in. Oh. I don't know how to do that as I've never tried (and never wanted to). I think some BIOSes support that (at least for PS/2 mice). Sorry I can't help with this. If you are using the touchpad driver in xfree86-driver-synaptics you can use the synclient program to disable and enable the touchpad: $ synclient TouchPadOff=[0|1] Work this into a hotplug script and you should be good to go. dt -- Dave Thayer | WARNING: Persons denying the existence of Denver, Colorado USA | robots may be robots themselves. [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
John L Fjellstad wrote:
Sam Halliday writes:
i would very much like to have a symlink set up by udev
(/dev/input/mousemain or similar) which points to the /dev/input/mouseX
unless it has been removed, in which case it should be pointed to
/dev/input/mouse1.
unfortunately the /dev/input/mouseX devices all remain when the usb mouse is
unplugged and reconnected.
snip
So, construct the udev rule:
BUS=usb, SYSFS{idProduct}=c012, SYSFS{product}=USB-PS/2 Optical Mouse,
NAME=input/%k, SYMLINK=usbmouse
hi there... i set this up, and udev seems to be creating the symlink dynamically
as expected.
however... there is one major problem! instead of creating the link to
/dev/input/mouseX, it is creating to the link to /dev/input/ts2, which does not
appear to be a valid mouse device. how can i fix it? (ts2 appears only when the
usb mouse is plugged in)
cheers,
Sam
--
Free High School Science Texts
http://www.nongnu.org/fhsst/
Sam's Homepages
http://fommil.homeunix.org/~samuel/
http://www.ma.hw.ac.uk/~samuel/
pgp8232zinYNL.pgp
Description: PGP signature
Re: udev question
On Wed, Jul 07, 2004 at 03:09:31AM +0100, Sam Halliday wrote: [...] | i want to DISABLE the touchpad when the usb mouse is plugged in. Oh. I don't know how to do that as I've never tried (and never wanted to). I think some BIOSes support that (at least for PS/2 mice). Sorry I can't help with this. -D -- Whoever loves discipline loves knowledge, but he who hates correction is stupid. Proverbs 12:1 www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: udev question
Sam Halliday [EMAIL PROTECTED] writes: You don't. In X, what you do is make one your primary mouse device, and the other just sends mouse events to the primary mouse device. So, at my place, the touchpad is the primary mouse device, and the usbmouse, when plugged in, sends mouse events through the primary mouse device. does that disable the touchpad when the usb mouse is plugged in? Not the way I set it up, but it's possible to do it. Take a look at hotplug. There is an event every time you plug in and take out an usb device (oncee when you insert the device, and once when you take it out). I would think it would be possible to set in a script to do what you want (changing X and possibly gpm). I really can't help you there, because I've never tried it. -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
Sam Halliday [EMAIL PROTECTED] writes: however that only solves half the problem... how can i make this /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1 (the touchpad) when the usb mouse is not plugged in? You don't. In X, what you do is make one your primary mouse device, and the other just sends mouse events to the primary mouse device. So, at my place, the touchpad is the primary mouse device, and the usbmouse, when plugged in, sends mouse events through the primary mouse device. I'm not sure how to do it on the console with gpm, since I don't use mouse on the console. Check out my website for how I set it up in X: http://www.fjellstad.org/projects/linuxlaptop.html -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
On Tue, Jul 06, 2004 at 10:51:10AM +0200, John L Fjellstad wrote: | Sam Halliday [EMAIL PROTECTED] writes: | | however that only solves half the problem... how can i make this | /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1 | (the touchpad) when the usb mouse is not plugged in? | | You don't. In X, what you do is make one your primary mouse device, | and the other just sends mouse events to the primary mouse device. So, | at my place, the touchpad is the primary mouse device, and the usbmouse, | when plugged in, sends mouse events through the primary mouse device. Alternatively use /dev/input/mice and your application will receive input from all attached mice. Simple. :-) (with kernel 2.6 that includes USB -and- PS/2 mice) | I'm not sure how to do it on the console with gpm, since I don't use | mouse on the console. Use the -M option to enable multiple mode and then specify the rest of the parameters as usual. (if you are using the /etc/gpm.conf file, then use the variable for extra paramters and put all of the gpm parameters in gpm's command line form there) HTH, -D -- If you want to know what God thinks about money, just look at the people He gives it to. -- Old Irish Saying www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: udev question
John L Fjellstad wrote: Sam Halliday [EMAIL PROTECTED] writes: however that only solves half the problem... how can i make this /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1 (the touchpad) when the usb mouse is not plugged in? You don't. In X, what you do is make one your primary mouse device, and the other just sends mouse events to the primary mouse device. So, at my place, the touchpad is the primary mouse device, and the usbmouse, when plugged in, sends mouse events through the primary mouse device. does that disable the touchpad when the usb mouse is plugged in? I'm not sure how to do it on the console with gpm, since I don't use mouse on the console. and thats the real killer... i want this setup for consoles as well. pgphmGbNJJd5v.pgp Description: PGP signature
Re: udev question
Derrick 'dman' Hudson wrote: John L Fjellstad wrote: | Sam Halliday writes: | | however that only solves half the problem... how can i make this | /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1 | (the touchpad) when the usb mouse is not plugged in? | | You don't. In X, what you do is make one your primary mouse device, | and the other just sends mouse events to the primary mouse device. So, | at my place, the touchpad is the primary mouse device, and the usbmouse, | when plugged in, sends mouse events through the primary mouse device. Alternatively use /dev/input/mice and your application will receive input from all attached mice. Simple. :-) (with kernel 2.6 that includes USB -and- PS/2 mice) thats not the point... i want to DISABLE the touchpad when the usb mouse is plugged in. and do it dynamically. this takes input from both all the time. pgpnS5KMwJFvI.pgp Description: PGP signature
Re: udev question
Sam Halliday [EMAIL PROTECTED] writes:
i would very much like to have a symlink set up by udev (/dev/input/mousemain or
similar) which points to the /dev/input/mouseX unless it has been removed, in
which case it should be pointed to /dev/input/mouse1.
unfortunately the /dev/input/mouseX devices all remain when the usb mouse is
unplugged and reconnected.
First you need to get SYSFS information and then plug it in.
Let me use my mouse as an example.
My usb mouse shows up as /dev/input/mouse2
Doing a udevinfo -n input/mouse2 -q path, gives me
/class/input/mouse2
Now, using the sys path, I can check for the sys variables, doing
udevinfo -p /class/input/mouse2 -a
Looking through the information, I see this:
looking at the device chain at '/sys/devices/pci:00/:00:1d.0/usb1/1-1':
BUS=usb
ID=1-1
SYSFS{bConfigurationValue}=1
SYSFS{bDeviceClass}=00
SYSFS{bDeviceProtocol}=00
SYSFS{bDeviceSubClass}=00
SYSFS{bMaxPower}= 98mA
SYSFS{bNumConfigurations}=1
SYSFS{bNumInterfaces}= 1
SYSFS{bcdDevice}=1320
SYSFS{bmAttributes}=a0
SYSFS{detach_state}=0
SYSFS{devnum}=3
SYSFS{idProduct}=c012
SYSFS{idVendor}=046d
SYSFS{manufacturer}=Logitech
SYSFS{maxchild}=0
SYSFS{product}=USB-PS/2 Optical Mouse
SYSFS{speed}=1.5
SYSFS{version}= 2.00
Now, pick up to SYSFS variables that would make the udev rule uniq, for
instance idProduct and product.
So, construct the udev rule:
BUS=usb, SYSFS{idProduct}=c012, SYSFS{product}=USB-PS/2 Optical Mouse,
NAME=input/%k, SYMLINK=usbmouse
Basically, this means, for USB device with idProduct this and product
that, create a node called input/%k (where %k is the kernel name for
the device), and a symlink called usbmouse (everything is relative to /dev).
Save this in a file like 05-mouse.rules, and store it in
/etc/udev/rules.d
Now, no matter what the kernel tells udev the mouse is named, udev will
create a symlink pointing to it.
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev question
John L Fjellstad wrote:
Sam Halliday writes:
i would very much like to have a symlink set up by udev
(/dev/input/mousemain or similar) which points to the /dev/input/mouseX
unless it has been removed, in which case it should be pointed to
/dev/input/mouse1.
unfortunately the /dev/input/mouseX devices all remain when the usb mouse is
unplugged and reconnected.
So, construct the udev rule:
BUS=usb, SYSFS{idProduct}=c012, SYSFS{product}=USB-PS/2 Optical Mouse,
NAME=input/%k, SYMLINK=usbmouse
thanks john!
however that only solves half the problem... how can i make this /dev/usbmouse
link (or whatever i call it) point to /dev/input/mouse1 (the touchpad) when the
usb mouse is not plugged in?
cheers,
Sam
--
Free High School Science Texts
http://www.nongnu.org/fhsst/
Sam's Homepages
http://fommil.homeunix.org/~samuel/
http://www.ma.hw.ac.uk/~samuel/
pgpOJXja2AHAO.pgp
Description: PGP signature
udev question
hi there, i was wondering if somebody could help me set up udev to make symlinks in a specific way... i have 2 mouse input devices... one is always connected (/dev/input/mouse1) and another is a usbmouse and appears as (/dev/input/mouseX), with X increasing every time i remove and reconnect it. i would very much like to have a symlink set up by udev (/dev/input/mousemain or similar) which points to the /dev/input/mouseX unless it has been removed, in which case it should be pointed to /dev/input/mouse1. unfortunately the /dev/input/mouseX devices all remain when the usb mouse is unplugged and reconnected. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
