New Kong test build r34900M 02-12-18

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page 1, 2, 3  Next
Author Message
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Mon Feb 12, 2018 23:10    Post subject: New Kong test build r34900M 02-12-18 Reply with quote
New Kong test build r34900M 02-12-18 is out.
http://desipro.de/ddwrt/K3-AC-IPQ806X/Test/

Report your findings Cool
Sponsor
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Mon Feb 12, 2018 23:12    Post subject: Reply with quote
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018

Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C
labo
DD-WRT Guru


Joined: 30 Jan 2015
Posts: 676
Location: Texas, USA

PostPosted: Tue Feb 13, 2018 0:10    Post subject: Reply with quote
jerrytouille wrote:
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018

Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C


I see 10degC less: DD-WRT v3.0-r34900M kongat (02/12/18 )

CPU TemperatureCPU 50.0 °C / ath0 51 °C / ath1 51 °C
I'm in Texas. Smile

_________________
ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Tue Feb 13, 2018 0:30    Post subject: Reply with quote
labo wrote:
I see 10degC less: DD-WRT v3.0-r34900M kongat (02/12/18 )

CPU TemperatureCPU 50.0 °C / ath0 51 °C / ath1 51 °C
I'm in Texas. Smile


And I'm in Ohio Shocked
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Tue Feb 13, 2018 0:45    Post subject: Reply with quote
jerrytouille wrote:
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018

Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C


They weren't correct in earlier builds.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Tue Feb 13, 2018 2:33    Post subject: Reply with quote
<Kong> wrote:
jerrytouille wrote:
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018

Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C


They weren't correct in earlier builds.


so all this time they were wrong? i figured one of them was wrong (idle 19c in a 21c room, but the other radio looked ok @ 30c or so). now they seem to be nearly sync'd to cpu temp.

also could u update ath10k fw to 10.4-3.5.3-00053 in next build? https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

Siggyceline
DD-WRT User


Joined: 14 Jan 2018
Posts: 65

PostPosted: Tue Feb 13, 2018 4:51    Post subject: Reply with quote
Upgraded all three of my APs to 34900M

R6400
R8000
R7800

Can confirm NTP behavior is the same on all builds...FQDN (time.nist.gov) doesn’t work anymore. Had to enter an IP to get clock set.

I posted the syslog NTP error message for the R6400 over in the Broadcom SOC forum, but it is the same on my R7800.
Siggyceline
DD-WRT User


Joined: 14 Jan 2018
Posts: 65

PostPosted: Tue Feb 13, 2018 4:57    Post subject: Reply with quote
Also...quick noob question:

What should the R7800 cpu clock read? Mine is reading 800MHz/800MHz. Is that status reading dynamic or fixed? (Meaning does it adjust up and down based on load/speed, or is it showing static max cpu clock capability?)

If it is max cpu clock, then I don’t think that is right on my R7800?

Thanks for any feedback!
labo
DD-WRT Guru


Joined: 30 Jan 2015
Posts: 676
Location: Texas, USA

PostPosted: Tue Feb 13, 2018 5:10    Post subject: Reply with quote
Siggyceline wrote:
Also...quick noob question:

What should the R7800 cpu clock read? Mine is reading 800MHz/800MHz. Is that status reading dynamic or fixed? (Meaning does it adjust up and down based on load/speed, or is it showing static max cpu clock capability?)

If it is max cpu clock, then I don’t think that is right on my R7800?

Thanks for any feedback!


Yes, yours is dynamic.
To set the peak/max fixed, you have to use Tatsuya's startup script:

for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n performance > $CPUFREQ; done

_________________
ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
Siggyceline
DD-WRT User


Joined: 14 Jan 2018
Posts: 65

PostPosted: Tue Feb 13, 2018 5:51    Post subject: Reply with quote
labo wrote:
Siggyceline wrote:
Also...quick noob question:

What should the R7800 cpu clock read? Mine is reading 800MHz/800MHz. Is that status reading dynamic or fixed? (Meaning does it adjust up and down based on load/speed, or is it showing static max cpu clock capability?)

If it is max cpu clock, then I don’t think that is right on my R7800?

Thanks for any feedback!


Yes, yours is dynamic.
To set the peak/max fixed, you have to use Tatsuya's startup script:

for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n performance > $CPUFREQ; done


Thanks!
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6437
Location: UK, London, just across the river..

PostPosted: Tue Feb 13, 2018 6:46    Post subject: Reply with quote
Router Model Netgear R7800
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/1Cool
Kernel Version Linux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018 armv7l

update: via ddup
reset : NO
status: operational
errors:
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 02:00:34 R7800 daemon.notice ntpclient[2321]: Network up, resolved address to hostname 212.18.3.19
Jan 1 02:00:34 R7800 daemon.debug ntpclient[2321]: Connecting to 212.18.3.19 [212.18.3.19] ...
Feb 13 08:30:19 R7800 daemon.info ntpclient[2321]: Time set from 212.18.3.19 [212.18.3.19].
Feb 13 08:30:19 R7800 daemon.err process_monitor[2320]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

so NTP time is kind of working now

Feb 13 08:32:17 R7800 user.info : Authentication fail
Feb 13 08:32:23 R7800 user.info : httpd login failure - bad passwd ! --- but i was logged in with correct pass ???!!!

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Tue Feb 13, 2018 14:36    Post subject: Reply with quote
<Kong> any thoughts on this? Seems to be an "easy" fix...
http://svn.dd-wrt.com/ticket/4839
MrDoh
DD-WRT Guru


Joined: 04 Dec 2012
Posts: 647

PostPosted: Wed Feb 14, 2018 9:16    Post subject: Reply with quote
Alozaros wrote:
Router Model Netgear R7800
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/1Cool
Kernel Version Linux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018 armv7l

update: via ddup
reset : NO
status: operational
errors:
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 02:00:34 R7800 daemon.notice ntpclient[2321]: Network up, resolved address to hostname 212.18.3.19
Jan 1 02:00:34 R7800 daemon.debug ntpclient[2321]: Connecting to 212.18.3.19 [212.18.3.19] ...
Feb 13 08:30:19 R7800 daemon.info ntpclient[2321]: Time set from 212.18.3.19 [212.18.3.19].
Feb 13 08:30:19 R7800 daemon.err process_monitor[2320]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

so NTP time is kind of working now

Feb 13 08:32:17 R7800 user.info : Authentication fail
Feb 13 08:32:23 R7800 user.info : httpd login failure - bad passwd ! --- but i was logged in with correct pass ???!!!


This one:

Feb 13 08:30:19 R7800 daemon.err process_monitor[2320]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

in my log is highlighted in red. I assume that's because it's from the daemon.err process monitor...because the content of the message is "success", not a "failure". Anyways, I'm back on r33770M again. I find red highlighting of success messages in the log too distracting from the events that I really need to see *smile*.
zabolots
DD-WRT User


Joined: 02 Dec 2015
Posts: 122

PostPosted: Wed Feb 14, 2018 12:52    Post subject: Reply with quote
What makes the recent <Kong> builds "test builds"? Is there some new feature/kernel/firmware being tried out?

Just curious...

_________________
--Netgear R7800--
DD-WRT v3.0-r49492 std (07/14/22)
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Wed Feb 14, 2018 15:12    Post subject: Reply with quote
zabolots wrote:
What makes the recent <Kong> builds "test builds"? Is there some new feature/kernel/firmware being tried out?

Just curious...


Because Kong doesn't consider them stable, or didn't test them personally.
Goto page 1, 2, 3  Next Display posts from previous:    Page 1 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum