Prev: snapshot flag on subdirectory
Next: NYC LOCAL: Tuesday 6 July 2010 NYLUG: The Smalltalk System Pharo
From: Niklas R on 10 Jul 2010 13:07
On 6 Juli, 14:29, r...(a)rpw3.org (Rob Warnock) wrote:
> Niklas R  <nikla...(a)gmail.com> wrote:
> +---------------
> | r...(a)rpw3.org (Rob Warnock) wrote:
> | > 0. Use "user-mode PPP" rather than any kernel-resident version,
> | >    since you need to be able to issue & react to AT commands
> | >    [via the "term" command] more flexibly than any kernel-resident
> | >    versions I've run across. [Especially given #4 below!]
> |
> | OK: How? I am stuck like
> | # ppp
> | set device /dev/ugen1
> | term
> | then neither at nor any react
> +---------------
>
> Not sure I can parse your last line there...
>
> You should be seeing slightly more that you show above, namely:
>
>     # ppp
>     ...[chatter]...
>     ppp ON ${hostname}> term
>     ppp ON ${hostname}> set device /dev/ugen1
>     deflink: Entering terminal mode on /dev/ugen1       # Did you get this?!?
>     Type `~?' for help                                  # Or this?!?
>
> You should then be able to type AT commands to the modem.
> Note that until you have turned on command echoing you might *not*
> see your commands being echoed, but you should at least see the
> result codes coming back. E.g., if you type "at<RETURN>" your might
> not see the "at" echoed, but you should still see the "OK" response.
> Do you?
>
> If not, try connecting to the modem with some other program,
> e.g., with "cu":
>
>     # cu -l /dev/ugen1 -s 9600
>     Connected
>
>     at                  # Type this (followed by <RETURN>)
>     OK                  #   and you should get this response code.
>     at+csq              # Type this (followed by <RETURN>)
>     +CSQ: 14,99         #   and you should get this response code (or similar)
>     OK                  #   and this.
>
> Does that work for you? If not, you may need to first do the "AT+CFUN=1"
> I mentioned before.
>
> Anyway, I wouldn't worry about trying to make PPP work until you can
> type "AT" codes to the modem and get responses via "cu" [or equiv.],
>
> -Rob
>
> p.s. The fact that the device is showing up as "/dev/ugen1" and not as
> "/dev/cuau${N}" [for N a small digit, e.g., "/dev/cuau1" or "/dev/cuau2"],
> suggests that you don't have the proper driver to make your USB modem
> look like a serial port.
>
> -----
> Rob Warnock                     <r...(a)rpw3.org>
> 627 26th Avenue                 <URL:http://rpw3.org/>
> San Mateo, CA 94403             (650)572-2607

not as
"/dev/cuau${N}" [for N a small digit, e.g., "/dev/cuau1" or "/dev/
cuau2"],

Trace:
#ppp
Working in interactive mode
Working Add: Rounte failed: ff02::::errorno Operation not supported
Using interface: tun0
ppp ON fly-live>term
Working: deflink:/dev/cuaa1: Bad file descriptor
Failed to open /dev/cuaa1
ppp ON dly-live>set device...
Warning: at: Invalid command Failed
From: Niklas R on 15 Jul 2010 23:26
On Jul 6, 12:29 pm, r...(a)rpw3.org (Rob Warnock) wrote:
> Niklas R  <nikla...(a)gmail.com> wrote:
> +---------------
> | r...(a)rpw3.org (Rob Warnock) wrote:
> | > 0. Use "user-mode PPP" rather than any kernel-resident version,
> | >    since you need to be able to issue & react to AT commands
> | >    [via the "term" command] more flexibly than any kernel-resident
> | >    versions I've run across. [Especially given #4 below!]
> |
> | OK: How? I am stuck like
> | # ppp
> | set device /dev/ugen1
> | term
> | then neither at nor any react
> +---------------
>
> Not sure I can parse your last line there...
>
> You should be seeing slightly more that you show above, namely:
>
>     # ppp
>     ...[chatter]...
>     ppp ON ${hostname}> term
>     ppp ON ${hostname}> set device /dev/ugen1
>     deflink: Entering terminal mode on /dev/ugen1       # Did you get this?!?
>     Type `~?' for help                                  # Or this?!?
>
> You should then be able to type AT commands to the modem.
> Note that until you have turned on command echoing you might *not*
> see your commands being echoed, but you should at least see the
> result codes coming back. E.g., if you type "at<RETURN>" your might
> not see the "at" echoed, but you should still see the "OK" response.
> Do you?
>
> If not, try connecting to the modem with some other program,
> e.g., with "cu":
>
>     # cu -l /dev/ugen1 -s 9600
>     Connected
>
>     at                  # Type this (followed by <RETURN>)
>     OK                  #   and you should get this response code.
>     at+csq              # Type this (followed by <RETURN>)
>     +CSQ: 14,99         #   and you should get this response code (or similar)
>     OK                  #   and this.
>
> Does that work for you? If not, you may need to first do the "AT+CFUN=1"
> I mentioned before.
>
> Anyway, I wouldn't worry about trying to make PPP work until you can
> type "AT" codes to the modem and get responses via "cu" [or equiv.],
>
> -Rob
>
> p.s. The fact that the device is showing up as "/dev/ugen1" and not as
> "/dev/cuau${N}" [for N a small digit, e.g., "/dev/cuau1" or "/dev/cuau2"],
> suggests that you don't have the proper driver to make your USB modem
> look like a serial port.
It kind of does but cuaa0 and hangs infinitely using prompt. cuaa1 is
unrecognized. Kindly inform if any ideas or upgrading to newer BSD
gets preferred where function may be solved.
From: Warren Block on 16 Jul 2010 09:13
Niklas R <niklasro(a)gmail.com> wrote:
> It kind of does but cuaa0 and hangs infinitely using prompt. cuaa1 is
> unrecognized. Kindly inform if any ideas or upgrading to newer BSD
> gets preferred where function may be solved.

Possibly you should be using cuaU0, but since you haven't mentioned what
version of FreeBSD you are using, it's hard to say. A Dell U5520 is
mentioned three times in the u3g(4) source, so maybe that applies.

--
Warren Block * Rapid City, South Dakota * USA
From: Niklas R on 16 Jul 2010 09:20
On Jul 16, 1:13 pm, Warren Block <wbl...(a)wonkity.com> wrote:
> Niklas R <nikla...(a)gmail.com> wrote:
> > It kind of does but cuaa0 and hangs infinitely using prompt. cuaa1 is
> > unrecognized. Kindly inform if any ideas or upgrading to newer BSD
> > gets preferred where function may be solved.
>
> Possibly you should be using cuaU0, but since you haven't mentioned what
> version of FreeBSD you are using, it's hard to say.  A Dell U5520 is
> mentioned three times in the u3g(4) source, so maybe that applies.
>
> --
> Warren Block * Rapid City, South Dakota * USA
DragonflyBSD says Dell 5520 compatible with ppp and my spec
http://www.dragonflybsd.org/docs/user/delld830/ with
many thanks for informing now version is the Dragonflybsd entering
either infinite loop with cuaa0 or fails with cuaa1 this message sent
from same hardware which works with linux, so it's doable and just
matter of know-how..

From: Niklas R on 23 Jul 2010 11:33
Screenshot
http://image.bayimg.com/danhcaacn.jpg
Then maybe you know how to activate mobile broadband which Linux
already with GUI can live booted
First  |  Prev  | 
Pages: 1 2 3
Prev: snapshot flag on subdirectory
Next: NYC LOCAL: Tuesday 6 July 2010 NYLUG: The Smalltalk System Pharo