I was going to see if the shot in the dark worked for him and then take him down the lspci, dmidecode, etc. path. At least that would tell us what he's dealing with. The point on RHEL was an aside really. Although, I wouldn't be surprised if RHEL did work on some server hardware where Fedora did not. Red Hat should be getting support for that hardware in upstream, but there may be some lag time there. On 5/2/06, Kostas Sfakiotakis <kostassf@xxxxxxxxxxxxxx> wrote:
Greetings Russel , Russell Harrison wrote: > Try booting fedora in rescue mode. At the first screen when you boot > the cd > type "rescue" and hit enter. This will boot a text based single user > mode > for you to look around. You should be able to see your drives there, and > you can get more information to give the list to help you out. Don't bet on that . Btw am afraid that the OP problem is not specifically release related ( for example Fedora Core has it , Redhat Enterprise Linux hasn't it .). The only time i have had a similar to the original poster problem was when i tried to use hard disk on a Promise Controller ( PDC20267) . You see in this case you must have an initrd file that loads the apropriate module , if not then nothing is going to happen no matter what . To that effect i would ask the OP if the hard disks in question are directly connected to the motherboard or through any kind of controller ( be it an old Promise one , a SATA one , a SCSI , or whatever ) ? Kostas -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
