im currently using windows 11 on msi gf63 laptop. if i used linux i would use ubuntu,bec it seems like the easiest thing.
i game,i use brave browser,i pirate games and software. i also like that my hoarded pirated binaries of games and software will work even years later on windows without too much effort.
i use an hp printer,and need to be able to use it on linux.
i expect to be able to use the laptop and not think about the os too much,meaning i wont distro hop or try to customize it too much. im fine with the terminal,my goal of using linux is being far from malware.
Hey, first of all welcome. Now, I’ve never used Fedora, but I wanted to give you some answers to your points:
I’m also surprised by this, KDE is very snappy so it shouldn’t feel like that. I have a gut feeling from this and some other things that you might have an Nvidia card, if so which driver are you using? I know the community shits on the proprietary drivers (with reason) but they provide the best experience (except when they don’t).
That’s true, but that’s also true for Windows. One thing we forget is the amount of knowledge we have acquired from years of just using the system. To me, every time I have to use Windows it’s a chore, nothing works out of the box, everything needs some tweaks, I can’t do anything, everything is complicated obtuse and weird. But to you it’s not, because you’re used to it, and since most stuff works and the ones that don’t you are familiar with troubleshooting it feels as if everything works. I feel the same thing happens to us on the Linux side, we say everything works because to us it does (but also you’ve had some issues I have never experienced before).
That is apparently needed to share your screen on certain apps like Discord. From what I read there are reports of people saying this crashes for them and it has to do with them running out of VRAM (which would also account for your computer feeling slower). And apparently there’s a bug in newer Nvidia drivers where there’s a memory leak that could cause this. If you’re using Nvidia proprietary drivers check the version z maybe trying to update to the latest or downgrade to 550 or before it fixes this.
This is because Windows hasn’t powered off in a while, it hibernates. Even when you ask it to power off it doesn’t, this is a known pain point for Linux because Windows doesn’t close NTFS drives properly unless it powers off completely, so you are locked out of your shared drives.
I never tried to use systemd-analyze, but my guess would be that they’re counting the time from when the service starts until it’s done, and most of that time is waiting for hardware or other services, so if you have one service that takes 11 second and 5 services that take 0.1 seconds but depends on your first service they would all say 11 seconds. If you send me the output I can try to read the docs and see what I can come up with, a quick look told me that you can also run
systemd-analyze critical-chain <unit>to get a dependency list which might give you more insight on all those that took 11 seconds.Never had that issue, never heard of Cisco codecs either. You’re correct that this is not newbie friendly, it’s related to why GPU drivers are an issue in some distros. Apparently from the link that you send that is a description on how to switch from an open source implementation to one that depends on the proprietary Nvidia drivers. This is the sort of thing your distro should do automatically when you switch to a proprietary drivers for the GPU, and why I like to recommend certain distros that (at least back when I started) took care to do these things when you selected the proprietary driver.
Yeah, all of my printers have been HP, the most I had to do was install a package for HP (hplip I think it was called) and they have all worked flawlessly.
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.deviceAnd here’s the output of systemd-analyze plot > plot.svg (had to covert to jpg to allow the upload):