View Full Version : StarV3 v1.1.5b build 1651 (beta-2) is ready for testing
The new release is available for testing. It is extremely BETA, and should not be used on mission-critical systems.
Downgrading back to previous V3 releases is possible.
Do not upgrade this release unless you are planning on working with us to help improve it. There are known problems, and there is a very good likelihood that your system will eventually lock up during testing.
Outside of the updated wireless support, the rest of the system should be reliable.
For more information, please visit the release page.
http://www.star-os.com/release-notes/starv3-1.1.5b-1651.htm
Please post your results in this thread.
Primary focus of this release is compatibility, and stability testing.
bobbyc
10-03-2006, 05:29 PM
I just loaded it on a WAR4 and WRAP2c. The only thing I've noticed so far is that the PPPoe server is enabled by default. I'll test the atheros/prism later.
Bob C
The PPPoE server isn't enabled by default, however if you upgraded from v2 that had it enabled, then it would have carried over to the new pppoe-enabled v3 release.
bobbyc
10-03-2006, 10:41 PM
So it is normal for it to be enabled on a war4 after performing the "/system factory" command?
I tested a WLM54G in 802.11b AP mode with a hwba11 ethernet bridge client (philips RF). Both client and AP are locked to 11mbps, power def, short preamble off, super a/g off.
The problem I saw was that the client would loose pings when the signal got worse than ~-60. When using 1.1.4, the signal can get as bad as ~-80 before the client looses pings.
The important thing to note is that 1.1.4 works fine all the way up to ~-80 signal with this type of client.
Interestingly enough, a orinoco usb client (hermes1) behaved fine on this beta; pings and speed were fine with signal all the way up to ~-80.
Bob C
bobbyc
10-03-2006, 11:14 PM
Update: I tested a SR2 in place of the WLM54G, and things worked great. So, whatever issue I was seeing is only an issue when the AP is a WLM54G. Perhaps that will shed some light.
Bob C
Thank you for the updates
bobbyc
10-04-2006, 10:05 AM
I'm going to do some more testing today with the WLM54G AP with other types of clients. So far I've just tested 1.1.4 and 1.1.5, and the philips RF based client (hawking hwba11 ethernet bridge) still has trouble with 1.1.5. My orinoco USB client and Orinoco PCMCIA card/laptop do just fine with 1.1.4 and 1.1.5.
I think I saw this as a caveat, but I noticed too that if the WLM54G is set at def power level, it barely has any tx power. If I set it to a value, such as 18, activate changes, then it is fixed. I can even go back to def, and activate changes, and it is still fixed. But if I reboot, it goes back to having a problem.
Bob C
The txpower problem on startup has been resolved in the next beta (effects AP mode).
The pppoe server was being enabled by default like you mentioned, and has been corrected in the next beta. Thank you for pointing this out.
The next beta will be released today.