I just realized this is happening to me as well. I can't enable DMA to save my life, but I had DMA enabled under RH 8.0 and never had a hiccup. What's the deal with this "blacklist"? Here's the message from hdparm: # hdparm -X66 -d1 -u1 -m16 -c3 /dev/hda /dev/hda: setting 32-bit IO_support flag to 3 setting multcount to 16 setting unmaskirq to 1 (on) setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted setting xfermode to 66 (UltraDMA mode2) multcount = 16 (on) IO_support = 3 (32-bit w/sync) unmaskirq = 1 (on) using_dma = 0 (off) What's the trick here? Best, Ed On Thu, 2003-04-24 at 12:45, Shawn wrote: > On Thu, 2003-04-24 at 12:08, Steve Snyder wrote: > > All of the above is a very verbose way of saying that I'm skeptical that > > my controller (OPTi 82C825 [Firebridge 2, rev 48] on a Compaq Presario > > 1260) is blacklisted. Unless, of course, RH is adding to the blacklist > > found in the stock 2.4.20 kernel. > > As I mentioned in an email to you, specific drives are on a blacklist, > and perhaps specific controllers. > > The only thing I am very unclear on is as to whether or not a device > being present on the kernel "blacklist" as it were, would prevent hdparm > from enabling DMA. > -- Whip it, whip it good!
