Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Sep 1998 14:17:13 -0700 (PDT)
From:      Doug White <dwhite@resnet.uoregon.edu>
To:        Christopher Raven <c.raven@ukonline.co.uk>
Cc:        freebsd-questions <freebsd-questions@FreeBSD.ORG>
Subject:   Re: dmesg: magic number incorrect
Message-ID:  <Pine.BSF.4.03.9809211416420.11562-100000@resnet.uoregon.edu>
In-Reply-To: <36038AB6.43EB4D5F@ukonline.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Sep 1998, Christopher Raven wrote:

> Hi,
> 
> It seems I have managed to break something again.
> After rebuilding the kernel I have been getting
> the above error at boot time, and also if typed at
> console after boot:
> 
> #dmesg: magic number incorrect
> 
> Ok, this is what I think I did: - After upgrading
> from 2.2.6 to 2.2.7 (been running fine) I tried to
> add SYSVEM to the kernel so I could run "Wine".
> However, I rebuilt from my original 2.2.6 kernel
> and not the new Generic kernel  (with hindsight
> this was maybe not such a bright thing to do).
> 
> Assuming this is what "broke" dmesg, could I
> simply recompile from the Generic 2.2.7 kernel to
> fix it? Or do I need to rebuild dmesg (and
> anything else that might have been affected) and /
> or also rebuild 2.2.7 kernel?

Rebuild dmesg.  

Remember: NEVER NEVER NEVER upgrade just the kernel!! you must match the
userland binaries to the version of the kernel you'reusing.

Doug White                               
Internet:  dwhite@resnet.uoregon.edu    | FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite    | www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9809211416420.11562-100000>