From: Daniel Freedman <freedman@ccmr.cornell.edu>
To: linux-kernel@vger.kernel.org, crazed_cowboy@stones.com
Cc: Daniel Freedman <freedman@ccmr.cornell.edu>
Subject: Re: ECS k7s5a motherboard doesnt work
Date: Mon, 29 Oct 2001 11:40:20 -0500 [thread overview]
Message-ID: <20011029114018.A29371@ccmr.cornell.edu> (raw)
Justin Mierta (Crazed_Cowboy@stones.com) wrote:
> and nowhere can i find the thread you mentioned.
>
> Also, this motherboard works *perfect* in windows (which is
> unfortunately where i've been stuck) -- it hasnt crashed in the last
> several weeks i've been using it! (probably the longest uptime i've ever
> seen for a windows machine that's actually being used) So I *seriously*
> doubt its bad hardware.
>
> Can you maybe give me a link to the thread you mention?
>
> Justin
>
Justin,
Hi! I've purchased three of these ECS K7S5A motherboards (based upon
Sis 735 chipsets) and have installed Linux (specifically Debian 2.2r3,
with 2.2.19 kernel) on all of them without any difficulty or hiccups.
This would tend to suggest, as Alan implied, that the board is not
incompatible (at least not wildly so, as you describe) and that you
may have hardware issues, even if Windows does run on this setup.
The main issue that I believe exists with this board, or actually with
the board's chipset (people, please correct me if I'm wrong), is that
the current 2.2.19 does not support the built-in ethernet capabilities
of the Sis 735. I've tried Sis's patch for the kernel from their
website, but that won't even compile. I'm planning to look into Alan's
2.2.20pre11 release that supposedly includes a Sis900 chipset update
(Sis seems to suggest that the 900 and 735 use the same drivers, at
least to some degree) and maybe this will work. In the meantime, I
just installed a NIC.
Hope this helps, Justin. I'd love to hear if anyone else knows about
the Sis735 ethernet issue.
Take care,
Daniel
PS Please CC me on replies.
--
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University
next reply other threads:[~2001-10-29 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 16:40 Daniel Freedman [this message]
[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
[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
[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=20011029114018.A29371@ccmr.cornell.edu \
--to=freedman@ccmr.cornell.edu \
--cc=crazed_cowboy@stones.com \
--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