Trying out a brand new Oceanic Geo 2.0 -- can't sync

Linus Torvalds torvalds at linux-foundation.org
Fri Jun 28 13:00:00 PDT 2013


Try doing

   rpm -e --nopdeps ModemManager

Followed by killing that silly daemon.

Or something similar. ModemManager is some crazy sh#t, and thinks all
serial ports are modems and tries to talk to them. That is usually the
reason for the "Device busy" errors.

It *might* also confuse the dive computer itself with silly probing IO, but
the other error you see might just also be due to some new protocol version
or whatever. But trying to get rid of modem manager first is worth a try,
just in case.

      Linus "sorry for the HTML crap" Torvalds

On Jun 28, 2013 9:27 AM, "Benjamin Kahn" <xkahn at zoned.net> wrote:
>
> I just received a brand new Oceanic Geo 2.0 for a dive trip next month.
> I won't have much network access, so I'd like to make sure I can connect
> my new dive computer to my Fedora 18 laptop before going.
>
> So far, I'm unable to connect.
>
> I've seen two types of errors. Sometimes I immediately get a permission
> error:
>
>         [0.000] ERROR: Device or resource busy (16) [in
serial_posix.c:107 (serial_open)]
>         [0.000] ERROR: Failed to open the serial port. [in
oceanic_atom2.c:377 (oceanic_atom2_device_open)]
>
> And sometimes, I get further. When this happens the DC appears to crash.
> Every element on the LCD turns black until I press one of the keys on
> the DC.  When this happens, I see this output to the console:
>
>         [0.112] ERROR: Unexpected answer start byte(s). [in
oceanic_atom2.c:287 (oceanic_atom2_send)]
>         [3.226] ERROR: Failed to receive the answer. [in
oceanic_atom2.c:281 (oceanic_atom2_send)]
>         [3.339] ERROR: Unexpected answer start byte(s). [in
oceanic_atom2.c:287 (oceanic_atom2_send)]
>         [3.449] WARNING: Uninitialized logbook entries detected! [in
oceanic_common.c:404 (oceanic_common_device_foreach)]
>         [6.453] ERROR: Failed to receive the answer. [in
oceanic_atom2.c:281 (oceanic_atom2_send)]
>
> HELP! :)
>
> Here's what I've tried so far:
>
> I have installed subsurface from the F18 repositories and have these
> versions:
>       * libdivecomputer-0.4.0-1.fc18.x86_64
>       * osm-gps-map-0.7.3-6.fc18.x86_64
>       * subsurface-3.1-1.fc18.x86_64
>
> I located a Windows computer and was able to connect to the DC (reading
> and writing) using the USB cable.
>
> (This DC is a pain: The cable is the serial modem. The DC waits 2
> minutes once it is connected to the cable looking for a command before
> reverting to watch mode again. Remove the DC from the cable for 10
> seconds after a connection is terminated before connecting again.)
>
> /var/log/messages shows that the cable is detected:
>
>         Jun 28 00:42:24 localhost kernel: [894764.927592] usb 1-1.2: new
full-speed USB device number 27 using ehci-pci
>         Jun 28 00:42:24 localhost kernel: [894765.009894] usb 1-1.2: New
USB device found, idVendor=0403, idProduct=f460
>         Jun 28 00:42:24 localhost kernel: [894765.009905] usb 1-1.2: New
USB device strings: Mfr=1, Product=2, SerialNumber=3
>         Jun 28 00:42:24 localhost kernel: [894765.009917] usb 1-1.2:
Product: 2002 Design,Inc. USB
>         Jun 28 00:42:24 localhost kernel: [894765.009922] usb 1-1.2:
Manufacturer: 2002 Design,Inc
>         Jun 28 00:42:24 localhost kernel: [894765.009926] usb 1-1.2:
SerialNumber: 20030001
>         Jun 28 00:42:24 localhost kernel: [894765.014762] ftdi_sio
1-1.2:1.0: FTDI USB Serial Device converter detected
>         Jun 28 00:42:24 localhost kernel: [894765.014871] usb 1-1.2:
Detected FT232BM
>         Jun 28 00:42:24 localhost kernel: [894765.014880] usb 1-1.2:
Number of endpoints 2
>         Jun 28 00:42:24 localhost kernel: [894765.014888] usb 1-1.2:
Endpoint 1 MaxPacketSize 64
>         Jun 28 00:42:24 localhost kernel: [894765.014895] usb 1-1.2:
Endpoint 2 MaxPacketSize 64
>         Jun 28 00:42:24 localhost kernel: [894765.014902] usb 1-1.2:
Setting MaxPacketSize 64
>         Jun 28 00:42:24 localhost kernel: [894765.016122] usb 1-1.2: FTDI
USB Serial Device converter now attached to ttyUSB0
>         Jun 28 00:42:24 localhost mtp-probe: checking bus 1, device 27:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
>         Jun 28 00:42:24 localhost mtp-probe: bus: 1, device: 27 was not
an MTP device
>
> I am in the correct groups:
>
>         $ groups
>         xkahn dialout lock wireshark
>         $ ls -l /dev/ttyUSB0
>         0 crw-rw----. 1 root dialout 188, 0 Jun 28 15:22 /dev/ttyUSB0
>
>
>
> _______________________________________________
> subsurface mailing list
> subsurface at hohndel.org
> http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20130628/1f398e50/attachment.html>


More information about the subsurface mailing list