might be nice to ship man pages for our images, just the github readme.md packaged as such
might be nice to ship man pages for our images, just the github readme.md packaged as such
Kmain could ship
man ublue-osKnvidia could ship
man ublue-os-nvidiaKand so on
Ksince we include usage instructions in there
Bsounds like a good proposal/issue 
'
'
Band i like the idea
K
KI'll work on a reference implementation since I want it in bazzite
Kand then open an issue
Bthe akmods and config repos are the most complicated 
Bprobably need distinct man pages for different RPMs etc
Bphew, trying to help a user get the and discovering that
wl driver going and discovering that nvidia failed to build this morning LOLBso, kernel mismatch!
Brebuilding nvidia now
Bwell, i guess nvidia won't build on 6.4.4 yet
Boh, not 530
B535 does work
Jneato
Bwe've definitely discussed that before, it's actually part of an open issue
Jyeah I was just showerthinking about it the other day
BI think maybe doing that would help with the current situation... a specific version of nvidia akmd doesn't build, but that wouldn't block all nvidia images
Bbut the nvidia version matrix is more complex than our other akmods
Jah ok
Bi'm sure we could make it work, i have just been away and trying to prioritieze
Bso atm i'm wondering, is 530 never going to work on kernel 6.4?
EThis must be partially what I saw last night
Bi'm doing some local build testing
Bi'm not 100% sure on our rational for when we keep an old nvidia driver version around
Bwith driver 470, i know it is because it supports older cards
Bbut on the desktop/laptop "latest" for nvidia from rpmfusion really just seems to keep going
Bso... yeah... hypothesis confirmed... 470 WILL build on kernel 6.4 fedora 38... but not 530... so I think i'm going to update the nvidia repo to build 470 and 535 for both f37 and f38 and get things working again
Band update the README 
C530 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.4CPop 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
BGitHub
I had previously fixed the akmods nvidia build matrix but not the os image variant matrix.
B
thanks @KyleGospoJyou can just post normally in the forum
