From owner-freebsd-small Mon May 3 14: 0:17 1999 Delivered-To: freebsd-small@freebsd.org Received: from beowulf.utmb.edu (beowulf.utmb.edu [129.109.59.83]) by hub.freebsd.org (Postfix) with ESMTP id 832AF14EE9 for ; Mon, 3 May 1999 14:00:08 -0700 (PDT) (envelope-from bdodson@beowulf.utmb.edu) Received: (from bdodson@localhost) by beowulf.utmb.edu (8.9.2/8.9.2) id PAA00419; Mon, 3 May 1999 15:58:04 -0500 (CDT) (envelope-from bdodson) Date: Mon, 3 May 1999 15:58:04 -0500 (CDT) Message-Id: <199905032058.PAA00419@beowulf.utmb.edu> From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrzej Bialecki Cc: Hoss Firooznia , freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > On Mon, 3 May 1999, Hoss Firooznia wrote: > > > Hi folks, > > > > > > Loading kernel. Please wait... > > /kernel text=0xc379c > > elf_loadexec: archsw.readin failed > > can't load 'kernel' > > Error booting > > > > This happens with both a modified 'net' configuration as well as with the > > stock 'router' configuration. The boot blocks and boot loader seem to work > > as usual (I get the usual loader messages, the BootFORTH menu, etc.) but > > the boot loader apparently can't read in the kernel properly. > > > > I've tried multiple machines and multiple disks, but the problem remains - > > so presumably this isn't simply a hardware read error. Does the problem > > sound familiar to anyone? Am I (most likely) missing something obvious? > > Well, it looks familiar to me - more or less it means "I can't read this > sector from the media, help!", and I usually was able to get rid of it > with a new floppy... but in your case, if you already tried it, well... > > Andrzej Bialecki Hmmmm.... I get that message when multibooting regular FreeBSD (3.1-stable kernel, but 3.1-release bootblocks) and NT, using the NT boot loader to load our /boot/loader sequence. Works fine when /boot.config contains 1:da(0,a)/kernel so there is nothing wrong with the kernel. I suspect a mismatch somewhere between the 3.1-release boot stuff (specifically, /boot/loader) and the 3.1-stable kernel, but I haven't gotten around to a make world and installation of new bootblocks. You might try cvsupping the 3.1-stable boot hierarchy, and using the new boot blocks on the floppy. (Although I don't know what that would do to your regular system disk.) A full make world might work better. There are hints of this kind of problem in the stable mailing list archives, I think. Bud Dodson > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message