Uwatec Smart Com

Salvador Cuñat salvador.cunat at gmail.com
Mon Apr 15 11:46:04 PDT 2013


On Sun, Apr 14, 2013 at 09:56:14PM +0200, Jef Driesen wrote:
> On 14-04-13 21:46, Salvador Cuñat wrote:
> >On Sat, Apr 13, 2013 at 10:25:20PM +0200, himura.kenshin at libero.it wrote:
> >>then I get the message "Unable to open Uwatec Smart Com (/dev/ttyUSB0)". I'm
> >>
> >>Results of dmesg
> >>
> >>[46137.144980] usb 1-6: new high-speed USB device number 9 using ehci_hcd
> >>[46137.307259] IRDA-USB found at address 9, Vendor: 66f, Product: 4210
> >>[46137.307839] irda_usb_parse_endpoints(), And our endpoints are : in=02,
> >>out=01 (512), int=00[46137.346415] irda_usb_init_qos(), dongle says
> >>speed=0x17F, size=0x20, window=0x8, bofs=0x80, turn=0x4[46137.347530] IrDA:
> >>Registered device irda0[46137.349860] STIR421X: Couldn't upload patch
> >>[46137.384419] irda-usb: probe of 1-6:1.0 failed with error -2[46137.384452] ir-
> >>usb 1-6:1.0: IR Dongle converter detected[46137.384749] usb 1-6: IR Dongle
> >>converter now attached to ttyUSB0
> >>
> >It may also be a permissions problem (as I'd recently suffered with
> >debian-weezy, and got resolved in the last  debian upgrade).
> >
> >If Dirk's solution doesn't work give a try to:
> >
> >    #chmod a+rw /dev/ttyUSB0      (as root)
> >
> >If it works after this, you have to get permissions for the next
> >sessions, usually including your user in the group which ubuntu assigns
> >to the device.
> 
> The IrDA communication uses the socket api. So there are no device
> nodes that can have wrong permissions.
> 
> I didn't notice this message regarding the ttyUSB0 originally. I
> wonder if this is maybe the problem? If the IR dongle is tied to
> this device node (no idea how that happened), then maybe it can't be
> accessed by the socket interface at the same time?
> 
> Jef

Hi Jef.

It may be more than an only problem. There's, probably, a firmware issue
and then, perhaps the others.

http://ubuntuforums.org/showthread.php?t=1494756

The thread is quite old but the guy who wrote it resolved his problem
downloading the correct firmware and hacking a bit
/etc/default/irda-utils.

Really it's not the same ubuntu but the messages logged by dmesg are
exactly the same, except 

[ 2228.919514] usb 2-3: firmware: requesting 42101002.sb

which isn't logged for our friend Himura.

BTW the guy in the forum needed  /dev/irda0, which Himura don't because
he can use /dev/ttyUSB0, so first thing would be to get and install the
correct firmware.

BTW (again :-) ) it looks like it's the first time Himura uses the IR
device with ubuntu, being a quite old device, so ...

Himura:

Installing the firmware should resolve the error messages in the log.
Next thing, I think, would be search for ttyUSB0 (e.g. "ls -al
/dev/ttyUSB0"). If it exitst, then verify that the user can read the
device.
Hopefully it will work.
If don't, we can take a review to the issue.

Regards

Salva.


More information about the subsurface mailing list