From owner-freebsd-hackers Thu Aug 10 21:57:24 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id VAA06816 for hackers-outgoing; Thu, 10 Aug 1995 21:57:24 -0700 Received: from netcom10.netcom.com (netcom10.netcom.com [192.100.81.120]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id VAA06803 for ; Thu, 10 Aug 1995 21:57:17 -0700 Received: from [192.0.2.1] by netcom10.netcom.com (8.6.12/Netcom) id VAA24227; Thu, 10 Aug 1995 21:54:49 -0700 X-Sender: shamrock@localhost Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 10 Aug 1995 22:00:42 -0800 To: freebsd-hackers@freebsd.org From: shamrock@netcom.com (Lucky Green) Subject: Bizzare floppy boot problems. Hardware hacker needed. Sender: hackers-owner@freebsd.org Precedence: bulk My 486-DX2, AMI BIOS, Adaptec 1542 SCSI card, SCSI HD only, started to show the following problem: Won't boot from a newly created DOS boot floppy using soft reboot. Will boot from new boot floppy using hard reboot. Will boot from floppy with soft reboot if I didn't just created it. I.e. in subsequent reboots after a hard reboot. The boot sequence gets until the "484-DX2" prompt and just sits there. No complaint about it not being a system disk, just hangs. If I use a FreeBSD boot disk, the behaviour is even more bizzare: It will access the FD *and then go straight to booting from the HD*. No "non-system disk" message, just boots as if there wasn't even a floppy in a:! The boot order is correct, I switched control of the FDs from the SCSI adaptor to the multi I/O card, even removing the I/O card, same problem. I tried different boot disks. I set the most conservative BIOS setting I can think of. I am at the end of my rope. Could it be a defective BIOS? What should I do next? TIA, -- Lucky Green PGP encrypted mail preferred.