From owner-freebsd-bugs Fri Jun 21 03:33:12 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA06746 for bugs-outgoing; Fri, 21 Jun 1996 03:33:12 -0700 (PDT) Received: from cgl.ucsf.EDU (cgl.ucsf.EDU [128.218.27.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA06741 for ; Fri, 21 Jun 1996 03:33:11 -0700 (PDT) Received: from ccnext.ucsf.edu (ccnext.ucsf.EDU [128.218.80.24]) by cgl.ucsf.EDU (8.6.12/GSC4.25) with SMTP id DAA03145 for ; Fri, 21 Jun 1996 03:33:05 -0700 Received: by ccnext.ucsf.edu (NX5.67d/NeXT-1.0) id AA17017; Fri, 21 Jun 96 03:29:25 -0700 Date: Fri, 21 Jun 96 03:29:25 -0700 From: jst@ccnext.ucsf.EDU (J.) Message-Id: <9606211029.AA17017@ccnext.ucsf.edu> To: bugs@freebsd.org Subject: Boot bugs, bug reporting. Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The "developers resources" document on freebsd.org is ambiguous as to whether mailing to bugs@frebsd.org constitutes an official bug report or not. As I cannot install FreeBSD, I cannot run send-pr to generate an official report. If there is an official "form", I wish it were placed on the front of the cdroms, with a mailing address to send it to. The problems: The boot-from-dos worked for a machine that Jordan specified, when it was used with an external SCSI CDROM drive, using version 2.0.5 32M, Adaptec 2940 SCSI card, at that time, a Matrox display card. Now that it has an ATAPI CDROM, primary device on the secondary IDE port as Linux requires, the fbsdboot procedure hangs, after printing a line and a half of addresses. (now has a #9 Imagine 128 display card). I'm booting from CDROM. I've tried 2.1, it hangs (which reports the existence of DPMI memory that I don't believe is installed in DOS without Windows running, and I don't have the DPMI driver from DJGPP running). I've tried 2.0.5, it hangs (It reports VCPI memory, which I believe exists in the DOS6.22 himem.sys) ---- Mounting a DOS partition R/W and writing to it, was coincident with many files being removed by FSCK on the next reboot, on several occasions. This was a while ago, and I think there were panics, as well. Could not make the VGA Ioctl's work (trying to set 50 line mode). Does there need to be a different video driver? J.