[PATCH] Add some troubleshooting to user manual

[Miika Turkia]

On Sat, Jun 29, 2013 at 6:50 PM, Bearsh <me at bearsh.org> wrote:

> Am 29.06.2013 06:45, schrieb Miika Turkia:
> > Let's cover at least the most common problem (modem manager interfering)
> > and also have instructions to dump debug log from the transfer.
> >
> > Signed-off-by: Miika Turkia <miika.turkia at gmail.com>
> > ---
> >  Documentation/user-manual.txt |   39
> ++++++++++++++++++++++++++++++++++++++-
> >  1 file changed, 38 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/user-manual.txt
> b/Documentation/user-manual.txt
> > index 63647f8..e5ba5c6 100644
> > --- a/Documentation/user-manual.txt
> > +++ b/Documentation/user-manual.txt
> > @@ -444,7 +444,11 @@ work for you :-).
> >  For downloading dives in subsurface you have then to specify
> '/dev/rfcomm0'
> >  as device name to use.
> >
> > -Troubleshooting:
> > +[[S_TroubleShooting]]
> > +Troubleshooting
> > +~~~~~~~~~~~~~~~
> > +**Bluetooth**
> > +
> >  Using Bluetooth for downloading from dive computers on Linux seems to
> be tricky
> >  some times. If you have issues please have a look to the following
> notes. Using
> >  a Shearwater Predator you may be able to pair but then encounter issues
> when
> > @@ -462,6 +466,39 @@ Please report issues and nonworking environments at
> >  http://trac.hohndel.org[our bugtracker] or send an email to
> >  mailto:subsurface at hohndel.org[our mailing list].
> >
> > +**USB**
> > +
> > +It is somewhat common that Modem Manager (or some other application)
> > +interferes with dive computers when using a USB serial connection. You
> > +might see errors similar to the following:
> > +
> > +     ERROR: Device or resource busy (16) [in serial_posix.c:107
> (serial_open)]
> > +     ERROR: Failed to open the serial port. [in oceanic_atom2.c:377
> (oceanic_atom2_device_open)]
> > +
> > +This often means that another application has opened the serial port
> > +in exclusive mode and should be disabled prior to connecting the dive
> > +computer.
> > +
> > +     sudo /etc/init.d/modemmanager stop
>
> maybe also mention the possibility to blacklist certain serial devices
> for modem manager (there mighty be people using it and also using a
> divecomputer the same time). see
> http://lists.hohndel.org/pipermail/subsurface/2013-June/006687.html
>
> as reference, my udev rule file:
> # cat /etc/udev/rules.d/77-my-mm-usb-device-blacklist.rules
> ACTION!="add|change", GOTO="mm_usb_device_blacklist_end"
> SUBSYSTEM!="usb", GOTO="mm_usb_device_blacklist_end"
> ENV{DEVTYPE}!="usb_device",  GOTO="mm_usb_device_blacklist_end"
>
> # beaglebone is not an modem device...
> ATTRS{idVendor}=="0403", ATTRS{idProduct}=="a6d0",
> ENV{ID_MM_DEVICE_IGNORE}="1"
> # std ftdi serial port adapter
> ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
> ENV{ID_MM_DEVICE_IGNORE}="1"
>
> LABEL="mm_usb_device_blacklist_end"
>
> Yep, it would make sense to add that too. Could you write that paragraph?

miika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20130629/8cee9ebe/attachment-0001.html>