#
…

2022-06-02

00:09dsrt^ has joined #asahi
00:17dsrt^ has quit [Remote host closed the connection]
00:18samil_karaduman[m] has joined #asahi
00:18samil_karaduman[m] has left #asahi [#asahi]
00:22derzahl has joined #asahi
00:24nehsou^ has joined #asahi
00:43derzahl has quit [Remote host closed the connection]
00:46AoV has joined #asahi
01:13ciggi has quit [Ping timeout: 480 seconds]
01:13bisko has joined #asahi
01:21bisko has quit [Ping timeout: 480 seconds]
01:31c10l has quit [Quit: Bye o/]
01:36c10l has joined #asahi
01:41nehsou^ has quit [Ping timeout: 480 seconds]
01:42derzahl has joined #asahi
01:45darkapex has joined #asahi
01:50Gaspare has joined #asahi
02:01derzahl has quit [Remote host closed the connection]
02:04derzahl has joined #asahi
02:15nehsou^ has joined #asahi
02:50PhilippvK has joined #asahi
02:53phiologe has quit [Ping timeout: 480 seconds]
02:54bisko has joined #asahi
03:02bisko has quit [Ping timeout: 480 seconds]
03:08ciggi has joined #asahi
03:18marvin24 has joined #asahi
03:22marvin24_ has quit [Ping timeout: 480 seconds]
03:29kov has quit [Quit: Coyote finally caught me]
03:36PyroPeter has joined #asahi
03:38pyropeter3 has quit [Ping timeout: 480 seconds]
04:12Gaspare has quit [Quit: Gaspare]
04:40ptudor has joined #asahi
04:47ptudor_ has quit [Ping timeout: 480 seconds]
04:54bisko has joined #asahi
05:02bisko has quit [Ping timeout: 480 seconds]
05:09jluthra has quit [Remote host closed the connection]
05:09jluthra has joined #asahi
05:28Ry_Darcy has quit [Remote host closed the connection]
05:29Ry_Darcy has joined #asahi
06:12nehsou^ has quit [Ping timeout: 480 seconds]
06:47the_lanetly_052___ has quit [Ping timeout: 480 seconds]
07:32thevar1able has quit [Quit: WeeChat 3.5]
07:33thevar1able has joined #asahi
07:42bisko has joined #asahi
07:46CaptainYukinoshitaHachiman[m]<CaptainYukinoshitaHachiman[m]> "Seems I can't install qemu..." <- ```... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/sedysvdZRFjLCvXjkjsbFloS)
07:48ktz_[m]well arch on arm is half-baked at least, at least that's my experience. a good majority of the packages simply won't run on aarch64
07:49boardwalk has quit [Quit: Ping timeout (120 seconds)]
07:49ktz_[m]you may want to take a look at alpine in case you get too frustrated. mps saying that arm is a first class citizen in alpine is right as per my experience so far as well
07:50boardwalk has joined #asahi
07:50bisko has quit [Ping timeout: 480 seconds]
07:58ktz_[m]<j`ey> "for those that missed it https:/..." <- hey what can you do with this?
08:01j`eyktz_[m]: it's just showing the first triangle produced from the m1 GPU, without using the macOS kernel
08:01ktz_[m]ahhh!! amazing then indeed gratz :)
08:03j`eylina is doing some great work, probably not too long before two triangles.. and beyond!
08:03ktz_[m]yeah great stuff well done
08:03CaptainYukinoshitaHachiman[m]<ktz_[m]> "you may want to take a look at..." <- Thanks! Actually I'm seeking to run some Windows apps and I don't know if there is any way to do that currently on Arch
08:04ktz_[m]check offtopic as well some nice news there too
08:04ktz_[m]well not sure about arch but I spent a couple of days trying to get it working on qemu and I was close
08:05nehsou^ has joined #asahi
08:05ktz_[m]I spent a lot of time reading qemu docs as well so it shouldn't take so much but I couldn't get past a point eventually, its doable I think tho
08:06j`eyCaptainYukinoshitaHachiman[m]: have you tried sudo pacman -Sy qemu-system-aarch64
08:08CaptainYukinoshitaHachiman[m]j`ey: Yes and I get the same error
08:09mpsktz_[m]: windows apps? I'm not sure wine runs on aarch64
08:09mpsfexemu could be solution
08:10ktz_[m]windows 10/11 on qemu
08:10ktz_[m]never heard of fexemu
08:11mpsfexemu is x86 emulator
08:12ktz_[m]well I guess running it on x86 will be a piece of cake
08:12mpsI started to port it on alpine/musl but lost interest
08:12derzahl has quit [Remote host closed the connection]
08:13mpsaccording to 'marketing' it should be (a lot) faster than qemu
08:13mpsbut will only emulate x86
08:13ktz_[m]if you have the zfs APKBUILD handy btw send it to me or try to compile it with the latest changes https://github.com/openzfs/zfs/commits/master I think it will build now
08:14ktz_[m]mps: ahh so it isn't related to qemu directly I see
08:14mpsktz_[m]: I'm not sure zfs have new release ready for 5.17 kernels
08:15ktz_[m]this is up to 5.18 supposedly
08:15mpsaha, maybe I will find time this evening to try with current asahi kernel, 5.18-rc5
08:16ktz_[m]they merged many commits from the 2.1.5 staging and I think they address the bio errors
08:16ktz_[m]send it to me if you can I'll try to do it
08:16ktz_[m]I somehow got it running too but no scripts available
08:16ktz_[m]I'm trying with zfs package instead of lts now
08:17mpsI have business meeting all the day, so don't have time till the evening
08:18ktz_[m]yes just cp the APKBUILD you have currently and I think I'll get it going
08:19mpsktz_[m]: btw, I fixed alpine linux-asahi-dev to use proper symlinks, did you upgraded it
08:20ktz_[m]yes I saw, good
08:20ktz_[m]thanks :)
08:21mps(last week I worked only on riscv64 kernel and u-boot, got first riscv SBC)
08:22ktz_[m]if there are any rules you can add to mdev would be nice, I cp'd a couple of them from here https://arvanta.net/alpine/libudev-zero/ but still can't get adb to see the phone
08:22mpswe could discuss this on #asahi-alt
08:23ktz_[m]let me join
08:24systwi has quit [Read error: Connection reset by peer]
08:25systwi has joined #asahi
08:36ptudor has quit [Remote host closed the connection]
08:37ptudor has joined #asahi
08:37f-fritz[m] has left #asahi [#asahi]
08:50snajpa has quit [Ping timeout: 480 seconds]
08:51povik has quit [Ping timeout: 480 seconds]
09:00bisko has joined #asahi
09:11nicklas[m] is now known as nIcKlAs[m]
09:16nIcKlAs[m] is now known as Pr[m]
09:19Pr[m] is now known as Nilsson[m]
09:37hir0pro has joined #asahi
09:41bisko has quit [Remote host closed the connection]
09:57n1c has quit [Quit: ZNC 1.8.2+deb1+focal2 - https://znc.in]
09:58n1c has joined #asahi
09:59rootbeerdan3 has joined #asahi
09:59rootbeerdan has quit [Read error: Connection reset by peer]
09:59rootbeerdan3 is now known as rootbeerdan
10:01Ry_Darcy has quit [Remote host closed the connection]
10:01Ry_Darcy has joined #asahi
10:13mpsktz_[m]: re: zfs, who merged 'many commits from the 2.1.5 staging and I think they address the bio errors'
10:47povik has joined #asahi
10:56kjellarne[m]How long time will the Asahi alfa take to install approximate?
10:57j`eyless than an hour
11:07_jannau_assuming the macOS partition resize works smoothly
11:11isdedev[m] has joined #asahi
11:11rowang077[m]Does linux have something equivalent to QoS settings for a thread/process?
11:11chadmedman nice
11:11rowang077[m]or is there onyl thread priority?
11:12chadmedthe scheduler takes care of "qos" under the hood, you can use the nice command to hint to the scheduler how you want certain things prioritised though
11:17rowang077[m]What does that mean in practice? Software not made for heterogeneous architectures will "waste" power/resources by running on P cores? Or does the scheduler see, this program doesn't need much researches so it gets moved to an E core?
11:18rowang077[m]Sorry if those are obvious questions. I have no linux experience with heterogeneous architectures.
11:20chadmedthe scheduler knows about the performance level of each core from the devicetree (we tell the kernel what each core can do)
11:21chadmedthe scheduler then shifts threads around based on their utilisation time/whether or not theyre sleeping/some other factors
11:22chadmedyou can of course manually set thread affinity to lock certain threads to certain cores if you really really want to minmax perf per watt
11:23chadmedif we had finer grained control over the CPU we could profile its energy use and then feed that into the Energy Model subsystem of the kernel which then makes scheduling decisions based on the core's perf/W and how much juice it thinks the thread needs
11:25chadmedcurrently we just use the standard performance level bindings for heterogeneous systems which is basically just a dimensionless scaling factor that tells the kernel how much more powerful the big cores are relative to the little ones
11:29kov has joined #asahi
11:34chadmedadding the core and cluster cost bindings to the dt for each op point isnt much work, its deriving the actual numbers accurately that would suck
11:34chadmedonce thats done you just have to write the energy model functions into the cpufreq driver and schedutil handles the rest
11:36nehsou^ has quit [Ping timeout: 480 seconds]
11:42nehsou^ has joined #asahi
11:45hir0pro has quit [Quit: hir0pro]
11:45hir0pro has joined #asahi
11:46hir0pro has quit [Remote host closed the connection]
11:46hir0pro has joined #asahi
11:50Ry_Darcy has quit [Remote host closed the connection]
11:54hir0pro has quit [Ping timeout: 480 seconds]
12:02chadmedoh lol you dont even have to do that anymore, cpufreq automagically gets it from the bindings now
12:08nehsou^ has quit [Ping timeout: 480 seconds]
12:11nehsou^ has joined #asahi
12:15c10l has quit [Quit: Bye o/]
12:25hir0pro has joined #asahi
12:26hir0pro has quit [Remote host closed the connection]
12:26hir0pro has joined #asahi
12:52snajpa has joined #asahi
13:16LinuxM1 has joined #asahi
13:19tsujpCan m1n1 be used to inject kexts?
13:31tsujpI guess the crux of my question is: can m1n1 boot macOS proper or is it "just" (for lack of a better word) compatible with Apple's UEFI or what have you, and then it's called from that
13:31svenyou can only boot xnu inside the m1n1 hv
13:32svenbut I guess you could inject kexts into the kernel ache you pass to run_guest.py
13:33tsujpSo I'm checking the wiki page for "SW:Hypervisor" sven and when it says "start into 1tr" that is a real macOS installation (per above steps on that page) but it was booted via m1n1?
13:34j`eyno, 1tr is not started via m1n1
13:34j`eybooting into 1TR is done so that you can install m1n1
13:35svenyeah, you have to have a real macOS installation and then replace XNU of that installation with m1n1 from 1TR
13:36tsujpOh right "1TR" is boot ID 1 "system/one true" recoveryOS
13:36tsujpI know basically nothing so trying to get started here is a bit tricky for me hehe
13:36svennot sure what boot ID 1 is but if you just remove that from your sentence you’re correct ;)
13:38svenlooks it’s just another name for the 1TR mode
13:38j`eycant you load custom kexts some other way?
13:38svennever heard about that before :D
13:38j`eytrying to understand why you want to do it with m1n1
13:38c10l has joined #asahi
13:44tsujpI was thinking about trying to get something like Lilu going which can live load and replace kexts but that uses OpenCore and that's x86 only
13:44tsujpI also thought any hacking I do with kexts on my m1 machine might be translateable to Asahi (idk how else to help) and I want to customise my m1 macos installation
13:48c10l has quit [Quit: Bye o/]
13:48j`eyguess it depends what kext hacking you do!
13:53hir0pro has quit [Quit: hir0pro]
14:06nehsou^ has quit [Ping timeout: 480 seconds]
14:49Gaspare has joined #asahi
14:59hir0pro has joined #asahi
15:05marcantsujp: one true yes, system no
15:05marcanthose two used to be related but no longer are, which is an endless source of confusion
15:06marcan1TR is *any* recoveryOS booted by holding down the power button, which usually is the paired recoveryOS for the default boot volume
15:06marcanjust updated the page
15:07marcanI wonder if we'll ever fix all references to that
15:08marcantsujp: you can build a custom kernelcache (with kmutil) and install it with kmutil itself, or you can load it with m1n1 as a chainload on bare metal, or run it under the hypervisor
15:08marcandon't think anyone has written the code to do what kmutil does
15:10marcanlive loading/replacing kexts, I have no idea how that goes. you definitely need to downgrade security to do that and disable kernel CTRR at least.
15:11guillaume_g has quit []
15:13marcanrowang077[m]: what macOS does isn't necessarily optimal for perf/W; depending on the situation running on the P cores and finishing faster can save energy
15:13j`eylina's been busy: 24 files changed, 3471 insertions(+), 615 deletions(-)
15:14marcanLinux just lets you set process/thread affinity, just use `taskset`
15:15^GaveUp^ has joined #asahi
15:15j`eygpudata is missing which means agx_1tri.py wont be runnable, but I guess her plan is to un-hardcode that stuff anyway
15:20TheFirst has quit [Ping timeout: 480 seconds]
15:20^GaveUp^ is now known as TheFirst
15:32marcanj`ey: I think you're supposed to get that by dumping a render from mesa on macos with that tooling
15:41Ry_Darcy has joined #asahi
15:43herbas has joined #asahi
15:44herbasHow does reverse engineering with m1n1 like on the recent gpu streams work? I have already seen many articles falsely claiming that the triangle was rendered with a linux kernel GPU driver, which is claimed to be false. What does m1n1 run? How does it run a python interpreter without a linux kernel apparently for the prototype GPU driver?
15:45j`eythe python runs on another machine, which sends commands via an RPC over usb
15:46j`eywhich m1n1 then executes as commands, to setup memory etc
15:46j`ey(m1n1 runs on an m1, python runs on any other machine)
15:54herbas has quit [Quit: herbas]
16:01opticronah, that makes sense, for some reason I was thinking m1n1 was running a super slim python backend
16:09LinuxM1 has quit [Ping timeout: 480 seconds]
16:13RevHelix has joined #asahi
16:13Gaspare has quit [Quit: Gaspare]
16:15Revy has quit [Ping timeout: 480 seconds]
16:18LinuxM1 has joined #asahi
16:48LinuxM1 has quit [Ping timeout: 480 seconds]
16:56LinuxM1 has joined #asahi
17:06LinuxM1 has quit [Read error: Connection reset by peer]
17:07LinuxM1 has joined #asahi
17:08c10l has joined #asahi
17:08LinuxM1 has quit [Read error: Connection reset by peer]
17:13LinuxM1 has joined #asahi
17:13hir0pro has quit [Quit: hir0pro]
17:15trouter has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:19trouter has joined #asahi
17:21LinuxM1 has quit [Ping timeout: 480 seconds]
17:31LinuxM1 has joined #asahi
17:50c10l has quit [Quit: Bye o/]
17:52LinuxM1 has quit [Read error: Connection reset by peer]
17:54Gaspare has joined #asahi
17:57c10l has joined #asahi
18:03LinuxM1 has joined #asahi
18:06c10l has quit [Quit: Bye o/]
18:10c10l has joined #asahi
18:12LinuxM1 has quit [Quit: Leaving]
18:34c10l has quit [Quit: Bye o/]
18:36hir0pro has joined #asahi
18:39trouter has quit [Quit: ZNC 1.8.2 - https://znc.in]
18:41trouter has joined #asahi
18:48rootbeerdan6 has joined #asahi
18:52rootbeerdan has quit [Ping timeout: 480 seconds]
18:52rootbeerdan6 is now known as rootbeerdan
19:56bisko has joined #asahi
20:04bisko has quit [Ping timeout: 480 seconds]
20:18james has joined #asahi
20:19james is now known as UnicornsOnLSD
20:27UnicornsOnLSDHi, sorry if this is a common question but does Gnome Wayland work? I got some very weird graphical glitches
20:40jannauUnicornsOnLSD: in principle yes but the current mesa release in arch linux arm has bugs in the software renderer
20:42Gaspare has quit [Quit: Gaspare]
20:43hir0pro has quit [Quit: hir0pro]
20:43jannaushould be fixed when mesa 22.1.1 in in arch linux arm
20:43hir0pro has joined #asahi
20:44Gaspare has joined #asahi
20:51hir0pro has quit [Ping timeout: 480 seconds]
21:05UnicornsOnLSDThat's great, time to test Mesa compile time on this laptop 🙃️
21:22roxfan2 is now known as roxfan
21:24bisko has joined #asahi
21:28Gaspare has quit [Quit: Gaspare]
21:32bisko has quit [Ping timeout: 480 seconds]
21:40UnicornsOnLSD has quit [Quit: UnicornsOnLSD]
21:42bisko has joined #asahi
21:43james has joined #asahi
21:44james is now known as UnicornsOnLSD
21:44bisko has quit []
21:45UnicornsOnLSDWorking great, here's a PKGBUILD if anyone else wants to do the same :) https://paste.gnome.org/11BoiGd1u
21:45UnicornsOnLSDNote that I just skipped hashes/signatures, shouldn't be too big of an issue though
21:47UnicornsOnLSD has left #asahi [#asahi]
21:48james has joined #asahi
21:48james is now known as UnicornsOnLSD
21:49UnicornsOnLSD has quit []
21:55yuyichao has joined #asahi
22:11trouter has quit [Ping timeout: 480 seconds]
22:16bisko has joined #asahi
22:17trouter has joined #asahi
22:43c10l has joined #asahi
23:08trouter- has joined #asahi
23:12trouter has quit [Ping timeout: 480 seconds]
23:16vmeson has quit [Quit: Konversation terminated!]
23:19vmeson has joined #asahi
23:26Skirmisher[m]I've been wondering... since M1 family doesn't support aarch32 mode, would it still be possible to run some sort of aarch64ilp32 chroot/multilib (analogous to what the "x32" Linux ABI does) to aid the likes of FEX/box86 library thunks?
23:27Skirmisher[m]since people are talking about x86 emulation lately what with The First Triangle happening, I was reminded of that idea
23:29opticronthat doesn't really do anything for you since while the M1 can run ILP32, it's really only cutting down the available memory space
23:30opticronit's still the same instructions and *MMU configuration
23:33opticronI don't know for certain that the kernel doesn't map memory differently in that mode, but I thought I read that it doesn't
23:35Skirmisher[m]true, but then is the bottleneck different between ia32->aarch64 and x86_64->aarch64? you need a different dynarec, but after that it seems like the main difference is different data/pointer sizes
23:42opticronfrom what I can tell, x86 assumes a page size of 4k though 2m or 1g are available on some systems. both will have the same problem unless the x86 native code is written for the other page sizes
23:43Skirmisher[m]that's true, but that's orthogonal to the instruction set and ABI, no?
23:44Skirmisher[m]page size is already something that will be solved at one level or another (people working on kernel patches, box64 works on 16k pages I think)
23:44Skirmisher[m]*kernel patches for 4k on M1
…