why the Fedora4 cannot be installed to SATA harddisk?
 

i downloaded the Fedora 4 from internet this morning and try to install it to my new desktop with 3.0 MHZ, 512 RAM and 80G SATA hard disk. i failed to install it,probaly is the fedora core 4 not able to detect the hard disk, am i right? could any expert help me on this? please guide me how to install it. i had a copy of window XP profesional installed in the hard disk. thanks

It sounds like FC4 is not detecting your SATA controller. I would expect this is a MOBO controller and not a seperate card? We need to know the name of the motherboard, and any info you have about the board. You could also try live distros, and see if any recognize the board/SATA correctly.

You could also search here and google for "install linux sata", and get much info. If you drop the model of your motherboard in there, you'll get guaranteed good results.

Peace,
JimBass

my mother board is Intel 915GEV which support dual channel Ram. hope you might help me on this.

The solution to your problem was in my last post. Use the search here, and at google, or even better, http://www.google.com/linux. The you put in your MOBO info, along with SATA, and see what comes up:

putting in Intel 915GEV sata lead me to several good sites, including some right here on http://linuxquestions.org Among the best I found:

http://www.groupsrv.com/linux/about46764.html
https://www.redhat.com/archives/fedo.../msg02445.html

Helping people understand linux is what this site is for, and seems to do a fine job of that. I can understand/remember being a brand newbie, and not knowing anything about commands and how to install software. The problem here isn't any of that. If you had done what I said, used google and the search here (through any computer, doesn't have to be a linux one), you would have found your answer.

You also could have helped yourself if you gave us some kind of an idea what the installer was saying. Some of the threads speak about an error message of not being able to locate disks, others a kernel panic. Both are also solved in the links I gave above, which you could have found for yourself with about 20 seconds of effort/work if you even consider it that.

Peace,
JimBass