From owner-freebsd-hackers Thu Apr 27 13:23: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id AA5F737C0D6 for ; Thu, 27 Apr 2000 13:23:03 -0700 (PDT) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id QAA03763; Thu, 27 Apr 2000 16:22:57 -0400 (EDT) To: "Jordan K. Hubbard" Cc: hackers@FreeBSD.ORG Subject: Re: 4.0-RELEASE ASUS K7V floppy boot fails -- register dump References: <749.956862134@localhost> From: Chris Shenton Date: 27 Apr 2000 16:22:57 -0400 In-Reply-To: "Jordan K. Hubbard"'s message of "Thu, 27 Apr 2000 12:02:14 -0700" Message-ID: Lines: 22 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Apr 2000 12:02:14 -0700, "Jordan K. Hubbard" said: Jordan> Mount the kern floppy on another FreeBSD box and do some Jordan> surgery on it along the following lines: Jordan> mount /dev/fd0 /mnt Jordon> rm /mnt/boot.config Jordon> umount /mnt Jordan> That should keep the -P flag out of your boot line and ensure Jordan> that the keyboard is properly detected. I think our use of -P Jordan> was over-eager since there are motherboards which don't play Jordan> nice with it, like this one. Just tried it, and as expected it didn't do the "-P" thing this time. Unfortunately: no joy -- same exact register dump. :-( It doesn't seem to be the keyboard finding problem others have written about (with NumLock hack workarounds) since the scan found the keyboard originally (keyboard: yes). Other suggestions welcome. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message