Date: Mon, 21 Feb 2011 14:10:05 -0600 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Fredrik Lindberg <fli@shapeshifter.se> Cc: freebsd-usb@freebsd.org Subject: Re: New uhso(4) device: Globetrotter HSUPA Modem Option N.V. Message-ID: <AANLkTimrahxyrATV=ukxXD2Meyw9UuMyt5qaLoW%2Bu1Fg@mail.gmail.com> In-Reply-To: <4D62B4E1.6070700@shapeshifter.se> References: <AANLkTi=YgTF434WgoF7w1B=y2rTBW_6Jqg3g3ncuy4-d@mail.gmail.com> <4D62A120.8040604@shapeshifter.se> <AANLkTikrhvNk%2Bk7jo5PLSPkTc22pT-5F=7Wr%2B87R2C_A@mail.gmail.com> <4D62B4E1.6070700@shapeshifter.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 21, 2011 at 12:54 PM, Fredrik Lindberg <fli@shapeshifter.se> wr= ote: > On 02/21/2011 07:28 PM, Brandon Gooch wrote: >> >> On Mon, Feb 21, 2011 at 11:30 AM, Fredrik Lindberg<fli@shapeshifter.se> >> =C2=A0wrote: >>> >>> 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 >>>> =DE=AD=EF=BF=BD=EF=BF=BD=EF=BF=BDT+CGDCONT=3D1,, >>>> 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=DE=AD=EF=BF=BD=EF=BF=BDa=DE=AD=EF=BF=BD=EF=BF=BDA=DE=AD=EF=BF=BD=EF= =BF=BDA=DE=AD=EF=BF=BD=EF=BF=BDA=DE=AD=EF=BF=BD=EF=BF=BDA=DE=AD=EF=BF=BD=EF= =BF=BDA=DE=AD=EF=BF=BD=EF=BF=BDA=DE=AD=EF=BF=BD=DE=AD=EF=BF=BD=EF=BF=BDA=DE= =AD=EF=BF=BD=DE=AD=EF=BF=BD=EF=BF=BD >>>> >>>> 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. =C2=A0Not connecting and not getting an serial > console is a bit different. =C2=A0From 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 OK, I have a kernel without VIMAGE running. Here's a run-down of the serial port connection attempts: ------------------------------------------------- uhso0: "Diagnostic" port at cuaU0 ------------------------------------------------- As per your instructions, I skipped it. ------------------------------------------------- uhso1: "Application" port at cuaU1 ------------------------------------------------- # cu -l /dev/cuaU1 AT Connected [GARBAGE RETURNED] ------------------------------------------------- uhso2: "Control" port at cuaU2 ------------------------------------------------- # cu -l /dev/cuaU2 Connected ...but then doesn't allow character input at all. ------------------------------------------------- uhso4: "Modem" port at cuaU4 ------------------------------------------------- # cu -l /dev/cuaU2 AT [NOTHING RETURNED] ...and any subsequent sequence of characters does nothing. Let me know if you'd like me to try anything else. -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimrahxyrATV=ukxXD2Meyw9UuMyt5qaLoW%2Bu1Fg>