Hello Thomas, I have to admit ignorance. What is the "DMA driver?" I'm going through menuconfig and am not sure what you're referring to. Is it the stuff that shows up as "Generic PSI bus-master DMA support" in menuconfig? If so, it's already compiled into the kernel directly.
Also, to give folks a clearer picture: the system does *not* boot from the IDE disks. It boots from a software raid1 mirror of two SCSI drives. The IDE drives are meant to be used, along with 4 SATA drives, in a raid5 array for a big storage area. Another poster suggested adding amd74xx to the /etc/modules file *before* ide-generic, but this doesn't seem to make any difference. On the stock AMD64 Sid install, which file controls what's going on in "module land:" /etc/modules or /etc/modprobe.d/aliases? They seem to be redundant... thanks, Jim On 4/20/05, Thomas Steffen <[EMAIL PROTECTED]> wrote: > On 4/20/05, Jim Wiggs <[EMAIL PROTECTED]> wrote: > > Folks, > > > > I've got a box built on the ASUS K8N-E Deluxe motherboard, and I > > absolutely > > can not get DMA working on my hard drives. I am running the Debian 2.6.11 > > kernel, to which I have applied the fixes suggested at: > > > > http://download.nvidia.com/XFree86/nforce/1.0-0301/KnownProblems.html > > > > But no joy. My only clue is that there are dmesg log messages which seem > > to suggest that by the time the NFORCE driver loads, the generic IDE drivers > > have already grabbed control of the ide interfaces (NFORCE3-250: "port > > 0x01f0 > > already claimed by ide0"). But how do I prevent this from happening? > > I had the same problem, and I had to compile the DMA driver into the > kernel to get it working. It seems that some DMA drivers have to > activate DMA during the boot process. > > Thomas >
