[logs now available] Anaconda DBus modules fail to start on time


Last night, the wi-fi adapter stopped working again. I tried my other wifi adapter and that didn’t work either.

In addition, I ran rpm-ostree ex livefs and now rpm-ostree times out whenever I try to do anything with it. Why did I think it was a good idea to try experimental features when I hadn’t even got the drivers installed yet? :laughing:

I tried gabx’s solution of booting a different option at the boot menu, but it only led to a barebones bash setup.

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

I wasn’t able to transfer the logs to a USB, I didn’t see anything in /dev/sd* when I plugged it in (is it somewhere else?).

I looked at /run/initramfs/rdsosreport.txt and it seems that it can’t switch root.

Failed to switch root: Specified switch path '/sysroot' does not seem to be an OS tree. os-release file is missing.

I really wish I could put the full logs here. journalctl indicates that “OSTree Prepare OS/” is failing as well as Switch Root.

Who knows how long it will take to get this other option to work? I’m wondering if it might be a better idea to wipe everything and reinstall Silverblue.


Unfortunately, rpm-ostree ex livefs is currently considered :warning: dangerous :warning: (as you mentioned, it was already marked experimental previously). In the latest release this is made even more explicit: https://github.com/projectatomic/rpm-ostree/pull/1622.

You can see if this might help: https://github.com/ostreedev/ostree/issues/1459#issuecomment-433675430.


Yeah, rpm-ostree ex livefs is definitely the equivalent of hitting your computer with a hammer and hoping it works… As @jlebon mentioned, removing old boot entries should help (I’ve done this successfully before).

Out of curiosity: did you try livefs to work around the reboot for RPMFusion to activate?


Thank you very much @jlebon, removing the old boot entry worked.

No, I was installing various things that I wanted such as Python, and I was scared of rebooting because I might lose my wi-fi access (which happened anyway).

So supposedly if the wifi dongle decides to start working just one more time, I can install broadcom-wl and everything will be usable.

Edit: I have no idea what I did to get it working the first time. I just kept turning it on and waiting, and one of the times it said “Connected”. lol


Earlier, when rpm-ostree wasn’t working when you tried installing the deps manually, I had mentioned:

  • Show the file names of the packages that are being installed. I can see if there’s anything in the Silverblue base image.
  • Run journalctl -u rpm-ostreed -b immediately after the error occurs, which should show all the logs from rpm-ostreed in the current boot, and upload the output.

Could you maybe try that if you can’t get this working?




No problem. :grin:


Hmm, these logs came after the “connection is closed” error?


Yes, I ran journalctl after the error.

Edit: It’s possible that I accidentally ran it a bit before, I can do it again if you’d like.


Can you, just to make sure? It just seems odd that there were absolutely no errors or the like in the logs…



How on earth did that happen? I came back to the computer and saw that wifi was working…

Anyway, I figured I’d install broadcom-wl before the time ran out. rpm-ostree runs for a while and then gets this error:

Resolving dependencies... Forbidden base package replacements:
  rpm-libs -> (updates)
  rpm-plugin-selinux -> (updates)
  rpm -> (updates)
error: Some base packages would be replaced

It looks like rpm-ostree is scared to replace base packages. Is there some option I can run to force the installation?

Edit: NVM, updgrading fixed it. Supposedly the broadcom drivers are installed now, although I’m terrified of rebooting…


Well, I rebooted and the drivers don’t seem to have done anything. Wi-fi is once again a thing of the past…



Can you give me:

  • The exact name of the WiFi adapter?
  • The output of journalctl -u NetworkManager -b?


I bought the wifi adapter here:

So I guess it’s the “Edimax EW-7811Un”

And here is the journalctl output:



I believe NetworkManager is taking up a lot of system resources, because when I log in it’s very slow. The GNOME settings app takes a long time to open up (if it does).

My computer had been in an idle state for several hours when the wifi started working (both times).

Edit: It’s working again. No idea why it’s so unreliable.


That’s…not a Broadcom chip…at all…

Can you try editing /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf and set wifi.powersave to 2, then run systemctl restart NetworkManager? If that doesn’t work, can you post the output of lsmod?


I thought Broadcom made the chip and Edimax made the plastic that surrounded it…similar to the way that Nvidia makes a GTX 2080 chip but MSI will make a graphics card that uses it. :thinking:
But whatever, I’ll give it a shot. I don’t really know anything about this lol

The directory /etc/NetworkManager/conf.d is empty.

Module                  Size  Used by
uas                    28672  0
usb_storage            69632  1 uas
binfmt_misc            20480  1
btrfs                1380352  0
xor                    24576  1 btrfs
zstd_compress         180224  1 btrfs
raid6_pq              122880  1 btrfs
zstd_decompress        81920  1 btrfs
xxhash                 16384  2 zstd_compress,zstd_decompress
ufs                    90112  0
hfsplus               114688  0
hfs                    69632  0
minix                  40960  0
vfat                   24576  0
msdos                  20480  0
fat                    77824  2 msdos,vfat
jfs                   212992  0
xfs                  1609728  0
fuse                  122880  5
nf_conntrack_netbios_ns    16384  1
nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
xt_CT                  16384  1
rfcomm                 86016  0
ip6t_rpfilter          16384  1
ip6t_REJECT            16384  2
nf_reject_ipv6         16384  1 ip6t_REJECT
xt_conntrack           16384  19
ebtable_nat            16384  1
ip6table_nat           16384  1
nf_conntrack_ipv6      16384  11
nf_defrag_ipv6         20480  1 nf_conntrack_ipv6
nf_nat_ipv6            16384  1 ip6table_nat
ip6table_mangle        16384  1
ip6table_raw           16384  1
ip6table_security      16384  1
iptable_nat            16384  1
nf_conntrack_ipv4      16384  11
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_nat_ipv4            16384  1 iptable_nat
nf_nat                 36864  2 nf_nat_ipv6,nf_nat_ipv4
iptable_mangle         16384  1
iptable_raw            16384  1
iptable_security       16384  1
nf_conntrack          147456  9 xt_conntrack,nf_conntrack_ipv6,nf_conntrack_ipv4,nf_nat,nf_nat_ipv6,nf_conntrack_netbios_ns,nf_nat_ipv4,nf_conntrack_broadcast,xt_CT
libcrc32c              16384  4 nf_conntrack,nf_nat,btrfs,xfs
ip_set                 45056  0
nfnetlink              16384  1 ip_set
ebtable_filter         16384  1
ebtables               36864  2 ebtable_nat,ebtable_filter
ip6table_filter        16384  1
ip6_tables             32768  7 ip6table_filter,ip6table_raw,ip6table_nat,ip6table_mangle,ip6table_security
cmac                   16384  1
bnep                   24576  2
sunrpc                430080  1
rtl8xxxu              135168  0
arc4                   16384  2
snd_hda_codec_hdmi     57344  1
rtl8192cu              81920  0
rtl_usb                24576  1 rtl8192cu
rtl8192c_common        61440  1 rtl8192cu
rtlwifi                98304  3 rtl8192c_common,rtl_usb,rtl8192cu
snd_hda_codec_realtek   110592  1
snd_hda_codec_generic    86016  1 snd_hda_codec_realtek
edac_mce_amd           28672  0
mac80211              913408  4 rtl_usb,rtl8192cu,rtlwifi,rtl8xxxu
snd_hda_intel          45056  6
snd_hda_codec         151552  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
ppdev                  20480  0
snd_hda_core           94208  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
kvm                   737280  0
snd_hwdep              16384  1 snd_hda_codec
snd_seq                81920  0
snd_seq_device         16384  1 snd_seq
snd_pcm               114688  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
btusb                  53248  0
btrtl                  16384  1 btusb
irqbypass              16384  1 kvm
btbcm                  16384  1 btusb
btintel                24576  1 btusb
wmi_bmof               16384  0
bluetooth             598016  31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
cfg80211              778240  2 rtlwifi,mac80211
sp5100_tco             16384  0
i2c_piix4              24576  0
k10temp                16384  0
snd_timer              36864  2 snd_seq,snd_pcm
snd                    94208  22 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
r8169                  90112  0
soundcore              16384  1 snd
mii                    16384  1 r8169
joydev                 24576  0
ecdh_generic           24576  2 bluetooth
rfkill                 28672  7 bluetooth,cfg80211
parport_pc             32768  0
parport                57344  2 parport_pc,ppdev
gpio_amdpt             16384  0
gpio_generic           16384  1 gpio_amdpt
pcc_cpufreq            16384  0
acpi_cpufreq           24576  0
dm_multipath           32768  0
nouveau              2187264  19
mxm_wmi                16384  1 nouveau
video                  45056  1 nouveau
i2c_algo_bit           16384  1 nouveau
drm_kms_helper        196608  1 nouveau
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
crc32c_intel           24576  7
ttm                   126976  1 nouveau
drm                   475136  8 drm_kms_helper,ttm,nouveau
ghash_clmulni_intel    16384  0
ccp                    16384  0
nvme                   36864  2
nvme_core              81920  4 nvme
wmi                    28672  3 wmi_bmof,mxm_wmi,nouveau
pinctrl_amd            28672  0


In that case, can you create default-wifi-powersave-on.conf inside with the contents wifi.powersave = 2?


GNOME Settings says this:

I figured I needed to run systemctl start NetworkManager, which said this:

Job for NetworkManager.service failed because the control process exited with error code.
See "systemctl status NetworkManager.service" and "journalctl -xe" for details.

So I ran those commands and all the logs are in the zip file below.


When looking at the output of journalctl -xe | grep -i network, it seems that default-wifi-powersave-on.conf is messed up in some way (needs a group declaration first?)

Nov 04 07:09:27 localhost.localdomain NetworkManager[1637]: Failed to read configuration: /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf: Key file does not start with a group


Ack, you’re right. The config file should say:

wifi.powersave = 2

Oops… :sweat_smile:


Unfortunately, I don’t think that did much. The settings app is still slowing the entire computer down and it took a very long time to connect again.