Date: Mon, 3 May 1999 15:58:04 -0500 (CDT) From: "M. L. Dodson" <bdodson@beowulf.utmb.edu> To: Andrzej Bialecki <abial@webgiro.com> Cc: Hoss Firooznia <hfir@math.rochester.edu>, freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel Message-ID: <199905032058.PAA00419@beowulf.utmb.edu> In-Reply-To: <Pine.BSF.4.05.9905032244520.70808-100000@freja.webgiro.com> References: <Pine.BSF.4.05.9905031352110.26816-100000@hecke.math.rochester.edu> <Pine.BSF.4.05.9905032244520.70808-100000@freja.webgiro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > > // <abial@webgiro.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905032058.PAA00419>