hi,

I have a WRT54GS-DE with Linksys firmware 2.07.2.de,
hardware version 2.0, boot version 3.2.
I use the snapshot-20050126 file.
I set boot_wait to on.

both, netkit-tftp and atftp dont work:

jvc-tux wrt # tftp 192.168.1.1
tftp> binary
tftp> rexmt 1
tftp> trace
Packet tracing on.
tftp> put openwrt-gs-code.bin
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
sent WRQ <file=openwrt-gs-code.bin, mode=octet>
received ACK <block=0>
tftp>

jvc-tux wrt # atftp
tftp> connect 192.168.1.1
tftp> mode octet
tftp>
tftp> trace
Trace mode on.
tftp> put openwrt-gs-code.bin
sent WRQ <file: openwrt-gs-code.bin, mode: octet <>>
timeout: retrying...
sent WRQ <file: openwrt-gs-code.bin, mode: octet <>>
timeout: retrying...
sent WRQ <file: openwrt-gs-code.bin, mode: octet <>>
received ACK <block: 0>
sent DATA <block: 1, size: 512>
received ACK <block: 1>
sent DATA <block: 2, size: 512>
received ACK <block: 2>
sent DATA <block: 3, size: 512>
received ACK <block: 3>
sent DATA <block: 4, size: 512>
received ACK <block: 4>
.
.
.
.
sent DATA <block: 1644, size: 512>
received ACK <block: 1644>
sent DATA <block: 1645, size: 512>
received ACK <block: 1644>
sent DATA <block: 1645, size: 512>
tftp: error received from server <transfer cancelled>
tftp: aborting

where is my mistake?

thanks in advance
tom

the router ist directly connected on my notebook with an TP-cable.

I try to set the interface speed to 10mbitsHD - same
problem.

tom

If it's pingable it should be able to flash...

I have found that specifying

put openwrt-gs-code.bin code.bin

sometimes does the trick. Some of the bootloaders expect the file that's uploaded to be called "code.bin"  ...

I have exactly the same issue with a WRT54G_EU, hardware version 2.2, Linksys firmware 3.03.1_EU.

The FAQ suggests downgrading, however this is not possible because this is the oldest (and only) firmware that's supported for this hardware version.

I don't like having to use the web firmware upload because I'd like to know in advance if boot_wait and TFTP flashing works properly before I mess things up and need it.

Hmmmm ....some WRT54GS you can only flash if you use the lan connector with number 1 on the router ...

Done that. Makes no difference. But I noticed from other posts there are more people with this problem... just no solution.

Okay, I got it to work.

First I tried flashing the original Linksys firmware through TFTP, that didn't work either.

So I checked the Linksys knowledge base and decided to give their suggestion of using 10 Mbit, half duplex a try. The driver for my SIS900 didn't want to be set to that so I plugged it in my old Realtek 8029, and voila: there it went.

I'm now happily running OpenWRT experimental :-)

I am not very clear about it. Can somebody explain more about it please?

Well, I am looking forward to be able to run it too..

Ok, I figured out this too. Finally I have OpenWrt working on my Wrt54g.

Let me explain how I managed to overcome the problems:
This page http://linksys.custhelp.com/cgi-bin/lin … _topview=1   suggests using 10BaseT half duplex link. I used mii-tool to set link speed. Specifically I used:

mii-tool eth0 -F 10baseT-HD

Note that my linux laptop had Intel ethernet controller (82801DB) which failed to upload even after link adjustment. I uploaded the image to desktop linux which had "Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)" Ethernet controller (you can use lspci to check). I was able to upload the image from this one successfully. I have Ubuntu installed on this computer. I downloaded debian's tftp. You can get tftp for Ubuntu from this link:
http://linus.yhspatriot.net/cs/docs/ubu … TSPInstall

I hope this would be useful for you if you're experiencing this problem.