From: "Zephaniah E\. Hull" <warp@mercury.d2dc.net>
To: Justin Mierta <Crazed_Cowboy@stones.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
hahn@physics.mcmaster.ca, lung@theuw.net,
linux-kernel@vger.kernel.org
Subject: Re: ECS k7s5a motherboard doesnt work
Date: Wed, 31 Oct 2001 03:30:18 -0500 [thread overview]
Message-ID: <20011031033018.A1917@babylon.d2dc.net> (raw)
In-Reply-To: <E15y9q4-0002ER-00@the-village.bc.nu> <3BDD7164.8080401@stones.com>
In-Reply-To: <3BDD7164.8080401@stones.com>
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
On Mon, Oct 29, 2001 at 10:10:28AM -0500, Justin Mierta wrote:
> well, i dont have a floppy drive, so that test is a little difficult to
> do, but i threw some ram in there that i have used in linux before, and
> i still had the slew of ide error messages. and this harddrive has
> worked in linux before. i'm getting more and more convinced its an ide
> controller +linux issue.
>
> plus, i just discovered this:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0109.1/0198.html
>
> which really points to ide controller and linux not fighting nicely
> together, altho the thread doesnt really point towards a solution.
I'm using a K7S5A with recent 2.4.x kernels, and have no major
problems[0].
I don't remember why I have CONFIG_IDEDISK_MULTI_MODE on, but I do.
I also have CONFIG_IDEDMA_NEW_DRIVE_LISTINGS on, and obviously have
CONFIG_BLK_DEV_SIS5513 on.
Oh, and I have CONFIG_IDEDMA_IVB as well.
The only problems I have seen with this board are that I can't find
drivers for the sound (no big loss), lmsensors does not seem to be able
to properly read the sensors (annoying), repeated 'VFS: Disk change
detected on device ide1(22,0)' messages (my cdrom drive, getting a
little annoying), and, thats about it.
I have not seen any data corruption.
My obvious question is what kernels are you running, and are you
enabling CONFIG_BLK_DEV_SIS5513 or not?
Zephaniah E. Hull.
>
> justin
--
1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
"<green>From</yellow>"
"Wow. The green word From is no longer yellow. That's deep, man."
-- Marcus Meissner & Lars Balker Rasmussen in the Scary Devil Monastery
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-31 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E15y9q4-0002ER-00@the-village.bc.nu>
2001-10-29 15:10 ` ECS k7s5a motherboard doesnt work Justin Mierta
2001-10-29 19:30 ` Adrian Burgess
2001-10-29 19:33 ` lung
2001-10-31 8:30 ` Zephaniah E. Hull [this message]
2001-10-31 10:52 ` Alan Cox
2001-11-02 15:48 ` ECS k7s5a audio sound SiS 735 - 7012 John Fremlin
2001-11-02 16:16 ` Alan Cox
2001-11-02 16:00 ` John Fremlin
2001-11-02 21:20 ` Dan Hollis
2001-11-02 23:42 ` Alan Cox
[not found] <Pine.LNX.4.10.10110291523140.27909-100000@coffee.psychology.mcmaster.ca>
2001-10-29 20:53 ` ECS k7s5a motherboard doesnt work Justin Mierta
2001-11-02 14:03 ` Marco Colombo
2001-10-29 16:40 Daniel Freedman
[not found] <Pine.LNX.4.33.0110281907240.22555-100000@narboza.theuw.net>
2001-10-29 0:58 ` Justin Mierta
-- strict thread matches above, loose matches on Subject: below --
2001-10-28 23:18 Justin Mierta
2001-10-28 23:50 ` Alan Cox
2001-10-29 8:02 ` Justin Mierta
2001-10-29 17:42 ` Joel Jaeggli
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=20011031033018.A1917@babylon.d2dc.net \
--to=warp@mercury.d2dc.net \
--cc=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