From: maxxle@t-online.de (maxxle)
To: linux-kernel@vger.kernel.org
Subject: Can't enable dma on /dev/hda
Date: 11 Feb 2003 19:31:16 +0000 [thread overview]
Message-ID: <1044991886.3923.43.camel@sam> (raw)
Hi!
I'm running a debian 3.0 System using kernel 2.4.19 (also tried 2.4.20).
On this system it's not possible to enable dma on /dev/hda (HDD IDE)
The MoBo is a VIA Board called VIA-C3M266 (CLE266 chipset)
Northbridge: VT8623
Southbridge: VT8235
My kernel is compiled with this features:
ATAPI/IDE/MFM/RLL support --> IDE, ATA and ATAPI Block devices -->
[*] generic PCI bus-master DMA support
[*] Use PCI DMA by default when available
[*] VIA82CXXX chipset support
And this is what hdparm tels me:
hdparm -d 1 /dev/hda:
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
What can I do to force my system to run using dma on /dev/hda.
Or is my CLE266 chipset a bit too new for being supported by 2.4.19/20?
Hope somebody is able to help me
maxxle
next reply other threads:[~2003-02-11 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 19:31 maxxle [this message]
2003-02-11 23:06 ` Can't enable dma on /dev/hda agri
2003-02-12 0:45 ` Alan Cox
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=1044991886.3923.43.camel@sam \
--to=maxxle@t-online.de \
--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