On Sun, 04 Sep 2022 01:58:08 -
Sharpened Blade via users wrote:
> I am sure it is not the config, unless there is something fedora
> specific, because there is an arch linux packagebuild that uses the
> the same config additions and works. I diffed menuconfig and got the
> same thing to. Does
I am sure it is not the config, unless there is something fedora specific,
because there is an arch linux packagebuild that uses the the same config
additions and works. I diffed menuconfig and got the same thing to. Does the
spec do something to prevent drivers in staging from being built.
That may or may not be the right CONFIG_* option."make oldconfig"
I think will copy the current config and question you on any new
options.
You could also look at the source code for the modules you want to
build (or make menuconfig and enable them and diff the config file) to
figure out what
I added the CONFIG_NAMEOFMODULE=m to local-config. which works for the normal
kernel, do I have to do something else, I would prefer to be able to do it
without a TUI because I want to script the build process. Should I run
`./scripts/config --module nameofmodule` and `make olddefconfig`.
__
I have to rebuild every new kernel because of the simple-drm module issue.
I modify my config with the file /rpmbuild/SOURCES/kernel-local
kernel-local :
# This file is intentionally left empty in the stock kernel. Its a nicety
# added for those wanting to do custom rebuilds with altered config o
You would have to run "make menuconfig" and update the config file
used in the source rpm.
The config file controls what modules and/or other drivers get
compiled, if you did not change the config file none of the add-ons
would get compiled.
On Fri, Sep 2, 2022 at 6:43 PM Sharpened Blade via use
I can get the kernel to build from the vanilla sources in the method you
outlined, I want to make it an RPM to distribute it in a repo. I am using
fedoras spec file because I want it to be as much of a drop in replacement of
the normal kernel possible.
___
You would have to change the correct config options. make menuconfig
used to bring up the interface for that and then you need to figure
out which corner of the menu your modules are hiding. the rpmbuild
is going to be very hardwired to make it harder to do what you are
wanting to do.
When doi
I want to build a custom kernel with some modules and patches added, and
package this as an rpm to install. I have tried adding it like building the
kernel from the git source, but it doesnt have the modules. I think it might
have to do with the .spec file. I added the patches to the rpm, and I
