Unified Kernel Image D-bus issues

plasticbox · 2024-02-03 19:47:50

Hello,
I wanted to create a unified Kernel Image. Since i have no experience with that i first wanted to create an unsigned image by just using dracut

dracut --uefi

and see how it goes (later i would have liked to enable secureboot and create a signed image). That worked fine so far: I'm able to choose the image from my systemd-boot and "finish" the boot process. However during boot i get messages saying

[Failed] Failed to listen  on D-Bus System Message Bus Socket
See "systemctl status dbus.socket" for details
[Depend] Dependency failed for nm-initrd.service
[Depend] Dependency failed for nm-wait-online-initrd.service

I did check systemctl which would tell me dbus.socket is active and running. To be honest i have no clue why i get these messages, what they mean and what's the Problem. I spent 2 hours with searching the internet, checking the Wiki and the forums but haven't found anything to this issue. All i could find was basically just "do that and it should work". Could someone help me out or point me at some direction?

dogknowsnx · 2024-02-03 20:05:52

So what's the actual problem you're experiencing? Can you boot a "regular" initramfs-*.img without those messages? You may want to run this in order to help "us"/@seth to help you debug the error...

Last edited by dogknowsnx (2024-02-03 22:00:48)

plasticbox · 2024-02-03 22:03:07

My actual problem is that i want to figure out why i would get these messages. I guess they are there for a reason and shouldn't just be ignored?
A regular image works without these messages. I ran the script you linked, these are my results:

/usr/share/dbus-1/system.d/org.kde.fontinst.conf - valid
/usr/share/dbus-1/system.d/org.kde.kcontrol.kcmclock.conf - valid
/usr/share/dbus-1/system.d/org.kde.kcontrol.kcmsddm.conf - valid
/usr/share/dbus-1/system.d/org.kde.kded.smart.conf - valid
/usr/share/dbus-1/system.d/org.kde.kinfocenter.dmidecode.conf - valid
/usr/share/dbus-1/system.d/org.kde.ksysguard.processlisthelper.conf - valid
/usr/share/dbus-1/system.d/org.kde.ktexteditor.katetextbuffer.conf - valid
/usr/share/dbus-1/system.d/org.kde.powerdevil.backlighthelper.conf - valid
/usr/share/dbus-1/system.d/org.kde.powerdevil.chargethresholdhelper.conf - valid
/usr/share/dbus-1/system.d/org.kde.powerdevil.discretegpuhelper.conf - valid
/usr/share/dbus-1/system.d/org.kde.ufw.conf - valid
/usr/share/dbus-1/system.d/teamd.conf:5.0: No declaration for attribute own_prefix of element allow
/usr/share/dbus-1/system.d/teamd.conf:9.0: No declaration for attribute own_prefix of element deny
 -------
45 of 45 look ok to me

dogknowsnx · 2024-02-03 22:25:19

https://wiki.archlinux.org/title/Dracut … ated_image

plasticbox · 2024-02-04 12:10:54

Ty, i checked the image though i'm not sure what i should look for. There are no Errors that jump right into my face... just a very long list folder and links. Under modules i see the dbus-broker and dbus listed so i guess it "should" work?

dracut modules:
bash
systemd
systemd-initrd
systemd-sysusers
modsign
dbus-broker
dbus
i18n
network-manager
network
btrfs
crypt
dm
kernel-modules
kernel-modules-extra
kernel-network-modules
lvm
mdraid
nvdimm
qemu
qemu-net
cifs
lunmask
resume
rootfs-block
terminfo
udev-rules
virtiofs
dracut-systemd
usrmount
base
fs-lib
shutdown

dogknowsnx · 2024-02-04 12:23:51

plasticbox wrote:

Ty, i checked the image though i'm not sure what i should look for.

That's why it's always recommended to post the full output/logs - you can use a pastebin service for large output and post the link here...

swsnr · 2024-02-04 13:39:03

Do you need networking in early boot? If not you could just disable the "network-manager", "dbus", and "dbus-broker" modules in your dracut configuration.

By "regular image", do you mean an initramfs generated with mkinitcpio, or a an initramfs generated by dracut without "--uefi"? If it's the former, I'd just like point out that you don't need dracut to build a UKI; recent versions of mkinitcpio can do so too.

Last edited by swsnr (2024-02-04 13:39:53)

dogknowsnx · 2024-02-04 14:05:52

swsnr wrote:

Do you need networking in early boot?

dogknowsnx wrote:

So what's the actual problem you're experiencing?

plasticbox wrote:

My actual problem is that i want to figure out why i would get these messages.

¯\_(ツ)_/¯

plasticbox · 2024-02-04 14:27:42

Actually the final goal was to get a unified kernel image that i would be able to use with secure boot enabled. Since i'm not that experienced i thought the easiest way might be by using dracut for this since it read pretty straight forward by reading the Arch Wiki. So i didn't do much besides just running dracut --uefi. If that would have worked i would have tried to then create a signed image. Yet it seems like i already had Problems just creating a unsigned image. By generating a regular initramfs i mean't dracut without "--uefi".
I didn't know i just can disable these moduls. So i might just try that.
However here's the complete pastebin https://pastebin.com/0aQqaebp

**EDIT**
Long story shot, i just used mkinitcpio and got it working first try after realizing i wasn't even able to boot the dracut generated .efi without systemd-boot (would get stuck at /dev/gpt-auto-root although root was already included in the image.. i had to add it to efibootmngr then it would work... but that makes kernel parameters kinda annoying). Don't know what the culprit was..

Last edited by plasticbox (2024-02-04 21:36:05)

Arch Linux

#1 2024-02-03 19:47:50

Unified Kernel Image D-bus issues

#2 2024-02-03 20:05:52

Re: Unified Kernel Image D-bus issues

#3 2024-02-03 22:03:07

Re: Unified Kernel Image D-bus issues

#4 2024-02-03 22:25:19

Re: Unified Kernel Image D-bus issues

#5 2024-02-04 12:10:54

Re: Unified Kernel Image D-bus issues

#6 2024-02-04 12:23:51

Re: Unified Kernel Image D-bus issues

#7 2024-02-04 13:39:03

Re: Unified Kernel Image D-bus issues

#8 2024-02-04 14:05:52

Re: Unified Kernel Image D-bus issues

#9 2024-02-04 14:27:42

Re: Unified Kernel Image D-bus issues

Board footer