UZ
Ulf Zibis
Sun, Aug 9, 2026 6:01 PM
Hi Judd,
much thanks for the long awaited update.
On my Ubuntu 24.04 the update happened automatically today before I noticed your latest messages. What a nice suprise. :-)
Now, when I start a HotSync, I only see this message (german), just before pressing the HotSync button, but no sync happens:
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
pi_bind error: usb: Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
What can I do to make HotSync work again?
-Ulf
Hi Judd,
much thanks for the long awaited update.
On my Ubuntu 24.04 the update happened automatically today before I noticed your latest messages. What a nice suprise. :-)
Now, when I start a HotSync, I only see this message (german), just before pressing the HotSync button, but no sync happens:
****************************************
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
****************************************
pi_bind error: usb: Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
What can I do to make HotSync work again?
-Ulf
JM
Judd Montgomery
Sun, Aug 9, 2026 10:06 PM
Hi Ulf,
Uh-oh. You can downgrade by specifying an older version.
Try installing pilot-link and do a "pilot-xfer -l". You might need do
do a "pilot-xfer -p usb: -l"
That will just list the databases and test that it will connect and do
something. Then we can see if its a jpilot or pilot-link problem.
Judd
On 8/9/26 14:01, Ulf Zibis wrote:
Hi Judd,
much thanks for the long awaited update.
On my Ubuntu 24.04 the update happened automatically today before I noticed your latest messages. What a nice suprise. :-)
Now, when I start a HotSync, I only see this message (german), just before pressing the HotSync button, but no sync happens:
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
pi_bind error: usb: Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
What can I do to make HotSync work again?
-Ulf
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Hi Ulf,
Uh-oh. You can downgrade by specifying an older version.
Try installing pilot-link and do a "pilot-xfer -l". You might need do
do a "pilot-xfer -p usb: -l"
That will just list the databases and test that it will connect and do
something. Then we can see if its a jpilot or pilot-link problem.
Judd
On 8/9/26 14:01, Ulf Zibis wrote:
> Hi Judd,
>
> much thanks for the long awaited update.
>
> On my Ubuntu 24.04 the update happened automatically today before I noticed your latest messages. What a nice suprise. :-)
>
> Now, when I start a HotSync, I only see this message (german), just before pressing the HotSync button, but no sync happens:
> ****************************************
> Abgleich mit usb:
> Hot-Sync Knopf jetzt drücken
> ****************************************
> pi_bind error: usb: Datei oder Verzeichnis nicht gefunden
> Check your sync port and settings
> Exit-Status: SYNC_ERROR_BIND
> Fertig.
>
> What can I do to make HotSync work again?
>
> -Ulf
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
JM
Judd Montgomery
Mon, Aug 10, 2026 4:12 AM
Ult, Good catch!
I built the debian packages without the enable-libusb config somehow. I
built new packages and pushed them up to packagecloud, so a simple apt
update && apt upgrade should install them.
Judd
On 8/9/26 18:06, Judd Montgomery wrote:
Hi Ulf,
Uh-oh. You can downgrade by specifying an older version.
Try installing pilot-link and do a "pilot-xfer -l". You might need do
do a "pilot-xfer -p usb: -l"
That will just list the databases and test that it will connect and do
something. Then we can see if its a jpilot or pilot-link problem.
Judd
On 8/9/26 14:01, Ulf Zibis wrote:
Hi Judd,
much thanks for the long awaited update.
On my Ubuntu 24.04 the update happened automatically today before I noticed your latest messages. What a nice suprise. :-)
Now, when I start a HotSync, I only see this message (german), just before pressing the HotSync button, but no sync happens:
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
pi_bind error: usb: Datei oder Verzeichnis nicht gefunden
Check your sync port and settings
Exit-Status: SYNC_ERROR_BIND
Fertig.
What can I do to make HotSync work again?
-Ulf
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Ult, Good catch!
I built the debian packages without the enable-libusb config somehow. I
built new packages and pushed them up to packagecloud, so a simple apt
update && apt upgrade should install them.
Judd
On 8/9/26 18:06, Judd Montgomery wrote:
> Hi Ulf,
>
> Uh-oh. You can downgrade by specifying an older version.
>
> Try installing pilot-link and do a "pilot-xfer -l". You might need do
> do a "pilot-xfer -p usb: -l"
>
> That will just list the databases and test that it will connect and do
> something. Then we can see if its a jpilot or pilot-link problem.
>
> Judd
>
> On 8/9/26 14:01, Ulf Zibis wrote:
>> Hi Judd,
>>
>> much thanks for the long awaited update.
>>
>> On my Ubuntu 24.04 the update happened automatically today before I noticed your latest messages. What a nice suprise. :-)
>>
>> Now, when I start a HotSync, I only see this message (german), just before pressing the HotSync button, but no sync happens:
>> ****************************************
>> Abgleich mit usb:
>> Hot-Sync Knopf jetzt drücken
>> ****************************************
>> pi_bind error: usb: Datei oder Verzeichnis nicht gefunden
>> Check your sync port and settings
>> Exit-Status: SYNC_ERROR_BIND
>> Fertig.
>>
>> What can I do to make HotSync work again?
>>
>> -Ulf
>> _______________________________________________
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Mon, Aug 10, 2026 8:22 AM
Hi Judd,
I'm the one who still has his Palm Treo 680 in daily use.
Now with apt update && apt upgrade at least pilot-xfer -p /dev/ttyUSB1 -l works.
But I still have to run sudo modprobe -a usbserial visor before.
What is the trick, that JPilot doesn't need that?
With JPilot the mentioned message disappeared, but HotSync still doesn't work:
$ jpilot -d
[.....]
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
command=100 [****************************************
]
command=100 [ Abgleich mit usb:
]
command=100 [ Hot-Sync Knopf jetzt drücken
]
command=100 [****************************************
]
jp_pref_write_rc_file()
paned pos = 681
jp_pref_write_rc_file()
output height = 293
Cancelling HotSync
caught signal SIGCHLD
paned pos = 681
jp_pref_write_rc_file()
output height = 293
[.....]
As you see, I still caught signal SIGCHLD on cancellation.
-Ulf
Am 10.08.26 um 06:12 schrieb Judd Montgomery:
Ult, Good catch!
I built the debian packages without the enable-libusb config somehow. I
built new packages and pushed them up to packagecloud, so a simple apt
update && apt upgrade should install them.
Judd
Hi Judd,
I'm the one who still has his Palm Treo 680 in daily use.
Now with apt `update && apt upgrade` at least `pilot-xfer -p /dev/ttyUSB1 -l` works.
But I still have to run `sudo modprobe -a usbserial visor` before.
What is the trick, that JPilot doesn't need that?
With JPilot the mentioned message disappeared, but HotSync still doesn't work:
$ jpilot -d
[.....]
****************************************
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
****************************************
command=100 [****************************************
]
command=100 [ Abgleich mit usb:
]
command=100 [ Hot-Sync Knopf jetzt drücken
]
command=100 [****************************************
]
jp_pref_write_rc_file()
paned pos = 681
jp_pref_write_rc_file()
output height = 293
****************************************
Cancelling HotSync
****************************************
caught signal SIGCHLD
paned pos = 681
jp_pref_write_rc_file()
output height = 293
[.....]
As you see, I still caught signal SIGCHLD on cancellation.
-Ulf
Am 10.08.26 um 06:12 schrieb Judd Montgomery:
> Ult, Good catch!
>
> I built the debian packages without the enable-libusb config somehow. I
> built new packages and pushed them up to packagecloud, so a simple apt
> update && apt upgrade should install them.
>
> Judd
JM
Judd Montgomery
Mon, Aug 10, 2026 10:49 AM
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
I'm the one who still has his Palm Treo 680 in daily use.
Now with apt update && apt upgrade at least pilot-xfer -p /dev/ttyUSB1 -l works.
But I still have to run sudo modprobe -a usbserial visor before.
What is the trick, that JPilot doesn't need that?
With JPilot the mentioned message disappeared, but HotSync still doesn't work:
$ jpilot -d
[.....]
Abgleich mit usb:
Hot-Sync Knopf jetzt drücken
command=100 [****************************************
]
command=100 [ Abgleich mit usb:
]
command=100 [ Hot-Sync Knopf jetzt drücken
]
command=100 [****************************************
]
jp_pref_write_rc_file()
paned pos = 681
jp_pref_write_rc_file()
output height = 293
Cancelling HotSync
caught signal SIGCHLD
paned pos = 681
jp_pref_write_rc_file()
output height = 293
[.....]
As you see, I still caught signal SIGCHLD on cancellation.
-Ulf
Am 10.08.26 um 06:12 schrieb Judd Montgomery:
Ult, Good catch!
I built the debian packages without the enable-libusb config somehow. I
built new packages and pushed them up to packagecloud, so a simple apt
update && apt upgrade should install them.
Judd
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
> Hi Judd,
>
> I'm the one who still has his Palm Treo 680 in daily use.
>
> Now with apt `update && apt upgrade` at least `pilot-xfer -p /dev/ttyUSB1 -l` works.
>
> But I still have to run `sudo modprobe -a usbserial visor` before.
>
> What is the trick, that JPilot doesn't need that?
>
> With JPilot the mentioned message disappeared, but HotSync still doesn't work:
>
> $ jpilot -d
>
> [.....]
>
> ****************************************
>
> Abgleich mit usb:
>
> Hot-Sync Knopf jetzt drücken
>
> ****************************************
>
> command=100 [****************************************
>
> ]
>
> command=100 [ Abgleich mit usb:
>
> ]
>
> command=100 [ Hot-Sync Knopf jetzt drücken
>
> ]
>
> command=100 [****************************************
>
> ]
>
> jp_pref_write_rc_file()
>
> paned pos = 681
>
> jp_pref_write_rc_file()
>
> output height = 293
>
> ****************************************
>
> Cancelling HotSync
>
> ****************************************
>
> caught signal SIGCHLD
>
> paned pos = 681
>
> jp_pref_write_rc_file()
>
> output height = 293
>
> [.....]
>
> As you see, I still caught signal SIGCHLD on cancellation.
>
> -Ulf
>
> Am 10.08.26 um 06:12 schrieb Judd Montgomery:
>
>> Ult, Good catch!
>>
>> I built the debian packages without the enable-libusb config somehow. I
>>
>> built new packages and pushed them up to packagecloud, so a simple apt
>>
>> update && apt upgrade should install them.
>>
>> Judd
>
> ---------------------------------------------------------------
>
> Jpilot mailing list -- jpilot@lists.jpilot.org
>
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Mon, Aug 10, 2026 12:31 PM
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Am 10.08.26 um 12:49 schrieb Judd Montgomery:
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Am 10.08.26 um 12:49 schrieb Judd Montgomery:
> Hi Ulf,
>
> Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
>
> Judd
>
> On August 10, 2026 4:22:01 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>
>
JM
Judd Montgomery
Mon, Aug 10, 2026 12:39 PM
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Am 10.08.26 um 12:49 schrieb Judd Montgomery:
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
> Hi Judd,
>
> thanks.
>
> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>
> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>
> Regards,
>
> -Ulf
>
> Am 10.08.26 um 12:49 schrieb Judd Montgomery:
>
>> Hi Ulf,
>>
>> Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
>>
>> Judd
>>
>> On August 10, 2026 4:22:01 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>
> ---------------------------------------------------------------
>
> Jpilot mailing list -- jpilot@lists.jpilot.org
>
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
JM
Judd Montgomery
Mon, Aug 10, 2026 1:08 PM
sudo apt install jpilot=2.0.2-1 worked for me.
On August 10, 2026 8:39:47 AM EDT, Judd Montgomery judd@jpilot.org wrote:
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Am 10.08.26 um 12:49 schrieb Judd Montgomery:
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
sudo apt install jpilot=2.0.2-1 worked for me.
On August 10, 2026 8:39:47 AM EDT, Judd Montgomery <judd@jpilot.org> wrote:
> About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
>
> You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
>
> On August 10, 2026 8:31:06 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>
>> Hi Judd,
>>
>> thanks.
>>
>> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>>
>> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>>
>> Regards,
>>
>> -Ulf
>>
>> Am 10.08.26 um 12:49 schrieb Judd Montgomery:
>>
>>> Hi Ulf,
>>>
>>> Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
>>>
>>> Judd
>>>
>>> On August 10, 2026 4:22:01 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>>
>> ---------------------------------------------------------------
>>
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>>
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>
> ---------------------------------------------------------------
>
> Jpilot mailing list -- jpilot@lists.jpilot.org
>
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
UZ
Ulf Zibis
Mon, Aug 10, 2026 1:17 PM
Ah, ok. I did:
$ sudo modprobe -r usbserial visor
modprobe: FATAL: Module usbserial is in use.
Now I can connect without visor, but only via -p /dev/ttyUSB1, not via usb, libusborusb:Is there another name or shortcut which can work? But I coudn't removeusbserial`.
===================
ich@W541:~$ pilot-xfer -p usb -l
Unable to bind to port: usb
Please use --help for more information
ich@W541:~$ pilot-xfer -p libusb -l
Unable to bind to port: libusb
Please use --help for more information
ich@W541:~$ pilot-xfer -p usb: -l
Listening for incoming connection on usb:... ^C
ich@W541:~$ pilot-xfer -p /dev/ttyUSB1 -l
Listening for incoming connection on /dev/ttyUSB1... connected!
Reading list of databases in RAM...
AddressingLibRecent-HsCh
MyTreoCASData
ADD053enUSSData
[......]
-Ulf
Am 10.08.26 um 14:39 schrieb Judd Montgomery:
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Ah, ok. I did:
$ sudo modprobe -r usbserial visor
modprobe: FATAL: Module usbserial is in use.
Now I can connect without `visor`, but only via `-p /dev/ttyUSB1`, not via `usb`, libusb` or `usb:`
Is there another name or shortcut which can work?
But I coudn't remove `usbserial`.
===================
ich@W541:~$ pilot-xfer -p usb -l
Unable to bind to port: usb
Please use --help for more information
ich@W541:~$ pilot-xfer -p libusb -l
Unable to bind to port: libusb
Please use --help for more information
ich@W541:~$ pilot-xfer -p usb: -l
Listening for incoming connection on usb:... ^C
ich@W541:~$ pilot-xfer -p /dev/ttyUSB1 -l
Listening for incoming connection on /dev/ttyUSB1... connected!
Reading list of databases in RAM...
AddressingLibRecent-HsCh
MyTreoCASData
ADD053enUSSData
[......]
====================
-Ulf
Am 10.08.26 um 14:39 schrieb Judd Montgomery:
> About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
>
> You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
>
> On August 10, 2026 8:31:06 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>
>> Hi Judd,
>>
>> thanks.
>>
>> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>>
>> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>>
>> Regards,
>>
>> -Ulf
UZ
Ulf Zibis
Mon, Aug 10, 2026 1:20 PM
Yes, I could go back to 2.0.2-1, but I prefer to use the new version.
What is missing, that it doesn't sync?
-Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
sudo apt install jpilot=2.0.2-1 worked for me.
On August 10, 2026 8:39:47 AM EDT, Judd Montgomery judd@jpilot.org wrote:
About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
On August 10, 2026 8:31:06 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Hi Judd,
thanks.
-
So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
-
But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
Regards,
-Ulf
Am 10.08.26 um 12:49 schrieb Judd Montgomery:
Hi Ulf,
Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
Judd
On August 10, 2026 4:22:01 AM EDT, Ulf Zibis Ulf.Zibis@CoSoCo.de wrote:
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Yes, I could go back to 2.0.2-1, but I prefer to use the new version.
What is missing, that it doesn't sync?
-Ulf
Am 10.08.26 um 15:08 schrieb Judd Montgomery:
> sudo apt install jpilot=2.0.2-1 worked for me.
>
> On August 10, 2026 8:39:47 AM EDT, Judd Montgomery <judd@jpilot.org> wrote:
>
>> About 9 hrs ago I rebuilt the pilot-link debs with libusb support and pushed them up to package cloud. It is version 0.15.0-2. It does not need the visor module and the visor module actually makes the libusb method not work.
>>
>> You'd have to downgrade to 2.0.2 and pilot-link 0.13.x. I can get the exact commands if you need them.
>>
>> On August 10, 2026 8:31:06 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>>
>>> Hi Judd,
>>>
>>> thanks.
>>>
>>> 1. So if I understand correct, pilot-link doesn't have an ABI to use libusb. That's the reason why the kernel module is needed.
>>>
>>> 2. But how can I make JPilot running, especially synching, again? With version 2.0.2 that worked fine over years, but now with 2.1.0 it doesn't work anymore. I had made no changes in settings.
>>>
>>> Regards,
>>>
>>> -Ulf
>>>
>>> Am 10.08.26 um 12:49 schrieb Judd Montgomery:
>>>
>>>> Hi Ulf,
>>>>
>>>> Sorry for my typo I did of your name. The visor module works over /dev/ttyUSB1. That was an older method before libusb. Try -p usb: , but the visor module cannot be loaded for that way to work. That's how you have jpilot configured according to your output.
>>>>
>>>> Judd
>>>>
>>>> On August 10, 2026 4:22:01 AM EDT, Ulf Zibis <Ulf.Zibis@CoSoCo.de> wrote:
>>> ---------------------------------------------------------------
>>>
>>> Jpilot mailing list -- jpilot@lists.jpilot.org
>>>
>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>> ---------------------------------------------------------------
>>
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>>
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
