Asuswrt-Merlin 380.59 is now available

[ColinTaylor]

@PartisanEntity Did you read through the posts between @cowst and RMerlin? Their conclusion was that it was caused by the /jffs partition not being writable. Is yours the same?

 

[PartisanEntity]

@ColinTaylor Thank you very much. I seem to have missed that. That was it, I formatted the JFFS partition and rebooted and now all is fine.

 

[Darunia]

'For the past couple of weeks the Network Map wasn't loading all of a sudden. I go to Tools > Sysinfo, go down to Ethernet Ports and find this message: 'Querying switch...' Everything plugged into the Ethernet ports and the router itself works fine otherwise. There's days where it queries the switch fine and shows what's plugged in along with the Network Map like normal, other times it goes back to that message. Any ideas what's going on?'

Remove the apostrophes.

Since June 21st when you said that I did remove all punctuation from my devices. This morning the same problem has reappeared again. As I've said previously I wasn't having this issue with previous firmware until 380.59. Takes about 3 or 4 reboots for the Network Map to start working again properly.

 

[Blinkyz]

'For the past couple of weeks the Network Map wasn't loading all of a sudden. I go to Tools > Sysinfo, go down to Ethernet Ports and find this message: 'Querying switch...' Everything plugged into the Ethernet ports and the router itself works fine otherwise. There's days where it queries the switch fine and shows what's plugged in along with the Network Map like normal, other times it goes back to that message. Any ideas what's going on?'



Since June 21st when you said that I did remove all punctuation from my devices. This morning the same problem has reappeared again. As I've said previously I wasn't having this issue with previous firmware until 380.59. Takes about 3 or 4 reboots for the Network Map to start working again properly.

Same issue "querying switch" without any quote or apostrophe or etc.... only Alphanumeric
Was on 380.60 b2 = "Message cable is unplugged "
On 380.59 since 2 days= Querying switch just appear this morning

Going back on .58( was solid for 30 + days before .59 and .60)

 

[StevenG]

I have just gone through all 35 pages of posts, trying to take my first plunge into Merlin's firmware on my N66U. I've been running Shibby Tomato the last couple of years and the stability has dropped off a bit. I'm ready to get back to Asus stock, or at least something very close like Merlin has done here.

But after reading all the pages, I can't determine if 59 is really screwed up, or if many of theee issues are do to such complex configurations. Should I not go with 59, and just load 58 for now, until 60 comes out and is proven to be solid? Just trying to read between the lines and gauge what others think.

RMerlin, this is your firmware, what do you think? Are you tracking as many bugs in 59 that I think I read, or does it look way worse than it really is?

Thank you

 

[L&LD]

StevenG, imo, you should go to 380.60 Beta 2 instead.

Know the limitations of doing so (no ability via the gui to go back to another version), do a full reset to factory defaults and then minimally and manually configure the router to secure it and connect to your ISP.

With the next version past 380.60 Beta 2, it may not be possible to use older firmware at all (even using the CFE methods).

But, yes, 380.59 is not worth 'testing' right now.

 

[OsoTheBear]

I have just gone through all 35 pages of posts, trying to take my first plunge into Merlin's firmware on my N66U. I've been running Shibby Tomato the last couple of years and the stability has dropped off a bit. I'm ready to get back to Asus stock, or at least something very close like Merlin has done here.

But after reading all the pages, I can't determine if 59 is really screwed up, or if many of theee issues are do to such complex configurations. Should I not go with 59, and just load 58 for now, until 60 comes out and is proven to be solid? Just trying to read between the lines and gauge what others think.

RMerlin, this is your firmware, what do you think? Are you tracking as many bugs in 59 that I think I read, or does it look way worse than it really is?

Thank you

I have N66R, which is basically identical to the U version. I've been running 59 on it for more than 3 weeks already. I'm happy to report that it's very stable.

 

[OsoTheBear]

StevenG, imo, you should go to 380.60 Beta 2 instead.

Know the limitations of doing so (no ability via the gui to go back to another version), do a full reset to factory defaults and then minimally and manually configure the router to secure it and connect to your ISP.

With the next version past 380.60 Beta 2, it may not be possible to use older firmware at all (even using the CFE methods).

But, yes, 380.59 is not worth 'testing' right now.

I thought 380.60 was missing some required components to work properly on N66U and AC66U? Or maybe I'm missing something?

 

[Blinkyz]

I thought 380.60 was missing some required components to work properly on N66U and AC66U? Or maybe I'm missing something?

380.60 beta is not ready for MIPS model like n66.Components are still missing for compile and if you flash with 380.60 now or latest official Asus serie 304_3XXX , you cant downgrade after

So the Wise choice for now is 380.59 or 380.58

http://www.snbforums.com/threads/im...le-with-asus-3-0-0-4-380_3000-or-newer.32962/

 

[StevenG]

I thought 380.60 was missing some required components to work properly on N66U and AC66U? Or maybe I'm missing something?

I read that in the .60 beta thread, so didn't even consider it. Hoping Asus gives what RMerlin needs so it can get into a final release.

 

[OsoTheBear]

I read that in the .60 beta thread, so didn't even consider it. Hoping Asus gives what RMerlin needs so it can get into a final release.

I'm on 380.59 and happy with it. So I'm not in a rush to upgrade to .60.

 

[RMerlin]

I have just gone through all 35 pages of posts, trying to take my first plunge into Merlin's firmware on my N66U. I've been running Shibby Tomato the last couple of years and the stability has dropped off a bit. I'm ready to get back to Asus stock, or at least something very close like Merlin has done here.

But after reading all the pages, I can't determine if 59 is really screwed up, or if many of theee issues are do to such complex configurations. Should I not go with 59, and just load 58 for now, until 60 comes out and is proven to be solid? Just trying to read between the lines and gauge what others think.

RMerlin, this is your firmware, what do you think? Are you tracking as many bugs in 59 that I think I read, or does it look way worse than it really is?

Thank you

I consider 380.59 to be a stable release. A lot of the "issues" are from people running highly customized setups, or putting the blame on the router for any wifi-specific issues they might encounter when sometimes the cause lies outside of the router (outside interference, for instance).

 

[L&LD]

I have just gone through all 35 pages of posts, trying to take my first plunge into Merlin's firmware on my N66U. I've been running Shibby Tomato the last couple of years and the stability has dropped off a bit. I'm ready to get back to Asus stock, or at least something very close like Merlin has done here.

But after reading all the pages, I can't determine if 59 is really screwed up, or if many of theee issues are do to such complex configurations. Should I not go with 59, and just load 58 for now, until 60 comes out and is proven to be solid? Just trying to read between the lines and gauge what others think.

RMerlin, this is your firmware, what do you think? Are you tracking as many bugs in 59 that I think I read, or does it look way worse than it really is?

Thank you

As people have rightly pointed out, the RT-N66U does not have an 380.60 Beta 2 version available.

Please ignore my post 695 for that and similar processor powered models. I guess I didn't see the model of router you were considering it for.

Sorry!

 

[terribell]

For the RT-N66, if WIFI range and router stability is important, I recommend John's fork.
Been running it on my RT-N66 with uptime of months.

 

[StevenG]

I'm on 380.59 and happy with it. So I'm not in a rush to upgrade to .60.

Which router are you using it on?

 

[StevenG]

For the RT-N66, if WIFI range and router stability is important, I recommend John's fork.
Been running it on my RT-N66 with uptime of months.

I must have missed something. John's fork?

 

[terribell]

I must have missed something. John's fork?

Yes, you can find it here: http://www.snbforums.com/threads/fork-update-for-374-43-available-v17e8-v18b9.18914/

This fork includes the wireless drivers which most of the people say have better range and since the code base has not changed for a long time, it may be more stable.

 

[OsoTheBear]

Which router are you using it on?

I'm using it on N66.

 

[Blinkyz]

If you go with John fork(awesome fw) and want to go back to 380.59 after, you need to flash with 378.55 before 380.59 and Factory Reset at the end when .59 is installed

 

[StevenG]

I'll probably want to just stick with Merlin's version. Closest to stock, with the stupid stuff solved, is what I'm looking for.