2.6.16.19 + gcc-4.1.1

2.6.16.19 + gcc-4.1.1

[Russell Whitaker]

hi

First, I did this:
   made kernel with cpu=486, gcc-3.3.6
   worked fine.

Next, changed cpu to k6, all else same.
   worked fine.

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'

How should I fix it?
Please cc personally.

   Thanks,
     russ

Re: 2.6.16.19 + gcc-4.1.1

[Avuton Olrich]

On 6/13/06, Russell Whitaker <russ@ashlandhome.net> 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"
-- 
avuton
--
 Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

Re: 2.6.16.19 + gcc-4.1.1

[Brice Goglin]

Avuton Olrich wrote:
> On 6/13/06, Russell Whitaker <russ@ashlandhome.net> 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"

Actually, "make modules" does not exist anymore with 2.6. Both built-in
and modular stuff are built at the same time.
Only "make modules_install" is still required.

Brice

Re: 2.6.16.19 + gcc-4.1.1

[Willy Tarreau]

On Wed, Jun 14, 2006 at 12:10:59AM -0400, Brice Goglin wrote:
> Avuton Olrich wrote:
> > On 6/13/06, Russell Whitaker <russ@ashlandhome.net> 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"
> 
> Actually, "make modules" does not exist anymore with 2.6. Both built-in
> and modular stuff are built at the same time.
> Only "make modules_install" is still required.

What's this bullshit ?

$ grep ^modules: Makefile
modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
modules: $(module-dirs)

Avuton is right, you *have* forgotten to make modules.

> Brice

Willy

Re: 2.6.16.19 + gcc-4.1.1

[Brice Goglin]

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 <russ@ashlandhome.net> 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"
>>>       
>> Actually, "make modules" does not exist anymore with 2.6. Both built-in
>> and modular stuff are built at the same time.
>> Only "make modules_install" is still required.
>>     
>
> What's this bullshit ?
>
> $ grep ^modules: Makefile
> modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
> modules: $(module-dirs)
>   

Sorry, my mistake. Didn't know the target still existed. Anyway, "make"
now implies "make modules" so the latter is not required anymore as long
as you fully rebuild your kernel using the former (which I assume
Russell did since he changed his compiler).

Brice

Re: 2.6.16.19 + gcc-4.1.1

[Russell Whitaker]

On Wed, 14 Jun 2006, 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 <russ@ashlandhome.net> 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"
>>
>> Actually, "make modules" does not exist anymore with 2.6. Both built-in
>> and modular stuff are built at the same time.
>> Only "make modules_install" is still required.
>
> What's this bullshit ?
>
> $ grep ^modules: Makefile
> modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
> modules: $(module-dirs)
>
> Avuton is right, you *have* forgotten to make modules.
>
>> Brice
>
> Willy
>
After found the above problem, did it all again to be sure:

   make mrproper
   rm -r /lib/modules/*
   cp ../config-2.6.16.19 .config
   make menuconfig    ( made sure it's same config, then saved without
                        changes )
   make
   make modules
   make modules_install
   make bzlilo

Same result.
   russ

Re: 2.6.16.19 + gcc-4.1.1

[Tino Keitel]

On Tue, Jun 13, 2006 at 19:23:30 -0700, Russell Whitaker wrote:
> hi
> 
> First, I did this:
>   made kernel with cpu=486, gcc-3.3.6
>   worked fine.
> 
> Next, changed cpu to k6, all else same.
>   worked fine.
> 
> 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'

Did you reboot with the kernel built with gcc 4.1.1? The gcc version in
/proc/version has to match the gcc version of the module you want to
load..

Regards,
Tino

Re: 2.6.16.19 + gcc-4.1.1

[Jan Engelhardt]

>Actually, "make modules" does not exist anymore with 2.6. Both built-in
>and modular stuff are built at the same time.
>Only "make modules_install" is still required.
>
You can _still_ build bzImage and modules separately.

The _default_ kernel Makefile target though reads (sth. like)

all: bzImage modules


Jan Engelhardt
-- 

Re: 2.6.16.19 + gcc-4.1.1

[Alistair John Strachan]

On Wednesday 14 June 2006 10:33, Jan Engelhardt wrote:
> >Actually, "make modules" does not exist anymore with 2.6. Both built-in
> >and modular stuff are built at the same time.
> >Only "make modules_install" is still required.
>
> You can _still_ build bzImage and modules separately.
>
> The _default_ kernel Makefile target though reads (sth. like)
>
> all: bzImage modules

Maybe for consistency with other packages, the default "make install" should 
imply modules_install too.

I know you can hack around this with /sbin/installkernel (on at least x86 and 
x86_64), but it's counterintuitive. I guess the reason is that 'install' has 
always meant "just the bzImage please", and sometimes it's valid to install 
only a bzImage without reinstalling modules. However, it just leads to 
problems such at the original poster's.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

Re: 2.6.16.19 + gcc-4.1.1

[Russell Whitaker]

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 <russ@ashlandhome.net> 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