00:37 <marcan> I'm going to do some abuse tests as soon as I get a chance, and see how that goes

00:40 <tpw_rules> using scarlet fire?

00:46 <marcan> nah, I Won The Loudness War

00:49 <eshmaki> I need ya'll to get back to work. I have an m1 that needs a feature complete linux distro

00:49 <eshmaki> jkjkjk

02:33 <chadmed_> povik: at this point i dont think we should really care what macos does in software apart from what i assume is a very light touch compressor given how the volume curve works

02:34 <chadmed> but thats a userspace thing

02:36 <chadmed> like ive put this j314 through the ringer now even without the safety stuff (which i will have a play with soon) and i havent been able to blow it up even at full pelt so i think at this point now that we do have the safety stuff im pretty confident in saying that theres no chance a user could destroy their machine from userspace

07:21 <jannau> I don't care either. I wasn't aware that the mac mini speaker was not disabled and thought it got accidentially dropped. Let's not introduce regressions

07:22 <jannau> especially since it's now safer than before

07:23 <jannau> Let's update Feature-Support once the new audio bits are merged, we have to update the headphone jack info then anyway

10:39 <dottedmag> I have tried to relax security policy on macOS installation to boot kernel under hypervisor, and got the following error. Did I miss some step? https://tea.dottedmag.net/~dottedmag/fail-bputil-on-macos.jpg

10:45 <ChaosPrincess> is the os that you want to change boot policy on set as default boot target?

10:46 <dottedmag> ah, let me check, thanks.

10:51 <dottedmag> that was it, thank you

10:58 <dottedmag> Relaxing boot policy didn't help boot macOS kernel, it panicked with "rootvp not authenticated after mounting": https://tea.dottedmag.net/~dottedmag/panic.txt Did I miss another step?

10:59 <chadmed> without knowing what steps you did, impossible to say

11:00 <ChaosPrincess> have you changed anything on root partition

11:00 <chadmed> that error sounds like youre trying to boot a kernelcache from an APFS container that isnt the root its trying to jump to

11:00 <dottedmag> ChaosPrincess: nope

11:00 <chadmed> i.e. youre trying to use the asahi m1n1 install, you need to set m1n1 as a custom boot object on the actual macos volume

11:00 <ChaosPrincess> can you tell us what exactly did you do

11:01 <dottedmag> chadmed: Aha, that's the thing. I didn't understand this point in the list of things to do. Let me try.

11:01 <chadmed> there we go :)

11:02 <chadmed> kmutil configure-boot -v /Volumes/[macos root] -c [path to m1n1.bin] -r --entry-point 2048 --lowest-virtual-address 0 <-- run that in 1TR

11:02 <chadmed> you need a clean m1n1.bin of course

11:06 <dottedmag> chadmed: clean as how clean? built from source?

11:08 <chadmed> yeah as in not glued to a payload

11:08 <dottedmag> got it. I have to do something else atm, will be back with more questions later :)