From owner-freebsd-questions Wed Apr 4 18:29:42 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nameserver.austclear.com.au (nameserver.austclear.com.au [192.83.119.132]) by hub.freebsd.org (Postfix) with ESMTP id E780A37B422 for ; Wed, 4 Apr 2001 18:29:34 -0700 (PDT) (envelope-from ahl@austclear.com.au) Received: from tungsten.austclear.com.au (tungsten.austclear.com.au [192.168.70.1]) by nameserver.austclear.com.au (8.9.3/8.9.3) with ESMTP id LAA98350; Thu, 5 Apr 2001 11:29:31 +1000 (EST) Received: from tungsten (tungsten [192.168.70.1]) by tungsten.austclear.com.au (8.9.3/8.9.3) with ESMTP id LAA16171; Thu, 5 Apr 2001 11:29:31 +1000 (EST) Message-Id: <200104050129.LAA16171@tungsten.austclear.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Yeck Cc: Mark Woodson , freebsd-questions@FreeBSD.ORG Subject: Re: Vectra XU 6/xxx In-Reply-To: Message from Mark Yeck of "Wed, 04 Apr 2001 20:02:45 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Apr 2001 11:29:31 +1000 From: Tony Landells Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG y3k@gti.net said (in response to mwoodson@wloq.com): > I used to have a link to an article on dejanews that mentioned boot > problems with freebsd and vectra's. unfortunately, that link doesnt > work anymore and i dont remember what the fix was. It had something to > do with the bios not working with the bootloader. Wish I could help > more. I know others have had a similar problem and the answer is out > there somewhere. I wish I could offer something helpful, but I haven't seen this problem even though I've installed on two sets of Vectras... Of course, neither is the particular model in question here. I think last time I made the disks "dangerously dedicated" and this time I didn't. Both times I installed the FreeBSD boot manager, though if you do "dangerously dedicated" I think the standard boot manager should work as well. I did "tune" the BIOS a bit, but nothing that really affects booting... I remember having a similar problem on a Compaq many years ago with BSDI and it was the choice of boot manager, so you could try using "the other one" than the one you've tried so far (or have you tried both?). Tony -- Tony Landells Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message