From: moabeat-berlin <moabeat-berlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cross-built kernel/dkms improvements
Date: Sun, 01 Oct 2023 22:15:54 +0200 [thread overview]
Message-ID: <20231001201554.5WUhHUFzISsYiOF-aGIT9FOcIiQwbNNNiYZ3UQZPdvc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46332@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]
New comment by moabeat-berlin on void-packages repository
https://github.com/void-linux/void-packages/pull/46332#issuecomment-1742189190
Comment:
I have rebuilt the packages in this PR with the latest changes (aarch64 and aarch64-musl), source is still `https://barrens.de/repo/`. I had to remove them also from `/var/cache/xbps/` to make sure it's not the old one installed from there.
Testing dkms on "aarch64-musl" by installing "ddcci-dkms" was successful and it also respected the `/etc/default/dkms` jobs settings on the Raspberry Pi Zero 2W (using new the "xbps-triggers" package). However, installing "zfs" was still not possible (device unresponsive after some time). It did not respect the setting. It seems to use it's own mechanism of building the module and was running with `-j4` again. But I was not able to figure out yet how this exactly happens.
<details><summary>dkms ddcci-dkms install log</summary>
```
# xbps-install ddcci-dkms
Name Action Version New version Download size
ddcci-dkms install - 0.4.3_1 -
Size required on disk: 82KB
Space available on disk: 27GB
Do you want to continue? [Y/n]
[*] Verifying package integrity
ddcci-dkms-0.4.3_1: verifying RSA signature...
[*] Collecting package files
ddcci-dkms-0.4.3_1: collecting files...
[*] Unpacking packages
ddcci-dkms-0.4.3_1: unpacking ...
[*] Configuring unpacked packages
ddcci-dkms-0.4.3_1: configuring ...
Added DKMS module 'ddcci-0.4.3'.
Prepare to build modules for kernel-6.1.54_1... done.
Building DKMS module 'ddcci-0.4.3' for kernel-6.1.54_1... done.
Installing DKMS module 'ddcci-0.4.3' for kernel-6.1.54_1... done.
Prepare to build modules for kernel-6.1.55_2... done.
Building DKMS module 'ddcci-0.4.3' for kernel-6.1.55_2... done.
Installing DKMS module 'ddcci-0.4.3' for kernel-6.1.55_2... done.
Prepare to build modules for kernel-6.3.13_2... done.
Building DKMS module 'ddcci-0.4.3' for kernel-6.3.13_2... done.
Installing DKMS module 'ddcci-0.4.3' for kernel-6.3.13_2... done.
Prepare to build modules for kernel-6.5.5_2... done.
Building DKMS module 'ddcci-0.4.3' for kernel-6.5.5_2... done.
Installing DKMS module 'ddcci-0.4.3' for kernel-6.5.5_2... done.
ddcci-dkms-0.4.3_1: installed successfully.
0 downloaded, 1 installed, 0 updated, 1 configured, 0 removed.
```
</details>
<details><summary>make processes during zfs install</summary>
```
#ps -Af | grep make
root 2326 2325 13 20:13 pts/1 00:00:00 make modules -k -j4 CONFIG_MODULES=y CFLAGS_MODULE=-DCONFIG_MODULES -C /lib/modules/6.1.54_1/build M=/var/lib/dkms/zfs/2.1.12/build/build
moabeat 2543 14729 0 20:13 pts/2 00:00:00 grep make
```
</details>
So, in general probably a success, beside "zfs" on the Zero 2W.
next prev parent reply other threads:[~2023-10-01 20:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 21:59 [PR PATCH] " classabbyamp
2023-09-30 1:14 ` [PR PATCH] [Updated] " classabbyamp
2023-09-30 16:46 ` Calandracas606
2023-09-30 16:49 ` Calandracas606
2023-09-30 16:54 ` classabbyamp
2023-09-30 16:54 ` classabbyamp
2023-09-30 17:05 ` Calandracas606
2023-09-30 18:21 ` moabeat-berlin
2023-09-30 22:30 ` moabeat-berlin
2023-10-01 1:06 ` classabbyamp
2023-10-01 1:06 ` classabbyamp
2023-10-01 1:59 ` [PR PATCH] [Updated] " classabbyamp
2023-10-01 3:09 ` Calandracas606
2023-10-01 4:40 ` [PR PATCH] [Updated] " classabbyamp
2023-10-01 10:02 ` moabeat-berlin
2023-10-01 10:03 ` moabeat-berlin
2023-10-01 15:42 ` Calandracas606
2023-10-01 20:15 ` moabeat-berlin [this message]
2023-10-01 20:21 ` [PR PATCH] [Merged]: " 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=20231001201554.5WUhHUFzISsYiOF-aGIT9FOcIiQwbNNNiYZ3UQZPdvc@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).