<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Lincoln -<br>
<br>
Conceptually, what you say makes sense. Red Hat 9 works with the
BE7-RAID board so what would be different in Centos (Red Hat Enterprise
4) so that it will not work? Granted, the Kernel is different in RH
Enterprise from RH 9, but is it that different?<br>
<br>
These are areas where my lack of knowledge/experience puts me at a
disadvantage.<br>
<br>
On the Highpoint site, I here is this:<br>
<br>
<a class="moz-txt-link-freetext"
href="http://www.highpoint-tech.com/USA/bios_rr133.htm">http://www.highpoint-tech.com/USA/bios_rr133.htm</a><br>
<br>
Then I had this exchange some time ago where the proprietary drivers
are discussed, but I am not sure what to make of it.<br>
<br>
<a class="moz-txt-link-freetext" href="http://lists.centos.org/pipermail/centos/2005-September/052353.html">http://lists.centos.org/pipermail/centos/2005-September/052353.html</a><br>
<br>
Does this make sense to you?<br>
<br>
Todd<br>
<br>
<br>
<br>
Lincoln Peters wrote:
<blockquote cite="mid200611101944.11044.sampln@sbcglobal.net"
type="cite">
<pre wrap="">On Friday 10 November 2006 19:11, Todd Cary wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Greatly appreciate your interest/question. I have Centos 4 running on
an old box; not sure of the motherboard or CPU. But when I went to
upgrade my Red Hat 9 to Centos 4 or Fedora 5 (I believe it was 5) or the
Linux on a CD (Ubuntu), none will install.
Now it may be due to my lack of understanding about upgrading drivers
that I can't upgrade. My main goal is to have Centos 4 on the computer
due to the great performance on the other box (I have not had to touch
it :-) ) and to have them both as close as possible since they are
suppose to be "backups" to each other.
</pre>
</blockquote>
<pre wrap=""><!---->
If the new distro doesn't support the board, it's more likely that the drivers
were left out to save space. But the drivers should still be present in the
Linux kernel sources, so one option might be to build a custom kernel
(containing the necessary drivers) that you can use both for the install and
first boot, i.e. until you get the custom kernel installed on the hard disk.
This should work in principle, but I've never tried it myself.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="65">--
Ariste Software
2200 D Street Ext
Petaluma, CA 94952
(707) 773-4523
</pre>
</body>
</html>