Audiovox Rtm8000 On R198 Options

[wrc4]

Has anyone tried Audiovox RTM8000 GPRS card on R198? It didn't work on my C1000. The result of running PPP dialer is as follows:

abort on (NO CARRIER)
abort on (NO DIALTONE)
abort on (BUSY)
send (^M)
expect (OK)

then after about a minute:

alarm
Failed
Connection script failed.

The card seemed to be recognized correctly. Here is the dmesg log:

pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0: detected caps 00000700 should be 00000100
0.0: ttyS0 at I/O 0xc4820400 (irq = 137) is a 16C950/954

The LED on the card was orange and blinking when inserted, and after several seconds it turned green.

[wrc4]

I saw a lot of discussions of GPRS card issue on this thread:

http://www.oesf.org/forums/index.php?showtopic=1382&hl=gprs

But I tried the same steps on R198 without success. I'm pretty sure the card is OK.

Are there anyone in this forum who still uses RTM8000 card?

[wrc4]

I tried minicom but still can't get anything back from the modem. I tried both ttyS0 and ttyS3, nothing was sent back for a "AT" command.

In the old thread (where people were talking about RTM8000 on 2.4 kernel roms), they always referred to ttyS3. But from dmesg it seems the card is using ttyS0.

In /sys/devices/platform/akita-ioexp/sharp-scoop.0/pxa2xx-pcmcia/0.0/

there is a file called tty:ttyS3, which is actually a link to ../../../../../../class/tty/ttyS3

I can't find the relationship among these facts, But I suspect that something is wrong.

[XorA]

You need to

setserial /dev/ttyS3 uart 16C550A

pccarcctl reset

to get card into right UART mode. Then minicom should talk to it.

[wrc4]

You need to

setserial /dev/ttyS3 uart 16C550A

pccarcctl reset

to get card into right UART mode. Then minicom should talk to it.

Thanks XorA! Minicom works!

I also got positive feedback from the PPP dialer Windows. However, after the connection is established, I see the following messages:

using channel 1
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS3
rcvd[LCP ConfReq id=0x01 <auth pap> <pcomp> <accomp>]
...

But finally:
Modem hangup

Connection terminated.

I'm still trying other methods...

[wrc4]

The error was after ATDT*99#, here is the log:

Serial connection established.
using channel 8
using interface ppp0
Connect: ppp0 <--> /dev/ttyS3
rcvd [LCP ConfReq id=0x02 <auth pap> <pcomp> <accomp>]
sent [LCP ConfReq id=0x01 <mru 1450> <asyncmap 0x0> <pcomp> <accomp>]
sent [LCP ConfAck id=0x02 <auth pap> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x02 <auth pap> <pcomp> <accomp>]
sent [LCP ConfAck id=0x02 <auth pap> <pcomp> <accomp>]
sent [LCP ConfReq id=0x01 <mru 1450> <asyncmap 0x0> <pcomp> <accomp>]

...(the last 3 lines above repeated 10 times. then)

Modem hangup
Connection terminated.

Does this mean authentication is failed? My ISP doesn't require user/password so I just use "1/1".

========Edit=========
I saw XorA and others' posts about this issue on other threads, (I should have searched all forums) I think this should be reported as a bug to the distribution maintainers.

[XorA]

As you will have seen in my other thread, I think this means what pppd sends the RTM8000 never receives, so it repeatedly asks for different LCP parameters until both sides give up because they can never agree. We arent actually as far as auth stage yet.

[wrc4]

As you will have seen in my other thread, I think this means what pppd sends the RTM8000 never receives, so it repeatedly asks for different LCP parameters until both sides give up because they can never agree. We arent actually as far as auth stage yet.

Thanks. I've submitted this as a bug in the pdaXrom bugtracker.