Posted: Sat Jul 11, 2009 4:16 Post subject: EKO 12476 NEWD-2 Only Thread
Although these test releases all carry some risk, the NEWD-2 build is particularly risky, and does brick some routers. Flashiing this build onto routers without the ability to jtag it is extremely risky.
That being said, we will compile a list here of the builds that work and those that don't.
This thread is for discussing the testing of build 12476 NEWD-2 only. Please post your experiences with this build, but do not seek assistance for your router in this thread, or discuss off topic items such as the mW limitations of 610N etc. If you need assistance for your router, start a new thread on your issue.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Last edited by Murrkf on Sat Jul 11, 2009 4:27; edited 3 times in total
Wrt54G V8 - Brick via newd2
wrt54g-TM - success, newd2 mini
wrt54g-TM - success, newd2 mega (reported from another member)
wrt54g-GL - Brick via newd2
wrt300n V1.1 - success (reported from another member)
wrt54g-V5 - success, micro plus (reported from another member) _________________ [MODERATOR DELETED]
Once we get through bricked vs. success thing, we would need to discuss the actual build.
Running mini on my TM, gateway, dhcp server, ap. No issues so far. TX power setting IS working. QOS IS working (HTB). I don't use upnp but I do test. I'm skipping upnp testing this time around unless "not working" reports show up. _________________ [MODERATOR DELETED]
Last edited by barryware on Sat Jul 11, 2009 5:12; edited 1 time in total
NEWD2 has been working well on my WRT600N's, V1.0 and V1.1 for a good 3 weeks now. No major issues to report. 2.4GHz Tx power still isn't quite right though. _________________ WRT600N v1.0 & v1.1 - Eko 12548M std-nokaid NEWD-2
Last edited by greekstile on Sat Jul 11, 2009 13:46; edited 1 time in total
Joined: 04 Jan 2007 Posts: 10812 Location: Wherever the wind blows- North America
Posted: Sat Jul 11, 2009 12:32 Post subject:
barryware....I read your reference to my chart in the other "Locked" thread....but I wanted to let you know...I expanded on it just a bit...I looked at the interface ID numbers to try to figure this out further...still no correlation.
If anyone has any ideas...let me know...I'll try to find some time to check into this futher.
redhawk
Clipboard01.jpg
Description:
Filesize:
78.11 KB
Viewed:
26927 Time(s)
_________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
Joined: 04 Jan 2007 Posts: 10812 Location: Wherever the wind blows- North America
Posted: Sat Jul 11, 2009 12:35 Post subject:
I have NEWD2 working on
Asus WL-520GU (usb_ftp_610n) - this is NEWD2
Buffalo WHR-HP-G54 (NEWD2-nokaid)
Buffalo WHR-G54S (NEWD2-nokaid and mini)
Linksys WRT54Gv5 (NEWD2-Micro_plus)
redhawk _________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
barryware....I read your reference to my chart in the other "Locked" thread....but I wanted to let you know...I expanded on it just a bit...I looked at the interface ID numbers to try to figure this out further...still no correlation.
If anyone has any ideas...let me know...I'll try to find some time to check into this futher.
redhawk
I'm wondering if this just isn't a "bug" that is being blamed on the new driver.. Get what I am saying? Maybe there is nothing wrong with the driver.
A V5 runs, a V8 doesn't. Tm runs, GL doesn't. You would thing if anything, the older equipment would have the problems..
If it were just the driver, you would think that just the radio would have problems, not brick the router. Like the other day.. Vint was bricking devices. What was the actual cause of that? _________________ [MODERATOR DELETED]
Joined: 04 Jan 2007 Posts: 10812 Location: Wherever the wind blows- North America
Posted: Sat Jul 11, 2009 12:46 Post subject:
agreed...I think it is a detection issue with the FW. Missing a boardflag, devicetype, some radio parameter maybe....something not detecting the radio as being supported.
I know Eko was trying to figure this part out too.
I just can see why a
GL won't work, a TM will - same chipset
520GU will, 614L won't. - same chipset
They have the same chipsets...so it must be a detection issue...but what is the key parameter that determines this.
That is why I started looking at some of the "ID" information in the variables...I just haven't found that correlation yet.
We'll figure it out...it just may take a while.
Anyone else have any ideas...I am open to them...I'll try to test anything I can.
redhawk _________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
If I'm not wrong Eko's NEWD-2 builds are using Broadcom version 4.150.66.6 wireless drivers.
Victek's Tomato firmware Mod is using Broadcom version 4.158.4.0 wireless drivers which seem more recent than the ones eko is using and I can confirm that there have been no problems.
Installs and runs fine on GL's, Asus 520GU and others that usually run fine with a normal ND build.
