Discussion, talk and tips
https://forum.puppylinux.com/
When the "kernel-kit" action is run,
Where does it get it's DOTconfig files from?
I'm trying to workout what needs to be changed to include the "battery" kernel configs.
The kernels generated by the "kernel-kit" action seem to have the opposite problem to the "debian-kernel" action.
i.e. the "boot" configs are present but the "battery" configs are missing.
They're built using complete configuration files (10k lines) under config_*, like https://github.com/puppylinux-woof-CE/w ... .13-x86_64.
The dpup kernels are built:
I do my best to add modules or change modules to =y when users report about issues with dpup, but I do it only for the dpup kernels because they have few issues (the Debian kernel more drivers enabled compared to most Puppy kernels) and they're easy to maintain.
dimkr wrote: Thu Feb 01, 2024 1:20 pmThey're built using complete configuration files (10k lines) under config_*, like https://github.com/puppylinux-woof-CE/w ... .13-x86_64.
Thanks for confirming this. I will look at a PR to "fix" these, starting with 6.1.13-x86_64.
dimkr wrote: Thu Feb 01, 2024 1:20 pmThe dpup kernels are built:
- Using Debian's kernel source (https://github.com/puppylinux-woof-CE/w ... el.yml#L50)
- Using Debian's generic kernel configuration (https://github.com/puppylinux-woof-CE/w ... el.yml#L28)
- Plus a small delta - just the 130 configuration changes needed by Puppy (mostly =m to =y changes to support boot media or various file systems, and for overlay+squashfs) plus some changes to reduce resource consumption (like TRANSPARENT_HUGEPAGE_MADVISE=y) (https://github.com/puppylinux-woof-CE/w ... s/bookworm)
I do my best to add modules or change modules to =y when users report about issues with dpup, but I do it only for the dpup kernels because they have few issues (the Debian kernel more drivers enabled compared to most Puppy kernels) and they're easy to maintain.
Yes, I get that, with your help the debian kernels have already been "fixed".