Edit: I must have missed something while scanning through the logs. In dbus.log I get
dbus-daemon[1590]: Activated service 'org.fedoraproject.Anaconda.Modules.Network' failed: Process org.fedoraproject.Anaconda.Modules.Network exited with status 1
dbus-daemon[1590]: Reloaded configuration
I haven’t found any fixes when researching this yet.
Edit again: There’s no anaconda-ks.cfg around anywhere, I’m not sure if that’s an issue or not.
Hello,
I admit I’m new to Silverblue. Anaconda seems to start properly:
Starting installer, one moment...
anaconda 29.24.3-1.fc29 for Fedora 29 (pre-release) started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* when reporting a bug add logs from /tmp as separate text/plain attachments
On the log tab I get lots of these:
INF startup_utils: Waiting 600 sec for modules to be started.
INF startup_utils: Waiting 599 sec for modules to be started.
INF startup_utils: Waiting 598 sec for modules to be started.
and so on until it times out:
Anaconda DBus modules failed to start on time.
The odd thing is, I don’t time out when using the exact same .iso file in a VM.
Possible relevant links are here because I’m not allowed to put all of them in this post.
I doubt it’s because my PC is too slow because if so, then the VM shouldn’t have even become close to working, and also, I don’t think my PC is that bad. I’ve got a Ryzen 3 1300X, 8 GB of RAM… (full list at https://pcpartpicker.com/list/cCxFHh)
Edit: I’ll also look into those other logs. Edit again: It appears that I’m stuck in text mode installation. I boot into tmux and the graphical stuff never even shows up. Most of the logs there seem to be the same as the log files attached above. I am using UEFI, I could try it from BIOS as well.
I recall seeing something like this when a broken version of dbus landed in F29 updates-testing. Since dbus never started, it impacted NetworkManager starting successfully too.
Broadcom drivers are available from the RPMFusion repo. Since you can’t really get the repo without internet access, you can grab the rpm from here, save it to a USB, and install it on the system via rpm-ostree install path-to-broadcom-wl.rpm. Then you can properly add RPMFusion to ensure it stays updated.
Hmm, if you have another working system where you can run Fedora Workstation 29 (the live CD should also work) with networking, you can install RPMFusion and then run dnf download --resolve broadcom-wl to download all the needed rpms into the current directory. Then you can transfer them to the USB and install them all at once (rpm-ostree install *.rpm or similar).
Well, typical wifi adapter. After stubbornly turning it on again, it decided to start working. I’m going to get the drivers installed now with the hopes that it will work next time I boot up.
Hmm, based on that issue, dnf download probably just downloaded too much and rpm-ostree is freaking out over a base package replacement…
Can you:
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.
We seem to have posted at nearly the exact same time. In case you didn’t see it, my wi-fi dongle randomly started working again and I now have internet access on my machine. Should I still continue with the steps you told me or should I just add RPMFusion and install broadcom-wl?
Installing the drivers might make it more reliable, and hopefully it would work the next time I boot up (rather than if I did nothing)…
If it’s working perfectly now, it’s your choice. That being said, you can always try installing RPMFusion (you might end up using this for other stuff anyway) + the broadcom-wl package and see how it goes. Since this is Silverblue, if it makes things worse you can just reboot and select the old deployment.
