From: moabeat-berlin <moabeat-berlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Raspberry PI Updates
Date: Sun, 17 Sep 2023 23:17:05 +0200 [thread overview]
Message-ID: <20230917211705.SNLi19ws5apxHKjWTmzEQOgXW1pE5eiimCh5oPxlLM0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43600@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
New comment by moabeat-berlin on void-packages repository
https://github.com/void-linux/void-packages/pull/43600#issuecomment-1722569106
Comment:
I think I figured something out why dkms is not working with the new kernel. There have been some changes how the kernel is configured. For example, the crypto module got has now dependencies into the "arch" directory. Check this [diff between the old 5.15.72 and the newer 6.1.53](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/crypto/Kconfig?id=v6.1.53&id2=v5.15.72) version.
Now, the dkms with the x86_64 architecture only works due an error in the template script of the "linux6.3" package. [Here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/linux6.3/template#L294) all files related to unnecessary architectures should actually get removed. The case to extend this also to architectures like "powerpc" (matching *p) uses the "arch" variable and expects it either as "i386" or "x86_64". However, this is never true as [here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/linux6.3/template#L119) the "arch" variable is set to "x86". Therefore no "powerpc" directory is removed on x86_64 and dkms works. By accident all necessary sub-directories in the "arch" directory are present.
For "arm64" this is different. Here architectures starting with "p*" are removed. Now the question is, why is this importantfor the "rpi-kernel"? Well, something similar is present in the "rpi-kernel" package [here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/rpi-kernel/template#L193). It even removes "arm64" if you are on "arm". And since there is a hard-coded dependency in "crypto/Kconfig" it breaks. Additionally the "dkms" package depends on the "linux-headers" package, only for architecture "arm" and "arm64" (matching arm*) [here](https://github.com/void-linux/void-packages/blob/master/srcpkgs/dkms/template#L20). That also installs the "linux6.3-headers" package, which also removes architectures (as describes above). So neither dkms module build is successful, not for "rpi-kernel" nor for the usual "linux-kernel".
Maybe the best approach is, to not remove any unnecessary architectures at all anymore if there are so many interdependences?
next prev parent reply other threads:[~2023-09-17 21:17 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 20:35 [PR PATCH] " kenrap
2023-04-24 21:22 ` classabbyamp
2023-04-24 23:21 ` [PR PATCH] [Updated] " kenrap
2023-04-24 23:24 ` kenrap
2023-04-30 22:00 ` kenrap
2023-04-30 22:23 ` classabbyamp
2023-05-09 7:42 ` tsjk
2023-05-10 14:18 ` leahneukirchen
2023-05-10 14:20 ` classabbyamp
2023-05-10 17:09 ` tsjk
2023-05-10 17:57 ` classabbyamp
2023-05-10 18:44 ` [PR PATCH] [Updated] " kenrap
2023-05-10 18:48 ` kenrap
2023-05-10 19:18 ` classabbyamp
2023-05-10 19:24 ` classabbyamp
2023-05-10 19:26 ` classabbyamp
2023-05-10 19:30 ` tsjk
2023-05-10 19:33 ` kenrap
2023-05-10 19:40 ` tsjk
2023-05-10 19:44 ` tsjk
2023-05-10 19:45 ` tsjk
2023-05-10 20:02 ` [PR PATCH] [Updated] " kenrap
2023-05-10 20:12 ` classabbyamp
2023-05-11 10:27 ` tsjk
2023-05-11 10:28 ` tsjk
2023-05-11 10:48 ` tsjk
2023-05-11 13:28 ` tsjk
2023-05-11 13:37 ` tsjk
2023-05-11 13:41 ` tsjk
2023-05-11 14:51 ` classabbyamp
2023-05-11 14:51 ` classabbyamp
2023-05-11 15:02 ` tsjk
2023-05-11 15:10 ` classabbyamp
2023-05-11 15:13 ` classabbyamp
2023-05-11 15:15 ` tsjk
2023-05-11 15:16 ` tsjk
2023-05-11 15:21 ` tsjk
2023-05-11 15:25 ` tsjk
2023-05-11 15:26 ` tsjk
2023-05-11 15:26 ` tsjk
2023-05-11 15:29 ` tsjk
2023-06-13 15:07 ` ahesford
2023-06-13 17:19 ` lilmike
2023-06-25 8:41 ` [PR PATCH] [Updated] " classabbyamp
2023-06-25 9:19 ` classabbyamp
2023-07-30 21:25 ` r-ricci
2023-08-03 19:09 ` tsjk
2023-08-03 19:39 ` classabbyamp
2023-09-17 21:07 ` moabeat-berlin
2023-09-17 21:17 ` moabeat-berlin [this message]
2023-09-17 21:18 ` moabeat-berlin
2023-09-19 11:16 ` leahneukirchen
2023-09-19 16:13 ` moabeat-berlin
2023-09-19 16:22 ` leahneukirchen
2023-09-19 18:22 ` tsjk
2023-09-19 18:26 ` classabbyamp
2023-09-20 11:34 ` classabbyamp
2023-09-20 11:34 ` classabbyamp
2023-09-20 11:36 ` [PR PATCH] [Closed]: " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230917211705.SNLi19ws5apxHKjWTmzEQOgXW1pE5eiimCh5oPxlLM0@z \
--to=moabeat-berlin@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).