Prev: Cannot hear sound on my fc10 box
Next: NYC LOCAL: Sunday 24 January 2010 Wikipedia Day NYC
From: Magnus Warker on 23 Jan 2010 05:18
Hi,

I used to build and install new kernels this way:

- download, unpack in /usr/src/linux...
- make menuconfig
- make
- make modules_install

Well, after this step it always gets confusing. I know that some files have
to be copied to /boot. Some do it manually, some use some tools.
Additionally, there may be a ramdisk. Finally, there has to be an entry in
the grub menu file.

Well, I always have problems with this installation step. Often the mkinitrd
step fails because of missing modules. Often the new kernel does not boot
because of this.

However, what would be a simple way of doing this? Maybe without a ram disk?
Is there a unique recipe?

Thanks
Magnus
From: Mumia W. on 23 Jan 2010 06:44
On 01/23/2010 04:18 AM, Magnus Warker wrote:
> Hi,
>
> I used to build and install new kernels this way:
>
> - download, unpack in /usr/src/linux...
> - make menuconfig
> - make
> - make modules_install
>
> Well, after this step it always gets confusing. I know that some files have
> to be copied to /boot. Some do it manually, some use some tools.
> Additionally, there may be a ramdisk. Finally, there has to be an entry in
> the grub menu file.
>
> Well, I always have problems with this installation step. Often the mkinitrd
> step fails because of missing modules. Often the new kernel does not boot
> because of this.
>
> However, what would be a simple way of doing this? Maybe without a ram disk?
> Is there a unique recipe?
>
> Thanks
> Magnus

Install kernel-package and read its documentation. I used to have the
problems that you do. Now I use "make-kpkg" and get a .deb package of
the kernel.

From: Magnus Warker on 23 Jan 2010 09:00
Mumia W. wrote:

> Install kernel-package and read its documentation. I used to have the
> problems that you do. Now I use "make-kpkg" and get a .deb package of
> the kernel.

Thank you! Sounds cool! I will try it today!

Magnus
From: Magnus Warker on 23 Jan 2010 12:53
Mumia W. wrote:

> On 01/23/2010 04:18 AM, Magnus Warker wrote:
> Install kernel-package and read its documentation. I used to have the
> problems that you do. Now I use "make-kpkg" and get a .deb package of
> the kernel.

Well, it works fine! Just another question:

When *reinstalling* a kernel I do:

dpkg -r linux-image-xyz
dpkg -i linux-image-xyz

If I do not remove the "old" one I get a message that there still are
modules.

Can I ignore this and omit the removal with dpkg?

The reason: It takes endless to reinstall the kernel...

Thanks
Magnus
From: Mumia W. on 23 Jan 2010 13:43
On 01/23/2010 11:53 AM, Magnus Warker wrote:
> Mumia W. wrote:
>
>> On 01/23/2010 04:18 AM, Magnus Warker wrote:
>> Install kernel-package and read its documentation. I used to have the
>> problems that you do. Now I use "make-kpkg" and get a .deb package of
>> the kernel.
>
> Well, it works fine! Just another question:
>
> When *reinstalling* a kernel I do:
>
> dpkg -r linux-image-xyz
> dpkg -i linux-image-xyz
>
> If I do not remove the "old" one I get a message that there still are
> modules.
>
> Can I ignore this and omit the removal with dpkg?
>
> The reason: It takes endless to reinstall the kernel...
>
> Thanks
> Magnus

Yes, purge the old one first:

dpkg --purge linux-image-xyz

You can have several copies of a custom-compiled kernel installed at the
same time so long as each is compiled with a slightly different version
string.

make-kpkg --append-to-version=-local2 --rootcmd=fakeroot kernel_image

The "-local2" kernel won't conflict with a "-local1" or "-local3" kernel.

Rather than to perform the slave-labor of going through every
configuration option in the kernel, you might just grab a .config file
from your Debian stock kernel and put that into the source directory. Do
a "make oldconfig" and then "make menuconfig" to add your desired features.
 |  Next  |  Last
Pages: 1 2 3
Prev: Cannot hear sound on my fc10 box
Next: NYC LOCAL: Sunday 24 January 2010 Wikipedia Day NYC