Prev: snapshot flag on subdirectory
Next: NYC LOCAL: Tuesday 6 July 2010 NYLUG: The Smalltalk System Pharo
From: Niklas R on 7 Jul 2010 03:41
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

Seemingly getting sequence improved now in order gladly since first
instruction set device and then term now trying this sequence first
term, then set device loading bsd directly now very thankful
ppp ON ${hostname}> term
ppp ON ${hostname}> set device /dev/ugen1
deflink: Entering terminal mode on /dev/ugen1 # Did you get
this?!?
From: Niklas R on 7 Jul 2010 08:05
OK kind of surrendering now that both cu and ppp failed where ppp did
show
Typ '~?' for help
ppp ON dfly-live#
then fiasco AT command did not respond so tried cu
dfly-live#cu -l /dev/ugen1 -s 9600
Connected
User signal 1
ping cannot resolve: Host name lookup failure...
From: Niklas R on 7 Jul 2010 08:13
Card is listed compatible. http://leaf.dragonflybsd.org/cgi/web-man?command=ugensa&section=4
So should get doable. Kindly inform if you see my error:
dfly-live# ppp
Working in interactive mode
Using interface: tun0
ppp ON dfly-live>term
Warning: deflink: /dev/cuaa1: Bad file descriptor
failed to open /dev/cuaa1
ppp ON dfly-live>set device /dev/ugen1
ppp ON dfly-live>+ PACSP0
Warning: +: Invalid command
Warning: +: Failed 1
ppp ON dfly-live>at
Warning: at: Invalid command
Warning: at: Failed 1
From: Niklas R on 8 Jul 2010 00:08
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?
ppp ON dfly-live>at
Warning: at: Invalid command
Warning: at: Failed 1

Caps same result. Still hw appears compatible and listed compatible.
Kindly inform if doable. Anyways thanks
From: Niklas R on 10 Jul 2010 11:20
http://www.dragonflybsd.org/docs/user/delld830/ updating here somewhat
unresolved issue welcoming all discussion looking through this and
other threads carefully
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: snapshot flag on subdirectory
Next: NYC LOCAL: Tuesday 6 July 2010 NYLUG: The Smalltalk System Pharo