Linksys ea8500 port is ready

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 81, 82, 83 ... 123, 124, 125  Next
Author Message
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Mon Oct 30, 2017 4:56    Post subject: Reply with quote
Hibino wrote:
Hi guys, I have a non-us EA8500 with the international 1.1.7.182977 firmware and I am thinking to flash it with dd-wrt.

I've been reading quite a few pages in this post and also the instructions in this page which stated in red is for US EA8500. But I just can't find any info regarding the non-us EA8500.

Does my non-us EA8500 also requires USB to TTL in order to flash? Or the international version does not lock the firmware?

Thank you.

You should be good to install the EA8500WW-factory-to-ddwrt.img from --
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/
Mr. K has a ReadMe file in that directory also --
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Readme

Reset the router after you install and you should be good to install whatever
EA8500 build you want then from Kong builds or from --
ftp://ftp.dd-wrt.com/betas/
Sponsor
Hibino
DD-WRT Novice


Joined: 30 Oct 2017
Posts: 5

PostPosted: Mon Oct 30, 2017 5:13    Post subject: Reply with quote
mrjcd wrote:
Hibino wrote:
Hi guys, I have a non-us EA8500 with the international 1.1.7.182977 firmware and I am thinking to flash it with dd-wrt.

I've been reading quite a few pages in this post and also the instructions in this page which stated in red is for US EA8500. But I just can't find any info regarding the non-us EA8500.

Does my non-us EA8500 also requires USB to TTL in order to flash? Or the international version does not lock the firmware?

Thank you.

You should be good to install the EA8500WW-factory-to-ddwrt.img from --
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/
Mr. K has a ReadMe file in that directory also --
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Readme

Reset the router after you install and you should be good to install whatever
EA8500 build you want then from Kong builds or from --
ftp://ftp.dd-wrt.com/betas/


Thank you, that's a really quick reply.

I just finished reading more pages from this post, with your answers and came up following:

- I can just flash non-us EA8500 through current Linksys web interface with the EA8500WW-factory-to-ddwrt.img. And the EA8500WW-factory-to-ddwrt.img come with the latest DD-WRT and I do not need to download ddwrt-Linksys-EA8500.bin to flash it again.
- The EA8500WW-factory-to-ddwrt.img will be flashed into 1st partition of the router.
- After the flashing and reboot, the router will be in DD-WRT web interface. If I flash the ddwrt-Linksys-EA8500.bin(future upgrades) in the DD-WRT web interface, it will be flashed into the 2nd partition of the router.

And here comes the question:
1. After I flashed ddwrt-Linksys-EA8500.bin(future upgraded version) in DD-WRT web interface, it is on the 2nd partition, then after I restart the router, will it boot into the 1st partition(existing version) or the 2nd partition(new future version)?
2. How can I always just flash the 1st partition of the router? So it just like a android phone or other devices after I flash and reboot it will always boot the newest firmware I just flashed.

Thank you.


EDIT:
Found answers
1. Flash done partition 1 will be writing to p2 and will boot to p2, flash done in p2 will be writing to p1 and boot to p1.

2. has to boot to p2 in order to flash p1
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7214
Location: Columbus, Ohio

PostPosted: Mon Oct 30, 2017 9:38    Post subject: Reply with quote
Hibino wrote:
Hi guys, I have a non-us EA8500 with the international 1.1.7.182977 firmware and I am thinking to flash it with dd-wrt.

I've been reading quite a few pages in this post and also the instructions in this page which stated in red is for US EA8500. But I just can't find any info regarding the non-us EA8500.

Does my non-us EA8500 also requires USB to TTL in order to flash? Or the international version does not lock the firmware?

Thank you.


Try to flash it, if it works it will have dd-wrt on it, if it doesn't, it will still have linksys on it and then you'll have your answer.

_________________
I am far from a guru, I'm barely a novice.
Wolf Kodi
DD-WRT User


Joined: 13 Jun 2010
Posts: 126

PostPosted: Mon Oct 30, 2017 13:58    Post subject: Reply with quote
mrjcd wrote:

The dd-wrt public release has several more features, some of which I play with when time permits, most I don't use on main router.


I want to give BS's a try and check out its additional features. It's been a while since I've tried the main releases, mostly because I'm using it on my main router and Kong's releases were more trustworthy as they are better tested earlier on. It seems that EA8500 has come to a more stable point.

_________________


YouTube | Facebook Page
Per-user Live Down/Upload Rate Monitoring [No PC needed!]
Hibino
DD-WRT Novice


Joined: 30 Oct 2017
Posts: 5

PostPosted: Mon Oct 30, 2017 23:04    Post subject: Reply with quote
I've flashed dd-wrt to my EA8500 and now have spend an hour trying to figure out how to set the VLAN tagging to my WAN port so I can connect to internet.

My ISP requires VID 10 for the PPPoE in order to connect to internet.

I tried to add a new entry in the "VLAN Tagging" under Setup->Networking, and I select "eth0" and Tag Number 10, then Save and reboot. After the reboot I can see the new selection "eth0.10" for "WAN Port Assignment" so I select it and Save/reboot again. I thought this is how it should be done according to few google results I found but it seems not working at all...

So I tried some telnet commands from google result like "nvram set pppoe_wan_ifname=eth0.10" and then "nvram commit" also seems has no effect...

Can someone tell me how I can tag the WAN port with VID 10? Thank you.

BTW, when I select interface I see the following options:
ath0
ath1
br0
eth0 (and another eth0.10 after added the tagging)
eth1
ip6tnl0
vlan1
vlan2

The EA8500 has 1 WAN and 4 LAN ports, so the eth0 will be WAN, eth1 will be LAN1? where are the other 3 LAN ports?
Wolf Kodi
DD-WRT User


Joined: 13 Jun 2010
Posts: 126

PostPosted: Tue Oct 31, 2017 9:49    Post subject: Reply with quote
Hibino wrote:
I've flashed dd-wrt to my EA8500 and now have spend an hour trying to figure out how to set the VLAN tagging to my WAN port so I can connect to internet.

My ISP requires VID 10 for the PPPoE in order to connect to internet.

I tried to add a new entry in the "VLAN Tagging" under Setup->Networking, and I select "eth0" and Tag Number 10, then Save and reboot. After the reboot I can see the new selection "eth0.10" for "WAN Port Assignment" so I select it and Save/reboot again. I thought this is how it should be done according to few google results I found but it seems not working at all...

So I tried some telnet commands from google result like "nvram set pppoe_wan_ifname=eth0.10" and then "nvram commit" also seems has no effect...

Can someone tell me how I can tag the WAN port with VID 10? Thank you.

BTW, when I select interface I see the following options:
ath0
ath1
br0
eth0 (and another eth0.10 after added the tagging)
eth1
ip6tnl0
vlan1
vlan2

The EA8500 has 1 WAN and 4 LAN ports, so the eth0 will be WAN, eth1 will be LAN1? where are the other 3 LAN ports?


eth0 is the interface for all ports. You'll need to use a virtual interface (vlan) for a VID of 10. I'm not sure if there is a GUI way of setting this up and if it works now but I configure mine using command line. The following should work for you. You'll need to save it as a startup script for it to stick across reboots.

Code:

swconfig dev eth0 vlan 1 set ports '0t 1 2 3 4 5t'
swconfig dev eth0 vlan 2 set ports '0t 5t'
swconfig dev eth0 vlan 2 set vid 10
swconfig dev eth0 set apply
vconfig add eth0 10
ifconfig vlan10 up
nvram set pppoe_wan_ifname="vlan10"

_________________


YouTube | Facebook Page
Per-user Live Down/Upload Rate Monitoring [No PC needed!]
derckchow
DD-WRT Novice


Joined: 06 Jan 2008
Posts: 11

PostPosted: Tue Oct 31, 2017 22:29    Post subject: Reply with quote
I get it work. the problem was the bit pre second set to 11520 on puty. Embarassed Embarassed
it should be 115200


mrjcd wrote:
derckchow wrote:
mrjcd wrote:
Looks like you have wires crossed

Maybe tx / rx or gnd

Do NOT connect serial adapter power!!!


Thanks! Mr. JCD,

This is the one I bought:

https://www.ebay.com/itm/PL2303HX-USB-to-TTL-RS232-COM-UART-Module-Serial-Cable-Adapter-for-Arduino-/322619331980

I used your guide to do it. I did not connect the power, and the white connect to the point 2,green connect to point 3, and black connect to point 5.

Thanks again,

Derick

All I can say is it's not communicating.
check device manager see if it's drivers are correct

Make sure putty setup correct

Swap tx & rx .....
Wolf Kodi
DD-WRT User


Joined: 13 Jun 2010
Posts: 126

PostPosted: Tue Oct 31, 2017 22:42    Post subject: Reply with quote
I tried the latest BS build and couldn't get swap memory to work. I need it, so I switched back to Kong's.
_________________


YouTube | Facebook Page
Per-user Live Down/Upload Rate Monitoring [No PC needed!]
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Tue Oct 31, 2017 23:32    Post subject: Reply with quote
EA8500
DD-WRT v3.0-r33620M (10/31/17)
Linux 3.18.78 #202 SMP PREEMPT Tue Oct 31 23:08:02 CET 2017 armv7l
so he don't go below 800 MHzs
default after reset --
Code:
Doing 4096 bit private rsa's for 10s: 194 4096 bit private RSA's in 10.01s
Doing 4096 bit public rsa's for 10s: 14609 4096 bit public RSA's in 10.00s

                  sign    verify    sign/s verify/s
rsa 4096 bits 0.051598s 0.000685s     19.4   1460.9

Doing aes-256 cbc for 3s on 16 size blocks: 4899709 aes-256 cbc's in 2.99s
Doing aes-256 cbc for 3s on 64 size blocks: 1702846 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 256 size blocks: 439929 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 1024 size blocks: 110948 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 8192 size blocks: 13694 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 16384 size blocks: 6840 aes-256 cbc's in 2.99s

The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
aes-256 cbc      26219.18k    36327.38k    37540.61k    37870.25k    37393.75k    37480.45k


::::::::::::::::::::::::

r33555

Code:
Doing 4096 bit private rsa's for 10s: 194 4096 bit private RSA's in 10.04s
Doing 4096 bit public rsa's for 10s: 14897 4096 bit public RSA's in 10.00s

                  sign    verify    sign/s verify/s
rsa 4096 bits 0.051753s 0.000671s     19.3   1489.7

Doing aes-256 cbc for 3s on 16 size blocks: 6259259 aes-256 cbc's in 2.99s
Doing aes-256 cbc for 3s on 64 size blocks: 1720291 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 256 size blocks: 429975 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 1024 size blocks: 110084 aes-256 cbc's in 2.99s
Doing aes-256 cbc for 3s on 8192 size blocks: 13969 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 16384 size blocks: 6973 aes-256 cbc's in 3.00s

aes-256 cbc      33494.36k    36699.54k    36691.20k    37701.01k    38144.68k    38081.88k
Hibino
DD-WRT Novice


Joined: 30 Oct 2017
Posts: 5

PostPosted: Wed Nov 01, 2017 4:03    Post subject: Reply with quote
I thought just give a final reply here since it might help someone else with vlan tagging.

I spend hours yesterday trying to set it up with a vid to wan port but the had no luck with the web interface so I tried the cli interface following all sorts of instructions from different results in google search. And the only one I got working is Wolf Kodi's command that he posted in a different post in this forum a while ago but need a little change. Here is the command that worked for me(Replace the 10 with the vid you want to set):
Code:

swconfig dev eth0 vlan 1 set ports '0t 1 2 3 4 5t'
swconfig dev eth0 vlan 2 set ports '0t 5t'
swconfig dev eth0 vlan 2 set vid 10
swconfig dev eth0 set apply
vconfig add eth0 10
ifconfig eth0.10 up
nvram set pppoe_wan_ifname="eth0.10"
nvram commit

The original command with "ifconfig vlanXXX up" will result "No such device" error.

So after the commands the router finally successfully connected to my isp through pppoe.

But here are the problems that made me switch back to stock Linksys firmware:
1. I have to run the commands again if I restarted the router. I tried to put the commands into the startup commands in the web interface but it doesn't work. or maybe I am doing it wrong.
2. I am using a 1gbps down and 500mbps up fibre, with dd-wrt I can only get 4xxmbps down and 4xxmbps up, and back to normal peek hour rates 8xxmbps down 4xxmpbs up after flash back to Linksys firmware. I am sure there must be some setting or commands I can use to make dd-wrt has the same rates but I just don't want to spend another few hours digging around to make it working.

So I flash back to stock Linksys firmware after 4 hours playing with dd-wrt. It does has much more features and some of them are very useful to me(e.g. the stats of the router and each devices), but I think it probably not ready for a normal user yet...
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Thu Nov 02, 2017 13:22    Post subject: Reply with quote
Newest Kong
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/
ddwrt-Linksys-EA8500.bin 2017-11-02 09:49 24M

DD-WRT v3.0-r33645M kongat (11/02/17)
Linux 3.18.79-rc1 #209 SMP PREEMPT Thu Nov 2 09:02:46 CET 2017
New 9980 firmware ver 10.4-3.5.3-00038
Looks ok so far.....
both radio ok
ovpn serv ok
vlan still ok
unbound still won't start ...I need to do a cleanup reset reconf someday
and prolly just quit using unbound --- looks like now got some good DNSCyrpt/DNSSEC
servers working these days. Probably switch to that in the near future.


so I installed on main router --
DD-WRT v3.0-r33647 (11/02/17)
Linux 3.18.79-rc1 #191 SMP PREEMPT Thu Nov 2 00:26:36 CET 2017
unbound working
looks like a keeper -- it's all good so far



Both these builds have new 9980 firmware ver 10.4-3.5.3-00038
and new CPU freq tweaks (min cycle point is 800MHz opposed to old 384MHz)

EDIT: had 2586 active connections and checking
/Status_Conntrack.asp .... No problem there Wink

http://www.dslreports.com/speedtest/24365960

another test --later
http://www.dslreports.com/speedtest/24385135

::::::::::::
r33555 was good - no problems there - twas stable if anyone wants to know
# uptime
08:01:17 up 12 days, 5:58, load average: 0.07, 0.07, 0.01
# date
Thu Nov 2 08:01:24 CDT 2017
:::::::::::
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Sat Nov 04, 2017 21:44    Post subject: Reply with quote
10.4-3.5.3-00038 is working but
didn't have any disconnects or problems other than the wierdness in dmesg

DD-WRT v3.0-r33647
Release: 11/02/17

14:21:08 up 2 days, 6:18

[ 40.511495] br1: port 3(vlan4) entered forwarding state
[ 44.930570] Ebtables v2.0 registered
[ 1641.268898] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[17225.693340] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[17226.309981] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[48192.294417] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[48192.328236] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[48192.330371] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[48192.362867] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[92206.805110] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[92206.838270] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106240.595562] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106240.627575] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106240.629705] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106240.664875] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106260.596453] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106260.620918] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106280.606358] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106280.620630] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106300.594640] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106300.607992] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106320.591417] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106320.606595] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106340.586276] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106340.601024] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106360.596811] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106360.612406] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106380.583525] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106380.596490] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106400.578494] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106400.592606] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106420.578717] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106420.594154] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106440.573419] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106440.588390] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106460.567281] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106460.578989] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106480.564339] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106480.580052] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106500.559561] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106500.574621] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106520.591547] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[106520.606417] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107273.345368] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107273.380041] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107274.787841] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107274.803787] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107275.534268] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107275.549454] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107278.016778] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107278.053304] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107308.443674] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107308.483365] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107381.023489] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107381.024518] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107381.084228] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[107381.085251] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[124235.955291] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124235.955333] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124235.962547] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124235.970709] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124934.973063] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124934.973105] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124934.980246] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124934.988536] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[124934.996782] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.182569] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.182602] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.189741] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.198050] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.206288] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.214535] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.222783] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125595.230958] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125640.195458] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125817.249272] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125817.249314] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125817.256531] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[125817.264743] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129175.543567] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129175.543608] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129175.550738] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129175.559072] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129187.546892] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129187.546937] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129187.554148] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[129187.562296] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130691.242409] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130691.242452] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130691.249582] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130691.257909] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[134634.718986] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[134634.719049] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[134634.726167] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[134634.734396] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[136198.193174] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[136198.193215] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[136198.200347] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[136198.208651] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[144288.382945] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144288.420483] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144294.592406] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144298.565662] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144299.529356] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144299.566507] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144300.511273] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[144300.546472] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[148356.918516] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[148356.957574] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[148356.959992] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[148357.006885] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186443.114140] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186443.125973] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186443.126614] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186443.139340] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186463.126579] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186463.138774] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186483.129588] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186483.143197] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186503.133142] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186503.146661] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186523.207837] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186523.271880] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186544.137594] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186544.150611] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186564.140901] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[186564.154895] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[187351.142492] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[187351.154155] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[187351.154717] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[187351.168117] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190524.847351] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190524.884533] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190525.989638] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190526.024850] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190527.464223] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190527.501450] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190527.958345] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[190527.995602] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
-----------
See how he does with newer
r33679 std (c) 2017 NewMedia-NET GmbH
Release: 11/04/17
uptime
16:35:23 up 2:07
he is clean so far..............

::::::::::::::::::::::::
r33555 is still 'bout good as it gets in my world
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Sat Nov 04, 2017 22:04    Post subject: Reply with quote
One good thing with the new ath10k FW
you can now pull up
cat /proc/kallsyms ... wouldn't work in old on EA8500

also can now run
cat /sys/kernel/debug/ieee80211/phy0/ath10k/fw_reset_stats
cat /sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats
cat /sys/kernel/debug/ieee80211/phy1/ath10k/fw_reset_stats
cat /sys/kernel/debug/ieee80211/phy1/ath10k/fw_stats
without it causing a never ending string of mess in dmesg .... so that is all now amusing I guess Razz

EDIT: No no no you are lyin --
it still floods dmesg with spam ... just not as fast as the old ath10k FW did .... this build also still has the 'unknown event' crap.
[ 9698.177310] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9698.211494] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9706.824294] ath10k_pci 0001:01:00.0: dropping fw peer stats
[ 9718.180172] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9718.214350] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9738.181284] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9738.215947] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9751.128129] ath10k_pci 0000:01:00.0: dropping fw peer stats
[ 9758.185257] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9758.219442] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9778.188058] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9778.222726] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9798.190995] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9798.225181] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9818.193546] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9818.227720] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9824.224800] ath10k_pci 0001:01:00.0: dropping fw peer stats
[ 9888.175591] ath10k_pci 0000:01:00.0: dropping fw peer stats
[ 9959.643810] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10025.218215] ath10k_pci 0000:01:00.0: dropping fw peer stats
[10096.548300] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10154.254622] ath10k_pci 0000:01:00.0: dropping fw peer stats
[10233.573784] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10277.694431] ath10k_pci 0000:01:00.0: dropping fw peer stats
[10370.606881] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10400.938433] ath10k_pci 0000:01:00.0: dropping fw peer stats

oh well, we'll reboot and just let it cook for few days Twisted Evil
tatsuya46
DD-WRT Guru


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

PostPosted: Mon Nov 06, 2017 9:24    Post subject: Reply with quote
mrjcd wrote:
One good thing with the new ath10k FW
you can now pull up
cat /proc/kallsyms ... wouldn't work in old on EA8500

also can now run
cat /sys/kernel/debug/ieee80211/phy0/ath10k/fw_reset_stats
cat /sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats
cat /sys/kernel/debug/ieee80211/phy1/ath10k/fw_reset_stats
cat /sys/kernel/debug/ieee80211/phy1/ath10k/fw_stats
without it causing a never ending string of mess in dmesg .... so that is all now amusing I guess Razz

EDIT: No no no you are lyin --
it still floods dmesg with spam ... just not as fast as the old ath10k FW did .... this build also still has the 'unknown event' crap.
[ 9698.177310] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9698.211494] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9706.824294] ath10k_pci 0001:01:00.0: dropping fw peer stats
[ 9718.180172] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9718.214350] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9738.181284] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9738.215947] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9751.128129] ath10k_pci 0000:01:00.0: dropping fw peer stats
[ 9758.185257] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9758.219442] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9778.188058] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9778.222726] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9798.190995] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9798.225181] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9818.193546] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9818.227720] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[ 9824.224800] ath10k_pci 0001:01:00.0: dropping fw peer stats
[ 9888.175591] ath10k_pci 0000:01:00.0: dropping fw peer stats
[ 9959.643810] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10025.218215] ath10k_pci 0000:01:00.0: dropping fw peer stats
[10096.548300] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10154.254622] ath10k_pci 0000:01:00.0: dropping fw peer stats
[10233.573784] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10277.694431] ath10k_pci 0000:01:00.0: dropping fw peer stats
[10370.606881] ath10k_pci 0001:01:00.0: dropping fw peer stats
[10400.938433] ath10k_pci 0000:01:00.0: dropping fw peer stats

oh well, we'll reboot and just let it cook for few days Twisted Evil


so u got the spam too, a bit different but still spam (i hate that "meat", if u get the joke there)

_________________
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/QCA9888 ------> r45891 std
[QUALCOMM] DIR-862L --------------------------------> r45891 std
[QUALCOMM] WNDR4300 v1 --------------------------> r45891 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] DIR-862L --------------------------------> r45891 std
[BROADCOM] DIR-860L A1 ----------------------------> r45891 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Fri Nov 10, 2017 20:37    Post subject: Reply with quote
For those that might want to squeeze the last bit out of your EA8500.
The new openSSL seems a bit faster than previous.

Maybe BS will do public release soon for all Razz

Here is the 'dd-wrt r33721 std (11/09/17) for EA8500'
Goto page Previous  1, 2, 3 ... 81, 82, 83 ... 123, 124, 125  Next Display posts from previous:    Page 82 of 125
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum 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