Re: error message at gpilotd initialization
Landis McGauhey <[email protected]> Mon, 15 Jun 2009 07:37:51 -0700
| Newsgroups | gmane.comp.gnome.apps.pilot |
|---|---|
| Message-ID | <[email protected]> |
--===============1887116013== Content-Type: multipart/alternative; boundary=001485eb041eb5d7fc046c64005a --001485eb041eb5d7fc046c64005a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Andrew, thanks, that did it! JPilot is now good to go. Now, please bear with me here as this is uncharted territory for me-- do I need to write a shell script for init so this is done at every boot, or is doing it once permanent? Thanks again, Landis McGauhey North-Central California USA On Mon, Jun 15, 2009 at 7:05 AM, Andrew Greig <[email protected]>wrote: > On Mon, 2009-06-15 at 06:52 -0700, Landis McGauhey wrote: > > Nathan, thank you very much. Unfortunately, all of the USB nodes > > (there are several) available from the applet's drop-down list > > generate the same error message. By the way, the same is true of the > > USB nodes available from the drop-down list in JPilot. > > > > Keeping on eye on Nautilus open to /dev, I notice that every time the > > sync button is pressed on the PDA, nodes with very strange names like > > "usbdev2.29_ep81" appear in /dev. The suffix numeral of each new node > > increases by one digit with each new press of the sync button. > > > > I'm rather stymied at this point, but I know there's a solution and > > with the insight and help of everyone on the list, we'll find it. > > > > Thanks again, > > > > Landis McGauhey > > North-Central California USA > > > > On Mon, Jun 15, 2009 at 3:57 AM, Matt Davey <[email protected]> > > wrote: > > Landis, > > > > Just to be explicit: what you need to do is to fire up the > > gnome pilot > > configuration applet (either via your configuration menus, or > > run > > "gpilotd-control-applet" from a terminal window). > > > > Then, under the 'devices' tab, you need to edit the port, and > > where it > > says "/dev/pilot" you need to choose "usb:" from the dropdown > > menu. > > > > That should be all you need to do, but let us know how you get > > on. > > > > Matt > > > > > > On Sun, 2009-06-14 at 06:14 -0700, Nathan Owens wrote: > > > It sounds like your distributions is using libusb. If so, > > then just > > > choose "usb:device", as mentioned in the error message. You > > wouldn't > > > need to rebuild the kernel or anything like that. > > > > > > Nathan > > > > > <snip> > > I have grown weary of trying to get my LifeDrive to sync usng libusb, so > when that message comes up I just do > > # modprobe visor > > and get on with the business. At first I thought it was a mandriva > thing, but I suspect it may be my device not behaving as expected. > > Andrew Greig > > _______________________________________________ > gnome-pilot-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-pilot-list > --001485eb041eb5d7fc046c64005a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Andrew, thanks, that did it!=A0 JPilot is now good to go.=A0 Now, please be= ar with me here as this is uncharted territory for me-- do I need to write = a shell script for init so this is done at every boot, or is doing it once = permanent?<br> <br>Thanks again,<br><br>Landis McGauhey<br>North-Central California USA<br= ><br><div class=3D"gmail_quote">On Mon, Jun 15, 2009 at 7:05 AM, Andrew Gre= ig <span dir=3D"ltr"><<a href=3D"mailto:[email protected]">algreig@= bigpond.net.au</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, = 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><= div class=3D"h5">On Mon, 2009-06-15 at 06:52 -0700, Landis McGauhey wrote:<= br> > Nathan, thank you very much. =A0Unfortunately, all of the USB nodes<br= > > (there are several) available from the applet's drop-down list<br> > generate the same error message. =A0By the way, the same is true of th= e<br> > USB nodes available from the drop-down list in JPilot.<br> ><br> > Keeping on eye on Nautilus open to /dev, I notice that every time the<= br> > sync button is pressed on the PDA, nodes with very strange names like<= br> > "usbdev2.29_ep81" appear in /dev. =A0The suffix numeral of e= ach new node<br> > increases by one digit with each new press of the sync button.<br> ><br> > I'm rather stymied at this point, but I know there's a solutio= n and<br> > with the insight and help of everyone on the list, we'll find it.<= br> ><br> > Thanks again,<br> ><br> > Landis McGauhey<br> > North-Central California USA<br> ><br> > On Mon, Jun 15, 2009 at 3:57 AM, Matt Davey <<a href=3D"mailto:mcda= [email protected]">[email protected]</a>><br> > wrote:<br> > =A0 =A0 =A0 =A0 Landis,<br> ><br> > =A0 =A0 =A0 =A0 Just to be explicit: what you need to do is to fire up= the<br> > =A0 =A0 =A0 =A0 gnome pilot<br> > =A0 =A0 =A0 =A0 configuration applet (either via your configuration me= nus, or<br> > =A0 =A0 =A0 =A0 run<br> > =A0 =A0 =A0 =A0 "gpilotd-control-applet" from a terminal win= dow).<br> ><br> > =A0 =A0 =A0 =A0 Then, under the 'devices' tab, you need to edi= t the port, and<br> > =A0 =A0 =A0 =A0 where it<br> > =A0 =A0 =A0 =A0 says "/dev/pilot" you need to choose "u= sb:" from the dropdown<br> > =A0 =A0 =A0 =A0 menu.<br> ><br> > =A0 =A0 =A0 =A0 That should be all you need to do, but let us know how= you get<br> > =A0 =A0 =A0 =A0 on.<br> ><br> > =A0 =A0 =A0 =A0 Matt<br> ><br> ><br> > =A0 =A0 =A0 =A0 On Sun, 2009-06-14 at 06:14 -0700, Nathan Owens wrote:= <br> > =A0 =A0 =A0 =A0 > It sounds like your distributions is using libusb= . If so,<br> > =A0 =A0 =A0 =A0 then just<br> > =A0 =A0 =A0 =A0 > choose "usb:device", as mentioned in th= e error message. You<br> > =A0 =A0 =A0 =A0 wouldn't<br> > =A0 =A0 =A0 =A0 > need to rebuild the kernel or anything like that.= <br> > =A0 =A0 =A0 =A0 ><br> > =A0 =A0 =A0 =A0 > Nathan<br> > =A0 =A0 =A0 =A0 ><br> > =A0 =A0 =A0 =A0 <snip><br> <br> </div></div>I have grown weary of trying to get my LifeDrive to sync usng l= ibusb, so<br> when that message comes up I just do<br> <br> # modprobe visor<br> <br> and get on with the business. =A0At first I thought it was a mandriva<br> thing, but I suspect it may be my device not behaving as expected.<br> <font color=3D"#888888"><br> Andrew Greig<br> </font><div><div></div><div class=3D"h5"><br> _______________________________________________<br> gnome-pilot-list mailing list<br> <a href=3D"mailto:[email protected]">[email protected]</a= ><br> <a href=3D"http://mail.gnome.org/mailman/listinfo/gnome-pilot-list" target= =3D"_blank">http://mail.gnome.org/mailman/listinfo/gnome-pilot-list</a><br> </div></div></blockquote></div><br> --001485eb041eb5d7fc046c64005a-- --===============1887116013== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ gnome-pilot-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-pilot-list --===============1887116013==--