OT: compilation

OT: compilation

[Grzesiek Sójka]

I have two problems with the kernel compilation.

1. I have a small rootfs. It is too small to put all the modules there 
without gzipping it first. So installing it requires lots of sweating. 
That is why I was wondering if there is a (more/less easy) way to make 
the "make modules_install" command gzip the modules "on the fly".

2. I modified the sources and after compilation the string 
"g76f6e1f-dirty" was appended to the kernel version. It is a bit 
annoying because of the lack of the space at the rootfs. Is there a way 
to avoid this kind of a version extension??

Thanks for your help in advance.

Re: OT: compilation

[Pekka Paalanen]

On Thu, 07 Oct 2010 22:14:19 +0200
Grzesiek Sójka <pld-t9zbU3WrWHI@public.gmane.org> wrote:

> I have two problems with the kernel compilation.
> 
> 1. I have a small rootfs. It is too small to put all the modules
> there without gzipping it first. So installing it requires lots
> of sweating. That is why I was wondering if there is a (more/less
> easy) way to make the "make modules_install" command gzip the
> modules "on the fly".

Wait, does modprobe support compressed kernel modules? I've
never heard of that. If you really do not want to touch
the partitioning, how about symlinking some directories
elsewhere? Be careful on what is needed to boot, though.

> 2. I modified the sources and after compilation the string 
> "g76f6e1f-dirty" was appended to the kernel version. It is a bit 
> annoying because of the lack of the space at the rootfs. Is there
> a way to avoid this kind of a version extension??

Yes, it is CONFIG_LOCALVERSION_AUTO as far as I recall, disable that.

-- 
Pekka Paalanen
http://www.iki.fi/pq/

Re: OT: compilation

[Grzesiek Sójka]

On 10/07/10 22:34, Pekka Paalanen wrote:
> On Thu, 07 Oct 2010 22:14:19 +0200
> Grzesiek Sójka<pld-t9zbU3WrWHI@public.gmane.org>  wrote:
>
>> I have two problems with the kernel compilation.
>>
>> 1. I have a small rootfs. It is too small to put all the modules
>> there without gzipping it first. So installing it requires lots
>> of sweating. That is why I was wondering if there is a (more/less
>> easy) way to make the "make modules_install" command gzip the
>> modules "on the fly".
>
> Wait, does modprobe support compressed kernel modules? I've
Yes, it does. I thing that most of the distribution pre-compiled kernels 
does have gziped modules.

> never heard of that. If you really do not want to touch
> the partitioning, how about symlinking some directories
> elsewhere? Be careful on what is needed to boot, though.
Wrong idea. I already tried this.

Re: OT: compilation

[Grzesiek Sójka]

On 10/07/10 22:34, Pekka Paalanen wrote:
> Yes, it is CONFIG_LOCALVERSION_AUTO as far as I recall, disable that.
Where is it?? Which file??

Re: OT: compilation

[walt]

On 10/07/2010 01:46 PM, Grzesiek Sójka wrote:
> On 10/07/10 22:34, Pekka Paalanen wrote:
>> Yes, it is CONFIG_LOCALVERSION_AUTO as far as I recall, disable that.
> Where is it?? Which file??

It is part of your kernel configuration.  Go to the directory containing
the source code of your kernel, usually /usr/src/linux-2.6.xx, and then
run 'make menuconfig'.

When the configuration menu appears, type the '/' character to enter the
'search' mode and then type 'localversion' (for example) to find the list
of matching items.

I find two items:

  Symbol: LOCALVERSION [=]                                                                                   │
   │ Type  : string                                                                                             │
   │ Prompt: Local version - append to kernel release                                                           │
   │   Defined at init/Kconfig:87                                                                               │
   │   Location:                                                                                                │
   │     -> General setup                                                                                       │
   │                                                                                                            │
   │                                                                                                            │
   │ Symbol: LOCALVERSION_AUTO [=y]                                                                             │
   │ Type  : boolean                                                                                            │
   │ Prompt: Automatically append version information to the version string                                     │
   │   Defined at init/Kconfig:97                                                                               │
   │   Location:                                                                                                │
   │     -> General setup                                                                                       │

The difference between the two is not obvious, but the second item is what
you were (correctly) advised to look for.

Notice that the "Location" of both items is "General setup".

Exit the search function.

You should now be back in the kernel configuration menu and , just by
luck, the "General setup" item should already be highlighted (for me it
is colored blue).

Hit Enter to see the the "General setup" menu.

On my machine the item you want is on line number four.  Hit the SPACE
bar to select the item and then use the TAB key to navigate to "Exit"
and hit Enter to go back to the main menu and then hit "Exit" again.

You should see a dialog asking you if you want to save your new kernel
configuration, and, of course, you do want to save it.

Now recompile and install your new kernel.


_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

Re: OT: compilation

[Xavier Chantry]

2010/10/7 Grzesiek Sójka <pld-t9zbU3WrWHI@public.gmane.org>:
> I have two problems with the kernel compilation.
>
> 1. I have a small rootfs. It is too small to put all the modules there
> without gzipping it first. So installing it requires lots of sweating. That
> is why I was wondering if there is a (more/less easy) way to make the "make
> modules_install" command gzip the modules "on the fly".
>

No idea if you can do that but here are some possible alternatives :
1) increase the size of your rootfs
2) remove modules you don't need and change from modules to builtin
for features or drivers that you don't need to unload/reload
3) a quick googling showed me this patch :
http://www.mail-archive.com/linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg271865.html
However it seems to install first then compress so if that's the case,
you will need to adapt it to your need
4) set INSTALL_MOD_PATH to a prefix , compress modules , then move to
/lib/modules/


LOCALVERSION_AUTO is found in :
make menuconfig
General Setup
Automatically append version information to the version string

Re: OT: compilation

[Grzesiek Sójka]

On 10/07/10 22:50, Xavier Chantry wrote:
> 2010/10/7 Grzesiek Sójka<pld-t9zbU3WrWHI@public.gmane.org>:
>> I have two problems with the kernel compilation.
>>
>> 1. I have a small rootfs. It is too small to put all the modules there
>> without gzipping it first. So installing it requires lots of sweating. That
>> is why I was wondering if there is a (more/less easy) way to make the "make
>> modules_install" command gzip the modules "on the fly".
>>
>
> No idea if you can do that but here are some possible alternatives :
> 1) increase the size of your rootfs
Veeeeeeeeeeeeery difficult in my case.

> 2) remove modules you don't need and change from modules to builtin
> for features or drivers that you don't need to unload/reload
I'm trying to do this. Unfortunately I did not compile the kernel by 
myself for at lest 5 yeas and it is a big in my a%$#.

> 3) a quick googling showed me this patch :
> http://www.mail-archive.com/linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg271865.html
> However it seems to install first then compress so if that's the case,
> you will need to adapt it to your need
If I'm right it compress every module _just_after_ imstalling it. So it 
should be fine for me.

> 4) set INSTALL_MOD_PATH to a prefix , compress modules , then move to
> /lib/modules/
If 3) don't helps I try to do this.


> LOCALVERSION_AUTO is found in :
> make menuconfig
> General Setup
> Automatically append version information to the version string


Supper thanks