1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Thibor15b1 reports wrong CPU rev 1

Discussion in 'HyperWRT Firmware' started by dirtyclyde, May 7, 2006.

  1. dirtyclyde

    dirtyclyde Network Guru Member

    3 WRT54GS V2.1 GSv3_Thibor15b1 Firmware

    Thibor14 CPU: BCM4712 rev 2 at 216 MHz
    Thibor15b1 CPU: BCM4712 rev 1 at 200 MHz

    Stock firmware reports rev 2 CPU @ 216MHz & Thibor14 & DD-WRT v23

    ******************* Thibor GS_Thibor14.bin ******************
    CPU: BCM4712 rev 2 at 216 MHz

    BusyBox v1.01 (2006.01.29-22:09+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    # dmesg
    CPU revision is: 00029007
    Primary instruction cache 8kb, linesize 16 bytes (2 ways)
    Primary data cache 4kb, linesize 16 bytes (2 ways)
    Linux version 2.4.20 (carl@Carl-Laptop) (gcc version 3.2.3 with Broadcom modific
    ations) #15 Sat Feb 25 11:55:59 GMT 2006
    Setting the PFC value as 0x15
    Determined physical RAM map:
    memory: 02000000 @ 00000000 (usable)
    On node 0 totalpages: 8192
    zone(0): 8192 pages.
    zone(1): 0 pages.
    zone(2): 0 pages.
    Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    CPU: BCM4712 rev 2 at 216 MHz
    Calibrating delay loop... 215.44 BogoMIPS
    Memory: 30560k/32768k available (1387k kernel code, 2208k reserved, 112k data, 6
    4k init, 0k highmem)


    ********************** GSv3_Thibor15b1.bin *********************
    CPU: BCM4712 rev 1 at 200 MHz

    BusyBox v1.1.2 (2006.04.29-14:07+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    /tmp # dmesg
    CPU revision is: 00029007
    Primary instruction cache 8kb, linesize 16 bytes (2 ways)
    Primary data cache 4kb, linesize 16 bytes (2 ways)
    Linux version 2.4.20 (carl@Carl-Laptop) (gcc version 3.2.3 with Broadcom modific
    ations) #142 Sun May 7 04:26:23 BST 2006
    Setting the PFC value as 0x15
    Determined physical RAM map:
    memory: 02000000 @ 00000000 (usable)
    On node 0 totalpages: 8192
    zone(0): 8192 pages.
    zone(1): 0 pages.
    zone(2): 0 pages.
    Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    CPU: BCM4712 rev 1 at 200 MHz
    Calibrating delay loop... 199.47 BogoMIPS
    Memory: 30536k/32768k available (1402k kernel code, 2232k reserved, 112k data, 6
    8k init, 0k highmem)


    love your Firmware, I'll send money BUT NO PAYPAL, it sucks will never use again!
     
  2. Lumute

    Lumute Network Guru Member

    It is not reporting the wrong processor, its actually 200 MHz but if I remember well Linksys overcloked it to 216 MHz to fix a bug (not very clean way to do it) some firmwares ago...

    I suspect this change comes from newest Linksys firmware 4.71.1 inwhich Thibor 15 series of fw is based. I dont think Thibor introduced this change. It may be that Linksys found a way to correct that bug the real way...

    Experts please correct this if I'm mistaken...
     
  3. Toxic

    Toxic Administrator Staff Member

    your right on m8 just confirmed this with Thibor, they had changed the cpu overclocking back to 200 and fixed the problem by other means.
     
  4. mstombs

    mstombs Network Guru Member

    I also noticed this, the clkfreq only change from 216 back to 200 when I reset the nvram in Thibor 15.

    In the official 4.71.1 firmware the only relevant bit of code I could find was in \release\src\router\rc\rc.c

    [NB there could be other places I can't even expand the tarball without getting duplicate file overwrites, so the ability to build or modify firmware is way beyond me. I did have a linux booting PC till the PSU failed and took out the motherboard...]

    Code:
    	if(check_hw_type() == BCM5325E_CHIP) {
    		/* Lower the DDR ram drive strength , the value will be stable for all boards 
    		   Latency 3 is more stable for all ddr 20050420 by honor */
    		ret += check_nv("sdram_init", "0x010b");
    		ret += check_nv("sdram_config", "0x0062");
    #if LINKSYS_MODEL == WRT54G
    		/* Only for 16M sdram need to override cpu clock */
    		ret += check_nv("clkfreq", "216");
    #endif
    Now that is a compiler switch - I guess Thibor's v15 firmware for the WRT54G has this flag set? In Thibor 14 the #if, #endif are not present so every router that got to this bit of code would have its clkfreq raised.

    NB at 200MHz I don't seem to have the large file transfer issue (same files but different wireless client laptop). As to whether it might be worth overclocking still at 216 I am unsure of the benefits, but runnning stably at lower will keep everything cooler and i may last longer!
     
  5. dirtyclyde

    dirtyclyde Network Guru Member

    The rc.c file was changed by Linksys on Apr 18th this year,
    for the 4.71.1 release from Linksys
    if LINKSYS_MODEL == WRT54G
    Only for 16M sdram need to override cpu clock
     
  6. Thibor

    Thibor Super Moderator Staff Member Member

    i have implemented a choice for this cpu type to automatically overclock the cpu if you have problems with large file transfers. the variable is "cpu_overdrive" and should be entered on the command line, or in command.asp, 1 is enable and sets the cpu frequency to 216mhz, and 0 os off and leaves it at 200mhz. i'm not going to add it to the web interface as it only affects the G models, 2.2, and 3.0 iiirc, and not the equivalent GS types
     
  7. dadaniel

    dadaniel Network Guru Member

    Why does Linksys change this part?
    As we can see the problems start again now??!!

    I don't get it :( :eek:
     
  8. Thibor

    Thibor Super Moderator Staff Member Member

    i'm as unsure as you are. haven't got a clue; at least it was spotted early and we could do something about it
     
  9. dirtyclyde

    dirtyclyde Network Guru Member

    WRT54G(s)

    WRT54G v3.1 should run stock 216MHz
    WRT54GS v2.0 v2.1 & v3.0 should run stock 216MHz

    if not you will have problems!
     
  10. Thibor

    Thibor Super Moderator Staff Member Member

    that is not correct clyde, ONLY the G's should run at 216, not the GS's
     
  11. Trademark

    Trademark Network Guru Member

    I would have to agree with Carl on this one.

    Based on what I've read, only the WRT54G v2.2-3.1 with the Broadcom 5325EKQM chip are effected by this.

    Has something to do with only having 16 megs of ram and the 5325 chip in combination that causes the problem.
     
  12. dirtyclyde

    dirtyclyde Network Guru Member

    I have WRT54GS v2.0 & V3.0 and a WRT54G v3.1 that I don't use anymore, if you put them on any type of load running 200MHz then ping them they will have timeouts, set them to 216MHz and I do not have any timeouts if it pings for 24 hours. @200MHz they are shit! Kids piss and moan about XBOX!

    The same is true for my 3 WRT54GS v2.1 that I use all the time.

    The v2.0 & v3.0 WRT54GS & WRT54G v3.1 I got from compusa for a dollar, they just have bad firmware loads!

    Cheers!
     
  13. Thibor

    Thibor Super Moderator Staff Member Member

    well in 15b2 you will have the choice if your cpu=BCM5325E by setting cpu_overdrive=1, so it will be up to you
     
  14. RTSAnime

    RTSAnime Network Guru Member

    Oddly enough my gV3 reports the correct 216 mhz
    Code:
    /proc # cat cpuinfo
    system type             : Broadcom BCM947XX
    processor               : 0
    cpu model               : BCM3302 V0.7
    BogoMIPS                : 215.44
    wait instruction        : no
    microsecond timers      : yes
    tlb_entries             : 32
    extra interrupt vector  : no
    hardware watchpoint     : no
    VCED exceptions         : not available
    VCEI exceptions         : not available
    unaligned_instructions  : 2
    dcache hits             : 4278189946
    dcache misses           : 135268367
    icache hits             : 1275821010
    icache misses           : 2075229054
    instructions            : 0
    /proc #
    and yes I did a complete reset (clear nvram and hard reset) after upgrading from 14 to 15b1
     
  15. exnetgear

    exnetgear Network Guru Member

    Hello,

    For my 54g v3.0 with Thibor 15b1, I still get:

    CPU: BCM4712 rev 1 at 216 MHz

    even after "Clear NVRAM, restore factory defaults" and hard reset.

    Thanks Thibor for the great FW and amazingly quick repairs!!
     
  16. RTSAnime

    RTSAnime Network Guru Member

    hmm, was having some problems so I did another reset+clear nvram and now my CPU is showing 200mhz as the speed. Not sure what happened this time around.
     
  17. GhaladReam

    GhaladReam Network Guru Member

    Ok. I entered the following in the run command:

    set "cpu_overdrive=1;nvram_commit"

    However, when i log onto putty, dmesg still reports my CPU at 200 MHz. Do I have to reboot my router for this to take effect, or does that string only work if you have a WRT54G v2.2? Because I don't have a 2.2.

    I have 15b2.
     
  18. beach-hobo

    beach-hobo LI Guru Member

    I have a 54g V2.2 running 15b1 and when I run the following:

    "NVRAM GET CLKFREQ"

    It reports back as:

    "216"

    According to all the reports it should be 200. Don't know why I'm reporting 216...

    Any ideas ????
     
  19. mstombs

    mstombs Network Guru Member

    lower case works better on my router!

    nvram get clkfreq

    If you haven't reset your nvram it could well still be showing 216 from Thibor 14 which seeems to have set 216 for everybody.

    The way I read the code is that it only changes the speed if requested, otherwise it leaves it alone at whatever it was before.
     
  20. dirtyclyde

    dirtyclyde Network Guru Member

    I guess so far I'm happy, just loaded Thibor15b3 on my WRT54GSv2.1, set cpu_overdrive=1, it shows 216MHz. I'll down load FC 5 now thats about 4.5 gig. I'll see if the WRT54GSv2.1 vomits!

    Also set overdrive on a WRT54Gv4.0 it did not overclock the WRT54Gv4.0 it stayed 200MHz. Just thought I would try! Besides if you want to overclock a WRT use dd-wrt.

    I do like Thibors Firmware
    Cheers Thanks!


    2 WRT54GSv2.1 dd-wrt v23 RC1
    1 WRT54GSv2.1 Thibor15b3 with overdrive set (216MHz)
    1 WRT54GSv1.0 Thibor15b3
    2 WRT54Gv4.0 Thibor15b3

    All running WDS WPA2/AES, XBOX360, XBOX, Laptop wg511T,AMD64 3200+ Linux/WinXP/2K,Old Compaq XP. Ft4100 XP,
    AMD64 3800 new boy FC 5 linux
     
  21. exnetgear

    exnetgear Network Guru Member

    Hello,

    For my 54g v3.0 with Thibor 15b1:

    Clear NVRAM, restore factory defaults - 216MHz
    30 sec hard reset - 216MHz
    Another Clear NVRAM, restore factory defaults - 216MHz

    Upgrade to Thibor 15b3
    Clear NVRAM, restore factory defaults = 216 MHz
    30 sec hard reset - 216 MHz
    Another Clear NVRAM, restore factory defaults - 216MHz

    After all resets I still show "CPU: BCM4712 rev 1 at 216 MHz"

    At least for my 54G v3.0, not messing with "cpu_overdrive" seems to have kept my unit's clock freq at 216 MHz.

    Thanks Thibor for the great FW!!
     
  22. adam217

    adam217 Network Guru Member

    For anybody that isn't sure how to set this, the command GhaladReam posted did not work for me. What did work was:

    nvram set cpu_overdrive=1

    You can then check to make sure it is set properly with:

    nvram get cpu_overdrive

    I then rebooted the router and entered:

    nvram get clkfreq

    Just to make sure it was working properly.

    Hope this helps some frustrated people.
     
  23. Thibor

    Thibor Super Moderator Staff Member Member

    adam, you need to "nvram commit" to save the changes
     
  24. adam217

    adam217 Network Guru Member

    Would that only effect the clock/setting if the router lost power? I've used the reboot multiple times and it has stayed at 216. I have a WRT54G v2.2 BTW. All commands were done via the "run command" interface.

    My guess was the by using the "nvram" in front of the set command that it was committing it. I have no knowledge of Linux or how this thing really works. If I did need to the "nvram commit" in there, what made it stick?

    BTW Thank you for your hard work, your firmware has made a big difference in everybody's online experience around here.
     

Share This Page