Re: New install won't boot off A7V133

2002-12-03 Thread Scott I. Remick
In article ashllk$28g0$[EMAIL PROTECTED], you say...
 On Mon, Dec 02, 2002 at 08:19:36PM -0800, Scott I. Remick wrote:
  I just got in an ATA133 30GB drive that I am going to dedicat to FreeBSD
on
  my main system (an Asus A7V133). I took off the existing 20GB (Win2000),
put
  the 30GB in its place (primary master). I boot from a 4.7-REL CD I made,
  install goes fine... it detects the controllers, drive, I partition the
  whole thing for FreeBSD, setting the auto defaults, etc etc.  Everything
  goes swell.  Then I'm done, I reboot, take out the CD... and it just
sits
  there when it should be booting from the drive.
  
 I can't tell you the solution, but by pure chance I too have been
 fiddling with installs on a A7V133 system with a 30GB drive. I am
 convinced there is a bug in the BIOS because it doesn't honour the boot
 order you set in the BIOS sometimes. I did a quick experiemental install
 of 5.0 just to see. It all went fine, and did indeed boot. However it
 then refused to boot anything other than the HD, Despite the boot order
 being FD, CD, HD. I got around this by rather drastic means,,,but if it
 happens again I shall be..mmm..pissed off :)
 
 Although this is not what you are seeing, it is a bit of a co-incidence.

Cliff,

Just to confirm: you get beyond the POST, to the hardware info screen, where
you should normally start seeing the boot process, correct? Mine just sits
there at that point.

A few things I haven't done yet that I intend on are installing MS-DOS to
the drive, as well as using a different drive, in order to determine whether
it is FreeBSD or the specific hard drive.

What brand drive is yours, out of curiosity? Mine is an IBM DeskStar.

What BIOS version are you using? I know there's a 1010 beta out for this
board, but I'm hesitant to try it until I've done some other things (as I
use this computer for Win2K also).

It is interesting that 5.0 boots for you... if it were truly a problem with
the A7V133's BIOS I'd expect 5.0 to not boot also.

Anyhow, I will be troubleshooting this some more tonight. Maybe others will
pipe in throughout the course of today with more ideas.

=
Scott I. Remick   --==--   ICQ: 450152 
Save the internet - Use Mozilla: http://home.adelphia.net/~sremick/mozilla/
Voici mon secret. Il est tres simple: on ne voit bien qu'avec le coeur. L'essentiel 
est invisible pour les yeux.
No trees were harmed in the composition of this message, although some
electrons were mildly inconvenienced.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: New install won't boot off A7V133

2002-12-02 Thread Cliff Sarginson
On Mon, Dec 02, 2002 at 08:19:36PM -0800, Scott I. Remick wrote:
 I just got in an ATA133 30GB drive that I am going to dedicat to FreeBSD on
 my main system (an Asus A7V133). I took off the existing 20GB (Win2000), put
 the 30GB in its place (primary master). I boot from a 4.7-REL CD I made,
 install goes fine... it detects the controllers, drive, I partition the
 whole thing for FreeBSD, setting the auto defaults, etc etc.  Everything
 goes swell.  Then I'm done, I reboot, take out the CD... and it just sits
 there when it should be booting from the drive.
 
I can't tell you the solution, but by pure chance I too have been
fiddling with installs on a A7V133 system with a 30GB drive. I am
convinced there is a bug in the BIOS because it doesn't honour the boot
order you set in the BIOS sometimes. I did a quick experiemental install
of 5.0 just to see. It all went fine, and did indeed boot. However it
then refused to boot anything other than the HD, Despite the boot order
being FD, CD, HD. I got around this by rather drastic means,,,but if it
happens again I shall be..mmm..pissed off :)

Although this is not what you are seeing, it is a bit of a co-incidence.

-- 
Regards
   Cliff Sarginson 
   The Netherlands

[ This mail has been checked as virus-free ]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message