So...you have an AC1450...but it shows as an R6300v2.
The FCC ID is the same for these two models...but they have different board_id numbers in the nvram settings. Somewhere along the line...your board_id got set to an R6300v2.
Good point; and... Hey Redhawk!
@macexperts You can also check the board_id (and all the other defaults) in mtd0, similarly as I mentioned above. Though a full reset should have fixed it... I have seen where some types of resets don't actually reset everything. Assuming this isn't a DD bug... _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Overclocking in the webUI was disabled a while ago... where you been?
Using OpenWRT mostly Lots of other various projects going on though.
But I did say I thought BS may have done so. Nothing a reset can't fix, if one knows what they're doing. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Wed Nov 10, 2021 9:12 Post subject: Re: partial success
jwh7 wrote:
macexperts wrote:
I did reset everything and go fresh in fact I'm still setting up everything. I toggled SPE / CTF and CTF was faster by far. From what I'm reading on some forums it seems DD-WRT is a bottleneck and people flashed back to factory to overcome it.
[...] PS I only see 800/600 in the clock
Ok cool BS may have restricted overclocking; or this model doesn't support it (the R6300v1 does not; but it's a totally different SoC). Try setting it manually*; backup your nvram in case you have to reset.
Check your `cat /proc/cpuinfo` output (or `dmesg|grep -i hz) before and after (if there's no frequency listed, go by the 'bogomips' field). Then check `nvram get clkfreq` for reference**. In telnet/ssh:
nvram set clkfreq=1000,666
nvram set overclocking=1000
nvram commit && reboot
The 'overclocking' parameter is to prevent DD from resetting 'clkfreq'. If it can overclock (stably, of course), that should almost proportionally increase CPU-bottlenecked NAT speed (25% for those playing at home).
* To compare, my EA6900's OEM nvram (& CFE) had clkfreq=800,533 while the third-party Xwrt CFE used 800,666. The datasheet for the memory showed it rated for a minimum of "667", and I've been running it (and now a 2nd) at 1000,666 for years. I reset the heatsink (from thermal pad to good compound) and drilled some holes in the top of the case to drop the temps down. Not necessary, but it will impress your friends and influence neighbors.
** To check the CFE default: `strings /dev/mtd0|grep clk`
I dusted off the old EA6900 which was sitting in the holiday home but my overclocking utility which I reinstated again (see picture) has 400, 533, 667, 800 as memory frequency
Should the default not be 667?
Furthermore The temps are over 70 Celsius is there a thread to open the router and reseat the heatsink?
Posted: Fri Nov 12, 2021 16:40 Post subject: Re: partial success
egc wrote:
I dusted off the old EA6900 which was sitting in the holiday home but my overclocking utility which I reinstated again (see picture) has 400, 533, 667, 800 as memory frequency
I imagine 667 is just a display value, and not from the actual pll table. Are you using an Xwrt CFE? Check your `strings /dev/mtd0|grep clkfreq`. Mine was 800,666, while the OEM was 800,533. Does your resultant clkfreq show '800,667'? And does dmesg report the speed? (out of town on vacation atm, so can't check)
egc wrote:
Furthermore The temps are over 70 Celsius is there a thread to open the router and reseat the heatsink?
I didn't post one for it, but I used a plastic separator tool to (carefully) open the lid; Linksys/Belkin/D-link cases are the worst. :-/ The heatsink has 3 screws I think, so my usual straight-edge razor blade to remove the old material, de-wax/grease solvent (I use PPG DX330; high-purity alcohol is prob ok), and little 330/400 then 600 grit wet-sanding if the surface is rough and/or un-flat. The case top has a grid structure inside, making hole drilling pretty easy (then a countersink to clean them up). I made 20 holes total, about 1/4"-5/16" or so. Dropped the steady-state temp quite a bit. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Lots of other various projects going on though.
Nothing a reset can't fix, if one knows what they're doing. 
BS may have restricted overclocking; or this model doesn't support it (the R6300v1 does not; but it's a totally different SoC). Try setting it manually*; backup your nvram in case you have to reset.
