Date: Fri, 21 Jun 1996 12:16:09 +0100 From: "Gary Palmer" <gpalmer@FreeBSD.ORG> To: "J." <jst@ccnext.ucsf.edu> Cc: bugs@FreeBSD.ORG Subject: Re: Boot bugs, bug reporting. Message-ID: <10528.835355769@palmer.demon.co.uk> In-Reply-To: Your message of "Fri, 21 Jun 1996 03:29:25 PDT." <9606211029.AA17017@ccnext.ucsf.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
"J." wrote in message ID <9606211029.AA17017@ccnext.ucsf.edu>: > 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. The only (real) difference is that the bug can't be tracked if you e-mail to bugs as it doesn't get recorded in our tracking database (GNATS). > 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. There is, but it (really) requires to be filled out and submitted electronically. Hence we only accept send-pr submitssions for our bug tracking database (they need to be in a specific layout for the code to handle them and properly categorise them). If you feel that Walnut Creek CDROM should prove an paper-based service for customers (we (the FreeBSD project) do not have the resources to undertake this), you should probably raise this issue with them, since they are responsible for the CDROM's and (probably) have the resources. > The problems: > 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). Weird. > 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) Weirder. There were no changes between 2.0.5 and 2.1 for the fbsdboot.exe program that I can find. The same version of the code should have been in 2.0.5 and 2.1. Have you tried booting WITHOUT any memory managers loaded? That MAY stand a better chance of success. If you are trying to install, I would also recommend trying the boot floppy install method. The fbsdboot.exe program is a nice idea, but due to differences between memory managers, it doesn't ALWAYS get it right. That's why we supply methods for trying floppies too... > 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. This is a known problem (the dosfs code is VERY weak), and a complete re-write is in progress. Sorry for any troubles. > Could not make the VGA Ioctl's work (trying to set 50 line mode). Does > there need to be a different video driver? You need to load an appropriate font for the screen resolution you are trying to use. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10528.835355769>