NVIDIA-Linux-x86_64-545.29.06

Ask Fedora
,
1

ISSUE
ISSUE

installed NVIDIA-Linux-x86_64-545.29.06.run
but
BOTH
nvidia-settings
as well as
nvidia-smi
report DRIVER VERSION as 545.23.08
&
NOT NVIDIA-Linux-x86_64-545.29.06

***NARRATIVE FOLLOWS***
***NARRATIVE FOLLOWS***

### Method 3: Install NVIDIA Drivers via Runfile on Fedora
#### Step 2: Disable the Nouveau Drivers
#### Step 3: Regenerate initramfs and Reboot
#### Step 4: went into CLI mode (init 3 equiv)
#### Step 5: executed the RUN file ```sudo bash NVIDIA-Linux-x86_64-*```
#### Step 6: followed the NCURSES installer & all of the steps 
#### Step 7: BOTH ```nvidia-settings``` as well as ```nvidia-smi``` report DRIVER VERSION as 545.23.08 & NOT NVIDIA-Linux-x86_64-545.29.06

RESOURCES
RESOURCES

followed all directions from:

How to Install NVIDIA Drivers on Fedora 39/38/37 Linux - LinuxCapable

2

I recommend you uninstall the nvidia provided software and use the rpmfusion package and tested drivers instead.

Please follow these instruction to install the rpmfusion nvidia drivers: Howto/NVIDIA - RPM Fusion

FYI the 545 driver version is not yet released by the rpmfusion developers.

2 Likes
3

Edited, I donā€™t mean to sound dismissive but following the RPM fusion path doesnā€™t really teach me where I went wrong or how to fix this issue if it happens again in the future Plus I want to learn and understand what Iā€™m doing and I need to grow with my knowledge so utilizing the EASIER PATH the RPM fusion path doesnā€™t teach me more about how to utilize my Linux system and grow as a power user: I hope you understand where Iā€™m coming from and why I need to understand what I did wrong where I went wrong and where my path deviated so I can grow as a Linux user

Intentionally

I do not wish to use the RPM fusion versions

Because they are older and more out of date

I prefer to use the driverā€™s directly from Nvidia

I just want the driver numbers to match

Thatā€™s the issue that Iā€™m dealing with right now

If I was interested in having older drivers I would have gone through the RPM fusion path as outlined in the tutorial document listed in my original post

If you care to read through that document it outlines several possible methods paths and avenues of installing the Nvidia drivers

The very first one is the RPM fusion method which is the easiest one

But for my particular setup and needs RPM fusion method is inappropriate and is out of scope

That is why I want to install directly from Nvidia because thatā€™s the scope that I need to obey

Edited, I donā€™t mean to sound dismissive

but following the RPM fusion path doesnā€™t really teach me where I went wrong or how to fix this issue if it happens again in the future

Plus I want to learn and understand what Iā€™m doing and I need to grow with my knowledge

so utilizing the EASIER PATH the RPM fusion path doesnā€™t teach me more about how to utilize my Linux system and grow as a power user:

I hope you understand where Iā€™m coming from

and why I need to understand:

what I did wrong
where I went wrong
and where my path deviated

so I can grow as a Linux user

4

There are plenty of opportunities to learn and grow no matter how you manage your system.

Installing the drivers directly from nvidia may seem ideal since nvidia is upstream and the newer drivers are released there sooner.

However, the reality is that many users encounter various config issues when installing that way since that version of nvidia drivers have not been specifically tweaked and tested with fedora. Rpmfusion does the tweaks and testing so the end user does not encounter problems with those drivers and configures the rpm so that when it is installed it makes the adjustments needed to properly function on your system. It even automatically compiles the drivers for the kernel being used so they match exactly.

If you choose to use the drivers directly from nvidia that is certainly your choice, but be aware that since very few do so there are also very few who have the experience to guide you through the various pitfalls you may encounter. Trying to stay at the bleeding edge of driver development as it seems you wish means that you may have to resolve any issues yourself and may get better support by asking this type question on the nvidia forums.

I have been using nvidia GPUs with fedora since fedora was first available, and it was at first a constant battle with the various tweaks required to make it work. I was happy when rpmfusion began providing the already tested packages to install since that meant I did not have to personally do the management of the graphics driver with system upgrades of various sorts and could use packages that were already tested and for most users would ā€œjust workā€ā€¦

Unloading some known issues and being willing to use the tested and reliable drivers, even though a little older, while learning the other parts of system administration might be a better path. Once you learn more then attacking the driver issues could provide less stress and more satisfaction.

2 Likes
5

I sincerely appreciate your response:

It was heartfelt informative & extremely detailed!

I really appreciate you taking the time & explaining your position!

I first started using Linux back in 1999

Linux for dummies second edition written by John maddog Hall

It came with Red hat 5.2

Because of my mental health issues and learning disabilities

They are comprehension, reading based and memory based

Similar to dyslexia

Using Linux and learning programming has always been an uphill battle for me

Never remembering the syntax

Never remembering the sequence

Always having difficulty with keywords and options

Always getting the process mixed up

the steps that need to be taken in which order

But that hasnā€™t stopped me from using Linux

That hasnā€™t stopped me from trying different distributions over the years

Linux from scratch and Gentoo from stage 1

These are all things that have helped me throughout my journey

Recently, I was really big on using Garuda and Manjaro,

But there were just certain issues with the repositories that recently just caused all of the installs to break

So I decided to go back to my favorite distribution of all time the Red hat family

I also used to use SuSE a bunch and I still consider it part of the Red hat family because it utilizes RPM package management even though I know itā€™s a completely different company

Which has changed over ownership a dozen times over the past 25 plus years

The one distribution family that Iā€™ve had zero luck with and still leaves a bad taste in my mouth is anything Debian based

Which is really sad because I used to be a huge Ubuntu evangelist back in high school days back when they used to send you free DVDs

Back when the wallpaper was tasteful nudes and it gave Ubuntu very silly nickname

But Iā€™ve stayed really proud about the red hat and fedora family still keeping on very strong

A really nice and welcoming community

Something that I really canā€™t say about the d e b i a n community

I think Iā€™m coming to figure out what went wrong with my install

And it seems a little bit stupid a little bit silly a little bit strange

But I guess I didnā€™t run the uninstall of the previous Nvidia drivers correctly

There is a particular NVIDIA-uninstall command that I guess I neglected to issue

Once I did that and tried to run nvidia- settings or Nvidia - SMI

Which of course didnā€™t work because the uninstaller uninstalled everything that it should

Then I was able to repeat the entire process that was listed on the

Website I was able to follow all of these instructions all the way over from the beginning

And then now miraculously I have the correct drivers installed

Yes youā€™re correct Iā€™ve always wanted to be on the bleeding edge because Iā€™ve always liked trying new things

Thatā€™s why I like tumbleweed Thatā€™s why I like rawhide Thatā€™s why I like Arch and gentu and Linux from scratch and Garuda and Manjaro

Thatā€™s why I love enabling testing and development and git hub repos

Thatā€™s why I always use nightly builds for pretty much every application that I can get my hands on

I want to live on the bleeding edge because I want to try all of these new features

Iā€™ve been using Linux since 1999 and itā€™s amazing seeing how much itā€™s grown and how much wide spread adoption that Linux has now

All of these industries are now using Linux specifically cinema and entertainment

For example Iā€™m trying to get render Man to work which is the rendering engine that Disney and Pixar uses for all of their animated films

And there is a direct shim plug-in that they maintain for blender

So you can spin up the render Man installer on RHEL Rocky centos or equivalent

I got it to work on Fedora with a little bit of juggling I had to watch several YouTube videos where one German creator had a really genius little hack type of situation to get it to work cuz of the QT library mismatches

But it works and Iā€™m grateful

Iā€™m grateful the open source community is so large now

Iā€™m so glad that regular people creative people artists and industry has embraced Linux

When it used to only be relegated to nerds and hackers that would live in the basements and closets and the server rooms

Now it powers all of our phone and tablets and appliances Itā€™s inside of our refrigerators and microwaves and ovens Itā€™s inside of our vehicles Itā€™s inside of every single IoT device

Epic games open source to the unreal engine and now people are using that along with blender for virtual production

Gone are the days of photorealistic VFX and professional production being out of reach for the common person

All of these tools are free and open source and available to all accessible to anyone whoā€™s willing to learn

Thatā€™s why Iā€™m grateful for the community Thatā€™s why Iā€™m writing this long-winded response

Because of you We are all better because of you because of this community because youā€™re willing to help people like me who are struggling

6

Thank you for the explanation, and keep up the good struggle. It warms my heart when there are individuals who continue and strive to always move forward into areas that most ignore or avoid.

Good luck in the future and I am glad I was able to assist in solving your driver issues. :upside_down_face:

1 Like
7

I have an adjacent question:

Do you prefer using the RPM fusion version of steam or the flat pack version of steam?

Iā€™ve been looking at both sides of the story and lots of people seem to prefer the flat pack version because of the safety and security of containerization

But my worry is I need my drone FPV controller to work because I primarily use steam to fly my drone simulators

Iā€™m curious if it will work because theyā€™re not really a standard joystick but they are visible over USB

8

I use steam from rpmfusion.

9

Rpmfusion version of steam.

10

As a guide see if the game on steam is ā€œSteam deckā€ compatible.
That often means it will work in linux Steam. But beware that all consoles
(XBOX, PS5, Steam deck) are AMD GPU based and that can mean that
NVidia support may be unoptimised or worse.

This was/is the case with Starfield for example.

1 Like
11

Oh thatā€™s really interesting

About the steam deck compatibility

I never even thought about that or drew that connection

(I mean yes I had the option enabled inside of steam I just didnā€™t draw that connection)

Thank you for sharing about the AMD GPU I didnā€™t realize that either

But whatā€™s really interesting that Iā€™m not quite sure how to troubleshoot or determine

Is when I was on my Garuda & Manjaro install

Steam was working very well without any appreciable lagging with the settings turned up to basically Maximum

Now I donā€™t know if Iā€™m having a driver based issue

A Kernel-based issue

A steam platform library based issue

Or some other miscellaneous issue

Because when Iā€™m using the flat pack version of steam

Itā€™s reporting m e s a based drivers instead of Nvidia

And the same is happening with the RPM fusion version of steam

Even the deb package version of steam

That I extracted into subsequent folders

And then executed the binary

Doesnā€™t seem to report correct driver implementation

So maybe me manually installing the drivers wasnā€™t the best idea

But I donā€™t know if thatā€™s the lagging issue that Iā€™m experiencing

Because when I attempt to select the use Vulcan all of the steam clients just crash

But when I was using Garuda or Manjaro

I had the bleeding edge mainline kernel installed in addition to Arch specific gaming modifications

And the steam ran really smoothly

Now I donā€™t really want to have to reinstall my entire fedora installation

Just to check to see if steam works correctly with which driver implementation and kernel implementation

But I think thatā€™s pretty much what Iā€™m going to have to do

Is back up all of my precious data

Which Iā€™m also probably going to neglect to do

And then Iā€™m going to probably jump into Manjaro & Garuda and probably stick strictly to defaults

Iā€™m going to do flat pack and their version of steam

To see if I can reproduce the lagging issue

If the lagging issue is still present then itā€™s probably some sort of hardware issue that Iā€™ll have to pull my hair out to figure it out

But if it works flawlessly like it did last time

Then Iā€™m probably going to go back to a quick install of Fedora with the RPM fusion version of the drivers

And then Iā€™m going to test the flat pack steam and RPM fusion version of steam

And then Iā€™ll report back with my findings

But Iā€™m really not looking forward to this

Iā€™ve also been eyeing at the blend OS project

Thatā€™s another immutable based operating system similar to what is it called silver blue or something

Blend OS claims that it supports every single package management including APKs

Iā€™m curious to see how it performs

But it didnā€™t offer l u k s hard driving encryption in the installer

And I want my system to be encrypted because encryption is groovy

But if Iā€™m just trying it out to validate a issue Iā€™m having I guess it really doesnā€™t matter if it has encryption on the hard drive

Especially cuz Iā€™m just trying to determine driver issues and steam issues

Iā€™m also going to test out SuSE (openSuSE leap & tumbleweed)

To see if their RPMs work any differently

I used to use them back in the day as well

12

Steam under wayland performs differently to steam under X1a.
Try logging in the DE as X11 if you ate on wayland does that help?

1 Like
13

Wait o.o really?

Hold the phone

Can you explain why they act so differently from one another?

Iā€™m definitely going to see if I can switch out of Wayland and back into x-11

EDITED:

After logging out of the desktop environment

At the bottom of the log in the screen where you can select the desktop environment

I selected x11 and miraculously steam is no longer sluggish and detects and utilizes properly the manually installed Nvidia graphics drivers

I still donā€™t understand why I have to use x11 and not Wayland

I still donā€™t really understand the purpose of Wayland if itā€™s supposed to be the successor of x11 or itā€™s supposed to be better than x11

Why is it not as performant or optimized as x11?

Would anybody be able to clarify my misunderstanding?

14

I didnā€™t see a difference between either with F39, but I donā€™t game on my PC often, and am not likely as critical about performance. I was playing Counter Strike if that makes any diff, and it was smooth enough in performance that I didnā€™t feel my hardware was limiting me. But I donā€™t use NVidia stuff on my system, so take this with a ā€˜grain of saltā€™.

1 Like
15

This usually means that for whatever reason the nvidia GPU is not being used. I have found that with my laptop which has dual GPUs (one is nvidia) I had to use the nvidia drivers and configure the system to use the nvidia GPU as primary as well as use X11 when I was using steam.

It seems that optimus based systems (dual gpu) are designed to use the intergrated GPU by default and thus do not get the ability to use the built-in hardware acceleration of the nvidia gpu without the nvidia drivers and using the nvidia GPU while running steam. When using the iGPU the system offloads the graphics rendering to the CPU which results in cpu overload with lagging and slowdown for everything.

I suggest this be approached first from the gpu driver standpoint.

Please run inxi -Fzxx and post the output as preformatted text using the </> button on the toolbar to retain the on-screen formatting for readability. It may be necessary to install inxi first. Also post the output of lsmod | grep nvidia

1 Like
16

EDITED:

After logging out of the desktop environment

At the bottom of the log in the screen where you can select the desktop environment

I selected x11 and miraculously steam is no longer sluggish and detects and utilizes properly the manually installed Nvidia graphics drivers

I still donā€™t understand why I have to use x11 and not Wayland

I still donā€™t really understand the purpose of Wayland if itā€™s supposed to be the successor of x11 or itā€™s supposed to be better than x11

Why is it not as performant or optimized as x11?

Would anybody be able to clarify my misunderstanding?

Editedā€¦

I will post the INXI results underneath this

puppy@2603-7080-3e00-d7e9-db4b-e9aa-7cdd-711d:~$ inxi -Fzxx
System:
Kernel: 6.6.2-201.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11
dm: 1: GDM note: stopped 2: SDDM Distro: Fedora release 39 (Thirty Nine)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X399-A v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1203
date: 10/09/2019
CPU:
Info: 8-core model: AMD Ryzen Threadripper 1900X bits: 64 type: MT MCP MCM
arch: Zen rev: 1 cache: L1: 768 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 2171 high: 2200 min/max: 2200/3800 boost: enabled cores:
1: 2196 2: 2200 3: 2200 4: 2197 5: 2200 6: 2200 7: 2200 8: 2193 9: 2195
10: 2196 11: 2196 12: 2195 13: 2200 14: 1975 15: 1997 16: 2196
bogomips: 121365
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: PNY driver: nvidia
v: 545.29.06 arch: Pascal pcie: speed: 8 GT/s lanes: 16 bus-ID: 41:00.0
chip-ID: 10de:1b06
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 68
Monitor-1: Unknown-1 mapped: HDMI-0 res: 1920x1080 dpi: 70
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
API: Vulkan v: 1.3.268 surfaces: xcb,xlib device: 0 type: discrete-gpu
driver: nvidia device-ID: 10de:1b06 device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Audio:
Device-1: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 0b:00.3 chip-ID: 1022:1457
Device-2: NVIDIA GP102 HDMI Audio vendor: PNY driver: snd_hda_intel
v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 41:00.1 chip-ID: 10de:10ef
Device-3: Generalplus [] driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 7-1:2 chip-ID: 1b3f:2008
API: ALSA v: k6.6.2-201.fc39.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 05:00.0 chip-ID: 8086:1539
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
pcie: speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2725
IF: wlp6s0 state: down mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-10:2 chip-ID: 8087:0032
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 1.38 TiB used: 555.26 GiB (39.4%)
ID-1: /dev/sda vendor: Silicon Power model: SPCC Solid State Disk
size: 931.51 GiB speed: 6.0 Gb/s serial: <filter>
ID-2: /dev/sdb vendor: Silicon Power model: SPCC Solid State Disk
size: 476.94 GiB type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
ID-1: / size: 929.91 GiB used: 452.67 GiB (48.7%) fs: btrfs dev: /dev/dm-0
mapped: luks-04aa2f9c-7b2e-4e20-9ee4-625244e85dff
ID-2: /boot size: 973.4 MiB used: 302.4 MiB (31.1%) fs: ext4
dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 929.91 GiB used: 452.67 GiB (48.7%) fs: btrfs
dev: /dev/dm-0 mapped: luks-04aa2f9c-7b2e-4e20-9ee4-625244e85dff
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 42.2 MiB (0.5%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.0 C mobo: 27.0 C gpu: nvidia temp: 34 C
Fan Speeds (rpm): cpu: 1569 case-1: 1085 case-2: 1051 case-3: 998
gpu: nvidia fan: 25%
Power: 12v: 12.16 5v: N/A 3.3v: N/A vbat: 3.18
Info:
Processes: 587 Uptime: 1d 11h 58m Memory: total: 64 GiB available: 62.64 GiB
used: 9.3 GiB (14.8%) Init: systemd v: 254 target: graphical (5)
default: graphical Compilers: gcc: 13.2.1 Packages: pm: rpm pkgs: N/A
note: see --rpm pm: flatpak pkgs: 26 Shell: Bash v: 5.2.21
running-in: konsole inxi: 3.3.31
puppy@2603-7080-3e00-d7e9-db4b-e9aa-7cdd-711d:~$

and then Iā€™ll switch back to my default desktop enviornment under wayland and post the INXI underneath here

puppy@2603-7080-3e00-d7e9-db4b-e9aa-7cdd-711d:~$ inxi -Fzxx
System:
Kernel: 6.6.2-201.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11
wm: kwin_wayland dm: 1: GDM note: stopped 2: SDDM Distro: Fedora release
39 (Thirty Nine)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X399-A v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1203
date: 10/09/2019
CPU:
Info: 8-core model: AMD Ryzen Threadripper 1900X bits: 64 type: MT MCP MCM
arch: Zen rev: 1 cache: L1: 768 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 3730 high: 3899 min/max: 2200/3800 boost: enabled cores:
1: 3894 2: 3892 3: 3892 4: 3892 5: 3892 6: 3892 7: 3892 8: 2595 9: 3893
10: 3893 11: 3892 12: 3892 13: 3899 14: 3892 15: 3893 16: 2595
bogomips: 121365
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: PNY driver: nvidia
v: 545.29.06 arch: Pascal pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 41:00.0
chip-ID: 10de:1b06
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.2
compositor: kwin_wayland driver: X: loaded: nvidia gpu: nvidia display-ID: 0
Monitor-1: Unknown-1 res: 1920x1080 size: N/A
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
gbm: drv: kms_swrast surfaceless: drv: nvidia wayland: drv: swrast x11:
drv: swrast inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 23.2.1 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 16.0.6 256 bits)
device-ID: ffffffff:ffffffff display-ID: :0.0
API: Vulkan v: 1.3.268 surfaces: xcb,xlib,wayland device: 0
type: discrete-gpu driver: nvidia device-ID: 10de:1b06 device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Audio:
Device-1: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 0b:00.3 chip-ID: 1022:1457
Device-2: NVIDIA GP102 HDMI Audio vendor: PNY driver: snd_hda_intel
v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 41:00.1 chip-ID: 10de:10ef
Device-3: Generalplus [] driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 7-1:2 chip-ID: 1b3f:2008
API: ALSA v: k6.6.2-201.fc39.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 05:00.0 chip-ID: 8086:1539
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
pcie: speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2725
IF: wlp6s0 state: down mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-10:2 chip-ID: 8087:0032
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 1.38 TiB used: 555.26 GiB (39.4%)
ID-1: /dev/sda vendor: Silicon Power model: SPCC Solid State Disk
size: 931.51 GiB speed: 6.0 Gb/s serial: <filter>
ID-2: /dev/sdb vendor: Silicon Power model: SPCC Solid State Disk
size: 476.94 GiB type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
ID-1: / size: 929.91 GiB used: 452.67 GiB (48.7%) fs: btrfs dev: /dev/dm-0
mapped: luks-04aa2f9c-7b2e-4e20-9ee4-625244e85dff
ID-2: /boot size: 973.4 MiB used: 302.4 MiB (31.1%) fs: ext4
dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 929.91 GiB used: 452.67 GiB (48.7%) fs: btrfs
dev: /dev/dm-0 mapped: luks-04aa2f9c-7b2e-4e20-9ee4-625244e85dff
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 37.2 MiB (0.5%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 46.8 C mobo: 27.0 C
Fan Speeds (rpm): cpu: 1577 case-1: 1086 case-2: 1051 case-3: 1000
Power: 12v: 12.16 5v: N/A 3.3v: N/A vbat: 3.18
Info:
Processes: 512 Uptime: 1d 12h 1m Memory: total: 64 GiB available: 62.64 GiB
used: 4.24 GiB (6.8%) Init: systemd v: 254 target: graphical (5)
default: graphical Compilers: gcc: 13.2.1 Packages: pm: rpm pkgs: N/A
note: see --rpm pm: flatpak pkgs: 26 Shell: Bash v: 5.2.21
running-in: konsole inxi: 3.3.31
puppy@2603-7080-3e00-d7e9-db4b-e9aa-7cdd-711d:~$
17

I think becuase valve has not completed the wayland support for steam.
If you use wayland then X11 programs use the Xwayland X11-client which slows things down. Beware that apps are servers in the X11 worls and the desktop is the client,
not what your intuition guesses.

X11ā€™s design is 40 years old. The world of computer graphics is very different now.
Its been amazing that X11 managed to stay perfrormant and feature rich for so many decades.

But it became clear that a replacement was required to all for apps to fully utilize the
power of modern GPUā€™s. There where security issues that cannot be fixed in the X11
world. Wayland is that replacement. Appā€™s using wayland are faster with lower latency.
Desktop environment using wayland are a lot more secure.
This migration has been driven by the X11 developers.

2 Likes