At 18:30 17-12-04 +0000, Alberto Monteiro wrote: >Warren Ockrassa wrote: >> >>> I've just installed a new HD in my new computer. The first time >>> I booted, the computer didn't, because it seemed that there were >>> no HDs. >> >> If the BIOS sees it, your OS should as well. >> >No, it doesn't. Stupid OS :-/ > >> Have you checked the Linux HW compatibility lists? >> >No, but I guess it should. It's not a new model of HD. > >> Also, you mention jumpers -- do you have a main boot drive set up >> already? And is it jumped to run as the master? In my experience "cable >> select" options don't work very well. In such a case the other drive >> has to be configged as the slave. >> >Yikes! I don't want to do it!
Most of the hard drives I have installed or moved have it printed on the label on the drive itself which pins you have to put the jumper on to make it a master or a slave. Of course, to read that, you pretty well have to remove the drive from the case. But you might want to check to make sure that the primary (old?) HD is jumpered as "master" and the secondary (new?) one is jumpered as "slave." It really isn't that hard, except that a hemostat is a _very_ handy tool to have when you are attempting to remove/insert the jumpers (though of course be careful not to put so much pressure on the jumper that you crush it) . . . >> >>> PS: the sound seems to have broken too :-/ >> >> Oh dear. HW interrupts? >> >No, I didn't connect the _cable_ from the computer to the monitor. >I was too much paranoid :-/ I was going to suggest that you check to see if you might have accidentally pulled a cable loose while fooling with the hard drive. -- Ronn! :) _______________________________________________ http://www.mccmedia.com/mailman/listinfo/brin-l
