Skip navigation.
Home
Now Shipping Version 8.0

Read this about SimplyMEPIS 3.4-3 RC 1

mmelbert's picture

Please read all of this before posting problems and e-mailing support. We will be updating this document as we find more problems and we will also update any fixes that we may find.

There have been a few items that have cropped up on SimplyMEPIS 3.4-3 RC1 and we currently working resolving them and we have updates on some of these issues.

1. The ext3 issue that Warren has fixed and a fix will be released in SimplyMEPIS 3.4-3 RC2. You can read more about the ext3 issue here: http://www.mepis.org/node/8821

2. Scanner issues. We have found that after switching to the udev system we missed a new group that was created for scanning devices. If you are having trouble scanning click on K -> System -> Kuser. Once you have started the KDE User Manager click on the "Groups" tab. Find the "saned" group , 101, and double click on it. Find your username in the right column, highlight it, and then click on the "Add" button. This should put your username in the left column with saned. Click ok to accept the changes. Your scanner should now work.

3. Parallel printers may not work unless you install MEPIS to your hard drive. We have seen this problem before and if your parrallel printer is not working running from the CD, install MEPIS and try it again.

4. Serial ports have been reported to not be present in some machines. We are working on this issue. It may be an issue of old kernel modules are not being loaded properly in the 2.6 kernel with udev.

5. ATI card may not be allowing users to power off their machines or switch users properly. This seems to only be a problem after installing the official ATI driver. This has not been found to be a problem with the free xorg driver. We have included a new version of te driver in this release and we dont know what is causing the issue. It could be anything from the new driver having a bug or how MEPIS has compiled the kernel module and included everything. We are researching a fix for this.

Thank everyone for their feedback. We are working on getting these problems solved. As we find more or fix issues we will address them here. Please check back for updates. If you are experiencing a problem that is not listed here please email us at .