| View previous topic :: View next topic |
| Author |
Message |
silex
n00b
Joined: 30 Dec 2002
Posts: 61
|
 Posted: Sun Mar 23, 2003 4:02 am Post subject: hda error message |
 |
|
I saw this in "dmesg"
| Quote: | hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError } |
Could anyone tell me what does this mean and how to fix it? Thanks! |
|
| Back to top |
|
 |
FormerSlacker
Guru
Joined: 11 Mar 2003
Posts: 340
Location: Toronto, ON. Canada
|
| Posted: Sun Mar 23, 2003 8:09 am Post subject: Re: hda error message |
|
|
| silex wrote: | I saw this in "dmesg"
| Quote: | hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError } |
Could anyone tell me what does this mean and how to fix it? Thanks! |
This is just a guess, but it may be a dma problem, try disabling dma: | Code: |
spitfire root # hdparm -d0 /dev/hda
/dev/hda:
setting using_dma to 0 (off)
using_dma = 0 (off)
|
Note that this will decrease your performance. |
|
| Back to top |
|
|
silex
n00b
Joined: 30 Dec 2002
Posts: 61
|
| Posted: Tue Mar 25, 2003 4:12 pm Post subject: |
|
|
Thanks. I enabled ultra ATA 100 by "hdparm ... -X69 /dev/hda" (Ultra DMA mode 5)
Maybe this is the problem? |
|
| Back to top |
|
|
FormerSlacker
Guru
Joined: 11 Mar 2003
Posts: 340
Location: Toronto, ON. Canada
|
| Posted: Tue Mar 25, 2003 9:41 pm Post subject: |
|
|
It could very well be. No two chipsets are created equal. Some have problems at some modes while others don't. I guess you could try starting out at ATA 33,66,100,133 to see which mode works best on your system.
On my system, KT266a, ATA 100 works fine. Too bad it doesn't support 133, oh well  |
|
| Back to top |
|
|
xiao
n00b
Joined: 10 Jan 2003
Posts: 18
|
| Posted: Tue Mar 25, 2003 11:24 pm Post subject: IDE cable |
|
|
The problem is the IDE cable that you use.
To avoid the problem, you may have to upgrade to a better UDMA IDE cable. |
|
| Back to top |
|
|
|
Kernel & Hardware
