From: Justin Mierta <Crazed_Cowboy@stones.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org, hahn@physics.mcmaster.ca,
alan@lxorguk.ukuu.org.uk, lung@theuw.net
Subject: Re: ECS k7s5a motherboard doesnt work
Date: Mon, 29 Oct 2001 03:02:22 -0500 [thread overview]
Message-ID: <3BDD0D0E.6000609@stones.com> (raw)
In-Reply-To: <E15xzhf-0000tl-00@the-village.bc.nu>
here's some more info for everyone trying to help:
redhat says (at some point) that it insmod'd sis900, not the sis5513
that mark had suggested, and the sis735 that everything says is actually
in the motherboard. (i have to assume the sis900 was ide, because it
didnt tell me anything more useful than "insmod sis900" and that it worked)
however, the messages i'm seeing are something like this:
hda atapi: reset complete
irq timeout: complete status = 0xC0 { busy } (sometimes thats 0xD0)
then there's a few lines every now and then saying "drive not ready for
command" and "I/O error"
any suggestions?
justin
next prev parent reply other threads:[~2001-10-29 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 23:18 ECS k7s5a motherboard doesnt work Justin Mierta
2001-10-28 23:50 ` Alan Cox
2001-10-29 8:02 ` Justin Mierta [this message]
2001-10-29 17:42 ` Joel Jaeggli
[not found] <Pine.LNX.4.33.0110281907240.22555-100000@narboza.theuw.net>
2001-10-29 0:58 ` Justin Mierta
[not found] <E15y9q4-0002ER-00@the-village.bc.nu>
2001-10-29 15:10 ` Justin Mierta
2001-10-29 19:30 ` Adrian Burgess
2001-10-29 19:33 ` lung
2001-10-31 8:30 ` Zephaniah E. Hull
2001-10-31 10:52 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 16:40 Daniel Freedman
[not found] <Pine.LNX.4.10.10110291523140.27909-100000@coffee.psychology.mcmaster.ca>
2001-10-29 20:53 ` Justin Mierta
2001-11-02 14:03 ` Marco Colombo
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=3BDD0D0E.6000609@stones.com \
--to=crazed_cowboy@stones.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lung@theuw.net \
/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