Just a suggestion, but perhaps a sticky thread about K26, or an addition to the peacock thread would be helpful. _________________ WRT600N v1.0 & v1.1 - Eko 12548M std-nokaid NEWD-2
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Sat Oct 03, 2009 13:06 Post subject:
greekstile wrote:
What's with all the conservatism around here? It's almost discouraging the process. We are all basically crash test dummies. We all take a calculated risk evertime we flash ANY build. That's how progress is made.
I'm not encouraging anyone to blindly flash their router. Especially older routers. What's the point? You won't gain anything with the 2.6 kernel. We each have different levels of copetency and understanding. You shouldn't flash any of these test builds, let alone highly experimental builds, if you aren't willing to take the associated risks.
My router, the 600N, is basically the same as the 610N. Aside from the RAM and different radio. If K26 is close to being supported on that router, the 600N should be close as well.
I could certainly hook up a serial console to my 600N if something went wrong. It's not my first time around the block. Having said that, I'm probably going to wait until we get the green light from Eko. I just don't have the time to experiment.
Anyway, you guys should lighten up, just a bit. As the Joker said, "Why so serious?"
I agree...however, there has been countless hours spent with the "less" competent individuals who brick there routers only because warnings were not posted clearly enough.
I'm not trying to squash progress either...and the more adventurist (pioneers) will be trying to flash the K26 on anything that has LED's anyway. I am not worried about them...they generally already know how to recover.
But its the other 20+ people that try it...one right after the other then posts on the forum whining about a bricked router that eats up all our forum resources for days trying to debrick them due to their ignorance in the matter...and ours for not supplying the warnings properly.
That's all I am trying to accomplish here...just trying to get the proper warnings out to the world.
redhawk _________________ The only stupid question....is the unasked one.
This slashdot developers article and the comments following are informative in relationship to the various differences in the 2.4 vs 2.6 linux kernel in embedded devices. _________________ Eko Builds
This slashdot developers article and the comments following are informative in relationship to the various differences in the 2.4 vs 2.6 linux kernel in embedded devices.
Nice. There is some good info in those posts. It's pretty obvious, in reading through the posts, that one of the biggest benefits of 2.6 kernel is going to be better overall performance. It's just faster then the 2.4 kernel. _________________ WRT600N v1.0 & v1.1 - Eko 12548M std-nokaid NEWD-2
It's about time... I really would appreciate a 2.6 kernel build of DD-WRT. I like to use my 610N as a network-fileserver. But all my HDs are crypted with Truecrypt and are using a NTFS filesystem.
Joined: 18 Jun 2006 Posts: 87 Location: Netherlands
Posted: Wed Oct 14, 2009 11:34 Post subject:
I have the 2,6 Kernel running on my WRT320N and must say is very stable now for now.
the only minor thing is that the lan to lan is littebit slower than original (2.4 kernel)linksys firmware
now i get avr: 59,893.78 KBps on dd-wrt this whas 79,633.88 KBps on linksys firmware. _________________ WRT320N
Zyxel NBG-460N
Tp-Link WR-1043ND
Linksys E3200
read support shouldn't be a problem at all, but writing on ntfs devices could cause datacorruption or probably could crash the whole NTFS filesystem. the 2.6 kernel solved a lot problems with ntfs, at least thats what I "know" (or believe). I'm no "linux-guru", so correct me if I'm wrong, but accessing NTFS from Linux was very complicated for a long time..
read support shouldn't be a problem at all, but writing on ntfs devices could cause datacorruption or probably could crash the whole NTFS filesystem. the 2.6 kernel solved a lot problems with ntfs, at least thats what I "know" (or believe). I'm no "linux-guru", so correct me if I'm wrong, but accessing NTFS from Linux was very complicated for a long time..
Yeah that's how I recall the history of the NTFS driver. In 2.4 it was very buggy and was only reliable at reading, then much later in k2.6 it got improved so much that distros now include it by default. I don't know if the improvements were ever backported to k2.4 though. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I had corruption on the old 2.4 kernels a few times writing to ntfs back in the day, I'm sure there are backports in the ntfs source in todays 2.4 from 2.6 but word to the wise is don't write. The ntfs filesystem has changed some over the years too so writing to a windows partition is a definite no no, if you needed to write to ntfs make sure and format it with something like gparted in linux. Don't format your windows partition with any linux software as windows doesn't like this. _________________ Eko Builds
