Mip
03-04-2001, 04:08 AM
Hey Gang,
I just built a new system for my brother in law. It's the first time I've done this, and was frankly more surprised that it all seemed to come together than I would have been had smoke started coming out the back.
Here are the relevant parts:
AMD T-bird 1 GHz
1 256 mem stick
Abit KT7A Raid
IBM 45 GB 7200 rpm HD
Aopen 52x CD drive
The problem is that the machine would run the BIOS (Award), but then wouldn't search the HDD or FDD during boot. It would boot from CD, so I was able to load Linux on it (Mandrake 7.2), but it never made the HDD or FDD lights even blink upon several restarts.
The BIOS was able to recognize the HDD correctly (size and brand), as well as the FDD, so I figure that they must be connected properly (although I wasn't sure that I had the cable correctly attached to the FDD, as there was no documentation that came with it (Mitsumi), nor was there any on their website about which was Pin1).
I changed two things on the BIOS in my trouble shooting, and now it powers up, but doesn't send any info on BIOS to the screen:
1 I switched the boot order to boot HD1 rather than HD0, thinking that perhaps this was the problem (the drive is on IDE1). I now think that HD0 must be the first primary IDE HDD.
2 THere was a place on the advanced CMOS settings where one could bypass the motherboard testing. It looked to me like it was set up to bypass, so I changed that. I now think that I must have misunderstood the wording, as it now won't even let me hit DEL to enter setup.
I think the only thing I can do is to pull the 5V battery, and switch the jumpers for a few seconds to erase the BIOS settings, and start from scratch. I'll do this tomorrow morning.
Any ideas as to why it wouldn't look to my FDD and HDD during boot (prior to my messing with it)?
The manual did say to erase the CMOS settings when installing a new CPU - but I didn't do this, figuring that everything was new, and so would already be set to factory defaults. Interestingly, the clockspeed on the CPU when I first powered up said 600 - so maybe the board has had another processor in it previously. If that's the case, then perhaps resetting the CMOS will take care of things.
Any ideas would be much appreciated.
M
I just built a new system for my brother in law. It's the first time I've done this, and was frankly more surprised that it all seemed to come together than I would have been had smoke started coming out the back.
Here are the relevant parts:
AMD T-bird 1 GHz
1 256 mem stick
Abit KT7A Raid
IBM 45 GB 7200 rpm HD
Aopen 52x CD drive
The problem is that the machine would run the BIOS (Award), but then wouldn't search the HDD or FDD during boot. It would boot from CD, so I was able to load Linux on it (Mandrake 7.2), but it never made the HDD or FDD lights even blink upon several restarts.
The BIOS was able to recognize the HDD correctly (size and brand), as well as the FDD, so I figure that they must be connected properly (although I wasn't sure that I had the cable correctly attached to the FDD, as there was no documentation that came with it (Mitsumi), nor was there any on their website about which was Pin1).
I changed two things on the BIOS in my trouble shooting, and now it powers up, but doesn't send any info on BIOS to the screen:
1 I switched the boot order to boot HD1 rather than HD0, thinking that perhaps this was the problem (the drive is on IDE1). I now think that HD0 must be the first primary IDE HDD.
2 THere was a place on the advanced CMOS settings where one could bypass the motherboard testing. It looked to me like it was set up to bypass, so I changed that. I now think that I must have misunderstood the wording, as it now won't even let me hit DEL to enter setup.
I think the only thing I can do is to pull the 5V battery, and switch the jumpers for a few seconds to erase the BIOS settings, and start from scratch. I'll do this tomorrow morning.
Any ideas as to why it wouldn't look to my FDD and HDD during boot (prior to my messing with it)?
The manual did say to erase the CMOS settings when installing a new CPU - but I didn't do this, figuring that everything was new, and so would already be set to factory defaults. Interestingly, the clockspeed on the CPU when I first powered up said 600 - so maybe the board has had another processor in it previously. If that's the case, then perhaps resetting the CMOS will take care of things.
Any ideas would be much appreciated.
M