Date: Tue, 4 May 1999 15:28:58 -0500 (CDT) From: "M. L. Dodson" <bdodson@beowulf.utmb.edu> To: Andrzej Bialecki <abial@webgiro.com> Cc: "M. L. Dodson" <bdodson@beowulf.utmb.edu>, Hoss Firooznia <hfir@math.rochester.edu>, freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel Message-ID: <199905042028.PAA00309@beowulf.utmb.edu> In-Reply-To: <Pine.BSF.4.05.9905032310010.70808-100000@freja.webgiro.com> References: <199905032058.PAA00419@beowulf.utmb.edu> <Pine.BSF.4.05.9905032310010.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, M. L. Dodson wrote: > > > 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 > > Hmm... Could be also some problem with geometry perhaps.. it's a wild > guess, but who knows.. you usually don't have problems with figuring out > the geometry of a floppy, whereas with HDDs it's a different > story. A make world and reboot solved my multiboot problems. So, Hoss, if you have the situation I had: a 3.1-RELEASE boot chain, but your /usr/src tree was -STABLE, you might suspect the same problem I had. I know that the problem that I had was also reproduced using a dedicated boot floppy with 3.1-RELEASE boot chain and 3.1-STABLE kernel.gz, so I don't think is was (directly, in any case) specific to a hard disk geometry problem. Good luck. Bud Dodson > > Andrzej Bialecki > > // <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/ ---- > -- 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?199905042028.PAA00309>