View previous topic :: View next topic |
Author |
Message |
n0n Guru


Joined: 13 Jun 2002 Posts: 355
|
Posted: Wed Jun 18, 2003 2:19 pm Post subject: IDE Drive Slowdown in Vanilla 2.4.21, ext3 |
|
|
'ello, everyone
Upgraded to vanilla 2.4.21 a few days ago, and it seems that something rather debilitating has happened with my IDE drives. Drive access is extremely slow. I first noticed it when watching some videos and it was rather glitchy. Booting into 2.4.20 fixed the problem. Then later I tried copying files across partitions it was excruciatingly slow (did hdc3->hdc2 and hdc3->hdb4); 2.4.20 was every bit as fast as I had expected.
I'm assuming that perhaps DMA or something didn't get enabled properly, though I checked and I *did* compile support for it into 2.4.21. I'm planning on debugging this more tonight when I get home, but wanted to put a message out here to see if anyone else has run into this.
Thanks... |
|
Back to top |
|
 |
MacFlecknoe Apprentice

Joined: 11 Feb 2003 Posts: 189 Location: Ann Arbor, MI
|
Posted: Fri Jun 20, 2003 1:21 am Post subject: |
|
|
just to post my own problems... I have an nforce2 based motherboard and I can no longer turn on dma mode on my harddrives. hdparm returns
Code: | /dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
|
|
|
Back to top |
|
 |
MacFlecknoe Apprentice

Joined: 11 Feb 2003 Posts: 189 Location: Ann Arbor, MI
|
Posted: Fri Jun 20, 2003 6:13 am Post subject: |
|
|
i discovered the solution to my problem anyway. for nforce based motherboards you need to enable IDE support for Athlon Viper. 2.4.20 relied on the generic driver to provide DMA to these boards but that seems to have been deprecated... |
|
Back to top |
|
 |
n0n Guru


Joined: 13 Jun 2002 Posts: 355
|
Posted: Tue Jun 24, 2003 9:01 pm Post subject: |
|
|
MacFlecknoe wrote: | i discovered the solution to my problem anyway. for nforce based motherboards you need to enable IDE support for Athlon Viper. 2.4.20 relied on the generic driver to provide DMA to these boards but that seems to have been deprecated... |
Ah, now that I've finally gotten around to trying to figure this out, this is what happened to me, too... Needed to activate the VIA82CXXX driver in the kernel, which I didn't have to do before on 2.4.20. No matter. Thanks for your input... |
|
Back to top |
|
 |
|