<other_stuff>
</other_stuff>
<important_bit>
>
> Here the kernel log:
>
> Jul 30 22:35:43 ruru kernel: hda: dma_intr: status=0x59 { DriveReady SeekComplete
> DataRequest Error }
> Jul 30 22:35:43 ruru kernel: hda: dma_intr: error=0x01 { AddrMarkNotFound },
> LBAsect=6815180, high=0, low=6815180, sector=6814976
> [3 more]
> Jul 30 22:35:47 ruru kernel: hda: DMA disabled
> Jul 30 22:35:47 ruru kernel: hdb: DMA disabled
> Jul 30 22:35:47 ruru kernel: ide0: reset: success
>
> This also shows the stupidity the Linux kernel exhibits when trying to
> be smart with hard disks which may not be capable of DMA: turn off DMA
> permanently and see if it works better. Fine during boot, plain stupid
> a few hours later. And gee thanks for turning DMA off on my dvdrom
> drive too. 2.6 is no better than 2.4 here.
</important_bit>
I think you will find this is purely distro specific , alot renable DMA
where possible once init has completed successfully (aka the gentoo that
many here seem to adore) , and personally id prefer to see it disabled
by default if dma isnt detected than it fsck' over the FS or whatever
else it decides is of little use at the time if the disk *doesnt*
support dma....
I dont see a safe default as "stupidity" at all especially when alot
could potentially be at stake ...
(ie potentially the contents the forementioned joe user would like to
keep and probably shifted to linux to try and retain)
Whats the point in shifting to the "stable" alternative if it "stupidly"
defaults to a potentially unstable implementation.
Dale.
