What's new

How Stable is Beta?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

BassKozz

Occasional Visitor
I am debating whether or not to upgrade from the 3mth old "stable" release (3.0.0.4.270.26b) to the current "beta" release (3.0.0.4.354.29-BETA1), I don't really NEED any of the features added in the past 3mths but I would like the added stability/bugfixes that have been added.

I am typically of the mind if it ain't broke don't fix it, but I am curious to know if there are any known issues in the current 'beta' releases that cause them to not be considered stable? Or if there is an ETA for a new release that will be labeled 'stable' ?

TIA,
-BassKozz
 
I am typically of the mind if it ain't broke don't fix it, but I am curious to know if there are any known issues in the current 'beta' releases that cause them to not be considered stable? Or if there is an ETA for a new release that will be labeled 'stable' ?
Hi,

This was already dicussed in the Beta-Thread: The conclusion is simple!

Stay with the last stable version if you do not have problems (or need the new addons)! :rolleyes:
Or you could say: Never change a well running system! ;)

The Beta-Version works fine for most people, expect the 5GHz WLAN issue with Intel WLAN Client Chips (and others). :eek:
Some people report different types problems, but most of them have other reasons the the Beta version of the firmware.

With kind regards
Joe :cool:
 
Last edited:
My Linksys AE3000 USB wireless adapter also won't connect with 40MHz. channel width on 5GHz. with the latest firmware wireless driver, which means that the fastest it'll go is 216Mbps instead of 450Mbps. And that uses a Ralink chip set. So there's more than just Intel wireless adapter chipsets that are affected by this buggy wireless driver.

As a result, I don't use the Beta firmware versions. Am using 270.26b instead, which works great, and gives me a full 450Mbps connection. I'd really like to be able to use the latest features in newer firmware, but won't be doing that until Asus provides a fixed Broadcom wireless driver.
 
It's definitely not just intel wireless cards that have problems with 354 beta and 370 5ghz. I have linksys AE2500's with Broadcom chipsets inside and they do not work very well with 354 beta 5ghz and 370 5Ghz. I keep seeing people post over and over that there is a compatibility problem with certain intel wireless cards when that's simply not the case. There's a lot more than just intel wireless cards.

Asus seems to be in some type of denial mode on this. Which basically translates to: they won't be fixing it, IMO.
 
It's definitely not just intel wireless cards that have problems with 354 beta and 370 5ghz. I have linksys AE2500's with Broadcom chipsets inside and they do not work very well with 354 beta 5ghz and 370 5Ghz. I keep seeing people post over and over that there is a compatibility problem with certain intel wireless cards when that's simply not the case. There's a lot more than just intel wireless cards.

Asus seems to be in some type of denial mode on this. Which basically translates to: they won't be fixing it, IMO.

i have problems with my macs which all have Broadcom chips. jlake please contact asus, (jermemy) and let him know about your issues. (I have already, the more people who do this the better)
 
Thanks vdemarco. I did contact him a few days ago. I've read all of the posts/threads regarding the 5Ghz issue in this forum. I wouldn't hold your breath for a fix. My guess is that mainstream consumers that are purchasing the RT-N66U now aren't updating the firmware to even know if they have the problem. Therefore, there will a be a low number of complaints and products returns and bad reviews. The router now comes with .260 installed and .260 appears to be broadly compatible on 5 Ghz. Asus isn't doing anything as long as they don't get a bunch of bad reviews and product returns. It's unfortunately how the business works.

If you read between the lines of Merlin's posts regarding this issue, it won't be fixed. He's stated numerous times "it's not that simple". Since he's in the loop, I wouldn't plan on ever seeing an update. If you noticed that 354 was beta and they went ahead and put out the non-beta 370 with the same 5 ghz issue for many of us-----that was a strong statement from Asus, that they are going with it. They read this forum. They read the 354 beta thread and the rest of the 5Ghz threads. They basically are telling us that we're SOL and we need to cough up $50-$100 per computer for new adapters if we want to move past .270 firmware. Which of course sucks if you have multiple adapters that don't work on 5Ghz with the new firmware.
 
The router now comes with .260 installed and .260 appears to be broadly compatible on 5 Ghz.

Is it suggested that the 260 version doesn't have issues with the signal drop on 5 Ghz?

That's the only issue I have--I don't have some of the issues with Xbox for example that others are having. Maybe I should roll back to that version.
 
If you read between the lines of Merlin's posts regarding this issue, it won't be fixed. He's stated numerous times "it's not that simple". Since he's in the loop, I wouldn't plan on ever seeing an update.

This is completely wrong.

"It's not that simple" simply means it's not something that can be fixed overnight just by changing a few lines of code. Asus has to work with Broadcom on this type of issue, it's not entirely just in their own hands.

Asus are aware of the problem, and they do intend to have it fixed.
 
This is completely wrong.

"It's not that simple" simply means it's not something that can be fixed overnight just by changing a few lines of code. Asus has to work with Broadcom on this type of issue, it's not entirely just in their own hands.

Asus are aware of the problem, and they do intend to have it fixed.



Listen to what he says.

If this was a end of a life product then we may be sol but this is a relatively new product no where near its end of life.

Its also clear this isn't just a mere driver issue which would be simpler to fix but a couple of things likely interconnected to each other.

The man has never steered you wrong yet and i don't see that happening.:D
 
Last edited:
Thanks for all the great feedback everyone, I will be sticking w/ 3.0.0.4.270.26b for the time being.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top