Hi Jr,

I`ve applied the patches by hand (had a little time to kill ;-) ). Everything seems ok so far. Tomorrow I´ll get an "UMTS" Card to test the connection to the provider. But as I said before everything looks good so far. BTW good job jr.

at first shot:

Mar 01 19:28:14 local Listening for Syslog messages on IP address: 192.168.173.50
Mar 01 19:29:12 192.168.173.1  dropbear[16378]: password auth succeeded for 'root' from 192.168.173.50:1181
Mar 01 19:30:25 192.168.173.11 syslogd started: BusyBox v1.1.0 (2006.02.28-10:30+0000)
Mar 01 19:30:35 192.168.173.11 pppd[1644]: pppd 2.4.3 started by root, uid 0
Mar 01 19:30:36 192.168.173.11 chat[1646]: timeout set to 120 seconds
Mar 01 19:30:36 192.168.173.11 chat[1646]: abort on (BUSY)
Mar 01 19:30:36 192.168.173.11 chat[1646]: abort on (ERROR)
Mar 01 19:30:36 192.168.173.11 chat[1646]: abort on (NO CARRIER)
Mar 01 19:30:36 192.168.173.11 chat[1646]: send (ATE1^M)
Mar 01 19:30:36 192.168.173.11 chat[1646]: expect (OK)
Mar 01 19:30:36 192.168.173.11 chat[1646]: ATE1^M^M
Mar 01 19:30:36 192.168.173.11 chat[1646]: OK
Mar 01 19:30:36 192.168.173.11 chat[1646]:  -- got it
Mar 01 19:30:36 192.168.173.11 chat[1646]: send (AT+CGDCONT=1,"IP","internet"^M)
Mar 01 19:30:37 192.168.173.11 chat[1646]: expect (OK)
Mar 01 19:30:37 192.168.173.11 chat[1646]: ^M
Mar 01 19:30:37 192.168.173.11 chat[1646]: AT+CGDCONT=1,"IP","internet"^M^M
Mar 01 19:30:37 192.168.173.11 chat[1646]: OK
Mar 01 19:30:37 192.168.173.11 chat[1646]:  -- got it
Mar 01 19:30:37 192.168.173.11 chat[1646]: send (ATD*99***1#^M)
Mar 01 19:30:37 192.168.173.11 chat[1646]: expect (CONNECT)
Mar 01 19:30:37 192.168.173.11 chat[1646]: ^M
Mar 01 19:30:37 192.168.173.11 chat[1646]: ATD*99***1#^M^M
Mar 01 19:30:37 192.168.173.11 chat[1646]: CONNECT
Mar 01 19:30:37 192.168.173.11 chat[1646]:  -- got it
Mar 01 19:30:37 192.168.173.11 chat[1646]: send (\d)
Mar 01 19:30:38 192.168.173.11 pppd[1644]: Serial connection established.
Mar 01 19:30:38 192.168.173.11 pppd[1644]: using channel 2
Mar 01 19:30:38 192.168.173.11 pppd[1644]: Using interface ppp0
Mar 01 19:30:38 192.168.173.11 pppd[1644]: Connect: ppp0 <--> /dev/usb/tts/0
Mar 01 19:30:39 192.168.173.11 pppd[1644]: sent [LCP ConfReq id=0x1 <asyncmap 0xa0000> <magic 0x2caef218>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: rcvd [LCP ConfReq id=0x3 <asyncmap 0x0> <auth chap MD5> <magic 0x82d684e> <pcomp> <accomp>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: No auth is possible
Mar 01 19:30:39 192.168.173.11 pppd[1644]: sent [LCP ConfRej id=0x3 <auth chap MD5> <pcomp> <accomp>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: rcvd [LCP ConfAck id=0x1 <asyncmap 0xa0000> <magic 0x2caef218>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: rcvd [LCP ConfReq id=0x4 <asyncmap 0x0> <magic 0x82d684e>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: sent [LCP ConfAck id=0x4 <asyncmap 0x0> <magic 0x82d684e>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
Mar 01 19:30:39 192.168.173.11 pppd[1644]: rcvd [LCP DiscReq id=0x5 magic=0x82d684e]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: rcvd [IPCP ConfNak id=0x1 <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: rcvd [IPCP ConfReq id=0x2]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: sent [IPCP ConfNak id=0x2 <addr 0.0.0.0>]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: rcvd [IPCP ConfNak id=0x2 <addr 172.17.167.98> <ms-dns1 193.254.160.1> <ms-dns3 193.254.160.130>]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: sent [IPCP ConfReq id=0x3 <addr 172.17.167.98> <ms-dns1 193.254.160.1> <ms-dns3 193.254.160.130>]
Mar 01 19:30:40 192.168.173.11 pppd[1644]: rcvd [IPCP ConfAck id=0x3 <addr 172.17.167.98> <ms-dns1 193.254.160.1> <ms-dns3 193.254.160.130>]
Mar 01 19:30:41 192.168.173.11 pppd[1644]: rcvd [IPCP ConfReq id=0x3]
Mar 01 19:30:41 192.168.173.11 pppd[1644]: sent [IPCP ConfAck id=0x3]
Mar 01 19:30:41 192.168.173.11 pppd[1644]: Could not determine remote IP address: defaulting to 10.64.64.64
Mar 01 19:30:41 192.168.173.11 pppd[1644]: not replacing default route to br0 [192.168.173.1]
Mar 01 19:30:41 192.168.173.11 pppd[1644]: local  IP address 172.17.167.98
Mar 01 19:30:41 192.168.173.11 pppd[1644]: remote IP address 10.64.64.64
Mar 01 19:30:41 192.168.173.11 pppd[1644]: primary   DNS address 193.254.160.1
Mar 01 19:30:41 192.168.173.11 pppd[1644]: secondary DNS address 193.254.160.130
Mar 01 19:30:41 192.168.173.11 pppd[1644]: Script /etc/ppp/ip-up started (pid 1729)
Mar 01 19:30:41 192.168.173.11 pppd[1644]: Script /etc/ppp/ip-up finished (pid 1729), status = 0x0

g3g card seems to work

I read all this thread... Thanks to JR for publishing the patches...
but I'm in trouble playing with patches and source code, sorry.
I'm wondering if it could be possible to have a copy of the firmware file already patched...
thanks to all of you...

I have tried to apply these patches too but get strange errors with my build:

root@OpenWrt:/# lsmod
Module                  Size  Used by    Tainted: P
ds                      7588   0
yenta_socket           12084   1
pcmcia_core            48208   0 [ds yenta_socket]
wlcompat               14896   0 (unused)
wl                    423640   0 (unused)
switch-robo             4412   0 (unused)
switch-core             4832   0 [switch-robo]

the status is ok so far:
root@OpenWrt:/# cardctl status
Socket 0:
  5V 16-bit PC Card
  function 0: [ready], [wp]

But I can't identify or access the card:
root@OpenWrt:/# cardctl ident
Socket 0:
  no product info available

and dmesg tells me:
root@OpenWrt:/# dmesg | tail
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!

So any ideas what's going wrong here?

Segmentation fault on cardctl. Anyone knows why?

I'm SO glad someone is doing this. I have the Verizon (V620) and I've been interested in this for months; in fact I was just looking for ways to hack a WRT54G to do this with something like mini pci-to-pci then pci-to-cardbus.

There's project called "stompbox" - http://stompboxnetworks.com - that has been going on for about a year- they have a working box built from scratch with boards from Soekris and a kernel that fits on a CF card. I'd prefer something more compact and cheaper to build tho so I've not tried it; their box looks good for use in a car or van but I'd love something I can throw in a carryon to take to conferences; that's why I've been checking out the WRT stuff (waiting for a newly-purchased WRT54G v2 from Ebay to get here; now I guess I've got to get my hands on the WRT54G3G...). 

I don't know how compatible the code is with OpenWrt but Stompbox uses Pebble Linux (Debian) - http://stompboxnetworks.com/buildit.html - the compiled image that fits on a Flash card is here: http://stompboxnetworks.com/cfimg.html - hopefully there's something that would work here.

(Last edited by LadyLinuX on 9 Apr 2006, 23:26)

hello.

I've got today the WRT543G. The same device arrived to my colleges.
We own a few PCMCIA Cards (Merlin U630 and Option Globetrotter 3G+ HSDPA Ready).

My colleges reported to me, that Merlin card works and Opton doesn't works.

I'm not so familiar with linux, so maybe you can help me to get the Opton Globetrotter 3G+ card to work.

I've made some research and I've founded theese links:

http://support.option.com/support/faq.p … ticleid=21

http://www.pharscape.org

http://www.pharscape.org/3G/gcom/ - command line utilty for linux for Globetrotter

http://www.pharscape.org/3G/nozomi.tgz - GlobeTrotter 3G/EDGE and FUSION+ (HSDPA) drivers

It is possible to get Option HSDPA Ready cards to work on WRT543G with theese files?

Best regards

(Last edited by pogarek on 12 Apr 2006, 19:31)

Yes nozomi drivers do work with OpenWrt. Just make sure you use exactly same flags that you compiled kernel with. On x86 it doesn't seem to matter, but with OpenWrt they must be identical.

thnx.

Maybe someone  already have compiled openwrt firmware with GlobeTrotter 3G/EDGE and FUSION+  support built in? My knowledge is too poor to handle this alone...... :-)

Thank you very much. :-)

Whats the chance of anyone putting toether a 'HOW' TO on this...

ok, I downloaded :

whiterussian_rc5.tar.bz2     (which compiled fine without any changes)
OpenWrt-SDK-Linux-i686-1.tar.bz2 
OpenWrt-ImageBuilder-Linux-i686.tar.bz2.

Compilation of OpenWrt-ImageBuilder-Linux-i686.tar.bz2 goes fine, but I don't know where I can put the nozomi drivers.

The compilation did not produced any firmware (or I can't find it), so I assume that it must be done ImageBuilder.
But when I execute 'make' under ImageBuilder directory (as described in Documentation) nothing happened.

So I asking for help with this or maybe for a compiled firmare...

The original GPL source for linksys also complied fine. Maybe will be easier to put support of my Opton to the original firmware?

Regards

If someone have compiled bins with cardbus support. Please make it available.

(Last edited by Marcel on 13 Apr 2006, 17:42)

Yes. I agree with that.

I wonder if someone will do that ,it will be with the carbus configuration via Web or not? :-)

I've noticed that cardbus support has a low priority :-( : https://dev.openwrt.org/ticket/53

(Last edited by pogarek on 13 Apr 2006, 19:12)

I've killed my WRT54G3G :-(

Power LED blinking all the time, device do not respond to pings.....

I'll have to use the JTAG interface.

Does WRT54G3G has exactly the same pins out as the other WRT54G?

Can I buy JTAG cable somewhere in the web?
EDIT: I've found this page: http://www.theforestnetworking.com/hardware.php. Are they sell a proper equipment for   WRT54G3G?

Can I flash by JTAG on Windows?

Regards

(Last edited by pogarek on 14 Apr 2006, 12:24)

@pogarek: a serial console is probably better to see what went wrong.

I've killed it by uplading changed Linksys original firmaware.

So it probably doesn't have a console...
WRT54G3G doesn't have a serial port.
I returned my device to service, but they will probably reject to repair it or replace to good one for free, so I'm preparing to open it when it comes back me and repair it by JTAG

Of course it has a serial port. I have a WRT54G3G as well.

where?????
How can I connect to it?

There's a row of 5 or 6 pins. I don't remember which one is which, but you can use a multimeter to figure it out...

ok.
So if service will sent me router back withour repait I'll try this before using JTAG.

Thank you.

I still looking for info abou JTAG socket and cables for buying :-)

You can make your own cable easily. Look inside of the http://downloads.openwrt.org/utils/Hair … ty_v45.zip file - IIRC you will find all the documentation in there...

Thnx. It's look simple to build JTAG cable..... :-)

WRT54G3G has the same pinouts as thees from PDF from your link?

How the command line shoud looke like for WRT54G3G?

My knowledge of electronic is poor. I believie that I can built the cable myself, but probably I'll look for othe skilled person, which will be make the cable and give me a little course.

I have never tried JTAG on that thing (never needed it...)
Just try it

I thought docs said you better have working serial console prior firmware hacking and not to return units to Linksys after killing them with bad flash..

Anyway see OpenWrt wiki for pinout. http://wiki.openwrt.org/OpenWrtDocs/Har … s/WRT54G3G

For JTAG better make sure power and GND pins match before blindly connecting it.

BTW. Mr.Packet - your email is broken. Tried to reply to email you sent, but it just bounced.

(Last edited by jr on 14 Apr 2006, 17:40)

JTAG works fine on the WRT54G3G.. THis is the only WRT i ever broke.