560 drivers are in testing and the are still in beta. Also legacy users will be auto rebased to 560

560 drivers are in testing and the are still in beta.

Also legacy users will be auto rebased to 560 drivers with legacy support if all goes well. You just have to wait tbh.

PrykaOP•8/8/24, 8:41 PM

Nothing really to do on your side, unless something will change. And I'm sure all of us will be informed about it.

PPryka Nothing really to do on your side, unless something will change. And I'm sure al...

HikariKnight•8/8/24, 8:47 PM

no no you will just wake up one day and be on nvidia-legacynvidia-legacy and we will all be like (this is a joke obviously)

HikariKnight•8/8/24, 8:47 PM

https://tenor.com/view/invaderzim-whistle-whistling-casual-bored-gif-4807992

Tenor

super casual

PrykaOP•8/8/24, 8:47 PM

hahah

PPryka 560 drivers are in testing and the are still in beta. Also legacy users will be...

Robotta•8/8/24, 9:00 PM

That's good to know

j0rge•8/8/24, 9:06 PM

oh, got this URL from Dan's talk: https://containers.github.io/bootable/

Bootable Container Images

Goals

Bootable container images

j0rge•8/8/24, 9:06 PM

I've updated the website to point to this instead of the old fedora spec

j0rge•8/8/24, 9:06 PM

this is awesome

Robert•8/8/24, 9:07 PM

@j0rge in Cosmic, I'm looking to make a few changes, but not sure if it would be too opinionated for a base image.

1. Enable Flathub user remote since this seems like a requirement to use the app store
2. Install system Flatpaks of default apps (calendar, document viewer etc) on the ISO?

WDYT?

j0rge•8/8/24, 9:09 PM

I dunno, the more you add the more people will want.

antheas•8/8/24, 9:10 PM

skip -main, make it usable and ship imo

Jj0rge oh, got this URL from Dan's talk: https://containers.github.io/bootable/

antheas•8/8/24, 9:10 PM

interesting, reminds me of robots building other robots

antheas•8/8/24, 9:10 PM

your container will have an installer and will be able to write itself

Adrian E. (Open Source)•8/8/24, 9:29 PM

Anyone got recommendations for intro to bootc docs/tutorials? I.e. building an image from a containerfile, customizing wallpapers and branding, and snippets for other useful stuff?

Adrian E. (Open Source)•8/8/24, 9:30 PM

Like any good reference docs people found especially helpful?

Kyle Gospo•8/8/24, 9:33 PM

@Robotta Try the latest

:testing

:testing

j0rge•8/8/24, 9:41 PM

""We're trying to say, the container ecosystem has won. Anything that isn't based off of the way people deal with containers is going to be a one off. We want to participate within the container ecosystem."

j0rge•8/8/24, 9:41 PM

nice zinger to Noel's question

Robert•8/8/24, 10:13 PM

Is there a way to check if you're on the open or closed source Nvidia kernel drivers without relying on the image tag?

mc•8/8/24, 10:25 PM

You can determine which flavor of kernel modules is installed using either modinfomodinfo or looking at /proc/driver/nvidia/version.

E.g., the proprietary flavor will report:

# modinfo nvidia | grep license
license: NVIDIA

# cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module [...]

The open flavor will report:

# modinfo nvidia | grep license
license: Dual MIT/GPL

# cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX Open Kernel Module for x86_64 [...]

fiftydinar•8/8/24, 10:25 PM

Nvidia akmods are not pinned to v555, so it can cause breakages for latest Nvidia images

mc•8/8/24, 10:25 PM

@Robert (p5)

mc•8/8/24, 10:26 PM

https://us.download.nvidia.com/XFree86/Linux-x86_64/560.31.02/README/kernel_open.html

Kyle Gospo•8/8/24, 10:26 PM

nvidia akmods shouldn't be pinned

Kyle Gospo•8/8/24, 10:26 PM

HWE should pin akmods

Kyle Gospo•8/8/24, 10:26 PM

as well as anything else that pulls akmods

j0rge•8/8/24, 10:26 PM

which we did last night

Kyle Gospo•8/8/24, 10:26 PM

yup

j0rge•8/8/24, 10:26 PM

need more info from people having issues

fiftydinar•8/8/24, 10:27 PM

Hmm, I see

Kyle Gospo•8/8/24, 10:28 PM

also 560 should be better now that we've figured out they just started defaulting to nvidia-open

Kyle Gospo•8/8/24, 10:29 PM

and fixed that in akmods

Kyle Gospo•8/8/24, 10:29 PM

needs re-testing

Robert•8/8/24, 10:33 PM

Yeah... That's why I wanted to check. I am now on the proprietary Nvidia 560 drivers, and still facing the freezes - mostly when applications are fullscreen (not maximised).
Although I've not seen anybody else having issues in the Bazzite testing branch

➜  ~ modinfo nvidia | grep license
license:        NVIDIA

➜  ~ modinfo nvidia | grep license
license:        NVIDIA

I believe this is the relevant error, though I don't know how to interpret it

Aug 08 23:37:19 fedora kernel: [drm:nv_drm_atomic_apply_modeset_config.isra.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to initialize semaphore for plane fence
Aug 08 23:37:19 fedora kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -11

Aug 08 23:37:19 fedora kernel: [drm:nv_drm_atomic_apply_modeset_config.isra.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to initialize semaphore for plane fence
Aug 08 23:37:19 fedora kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -11

Kyle Gospo•8/8/24, 10:40 PM

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/622

GitHub

Atomic commit fails if IN_FENCE_FD is set · Issue #622 · NVIDIA/ope...

NVIDIA Open GPU Kernel Modules Version 550.40.59 Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the ope...