mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: aeleblanc@olgc.on.ca
To: linux-kernel@vger.kernel.org
Subject: UDMA Troubles and Possible Physical Damage?!
Date: Sun, 12 May 2002 17:27:20 -0400	[thread overview]
Message-ID: <OF3BBACEBD.3823AB14-ON85256BB7.0074FF80@LocalDomain> (raw)

First off, sorry if this message looks messed up, work forces us to use 
Lotus Notes (Bah!)
and second off heres the system that causing me greif:

Duron 1GHz on an ACS Mobo with SiS Chipset. 100MHz FSB & 384 MB PC133 
SDRAM.
and a Fujitsu 30MB ATA100 Drive


I Just finished installing Debian - Woody, which installs Kernel Version 
2.2.17 I Believe (I may be wrong there)

I installed and ran hdparm and after telling me that dma and all that 
other good stuff was disabled it said "HDIO: Failed to check BUSSTATE"

i ran hdparm -c3 -d1 -X34 to try and get DMA Working... the command ran 
fine but as soon as I tried to run another command (just 'ls' in fact) the 
system Locked up Solid.  upon rebooting my Bios didn't even Pick up the 
Hard drive.. I did a Hard reset again and the Bios picked it up, then 
reset again and it failed to pick it up again.. is it possible that I 
Screwed up my motherboard or Hard drive somehow?

the on a side note, before attempting to use hdparm under the above 
mentioned kernel, I compiled a custom 2.4.18 kernel, however it caused 
even more problems with ide, a bunch of:

hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }

Flew by then it said ide0: reset: success, then locked up again.

if anyone can help it would be greatly appreciated.


             reply	other threads:[~2002-05-12 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12 21:27 aeleblanc [this message]
2002-05-12 22:06 ` Barry K. Nathan
2002-05-12 22:04 aeleblanc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OF3BBACEBD.3823AB14-ON85256BB7.0074FF80@LocalDomain \
    --to=aeleblanc@olgc.on.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®