[EMAIL PROTECTED] wrote: > In <[EMAIL PROTECTED]> Peter Wemm <peter@netple x.com.au> wrote: > > Charlie & wrote: > >> On Tue, Jan 11, 2000 at 01:41:18AM -0800, Kris Kennaway wrote: > >> > On Tue, 11 Jan 2000 [EMAIL PROTECTED] wrote: > >> > > >> > > At least from the January 9 after 'cvsup', > >> > > 'make buildworld','make installworld', 'make & install kernel' > >> > > I can't 'kldload linux'. 'Kldload" says: > >> > > >> > Probably one of these is not up to date, or is out of sync. I had this > >> > problem yesterday when my modules were out of date. Please double-check to > >> > make sure.. > >> > >> And what (apart from listed actions) is the best > >> method to establish "syncronization" of the kernel, modules and > >> kldload ? > > > > IMHO, add 'options COMPAT_LINUX' to your kernel and don't use the module if > > you are going to be regularly compiling the kernel and modules seperately.. > > Thanks a lot for your advice(s) but on my CURRENT > box I compile kernel and modules seperately only in thouse > (rare enough) cases when one of them is broken. > > So, the problem is not in "out of sync" kernel > and modules. And besides of "linux.ko" the same problem > (i.e. kldload errror) have all modules with NDFREE reference - > ccd.ko, cd9660.ko, coda.ko, ibcs2.ko, ibcs2_coff.ko, msdos.ko, > nfs.ko, ntfs.ko, null.ko, svr4.ko, umap.ko, union.ko, vinum.ko, vn.ko. > > Can somebody with CURRENT system test 'kldload' some > of the above modules on his machine and post the results ? First of all, can you try this please? > nm /kernel | grep NDFREE c0186b64 T NDFREE This is to check that NDFREE is actually defined in your /kernel.. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
