From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland, rpi-eeprom)
Date: Sat, 30 Sep 2023 04:41:26 +0200 [thread overview]
Message-ID: <20230930024126.kNWtDiwlKfO5EIW1oIDlNUGiL8yl89FQvLzqZCDsKyI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46152@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4906 bytes --]
There's a merged pull request on the void-packages repository
rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland, rpi-eeprom)
https://github.com/void-linux/void-packages/pull/46152
Description:
- rpi-kernel: update to 6.1.54.
- rpi-firmware: update to 20230920.
- rpi-userland: update to 20230920.
continuation of #43600, made a new PR to clean things up
builds for testing: https://devspace.voidlinux.org/abby/updates/rpi/
#### Testing the changes
- I tested the changes in this PR: **YES**
Still getting the DKMS/headers issue:
When building `fixdep` and `modpost` in `/etc/kernel.d/post-install/10-dkms`, it gets stuck in an infinite makefile loop:
https://github.com/void-linux/void-packages/blob/5b18878cc72b410bc076ac15218f4c5fa0c3fcbf/srcpkgs/dkms/files/kernel.d/dkms.postinst#L22-L24
```
# xbps-reconfigure -f rpi-kernel
rpi-kernel: configuring ...
Executing post-install kernel hook: 10-dkms ...
SYNC include/config/auto.conf
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/confdata.o
HOSTCC scripts/kconfig/expr.o
HOSTCC scripts/kconfig/lexer.lex.o
HOSTCC scripts/kconfig/menu.o
HOSTCC scripts/kconfig/parser.tab.o
HOSTCC scripts/kconfig/preprocess.o
HOSTCC scripts/kconfig/symbol.o
HOSTCC scripts/kconfig/util.o
HOSTLD scripts/kconfig/conf
HOSTCC scripts/dtc/dtc.o
HOSTCC scripts/dtc/flattree.o
HOSTCC scripts/dtc/fstree.o
HOSTCC scripts/dtc/data.o
HOSTCC scripts/dtc/livetree.o
HOSTCC scripts/dtc/treesource.o
HOSTCC scripts/dtc/srcpos.o
HOSTCC scripts/dtc/checks.o
HOSTCC scripts/dtc/util.o
HOSTCC scripts/dtc/dtc-lexer.lex.o
HOSTCC scripts/dtc/dtc-parser.tab.o
HOSTLD scripts/dtc/dtc
HOSTCC scripts/dtc/libfdt/fdt.o
HOSTCC scripts/dtc/libfdt/fdt_ro.o
HOSTCC scripts/dtc/libfdt/fdt_wip.o
HOSTCC scripts/dtc/libfdt/fdt_sw.o
HOSTCC scripts/dtc/libfdt/fdt_rw.o
HOSTCC scripts/dtc/libfdt/fdt_strerror.o
HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o
HOSTCC scripts/dtc/libfdt/fdt_addresses.o
HOSTCC scripts/dtc/libfdt/fdt_overlay.o
HOSTCC scripts/dtc/fdtoverlay.o
HOSTLD scripts/dtc/fdtoverlay
HOSTCC scripts/genksyms/genksyms.o
HOSTCC scripts/genksyms/parse.tab.o
HOSTCC scripts/genksyms/lex.lex.o
HOSTLD scripts/genksyms/genksyms
HOSTCC scripts/kallsyms
HOSTCC scripts/sorttable
HOSTCC scripts/asn1_compiler
UPD include/generated/compile.h
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/modpost.o
CC scripts/mod/devicetable-offsets.s
UPD scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
scripts/Makefile.build:425: warning: overriding recipe for target 'built-in.a'
Makefile:1259: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:440: warning: overriding recipe for target 'modules.order'
Makefile:1923: warning: ignoring old recipe for target 'modules.order'
scripts/Makefile.build:425: warning: overriding recipe for target 'built-in.a'
Makefile:1259: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:440: warning: overriding recipe for target 'modules.order'
Makefile:1923: warning: ignoring old recipe for target 'modules.order'
scripts/Makefile.build:425: warning: overriding recipe for target 'built-in.a'
Makefile:1259: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:440: warning: overriding recipe for target 'modules.order'
Makefile:1923: warning: ignoring old recipe for target 'modules.order'
scripts/Makefile.build:425: warning: overriding recipe for target 'built-in.a'
Makefile:1259: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:440: warning: overriding recipe for target 'modules.order'
Makefile:1923: warning: ignoring old recipe for target 'modules.order'
^Cmake[4]: *** [Makefile:1307: asm-generic] Interrupt
Interrupt
make[3]: *** [Makefile:1289: prepare0] Interrupt
make[2]: *** [Makefile:1289: prepare0] Interrupt
make[1]: *** [Makefile:1289: prepare0] Interrupt
make: *** [Makefile:1289: prepare0] Interrupt
```
However, `^C`ing out of that and re-running it succeeds, because `fixdep` and `modpost` were build before the infinite loop:
```
# xbps-reconfigure -f rpi-kernel
rpi-kernel: configuring ...
Executing post-install kernel hook: 10-dkms ...
rpi-kernel: configured successfully.
```
And dkms works after that:
```
Building DKMS module 'rtl8821cu-5.12.0.4' for kernel-6.1.54_1... done.
Installing DKMS module 'rtl8821cu-5.12.0.4' for kernel-6.1.54_1... done.
rtl8821cu-dkms-20210916_2: installed successfully.
```
So the issue left to figure out is: why does it infinite loop?
prev parent reply other threads:[~2023-09-30 2:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:34 [PR PATCH] rpi-kernel: update to 6.1.54 classabbyamp
2023-09-20 12:35 ` rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland) r-ricci
2023-09-20 13:36 ` tsjk
2023-09-20 13:37 ` tsjk
2023-09-20 16:41 ` classabbyamp
2023-09-23 19:03 ` moabeat-berlin
2023-09-23 19:12 ` classabbyamp
2023-09-23 19:28 ` moabeat-berlin
2023-09-23 19:29 ` moabeat-berlin
2023-09-23 23:11 ` [PR PATCH] [Updated] " classabbyamp
2023-09-23 23:12 ` classabbyamp
2023-09-23 23:13 ` classabbyamp
2023-09-23 23:15 ` classabbyamp
2023-09-23 23:28 ` moabeat-berlin
2023-09-23 23:29 ` moabeat-berlin
2023-09-23 23:59 ` classabbyamp
2023-09-24 0:20 ` moabeat-berlin
2023-09-24 0:21 ` moabeat-berlin
2023-09-24 17:53 ` tsjk
2023-09-24 17:54 ` tsjk
2023-09-24 17:54 ` tsjk
2023-09-24 19:53 ` tsjk
2023-09-25 6:33 ` [PR PATCH] [Updated] " classabbyamp
2023-09-25 6:40 ` classabbyamp
2023-09-25 8:44 ` tsjk
2023-09-25 8:45 ` tsjk
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:37 ` tsjk
2023-09-29 18:40 ` classabbyamp
2023-09-29 18:41 ` tsjk
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:05 ` classabbyamp
2023-09-29 19:37 ` [PR PATCH] [Updated] " classabbyamp
2023-09-29 20:57 ` moabeat-berlin
2023-09-29 21:09 ` classabbyamp
2023-09-29 21:18 ` classabbyamp
2023-09-29 21:24 ` [PR PATCH] [Updated] " classabbyamp
2023-09-29 22:01 ` rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland, rpi-eeprom) classabbyamp
2023-09-30 2:41 ` classabbyamp [this message]
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=20230930024126.kNWtDiwlKfO5EIW1oIDlNUGiL8yl89FQvLzqZCDsKyI@z \
--to=classabbyamp@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).