Date: Mon, 21 Feb 2011 19:54:25 +0100 From: Fredrik Lindberg <fli@shapeshifter.se> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: freebsd-usb@freebsd.org Subject: Re: New uhso(4) device: Globetrotter HSUPA Modem Option N.V. Message-ID: <4D62B4E1.6070700@shapeshifter.se> In-Reply-To: <AANLkTikrhvNk%2Bk7jo5PLSPkTc22pT-5F=7Wr%2B87R2C_A@mail.gmail.com> References: <AANLkTi=YgTF434WgoF7w1B=y2rTBW_6Jqg3g3ncuy4-d@mail.gmail.com> <4D62A120.8040604@shapeshifter.se> <AANLkTikrhvNk%2Bk7jo5PLSPkTc22pT-5F=7Wr%2B87R2C_A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/21/2011 07:28 PM, Brandon Gooch wrote: > On Mon, Feb 21, 2011 at 11:30 AM, Fredrik Lindberg<fli@shapeshifter.se> wrote: >> On 02/18/2011 01:58 AM, Brandon Gooch wrote: >>> >>> I've recently got my hands on an Option N.V. Globetrotter HSUPA Modem, >>> rev 2.00/0.00, addr 2. >>> >> [...] >>> >>> Also, I tried doing something like this (as per the uhso(4) man page): >>> >>> brandon@x300:~$ sudo cu -l /dev/cuaU2 >>> Connected >>> uhso2: failed to set ctrl line state to 0x01: USB_ERR_TIMEOUT >>> uhso2: failed to set ctrl line state to 0x03: USB_ERR_TIMEOUT >>> ޭ���T+CGDCONT=1,, >>> OK >>> uhso1: failed to set ctrl line state to 0x01: USB_ERR_TIMEOUT >>> uhso1: failed to set ctrl line state to 0x03: USB_ERR_TIMEOUT >>> _OWANCALL: 1, 1 >>> aޭ��aޭ��Aޭ��Aޭ��Aޭ��Aޭ��Aޭ��Aޭ�ޭ��Aޭ�ޭ�� >>> >>> That's where I'm stuck. >>> >> >> Hmm. Not sure whats going on here. >> Could you try the other serial ports (except the diagnostic one) with >> cu or minicom and see if you get the same result with those? >> > > I did, but seemed to get no response at all from the others, or > couldn't connect. > > I sent an updated message with debugging turned on, not sure if you > got it, I can re-send if needed. > > Thanks for helping out with this, the device in question is the model > we are now getting here at the university for our AT&T mobile > broadband accounts. I may be able to try out a recent Ubuntu or Fedora > to see what's happening there, but it could be a couple of days... > Yeah, I got that message. Not connecting and not getting an serial console is a bit different. From the output above it looks like random garbage on the serial port. Try connecting to all different serial ports (without uhsoctl running) with minicom or cu and try typing AT<enter>. (The diagnostic port doesn't work, so skip that one). Fredrik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D62B4E1.6070700>