Quick question, how far off being a proper distribution is bazzite now considering it ships it's own
Quick question, how far off being a proper distribution is bazzite now considering it ships it's own kernel?
Jdun dun dun
Kvery far, it's still fedora through and through
VThe one person you hope to not see that message
Jwe know what's happening here
Jhahahaha
VAhh ok, just curious.
Jby now it's like a knob, 0 being stock and 10 being full turbo
Jbazzite keeps turning up the volume
Jwhereas I try to not crank it so loud in bluefin.
Jit's all balance in the end.
VI think balancing it with Bazzite is harder when it's goal is ultimately to recreate another distro, which means the knobs do have to be turned a fair amount.
Jyeah plus bazzite targets new hardware devices
Jat some point it needs to pull in non-stock things
VYup
VStill more than faithful to Ublue more than anything though
Jso I guess as long as people use it and contribute to it, it's kind of up to the community how far to go
JYou can't have too many branches and tags in git, it'll grow depending on the people who contribute to it.
VI don't know what the "proper" definition of a distro is
In my head seeing as bazzite's shipping a kernel, it is distributing linux to some degree lol
In my head seeing as bazzite's shipping a kernel, it is distributing linux to some degree lol
Kfsync is just patched fedora kernel
Kso it's still fedora even w/ a custom kernel
Kwe just can't use their signing keys
VGotcha
Tpeople will still call it a distro regardless because OCI image isn't exactly known to the general public... yet!
Jdepends on the opinion, the concept of "distribution" kind of goes out the window when you can use what you want
Ti prefer not calling it that though
JI consider it "an operating system"
Tbecause it makes these projects look like "fringe distros"
VSometimes I do just for ease of explaining it. I prefer not too, because I know it's not, but it's hard to explain.
Joh sweet. I am just using it on a htpc
CWait, are we using the Neptune kernel now?
Coh riiight, the fsync thingy
Kchecked Nobara's sources
Kthey have my wireplumber patches but not my pipewire ones
Kone of the pipewire patches caused our popping audio which I fixed, the other is causing the issue we face
Kbut is also directly responsible for huge portions of Steamdeck-DSP working
Kso that's why there's a difference
Kgonna figure that one out here soon
Mgotcha, that certainly explains things then. Only Nobara audio issue I’ve noticed is an occasional crackle on resume from sleep but that goes away on its own
Kmy guess is because Steamdeck-DSP puts config files in /run it's causing issues w/ resuming from sleep
Kgonna find a way to work around that
Kat the very least restarting them works
Mfuture rambles from me on general kernel woes will be going in the kernel channel of the Linux Gaming Dev server, figured we’d focus our efforts there
Ksounds good
K@M2 might have a task that'd be up your alley if you're willing to help
K
Kvalve has this rather silly system where they override BT audio configs by writing one into /run/
Kand then patch wireplumber to read from /run instead of /usr
Kwhat would be nicer is if we mounted over top of /usr
