Quoting: ShmerlI don't get this part:

Use cases have been identified for which separating the core GPU programming out of the full DRM driver stack is a strong requirement from our key customers.

Why does it need separating?

I believe it is because otherwise there would be no valid selling point for their Quardo line of GPUs.

They often times share the same architecture as the consumer GTX and RTX cards. But certain features, especially around virtualisation, are simply switched off driver side.
If this would be all open ppl could "just" enable the Quadro exclusive features and do not need to pay a fortune on Quadros.

One of the reasons why the move towards the GSP co-processor was made and the nvidia firmware blob being so huge. Instead of doing things (switch things on/off) driver side they moved into the GSP.

I think there is a strong link between these two things and the reason for "Use cases have been identified for which separating the core GPU programming out of the full DRM driver stack is a strong requirement from our key customers."

As a side note: I believe AMD is doing similar things. Certain workstation GPU features are turned on/off by firmware rather than driver and the reason there are some industry software strongly requiring the closed source AMD drivers. Especially around compute stuff.

The flip side of the coin is: This way you can server open drivers and still lock certain things behind a kind of pay wall for enterprise customers.

If I am wrong with any of these statements I encourage everyone to correct me where I might picked up things wrong.

View this comment - View article - View full comments

Quoting: nwildner

Quoting: Luke_NukemZero problems on 3 of my laptops with fedora 40 and the rpmfusion version or manual install. No issues with 555 beta either (which runs damned smooth).

reports for openSUSE [External Link] where it crashes during shutdowns only, and that systemctl reboot does not reproduces the issue

I somehow find the openSUSE Tumbleweed report strange. As the user runs Kernel 6.8 because an up-to-date TW should run 6.9.3.
Which somehow leads me to suspect that the user might be missing a few patches / fixes and issues are to be expected.

Edit: Oh the report is from April 22nd. Nevermind.

But why should this be limited to Laptops only?

View this comment - View article - View full comments

It still questioning why they still not use BtrFS snapshots for this.
One snapshot is the running one and then a new snapshots is used for the update and also just flipped over. As the SteamDeck already uses BtrFS for their root filesystem.

No need for two partitions, less space requirements as you do not need a full copy of the OS and bootloader (there are actually 5 partitions on Steam Deck 2x Boot loader, 2x The root filesystem and 1x the home partition) and no need for hashing the os image. What ever this is used for. Also using the BtrFS snapshot changes made by a user would keep persistent across updates too.

I would appreciate if someone could explain this to me? 😅

View this comment - View article - View full comments

Quoting: JarmerWhat exactly is "frame pacing" ...?

Usually frames are rendered in sequence 1,2,3,4,5,6,7...
Frame paceing means frames are displayed in the wrong order.

1,3,2,5,4,7, and so forth.

View this comment - View article - View full comments

open source developers not choosing he word open or libre in their project names:

View this comment - View article - View full comments

Quoting: Pengling

Quoting: scaineInvestors.

I think now's probably a good time to remind people of the Phantom console and the Gametrac/Gizmondo handheld. :wink: (For anyone who doesn't remember them, they were infamous investor-scams.)

Quoting: scaineAs for "NFT haters", I think you mean "normal people". Nothing wrong with blockchain per se, but it's most commonly associated with burning the planet via proof of work, and it'll take a long time to shift perception on that.

I think it's quite fair to describe it as a solution looking for a problem, really. :tongue:

Or it will be just another Ouya story. Things will go silent and then plans will be discontinued 😅

View this comment - View article - View full comments

Quoting: Phlebiac

Quoting: Vortex_AcheronticI think the funniest thing about AppImages is that they are not even fully self contained.

That would hardly work for a tool that has to manipulate data for third-party programs?

No that's not what I meant sorry for the confusion. It was about that AppImages do not contain all libraries they require to run in the first place. Of course a ProtonUP-Qt AppImage which fetches custom Proton builds from the web does not include said Proton builds.

I was speaking about what the AppImage itself needs to even open up.

For example, as someone who is on the immutable distro band wagon, I was hit hard by AppImages not being able to run on their own without modifying the host system. So I ended up setting up a distrobox container with all those random dependencies AppImages require to run as quite a few of them aren't installed. Neither on my host system and not in the container image by default.

Even after running countless of AppImages inside that container and installing missing dependencies there's every now and then a new AppImage which requires some new random dependencies installed in the system in order to run.

Which contradict with the idea of AppImages to ship all libraries they require to run by themselves. This means AppImages aren't true portable application formats in the end and thus aren't particular useful.

In case of ProtonUP-Qt this isn't a big deal as I use the flatpak anyway. But for other software which aren't on flathub this might be the case or I just need to extend the AppImage distrobox container 😅

View this comment - View article - View full comments

Quoting: dziadulewicz

Quoting: Vortex_Acherontic

Quoting: dziadulewiczI wish there was a flatpak and or a snap package rather than appimage :/

New users have no idea they have to be made executable and they don't integrate not self update. They apparently don't support Wayland either. Oh well.

If that just where the only issues AppImages had 😅

Yup! Don't know whether i'm the only one who finds appimage nothing short of joke actually at this point :huh:

AFAIK its the devs decisions keeping it from being more usable and current with times.

I think the funniest thing about AppImages is that they are not even fully self contained. Which is their whole selling point and purpose 😅

View this comment - View article - View full comments

Quoting: dziadulewiczI wish there was a flatpak and or a snap package rather than appimage :/

New users have no idea they have to be made executable and they don't integrate not self update. They apparently don't support Wayland either. Oh well.

If that just where the only issues AppImages had 😅

View this comment - View article - View full comments

Quoting: rustigsmedwith win10 support ending for home users late next year combined with win11 high system requirements we could see a continued or slight jump. anyone want to predict Jan 2026? will 6% or higher be possible? It will be interesting and fun to watch.

I suspect not. Most users are lazy and instead will just buy new hardware. Especially since Windows has established the "well known fact" that PCs slow down over time and you have to either re-install the OS or just get a new computer. Most ppl will do the later I suspect.

Even at the company where I work they downgraded to Windows 11 in the past few months and oh boi ... the amount of PCs which where ripped out of the office was stellar maybe like 30 PCs just from our department. Considering companies try to keep costs low it seemed not be the an issue to trash alls those still wonderfully working systems.

View this comment - View article - View full comments