From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: Bill Waddington <william.waddington@beezmo.com>
Subject: Re: SATA Conflict with PATA DMA
Date: Sun, 16 Apr 2006 04:48:47 +0100 [thread overview]
Message-ID: <200604160448.47225.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <p9f2425uijetlpcq49m08cto9la898l80f@4ax.com>
On Saturday 15 April 2006 19:38, Bill Waddington wrote:
> On Sat, 15 Apr 2006 16:42:22 UTC, in fa.linux.kernel you wrote:
> >Esben Stien wrote:
> >> I'm having problems enabling DMA for my PATA HD.
> >>
> >> hdparm -d1 /dev/hdb reports:
> >> HDIO_SET_DMA failed: Operation not permitted
> >>
> >> Of course, I'm super user. Nothing is printed in dmesg.
> >>
> >> I'm on linux-2.6.16 and motherboard is Fujitsu Siemens D1561 with an
> >> ICH5. I also have a SATA hd in the computer and this only happens when
> >> the SATA hd is there. If I remove the SATA HD, then I can enable DMA
> >> for the PATA hd.
> >
> >Disabled combined mode in BIOS.
>
> If only that was possible on my fscking T43. *sigh*
Not sure if this is universal, but if Linux doesn't claim the PATA interface,
the SATA seems to drive optical drives on (presumably) the other channel
(ICH7 here, on a Dell laptop with a similar BIOS limitation).
Try CONFIG_IDE=n and boot with libata.atapi_enable=1 and see what happens...
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-04-16 3:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.m9JwGQvLBixssS4UodPQfih6Ygk@ifi.uio.no>
2006-04-15 17:02 ` Esben Stien
2006-04-15 16:41 ` Jeff Garzik
2006-04-23 17:54 ` Esben Stien
2006-04-23 18:00 ` Esben Stien
2006-06-10 20:39 ` Esben Stien
2006-06-15 17:29 ` Esben Stien
[not found] ` <fa.foo0W8w4UdiDztK9eBiA9awyAi8@ifi.uio.no>
2006-04-15 18:38 ` Bill Waddington
2006-04-16 3:48 ` Alistair John Strachan [this message]
2006-04-16 4:30 ` Randy.Dunlap
[not found] ` <fa.UjEGyG0y7x3qVLsO0eHpXVza2r8@ifi.uio.no>
2006-06-10 22:58 ` Bill Waddington
[not found] <61Y0s-AN-23@gated-at.bofh.it>
[not found] ` <61UzA-43O-5@gated-at.bofh.it>
[not found] ` <61Y0s-AN-25@gated-at.bofh.it>
[not found] ` <61Y0s-AN-21@gated-at.bofh.it>
2006-04-15 23:33 ` Robert Hancock
2006-04-15 23:51 ` 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=200604160448.47225.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=william.waddington@beezmo.com \
/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
all inboxes | Powered by JetHome®