From: Robert van Herk <rherk@students.cs.uu.nl>
To: linux-kernel@vger.kernel.org
Subject: Mouse problems solved...
Date: Tue, 27 Jan 2004 14:03:41 +0100 [thread overview]
Message-ID: <401661AD.7010801@students.cs.uu.nl> (raw)
Hi people,
Earlier today I mailed that I had a mouse going sluggish and crazy under
kernel 2.6.2 rc2.
The problem was just that my harddisk wasn't working in DMA mode.
For people that have mice going crazy, I solved my problem like this:
hdparm /dev/xxxx (e.g. hdparm /dev/hda)
There should be something like
/dev/hda:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 156301488, start = 0
If using_dma is off, than that might explain why your mouse is so
sluggish. Try hdparm -d1 /dev/xxx (this should put dma on).
If you get an error message, check whether you compiled your kernel with
the needed support for your motherboard chipset for DMA. If not so,
build the module that corresponds with your chipset, modprobe that
module and try again.
After this, mouse problems should be over...
Grtz
Robert
reply other threads:[~2004-01-27 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=401661AD.7010801@students.cs.uu.nl \
--to=rherk@students.cs.uu.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox