From owner-freebsd-questions Thu Dec 16 10:42:19 1999 Delivered-To: freebsd-questions@freebsd.org Received: from urquell.pilsnet.sunet.se (urquell.pilsnet.sunet.se [192.36.125.77]) by hub.freebsd.org (Postfix) with ESMTP id AAD4814EB6 for ; Thu, 16 Dec 1999 10:42:16 -0800 (PST) (envelope-from bd@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id TAA26327; Thu, 16 Dec 1999 19:42:08 +0100 (CET) (envelope-from bd) To: Roxanne Parent Cc: FreeBSD-questions@FreeBSD.ORG Subject: Re: 3.2 install problems References: From: Bjorn Danielsson Date: 16 Dec 1999 19:42:07 +0100 In-Reply-To: Roxanne Parent's message of "Thu, 16 Dec 1999 11:26:25 -0500 (EST)" Message-ID: Lines: 26 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roxanne Parent wrote: > I have an IBM Aptiva E26 wit ATAPI EIDE cdrom. > > I can not seem to be able to use the cdrom to boot. I don't have any clue about that, but please read on. > I have also had no luck with the floppies!?! What happened when you tried the floppies? I tried the 3.3 floppies on an old machine that doesn't have a CDROM, and got the error "Can't find /mfsroot" after switching to the second floppy. If the exact same thing happened to you, maybe my solution will work: I made a copy of the first floppy (kern.flp), mounted it, and in the file /boot/loader.rc I inserted the line "set currdev=disk0:" just before the line "load -t mfs_root /mfsroot". After this change it booted without problems. I still really don't know *why* this was needed, it was pure trial and error on my part actually. But I'd guess that there is some problem with the naming conventions for the floppy file system. -- Björn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message