you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 8 months ago* (last edited 8 months ago) (1 child)

Thanks for reading through this. No Nvidia card. it's AMD Ryzen 7 CPU with integrated Radeon Vega 10 GPU. 20 GB system memory with 2 GB allocated for the video card. I didn't install anything for graphics, I just let Fedora do its defaults.

I looked up the codecs to get the specifics. This was the first thing I found when having Firefox + YouTube issues: https://docs.fedoraproject.org/en-US/quick-docs/openh264/

Installed that and it wasn't any better. Then had to figure out how to remove it and try the rpmfusion stuff (whatever that is).

Here's the output of systemd-analyze critical-chain:

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @12.832s

└─sddm.service @12.832s

  └─plymouth-quit.service @12.727s +98ms

    └─systemd-user-sessions.service @12.681s +20ms

      └─remote-fs.target @12.659s

        └─remote-fs-pre.target @8.131s

          └─nfs-client.target @8.130s

            └─gssproxy.service @8.044s +85ms

              └─network.target @8.037s

                └─wpa_supplicant.service @8.002s +33ms

                  └─basic.target @4.810s

                    └─dbus-broker.service @4.627s +137ms

                      └─dbus.socket @4.607s +1ms

                        └─sysinit.target @4.596s

                          └─systemd-resolved.service @4.452s +143ms

                            └─systemd-tmpfiles-setup.service @3.827s +613ms

                              └─local-fs.target @3.814s

                                └─boot-efi.mount @3.692s +119ms

                                  └─boot.mount @3.552s +118ms

                                    └─systemd-fsck@dev-disk-by\x2duuid-e61e388b\x2d6938\x2d4f16\x2d9746\x2dce2c084d3f44.service @3.206s +170ms

                                      └─dev-disk-by\x2duuid-e61e388b\x2d6938\x2d4f16\x2d9746\x2dce2c084d3f44.device

And here's the output of systemd-analyze plot > plot.svg (had to covert to jpg to allow the upload):

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 8 months ago

    Sorry, I haven't had time to look at this with calm but:

    remote-fs.target @12.659s

    that one stands out to me, from the name it seems like it's related to networking file shares, which I don't think you need during boot. Also I see wpa_supplicant there, if I'm not mistaken that means that you're waiting for a wireless connection before proceeding. Looking at the other image though it seems your disk is taking a long time to start up, which is weird considering it's

    Both of those might be okay and preferable (for example for a server), but for a laptop I would expect to have networking stack start after graphical so the system feels like it's faster. I imagine those are the default for Fedora and not something you configured, and probably you should not poke on this unless you're okay with reinstalling your system in case you break something (speaking of that for future references you should consider having one partition for / and another for /home, that way you can reinstall or distro hop without affecting your personal files). Good luck.

  • source
  • parent