OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Rtm8000
XorA
post Apr 4 2007, 05:51 AM
Post #1





Group: Members
Posts: 101
Joined: 23-June 04
Member No.: 3,800



Has anyone managed to get an rtm8000 working on a zaurus with a 2.6.X kernel.

All I get is

CODE
Apr  4 14:48:26 p3n3tr4t0r local2.info chat[2319]: ATD*99#^M^M
Apr  4 14:48:26 p3n3tr4t0r local2.info chat[2319]: CONNECT
Apr  4 14:48:26 p3n3tr4t0r local2.info chat[2319]:  -- got it
Apr  4 14:48:26 p3n3tr4t0r local2.info chat[2319]: send (\k^M)
Apr  4 14:48:26 p3n3tr4t0r local2.info chat[2319]: timeout set to 5 seconds
Apr  4 14:48:26 p3n3tr4t0r daemon.info pppd[2317]: Serial connection established.
Apr  4 14:48:26 p3n3tr4t0r daemon.debug pppd[2317]: using channel 21
Apr  4 14:48:26 p3n3tr4t0r daemon.info pppd[2317]: Using interface ppp0
Apr  4 14:48:26 p3n3tr4t0r daemon.notice pppd[2317]: Connect: ppp0 <--> /dev/ttyS0
Apr  4 14:48:27 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:29 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:29 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:30 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:32 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:32 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:33 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:35 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:35 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:36 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:38 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:38 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:39 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:41 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:41 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:42 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:44 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:44 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:45 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:47 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:47 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:48 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:50 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:50 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:51 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:53 p3n3tr4t0r daemon.debug pppd[2317]: rcvd [LCP ConfReq id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:53 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfAck id=0x1 <auth pap> <pcomp> <accomp>]
Apr  4 14:48:54 p3n3tr4t0r daemon.debug pppd[2317]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xfaabbcda> <pcomp> <accomp>]
Apr  4 14:48:56 p3n3tr4t0r daemon.info pppd[2317]: Hangup (SIGHUP)
Apr  4 14:48:56 p3n3tr4t0r daemon.notice pppd[2317]: Modem hangup
Apr  4 14:48:56 p3n3tr4t0r daemon.notice pppd[2317]: Connection terminated.
Apr  4 14:48:58 p3n3tr4t0r daemon.info pppd[2317]: Exit.


Which is of no use at all, I am beginning to suspect a kernel bug.
Go to the top of the page
 
+Quote Post
zmiq2
post Apr 4 2007, 01:41 PM
Post #2





Group: Members
Posts: 385
Joined: 3-December 03
Member No.: 1,038



Hi,

I'm getting the same as you. I tried to fiddle with many setting, but got nowhere.

See my post at

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

I haven't tried the proposed fix yet; if you do, please write back your results.
Go to the top of the page
 
+Quote Post
XorA
post Apr 5 2007, 12:25 AM
Post #3





Group: Members
Posts: 101
Joined: 23-June 04
Member No.: 3,800



The proposed fix makes no difference. connect_delay delays the time until you start LCP negotiation. And you can see from the logs the card starts LCP fine.

I am pretty sure that anything the pppd sends is not making it to the card, but what the card sends makes it to pppd.

This seems to only affect pppd as I can start a connection in picocom and use +++ to halt it again. And all other AT commands I have tried work fine.

Luckilly I have 3 Zaurus machines so I tried the card on 2.4 kernel (Cacko 1.23 C860) and it works fine. As this is the same pppd version this leads me to think there is a bug somewhere in ppp/serial layers in the kernel. But I am not an expert at those. Serial was re-written for 2.6 though.
Go to the top of the page
 
+Quote Post
martschie
post Sep 30 2007, 06:29 AM
Post #4





Group: Members
Posts: 1
Joined: 30-September 07
Member No.: 20,770



Hi,

i had the same problem like XorA with a Fujitsu Siemens (FSC) connect2air card, these card is identical with the rtm-8000.

Output of cardctl ident:

product info: "GPRS Modem", "GPRS", "", ""
manfid: 0x0279, 0x950b
function: 2 (serial)


At the moment, i have the angstrom-distribution with a kernel version 2.6.22. The card is recognized as uart 16950/954, but in this configuration, minicom did not react to some commands. Then i read that this card is a uart 16550A, i changed this with setserial and then i could send commands in minicom. But the connection to the internet didn't work, and i had the output like XorA. In kernel version 2.4, there are no problems with this card and the uart 16550A. After two days search, i found this
http://www.webservertalk.com/archive216-2005-2-865933.html. There i read that you must set the uart to 16750. I did this and the connection was established.

Ok you must do the following: put the card in your zaurus, my device ist the ttyS4, and then type

setserial /dev/ttyS4 uart 16750
pccardctl reset

pccardctl reset is important, i forget it always and i wonder why does not work. Ok the thread is a little bit older but i hope i could help you, this is my first answer in this forum, sorry for my bad english

bye martin

Go to the top of the page
 
+Quote Post
zmiq2
post Oct 1 2007, 04:21 AM
Post #5





Group: Members
Posts: 385
Joined: 3-December 03
Member No.: 1,038



better late than never !!

I'll be trying this trick and I'll post back with my results.

Many thanks; I already quit the Z because the inability to get it connected...
Go to the top of the page
 
+Quote Post
XorA
post Oct 22 2007, 05:31 AM
Post #6





Group: Members
Posts: 101
Joined: 23-June 04
Member No.: 3,800



QUOTE(martschie @ Sep 30 2007, 03:29 PM) *
setserial /dev/ttyS4 uart 16750
pccardctl reset


I am a monkey, I could have sworn I had tried all the uart types must have missed this one.

Yes this works on rtm-8000
Go to the top of the page
 
+Quote Post
sdjf
post Jul 16 2008, 07:32 AM
Post #7





Group: Members
Posts: 454
Joined: 17-November 05
Member No.: 8,551



great job figuring that out! if you get tired of having to do all that typing every time you want to start a connection, then consider putting all the relevant commands into an alias or short script.

here are my explanations of these concepts for those of you who are not already experienced with them:

http://sdjf.esmartdesign.com/scripts/aliases.html

http://sdjf.esmartdesign.com/scripts/shortsh.html

you write script as a text file, with "#!/bin/bash" as the first line, do a "chmod 700 SCRIPTNAME" and then invoke it with ./SCRIPTNAME or remove the "./" and just enter the name if you move it into your path.

aliases are easier in some ways, harder in others, will let you read my writeups to decide for youself.

sdjf


This post has been edited by sdjf: Jul 16 2008, 07:37 AM
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 16th September 2014 - 03:33 PM