simrel

I can communicate with the lg2030 phone at 115200 baud, using minicom. However I cannot do so at 230400 even though the phone menu offers a 230400 setting. Anyone knows how to get the phone to do 230400 baud.

I am using a local usb cable to connect my laptop to a 2030 lg phone and it works fine under win xp. I want to use the same thing under linux fc4. Does anyone know which drivers to use. WIndows lists it as an Ark MIcro usb to serial device. Thanks simrel

Thanks simrel but I am still stuck no cable manufaturer seems to to support Sharp Zaurus BTW How much did you get this cable for? And from where? -------- Sameer 33213[/snapback] This is the one I bought. http://www.gomadic.com/comipseradca.html The following may work for the Zaurus. http://www.serialio.com/products/adaptors/ZThinCableUSB.htm http://www.fivestarassoc.com/Z/ Try some of the Zaurus forums for more information.

I have used a cable from www.gomadic.com to connect lgrd2030 to an ipaq running linux. The gomadic cable converts the ipaq serial port to a regular rs232 serial port. You can then connect the reliance lf2030 cable to this port.

Reliance should have no problems providing 144k in the near future. This should start to happen as soon as the GSM folks provide EDGE services.

It seems the problem was due to a getty running on the same port. I can connect now, after killing the getty. I am using a serial cable so maybe that rules out connecting at 230400. The strongarm UART is not a standard one. To Greens Increasing speed to 230400 should help since the linux rconnect script comes with a setting of 115200 which is not enough to reach the 144k claimed by Reliance. One needs to increase the setting in the rconnect script as well as in the phone.

MInicom is just for testing. I get the same results for pppd. This is what happens on my laptop running fedore core 1. -> setserial -a /dev/rmodem /dev/rmodem, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 Baud_base: 115200, close_delay: 50, divisor: 0 closing_wait: 3000 Flags: spd_normal skip_test The phone is set to 115200 baud and it works fine Now I set the serial port to 230400 and the phone to 230400 -> setserial /dev/rmodem baud_base 230400 -> setserial -a /dev/rmodem /dev/rmodem, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 Baud_base: 230400, close_delay: 50, divisor: 0 closing_wait: 3000 Flags: spd_normal skip_test Now I cannot ccmmunicate with the modem even though everything is set to 230400 baud. You might want to know why I am doing all this. The laptop is not the problem as I can use it with 115200 which is fine. The real issue is my linux handheld. There the setserial command refuses to let me change the speed to anything other than 230400. Though 230400 does not work. Therefore I tried the above experiment to see if things work at 230400 at all, and it seems that they don't. even on the laptop. I just want it work on the handheld that's all, the speed is irrelevant. Here is what happens on my handheld (an ipaq running familiar linux 7.2) ~ # setserial -a /dev/ttySA0 /dev/ttySA0, Line 0, UART: undefined, Port: 0x0000, IRQ: 17 Baud_base: 230400, close_delay: 50, divisor: 0 closing_wait: 3000 Flags: spd_normal ~ # ~ # setserial /dev/ttySA0 baud_base 115200 Cannot set serial info: Invalid argument ~ # ~ # uname -a Linux familiar 2.4.19-rmk6-pxa1-hh30 #3 Wed Nov 12 11:07:41 EST 2003 armv4l unknown ~ # P.S. - Could the cable be a problem? It is not the original Reliance one but a clone.

Cables used for connecting pdas to mobile phones are commonly available in lengths less than 50cm. It does not make much make sense to lug around metres of cable to connect mobile devices, meant to be carried in the pocket.

How does one find out the balance remaining on prepaid coupons.

where could I find a cable for lg 2030 whihc is not more than 20 inches in length