Ok... but who said 600n is supported with Newd-2 driver? I didn't... newd-2 k24 supports only wrt610nv1 officially. All the rest is experimenting.
we are experimenting...just trying to figure some things out here with no success :P
We know the 600N bricks with K26...but it was supposed to work initially...so maybe newd2 is why? Just thinking out loud here and sharing thoughts
I haven't flashed any recent builds on either of my 600N's. But on both my 1.0 and 1.1, I never experienced any of these issues with NEWD-2. Both radios always initialized perfectly upon every flash and subsequent reboot. Never once have I observed any of this strange behavior. _________________ WRT600N v1.0 & v1.1 - Eko 12548M std-nokaid NEWD-2
It's not a priority. I got bitchslapped by LOM for even bringing it up. I can't figure out why they're being so obtuse about this. Maybe we didn't bow and scrape enough??
Keep in mind, 2.4GHz Tx power still isn't working for many routers either. Point is, even though we may think it's an important issue, the devs apparently, do not. _________________ WRT600N v1.0 & v1.1 - Eko 12548M std-nokaid NEWD-2
Posted: Mon Jan 11, 2010 21:39 Post subject: Re: @ LOM - Need opinion
Holy Threadjacked post. What the frig does the discussion in the latter part of this thread have to do with the question BW asked LOM, specifically, about?
barryware wrote:
The plan is to install the flash chip from the V1, to the fubar'd V1.1.. Aught'a work.. Right?
An alternative is I have a 300 V1.1 that I can jtag all day but it won't run cuz of some other hardware problem.. I was thinking of flashing a 600 cfe on the 300, then swapping the flash chip..
Wadda'ya think?
No wonder people are getting bitch slapped....you turned this thread into a bitch session. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
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.."
Frater probably posted in this thread because he thought Eko was monitoring it. He keeps contacting Eko, trying to get a response regarding some issues that are negatively affecting his ORW script, and is not getting any response. Hence the threadjack...
Ok... but who said 600n is supported with Newd-2 driver? I didn't... newd-2 k24 supports only wrt610nv1 officially. All the rest is experimenting.
we are experimenting...just trying to figure some things out here with no success :P
We know the 600N bricks with K26...but it was supposed to work initially...so maybe newd2 is why? Just thinking out loud here and sharing thoughts
I haven't flashed any recent builds on either of my 600N's. But on both my 1.0 and 1.1, I never experienced any of these issues with NEWD-2. Both radios always initialized perfectly upon every flash and subsequent reboot. Never once have I observed any of this strange behavior.
Have you tried power cycling your router right after you loaded newd2 firmware? I do this all the time. If you don't power cycle you will not get the issue, but if you get a power outage it will do it. _________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
Have you tried power cycling your router right after you loaded newd2 firmware? I do this all the time. If you don't power cycle you will not get the issue, but if you get a power outage it will do it.
Yes, I always power cycle after flashing. And have power cycled many times since. I remember both you and Macgyver reporting this issue upon first flashing NEWD-2 builds on your routers. But I never saw it then, and I have yet to see it now. Maybe this week, I will flash a recent build if I can find the time. But I don't think it will matter. _________________ WRT600N v1.0 & v1.1 - Eko 12548M std-nokaid NEWD-2
