[PATCH] Don't list /lib/modules/$KernelVer/kernel twice
by Paul Bolle
For quite some time I see warnings like
warning: File listed twice: /lib/modules/[...]/kernel
when building the kernel-core rpm. This is because that directory is included
both in module-dirs.list (and therefor in, basically, kernel-core.list) and in
kernel_variant_files().
Tweak the find command that generates module-dirs.list so that this directory
is not included in that list anymore.
Signed-off-by: Paul Bolle <pebolle(a)tiscali.nl>
---
Works as expected on my current local F24 based tree (that branched of
at release 4.6.5-300).
Applies cleanly to current master. But I have not tested this on that
branch.
kernel.spec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel.spec b/kernel.spec
index 1b7040b503e9..8d3f630b310b 100644
--- a/kernel.spec
+++ b/kernel.spec
@@ -1644,7 +1644,7 @@ BuildKernel() {
# Go back and find all of the various directories in the tree. We use this
# for the dir lists in kernel-core
- find lib/modules/$KernelVer/kernel -type d | sort -n > module-dirs.list
+ find lib/modules/$KernelVer/kernel -mindepth 1 -type d | sort -n > module-dirs.list
# Cleanup
rm System.map
--
2.7.4
6 years, 11 months
realtek wireless modules
by Peter Robinson
Hi Laura, Justin, et el,
I've been playing with a handful of cheap USB wireless modules for
support on the Raspberry Pi and other similar devices.
I've noticed that there's a bunch of overlap regarding usb IDs between
the newer (and IMO preferred) rtl8xxxu and the vendor collection of
drivers so you often get both drivers loaded. I've tended to fix this
by just blacklisting the vendor upstream drivers.
The question is how best to deal with this in a generic way to ensure
a good experience with these in Fedora?
Do we cross reference all the USB IDs and disable the non rtl8xxxu
drivers once they have full coverage in rtl8xxxu? Do we actively patch
out the IDs supported in rtl8xxxu from associated drivers?
Peter
6 years, 11 months
4.8, stabilization, and F25
by Justin Forbes
We have been using the stabilization branch and copr lately to keep the
stream going on a stable kernel release before we rebase a Fedora release
with it. We will not be doing that with 4.8 as it is already being
maintained in F25. For those wishing to run it early on F24, the F25
builds should work just fine. The 4.8.1 build is running now and will be
submitted to bodhi for F25 as soon as it finishes and goes through some
testing.
For Fedora 24 and 23, they will be rebased to 4.8.x probably around mid
month, depending on how things are looking with respect to regressions and
bugs fixed.
Thanks,
Justin
6 years, 12 months
