BIOS problem

On Sat, 12 Mar 2005 10:42:07 +1100, Bob Bob <bcnntp RemoveThis @optusnet.com.au>
wrote:

>Hi Colin
>
>In my experience the most common fault for non detection (apart from a
>h/w fault) is that the BIOS is a little old and needs to be reflashed to
>a later version. Do a search on your m/b and see if your version is not
>so current on their support site.

This sounds right. The processor is at least 5 years old - a 550MHz
Athlon, the cutting edge of its day.

I've never flashed a BIOS chip before it might be an interesting
experience. I am considering a new mobo and processor. I've already
had to replace the video card.

The reason that I suspected the Linux installation is that I have an
irritating problem on bootup which I am certain is down to Linux.
It's soemthing I started to get to grips with but then got very busy
and had to leave it until another time. The computer halts during
bootup saying that it's pointing at the CD for a boot disk. The BIOS
tells it to look at the floppy first. A warm boot sorts it until the
next boot up. I'll get round to it one day.

Many thanks

Linux still works very well. I'm glad of it. It's only for a hobby.

Colin


>
>You can also have problems where one drive will "fight" another even
>though they are configured properly. Doesnt happen often but it does
>happen. The way to prove this is to disconnect your primary master and
>see if it detects the other drive next boot.
>
>To a degree Linux doesnt care about the BIOS settings as it searches for
>all devices again on startup. I doubt the SuSE install had anything to
>do with it. Unless of course it changed the disk to some weird geometry
>that the BIOS gets confused over. You can always read off the geometry
>from dmesg and then input those numbers manually into the BIOS if you like.
>
>Hope this helps.
>
>Cheers Bob
>
>
>me@privacy.net wrote:
>> Hi
>>
>> apologies for this not being strictly a linux problem, but I think it
>> stems from the installation of Linux SUSE 9.2.