Posted: Sun Mar 01, 2015 7:16 Post subject: Strange behavior with release 26xxx
My R7000 runs fine with any r25xxx version of brainslayer, but as soon as I upgrade to a R26xxx releqse the router runs fine for a couple of hours and then Internet connectivity gets lost.
Connection to internal resources is still working (dns?)
Any idea how I can best troubleshoot?
Thanks!
Joined: 10 Jan 2015 Posts: 270 Location: Minnesota
Posted: Sun Mar 01, 2015 10:29 Post subject:
Have you cleared nvram before and after installing your current version of firmware?
Anything past 26300 requires an nvram reset as there are some variables that are changed from previous releases and anything past 26075 has the new broadcom driver so i cleared nvram at that point too.
I cleared nvram after the upgrade.
I loaded a config backup however since I have a lot of portforwarding to manually reconfigure.
Can this be an issue?
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
I did a double nvram reset with reload of old config.
I'll check this out. If not ok I'll try a clean install with a 26138 release.
Thanks already!
What you are doing is pointless.
You are erasing your nvram, and then you are restoring it back to the broken state before the erase. _________________ http://www.speedtest.net/result/3915993898.png
DO NOT 30-30-30 or erase nvram newer routers! It can brick them.
EA6700: Build 27745 (nvram below 32K, ipv6 - HE 6in4)
E4200: Build 26587
WRT54GL: Retired - waiting in the closet for an emergency.
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Good clarification from HalfBit. Folks have found the gui reset to be inadequate.
AFTER flashing one of these BCM4707/4708/4709 units use telent and issue "nvram erase && reboot" from the CLI
jheide44 wrote:
**BCM4707/4708/4709 Devices w/ ARM CPUs**
Be advised that Kong announced on his Personal Test Build thread that a reset IS required if coming from BS build 26138 or earlier. (Also, both Kong and BS are working from the main SVN trunk these days.)
Kong Test Build users may want to read up to make an informed decision. Details on the "New Boadcom ARM driver ?" thread, HERE.
(Of course the official Peacock recommendation is a NVRAM reset before and after flashing... however, folks resetting from the CLI via telnet after flashing are reporting good results... and for goodness sake do NOT reuse an old config backup!)
I should probably add the underlined section to the new builds thread general reminders. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Sorry guys but I did all as mentioned and again no Internet anymore after a couple of hours.
Did nvram resets via ssh.
Very annoying. Are there any useful logs?
Joined: 10 Jan 2015 Posts: 270 Location: Minnesota
Posted: Mon Mar 02, 2015 12:19 Post subject:
You can enable syslogs under the services tab. You then telnet or ssh and look at /var/log/syslog to see what errors are possibly occuring.
What problem you are describing though is the old broadcom driver before 26075 that caused reboots due to 2.4ghz amdpu. It shouldnt happen past that version now.
I'm gonna try it again tonight:
1. erase nvram && reboot
2. upgrade dd-wrt to 26160
3. erase nvram && reboot
4. reconfigure everything (nice with >30 port forwarding rules)
5. safe config and a last reboot to be sure
I'm gonna try it again tonight:
1. erase nvram && reboot
2. upgrade dd-wrt to 26160
3. erase nvram && reboot
4. reconfigure everything (nice with >30 port forwarding rules)
5. safe config and a last reboot to be sure
These steps are correct, aren't they?
looks good, may not actually need step 1, but it couldn't hurt. (at step 2, just select reset from the dropdown on the firmware update web GUI) then proceed with your steps 3-5
If you are going to run a Kong PTB, folks are reporting good results on the latest. Dated 2/26/15 (26365) from HERE.
i suppose, either way that config backup puts you on the recent side of Kongs *reset manual reconfig required* announcement _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
