Is this the script that installs the propietary driver if legacy gpu?
Is this the script that installs the propietary driver if legacy gpu?
ADunno looks cool
Hthis is what installs it into the image you download in the end, it is not the silent rebase logic if that is what you are thinking about (we dont have that yet as we need images first)
P560 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.
Also legacy users will be auto rebased to 560 drivers with legacy support if all goes well. You just have to wait tbh.
PNothing really to do on your side, unless something will change. And I'm sure all of us will be informed about it.
Hno no you will just wake up one day and be on
nvidia-legacy and we will all be like (this is a joke obviously)
Phahah 
RThat's good to know
JJI've updated the website to point to this instead of the old fedora spec
Jthis is awesome
R@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?
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?
JI dunno, the more you add the more people will want.
Askip -main, make it usable and ship imo
Ainteresting, reminds me of robots building other robots
Ayour container will have an installer and will be able to write itself
AAnyone 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?
ALike any good reference docs people found especially helpful?
K@Robotta Try the latest
:testingJ""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."
Jnice zinger to Noel's question
RIs there a way to check if you're on the open or closed source Nvidia kernel drivers without relying on the image tag?
MYou can determine which flavor of kernel modules is installed using either
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 [...]
modinfo 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 [...]
FNvidia akmods are not pinned to v555, so it can cause breakages for latest Nvidia images
M@Robert (p5)
Knvidia akmods shouldn't be pinned
KHWE should pin akmods
Kas well as anything else that pulls akmods
Jwhich we did last night
Kyup
Jneed more info from people having issues
FHmm, I see
Kalso 560 should be better now that we've figured out they just started defaulting to nvidia-open
Kand fixed that in akmods
Kneeds re-testing
RYeah... 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
I believe this is the relevant error, though I don't know how to interpret it
Although I've not seen anybody else having issues in the Bazzite testing branch
I believe this is the relevant error, though I don't know how to interpret it
KGitHub
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...
RThanks. That looks like it, and the latest comment suggests it's not isolated to just my system. But there's really just one other person???
Dno
Dthat just simplifies the building of akmods assuming I can get it working
DIt's a nice bit of refactoring
Done install script that should work with both types of nvidia drivers
Dthe bug I hit earlier with the labels blocking build args from being parsed was really strange
KThat will have to be a separate image
KThere's no script that's going to make that work here
M@Robert (p5) @Kyle Gospo need to recheck the hwe pinning. Somehow images seem to have mixed nvidia drivers between the kmods and the repo packages.
KI think we just turn it off, the main issue was Nvidia open which is fixed
KAnything else is on Nvidia
MRight now we have the kmod and repo packages providing a mix of 555 and 560.
