From azrael@borris.toztech.com Sun Feb 3 01:19:48 2002 Return-Path: Received: from borris.toztech.com (d150-234-40.home.cgocable.net [24.150.234.40]) by hub.freebsd.org (Postfix) with ESMTP id 9A05F37B417 for ; Sun, 3 Feb 2002 01:19:47 -0800 (PST) Received: (from root@localhost) by borris.toztech.com (8.11.1/8.11.1) id g138XAl01049; Sun, 3 Feb 2002 03:33:10 -0500 (EST) (envelope-from azrael) Message-Id: <200202030833.g138XAl01049@borris.toztech.com> Date: Sun, 3 Feb 2002 03:33:10 -0500 (EST) From: stompkins.mofo-x@efnet.FreeBSD.ORG Reply-To: admin@toztech.com To: FreeBSD-gnats-submit@freebsd.org Subject: cannot load freebsd X-Send-Pr-Version: 3.2 >Number: 34576 >Category: i386 >Synopsis: cannot load freebsd >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 03 01:20:02 PST 2002 >Closed-Date: Fri Aug 09 09:47:25 PDT 2002 >Last-Modified: Fri Aug 09 09:47:25 PDT 2002 >Originator: Borris Administration >Release: FreeBSD 4.5-RELEASE i386 >Organization: toztech internet services >Environment: >Description: FreeBSD v4.5 Attempting Freshload i386 model on P3-733 w384 MB RAM Attempting to load during the CD Kernel boot, setup locks directly after detecting Parrallel/Serial devices, if i reboot machine and modify kernel before setup and remove everything (ie serial) it will lock at parallel or just keep going back a step, I ahve succesfully loaded numerous machines with my cds following same procedure, this is a really rare occurance seeing as I have already in the past, and still presently have freebsd running on this machine >How-To-Repeat: According to my knowledge I have no way to make you repeat this, I know not what comes after detecting the parrallel/serial devices, have never encountered this error before. >Fix: >Release-Note: >Audit-Trail: From: Hiten Pandya To: freebsd-gnats-submit@FreeBSD.org, admin@toztech.com Cc: Subject: Re: i386/34576: cannot load freebsd Date: Sun, 17 Feb 2002 11:49:04 +0000 Have you checked you BIOS/CMOS Settings. It would be also good, if you put PNP/OS in BIOS to a false value; as this was always causing a problem. I had this problem too, but it was solved by disabling this option (PNP/OS). Also, try poking around with you BIOS settings, as this will get your system to boot into FreeBSD. Most of the times, when the probe fails, that means it either something to do with you hardware, or with the clever BIOS! :) Regards, -- - Hiten Pandya - State-Changed-From-To: open->feedback State-Changed-By: johan State-Changed-When: Mon Apr 22 17:59:02 PDT 2002 State-Changed-Why: Where you able to get FreeBSD to boot on your machine after changing the BIOS setting for PNP? http://www.freebsd.org/cgi/query-pr.cgi?pr=34576 State-Changed-From-To: feedback->closed State-Changed-By: schweikh State-Changed-When: Fri Aug 9 09:45:59 PDT 2002 State-Changed-Why: Feedback timeout. If this is still an issue you might have more luck asking questions@ if you describe your HW. Someone might have a similar configuration. http://www.freebsd.org/cgi/query-pr.cgi?pr=34576 >Unformatted: