530 is for when 535 or "535.123" -> "535.124" breaks something major on your particular machine whic
530 is for when 535 or "535.123" -> "535.124" breaks something major on your particular machine which might be fixed in "535.125" or 540
Bnot anymore. 
it doesn't build in kernel 6.4
it doesn't build in kernel 6.4
CPop and Mint are the only options with that safety net since rpmfusion dropped all but the latest and sometimes legacy
Byep
CBriefly, ublue had the best Nvidia support on Linux
Bi wish they would keep current-1
CYeah
Kanything stopping us from ingesting their RPMs and caching them for that purpose?
Boperational and maintenance complexity
Bi'm not opposed to doing it, if it's a full solution, like, all our nvidia stuff (at least) goes through the same process
Bplease review and approve if this looks good https://github.com/ublue-os/nvidia/pull/131
GitHub
remove v530 from f38 (fails due to kernel 6.4)
enable v470 on f38 (wasn't built previously)
now f38 and f37 are both building v535 and v470
update README to reflect current state (was out of date)
enable v470 on f38 (wasn't built previously)
now f38 and f37 are both building v535 and v470
update README to reflect current state (was out of date)
B@j0rge i see that giscus is posting https://github.com/orgs/ublue-os/discussions/categories/announcements here
I'm wanting to post an announement here https://github.com/orgs/ublue-os/discussions/categories/nvidia-driver-announcements?discussions_q=is%3Aopen+category%3A%22Nvidia+Driver+Announcements%22 (per Nvidia README) but i'm not sure how
I'm wanting to post an announement here https://github.com/orgs/ublue-os/discussions/categories/nvidia-driver-announcements?discussions_q=is%3Aopen+category%3A%22Nvidia+Driver+Announcements%22 (per Nvidia README) but i'm not sure how
Bis that a website blog post addition?
Bnvidia driver version change merged... and manually building
Bugh... i missed the secondary matrix... yeah, we need nvidia akmods in the akmods repo 
B
GitHub
I had previously fixed the akmods nvidia build matrix but not the os image variant matrix.
B
thanks @KyleGospo
Jyou can just post normally in the forum
Junless you want to do a blog post?
Bmeh, not really earth shattering stuff
Bjust fixing the build
Jthen you just do
comments:true in the postBbut we are dropping v530
Jheh
KPing me when that's all built by the way please
KGot some builds I'm waiting on it for
Bwill do
KPS @bsherman do you have Nvidia hardware?
KI don't and we're having an issue that's blocking release
Byeah, i've got a couple Dell laptops with intel+nvidia (mux'd, not gamer laptops)
and i've got a desktop test rig with a gtx 1660ti
and i've got a desktop test rig with a gtx 1660ti
KGitHub
Distrobox with the --nvidia flag is supposed to copy the host's Nvidia drivers into the container. It seems this may be incomplete, as currently this results in a broken installation. This is a...
KIf you have time to solve a mystery this is driving me nuts
KWe could have a beta release of desktop right now
KYou don't have to install bazzite or anything, any host with distrobox should have the same behavior
Bi'm pushing way past my ublue time box today thanks to broken nvidia but i'm happy to look when i have more time
but i'm happy to look when i have more time
EAt this point let's just link Nvidia users to the free month of Xbox game pass and call it
KHere bro, rent a functional GPU
ELmao
ENot wrong
BNVIDIA BUILT GREEN https://github.com/ublue-os/nvidia/actions/runs/5649430544
Kyay! ty
ACan you try reproducing with podman?
KI can't, but if anyone with nvidia hardware wants to try..
EAny ideas for how we can document the upgrade path to signed images from Silverblue cleanly? https://github.com/ublue-os/nvidia/issues/133
GI'm really confused as to what i'm doing here
GI'm trying to follow/adapt the guide to fedora and ostree container native builds but I can't
J@bsherman I have brought the merge queue to work!!
J
Jbringing things we learn here to our pro toolkits, hell yeah!
LAyy it’s Taylor! (he is cool)
J