Re: [Evolution] New system, once more for libusb
- From: Frederic Crozat <fcrozat mandriva com>
- To: evolution-list gnome org
- Subject: Re: [Evolution] New system, once more for libusb
- Date: Tue, 06 May 2008 09:28:23 +0200
Le mardi 06 mai 2008 à 14:54 +1000, Andrew Greig a écrit :
On Mon, 2008-05-05 at 23:09 -0430, Patrick O'Callaghan wrote:
On Tue, 2008-05-06 at 09:46 +1000, Andrew Greig wrote:
On Mon, 2008-05-05 at 12:58 -0430, Patrick O'Callaghan wrote:
On Tue, 2008-05-06 at 01:52 +1000, Andrew Greig wrote:
Hi All,
I have just upgraded to Mandriva 2008.1. I checked if the visor module
was loaded, and as it was I removed it
#rmmod visor
and checked that it was in fact absent.
Hit hot sync on my Palm Life Drive and lo and behold! visor is back
again.
I would really like to get libusb running this time. I have a faster
machine with usb2.0 native.
Here are some other specs:
[andrew andrew ~]$ rpm -q hal
hal-0.5.11-0.rc2.1mdv2008.1
[andrew andrew ~]$ rpm -q pilot-link
package pilot-link is not installed
[andrew andrew ~]$ rpm -q evolution-pilot
evolution-pilot-2.22.0-4mdv2008.1
[andrew andrew ~]$ rpm -q gnome-pilot
gnome-pilot-2.0.16-1mdv2008.1
What would be causing the re-installation of the visor module, please?
What else should I do?
AFAIK you *must* have pilot-link installed since everything else uses
it. Make sure your version of pilot-link is compiled with libusb. One
way to check:
# pilot-dlpsh -p usb:
should give you a small shell-like environment to poke around in your
Pilot. If the command fails, you need a different version of pilot-link.
poc
Thanks Patrick,
Now I have:
[root andrew andrew]# rpm -q pilot-link
pilot-link-0.12.3-2mdv2008.1
and when I run, as instructed:
[root andrew andrew]# pilot-dlpsh -i -p usb:
Listening for incoming connection on usb:..
Then I hit hotsync button, nothing happens until I type Ctrl C, and
cancel in the Palm, then I get back to a command prompt.
While still connected by the cable I get this>>>
andrew andrew ~]$ lsusb
Bus 001 Device 014: ID 0830:0061 Palm, Inc.
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0a5c:2021 Broadcom Corp.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 046d:c03d Logitech, Inc.
Bus 002 Device 002: ID 04b8:0005
So it is being detected by the system, OK.
What next, please?
Take a look at /usr/share/doc/pilot-link-0.12.3/README.libusb (that's
where it is on Fedora, YMMV). It has fairly precise instructions on how
to set everything up. One detail: you may need to copy or link the
60-libpisock.rules file into /etc/udev/rules.d (and restart udev if
necessary). The pilot-link install script doesn't put it there and on
Fedora it's not necessary, but I'm not familiar with Mandriva so it
might make a difference.
Oh, and make sure the 'visor' module is *not* loaded before starting
your tests.
poc
Thanks Patrick,
I tried # service -R
which restarts all running services, but saw no mention of udev so I
re-booted.
I noticed on reboot that there were lots of comments relating to each
line of the libpisockrules
they all related to an absence of group "dialout".
Shoud I run groupadd dialout and then put myself in that group?
No.
Also, there is this line in the /etc/udev/rules.d/60-dynamic.rules file:
# KERNEL=="ttyUSB[13579]*", RUN+="/bin/sh -c
'/etc/dynamic/scripts/visor.script &'"
which I have commented out as you can see, is this OK?
You don't have to touch these.
Just install pilot-link package. And no, it should not be a requirement
for it to be installed for programs linked with libpysock, like
gnome-pilot.
--
Frederic Crozat <fcrozat mandriva com>
Mandriva
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]