00:18 <clover[m]> Is it a noticeable difference opening apps

00:21 <HdkR> I mean, snap is still slow no matter what you do

00:22 <HdkR> and I didn't bench any game load times or anything

00:27 <HdkR> and since I load my Steam library off the network anyway, I'm bottlenecked by the slow USB 2.0 network speeds

00:43 <HdkR> Half-Life 2 might have loaded a bit faster? I don't really have the same laptop side-by-side for comparison

01:00 <steev> using snap smh

01:01 <steev> i keep trying to tell you to use a real distro like debian, i dunno why you insist on being a masochist and using ubuntu

01:02 <steev> hmmm

01:02 <steev> i'm tempted to get one if those speeds really are that much higher

01:03 <HdkR> Well, I actually just do a `sudo apt-get remove snapd` :P

01:03 <HdkR> Since I don't use firefox or chromium on the device

01:03 <steev> links should be good enough for anyone

01:06 <HdkR> If I was going to daily drive it I would definitely need chromium. So would slap Debian on it

01:06 <steev> if you daily drove it, you could probably report problems better than the rest of us

01:06 <steev> i've never noticed the usb issue

01:07 <steev> aside from the whole, some usb devices block the wifis

01:07 <HdkR> haha. That one I notice just because my weirdo Steam library setup :P

01:07 <steev> which... a) wtf and b) i have no idea where to even look to figure out why that is happening

01:08 <steev> but, i do believe someone much smarter than me came across it somewhat recently, and has the skills and knowhow so maybe something will come from it

01:09 <HdkR> Someone smarter than me can solve the USB issue :P

09:50 <juergh> srinik: Are you planing on upstreaming your audioreach topology files to debian? If not I could give it a whirl.

10:14 <_`[m]1> what does upstream mean here? kernel (so wait for 6.3) or packages (so wait for ??)

10:24 <juergh> SC8280XP-LENOVO-X13S-tplg.bin (and potentially others from srini's repo) to be provided by Debian package alsa-topology-conf

10:32 <srinik> juergh: yes, Ideally these need to go in linux-firmware, planning to send PR soon, working out some details on what to go into the Licence wordings.

11:03 <juergh> srinik: Hmm. linux-firmware? There's /lib/firmware/skl_hda_dsp_generic-tplg.bin but its provided by alsa-topology-conf. https://github.com/alsa-project/alsa-topology-conf

11:04 <juergh> actually the debian source is here: https://github.com/alsa-project/alsa-topology-conf

11:04 <srinik> juergh: there is already some tplg files in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek/sof-tplg

11:05 <juergh> oh. what a mess.

11:05 <srinik> juergh: am really not sure if https://github.com/alsa-project/alsa-topology-conf is maintained, it see last update to it was sometime 2-3 years back

11:05 <juergh> are the conf files used for anything other than compiling the bins?

11:06 <srinik> juergh: no,

11:09 <juergh> ok. then maybe best to submit to linux-firmware. they'll bark if they don't want it :-)

13:31 <steev> does anyone happen to know why grub's GRUB_GFXMODE being set to auto, breaks video output when msm probes (c630 and x13s) - i'd love to track down what the heck does it

13:35 <steev> no, i lied; it's not being set to auto, it's forcing it to 16x9 that does it (aka GRUB_GFXMODE="1280x720,1280x800,auto") causes the display to go... a bit off

13:38 <bamse> steev: never seen that stacktrace before...

13:39 <steev> which?

13:39 <steev> oh, c630

13:39 <steev> yeah me either :D

13:59 <init_x13s> x13s is becoming very liveable on a day to day basis. Still a bit disapointed by the various third party software availability for ARM (slack, spotify), and I might give a chance to FEX-EMU for that, but regarding the work done on the kernel and driver side, it's pretty neat.

13:59 <init_x13s> Anything big coming on 6.4?

14:02 <HdkR> I don't think Spotify app works under FEX because of chromium seccomp crap. Slack might be the same

14:02 <HdkR> Which luckily both offer their interface through a regular browser

14:08 <init_x13s> yeah, spotify is tolerable, and there's "spot" client that somewhat works. Slack however is absolutely horrible to use if you have multiple workspaces.

14:08 <bamse> HdkR: you can use spotify? mine says that i should enable drm support...

14:09 <init_x13s> bamse: on which distro are you on? For Arch we have widevine-aarch64 that solves it.

14:10 <bamse> i'm on arch, but this is news to me...need to check that out

14:11 <init_x13s> I had some weird behaviour the first time I installed it and if I remember I had to install one of the dependency separatly but it overall went all good. Then firefox drm plugin just activated itself and it worked like a charm after that.

14:11 <bamse> init_x13s: i was expecting that you needed some actual support for tz or the likes to do widevine...

14:11 <bamse> init_x13s: interesting, i couldn't get firefox to render properly when i tried last time...but that's quite a while ago

14:12 <init_x13s> X or Wayland?

14:12 <bamse> wayland

14:12 <init_x13s> I reverted to X, wayland was way too slughish for my taste.

14:12 <HdkR> bamse: I guess I never tried actually playing anything but the UI came up when I was poking around. I don't use it personally

14:12 <init_x13s> only on this laptop however, my ryzen one is on wayland and the intel one at work also is.

14:13 <bamse> i had rendering artifacts in x and robclark was running wayland...perhaps also something that has improved

14:13 <init_x13s> havent tested wayland back in a while tho.

14:13 <init_x13s> yeah. might re-give it a try . I also had a very annoying focus problem with guake under wayland

14:14 <bamse> so, on this subject...my gtk applications are flickering black whenever they are rendering...any suggestions?

14:14 <bamse> i think those are xwindows applications...

14:15 <bamse> it's just as if every window update first gives me one frame of black, and then it renders the content

14:15 <bamse> resizing windows are epilepsy inducing...

14:15 <HdkR> I don't get that under i3wm

14:17 <bamse> no problems with e.g. alacritty...but i tried playing kicad the other day, and it was not fun

14:22 <init_x13s> like I said, I had a lot of random issues with Wayland+Gnome. But my last test dates from februry, when the state of mesa/gpu acceleration was experimental at best.

14:24 <bamse> init_x13s: i haven't tried gnome...would be interesting as a comparison to see if it something caused by my "non-standard" setup (sway + xwindows/gtk apps)

14:25 <init_x13s> on 43.4, with X, the current state would be : seamless operation.

14:25 <init_x13s> and a good battery life.

14:25 <init_x13s> also a very good overall responsivity.

14:25 <bamse> but it does a good job rendering alacritty and chromium...which are the only two apps i use on a regular basis

14:26 <bamse> was a little bit sluggish before we got gpu...

14:27 <krzk> init_x13s: slack app is proprietary and there is non-intrusive alternative via Web so why would anyone need it on your Linux system?

14:28 <krzk> It's like encouraging weird, spyware apps to your PC when you have real alternative - sandboxed in browser...

14:28 <init_x13s> krzk: I cannot care less about the proprietary state of that software. I run a business that requires sync between 3 slack organization. The web app is really bad for that. I'm not complaining here, but this is something I hate.

14:29 <init_x13s> thanks for techsplaining me how I should use my computer.

14:35 <HdkR> ooo, that's a good term, I'll borrow that

14:42 <steev> X still has some minor issues here and there

14:43 <steev> sometimes my terminal sits there like it's frozen, but it just hasn't refreshed

14:44 <init_x13s> I'm trying to find a time slot to invest in debugging the resume functions from suspend-then-hibernate -> shutdown.

14:44 <init_x13s> from my readins, there shouldn't be any firmware related issued with that, as it's not really hardware bound.

14:45 <init_x13s> my initial tests shows issues with the gpu having a problem resuming, but that might not be a big problem.

14:54 <jhovold> init_x13s: heh, that's the first time I've heard that term too ('techsplaining')

14:55 <jhovold> init_x13s: regarding hibernate, a lot of driver are likely going to have to be amended as they all currently assume that a lot of state is retained. So getting hibernation to work may be easier said than done...

14:57 <init_x13s> jhovold: very good point, I'll try to stay as naive as possible until I sink a lot of time before realizing the difficulty of it. Otherwise I won't give it a look.

14:57 <jhovold> but as bamse alluded to the other day, we should be able to get pretty low suspend consumtion also using s2idle (as windows also uses). But that too is going to take a bit of work.

15:34 <_`[m]1> how do you get bt and audio drivers working?

16:05 <steev> audio requires the firmware, and alsa-ucm-conf configs, and bluetooth just requires the bluetooth firmware which should be in linux-firmware; that is, assuming you have the audio config options on