Short bio: Computer Scientist, FOSS supporter (read more)
Tux Machines (TM)-specific
I didn't spot too much really new with yesterday's (or the day before's) release of SimplyMepis 6.5.rc3, but there were two noteworthy improvements. ..or rather one noteworthy improvement and one feature addition.
One can see by the screenshot that Beryl xgl/3D desktop is in the boot/install image and if one has an nvidia graphics chip, one can choose support at boot. Then at login one can choose KDE 3D if they wish. It still has quite a few bugs and the main one being that no windows will show their content. This is a major drawback.
But the real good news is that the wireless connection that I've been complaining about all developmental cycle is now working. And I must say it's the best in the biz right now. What I mean by that is it worked at login automagically. I don't know if it used some driver included in the image or whether it found and loaded the windows driver itself, although I suspect the former, but this is the first time my wireless connection worked automagically with any distro! Kudos to the SimplyMepis team.
Suspend to ram worked - well half way. It goes to sleep, but it won't wake back up. So, that's a bummer. Wouldn't it be nice if they could get all that stuff working before final? (Of course this is just booting up the livecd. It may actually work if installed onto hard drive making sure the resume= parameter is being used.)
Just a quickie here. I'll probably wait until final to do a real review. I have Frugalware and Knoppix waiting for reviews as well as a couple of other developmental releases I'd like to download and test.
UPDATE: Well after further tests of the livecd I can report that suspend to ram just can't wake up. Again, to be fair I should mention this is from the livecd, but I really think it should wake on up even if running from the cdrom. Suspend to disk acts like it would work. It tries to come on back, but since it don't poll the devices again, it don't know to use the system on cdrom. Instead it just goes straight to grub. I feel like suspend to disk probably works. It doesn't go to sleep on its own even after the designated inactive time period, so these tests were run by clicking the suspend menu items manually.