Posted: Mon Apr 27, 2020 3:12 Post subject: BCM MIPS k4.4 coming soon to a(n older) router near you!
At least, based on the 43007 alpha build on my WNDR4500v2:
Linux version 4.4.219 OpenWrt GCC 9.2.0 r10890-7d542dc804
I'd been watching BS' MIPS k4.4 commits, so had been tracking the progress. I pinged him for any more info on it, incl on the mips32r1 build. Stay tuned.
My 4500v2 is still running Client Mode: 2.4 GHz -> 5 GHz AP. I will try adding a guest VAP tomorrow to see if it still works. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Mon Apr 27, 2020 3:21 Post subject:
I think it may be only certain MIPS routers. I was watching that and thinking, "Ahhh, @#$%^&*!", because K4.x builds don't work in bridge modes, last I knew. I guess we'll see what we see when we see it. The images for E4200 I think are still K3.x. About to find out the fun way
this one ain't broadcom but ---
WNDR3700 V4
DD-WRT v3.0-r43007 std (04/27/20)
Linux 3.18.140-d4 #76807 Mon Apr 27 05:18:29 +04 2020 mips
Linux version 3.18.140-d4 (gcc version 9.2.0 (OpenWrt GCC 9.2.0 r10890-7d542dc804) )
Ya, last night after posting this, for a minute I was thinking my 810L (MT7620A, also on k3.10) might get updated too, then remembered the commits were bcm mips only (incl the mips32r1 build, it appears).
BS said there was no new bcm driver; he ported it as a first step to a newer kernel. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Asus RT-N12B (...RT-N12D1)
DD-WRT v3.0-r43007 mega (04/27/20)
Linux 4.4.219 #267 Mon Apr 27 00:30:02 +04 2020 mips
GUI install over r42925
'dd-wrt.v24-43007_NEWD-2_K3.x_mega.bin'
guessing they should now change the file & directory name, huh
--
EDIT:
this old dog has:
CPU Features --> MIPS32r1 MIPS32r2 MIPS16 DSP DSP2
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Mon Apr 27, 2020 15:03 Post subject:
jwh7 wrote:
BS said there was no new bcm driver; he ported it as a first step to a newer kernel.
But not sure what the K3.x commits were for, except maybe the devices that will remain on 3.2, 3.5, 3.10, and 3.18. I don't think some devices will ever see a K3.x build, let alone K4.x.
On a semi-possibly-totally-unrelated note, K2.6 will no longer get anything after RHEL 6 support drops without someone pushing up sleeves and getting down and dirty to backport fixes. Only certain hardware out in the real world has recently stepped to a 3.x kernel, and they are still sorting out the issues because the proprietary hardware support for anything newer than K2.6 is not very forthcoming. In fact, the only folks besides RHEL that are still patching K2.6 is probably Cisco, but I think they are now using a 3.x kernel, too. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Posted: Tue Apr 28, 2020 18:50 Post subject: Re: BCM MIPS k4.4 coming soon to a(n older) router near you!
jwh7 wrote:
My 4500v2 is still running Client Mode: 2.4 GHz -> 5 GHz AP. I will try adding a guest VAP tomorrow to see if it still works.
I set up my unbridged VAP yesterday; works great.
Since I'm here, I should mention the BS said his plan is to update to k4.9, once he fixes the NAND driver. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Any help on urandom read issues or are those expected?
I have also noticed latest firmware (r43028) created a second nvram partition called nvram_cfe with the same start and end sizes as the first one. _________________ ASUS RT-AC68R: 42954
Belkin F7D7302: 43078
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Thu Apr 30, 2020 0:16 Post subject:
CTEC wrote:
I have also noticed latest firmware (r43028) created a second nvram partition called nvram_cfe with the same start and end sizes as the first one.
This is from my serial log after flashing 40559 (K3.x):
Code:
Creating 1 MTD partitions on "bcmsflash":
0x000000ff0000-0x000001000000 : "nvram_cfe"
This is from my syslog for 36154 (K3.x):
Code:
Jan 1 00:00:03 DD-WRT kern.notice kernel: 0x000000ff0000-0x000001000000 : "nvram_cfe"
It's been there a while. You should probably go back a ways and re-check
EDIT: It goes back to the 2**** build that was originally on my E4200 when it was given to me. I presume it was one of the builds that got removed from the server or some nonsense. From sometime in 2013. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I have also noticed latest firmware (r43028) created a second nvram partition called nvram_cfe with the same start and end sizes as the first one.
This is from my serial log after flashing 40559 (K3.x):
Code:
Creating 1 MTD partitions on "bcmsflash":
0x000000ff0000-0x000001000000 : "nvram_cfe"
This is from my syslog for 36154 (K3.x):
Code:
Jan 1 00:00:03 DD-WRT kern.notice kernel: 0x000000ff0000-0x000001000000 : "nvram_cfe"
It's been there a while. You should probably go back a ways and re-check
EDIT: It goes back to the 2**** build that was originally on my E4200 when it was given to me. I presume it was one of the builds that got removed from the server or some nonsense. From sometime in 2013.
Thanks for responding.
I guess I shouldn't worry about it then.
Are urandom read errors normal? I don't remember seeing that in the logs. _________________ ASUS RT-AC68R: 42954
Belkin F7D7302: 43078
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Thu Apr 30, 2020 2:38 Post subject:
CTEC wrote:
Thanks for responding.
I guess I shouldn't worry about it then.
Are urandom read errors normal? I don't remember seeing that in the logs.
Without going into another room and pulling more recent K3.x logs off the other laptop, this is definitely something "new" in the K4.x builds. I'm still on the 43007 alpha build. About to flash today's build here in a bit.
CONFIG_BOUNCE: Enable bounce buffers found in mm/Kconfig
The configuration item CONFIG_BOUNCE:
prompt: Enable bounce buffers
type: bool
depends on: CONFIG_BLOCK && CONFIG_MMU && ( CONFIG_ZONE_DMA || CONFIG_HIGHMEM )
defined in mm/Kconfig
found in Linux kernels: 3.10–3.19, 4.0–4.20, 5.0–5.6, 5.7-rc+HEAD
Enable bounce buffers for devices that cannot access the full range of memory available to the CPU. Enabled by default when ZONE_DMA or HIGHMEM is selected, but you may say n to override this. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4