J-Pilot and Handspring Visor
in [Debian]
|
Prev: ¡Ven y únete a LGN Prosperity!
Next: FW: Debian support on newer 4K Advanced format drives (rather than 512 bytes)
From: Marc Shapiro on 3 Jul 2010 22:40 No, this post did not just appear out of the ether after 10 years in limbo. Yes, I do own a Visor. I haven't used mine in ages, but my wife depends on hers. She has been syncing to her box at work (with that other OS), but it has been giving increasing trouble with newer versions of the OS. Now, her Visor appears to have died, as well. Since I am not using mine, I said that she could have it. But since here box at work bluescreens every time she tries to sync, I thought that it would be best to sync the Visor at home for backup. More convenient, too. My problem is that I can not get a connection when I try to sync. The visor is a great, but ancient device and the docs talk about using a "fairly new kernel, like 2.4.17". I am using 2.6.32 from backports and I have done 'modprobe visor' to load the module, but neither /dev/pilot, not /dev/ttyUSB1 are being created by udev. I have the Vendor and Product IDs from dmesg. How do I set up udev to create /dev/pilot when the hotsync button on the cradle is pressed -- Marc Shapiro mshapiro_42(a)yahoo.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/719051.65652.qm(a)web55501.mail.re4.yahoo.com
From: Florian Kulzer on 4 Jul 2010 05:50 [ Please wrap your lines at 72 characters for readability. ] On Sat, Jul 03, 2010 at 19:34:04 -0700, Marc Shapiro wrote: [...] > The visor is a great, but ancient device and the docs talk about using > a "fairly new kernel, like 2.4.17". I am using 2.6.32 from backports > and I have done 'modprobe visor' to load the module, but neither > /dev/pilot, not /dev/ttyUSB1 are being created by udev. I have the > Vendor and Product IDs from dmesg. Then why did you not include this information in your mail? > How do I set up udev to create /dev/pilot when the hotsync button on > the cradle is pressed? The first step is to check if your combination of USB vendor and USB device ID is listed in one of the alias lines of "modinfo visor". Udev tricks will most likely be useless if the kernel module does not recognize your device as being supported. -- Regards, | Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100704092436.GA4485(a)isar.localhost
From: Marc Shapiro on 4 Jul 2010 20:20 From: Florian Kulzer <florian.kulzer+debian(a)icfo.es> >On Sat, Jul 03, 2010 at 19:34:04 -0700, Marc Shapiro wrote: >> I have the Vendor and Product IDs from dmesg. > Then why did you not include this information in your mail? This is the output from dmesg: [637797.771076] usb 2-3.1: New USB device found, idVendor=082d, idProduct=0100 [637797.771083] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [637797.771087] usb 2-3.1: Product: Handspring Visor [637797.771090] usb 2-3.1: Manufacturer: Handspring Inc >> How do I set up udev to create /dev/pilot when the hotsync button on >> the cradle is pressed? > The first step is to check if your combination of USB vendor and USB > device ID is listed in one of the alias lines of "modinfo visor". Udev > tricks will most likely be useless if the kernel module does not > recognize your device as being supported. This is from the output from 'modinfo visor' (a command of which I was not aware. Thanks, Florian): filename: /lib/modules/2.6.32-bpo.3-686/kernel/drivers/usb/serial/visor.ko license: GPL description: USB HandSpring Visor / Palm OS driver author: Greg Kroah-Hartman <greg(a)kroah.com> alias: usb:v0E67p0002d*dc*dsc*dp*ic*isc*ip* <SNIP> alias: usb:v082Dp0100d*dc*dsc*dp*ic*isc*ip* depends: usbserial,usbcore vermagic: 2.6.32-bpo.3-686 SMP mod_unload modversions 686 parm: debug:Debug enabled or not (bool) parm: stats:Enables statistics or not (bool) parm: vendor:User specified vendor ID (ushort) parm: product:User specified product ID (ushort) That last alias line matches the vendor and product ID, so that looks good. So, is there a way to have udev created /dev/pilot when the hotsync button is pressed? -- Marc Shapiro mshapiro_42(a)yahoo.com -- Marc Shapiro mshapiro_42(a)yahoo.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/817947.84540.qm(a)web55504.mail.re4.yahoo.com
From: Florian Kulzer on 5 Jul 2010 14:30
On Sun, Jul 04, 2010 at 17:18:24 -0700, Marc Shapiro wrote: > From: Florian Kulzer [...] > This is the output from dmesg: > > [637797.771076] usb 2-3.1: New USB device found, idVendor=082d, idProduct=0100 > [637797.771083] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > [637797.771087] usb 2-3.1: Product: Handspring Visor > [637797.771090] usb 2-3.1: Manufacturer: Handspring Inc It does not report the creation of any device node; that is not good. (All the udev debugging tricks that I know require that I have at least one basic kernel name or subsystem path device node to start with.) > >> How do I set up udev to create /dev/pilot when the hotsync button on > >> the cradle is pressed? Does pressing the hotsync button when the visor is connected produce anything in the logs? (Note that I do not know much about this device; I am mostly trying to come up with suggestions based on what I know about the kernel and udev in general.) > > The first step is to check if your combination of USB vendor and USB > > device ID is listed in one of the alias lines of "modinfo visor". Udev > > tricks will most likely be useless if the kernel module does not > > recognize your device as being supported. > > This is from the output from 'modinfo visor' (a command of which I was not aware. Thanks, Florian): > > filename: /lib/modules/2.6.32-bpo.3-686/kernel/drivers/usb/serial/visor.ko > license: GPL > description: USB HandSpring Visor / Palm OS driver > author: Greg Kroah-Hartman <greg(a)kroah.com> > alias: usb:v0E67p0002d*dc*dsc*dp*ic*isc*ip* > <SNIP> > alias: usb:v082Dp0100d*dc*dsc*dp*ic*isc*ip* > depends: usbserial,usbcore > vermagic: 2.6.32-bpo.3-686 SMP mod_unload modversions 686 > parm: debug:Debug enabled or not (bool) > parm: stats:Enables statistics or not (bool) > parm: vendor:User specified vendor ID (ushort) > parm: product:User specified product ID (ushort) > > That last alias line matches the vendor and product ID, so that looks > good. So, is there a way to have udev created /dev/pilot when the > hotsync button is pressed? The main question is if any device node is created at all; if I remember your previous message correctly, you said that not even a /dev/ttyUSBx appears after you plug in the visor. That looks like a problem with the kernel module to me, even though it should know your device based on the modinfo-alias output. I propose to do the following: Run "tail -fn0 /var/log/syslog" in one terminal window so that you see all new syslog messages (until you hit CTRL-C to exit.) Then you can use another terminal window to try: - Load the visor module with debugging enabled "modprobe visor debug=1" and then plug in the device. - Tell the visor module explicitly that it should operate your device: "modprobe visor debug=1 vendor=0x082d product=0x0100". I would try both loading the module with these parameters and then connecting the visor, as well as loading the module like this with the visor already plugged in. (Unload the module with "modprobe -r visor" every time before you try changing parameters.) Hopefully the debug mode will result in some clues (or at least a good starting point for a targeted Google search) in the syslog. -- Regards, | Florian | -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100705181054.GA3924(a)isar.localhost |