#
…

2024-01-20

01:34possiblemeatball has joined #asahi-alt
01:47RoundDuckKira has joined #asahi-alt
01:51matteo has quit [Quit: Leaving...]
02:43kidplayer666 has quit [Quit: Connection closed for inactivity]
02:46john-cabaj has joined #asahi-alt
02:54john-cabaj has quit [Ping timeout: 480 seconds]
04:17JayBeeFOSS has quit [Remote host closed the connection]
04:18JayBeeFOSS has joined #asahi-alt
05:18enick_78 has quit [Ping timeout: 480 seconds]
05:18rhysmdnz has quit [Ping timeout: 480 seconds]
05:28chadmed has quit [Ping timeout: 480 seconds]
06:13chadmed has joined #asahi-alt
06:13possiblemeatball has quit [Quit: Quit]
09:09rhysmdnz has joined #asahi-alt
09:10enick_78 has joined #asahi-alt
09:28cy8aerI expected the E core stuff would be "just in" the kernel. So I run without them because of CONFIG_UCLAMP_TASKS. I will build it in with the 6.6-15 and the actually in a merge request hanging new mesa.
09:29j`eycy8aer: UCLAMP allows userspace to give hints to the kernel
09:30cy8aerBut I habe a question for that too: "so pipewire can run on the E cores" - is that a global thing then because pipewire does/will do the video streaming stuff in future too. Ok with hardware acceleration that would work but without...
09:31cy8aerj`ey: ah I see.
09:34j`eychadmed: is the uclamp stuff for the whole of pipewire?
09:34j`eyor just the dsp stuff
09:35j`eybtw the E cores can decode 1080p happily
09:38chadmedj`ey: it will affect all of pipewire and wireplumber if set
09:39chadmedwhich is fine because again the ecores are more than happy doing up to 24/192
10:17leioI guess the question is - will it be fine doing 4K screen sharing and libcamera integration
10:42cy8aerAs I understand is videopiping ok with pipewire. The problems are with the sinks. And if they use hardware acceleration (@eiln is working on it) the whole video stuff will be low power too and would work fine with higher resolutions IMHO.
10:51eilnye avd can do up to 4K (I think M2 had 8K?). though I feel the bigger gains with avd are power savings
10:51eilnavd can't do everything though. we still have to do some things ourselves e.g. vp9 probability adaptation/merging (apple didn't add silicon for that). all that can stick to an e-core. I don't think apple does fancy scheduling for video
10:51eilnI've also talked to m arcan about zero-copy frame dma out (which would be natural if this does end up on the mesa side)
10:56j`eyyay for even less CPU usage
11:11u154ss has joined #asahi-alt
11:16u154ss#j'ey/cy8aer who will build the newest mesa to match linux 6.6-15? I tried Glanzmann's script bumping the release using tag asahi-20231213. It is still producing version 22.x.x .debs however. The Fedora fc39 is already using mesa version 24.x.x as far as I can see.
11:18u154ssBackgroung being I want to run Debian/XFCE on my M2 Mini. Fedora FC39 works on the M2 Mini, but I do not want this setup, prefer Debian...
11:19u154ssBackgroung = background.
11:19cy8aerI would build it if it "is out" - as I see the merge request is still open. And my mesa version will be 24 - as my 20231213 too. But my naming is not really right I guess.
11:19cy8aerSo actually I am "on hold" and waiting for the mesa patch
11:21u154ss@cy8aer using tag 20231213 why are version 22.x.x .debs being produced then? Scratches head..
11:22u154ss@cy8aer I saw the merge request already. Thanks.
11:25cy8aerThe package version depends on https://git.g3la.de/repos/m1-debian/src/branch/baer/mesa.sh line 31. And I try to be higher than the last debian package there. Probably I will follow the fedora version numbers in future time.
11:26cy8aerThe used patches are out of the official version numbering so it is a bit nifty to give a plausible version number
11:27cy8aerMesa version itself is 24.0.0-devel
11:30u154ss@cy8aer the script https://git.g3la.de/repos/m1-debian/src/branch/baer/mesa.sh is more or less the same as Glanzmann's script. There is no guarantee should I build kernel 6.6-15 and the latest mesa stuff that XFCE/X11 will run on the M2 Mini. My thoughts..
11:32j`eyu154ss: yes -15 won't fix anything there, pretty sure
11:32cy8aerI am working with a fork of the Glanzmann scripts. And the 20231213 is a bit backported to the Glanzmann repo because there were some documentation files missing which I just kicked out of the packaging.
11:33hightower2 has quit [Ping timeout: 480 seconds]
11:37u154ss@j'ey - to recap - on the M2 Mini using Fedora fc39, KDE(Plasma) and XFCE/X11 work, Debian/XFCE does not (libunwind -10 segfault etc.). I am wondering whether Debian/XFCE will ever run on the M2 Mini. Again, Fedora/KDE is too bloated/top-heavy for me.
11:38u154ss@cy8aer I see that. Gut.
11:38j`eyu154ss: No idea, but it won't run unless a) it's solved by accident b) someone figures it out
11:39j`eydepends what's more important for now, Debian/???? or Fedora/XFCE
11:39u154ss@j'ey my thoughts/worst fears exactly.
11:40j`eywe know that it's possible since Fedora/XFCE works, so it's hard to tell where the exact issue would be, lots of different packaging differences
11:41u154ss@j'ey not that I am resistant to change, but I prefer to run lean-and-mean anyway. My mainframe mentality.
11:42j`eythat's fine :)
11:45u154ssThis is my memory usage/allocation, just after startup on the M1 Mini - Memory: 243568K/16287488K available (6976K kernel code, 770K rwdata, 1520K rodata, 704K init, 418K bss, 230912K reserved, 0K cma-reserved)
11:45qyliss has quit [Quit: bye]
11:46u154ss@j'ey, I would prefer to keep thing that way on the M2 Mini also. I have 24GB on the M2 Mini.
11:46mpsI've made mesa-asahi 24.0.0_pre20231213 version for alpine
11:46qyliss has joined #asahi-alt
11:46j`eyu154ss: Im not really sure what to say, you pretty much just have 2 options
11:47u154ss@j'ey - or no options.. :)
11:47u154ss @j'ey - at the moment.
11:55u154ss@mps have you tested your setup (24.0.0_pre20231213) on a M2 Mini?
11:55mpsu154ss: no, I don't have M2
11:55u154ss@mps OK.
11:56mpsbut on M1 and M1pro it works fine
11:56u154ss@mps the M2 Mini is a different (hardware) beast methinks.
11:57mpsbut if fedora works I don't see reason why debian will not
11:58hightower2 has joined #asahi-alt
11:58u154ss@mps different distribution/mesa version/kernel/hardware - a lot of variables there.
11:59maxg_ has joined #asahi-alt
11:59maxg_ has quit []
11:59maxg_ has joined #asahi-alt
11:59mpsIDK if anyone run alpine on M2 to ask
12:00j`eyIm not sure what that will give you anyway, if it works on alpine.. then what? :)
12:01mpsand alpine uses different libc than others but anyway everything works, no one posted bug report at least
12:13qyliss has quit [Quit: bye]
12:15qyliss has joined #asahi-alt
13:09maxg_ has quit [Quit: maxg_]
13:14u154ss has quit [Remote host closed the connection]
13:55possiblemeatball has joined #asahi-alt
13:59mkurz has quit [Ping timeout: 480 seconds]
14:27RoundDuckKiradoes asahi use rust code as part of the development of the Asahi drivers
14:27RoundDuckKiraI have a feeling void linux doesn't use rust by default
14:27j`eyyes for the GPU
14:28j`eymost distro's wont enable rust in the kernel yet
14:28j`eyI would just run without the GPU to start with
14:28Leo3418 has quit [Quit: Applying updates]
14:29RoundDuckKiraI may need to ask the void devs if it's possible to change the template to allow rust compile
14:29RoundDuckKirathe GPU is a big one
14:29j`eywell youre going to need a 'fork' of the kernel anyway for some time, so you dont really need to modify upstream void for that yet
14:29Leo3418 has joined #asahi-alt
15:03RoundDuckKirawell idk how the fedora kernel is made that's for sure\
15:03RoundDuckKirabtw patching the void kernel was where it failed it
15:03RoundDuckKirait failed to patch
15:04RoundDuckKirawhat's asahi-6.6-15 supposed to be
15:04RoundDuckKirav6.6 is the pure 6.6.0 kernel right?
15:05RoundDuckKiraand asahi-6.6-15 is the modified one with the latest asahi patches right?
15:08j`ey-15 needs some mesa changes for GPU, but I think you can ignore that if you just go for software rendering to start off
15:10RoundDuckKirayeah I just am focusing on booting into a tty merely at first
15:10RoundDuckKiratho I do want kernel side gpu support working
15:10RoundDuckKirajust get that mess out of the way
15:21RoundDuckKirahey btw j`ey, you know lactose here right? The thing is we both started projects to get weird Linux distros working on Asahi, she's a friend of mine from discord. The reason I am asking is I'm asking that did she ever say about how she got the Asahi kernel working with slackware, I wonder if there's some info I can glean to help me with this task
15:22j`eyRoundDuckKira: I cant remember what they did in the end
15:23j`eytbh most of the kernel build is pretty easy, and you can probably boot to a tty without many special options
15:23j`eyand then you can slowly add more as you go
15:25j`eyI think starting by just building the tree directly, rather than trying to get the diff and patch a tree is also good to start with
15:27RoundDuckKiraj`ey: https://termbin.com/j8tb here's the output of my patch attempt and fialure
15:27RoundDuckKirathis is me patching the 6.6.13 kernel with the asahi 6.6-15 stuff
15:28j`eyyeah, I think this is a good example of why it's better to focus on building the asahi tree directly first
15:28j`eythat's the important bit
15:28RoundDuckKirawell I can build that fine with dependenciesz
15:28RoundDuckKiraI just want it to work on a newer kernel base
15:29j`eyit sounded like you hadn't gotten a kernel working at all yet?
15:31j`eybut yeah, 6.6.13 changed that file, and so has asahi, that's why it conflicts
15:34j`eyRoundDuckKira: fedora is based on 6.6.3 it seems, that change conflicted since 6.6.7
15:34j`eyyou could try base it on v6.6.6
15:44lynndotpy has quit [Quit: bye bye]
15:45lynndotpy has joined #asahi-alt
15:54RoundDuckKirayeah I don't have a working kernel
15:55RoundDuckKiraand v6.6.6 lol
15:55RoundDuckKirathe satanic linux lol
16:06psykose has quit [Remote host closed the connection]
17:35maxg_ has joined #asahi-alt
19:40maxg_ has quit [Remote host closed the connection]
19:49jacksonchen666 has joined #asahi-alt
19:57KxCORP has quit [Quit: Bye!]
19:57KxCORP has joined #asahi-alt
20:15possiblemeatball has quit [Quit: Quit]
20:17possiblemeatball has joined #asahi-alt
20:40jacksonchen666 has quit [Quit: WeeChat 4.1.2]
20:43jacksonchen666 has joined #asahi-alt
20:43mike2578 has joined #asahi-alt
20:57mike2578 has quit [Quit: WeeChat 4.0.4]
22:42RoundDuckKiraj`ey: I tried 6.6.6 and still a conflict there oof
22:42RoundDuckKiragonna try 6.6.3
22:44j`ey6.6.6 didnt look it should, but .3 def shouldnt
22:44RoundDuckKiraye since asahi uses it
22:46ah- has quit [Read error: Connection reset by peer]
22:46ah- has joined #asahi-alt
22:47RoundDuckKirawhat the heck, even 6.6.3 fails
22:50j`eysame file?
…