problems downloading from predator in ubuntu 12.10

[Jan Schubert]

On 08.03.2013 03:49, Diego Mainou wrote:
> Hi Jan,
>
> Didn't try to hci1 it but simply removed the old pairing and paired it
> again from scratch with the original bundle rather than the on-board
> adapter.

Diego, using hci0 after pluging in the orginal dongle means you are
still using the built in one. Try something like 'sudo hciconfig -a' and
you should see a hci0 (built in) and a hci1 (Shearwater dongle). Try
pairing and binding to hci1, to make sure you should "shut down" hci by
something like 'sudo hciconfig hci0 down'.

Can you provide the output from 'lspci -vv' as well? This may help in
identifying what inbuilt BT device you have.

//Jan

> Wouldn't know which other driver to use.
>
> this is my machine... paid a premium just to avoid the Microsoft tax..
>
> https://www.system76.com/laptops/model/lemu4
>
>
> Diego Mainou
> +61 4 1515 2091
>
>
> On 8 March 2013 02:18, Jan Schubert <Jan.Schubert at gmx.li> wrote:
>> On 07.03.2013 13:39, Jef Driesen wrote:
>>> On 2013-03-07 13:29, Diego Mainou wrote:
>>>> Followed the manual  to pair the computer with no joy.
>>>>
>>>> Tried with the original blue tooth dongle and another two with no joy.
>>>>
>>>> I get: Slip RX: unexp. SLIP END
>>>>
>>>> Also have tried with the wifi  off. Haven't tried other drivers as I
>>>> wouldn't even know where to find them.
>>> I already received another report with a similar error, but I haven't
>>> found the problem yet.
>> Yeah this is common issue and is also seen in Windows some times. And
>> I've also seen this when trying JDiveLog on the same box where
>> ldc/subsurface worked fine, so the issue might be indeed on the software
>> side.
>>
>> Diego, just to make sure:
>> - when using the Original bluetooth dongle you used hci1 (instead of hci0)?
>> - you tried repairing (meaning delete the "old" pairing completely?)
>>
>> For the drivers: This surely depends on your hardware. For several
>> devices like on my MacBookPro there are proprietary closed source
>> drivers available and free open source ones as well. Maybe you can tell
>> us a little bit more about your hardware used.
>>
>> And lets hope Jef is able to find out something more detailed after you
>> provide a dump.
>>
>> //Jan
>>
>>