Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] "depmod: WARNING" after kmod update
@ 2022-07-30 10:20 Haagen-Dazs
  2022-07-30 13:36 ` Haagen-Dazs
                   ` (17 more replies)
  0 siblings, 18 replies; 19+ messages in thread
From: Haagen-Dazs @ 2022-07-30 10:20 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

New issue by Haagen-Dazs on void-packages repository

https://github.com/void-linux/void-packages/issues/38367

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.14_1 x86_64 AuthenticAMD uptodate FFF

### Package(s) Affected

kmod-30_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://groups.google.com/g/linux.debian.bugs.dist/c/7hZiQYDXaiI

### Expected behaviour

No errors given after `sudo xbps-reconfigure -fa`

### Actual behaviour

depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/dracut.../initramfs/lib/modules/5.18.14_1: No such file or directory

### Steps to reproduce

`sudo xbps-install -Su`
`sudo xbps-reconfigure -fa`

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
@ 2022-07-30 13:36 ` Haagen-Dazs
  2022-08-05 17:52 ` TeusLollo
                   ` (16 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: Haagen-Dazs @ 2022-07-30 13:36 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 464 bytes --]

New comment by Haagen-Dazs on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1200159317

Comment:
Latest dracut v.056 seems to have this covered, not tested though:

dracut-init.sh line 1001:

`dracut_kernel_post() {
    for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do
        [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f"
    done`

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
  2022-07-30 13:36 ` Haagen-Dazs
@ 2022-08-05 17:52 ` TeusLollo
  2022-08-05 17:54 ` TeusLollo
                   ` (15 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-05 17:52 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1206703895

Comment:
Could have sworn it was me causing this due to messing with the /etc/modprobe.d/ directory, but it appears not. Here's my output:

```
linux5.15-5.15.59_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: vhba-module-20211218.
Building DKMS module: vhba-module-20211218... done.
Installing DKMS module: vhba-module-20211218... done.
Executing post-install kernel hook: 20-dracut ...
depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/dracut.FBnZ1r/initramfs/lib/modules/5.15.59_1: No such file or directory
Mode:                     real
Method:                   sha256
Files:                    2380
Linked:                   190 files
Compared:                 0 xattrs
Compared:                 3398 files
Saved:                    17.43 MiB
Duration:                 0.231233 seconds
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.59_1
Found initrd image: /boot/initramfs-5.15.59_1.img
Found linux image: /boot/vmlinuz-5.15.57_1
Found initrd image: /boot/initramfs-5.15.57_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
linux5.15-5.15.59_1: updated successfully.
linux5.15-headers-5.15.59_1: configuring ...
linux5.15-headers-5.15.59_1: updated successfully.
```

Using the following packages:
```
dracut-053_2
kmod-30_1
```
This output was generated circa 24 hours ago. 
Feel free to delete this if it's not relevant anymore

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
  2022-07-30 13:36 ` Haagen-Dazs
  2022-08-05 17:52 ` TeusLollo
@ 2022-08-05 17:54 ` TeusLollo
  2022-08-05 17:54 ` TeusLollo
                   ` (14 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-05 17:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1206703895

Comment:
Could have sworn it was me causing this due to messing with the /etc/modprobe.d/ directory, but it appears not. Here's my output when I update to package _linux5.15-5.15.59__1:

```
linux5.15-5.15.59_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: vhba-module-20211218.
Building DKMS module: vhba-module-20211218... done.
Installing DKMS module: vhba-module-20211218... done.
Executing post-install kernel hook: 20-dracut ...
depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/dracut.FBnZ1r/initramfs/lib/modules/5.15.59_1: No such file or directory
Mode:                     real
Method:                   sha256
Files:                    2380
Linked:                   190 files
Compared:                 0 xattrs
Compared:                 3398 files
Saved:                    17.43 MiB
Duration:                 0.231233 seconds
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.59_1
Found initrd image: /boot/initramfs-5.15.59_1.img
Found linux image: /boot/vmlinuz-5.15.57_1
Found initrd image: /boot/initramfs-5.15.57_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
linux5.15-5.15.59_1: updated successfully.
linux5.15-headers-5.15.59_1: configuring ...
linux5.15-headers-5.15.59_1: updated successfully.
```

Using the following packages:
```
dracut-053_2
kmod-30_1
```
This output was generated circa 24 hours ago. 
Feel free to delete this if it's not relevant anymore

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (2 preceding siblings ...)
  2022-08-05 17:54 ` TeusLollo
@ 2022-08-05 17:54 ` TeusLollo
  2022-08-05 17:54 ` TeusLollo
                   ` (13 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-05 17:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1206703895

Comment:
Could have sworn it was me causing this due to messing with the /etc/modprobe.d/ directory, but it appears not. Here's my output when I update to package _linux5.15-5.15.59_1_:

```
linux5.15-5.15.59_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: vhba-module-20211218.
Building DKMS module: vhba-module-20211218... done.
Installing DKMS module: vhba-module-20211218... done.
Executing post-install kernel hook: 20-dracut ...
depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/dracut.FBnZ1r/initramfs/lib/modules/5.15.59_1: No such file or directory
Mode:                     real
Method:                   sha256
Files:                    2380
Linked:                   190 files
Compared:                 0 xattrs
Compared:                 3398 files
Saved:                    17.43 MiB
Duration:                 0.231233 seconds
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.59_1
Found initrd image: /boot/initramfs-5.15.59_1.img
Found linux image: /boot/vmlinuz-5.15.57_1
Found initrd image: /boot/initramfs-5.15.57_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
linux5.15-5.15.59_1: updated successfully.
linux5.15-headers-5.15.59_1: configuring ...
linux5.15-headers-5.15.59_1: updated successfully.
```

Using the following packages:
```
dracut-053_2
kmod-30_1
```
This output was generated circa 24 hours ago. 
Feel free to delete this if it's not relevant anymore

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (3 preceding siblings ...)
  2022-08-05 17:54 ` TeusLollo
@ 2022-08-05 17:54 ` TeusLollo
  2022-08-07  2:13 ` Haagen-Dazs
                   ` (12 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-05 17:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1206703895

Comment:
Could have sworn it was me causing this due to messing with the /etc/modprobe.d/ directory, but it appears not. Here's my output when I updated to package _linux5.15-5.15.59_1_:

```
linux5.15-5.15.59_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: vhba-module-20211218.
Building DKMS module: vhba-module-20211218... done.
Installing DKMS module: vhba-module-20211218... done.
Executing post-install kernel hook: 20-dracut ...
depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/dracut.FBnZ1r/initramfs/lib/modules/5.15.59_1: No such file or directory
Mode:                     real
Method:                   sha256
Files:                    2380
Linked:                   190 files
Compared:                 0 xattrs
Compared:                 3398 files
Saved:                    17.43 MiB
Duration:                 0.231233 seconds
Executing post-install kernel hook: 50-efibootmgr ...
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.59_1
Found initrd image: /boot/initramfs-5.15.59_1.img
Found linux image: /boot/vmlinuz-5.15.57_1
Found initrd image: /boot/initramfs-5.15.57_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
linux5.15-5.15.59_1: updated successfully.
linux5.15-headers-5.15.59_1: configuring ...
linux5.15-headers-5.15.59_1: updated successfully.
```

Using the following packages:
```
dracut-053_2
kmod-30_1
```
This output was generated circa 24 hours ago. 
Feel free to delete this if it's not relevant anymore

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (4 preceding siblings ...)
  2022-08-05 17:54 ` TeusLollo
@ 2022-08-07  2:13 ` Haagen-Dazs
  2022-08-07 17:52 ` TeusLollo
                   ` (11 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: Haagen-Dazs @ 2022-08-07  2:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

New comment by Haagen-Dazs on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207315757

Comment:
> This output was generated circa 24 hours ago. Feel free to delete this if it's not relevant anymore

It is still relevant, dracut is still not patched for the kmod update.
[mkinitcpio](https://github.com/void-linux/void-packages/commit/ff39c912d412717d17232de9564f659b037e95b5) is already patched though.

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (5 preceding siblings ...)
  2022-08-07  2:13 ` Haagen-Dazs
@ 2022-08-07 17:52 ` TeusLollo
  2022-08-07 17:52 ` TeusLollo
                   ` (10 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-07 17:52 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207455824

Comment:
I guess the _needs-testing_ label could be removed then, since there's at least two users with this problem. 

Honestly, I hope Void devs could eventually join forces with Alpine/Devuan/Gentoo devs and maintain mkinitcpio together, since dracut is going deeper into systemd hard-requirements. 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (6 preceding siblings ...)
  2022-08-07 17:52 ` TeusLollo
@ 2022-08-07 17:52 ` TeusLollo
  2022-08-07 17:58 ` TeusLollo
                   ` (9 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-07 17:52 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207455824

Comment:
I guess the _needs-testing_ label could be removed then, since there's at least two users with this problem. 

Honestly, I hope Void devs could eventually join forces with Alpine/Devuan/Gentoo devs and maintain mkinitcpio together, since dracut is going deeper into systemd hard-requirements. 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (7 preceding siblings ...)
  2022-08-07 17:52 ` TeusLollo
@ 2022-08-07 17:58 ` TeusLollo
  2022-08-07 20:51 ` Haagen-Dazs
                   ` (8 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-07 17:58 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207455824

Comment:
I guess the _needs-testing_ label could be removed then, since there's at least two users with this problem (I guess that is the practice around here, correct me if I'm wrong). 

Honestly, I hope Void devs could eventually join forces with Alpine/Devuan/Gentoo devs and maintain mkinitcpio together, since dracut is going deeper into systemd hard-requirements. 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (8 preceding siblings ...)
  2022-08-07 17:58 ` TeusLollo
@ 2022-08-07 20:51 ` Haagen-Dazs
  2022-08-08  1:34 ` ahesford
                   ` (7 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: Haagen-Dazs @ 2022-08-07 20:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]

New comment by Haagen-Dazs on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207483364

Comment:
> Honestly, I hope Void devs could eventually join forces with Alpine/Devuan/Gentoo devs and maintain mkinitcpio together, since dracut is going deeper into systemd hard-requirements.

[Booster](https://github.com/void-linux/void-packages/pull/29434) is also a great alternative written in Go, I personally use it on Arch and so far I did not have any issues with it.


^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (9 preceding siblings ...)
  2022-08-07 20:51 ` Haagen-Dazs
@ 2022-08-08  1:34 ` ahesford
  2022-08-08  9:12 ` TeusLollo
                   ` (6 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: ahesford @ 2022-08-08  1:34 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207553705

Comment:
1. `mkinitcpio` is an Arch project and works fine with Void as is. I personally use `mkinitcpio` on most of my systems, even as the foundation of my ZFSBootMenu images, and have a vested interest in making sure it stays that way. But there's no need to attempt to take ownership over from Arch.
2. Has anybody shown that this warning actually indicates a problem with the initramfs image? It says "WARNING" right in the text, and even before I pulled the `mkinitcpio` patch from upstream, I confirmed that expected kernel modules made their way into initramfs images.
3. Somebody is welcome to PR a backport of the fix to our current dracut pending a full update. (It won't be me because I no longer have installations that will let me meaningfully test the patch.) Otherwise, as I noted when closing an untested PR to bump the dracut package, a full update requires more extensive testing and will hopefully be done once a core member finds some time and interest to take up the matter. (Documenting that this causes a real problem beyond spitting out some warnings will almost certainly increase the sense of urgency there.)

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (10 preceding siblings ...)
  2022-08-08  1:34 ` ahesford
@ 2022-08-08  9:12 ` TeusLollo
  2022-08-12 13:29 ` MaMiMa81
                   ` (5 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-08  9:12 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1207867875

Comment:
1. I was not suggesting a "takeover", at best a fork. In previous months, although I can't find a link anymore, one of the Void devs was saying that `mkinitcpio` was under-maintained, thus Arch devs were planning to switch fully to `dracut`, which however is going deeper into systemd hard-dependencies. That's obviously concerning for Void Linux, and I had never heard of `booster`.
2. Even then, sometimes `dracut`, at least on certain of my systems, fails loading the `intel_pstate` driver, although it's totally random and can't be replicated. This never happened when I used Arch with `mkinitcpio`, hence I assumed it was further proof of `dracut` ditching non-systemd support. 
3. Hell, I thought `mkinitcpio` on Void was somewhat of an _experimental/it's your problem_ approach, but it seems I was wrong and it's fully supported instead. I may actually try it. 
4. Or I may go with the new boy in town, `booster`

I just wanted to remark that I was not suggesting any "takeoverist" approach. I was just wishing for developers not to depend upon software that appears to be hostile towards non-systemd approaches. Hell, the whole `eudev` story is similar, so I was just presuming eventually a similar joint-effort approach would appear for inittramfs generators, which may not be necessary anymore with the arrival of the new boy in town, `booster`.

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (11 preceding siblings ...)
  2022-08-08  9:12 ` TeusLollo
@ 2022-08-12 13:29 ` MaMiMa81
  2022-08-12 13:30 ` MaMiMa81
                   ` (4 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: MaMiMa81 @ 2022-08-12 13:29 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - espescially as it appears that it is moving to be more systemd centric - plus this will also alleviate demand upon core devs, would not a simple & sensible course
of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely but it forward as a suggestion to try and help.
Regards

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (12 preceding siblings ...)
  2022-08-12 13:29 ` MaMiMa81
@ 2022-08-12 13:30 ` MaMiMa81
  2022-08-12 13:34 ` MaMiMa81
                   ` (3 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: MaMiMa81 @ 2022-08-12 13:30 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - espescially as it appears that it is moving to be more systemd centric - plus this will also alleviate demand upon core devs, would not a simple & sensible course of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely but it forward as a suggestion to try and help.
Regards

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (13 preceding siblings ...)
  2022-08-12 13:30 ` MaMiMa81
@ 2022-08-12 13:34 ` MaMiMa81
  2022-08-12 14:45 ` MaMiMa81
                   ` (2 subsequent siblings)
  17 siblings, 0 replies; 19+ messages in thread
From: MaMiMa81 @ 2022-08-12 13:34 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
Regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - espescially as it appears that it is moving to be more systemd centric - plus this will also put more demand upon core devs, would not a simple & sensible course of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely put it forward as a suggestion to try and help.
Regards

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (14 preceding siblings ...)
  2022-08-12 13:34 ` MaMiMa81
@ 2022-08-12 14:45 ` MaMiMa81
  2022-08-12 14:56 ` MaMiMa81
  2022-08-12 16:24 ` TeusLollo
  17 siblings, 0 replies; 19+ messages in thread
From: MaMiMa81 @ 2022-08-12 14:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
Regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - espescially as it appears that it is moving to be more systemd centric - plus this will also put more demand upon core devs, would not a simple & sensible course of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely put it forward as a suggestion to try and help.

Also regarding @ahesford:

>     3. ........ (Documenting that this causes a real problem beyond spitting out some warnings will almost certainly increase the sense of urgency there.)


See here:

[https://groups.google.com/g/linux.debian.bugs.dist/c/7hZiQYDXaiI](url)


#Michael Biebl
unread,
Jul 7, 2022, 11:40:03 AM
to

Control: severity -1 important

On Mon, 04 Jul 2022 15:01:13 +1000 Konomi Kitten
<konomi...@gmail.com> wrote:
> Package: initramfs-tools
> Version: 0.141
> Severity: minor
> X-Debbugs-Cc: konomi...@gmail.com
>
> When update-initramfs runs I receive the following message:
>
> depmod: WARNING: could not open modules.builtin.modinfo at
> /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
> directory


Unfortunately this is not a minor issue, as it breaks the autopkgtest
suite of initramfs-tools and thus prevents kmod from entering testing
(and dependent packages like systemd [1] as well).

It would thus be great to have the patch in [2] applied and uploaded
soon. I can offer to NMU if available time is an issue.

Regards,
Michael 


So it is probably of some importance that this is attended to.
Incidently I have currently downgraded to kmod v.29 as alluded to in that linked bug report.



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (15 preceding siblings ...)
  2022-08-12 14:45 ` MaMiMa81
@ 2022-08-12 14:56 ` MaMiMa81
  2022-08-12 16:24 ` TeusLollo
  17 siblings, 0 replies; 19+ messages in thread
From: MaMiMa81 @ 2022-08-12 14:56 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2917 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
Regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - especially as it appears that it is moving to be more systemd centric - plus this will also put more demand upon core devs, would not a simple & sensible course of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely put it forward as a suggestion to try and help.

Also regarding @ahesford:

>     3. ........ (Documenting that this causes a real problem beyond spitting out some warnings will almost certainly increase the sense of urgency there.)


See here:

[https://groups.google.com/g/linux.debian.bugs.dist/c/7hZiQYDXaiI](url)


#Michael Biebl
unread,
Jul 7, 2022, 11:40:03 AM
to

Control: severity -1 important

On Mon, 04 Jul 2022 15:01:13 +1000 Konomi Kitten
<konomi...@gmail.com> wrote:
> Package: initramfs-tools
> Version: 0.141
> Severity: minor
> X-Debbugs-Cc: konomi...@gmail.com
>
> When update-initramfs runs I receive the following message:
>
> depmod: WARNING: could not open modules.builtin.modinfo at
> /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
> directory


Unfortunately this is not a minor issue, as it breaks the autopkgtest
suite of initramfs-tools and thus prevents kmod from entering testing
(and dependent packages like systemd [1] as well).

It would thus be great to have the patch in [2] applied and uploaded
soon. I can offer to NMU if available time is an issue.

Regards,
Michael 


So it is probably of some importance that this is attended to.
Incidently I have currently downgraded to kmod v.29 as alluded to in that linked bug report.



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: "depmod: WARNING" after kmod update
  2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
                   ` (16 preceding siblings ...)
  2022-08-12 14:56 ` MaMiMa81
@ 2022-08-12 16:24 ` TeusLollo
  17 siblings, 0 replies; 19+ messages in thread
From: TeusLollo @ 2022-08-12 16:24 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2978 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213297831

Comment:
I'm going to leave the following as MY OWN PERSONAL OPINIONS and SUGGESTIONS:

1. It was always known that `dracut`was growing more and more systemd-centric. I recall Void Devs having a discussion on _github_ about it (Which I can't find anymore, it would be useful if someone could eventually link it). Eventually, it was anticipated something would break due to some systemd-based mishap. 

2. Given the current situation, this `dracut` update will require extensive testing, putting a lot of pressure on core devs. However, there's no guarantee a further `dracut` update down the line (Maybe even the next one) will not require another extenuating testing session, further undercutting core dev development time which could be spent anywhere else, assuming also that next version `dracut` won't be systemd-only at all, knowing also how much of a moving target systemd is. 

3. At this point, since `mkinitcpio` does not seem under-maintained anymore, and since the new `booster`, although not as minimalist as `mkinitcpio`, seems also to work reasonably well, I would say to just jump ship, and prepare to switch to a `mkinitcpio` configuration by default for Void Linux, with `booster`as supported yet experimental (It still has some maturing to do, it's very recent), and `dracut` as unsupported due to excessive systemd dependencies.  

4. To me, gradually dropping `dracut` in favor of alternatives will eventually become necessary anyway due to systemd woes, and this would be a reasonable occasion to jump ship. None will blame Void Devs, since it's known how `dracut` has grown to become increasingly unresponsive to non-systemd approaches. Also, even should eventually `mkinitcpio` be dropped by its original author/maintainer, it wouldn't be catastrophically difficult to perform some maintenance along with Alpine/Gentoo/Devuan devs, even if Arch too abandons `mkinitcpio`. Furthermore, the maturing `booster` would also provide a further safety net, if not as minimalist. 

I would say thus to minimize chances of potentially wasting time, efforts, and energy into something that tomorrow may very well grow into yet another systemd (Sarcasm MODE ON) "non-monolithic binary" (Sarcasm MODE OFF), and concentrate efforts into `mkinitcpio` and `booster`. In fact, it probably has not been this favorable switching to less conventional initramfs for Linux Distros in quite a few years, if not decades, thus I would say to just jump ship. 

In every case, I would like to thank both Void Devs and the entire Void Community for devoting their time and efforts into something excellent which has earned to only rely on the best. 

Now, it would be useful if one of the Core Devs could chime in, possibly. 
Thanks for reading, and remember: the aforementioned are just MY OWN PERSONAL OPINIONS and SUGGESTIONS. 

^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2022-08-12 16:24 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-30 10:20 [ISSUE] "depmod: WARNING" after kmod update Haagen-Dazs
2022-07-30 13:36 ` Haagen-Dazs
2022-08-05 17:52 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-07  2:13 ` Haagen-Dazs
2022-08-07 17:52 ` TeusLollo
2022-08-07 17:52 ` TeusLollo
2022-08-07 17:58 ` TeusLollo
2022-08-07 20:51 ` Haagen-Dazs
2022-08-08  1:34 ` ahesford
2022-08-08  9:12 ` TeusLollo
2022-08-12 13:29 ` MaMiMa81
2022-08-12 13:30 ` MaMiMa81
2022-08-12 13:34 ` MaMiMa81
2022-08-12 14:45 ` MaMiMa81
2022-08-12 14:56 ` MaMiMa81
2022-08-12 16:24 ` TeusLollo

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).