conceptually, since we're building akmods in that repo, couldn't we build nvidia there and then have
conceptually, since we're building akmods in that repo, couldn't we build nvidia there and then have the nvidia images build out of main?
RThat's what I've been doing for a while now, and it works great.
The only thing I am wanting to do is split the builds to be grouped by Fedora version. E.g. make sure 38-Nvidia does not depend on 37 builds
The only thing I am wanting to do is split the builds to be grouped by Fedora version. E.g. make sure 38-Nvidia does not depend on 37 builds
KI'm not super familiar with how nvidia is built, but certainly we could host the kmod portion there
K@bsherman build errors on akmods are from Kernel 6.4, Gasket driver needed an update
Kthat's building now
Ghttps://github.com/ublue-os/startingpoint/pull/121
@j0rge the PR is up and i've resolved the conflicts
also what do you think of naming the repo file and public key the name of the repo?
Would that be the best choice or is there something else you have in mind?
@j0rge the PR is up and i've resolved the conflicts
also what do you think of naming the repo file and public key the name of the repo?
Would that be the best choice or is there something else you have in mind?
GitHub
Sorry, forgot to make the last PR a draft, jq wasn't working as intended as well as a couple other things, this should fix it all
Jyeah that seems to make sense
EI was thinking... With the faster build times we can probably fine tune when builds are triggered to get releases out more synchronously
EFor instance, even though the build time for main is 10 minutes, we wait a while hour it looks like for Nvidia
Jwhat I'd like is to trigger builds via rss or a webhook mechanism or something
Jlike when you push something into config it should trigger the rest of the stack
EThat would be awesome. Then we wouldn't really have to worry about scheduled build times. Expensive but awesome
Bnot that expensive, done it in past
EThat's good to hear
Bwebhooks should require 0 infrastructure if i remember correctly
Jyeah but like we'd probably keep the paid builders for the cron jobs
Byou can have both for a while, to see that it works correctly(i mean using webhooks and timers)
B@j0rge crap i think they changed how they group the webhooks so you do need infrastructure. As they group workflow requested and workflow completed together.
Jthere's a few webhook apps we could use, but haven't investigated recently
Btrue
BI like how you did that jq scripting to add a section to the policy.json
Jlol, of course it's not going to be easy
J
JI don't have time to do this until after work but if someone has any ideas: https://github.com/ublue-os/bluefin/actions/runs/5647367267/job/15297332335?pr=342
GitHub
An interpretation of the Ubuntu spirit built on Fedora technology - fix(framework): pin to kernel 6.3.11-200 · ublue-os/bluefin@efd5d04
KWhy the old kernel version on framework?
Jthis new kernel isn't running awesome on my desktop either
Bruh roh
Guh oh
Kmay need to rpm-ostree override remove *every kernel package* --install *every lower-version kernel package*
Kto get this to work
Jis it because the akmods stuff doesn't match?
Kit's ostree being goofy, it really does not enjoy replacing core packages like this
Bwhat's noticably problematic there?
Jevery few minutes or so the system bogs down, mouse stutters, I'm on an old version now
Git's TPM problem iirc so it might effect other systems with it enabled idk
Ksounds like the old TPM bug
Gyeah
Boh, so if tpm is disabled it may be fine
Kended up turning that off on my threadripper rig and the issue completely went away
Joh interesting
Jwhat am I looking for in the bios?
Bits' the same command line arg you added to just for framework no?
Gthe karg worked for me
K
Kis what I did, to be sure
Bi need TPM on my laptop 
so can't do it there
so can't do it thereKTPM is cool, but I'm boycotting it at this point due to it being used for DRM and doing this
K
Gwell you might want to stick with it for a bit
