i have recently installed mandrake linux 10 and its very very slow.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I cannot disagree more! Until Last spring when I installed Mandrake 10 on my P-III 700, I didn't know what speed with KDE was! It is the 2nd fastest binary distro I have tried (nest to Slackware 10). Its not KDE, not Mandrake, and definitely not kernel 2.6. Therefore, its a config somewhere.
I have ran Mandy 10 on a P-2 350mhz with 160mb ram and it was as tolerable as Windows XP on the same.
The DMA is likely the problem. I just reinstalled on a (new to me) Duron 800 system with 384 mb ram (VIA KT133 chipset). It ran like crap! The benchmarks on a Duron 800 are significantly higher than P-III 700, so I knew that something was wrong. After a bit of googling, I found that enabling generic IDE support as well as the VIA IDE support in the kernel made it revert to NO DMA!
Look through the output of "dmesg" or pore through the /var/log/messages file and see what is happening with your disk controller. It will explicitly show in the boot messages that DMA has been enabled for all drives involved. For example, mine has an ATA100 hard drive and the same for CD burner. The HD has an 80 wire cable so it shows UDMA@100 and the cd burner has a regular 40 wire cable and shows UDMA@33. You should find the same thing (or you could also load hdparm and test it. You should not get speeds of 3 or 4mb/s. It should be much higher if DMA works.
I agree with you. These guys are turning this into a big mess.
Ant, do this:
Open console, su to root and use hdparm to probe how is your system configured:
hdparm -I /dev/hda #assuming we're talking about hda
This will list several info about your disk. If you have any monitoring program like gkrellm, load it, do some file copying and see if is there much cpu activity during file copying (it shoudn't).
If dma ins't enabled, issue:
hdparm -d 1 /dev/hda
will enable dma transfer on this disk.
hdparm -k 1 /dev/hda
will tell it to keep settings.
Now, enable the highest dma speed for the disk:
This step is kinda risky, because you have to know for sure what speed your disk can handle. If its a 7200rpm, surely you can do:
hdparm -X 69 /dev/hda
and set speed for UDMA100.
Notice that, as vector said, enabling this setting will not yield benefit if you don't use 80pin flat cables. Also, the disk must be alone in the controller or together with another UDMA100 disk. Any slower disk will slow everything with it.
After all this, re-run the file copying test and see what gkrellm says about your cpu.
If everything worked, now you must ensure Mdk will do this every reboot, so you don't have to hdparm every time.
Additionally, you can set Mdk to run as few services/daemons as possible, by going to the setup and disabling everything you don't need. Just make sure you know what you are disabling, so you don't screw things.
Last edited by bruno buys; 09-01-2004 at 08:49 PM.