Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Fri, Jun 23, 2006 at 07:01:51PM -0400, John Abreau wrote: > Replacing the cable didn't help; it's still giving the error. > > I found a message through google where someone says the error indicates > that DMA got disabled. > > http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-11/0679.html > > hdparm -I showed > > DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 > Cycle time: min=120ns recommended=120ns > > I tried > > sudo hdparm -d1 -X udma5 /dev/hda > > to see what would happen; there was no change, the error still happens > every 30 seconds. Output was as follows: > > sudo hdparm -d1 -X udma5 /dev/hda > > /dev/hda: > setting using_dma to 1 (on) > HDIO_SET_DMA failed: Operation not permitted > setting xfermode to 69 (UltraDMA mode5) > using_dma = 0 (off) OK; disk access must be horribly slow too, right? Try doing a 'find /' or something - does it take forever? Wait - didn't you say that you had a SATA controller? Your drives are being recognized as /dev/hda rather than /dev/sda, so it must be set to PATA emulation in the BIOS then? That could be the reason why you can't set DMA. Alteratively, you don't have the proper driver for your SATA controller loaded, that's why you can't enable DMA. Maybe you need a more recent kernel (2.6.9 is not exactly state of the art), or maybe you need to load a module. Ward. -- Pong.be -( "Just wait, My crystal ball is infallible." -- Linus )- Virtual hosting -( Torvalds, discussing the future of smart I/O hardware. )- http://pong.be -( )- GnuPG public key: http://gpg.dtype.org
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |