2022-03-09
00:07amarioguy has quit [Ping timeout: 480 seconds]
00:55amarioguy has joined #asahi-dev
01:02chadmedpovik: just as a test, have you a way of identifying which channels are which physical speakers in the device? if so, it might be worth setting up a stereo loopback sink, upmixing that to 6 channels, then playing with JACK or something to feed each channel into a DSP chain consisting of a bandpass filter and EQ and then outputting that to each channel in the speaker array
01:02chadmedjust so we can get an idea of settings and such to create a profile/FIR for it so this all happens automagically
01:03chadmedi think this is better than just presenting it to ALSA as a stereo device, it gives us (and the user) far more control over the sound profile
01:53user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:00user982492 has joined #asahi-dev
02:05riker77_ has joined #asahi-dev
02:10riker77 has quit [Ping timeout: 480 seconds]
02:10riker77_ is now known as riker77
02:14user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:18user982492 has joined #asahi-dev
03:25pfdub[m] has joined #asahi-dev
03:26phiologe has joined #asahi-dev
03:28amarioguy has quit [Ping timeout: 480 seconds]
03:29pfdub[m]Hey There, new here and wanting to help with checking notes and creating documentation. I currently have a MacMini M1, know a bit about networking, good but rusty at Java, haven't programmed C in a while. Here to soak up things. Probably waiting to I get a new MacMini M1 to try and install(maybe I'll dip my toe in before that). How do I get permissions to see earlier messages so I can see what is going on?
03:29PhilippvK has quit [Ping timeout: 480 seconds]
03:58kov has quit [Quit: Coyote finally caught me]
03:59kov has joined #asahi-dev
03:59csileeeeeeeeeeeeeeeeeeeeeeeeoe has joined #asahi-dev
04:18psykose has quit [Remote host closed the connection]
04:18psykose has joined #asahi-dev
04:20chadmedpovik: what do i have to do to get alsa to see the sound card on a j314s? ive build your asahi-snd-wip branch and built a new m1n1 payload with the dt from there, the modules load on boot but alsa says theres no sound cards
04:33marcanchadmed: the upmixing story is down to userspace; povik is working on the kernel side right now
04:35marcankettenis: I don't think the EQ is done in the codecs, because otherwise iBoot wouldn't need 6ch audio files for the boot chime, they could just load the same configs
04:35chadmedyeah i was just referring to the part where he suggested presenting it as a stereo device to userspace rather than exposing all the channels and letting userspace decide what to do with them in configuration, which is what i was about to have a play with now
04:38marcanok, going to grab lunch and then wrap up the chainloading thing (and implement the packaging/etc) so we can ship this and not be worried about DTB updates being cumbersome :)
05:00hizon has joined #asahi-dev
06:02csileeeeeeeeeeeeeeeeeeeeeeeeoe has quit [Remote host closed the connection]
06:11the_lanetly_052__ has joined #asahi-dev
06:26gladiac has joined #asahi-dev
07:15povikchadmed: hmm, weird the device didn't show up when you built from asahi-snd-wip. send me a dmesg in PM please
07:16chadmednah i figured it out, apple-admac wasnt loading automatically so i just added it to modules.load.d
07:17chadmednightcore is a genre of music where they take a sped up song and chop and screw it, i was referring to how everything is sped up and chipmunk-y
07:27user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:40bluerise has quit [Quit: brb]
08:20marcanbut really all that's left is the chainloading function (which is just porting python -> C)
08:20marcanthis means we probably won't have to have existing alpha release users ever re-1TR at *all*
08:21marcanit should cover all future magic we add including full PSCI/sleep/etc; something would have to go very wrong for a top-level m1n1 change to be required
08:23marcanit also means we can afford minor DT compat breaks in the non-upstream branches without too much fuss, since we can ~guarantee people will upgrade in lockstep
08:23marcanobviously I wouldn't want anything that actually breaks boot majorly, at least not without a transition period
08:36povikalso, that together with the power domain fixes explains the "pwrstate change failed" message people have reported when compiling to modules earlier
08:42marcana bunch of refcounting issues still in asahi, unloading certain modules in the wrong order explodes :-)
08:50jannaumarcan: alpha release users should update through 1tr once we add signature checks (unless you plan to implement that now as well)
08:52marcansecureboot only makes sense if you encrypt your rootfs (and ideally hashtree sign it too), which we aren't doing
08:53marcanso an end-user ready secureboot option will come much later and will probably involve a full reinstall from our POV; users who want to roll their own transition of course can do that and upgrade from 1TR at that point
08:54marcanmy goal with secureboot is to make it *possible* and engineer things such that we can support it; but I think the majority of users don't care, and those who do will probably want to roll their own tweaks anyway
08:54marcanbuilding transparent secureboot for the masses is a much harder problem, which is why it's cool that Apple is doing it :-)
08:55marcanand none of this really makes much sense without SEP support too, to aid in the crypto and take advantage of some of Apple's own engineering
08:56marcanso, all much further in the future, probably by which point we'll want to have not just m1n1 upgrades but stub firmware upgrades implemented too
08:58rkjnsnPersonally, I'll be happy just to have everything through Grub (and configuration) verified. Since I keep my kernel and rootfs on an encrypted partition unlocked by Grub, that should be enough to make offline attacks difficult.
09:00marcanfor now, you should probably just enable FileVault in macOS and set up u-boot/grub to disable the console
09:00marcanthat won't verify things, but will disable any way to take over the machine without a full wipe or disassembling it, in principle
09:02marcangiven the hardware security of these machines, and that AIUI all NVMe data should be encrypted at rest by the controller anyway, just that alone should be rather strong security
09:06rkjnsnGood to know. I was thinking I had to worry about target disk mode, but it looks like the Apple Silicon require entering recovery (and thus authenticating) to enable it, instead of using a key combination?
09:07rkjnsnThat's kind of annoying, though. When I've used target disk mode in the past, it was because the system was too dead to even boot recovery..
09:07jannaumy expectation was that we can support UEFI secure boot via u-boot and have not to do much else to satiesfy standard distro's secure boot needs
09:08marcanyou can use the "revive" option if you just borked system recovery, and that should leave your OS partition intact, though honestly you'd have to try pretty hard to break that too
09:09marcanthere are probably cases where that fails and requires a full wipe though, no idea what happens if e.g. the GPT is mangled
09:09marcanjannau: UEFI secure boot requires key provisioning, but we don't have sane EFI variable storage to store that
09:10marcanso at the very least we'll have to provision distro keys in top-level m1n1, and distros will have to ship a signed m1n1+u-boot second stage that then contains the hardcoded UEFI secure boot keys they use for the rest of the story
09:15marcanlike how do you do distro installs? from USB? that means if you're already doing secureboot then, you have a chain break in the USB boot mechanism
09:17marcanUEFI secure boot/TPM/etc systems aren't... exactly a good inspiration to go by, seeing as the entire x86 secureboot ecosystem is kind of a joke in various ways
09:18marcanso yeah, ultimately, in the short term this is going to be a power user thing for people who really care and don't mind e.g. going through 1TR for every secureboot transition they want to make
09:18marcanand either way distros are going to have to cooperate and take on a bunch of the engineering/integration if they want to make it easy for *their* users
09:20marcane.g. one way to solve the bootstrapping issue might be to have a signed recovery kernel/initramfs option (stored in the ESP) that can launch e.g. online or USB recovery, but only after authenticating against SEP
09:21marcanwe could work on building a generic version of something like that, but making it end-user-proof would definitely be a distro's domain
09:31bluetail[m]marcan: I've been messing with UEFI+SecureBoot quite a while now. Turns out that Windows 10+ or Debian is the only thing I can secureboot on a severely secured machine. ARCH wouldn't do...... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/MZBfHtbknuGXCLbPSRlfXEYk)
09:35marcanand probably also doesn't do module signing so you'd want to build your own kernel with that anyway
09:40kettenislinaro folks are working on UEFI secure boot support in U-Boot but it heavily relies on having a TPM of some sorts
09:41kettenisI think the idea is to have some sore of fTPM running in secure EL2 if there is no hardware TPM
09:42rkjnsnSo, SEP doesn't access the SSD directly, but asks the OS to do so on its behalf (and then verifies the data the OS gives it back is legit), right? Could U-Boot do something similar for EFI vars, where it gives the OS a signed blob to store for it that it can read on the next boot?
09:45marcanthat might work, but it's a bit dodgy and you still need a "machine key" provisioned on first install somehow
09:47marcanultimately, if we want to do this properly, the only real way is to use the SEP, which means either having "static" secureboot all the way to Linux (and SEP + APFS there), or sticking APFS+SEP support into u-boot too
09:49marcannote that we don't need full APFS support, just enough to find the single fixed-size file present in a specific volume, and replace blocks in it
09:52marcanhonestly, given Apple apparently already have two extra NVMe namespaces for some magic stuff, I don't know why they didn't just stick xARTS there and had to use APFS...
10:06MajorBiscuit has joined #asahi-dev
11:26hizon has quit [Remote host closed the connection]
12:20os has quit [Quit: The Lounge - https://thelounge.chat]
12:21os has joined #asahi-dev
12:52amarioguy has joined #asahi-dev
12:59yuyichao_ has quit [Ping timeout: 480 seconds]
13:14yuyichao_ has joined #asahi-dev
13:36bisko has joined #asahi-dev
14:38bligma[m] has joined #asahi-dev
14:50amarioguy has quit [Ping timeout: 480 seconds]
14:56amarioguy has joined #asahi-dev
15:44kloenk has quit [Remote host closed the connection]
15:54amarioguy has quit [Ping timeout: 480 seconds]
16:04marcankettenis: new installer UEFI only option now does chainloading, and also should be setting /chosen/efi-partition to the ESP PARTUUID
16:46kettenisone possibility would be to generate Boot0000 and BootOrder variables from that and have the built-in U-Boot efi bootmgr code handle the boot
16:47kettenisjanneau had a script-based hack, but one of the u-boot maintainers is pushing a patchset to replace those with a different implementation in C
16:50_jannau_the script based hack could be extended to read this from the fdt, setting EFI Boot variables look cleaner but we still have the problem that a random ESP with extlinux.conf could prevent the EFI boot
16:50Telvana2 has joined #asahi-dev
16:53Telvana has quit [Ping timeout: 480 seconds]
16:53_jannau_yes, the sane thing would be to disable distro boot but there were people wanting to use extlinux
16:57Telvana2 has left #asahi-dev [Textual IRC Client: www.textualapp.com]
16:57Telvana has joined #asahi-dev
17:04amarioguy has joined #asahi-dev
17:10alyssa is now known as random_user_174
17:12random_user_174 is now known as alyssa
17:34FireFox317marcan, just a heads up but the currently pushed installer at mrcn.st/alxsh isnt working. I know there might be some bugs in the kernel as you said in the stream, but thats okay for me. See the following pastebin: https://pastebin.com/d6HDzJzR
17:36FireFox317I guess you didnt update the installer_data.json file maybe?
17:38FireFox317j`ey, i know, but he said that he did push it to the link. I get the new python code through the link
17:39j`eyexport INSTALLER_DATA=https://github.com/AsahiLinux/asahi-installer/raw/main/data/installer_data.json
17:39FireFox317j`ey, aha, thanks. yeah that is the issue then, but fixing it can wait :) im not in a hurry, just super excited xd
17:52alyssa has left #asahi-dev [#asahi-dev]
18:32amarioguy has quit [Ping timeout: 480 seconds]
18:36MajorBiscuit has quit [Quit: WeeChat 3.4]
18:37amarioguy has joined #asahi-dev
18:45the_lanetly_052__ has quit [Ping timeout: 480 seconds]
19:10user982492 has joined #asahi-dev
19:22___nick___ has joined #asahi-dev
19:26marcanalso pushed a new installer to fix a nvme boot surprise leftover in the 1st-stage m1n1 (which was breaking nvme on linux when booted without u-boot and with a m1n1 chainload attempt along the way :))
19:29amarioguy has quit [Ping timeout: 480 seconds]
19:32csileeeeeeeeeeeeeeeeeeeeeeeeoe has joined #asahi-dev
19:36kaferka has joined #asahi-dev
20:14user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:18kaferka has quit [Read error: Connection reset by peer]
20:18___nick___ has quit []
20:21___nick___ has joined #asahi-dev
20:30user982492 has joined #asahi-dev
21:07jannauwhy would allocating the shadow framebuffer (23M) break dcp after a chainload. the rest of m1n1's fb code is disabled
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:09Glanzmannjannau: When I boot, I get the following error message, but I assume it is unrelated? [ 2.212786] simple-framebuffer be2120000.framebuffer: [drm] could not acquire memory region [mem 0xbe2120000-0xbe30bffff flags 0x200]
21:19tanty has quit []
21:22tanty has joined #asahi-dev
21:25tanty has quit []
21:27tanty has joined #asahi-dev
21:43user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:44amarioguy has joined #asahi-dev
21:54csileeeeeeeeeeeeeeeeeeeeeeeeoe has quit [Remote host closed the connection]
22:50gladiac has quit [Quit: k thx bye]
22:57amarioguy has quit [Ping timeout: 480 seconds]
23:17user982492 has joined #asahi-dev