People who compile Puppy kernels some info and questions

[bigpup]

For those of you that compile Puppy kernels.

Something to consider when compiling a kernel.

Recently I helped someone trying to get Fossapup64 9.5, to boot, installed on an internal emmc/nvme drive.
It would not boot with errors about not finding Fossapup64 files.

On my suggestion, the person changed the kernel in Fossapup64, to a very new Puppy kernel package, compiled for LxPupsc64.

This kernel package change fixed the boot issues and Fossapup64, now boots from the install on a emmc/nvme internal drive.

What do you think is the difference in the kernel, that comes with Fossapup64 9.5, and this different kernel?

Having it better configured to support emmc/nvme drives?

Having newer stuff from the Puppy building kernel-kit?

[rockedge]

@bigpup

The Linux NVMe driver is natively included in the kernel since version 3.3. NVMe devices should show up under /dev/nvme*

Though it seems the higher newer versions of kernel 5+ are "seeing" and booting the solid state drives.

[bigpup]

When compiling the kernel.
Doesn't the nvme need to be configured enabled, when doing the config setup of the kernel?

[Phoenix]

When compiling the kernel.
Doesn't the nvme need to be configured enabled, when doing the config setup of the kernel?

It may be enabled by default. Usually you can find this in documentation or when you look through the options when allowing Kconfig to select defaults.
But there are some catches, particularly in puppy for instance. It would be unwise for example to place a kernel on a drive, put the support for it in a module which is also in this same drive. It won't work! (Partially will work but otherwise not)

[rockedge]

it is included in the kernel build as default. No special configuration is needed for nvme to be included.