I don't have time at the moment or tomorrow. Have folks over currently. May have time late tonight.
I don't have time at the moment or tomorrow. Have folks over currently. May have time late tonight.
Bif I get to it, will post something .... cool?
NSounds good!
J11.5 million pulls, 12 will be noproblemo!
JI wonder if we'll hit 13 before or after F40
MUnsure if we can blacklist that via modprobe. I've added it as a karg. The specified karg in the write up is an actual karg and not one that is passed to modprobe
BOMG are you implying that rpmfusion's docs may be incorrect? 
Mno
Mjust confused on why they specified it like this
Bi haven't checked the details yet.
Bbut if we actually want to do work on this ticket, i think it should be added to the project plan
MI added it as a karg check in bluefin/aurora. Personally, haven't seen this described issue on my nvidia box that runs luks
Jhey does anyone else find this weird: https://github.com/fedora-silverblue/issue-tracker/issues/543
- everyone else seems to be hitting this?
GitHub
Describe the bug Trying to rebase an existing SB39 to SB40 fails to boot showing vmlinuz-6.8.1-300.fc40.x86.x64 has invalid signature. you need to load the kernel first on an Thinkpad T495. I was n...
RColin's message makes it seem all that's needed is bootupd? Which has been in the images for months
travier and I had a chat, a few things here:
We can safely add bootupd to f39
I think we can also document a flow of rpm-ostree upgrade but without restarting, then
Run bootupd from the new root
Jsince september of last year, that's when we added it
Bi have a machine which i could use for testing, but i'm a bit in the weeds on several other issues, so as far as I'm concerned, this needs to get on the backlog, but that doesn't mean we need to action it yet
MI think that is fair to put on backlog.
Bi added a comment on the issue https://github.com/ublue-os/config/issues/250
MThe proposed fix was added in bluefin/aurora builds as part of the initramfs work.
MBut, as an nvidia + luks user on my desktop, I haven't seen this bug
Bwould you please add that context to the issue ticket?
MAdded a bug report that describes the issue affect Gnome back on 42 that had the proposed solution. So must be a weird combo of hardware
JWallpaper question about GNOME and KDE
Bi hate hearing about bootupd cause im still miffed it doesnt work outside of RPM which is only thing that i still need for it to do then i can do any distro in bootc
K
K
MKernel bumped again
MNvidia builds failing
MOn 39
MNow on 6.8.5
MAnd I guess akmods need a rebuild too
BYeah I was actually trying to merge the nvidia akmods change last night and saw the kernel bump skew. If we can get clean builds today I play to merge and rebuild all
BKUpdated the ublue site as well, our containerfile template is ready to use
Tthis is so cool??????????
Tme rn
FGlad to see something where I can direct users if they want Containerfile approach
NLong time coming. If folks want to contribute to it, feel free to add issue or PRs. We are trying to keep the scope pretty small. I would still like to add a generic workflow for generating ISOs, but we wanted to get something out there first.
J@Kyle Gospo can we make docs.universal-blue.org work? Probably link it from the website too
BI've been thinking about scope and how to accomodate things in
https://github.com/ublue-os/config/issues/254
confighttps://github.com/ublue-os/config/issues/254
GitHub
I've been thinking recently about how best to facilitate shared code (eg, ujust recipes) which are no doubt useful, very much desired in aurora/bluefin/bazzite, but seem somewhat out of scope f...
Jhello, is there any eta for v4l2loopback being enabled again in the akmods repo?
Bwe're waiting on RPM fusion to promote the fixed package from updates-testing to updates: https://github.com/ublue-os/akmods/pull/168
as soon as that happens, this PR is staged to build and merge
as soon as that happens, this PR is staged to build and merge
Jis there any place to see discussions or the status on rpm fusions side
Bi'm not sure, but i welcome a link in a comment on the PR if you find it
Jlook like it disappeared from the link in the comment lol
Bit didn't disappear, it's never been there
Bfor F39, v4l2loopback was built for the
release but never updated... the released version was not kernel 6.8 compatible... so that's what we're waiting on the updated version of the package which will build against kernel 6.8 to be promoted to the updates repoJi see ty
