Re: config/kernel version mismatch after cvsup

From: Olivier Houchard (cognet_at_ci0.org)
Date: 05/31/04

  • Next message: mangala: "Re: reboot and shutdown don't work, suspect acpi" 
    Date: Mon, 31 May 2004 03:34:54 +0200
To: Peter Schuller <peter.schuller@infidyne.com>

    On Mon, May 31, 2004 at 03:17:56AM +0200, Peter Schuller wrote:
    > Hello,
    >
    > I cvsuped CURRENT today, wanting to test some new things that have gone into
    > the tree. However I now get:
    >
    > ERROR: version of config(8) does not match kernel!
    > config version = 500012, version required = 500013
    >
    > ... etc, during 'make buildkernel KERNCONF=THUNDERBOLD' (happens with
    > GENERIC too).
    >
    > To be certain I didn't accidentally cvsup in the middle of an update I have
    > cvsuped again a few hours later, but I still have the same problem.
    >
    > The only thing I could think of was that it was caused by me running a kernel
    > newer than userland (though I would expect the above to refer to the source
    > tree only?), so I booted a kernel matching my userland (5.2-RELEASE) but am
    > still getting the same error.
    >
    > What am I missing?
    >
    > (I did the full 'make cleandir && make cleandir && make buildkernel
    > KERNCONF=THUNDERBOLT' sequence, not just 'make buildkernel')
    >

    Hi,

    Please recompile config (cd /usr/src/usr/sbin/config && make depend all install)

    Cheers,

    Olivier
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: mangala: "Re: reboot and shutdown don't work, suspect acpi"

    Relevant Pages

    • Re: config/kernel version mismatch after cvsup
      ... version of configdoes not match kernel! ... > newer than userland (though I would expect the above to refer to the source ... > tree only?), so I booted a kernel matching my userland but am ... The correct update sequence documented in the handbook and UPDATING. ...
      (freebsd-current)
    • Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
      ... If I understand correctly the above means "include/* userland breakage ... Potential breakage is mostly a non issue - since vanilla kernel headers are ... layer that will look like the old tree but in fact use the new tree.* And ...
      (Linux-Kernel)
    • powerpc: Add flattened device tree documentation
      ... The flattened device tree is the only supported way of booting ... +order to avoid the degeneration that had become the ppc32 kernel entry ... +the presence of a device-tree whose format is defined after Open ... + present if the processor is a SOC. ...
      (Linux-Kernel)
    • Re: RFC: Starting a stable kernel series off the 2.6 kernel
      ... > kernel upgrade depends on a new wpa_supplicant package. ... I've broken stuff by upgrading glibc, upgrading X, upgrading KDE... ... Automating the patch flow allowed entire subsystems to be effectively ... maintain a tree and merge with linus, and back then the -ac tree was very ...
      (Linux-Kernel)
    • Re: Attempted summary of "RT patch acceptance" thread
      ... tries to keep the userland API as close as possible to the non-RT one, ... by increasing the kernel complexity with relative slowdown. ... RTAI quickly becomes useless (ok it can run nanosleep with fusion fine, ... RTAI/rtlinux as the only hard-RT with guaranteed deadline. ...
      (Linux-Kernel)