Tiny Core Extensions > TCE Tips & Tricks

Compiling kernel and modules on TC

<< < (9/12) > >>

Misalf:
You could rename it to  vmlinuz  or something else, and edit your boot loader's config file.

--

In my understanding, building the kernel from source, will create a binary file. Features that are not used often can be separated by creating modules to be loaded only if needed. Though, separated modules need to be available for the kernel early in the boot process. That's why you need to store kernel modules in an initrd (initial ram drive?). However,  core.gz  could be updated manually, if needed. But by building the kernel, you dont create the initrd file.

Scampada:
I tried to boot from the new bzImage with old initrd (editing my grub entry) but it crashed to something like "can't change directory to 3.16.6 blah blah". Then, I somehow managed to login as tc but no disk were mounted and no extensions installed. I think maybe the old initrd is not suitable. But I found no new initrd in the kernel-build folder...

I read README in source folder, but there were not any clues... So weren't they on the wiki page.

gerald_clark:
Please read the wiki articles on compiling a kernel and rebuilding the initrd.
Your initrd must hold the modules for your new kernel.

Scampada:

--- Quote from: gerald_clark on April 08, 2015, 06:29:22 PM ---Please read the wiki articles on compiling a kernel and rebuilding the initrd.
Your initrd must hold the modules for your new kernel.

--- End quote ---
Erm. Okay. Maybe I read it not very attentively.

Scampada:
That occured after I did
make INSTALL_MOD_PATH=/path modules_install firmware_install
from the wiki page.

Navigation

[0] Message Index

[#] Next page

[*] Previous page