#
…

2022-08-04

00:11babble has quit [Remote host closed the connection]
00:11babble has joined #asahi
00:18pi1 has joined #asahi
00:19pi1hi. is it possible to test asahi on an m1 mac without destroying the native installation?
00:20tpw_rulesyes, in fact you shouldn't touch the native installation
00:21pi1so the installer will help me create a dual boot setup or>
00:21tpw_rulesdual boot is the only supported setup
00:21pi1i'm highly skeptical of installers after messing with the debian one last week
00:21tpw_ruleswhich one?
00:21pi1so i want to be absolutely 100% sure i undersatnd everything before trying asahi
00:21tpw_rulesafaik, debian on m1 is all manual. but that's kind of a problem if there is a broken automated installer
00:22pi1no i mean on x86
00:22qeeg__ has quit [Remote host closed the connection]
00:22pi1i was testing the installer in a vm with varying amounts of memory. the behavior was somewhat inconsistent.
00:22qeeg__ has joined #asahi
00:22tpw_rulesthe official asahi installer is pretty much completely safe. i think still the only reports i've seen of people who severely broke their machines are people who messed up with a partition editor once they got linux installed
00:22pi1so i wouldn't be surprised if i ran the asahi installer and it wiped my m1 install. that's just how things are in linux land
00:23pi1your confidence is reassuring
00:23tpw_rulesno, it's very straightforward
00:23tpw_rulesbut it's always good to have backups ;)
00:23pi1frankly my opinion of computing is so low i consider backups mandatory.
00:24pi1but thanks i will investigate further. is the wiki good?
00:24tpw_rulesi don't think it's super relevant to an ordinary user
00:25ptudor_ has quit [Read error: No route to host]
00:27tpw_rulesbtw if you do severely break your machine, you'll need access to another one and a usb cable with at least one C end to restore the mac. the other machine can be a VM and/or run linux (not sure about windows).
00:29nicolas17that's an interesting question, idk if anyone has tried it on windows
00:29babble has quit [Read error: Connection reset by peer]
00:29pi1would a laptop running linux suffice? or maybe a bsd?
00:29tpw_rulesi'm not sure about a bsd either, but yes anything running linux should work
00:30tpw_rulesi've thoroughly tested running idevicerestore from computers and VMs with linux and macos and aarch64 and x86_64 cpus
00:31tpw_rules(and wrote a guide)
00:31ptudor has joined #asahi
00:33qeeg__ has quit [Remote host closed the connection]
00:33qeeg__ has joined #asahi
00:39doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
00:42tpw_ruleslooked through the wiki and it is actually pretty cleaned up and good looking now
00:42tpw_rulesat least check out the FAQ
00:45nicolas17 has quit [Quit: Konversation terminated!]
00:45nicolas17 has joined #asahi
00:47jluthra has quit [Remote host closed the connection]
00:48jluthra has joined #asahi
01:05jjleahy has joined #asahi
01:06jjleahy has left #asahi [#asahi]
01:28minecrell has quit [Quit: Ping timeout (120 seconds)]
01:28minecrell has joined #asahi
01:29qeeg__ has quit [Remote host closed the connection]
01:29qeeg__ has joined #asahi
01:44babble has joined #asahi
01:50babble has quit []
01:52dviola has quit [Quit: WeeChat 3.6]
01:54ciggi has quit [Ping timeout: 480 seconds]
01:55ciggi has joined #asahi
02:36phiologe has joined #asahi
02:39PhilippvK has quit [Ping timeout: 480 seconds]
03:11marvin24 has joined #asahi
03:15marvin24_ has quit [Ping timeout: 480 seconds]
03:25Stroller has quit [Quit: Stroller]
03:36pyropeter2 has joined #asahi
03:36julio7359 has quit [Ping timeout: 480 seconds]
03:38pyropeter1 has quit [Ping timeout: 480 seconds]
03:44julio7359 has joined #asahi
04:18amwThis link says some apple tools don't like partition tables entries out of order - https://github.com/AsahiLinux/docs/wiki/Partitioning-cheatsheet#physical-disk-layout-on-apple-silicon
04:19amwMine are out of order - should I worry and try to re-order them (sounds bit dangerous) as I haven't been bitten by anything yet.
04:24tpw_rulesafaik "don't like" is limited to displaying incorrect info
04:24tpw_rulesi don't think any of them will actually mangle data but i'm not convinced
04:25tpw_rulesin any case it's an easy operation to fix, assuming you used something other than partition numbers in your fstab
04:25tpw_rulesyou can also do sgdisk --sort /dev/nvme0n1
04:27doggkruse has joined #asahi
04:30qeeg has joined #asahi
04:31qeeg__ has quit [Read error: No route to host]
04:39mini0n has joined #asahi
04:40amwtpw_rules: Thanks - that worked - step 1. switch to labels, step 2. sgdisk (step 0 was installing sdisk package for sgdisk!)
04:40bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:48Ry_Darcy has joined #asahi
04:55Ry_Darcy has quit [Quit: Page closed]
05:17Rame has joined #asahi
05:24nicolas17 has quit [Remote host closed the connection]
05:24nicolas17 has joined #asahi
05:29mini0n has quit []
05:46rvalue has quit [Remote host closed the connection]
05:46rvalue has joined #asahi
05:55nicolas17 has quit [Quit: Konversation terminated!]
06:07L1Q has joined #asahi
06:29doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:38the_lanetly_052 has joined #asahi
06:54guillaume_g has joined #asahi
07:23mazamarioguy: maintenance interrupts have always been supported, even on M1, and I've always seen them firing. They are simply not represented as a Linux IRQ, but we don't care about that for KVM.
07:23mazall we need is for the FIQ to fire and get us out of the guest. the source of the interrupt will be disabled long before there is anything to handle.
07:24mazand the M1 bug only shows if you violate the GICv3 state machine, such as EOI a non active interrupt.
07:26mazas the M1 implements SEIS, it will deliver an SError. But instead of delivering a *virtual* SError, it delivers a physical one. please see the Linux commit message for the gory details.
07:31MajorBiscuit has joined #asahi
07:43mazj`ey: yeah, this only indicates the lack of a *Linux* maintenance IRQ, because the traditional way to represent it is to expose it from the GIC itself. here, the signal comes directly from the CPU, unfiltered by AIC, and we simply don't represent it in the DT. Hence, no Linux view of that signal.
07:43Ry_Darcy has joined #asahi
07:44mazhowever, the signal very much exists, and is extensively used to manage the vgic.
07:48j`eyaha, normally the vGIC maintenance IRQ is in the irq controller node in DT (looking at Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml)
07:50j`eymaz: so, with more code, this could be used, but there's no need really
07:55mazj`ey: yeah, it is absolutely pointless, because this is not a synchronous signal. it means that you absolutely need to inspect the vgic state on every exit. so we simply enable the interrupt at boot time (because the GIC otherwise gates it), and forget about it. on M1, we do nothing, which is the bestest.
08:11L1Q has quit [Ping timeout: 480 seconds]
08:14qazws[m] has joined #asahi
08:14qazws[m]hello, I seem to have stumbled on a language problem when installing the alpha.
08:15qazws[m]nevermind, I have reread it and I have stumbled on a wetware issue. all good now
08:19bisko has joined #asahi
08:28Techcable has quit [Remote host closed the connection]
08:30Techcable has joined #asahi
08:43Major_Biscuit has joined #asahi
08:44MajorBiscuit has quit [Ping timeout: 480 seconds]
08:49NikolayNikolaev[m] has joined #asahi
09:33bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:44bisko has joined #asahi
09:48psykose has quit [Remote host closed the connection]
09:49bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:49psykose has joined #asahi
10:14bisko has joined #asahi
10:21cupra has joined #asahi
10:22bobmaster[m] has joined #asahi
10:27cupra has quit [Quit: Leaving...]
10:51Ry_Darcy has quit [Remote host closed the connection]
10:53a_plastic_bag has joined #asahi
11:03bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:04a_plastic_bag has quit [Quit: Textual IRC Client: www.textualapp.com]
11:08a_plastic_bag has joined #asahi
11:09a_plastic_bag has quit []
11:22bisko has joined #asahi
11:25a_plastic_bag has joined #asahi
11:25a_plastic_bag has quit []
11:30bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:42a_plastic_bag has joined #asahi
11:47a_plastic_bag has quit []
11:47a_plastic_bag has joined #asahi
11:49a_plastic_bag has quit []
12:19Ry_Darcy has joined #asahi
12:22Moprius has joined #asahi
12:23bisko has joined #asahi
12:35rvalue has quit [Read error: Connection reset by peer]
12:35rvalue has joined #asahi
12:38julio7359 has quit [Ping timeout: 480 seconds]
12:38julio7359 has joined #asahi
12:48julio7359 has quit [Remote host closed the connection]
12:50amwIn https://github.com/AsahiLinux/docs/wiki/Yaks-in-need-of-shaving it points to the PASemi i2c driver but in the configurations I never see it - CONFIG_I2C_PASEMI compiled in?
12:51amwIs that Yak extinct now?
12:59sveni2c_apple uses that as well
13:02babble has joined #asahi
13:04cjones2 has joined #asahi
13:06cjones1 has quit [Ping timeout: 480 seconds]
13:11doggkruse has joined #asahi
13:20Moprius has quit [Quit: bye]
13:25mini0n has joined #asahi
13:38bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:55whynothugoWhat's missing for display backlight control to work?
14:03bisko has joined #asahi
14:15bisko has quit [Ping timeout: 480 seconds]
14:24Stroller has joined #asahi
14:24amarioguymaz: ahh gotcha that makes sense
14:24babble has quit [Remote host closed the connection]
14:25babble has joined #asahi
14:28dottedmagwhynothugo: display controller driver (= huge amount of work still)
14:41babble has quit []
14:43chadmed has quit [Remote host closed the connection]
14:43chadmed has joined #asahi
14:45thenailedone has joined #asahi
14:46whynothugoThanks, I guess I'll have to wait -- it's not even something in which I can contribute.
14:48nehsou^ has quit [Ping timeout: 480 seconds]
14:52the_lanetly_052 has quit [Ping timeout: 480 seconds]
14:52thenailedoneHi all, good thing Konversation doesn't require the hash before a channel name as I haven't been able to figure out how to make one on this imac GB keyboard I am using >.<
14:56StrollerI remember when I got my first mac - I was asking on IRC where the hash key was and people were asking "do you mean the pound sign" and I was like "no, I have £, I'm talking about the hash sign for comments in code"
14:57StrollerIt's option-3, thenailedone
14:59thenailedoneHi Stroller - option 3 hasn't been working for me. I tried most of the apple keyboard options available and just can't get it to show up... but thanks for the anwer :)
15:00Willmish[m]Stroller: Lol i had the same problem
15:00thenailedoneoh snap, right hand option it works, left it doesn't
15:00Willmish[m]Hm, maybe u remapped the left one?
15:01StrollerIt's option-3 on my 2018 Macbook (left hand option too), but I think they changed the keyboard arohnd a bit on the M2
15:01StrollerThe fn key works as an emoji button on the latter - I haven't started using it peroperly yet
15:02thenailedonehaven't touched any of the defaults on this system (mostly playing about to see how well it runs and it is amazing so far) so no keybaord mapping etc. But glad I can now make # and € symbold :p
15:03Willmish[m]Stroller: Oh yeah I found it’s the most pointless thing ever, I just remapped it to change input source as I use GB/Polish keyboard
15:03tpw_rulescould this be a bug? iirc there is some special sauce to automatically determine and apply the correct keyboard layout in asahi
15:04thenailedoneNow my next issue is more of a mystery. I canplay youtube vids embedded on other sites (like reddit) but I can't open youtube directly. www.youtube.com gived me an unable to connect message and says try again later (bith chromium and firefox)
15:05guillaume_g has quit []
15:09NikolayNikolaev[m]Are there any pointers of what needs to be done to compile the kernel from the asahi branch. I am running debian with 5.19-rc7 kernel and tried multiple times and its always no WLAN interface.
15:10tpw_rulesare you using 16k pages?
15:10_jannau_NikolayNikolaev[m]: most likely configure page size as 16k
15:12NikolayNikolaev[m]Will try that. Thanks. But my /boot/config is hmm using 4k. Will double check it.
15:13tpw_ruleswifi won't work if you use 4k pages. you have to use 16k
15:14svenmaybe we should add a dev_warn print to the dart driver if a dart without bypass support is probed on a 4k kernel
15:15svenor maybe even if the force_bypass/supports_bypass check is triggered in device_attach
15:19babble has joined #asahi
15:32surgeon has joined #asahi
15:41surgeon has quit [Quit: Reconnecting]
15:41surgeon has joined #asahi
15:44thenailedone has quit [Quit: Konversation terminated!]
15:46kefu-away is now known as kefu
15:46NikolayNikolaev[m]Thank you all, 16k made WLAN being discovered.
15:49mpswifi works fine with 4K and 16K page size
15:50tpw_rulesif you patch the kernel appropriately
15:50svenyes, with the upstream kernel or the asahi kernel WiFi will not work with 4k
15:51sven I guess it actually won’t work at all with the upstream kernel because the patches haven’t landed yet :D
15:53babble has quit []
15:53mpssven: with Glanzmans rebased patch it works
15:53svenofc, I wrote that patch
15:53mpsyes, I know :)
15:54svenbut the point of the discussion above was that WiFi won’t work with 4K unless you apply some more patches
15:54surgeon_ has joined #asahi
15:55surgeon_ has quit []
15:58NikolayNikolaev[m]So, is there an option for the asahi branch to adopt that patch?
15:58mpshmm, I only added this one
15:59mpsand font one, unrelated
15:59mpsfonts*
15:59tpw_rulesno, the official asahi stance and of most people is to use 16k. it's noticeably faster and most of the problematic software has been fixed
16:00mpsyes, I only boot 4K kernel when have to work with F2FS
16:02probieDoes anyone know off the top of their head which is the minimum version of electron that will work with 16k pages?
16:03sventechnically the 4K patch is like 6 patches but people have been merging it into a single patch file for reasons I don’t understand
16:04jannausingle patch or mbox of 6 patches?
16:05surgeon has quit [Quit: Lost terminal]
16:05svenSunfle
16:05sven*single patch unfortunately
16:06marcanwe will start offering 4K kernels when they start being useful for e.g. FEX in practical situations (e.g. once the GPU driver is good enough to run games / x86 software)
16:06marcanuntil then, there is approximately zero reason to use 4K kernels other than as a workaround for broken software, and that software needs to get fixed
16:06jannauprobie: I think 19 but it might have been backported to 18, not sure if offciaclly or just some high rofile cases like vscode
16:07surgeon[m] is now known as surgeon
16:07sventhe patch will probably also fail in interesting ways once thunderbolt is up fwiw :D
16:07marcanvscode/electron/etc got fixed because we shipped 16K kernels. if we'd been shipping 4K kernels they wouldn't have.
16:07marcanalso that.
16:07marcanplus gpu stuff (IIRC DRM was one of the corner cases?)
16:07surgeon has quit [Quit: Reconnecting]
16:07surgeon has joined #asahi
16:07svenI’m not sure the patch that is floating around has the safety check for untrusted devices
16:08svenyeah, but DCP just needs to stop abusing the dma api
16:08marcanjannau: it got officially backported but only partially, so it doesn't work
16:08marcanoh, was it DCP?
16:08marcanI thought it was a general DRM thing
16:08marcanwith some scatter-gather list stuff
16:08svenit depends
16:08svendcp clearly abuses that api
16:09probieThe codebase I need to get running is currently on 13. It's going to be a long night
16:09svenI don’t think drm uses it in general, just some drivers iirc
16:10psykoseif you build electron yourself, apply that to the chromium tree
16:10marcanthat patch is not sufficient
16:10psykoseif it doesn't apply, then have fun
16:10psykoseand yes, there's a few more
16:11jannauswitching to an unmanaged iommu domain is the main todo item for dcp for me I just don't get to it
16:13psykoseyou can also disable the partition alloc and try that if you want
16:14svenjannau: yeah, that’s also a fairly big change unfortunately:(
16:15NikolayNikolaev[m]I guess 64k is out of the question with m1/m2? Even just for basic CLI?
16:15svenbut that reminds me that I have to add an api to allocate unmanaged domains with a page size mismatch once I eventually get back to that 4K patch
16:16jannauNikolayNikolaev[m]: 64k is not supported by the hw
16:20svenhm, that reminds me: didn’t you want to look into making WiFi untrusted as well because Broadcom, marcan?
16:22Rame has left #asahi [Leaving]
16:22marcanwe are absolutely not shipping kernels that will allow that thing in passthrough mode. nope. not going there.
16:23marcansven: does the 4K patchset put it in passthrough right now?
16:23marcanif so, then yeah, that's a hard nope
16:23svenit doesn’t work at all with that patch set because those iommus don’t do pass through
16:24svenbut if brcmfmac uses non-coherent mappings anywhere it’ll still expose adjacent memory
16:26marcanah, right
16:26marcanwe should be able to fix that with subpage protection, right?
16:27svenyeah… it seems to use dma_map_single at least in one place to map < PAGE_SIZE buffers so it’ll already expose something adjacent
16:28svenyeah, just need to pass through the page offset/size all the way to the iommu driver
16:28marcanin the interim, untrusted mode would make it use swiotlb?
16:28svenyup, for dma_map_single at least
16:29marcanprobably a good idea for now then
16:29* marcanhopes that DART split patchset gets in already...
16:29marcanit's going to make our life a lot easier
16:29svenbut the code is smart enough to use direct mappings for anything dma_alloc_coherent and anything that happens to be page aligned
16:38jannauI need to send a new roll of the iopgtbl-dart patchset, got carried away by Robin's review comments
16:41sveniirc joerg picks up new code between rc4 and 6(?). Still some time left ;)
16:46Major_Biscuit has quit [Ping timeout: 480 seconds]
16:51Foresia has joined #asahi
16:56Foresia has left #asahi [#asahi]
17:41kettenisdidn't realize how fortunate we are in BSD land with the bus_dma(9) API
17:51___nick___ has joined #asahi
17:52___nick___ has quit []
17:54___nick___ has joined #asahi
18:55pi2 has joined #asahi
18:57pi1 has quit [Ping timeout: 480 seconds]
19:16stellarorbit[m] has joined #asahi
19:18stellarorbit[m]Hello, I have a question. I installed m1n1 and u-boot via the 3rd option in the script so I could install OpenBSD to test it out and i was wondering what the preferred way to update u-boot and m1n1 would be since I am not using asahi linux on my m1 mac mini
19:19cabbage has joined #asahi
19:42kettenisit is relatively easy to copy an updated m1n1.bin to the ESP; could provide that as a package
19:45jannauit depends on you keeping the dts in u-boot up to date
19:51kettenisI think stellarorbit meant "asahi linux" as a linux distro
19:52kettenisalthough checking out the asahi linux tree just to build the dtb isn't optimal
19:57cabbage has quit [Ping timeout: 480 seconds]
20:03lilly has joined #asahi
20:04Stroller has quit [Quit: Stroller]
20:07___nick___ has quit [Ping timeout: 480 seconds]
20:09jannauyes, I ment would not want to create a asahi-linux package just to update the dtbs
20:12eeqk[m]would you recommend any books that would make it easier for me to contribute some features into this project?
20:12eeqk[m]I'll soon have 2 weeks without an access to my laptop, that's why for now simply cracking on with the code is not an option for me
20:12eeqk[m]FYI my background is with high level programming languages, I'm a full stack+mobile dev
20:22rvalue has quit [Read error: Connection reset by peer]
20:22rvalue has joined #asahi
20:22lilly has quit [Remote host closed the connection]
20:25Chainfire has joined #asahi
20:25Major_Biscuit has joined #asahi
20:26Chainfireis it safe yet to upgrade to the macOS 13 beta with a fully updated Asahi?
20:27bisko has joined #asahi
20:32mini0n has quit [Read error: Connection reset by peer]
20:41princesszoeyworks fine for me Chainfire
20:43jannauChainfire: yes, both asahi and asahi-dev have the necessary fixes for u-boot and kernel
20:45nehsou^ has joined #asahi
20:47princesszoeyI can't believe how fast asahi is, it's nuts.
20:47princesszoeyeven compiling AUR stuff is like blink and you miss it
20:57nehsou^ has quit [Ping timeout: 480 seconds]
21:09Stroller has joined #asahi
21:12doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:13Major_Biscuit has quit [Remote host closed the connection]
21:14Major_Biscuit has joined #asahi
21:14doggkruse has joined #asahi
21:15ChainfirePossibly offoptic: So, imagine I have lots of k8s services based on dockerfiles based on x64 images I can't easily port. Any recommended way to test/run/dev these on M1? We don't *push* any built images, those are recreated from the Dockerfiles using Google CloudBuild. Searching for this leads me to a lot of suggestions but they all seem focused on building multiarch images which would require both porting the base and isn't really what I'm
21:16ChainfireThe only thing I've come up with so far that would end up with giving me working docker-compose without heavily modifying anything else, is using qemu-user-static and systemd-nspawn to fake an entire x86_64 root and run inside there.
21:16princesszoeymaybe box64?
21:17tpw_rulesqemu-user-static is depressingly slow even on m1
21:18ChainfireI've not used box64 at all as of yet, would it be essentially the same as the setup outlined above but qemu-user-static replaced in binfmt with box64 ?
21:18tpw_rulesi don't think so, box64 hooks a lot of libraries inside the x86_64 environment
21:20Chainfirealso qemu-user-static is depressingly slow on everything... One of the reasons I got the M1 to begin with is that I have a bunch of stuff I need to compile that can't go through a proper crosscompiler, doing it with qemu-user-static on my ThreadRipper takes something like 90 minutes vs 90 seconds on the M1
21:21Major_Biscuit has quit [Read error: Connection reset by peer]
21:21jni wonder if qemu-system is faster for workloads with many process spawns (like compiling)
21:22Major_Biscuit has joined #asahi
21:22jnbecause, in theory, qemu's JIT cache might have a chance then
21:28SuperED has joined #asahi
21:32dottedmagChainfire: ^
21:32dottedmagsorry chadmed, wrong highlight
21:34doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:36SuperED has quit [Ping timeout: 480 seconds]
21:40SuperED has joined #asahi
21:50NikolayNikolaev[m]Chainfire: docker for osx will use rosetta and will run your x86 images, no?
21:50AoV has quit []
21:53dottedmagmacOS is easy, yeah. There is colima that will boot x86 VM with Docker under Rosetta.
22:02surgeon_ has joined #asahi
22:04julio7359 has joined #asahi
22:04Major_Biscuit has quit [Ping timeout: 480 seconds]
22:06surgeon_ has quit []
22:08doggkruse has joined #asahi
22:12Stroller has quit [Quit: Stroller]
22:13difficultvelcro[m]Oh yeah uhh is Rosetta going to come to Asahi?
22:13difficultvelcro[m]I heard something about Rosetta on Linux
22:14tpw_rulesthat applies to linux vms running under macos
22:14NikolayNikolaev[m]Rosetta on Linux in a VM under darwin
22:15princesszoeyThat would be AMAZING if someone could boot both at the same time
22:23doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:25pwg has quit [Remote host closed the connection]
22:25difficultvelcro[m]Sounds like I just copy the executable somehow onto a Linux system running on M1
22:25pwg has joined #asahi
22:25Brainium has joined #asahi
22:26difficultvelcro[m]<j`ey> "difficultvelcro: https://..." <- That might be a heavy misinterpretation of the article you sent me
22:28j`eydifficultvelcro[m]: I think you need to modify the kernel to implement that ioctl
22:29j`eybut otherwise it looks like it just works
22:42vx5i2 has joined #asahi
22:47difficultvelcro[m]Change of subject: Will VeraCrypt work on Asahi?
22:50Stroller has joined #asahi
23:08doggkruse has joined #asahi
23:42doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:55doggkruse has joined #asahi
…