ASUS RT-AC68U Firmware version 3.0.0.4.374.4561 is out

[speedingcheetah]

A print out of the LOG wont tell them what is happening?

I'm pretty sure if it was that easy, then RMerlin wouldn't be stumped.

 

[RMerlin]

A print out of the LOG wont tell them what is happening?

No. The actual crash message is dumped over the serial port, and not in syslog (since at that stage, the kernel cannot rely on syslog and the filesystem of being in a usable state).

 

[RMerlin]

Well...there is a guy that has it up to 1400....is that a "valid" clock speed then?

And as u had mentioned in previous post to check MIPS value...mine is 1998 which is above the stock 1600 value u mentioned and that number goes up and down if i change the clock speed. So it appears to take what ever value I set it at.

Here are the valid clock rates:

static unsigned int cpu_clock_table[] = {600, 800, 1000, 1200, 1400, 1600};
static unsigned int ddr_clock_table[] = {333, 389, 400, 533, 666, 775, 800};

If the values aren't in these tables, it reverts back to 800/533.

 

[IanEnc]

If the values aren't in these tables, it reverts back to 800/533.

BogoMIPS says otherwise for my unit. It turned out my syntax was incorrect (I used clkfrq instead of clkfreq), which solved the reason why Sysinfo did not show the CPU clock set into the nvram.

But even by using these values mentioned, my AC68R is always reverted back to stock.

Again, Bootloader is 1.0.1.1. Running 40_alpha8. I guess my unit just can't be overclocked (other than turbo mode).

 

[IanEnc]

Perhaps the CFE in my unit has disabled the ability to overclock, even though my bootloader is 1.0.1.1.

I've given up on over clocking this unit. I will now have to decide to either go with turbo mode or the DDR upgrade utility from ASUS.

 

[Adamm]

Try upgrading the bootloader, my AC68R shipped this week with 1.0.1.6 by default and I had no issues overclocking it to 1000/800 via the cklfreq value. The only downside is the overclock feature being broken at the moment, but no functionality is lost as the nvram value can still be modified.

admin@RT-AC68R:/tmp/home/root# nvram get clkfreq
1000,800

admin@RT-AC68R:/tmp/home/root# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1998.84

processor : 1
BogoMIPS : 1998.84

Features : swp half thumb fastmult edsp
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0

Hardware : Northstar Prototype
Revision : 0000
Serial : 0000000000000000

admin@RT-AC68R:/tmp/home/root# nvram get bl_version
1.0.1.6

 

[SeCrEt_BoY]

How to check bootloader?

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

 

[Adamm]

How to check bootloader?

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

In SSH or admin GUI;

nvram get bl_version

 

[SeCrEt_BoY]

In SSH or admin GUI;

nvram get bl_version

Admin GUI??? 192.168.1.1 with Admin?

Gửi từ SM-N900 của tôi bằng cách sử dụng Tapatalk

 

[Adamm]

Yes under Tools - Run Cmd



192.168.1.1/Tools_RunCmd.asp

 

[SeCrEt_BoY]

Yes under Tools - Run Cmd



192.168.1.1/Tools_RunCmd.asp

Where is Tools Run Cmd I am using 68R and I can not see Tools - Run CMD

 

[rtcomputersinc]

Didn't reboot for over a day and then last night 3 reboots in a row in 15 minutes. I was streaming a movie at the time from a wired NAS. I also have apple devices on the network phones and ipods.

 

[rtcomputersinc]

No. The actual crash message is dumped over the serial port, and not in syslog (since at that stage, the kernel cannot rely on syslog and the filesystem of being in a usable state).

Is there a way to pull the message from the serial port ourselves? Or route it to a thumb drive?

 

[Mordred]

random reboots

By the way I also experienced random reboots on dd-wrt builds.
Sometimes the unit would just reboot at night with no device connected.

Since I'm on kongs build I haven't seen any crash/random reboot and I had uptimes of more than 14 days, with all other builds I tried the unit rebooted once or twice a day. According to dd-wrt forum the random crash issue is only fixed in kong builds.

 

[vaszago]

30 hours online on alpha9 and still no reboot

 

[RMerlin]

Is there a way to pull the message from the serial port ourselves? Or route it to a thumb drive?

No. The only way is to hook a TTL serial cable to it, and monitor the output.

 

[Binar]

No. The only way is to hook a TTL serial cable to it, and monitor the output.

Is ASUS aware of the reboots? Should we expect a new firmware soon? I know you are not an ASUS rep but they send you the new firmware before they release it to us

 

[Paralel]

Is ASUS aware of the reboots? Should we expect a new firmware soon? I know you are not an ASUS rep but they send you the new firmware before they release it to us

As mentioned earlier in this thread, yes they are aware, and they are having trouble triggering it in their lab to study it, so don't expect a quick fix.

 

[SeCrEt_BoY]

Someone plz guide me how to know bootloader version....

 

[IanEnc]

Someone plz guide me how to know bootloader version....

In the Web GUI of your router, go to Tools on the left side of the screen.

You should be at a page the Sysinfo page (look at the tabs near the top).

You should be able to find your Bootloader version in the information here.