2022-05-20
00:00gladiac has joined #asahi
00:00gladiac has quit [Remote host closed the connection]
00:00gladiac has joined #asahi
00:00gladiac has quit [Remote host closed the connection]
00:01gladiac has joined #asahi
00:01gladiac has quit [Remote host closed the connection]
00:01gladiac has joined #asahi
00:01gladiac has quit [Remote host closed the connection]
00:01gladiac has joined #asahi
00:01gladiac has quit [Remote host closed the connection]
00:02gladiac has joined #asahi
00:02gladiac has quit [Remote host closed the connection]
00:02gladiac has joined #asahi
00:02gladiac has quit [Remote host closed the connection]
00:02gladiac has joined #asahi
00:02gladiac has quit [Remote host closed the connection]
00:02gladiac has joined #asahi
00:03gladiac has quit [Remote host closed the connection]
00:03gladiac has joined #asahi
00:03gladiac has quit [Remote host closed the connection]
00:03gladiac has joined #asahi
00:03gladiac has quit [Remote host closed the connection]
00:03gladiac has joined #asahi
00:04gladiac has quit [Remote host closed the connection]
00:04gladiac has joined #asahi
00:04gladiac has quit [Remote host closed the connection]
00:04gladiac has joined #asahi
00:04gladiac has quit [Remote host closed the connection]
00:04gladiac has joined #asahi
00:05gladiac has quit [Remote host closed the connection]
00:05gladiac has joined #asahi
00:05gladiac has quit [Remote host closed the connection]
00:08GustavBlty[m] has joined #asahi
00:17jabashque has joined #asahi
00:27greguu has joined #asahi
01:12riker77_ has joined #asahi
01:17riker77 has quit [Ping timeout: 480 seconds]
01:17riker77_ is now known as riker77
01:51witchbutter has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:06PhilippvK has joined #asahi
02:08derzahl has joined #asahi
02:10phiologe has quit [Ping timeout: 480 seconds]
02:11derzahlanyone get chromium to work yet? I had no luck with 100 and 101 after updating for 16k kernel pages. Trying to compile chrome canary 104...I think that should have the 16k page patch built in....
02:18Telvana2 has quit [Read error: Connection reset by peer]
02:19Telvana has joined #asahi
03:32marvin24_ has joined #asahi
03:35marvin24 has quit [Ping timeout: 480 seconds]
03:38nicolas17 has quit [Ping timeout: 480 seconds]
03:44kov has quit [Quit: Coyote finally caught me]
04:24chadmednot specifically chromium v102 but im pretty sure the patch was tested before it was submitted
04:24chadmed has quit [Quit: Konversation terminated!]
04:28derzahlwell one would think so. perhaps not necessarily on apple hardware. dunno. but I have not seen any mention of results. no packages or pkgbuilds specifically for asahi
04:29chadmed has joined #asahi
04:30qyousef_ has joined #asahi
04:32qyousef has quit [Ping timeout: 480 seconds]
05:37jonaburg[m]chadmed: this is awesome work in regards to the audio sink config for the 14/16 inch m1 macbook pros. also super cool to understand why it's like that and what's happening
05:38jonaburg[m]something really cool in the asahi community is how the knowledgeable share their knowledge with everyone and explain it for the curious
05:39chadmedheh thanks :) just need to do the same for the other machines when i have the funding/time available to do so. i think it would be interesting to do the mac mini and mac studio, will be v challenging
05:41jonaburg[m]should the feature list not be updated to now include working audio? i assume the plan is to bake this in the installer right?
05:43chadmedpovik's working on a new patch series that introduces a hard volume limit in the kernel so that cant happen
05:44jack[m]12345 has joined #asahi
05:44chadmedfwiw in my testing ive yet to actually make the machine explode even after blasting bass through the tweeters for a few seconds so its probably reasonably safe but im not in a position to be able to run the test to possible destruction
05:44chadmedfor me personally, not exploding after ~2 seconds at max volume is good enough. that's simply not good enough for end users to daily drive though
05:47jannaujudging by the boot chime the speaker in the studio is in a different league than the min1
05:48chadmedi was going to buy one at launch but the wait times were over a month here in australia and my car needed some TLC so it went on the backburner
05:48chadmedtpw_rules: i dont blog because im nowhere near important enough lmao but i made a couple of tweets about it
05:51chadmedwell a mac studio would sure as heck beat the pants off this 2017 dual core macbook pro im using as a desktop with a lenovo thunderbolt dock
06:07guillaume_g has joined #asahi
06:07chadmed_ has joined #asahi
06:17eroux has joined #asahi
06:23bps has joined #asahi
06:30eroux has quit [Quit: Textual IRC Client: www.textualapp.com]
06:44the_lanetly_052 has joined #asahi
07:01eroux has joined #asahi
07:20eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:22Telvana has quit []
07:30Telvana has joined #asahi
07:31bps has quit [Ping timeout: 480 seconds]
07:35eroux has joined #asahi
07:54bps has joined #asahi
08:21jluthra has quit [Remote host closed the connection]
08:21jluthra has joined #asahi
08:49voj343[m] has joined #asahi
08:55SorunomeLuckySkies[m] has joined #asahi
09:22conradev has quit [Quit: -]
09:23conradev has joined #asahi
09:24joske has joined #asahi
10:27Cy8aer[m]I have seen this: https://github.com/chadmed/asahi-audio and as I understand there is a waveform added to the payload audio in realtime, right? And there are waveforms for the mbp14 right now and mbp16 is just interpolating that the data of the mbp14 is working for it too somehow? How were these waves generated (really measured or calculated?)
10:30joskeCy8aer[m]: IIRC he measured these (and wrote a detailed explanation somewhere how he did so)
10:31chadmed_hopefully theyre detailed enough for someone like m arcan to reproduce on machines i dont have/cant get access to myself
10:49kov has joined #asahi
11:10Cy8aer[m]But I still wait for the save and switched on audio support with the right output levels before I try it.
11:30timokrgr has quit [Quit: User left the chat]
11:31timokrgr has joined #asahi
12:00beep-boop[m]Have you guys done any tweaks on keyboard settings and shortcuts to make it behave more like macos?
12:07beep-boop[m]What I miss most in linux is the ctrl+a to move to the beginning of the text etc.
12:08Cy8aer[m]That is emacs style and depends on the GUI (Gnome has some parameter to set emacs style)
12:08beep-boop[m]Cy8aer[m]: I think that was removed in 4x release
12:09matthewayers[m]I’m much more of a Vim guy myself
12:11* beep-boop[m]uploaded an image: (6KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/qlcEVrJLGGJewSlzMcKausUG/image.png >
12:11beep-boop[m]This one?
12:13beep-boop[m]Cy8aer[m]: I cant see this entry in dconf
12:15Cy8aer[m]mom, just googled it, and that was from 2007. But now I found the emacs option you showed from the tweak tool. That is the paramater I clicked.
12:18Axenntio has joined #asahi
12:18Sobek[m]Also didn't marcan ask people to actually provide feedback about which keyboard layout matched hardware best and what bugs there were ?
12:19Cy8aer[m]Just learned today that "verkehrsverbund" can be found in english like "kindergarten". "Verkehrsverbund" - Something that does not work in Germany - but that is off topic.
12:20Cy8aer[m]But the emacs settings are some gui standard on all archs. I was happy to have `/sys/module/hid_apple/parameters` for having the keyboard more ISO and that works fine for me.
12:23Cy8aer[m]I needed `/sys/module/hid_apple/parameters` for emacs - because I had problems to type M-x without twisting my fingers...
12:38minecrell has quit [Read error: Connection reset by peer]
12:40minecrell has joined #asahi
12:47Bai-Chiang has joined #asahi
13:03m42uko has quit [Quit: Leaving.]
13:11eroux has quit [Ping timeout: 480 seconds]
13:12eroux has joined #asahi
13:17Axenntio has quit [Ping timeout: 480 seconds]
13:26AstrOwO[m] has joined #asahi
13:26AstrOwO[m] is now known as AstrOwO[m]1
13:40m42uko has joined #asahi
13:46chadmed_ has quit [Remote host closed the connection]
14:26joske has quit [Quit: Leaving]
14:45darkapex1 has joined #asahi
14:46darkapex has quit [Ping timeout: 480 seconds]
15:10Gaspare has joined #asahi
15:19guillaume_g has quit []
15:22bps has quit [Ping timeout: 480 seconds]
15:32ciggi has quit [Read error: Connection reset by peer]
15:56Gaspare has quit [Quit: Gaspare]
15:59bps has joined #asahi
16:11RevHelix has quit [Read error: Connection reset by peer]
16:11RevHelix has joined #asahi
16:13derzahlas far as optiimizing gcc builds for the cpu, what is best practice? just "-march=armv8.5-a"? I dont think gcc has any more specific definition for the m1 architecture, right?
16:26Telvana has quit []
16:38Gaspare has joined #asahi
16:39Gaspare has quit []
16:42nicolas17 has joined #asahi
16:44Gaspare has joined #asahi
16:50mpsI need to delete data from partition on mbp to send it to service. not sure which partitions I have to wipe
16:51ptudor has joined #asahi
16:52tpw_rulesgdisk calls the ones you need to keep "iBootSystemContainer" and "RecoveryOSContainer"
16:54tpw_rulesi wonder if there's a quick way to reset the ssd keys. but i assume that would require a DFU restore afterward
16:55mpsI have to do this over network, display doesn't work and I can't boot to macos because linux is default
16:57ptudor_ has quit [Ping timeout: 480 seconds]
17:08bps has quit [Remote host closed the connection]
17:08bps has joined #asahi
17:18bps has quit [Ping timeout: 480 seconds]
17:30xfim has joined #asahi
17:30xfimI asked a few days ago if it was possible to install Asahi on a Mac Studio, although it was not listed as supported.
17:31xfimHowever, I just had my Mac Studio a couple hours ago, and after updating MacOs I went straight ahead with the Asahi installer.
17:33xfimMy idea is to use Kellerman Rivero's guide to go directly to install my usual working distro (https://blog.devgenius.io/installing-gentoo-linux-in-apple-macbook-pro-m1-49e163534898).
17:35witchbutter has joined #asahi
17:37_jannau_I will eat in a couple of minute and read over the installation instructions to see what's necessary to get you started
17:37Glanzmann has joined #asahi
17:38GlanzmannHello, I just wanted to pull the subtiles from todays asahi lina stream but the video has disappeared. Could someone summarize what was accomplished today?
17:38hellstabber has joined #asahi
17:41hellstabber has quit []
17:43eroc1990 has quit [Quit: Ping timeout (120 seconds)]
17:44eroc1990 has joined #asahi
17:44Glanzmannj`ey: Good to hear. I look forward to have accelerated graphics under linux on the m1.
17:45Gaspare has quit [Quit: Gaspare]
17:49Sobek[m]Random thought, is it technically possible to write drivers to support Touch ID under linux ? What are the moving parts required ?
17:51nicolas17I think the kernel (or userland?) needs to read some files off an APFS filesystem and give them to the SEP
17:52Sobek[m](Is there anything remotely like SEP that has linux drivers btw or will that likely be a significant amount of work simply becuase such component don't have any subsystem in the kernel and interface ?)
17:53nicolas17I think Sobek[m]'s question is more like, "does the SEP count as an HSM, and can we make a driver for Linux's HSM subsystem, if there is one? or would it need a whole new API?"
17:54Sobek[m]What would rprevent the installer from grabbing those files and dumping them along with the firmware, and then the kernel can grab those off its usual filesystems and hand them to SEP ?
17:54nicolas17what I said about "read files and send them to the SEP" was 100% a guess pulled out my ass, idk how it works
17:55svenanyway, please figure out a reasonable question that I can actually understand and then i'll try to answer
17:55nicolas17sven: Linux needs to handle reading/writing "gigalocker" stuff from APFS on behalf of the SEP?
17:56roxfan2 has joined #asahi
17:56sventhat gigalocker thing is a single file with a constant size on a special APFS partition fwiw
17:58svenif we wanted to hack this we might be able to just grab the block ids once and then just ignore APFS altogether :D
18:00svendebugging the whole userland-kernel module-SEP stack will be annoying enough even if we already understand how the SEP communication works
18:00nicolas17what's the mailbox protocol to add a new fingerprint? add one on Mac, while m1n1 is logging everything
18:00Sobek[m]I'm more intrigued by your statement that most stuff would occur in the userland, how would the thing be architectured exactly ? (What are the security implication of most stuff being in userland)
18:00roxfan has quit [Ping timeout: 480 seconds]
18:01sventhis is all very far away and something to think about once there's a better understand how the SEP protocol looks like
18:01Sobek[m]Anyway SEP is unlilely to get investigated until stuff like sound, GPU and Thunderbolt have all been sorted out, isn't it ?
18:02nicolas17if someone who isn't working on sound/GPU/thunderbolt wants to look into SEP they're welcome to :)
18:03svenwe'll also need to understand how e.g. SEP interacts with the NVMe encryption before we can design how the linux implementation will look like
18:05Gaspare has joined #asahi
18:11Glanzmann has quit [Quit: EOF]
18:21witchbutterAre you guys maintaining a project board or anything with things that need to be worked on? How can I find a way to contribute?
18:29Telvana has joined #asahi
18:32jannauhttps://github.com/jannau/asahi-installer/tree/mac_studio is an installer branch with mac studio "support". only the "tethered boot" option will work out of the box but the other images can be easily fixed
18:42linearcannon has quit [Ping timeout: 480 seconds]
18:55linearcannon has joined #asahi
18:56jannauxfim: building is a little tricky since you need a bleeding edge rust toolchain to build m1n1 with chainloading for the installer
18:59jannauyou need 'RUSTUP_TOOLCHAIN=nightly rustup target install aarch64-unknown-none-softfloat' see how the github ci does that https://github.com/AsahiLinux/m1n1/blob/d44306a1c7eabe46dfc4b1ed3b04861786e23db3/.github/workflows/build.yml#L32
19:06kaprestswitchbutter: I am by no means involved in the development myself, but my understanding is that the wiki and this room are the things to check out if you want to contribute
19:12the_lanetly_052 has quit [Ping timeout: 480 seconds]
19:15xfimCorrect me if I am wrong: the big picture is to build this installer, and then to copy the resulting binary to the MacOs and run it. Is that it?
19:18roxfan2 is now known as roxfan
19:24witchbutter has quit [Ping timeout: 480 seconds]
19:32jannauxfim: yes, you need to copy installer.tar.gz and data/installer_data.json to macos, unpack installer.tar.gz and run ./install.sh as root
19:34jannauyou can select and the the minimal asahi linux distro but it will not boot. you should end up with a m1n1 prompt
19:38the_lanetly_052 has joined #asahi
19:42jannauclone https://github.com/jannau/u-boot-1/tree/installer-release-t6001_j375c; make apple_m1_defconfig; make
19:45jannau`cat m1n1/build/m1n1.bin u-boot/arch/arm/dts/t6001-j375c.dtb <(gzip -c u-boot/u-boot-nodtb.bin) > boot.bin
19:46xfimAbout usb a-c cable. Something like this: https://m.media-amazon.com/images/I/61saWQ69dsL._AC_UY436_QL65_.jpg? If so, yes.
19:48jannauthe installer creates a fat partition (efi system partition). replace /m1n1/boot.bin on that partition with the one you've created
19:49the_lanetly_052 has quit [Ping timeout: 480 seconds]
19:55xfimjannau: OK perfect for the cable. But I need some more time to digest everything: a) build the installer; b) copy it to MacOs, along with the json, unpack and run install; c) select minimal and end up with a m1n1 prompt; d) in the meantime in another machine build m1n1 and make the u-boot-1 ending up with a boot.bin file; e) move boot.bin to the Mac Studio either via USB cable or via m1n1 proxy; Is that more
19:57xfimThere are so many steps that can fail here, wow. So much to learn. The alternative would be to wait a few days to incorporate the changes into the main installer and just go with the "curl ... | sh"? If so, how many days you think it would be needed to incorporate it?
19:57jannauxfim: more or less. there is no transfer over usb but you can remotely boot the binary over usb
19:58xfimI'm just struggling with a), as it seems that rust development and gentoo are not very good friends (https://www.reddit.com/r/Gentoo/comments/sy3no5/why_is_rust_development_such_a_pain_on_gentoo/), as I have not been able to find rustup.
20:03xfimjannau: OK. Thank you. I can work with it. At least step a) is one less thing to worry about.
20:03xfimOK, so I've got the three files bootstrap.sh, installer.tar.gz and installer_data.json on the MacOs
20:10jannauxfim: no idea how long it will take to update the official installer. there are quite a few things which need to be updated with dependencies
20:21Bai-Chiang has quit [Ping timeout: 480 seconds]
20:22xfimjannau: all well in the MacOS, resize done. Now trying to build m1n1, but I need the full toolchain for arm64. Another thing to learn.
20:30lightclient[m] has joined #asahi
20:32jannauif it where just m1n1 you could take it from https://github.com/AsahiLinux/m1n1/actions/runs/2360120439 but you need u-boot as well
20:34jannauxfim: you can either build a toolchain via crossdev or you can download it from https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/downloads
20:36Gaspare has quit [Quit: Gaspare]
20:46int80 has quit [Quit: WeeChat 3.4]
20:59xfimjannau: oh, so many options. Building the crossdev system in gentoo is something that I would like to learn anyway, as one of my ideas is to use tho Mac Studio to compile the packages for the laptop. so it is worth doing the investment now. (BTW, does this seems reasonable?). But maybe downloading it is just easier now and I leave the crosscompilation for another time.
21:24Bai-Chiang has joined #asahi
21:37amarioguy has quit [Remote host closed the connection]
21:38xfimjannau: the crossdev part is proving to be quite challenging. Can I ask if the option to wait for Mac Studio to be included in the main installer is expected in the foreseeable future? (I can not see myself right now doing this in a couple of days).
21:38ElvishJerricco[m]So I'm considering adding some infra in NixOS for booting with the Asahi kernel and m1n1, but I'm a tad concerned about the firmware stuff. I remember reading at one point that the Asahi kernel has to be written for a specific version of the firmware. Does that also mean the system has to have been booted with a macOS stub based on that version? Because while I'm happy to write some code for pulling the firmware out of IPSWs in Nix to
21:38ElvishJerricco[m]provide to the kernel (we have good support for automating non-redistributeable firmware), I wouldn't be able to automate setting up the macOS stub (given that I think you have to do that from macOS, not to mention lack of APFS support in Linux)
21:40ElvishJerricco[m]j`ey: Well the concern is updating the kernel. If that one day requires a new version of macOS stub, then we can't automate that in NixOS. If all I need to automate is /lib/firmware on the linux side and stage 2 m1n1, then no problem
21:41ElvishJerricco[m]oh wow Element really screwed up your name...
21:43ElvishJerricco[m]mps: I'm not holding my breath :P
21:46ElvishJerricco[m]j`ey: Ah, so the goal is that any firmware that was previously supported with Asahi will remain supported in future versions? That certainly helps a lot, but *then* we might have /lib/firmware not matching macOS stub. I don't know if that would be a problem.
21:47j`eyElvishJerricco[m]: Im not sure if that's the goal or not.. but I think it should be.. depends if the interface changes in the fw are easy enough to work around
21:47mpsElvishJerricco[m]: this is rarely problem on all other drivers, but I'm not sure about apple
21:47ElvishJerricco[m]mps: Yea I don't know if the same stability can be expected from a platform like Apple Silicon
21:48ElvishJerricco[m]Just on the basis that it's literally only designed to run one OS, and that OS manages installing the firmware too
21:48j`eyElvishJerricco[m]: you wont need to do anything with the fw in nixos, the asahi installer does it.
21:50ElvishJerricco[m]j`ey: NixOS is going to want to manage /lib/firmware
21:53ElvishJerricco[m]tpw_rules: Yea. I'm looking into how we might integrate something like it into nixos proper
21:53ElvishJerricco[m]But for that I want a level of certainty that firmware versions and macOS stub versions won't be problematic
21:54tpw_rulesElvishJerricco[m]: ahh, great. be sure to keep me in the loop :) the way the asahi stuff expects it to be managed is copying to the ESP like j`ey said
21:54tpw_rulesso there at least has to be enough cross-version support to boot into a new version and get the script running to copy new firmware
21:55tpw_ruleslike the asahi arch install proper does manage /lib/firmware, the installer doesn't do anything to that at all except dd a filesystem which contains that directory, but it's empty for legal reasons
21:56ElvishJerricco[m]m1n1 is tied to the kernel? I thought we could just use it to boot u-boot and then EFI boot the OS
21:56xfim has quit [Ping timeout: 480 seconds]
21:57tpw_rulesi think that problem will lessen over time as things stabilize. i have it managed to some degree with boot.loader.*.extraFiles but if you install a broken one you're hooped and nixos can't roll it back
21:58ElvishJerricco[m]So I'm still not clear on my original question. To what degree is the Asahi kernel tied to the version of macOS stub that's installed, and the version of the firmware intended to be copied to /lib/firmware?
21:58tpw_ruleseven in arch this is a problem: how do you have two different versions of your kernel in the grub menu, each of which need a different device tree?
21:59tpw_rulesmy 2 cents says it can't be so tied that it's unbootable, because the asahi kernel needs to boot to copy new stuff from the stub to /lib/firmware
22:00ElvishJerricco[m]wait the Asahi kernel copies stuff from the stub? It can read APFS?
22:01ElvishJerricco[m]got it
22:01ElvishJerricco[m]and the OS loads firmware from ESP I guess
22:02tpw_ruleshttps://github.com/AsahiLinux/docs/wiki/Open-OS-Ecosystem-on-Apple-Silicon-Macs#firmware-provisioning
22:03AstrOwO[m]1Hey y'all, I'm new here
22:03AstrOwO[m]1Quick question
22:03AstrOwO[m]1Last I've seen about touch ID is from this page
22:03AstrOwO[m]1oct/nov 2021
22:03AstrOwO[m]1Anyone know if there's been any updates since then?
22:03AstrOwO[m]1Sorry for the noob question
22:03AstrOwO[m]1Thanks :3
22:31sventpw_rules: the device tree will be forward and backward compatible but only for things that have been upstreamed already
22:32crabbedhaloablut has quit []
22:33crabbedhaloablut has joined #asahi
22:33sven(so far we only had a single exception to that rules with the power-domains and I hope that remains the only one)
22:34eroc1990 has quit [Ping timeout: 480 seconds]
23:25eroc1990 has joined #asahi