From owner-freebsd-questions Thu Oct 7 6:34:27 1999 Delivered-To: freebsd-questions@freebsd.org Received: from xena.gsicomp.on.ca (gsi.enoreo.on.ca [209.82.52.145]) by hub.freebsd.org (Postfix) with ESMTP id 1C35A14D1B for ; Thu, 7 Oct 1999 06:34:24 -0700 (PDT) (envelope-from matt@xena.gsicomp.on.ca) Received: from localhost (matt@localhost) by xena.gsicomp.on.ca (8.9.2/8.9.2) with SMTP id JAA31755 for ; Thu, 7 Oct 1999 09:37:08 -0400 (EDT) (envelope-from matt@xena.gsicomp.on.ca) Date: Thu, 7 Oct 1999 09:37:08 -0400 (EDT) From: Matthew Emmerton To: freebsd-questions@freebsd.org Subject: Problems Upgrading 2.2.7 to 3.3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last night I tried to upgrade my 2.2.7 machine to the newly-released 3.3. When I installed, I get "no boot.conf found", and then "invalid format!" whenever I try and boot one of the kernel[.GENERIC] images. I had the same problem when trying to do an upgrade to 3.2 a while back. I chose to revert back to 2.2.7. However, the situation has now changed and I can't run an a.out development box anymore. I installed 3.[23] via the CD-ROMS and floppies (created from CD-ROM), so according to the messages in the mailing list archives, I shouldn't run into this error, as the bootblocks from the floppies can boot ELF kernels properly. Is it possible that the boot loader / boot sector from my 2.2.7 install is not being overwritten properly, and then upon reboot, it can't figure out how to load an ELF kernel? Please phone, fax, or e-mail. I don't have newsgroup access. -- Matthew Emmerton || matt@gsicomp.on.ca GSI Computer Services || P: +1 (800) 217-5409 Technical Director || F: +1 (519) 335-6584 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message