OpenWrt Forum Archive

Topic: Overclocking

The content of this topic has been archived on 19 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I was wondering whether Openwrt is overclocking at all? Before you post a response of me being a little loopy just read the nex sentence. I recall that to sync with one of the chips (i think it's either wifi or switch) it's better to overclock the Broadcom WRT54g chip to 216 MHZ? This was apparently done for the Linksys stock firmware eventually even. I know that several other distros (Thibor and ddwrt) did this too. Are they overclocked to that speed for OpenWRT? I understand that it's not exactly a "faster" speed, but one more in sync with some components.


This post is somewhat vague:
http://forum.openwrt.org/viewtopic.php?id=9102

Is it good or not? Considering I was using Thibor for some time I guess my routers even ran at 216, so will it brick my router?

This post actually refers to specific problems that are fixed by this minor overclocking:
http://forum.openwrt.org/viewtopic.php?id=2937

(Last edited by napierzaza on 5 Aug 2007, 01:28)

Overclocking to 216 was to correct a specific issue on the WRT54G v2.2 only (which I happen to have).   I've run the v2.2 router at 216 with WhiteRussian without problems.  It's my understanding that you don't "have to" overclock any other WRT54G or GL versions - and (with the exception of the v2.2) it's generally not recommended.

(Last edited by regloss on 5 Aug 2007, 03:47)

I don't think the issue affected only the 2.2 model - I used to have a WRT54G 3.1 that came overclocked to 216MHz as well.

I have overclocked both my WRT54GS' (I think version 2) to 216 last night and as far as I can tell it is not any less stable. Speeds over my STA to AP link appear slightly faster but that might be because I updated one of the APs to Kamikaze 707.

Heehee,

Just so everyone knows, out of my 4 WRTs 2 of them bricked when I overclocked to 216!

Two were v2.1 WRT54GS (no problems)
One was a v2 WRT54G
One was a v2 WRT54GS

I was able to JTAG and erase nvram with total success, but I learned my lesson!

Oh, and thank you so much HairydairyMaid for making it so unbelievably easy to recover! It was almost a no brainer and once the cable was made and the headers were in, it was done! Really unbelievable, I've had so much trouble in other places (xbox modding, microcontroller projects) and the support is just not there!

(Last edited by napierzaza on 6 Aug 2007, 00:11)

My wrt54g v2 bricked at 216mhz with dd-wrt v.23sp2.
Everything else in my house is overclocked, and the router was feeling left out.

The JTAG guide made me laugh: All you need are 4 100 ohm resistors. If you don't have any 100 ohm resistors, here's how you make them...

I'm afraid the time required for me to solve this problem is worth more than the device, and this is a super excuse to upgrade to a Buffalo G54.

If anyone is interested in attempting to resurrect this router and make use of it, I will gladly send it to you for the cost of the shipping. Email me.

(Last edited by jonathanwrt on 11 Aug 2007, 04:22)

jonathanwrt wrote:

My wrt54g v2 bricked at 216mhz with dd-wrt v.23sp2.
Everything else in my house is overclocked, and the router was feeling left out.

The JTAG guide made me laugh: All you need are 4 100 ohm resistors. If you don't have any 100 ohm resistors, here's how you make them...

I'm afraid the time required for me to solve this problem is worth more than the device, and this is a super excuse to upgrade to a Buffalo G54.

If anyone is interested in attempting to resurrect this router and make use of it, I will gladly send it to you for the cost of the shipping. Email me.

I have been thinking of building a JTAG setup, but was afraid of toasting my own router, which is also a V2.  I'd be up for giving it a try...

It works, believe. I've had trouble with my parallel port in the past, and how annoying it can be. But the jtag cable just came together really simply. Not to mention how it was able to delete the nvram on the first try, and the router just come right back up.

jimboWRT wrote:
jonathanwrt wrote:

My wrt54g v2 bricked at 216mhz with dd-wrt v.23sp2.
Everything else in my house is overclocked, and the router was feeling left out.

The JTAG guide made me laugh: All you need are 4 100 ohm resistors. If you don't have any 100 ohm resistors, here's how you make them...

I'm afraid the time required for me to solve this problem is worth more than the device, and this is a super excuse to upgrade to a Buffalo G54.

If anyone is interested in attempting to resurrect this router and make use of it, I will gladly send it to you for the cost of the shipping. Email me.

I have been thinking of building a JTAG setup, but was afraid of toasting my own router, which is also a V2.  I'd be up for giving it a try...

Well folks, I ended up with that router mentioned in the grandparent quote above.  I spent a chunk of time getting this ready to JTAG, and today was able to give it a new life.

I'm going to look around the forum and/or the wiki and create a post with details of the process. 

I'm thinking of adding dual serial, maybe even SD and/or internal PoE support.  If I do those things, I'll document them as well.

Anyone have any suggestions about where I should post my pictures of the process?

I realise this thread's a bit old. But it's fairly newer than the other one I've been reading. So.

Try Flickr or Wikimedia,
or just imageshack.us it and post right here

This is my first post. I've been reading for a while before I registered. I just bricked my WRT54GS a few hours ago by overclocking it. I read up on this page linked below which helped alot (and is relevant to the topic in this thread too). It's linked on google directly. I'm connected directly to the net right now.

http://forum.openwrt.org/viewtopic.php?pid=12371

And I found this thread after registering. And decided it was time to post. The only thing left for me to do is the JTAG cable but I needed to ask something before I went on. The power keeps flashing when I turn the router on. That's supposed to mean it's being reset, aka bricked.

I got connected to the net when I was still trying to connect to the router. It just went right through to the WAN port. The ports 1-4 lights are blinking too and data is going through the router. It really doesn't look like something that's bricked, aside from the not booting or pinging or resetting to defaults if I hold the reset button for 40 seconds. Is this normal behaviour?

I also tried putting it in the freezer, that didn't work tongue

The discussion might have continued from here.