Hi Jef Yes, I think I may be having issues with irda and Mint rather than Subsurface. Here's what I can see from dmesg:
usb 2-1.2: new full-speed USB device number 3 using ehci-pci usb 2-1.2: New USB device found, idVendor=066f, idProduct=4200 usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-1.2: Product: IrDA/USB Bridge usb 2-1.2: Manufacturer: Sigmatel Inc usbcore: registered new interface driver usbserial usbcore: registered new interface driver usbserial_generic usbserial: USB Serial support registered for generic usbcore: registered new interface driver option usbserial: USB Serial support registered for GSM modem (1-port) option 2-1.2:1.0: GSM modem (1-port) converter detected usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0 usbcore: registered new interface driver stir4200 Here's the libdivecomputer logfile: Subsurface: v4.7.6, built with libdivecomputer v0.7.0-devel-Subsurface-branch (8ae735a4d70307ebe2a42d315697f02ce71dbe88) ERROR: No dive computer found. [in uwatec_smart.c:182 (uwatec_smart_device_open)] I assume subsurface needs to find irda0?? On 3 February 2018 at 20:00, Jef Driesen <[email protected]> wrote: > On 03-02-18 18:05, Berthold Stoeger wrote: > >> On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote: >> >>> Hi Berthold - the subgear is irda, not bluetooth. It has worked >>> previously >>> on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3. >>> -- >>> >> >> Yes I know. Nevertheless, the "interface consistency fix" in commit >> d23bd46 >> enables the device field only for serial transport. >> >> To my defense - I just copied old buggy code, but made it more >> noticeable. I >> pushed a fix to github. If you can compile from source, you can use this. >> If >> not, there is a workaround: Select a dive computer with serial transport >> (I >> think the XP-Air is), change the device and then go back to the XP-10. >> This >> should be saved to the preferences, so you only have to do it once (until >> you >> change dive computer). >> > > The reason why the dropdown is disabled is because IrDA communication > doesn't use a device node at all. Libdivecomputer will automatically > discover the IrDA device address. So it doesn't matter what is shown in the > dropdown box, because it's not used for anything. > > If the download fails because no dive computer is found, that means the > discovery did not found any IrDA device (or at least not one that matches a > known dive computer). Enable the libdivecomputer logfile checkbox and send > us the log. That should tell us what is going on. > > Jef > > _______________________________________________ > subsurface mailing list > [email protected] > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface >
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
