Date: Thu, 12 Aug 2004 01:35:07 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, "Daniel C. Sobral" <dcs@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/common help.common src/sys/boot/forth loader.conf Message-ID: <20040811223507.GD96867@ip.net.ua> In-Reply-To: <20040810173617.GQ991@funkthat.com> References: <200408061506.i76F66sl018247@repoman.freebsd.org> <20040809124153.GN628@darkness.comp.waw.pl> <20040809173814.GG991@funkthat.com> <20040810103007.GB30151@darkness.comp.waw.pl> <20040810144135.GN991@funkthat.com> <20040810154715.GC19937@ip.net.ua> <20040810173617.GQ991@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--yudcn1FV7Hsu/q59
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Aug 10, 2004 at 10:36:17AM -0700, John-Mark Gurney wrote:
> Ruslan Ermilov wrote this message on Tue, Aug 10, 2004 at 18:47 +0300:
> > > Have you tried booting another kernel? I can't see how your machine
> > > could of booted /boot/kernel.old ever with kernel modules, if your
> > > machine is currently having troubles with loading kernel modules.
> > > (Since kernel.old would not have been added to module path, since it
> > > isn't being now, and the correct modules would never load.)
> > >=20
> > Do you get the correct module_path with beastie_disable=3D"YES" set in
> > /boot/loader.conf? (Sorry, but I cannot try it right now.)
>=20
> Yep, I do:
> # sysctl kern.module_path
> kern.module_path: /boot/kernel;/boot/modules
> # kldload pf
> # kldunload pf
> # grep beastie /boot/loader.conf
> beastie_disable=3D"YES"
> # uname -a
> FreeBSD carbon.funkthat.com 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Sun Aug =
8 22:07:02 PDT 2004 jmg@carbon.funkthat.com:/a/obj/a/src/sys/GENERIC i=
386
>=20
OK, now we have a real problem here.
I have updated my system today, and when I let it boot automatically,
it didn't result in module_path set to point to the kernel directory,
as many others here have reported. I did some experimenting though.
If I enter the loader(8) prompt and type
unload
boot /boot/kernel/kernel
then it'd set module_path correctly. Finally, I've been able to find
the root of this problem: this is rather an old and sad story about
/boot/loader.rc -- the latter does not get updated automatically by an
installworld. I had my /boot/loader.rc matching revision 1.1 of
sys/boot/i386/loader/loader.rc. Now (because I knew this magic) after
I've manually updated it to:
$ ident /boot/loader.rc
/boot/loader.rc:
$FreeBSD: src/sys/boot/i386/loader/loader.rc,v 1.2 2003/11/21 19:01:02=
dcs Exp $
it all works as you intended. I think a lot of people will be bite
by this (since installworld doesn't update this file if it exists).
I suggest that at least a HEADS UP is sent and the UPDATING entry
is made, describing symptoms and a solution.
You can reproduce it yourself by downgrading your /boot/loader.rc
to rev. 1.1, and trying to reboot. I have beastie_enable=3D"NO" set
in my /boot/loader.conf, FWIW. I didn't try without it.
Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer
--yudcn1FV7Hsu/q59
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFBGp8bqRfpzJluFF4RAkRWAJ9lIfC5TaaKeaQmP6umsLZCAehUXgCfWaov
cZt1stBdQ6EG6V+j8BRJEZY=
=7EEH
-----END PGP SIGNATURE-----
--yudcn1FV7Hsu/q59--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040811223507.GD96867>