Shearwater Perdix test result, was Re: Fwd: Re: OSTC Sport bluetooth problem with Linux
Lutz Vieweg
lvml at 5t9.de
Tue Apr 4 14:34:07 PDT 2017
As promised earlier today, I just had a small window of opportunity this evening
to check whether downloading from a friend's just-bought Shearwater Perdix
(firmware release v44) with Subsurface under Linux works.
Hardware tested on:
- Desktop computer (AMD Ryzen 7 1800X, Asus X370 Pro)
- Bluetooth adapter: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(Bluetooth 4 LE capable, according to its specs)
Software:
- Arch Linux, linux-4.10.6 kernel
- bluez 5.44-1, bluez-utils 5.44
- subsurface 4.6.3-5
Pairing looked just fine: (serial numbers obfuscated with "*")
>> bluetoothctl
> [NEW] Controller 00:1A:7D:**:**:** ryzen [default]
> # agent KeyboardOnly
> Agent registered
> # default-agent
> Default agent request successful
> # scan on
> Discovery started
> [NEW] Device D4:60:3A:**:**:** Perdix
> # info D4:60:3A:**:**:**
> Device D4:60:3A:**:**:**
> Name: Perdix
> Alias: Perdix
> Paired: no
> Trusted: no
> Blocked: no
> Connected: no
> LegacyPairing: no
> # pair D4:60:3A:**:**:**
> Attempting to pair with D4:60:3A:**:**:**
> Pairing successful
> # connect D4:60:3A:**:**:**
> Attempting to connect to D4:60:3A:**:**:**
> Connection successful
> [CHG] Device D4:60:3A:**:**:** Connected: yes
> [NEW] Primary Service
> /org/bluez/hci0/dev_D4_60_3A_**_**_**/service000a
> 00001801-0000-1000-8000-00805f******
> Generic Attribute Profile
> [NEW] Primary Service
> /org/bluez/hci0/dev_D4_60_3A_**_**_**/service000b
> fe25c237-0ece-443c-b0aa-e02033******
> Vendor specific
> [NEW] Characteristic
> /org/bluez/hci0/dev_D4_60_3A_**_**_**/service000b/char000c
> 27b7570b-359e-45a3-91bb-cf7e70******
> Vendor specific
> [NEW] Descriptor
> /org/bluez/hci0/dev_D4_60_3A_**_**_**/service000b/char000c/desc000e
> 00002902-0000-1000-8000-00805f******
> Client Characteristic Configuration
> [NEW] Descriptor
> /org/bluez/hci0/dev_D4_60_3A_**_**_**/service000b/char000c/desc000f
> 00002901-0000-1000-8000-00805f******
> Characteristic User Description
> [CHG] Device D4:60:3A:**:**:** UUIDs: 00001800-0000-1000-8000-00805******
> [CHG] Device D4:60:3A:**:**:** UUIDs: 00001801-0000-1000-8000-00805******
> [CHG] Device D4:60:3A:**:**:** UUIDs: fe25c237-0ece-443c-b0aa-e0203******
> [CHG] Device D4:60:3A:**:**:** ServicesResolved: yes
> [CHG] Device D4:60:3A:**:**:** Paired: yes
> # trust D4:60:3A:**:**:**
> Changing D4:60:3A:**:**:** trust succeeded
> [CHG] Device D4:60:3A:**:**:** Trusted: yes
> # info D4:60:3A:**:**:**
> Device D4:60:3A:**:**:**
> Name: Perdix
> Alias: Perdix
> Paired: yes
> Trusted: yes
> Blocked: no
> Connected: yes
> LegacyPairing: no
> UUID: Generic Access Profile (00001800-0000-1000-8000-00805******)
> UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805******)
> UUID: Vendor specific (fe25c237-0ece-443c-b0aa-e02033******)
At this point I started Subsurface (under the same user), selected the
Shearwater/Perdix in the import logs dialog, checked the "download via bluetooth"
button, and chose the Perdix BT device that Subsurface presented.
But whenever I tried to start the download, the operation failed after a wait
time of ~5 seconds with a dialog stating:
> Insufficient privileges to open the device D4:60:3A:**:**:** Shearwater (Perdix)
"strace" did not reveal any "ENOPERM"-failing operations or such.
Regards,
Lutz Vieweg
More information about the subsurface
mailing list