Hosed something up...


 

J. Winn

TVWBB Fan
I hadn't used my LinkMeter in awhile so I figured I should update it. I updated it through the web GUI and it finished successfully but then when I opened it back up everything was blanked out on the HeaterMeter page. I poked around the forums some and found out I had to update the LinkMeter software as well, that it was a communication problem between the two. I did that with opkg install http://capnbry.net/linkmeter/snapshots/trunk/packages/linkmeter_2_brcm47xx.ipk, unsuccessful the first time because I forgot about the reset button. The second time it went through successfully but now the web GUI wont load at all. I can still ssh though. What happened?

Edit: Now Im screwed, I went into the config file and changed the baud rate from 115200 to 38400 as seen in this post: http://tvwbb.com/showthread.php?36294-Upgrading-HeaterMeter-amp-LinkMeter. Now I cant get into to it at all and the green light on the front wont stop blinking. Please help!!
 
Last edited:
Did the green light ever stop blinking? I know for me sometimes it can take up to 5 minutes before it boots all the way up. If not, you can go over to openwrt and take a look at their guides and see if they have anything to help.

If worst comes to worst, you have to take the .bin file and use tftp to upgrade the router. Honestly this is the only way I've ever successfully updated my linkmeter. Read over on the openwrt site to learn how to do this.

I can't see anything that you did wrong. You do have to set the baud rate to 38400 to get it to work, but it should not have had any effect on the router booting.

dave
 
I believe I have the bin file, got it here: http://capnbry.net/linkmeter/snapshots/trunk/. I am not having any luck with this at all though. I'm using Mac TFTP Client. I've gotten a couple different errors but can find anywhere these error codes are listed to see what they mean. I've also gotten to where it looks like its going to transfer but then says no response from server. For some reason I'm only getting a self assigned ip address while connected so this may be where the no response message is coming from. Please help, pulling my hair out over here.
 
Ok, so I have it now connected via a patch cord to my home network. I can see it connected if I log into my router using the static IP Ive assigned to it. I can also ping it fine. However when I try to ssh to it the connection is refused and when i type in its ip into my browser I just get a failed to open page. I really have no idea what happened, I thought it would just be a simple upgrade. I wish now I would have just left it like it was.

Edit: I just went back and looked on my routers info page and now its not there so for some reason it disconnected.
 
Did you ever have ssh setup? If not use telnet.

To tftp to the router you have to get it in recovery mode, per the website. After it is in this mode you can hook it directly to your computer and you will be able to ping the router at 192.168.1.1 (I think, been a while since I did this). If this works you have to immediately tftp the bin to the router IP address. The timing can be annoying, but keep trying, eventually you will get it. The openwrt website has lots of info on the details, along with the tftp command to use.

dave
 
I've tried everything I can think of as well as everything I could come up with through searching but I can't figure this out. I have posted over at openwrt forums but so far no luck and it seems to be buried now so not sure if ill get any responses. I've posted some additional information over in that post if anybody here is able to help: https://forum.openwrt.org/viewtopic.php?id=40719
I figured it would just be an easy upgrade otherwise I would have just left it :-/. I've spent hours trying to figure this out now.
 
These sort of problems are incredibly difficult to troubleshoot. It seems these devices have a 50/50 chance of doing what they're designed to do sometimes, and most the failures come in packs.

The only advice I can give you is to try and get the TFTP working.
1) Plug a patch cable into a LAN port on the WRT54GL and into your home network.
2) From your computer, also on a wired connection on your home network, set your IP address to 192.168.1.254 netmask 255.255.255.0 no gateway.
3) Start a ping of 192.168.1.1, unplug and replug the power on the WRT54GL. If you do this a few times and never see any responses, I don't know what your next option is. Maybe holding the reset button while plugging in the power and holding it for 20 secs?

If you do see some pings coming back, try the TFTP client. Make sure you use the BIN file, not the TRX.
 
Well...I GOT IT!!! I dont know how but I finally got it to flash via TFTP. I tried an old netbook I have running windows instead of my MacBook. Maybe using the alternate TFTP client was it i dunno. Anyhow, what version of HeaterMeter and OpenWRT should I be running; whats the latest? Right now HeaterMeter version is 20121113B and OpenWRT is Attitude Adjustment (r29664) | Load: 0.01 0.04 0.05. Is this the latest? Thanks for the help trying to get this fixed too!
 
I have new problem now lol. A couple of the tabs, Network and Administration tabs for instance, give me a 500 Internal Server Error. So I can't re set up wifi and everything again. Any ideas? Do I have to reinstall the OpenWRT firmware (scary)? Also, I thought there were some alarm options in the newest HeaterMeter firmware but Im not seeing it anywhere. Thanks again guys!
 
Yeah the bcm47xx image gets updated a lot less frequently, as you can see it is a real pain in the butt sometimes to update. You can either update with the snapshot posted today or install the upgraded packages (with opkg install ): [code] http://home.capnbry.net:...he web interface seems like a bad idea to me.
 
Doing what Bryan describes is the first step. When pinging(ping -t -w 2 192.168.1.1) the router you need to try all known IP adresses that it could have used. If you get something like Destination not Available then you know the IP address is not correct or the router is not communicating. Any other responses are good and you can restore the router back to stock. You need to get the Stock bin file for the router version you have and this TOOL, will help. Following the Direction from this page will help you recover the router. http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash
 
I upgraded the firmware again using TFTP but now I cant get to the Administration tab to change the password. Something about
Code:
XML Parsing Error: not well-formed
Location: http://192.168.200.1/luci/;stok=d0e40471db0c7d15a9668204e19c3cbe/admin/system/admin/
Line Number 239, Column 57:	/usr/lib/lua/luci/dispatcher.lua:139: in function </usr/lib/lua/luci/dispatcher.lua:138></pre>
---------------------------------------------------------------^
Any suggestions?

Edit: Also getting a
Code:
wget: bad address 'capnbry.net'
Download failed
when i try and update HeaterMeter :-/(just ended up doing this by downloading hex file, still not sure why it wouldn't work though)
 
Last edited:
I'll have to investigate by wiping and reflashing my WRT54GL, but I'm probably not going to get a chance to do that until Sunday.
 
Ok cool thanks. Also, the network interfaces page has an error and won't load either. I think a may be able to fix the XML if I knew where to find it lol. Look forward to seeing what you come up with. Thanks again!
 
I haven't had time to get to this, but you may want to try booting the WRT54GL and then before you go to any other web page, going to
http://192.168.200.1/luci/admin/system/packages/

And installing
http://capnbry.net/linkmeter/snapshots/trunk/packages/linkmeter_2_brcm47xx.ipk

Then once that installs, reboot the device and see if it fixes anything. There's a bug in both the linksys and raspberrypi version that causes the web interface to error out if the config page is hit without there being a configuration object available at the time. It may not fix your problem but it is quick and doesn't require a tftp or losing your config or anything so it might be worth a try. Up to you though, because I'm still going to wipe my linksys and put the default back on to see if it works.
 
Just to add to this thread... I updated both the Router & Heatermeter code last week (on account of me getting my Sous Vide setup working). I screwed up the Linksys update and had to result in TFTP'ing to get back to working system. After the re-flash, mine exhibited the same web errors when trying to configure the network settings.

Luckily I had a backup configuration taken before and after... after a bit of comparing files I was able to manually (using terminal connection) edit the config files and successfully got the network setup working again.

I too will try the steps Bryan suggests
 

 

Back
Top