[01:43] <lotuspsychje> good morning
[16:04] <Chunkyz> not a support related question but did the point release get delayed?
[16:05] <rfm> Chunkyz,  yes  https://lists.ubuntu.com/archives/ubuntu-devel/2022-August/042247.html
[16:08] <Chunkyz> Well, that sucks. thanks.
[16:08] <leftyfb> Chunkyz: are you running 20.04 and waiting for the popup to upgrade to 22.04?
[16:09] <Chunkyz> no.
[16:10] <leftyfb> Chunkyz: then how does the delay affect you?
[16:11] <Chunkyz> I was thinking of trying to install 22.04 to a RPI CM4. Haven't been active lately and heard hardware acceleration is working.
[16:11] <Chunkyz> leftyfb, did I say it affected me?
[16:17] <ogra> Chunkyz, just use the 22.04 Pi image and update it ... you'll then be on 22.04.1 anyway
[16:18] <Chunkyz> Sure, not disputing it. Just wondered *why* it was delayed. :-)
[16:18] <ogra> (22.04.1 is done ... just the specific install images that hold all the updates are not) 
[16:19] <Chunkyz> So it's not done, then.
[16:19] <Chunkyz> Is it true Hardware acceleration is working under RPI?
[16:19] <ogra> ah. well, it was delayed because oem-config uses an unusual systemd target ... that snaps were not prepared for ...
[16:20] <ogra> for desktop stuff. yeah 
[16:25] <waveform> Chunkyz, depends on the bit of hardware acceleration you want, and which application. For instance, hardware accel on firefox on the Pi is not working yet, because firefox demands opengl 3+, as does gtk3 (hilariously, this is why the graphics card is "" in the gnome control center -- simply because opengl isn't 3+ so it won't initialize a surface, and then won't query the graphics card)
[16:27] <waveform> on the other hand, accelerated h264 decode *is* working under ffmpeg ... but only when it's prodded to use v4l2m2m explicitly. Things are basically "getting there"; the upstream drivers are largely in place (though there are further improvements to come with the recent vulkan 1.2 announcement), but there's still plenty of frameworks (gtk3) and applications (firefox) that don't yet work properly with them
[18:32] <Chunkyz> waveform: what's the command to enable vc4 via config.txt? it's not enabled in the server edition.
[18:51] <Chunkyz> nvm, found it with Google. :-)
[20:37] <waveform> Chunkyz, yup -- server edition doesn't enable any KMS specifically (yet). I'm sure you've found it but just for reference, dtoverlay=vc4-fkms-v3d enables the legacy KMS stack (relying on the closed-source blob to control the GPU), dtoverlay=vc4-kms-v3d enables the new KMS stack (relying on the Linux kernel to control the GPU; this is the variant used on the desktop images). With neither of these the legacy framebuffer is used (the server 
[20:37] <waveform> default)