On Wed, 14 Jun 2006, Brice Goglin wrote:
Willy Tarreau wrote:
On Wed, Jun 14, 2006 at 12:10:59AM -0400, Brice Goglin wrote:
Avuton Olrich wrote:
On 6/13/06, Russell Whitaker <[email protected]> wrote:
Then, after mrproper, rebuilt with gcc-4.1.1, no other changes.
compiles ok, installs ok. But, when attempting to load a module, get
the following message: version magic '2.6.16.19via K6 gcc-4.1',
should be '2.6.16.19via 486 gcc-3.3'
You may have forgotten to "make modules modules_install"
Problem solved:
The original installation, Slackware, uses "/vmlinuz". The kernel build
uses "/boot/vmlinuz" and the original lilo.config without checking to see
if there is a "/boot/vmlinuz" in it. Thus on reboot the system is trying
to match the old kernel with the new modules.
A warning message would have been nice.
Thanks, all, for the help.
russ
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
