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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've tried that though. Look confusing. Give me some light
Actually I got problem with these things especially kupdated. Sometimes (about every 10 minutes, it used up my cpu (100%), slow down mouse pointer, and sometimes even disconnect my modem! Can I disable this thing? I have problem with this only with my slow processor though (1.3Ghz Duron). I don't seem to have problem with my 2400XP Athlon even with kupdated running.
I recompile the kernel, include all IDE chipsets and no more problems! This is the answer (somewhere in 100th page of google search result):
Quote:
Problem:
When using the disk kupdated hogs the cpu, making the system slow to a crawl. The mouse stops responding for several seconds at a time. Serial comm gives errors like "/dev/ttyS0: 1 input overrun(s)".
Cause:
Slow IDE throughput due to unsupported chipset. Run 'hdparm -t /dev/hda' to make sure (it will be really low, around 2-6mb/s)
Solution:
Compile a kernel that supports your IDE chipset (just enable them all).
Reason:
<sholom> koala_man: Btw, the 'reason' part for the 'kupdated hogs CPU because of disk usage' thing is because the system runs in PIO mode, meaning the main CPU have to manage all reading and writing, rather than letting the chipset use busmastering.
Originally posted by chii-chan I recompile the kernel, include all IDE chipsets and no more problems! This is the answer (somewhere in 100th page of google search result):
I want to say a big thank you for this advice (it worked for me). I also wanted to mention that it is important not to use modules. I would recommend that you find out what chipset your motherboard has and then only enable that kernel driver (smaller the kernel the better is what I've always heard).
Another note: you can use hdparm -d /dev/hd* (where * is the device letter) to check on whether or not dma was enabled successfully.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.