have u tried the newer board-2.bin? if u did what changes do u see from it if any, on lede?
happy new year
We already had this board-2.bin in the build for some time. The current fw from codeaurora has a problem with 160Mhz operation, crashes the radio. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
I have a trouble with VHT160, it doesn't work. If I set my ath0 to 160mhz, from the info page I can't see the speed, or nothing else, no clients connected... what <i'm doing wrong?
I have a trouble with VHT160, it doesn't work. If I set my ath0 to 160mhz, from the info page I can't see the speed, or nothing else, no clients connected... what <i'm doing wrong?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Jan 11, 2017 10:02 Post subject:
153+155 is normal. there is a bug where u pick 161 lower or 149 upper and it does something else. but 153 is a valid config, its part of the upper/lower, lower/upper combos that ac can do like what broadcom does. but qca units arent updated for these configs yet. myself have 149+upper selected. its using 153. so hw/fw can do it, ddwrt just needs updating for it. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
and I still have the same troubles with ath0 interface: unknown status with VHT160 enable, works with HT80 but my devices can't join it...
Untill this bug will be fixed I ask again if someone can send me a link to the r30940 (because I saved only r30880 who works fine but is a bit old). Thanks!
** Edit **
I was able to use Kongs previous stock to ddwrt img file he had under a separate folder to get the router flashed.
Not sure if it was the image revision difference, the fact I rebooted the new router again, moving the cat5 from port 3 to 1 on the router or some combination there of.
Once there, I had no issue using the .bin to upgrade to the latest/current.
** End **
Guys, back on page 4 a couple of users were having issues with loading the initial kong firmware on the router which according to Kongs follow up post said it was because of debug symbols added by him which made the file slightly larger than the router wanted.
Anyone got an older version of Kong initial load firmware I can use to put on my new R7800?
I am having the exact same issue with the current distro on his page.
Thinking that if there is a slightly smaller size .img file it should also work for my stock router as it did for those 2 guys on page 4.
Thank you _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
WOW, that will be very cool. I hope that hardware-nat will be added to dd-wrt. _________________ TPLINK WR1043ND V3
Firmware DD-WRT v3.0-r33772 std (11/16/17)
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Jan 24, 2017 1:48 Post subject:
i hope thats not like ddtb that was attempted couple years ago..it was the buggiest thing ddwrt ever seen & it didnt play nice with qos.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Jan 27, 2017 13:50 Post subject:
next build will have working vht80+80 for the first time cause of the new ath10k 10.4-3.4 fw. also noise floor is now perfect, before when using wds, noise floor was correct for all devices on the other radio & the wds station, but other devices on the same radio as the wds station always said -95. also 2.4ghz radio noise floor no longer displays 0 snr for 1 second when switching between ath0 & ath1 at wireless status page.
contiguous vht160 still not working (maybe its ath10k driver that broke it?) but vht160 via 80+80 is. but it only uses upper band for the second 80mhz half, primary (first) 80mhz half must be from 36-128, no way to pick 149 or 161 & have the second 80mhz half be put on the lower band.
channel selection is still a mess showing a bunch of invalid combos as usual. not seeing any new problems yet, looks like should be a good release (as of now anyway) at least for this router.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers