#
…

2025-03-22

00:06zumi_ has joined #asahi-dev
00:06zumi has quit [Remote host closed the connection]
00:11zumi_ is now known as zumi
00:23pb17 has quit [Ping timeout: 480 seconds]
00:35pb17 has joined #asahi-dev
00:37BesterGester has left #asahi-dev [The Lounge - https://thelounge.chat]
00:43nesnas has quit [Ping timeout: 480 seconds]
00:51nesnas has joined #asahi-dev
01:04nesnas has quit [Ping timeout: 480 seconds]
01:12nesnas has joined #asahi-dev
01:20dylantaylor has joined #asahi-dev
01:23dylantaylorI made a PR to asahi-wip to enable the microphone on this device based on earlier testing, I see jannau has been maintaining this, and was hoping that everyone would be okay with this being merged. https://github.com/AsahiLinux/linux/pull/380 I think it's ready, and would love to see this land in time for F42 stable.
01:24nesnas has quit [Ping timeout: 480 seconds]
01:31nesnas has joined #asahi-dev
01:32dylantaylor has quit [Quit: Leaving]
01:58nesnas has quit [Ping timeout: 480 seconds]
02:07nesnas has joined #asahi-dev
02:16nesnas has quit [Ping timeout: 480 seconds]
02:19nesnas has joined #asahi-dev
02:28nesnas has quit [Ping timeout: 480 seconds]
02:33nesnas has joined #asahi-dev
02:42nesnas has quit [Ping timeout: 480 seconds]
02:50nesnas has joined #asahi-dev
02:57rrendec has quit [Ping timeout: 480 seconds]
03:00nesnas has quit [Ping timeout: 480 seconds]
03:10nesnas has joined #asahi-dev
03:20nesnas has quit [Ping timeout: 480 seconds]
03:29nesnas has joined #asahi-dev
03:37pb17 has quit [Ping timeout: 480 seconds]
03:43john-cabaj has quit [Ping timeout: 480 seconds]
03:46tobhe has joined #asahi-dev
03:47nesnas has quit [Ping timeout: 480 seconds]
03:53tobhe_ has quit [Ping timeout: 480 seconds]
03:55nesnas has joined #asahi-dev
03:58pb17 has joined #asahi-dev
04:00jmax_ has quit [Ping timeout: 480 seconds]
04:05nesnas has quit [Ping timeout: 480 seconds]
04:14nesnas has joined #asahi-dev
04:14nora has joined #asahi-dev
04:16nora_ has quit [Ping timeout: 480 seconds]
04:18aditya has joined #asahi-dev
04:21chrisl has quit [Ping timeout: 480 seconds]
04:25nesnas has quit [Ping timeout: 480 seconds]
04:31chrisl has joined #asahi-dev
04:34nesnas has joined #asahi-dev
04:39chrisl has quit [Ping timeout: 480 seconds]
04:44nesnas has quit [Ping timeout: 480 seconds]
04:52nesnas has joined #asahi-dev
05:04nesnas has quit [Ping timeout: 480 seconds]
05:12nesnas has joined #asahi-dev
05:19JayBeeFOSS has quit [Remote host closed the connection]
05:20JayBeeFOSS has joined #asahi-dev
05:22nesnas has quit [Ping timeout: 480 seconds]
05:29nesnas has joined #asahi-dev
05:29chadmeddylantaylor: did you make any changes to asahi-audio other than relabelling the node? /
05:39nesnas has quit [Ping timeout: 480 seconds]
05:42nesnas has joined #asahi-dev
05:52nesnas has quit [Ping timeout: 480 seconds]
05:55nesnas has joined #asahi-dev
06:06zumi_ has joined #asahi-dev
06:06zumi has quit [Remote host closed the connection]
06:10elvishjerricco has quit [Remote host closed the connection]
06:11zumi_ is now known as zumi
06:12elvishjerricco has joined #asahi-dev
07:04nesnas has quit [Ping timeout: 480 seconds]
07:12nesnas has joined #asahi-dev
07:25nesnas has quit [Ping timeout: 480 seconds]
07:30nesnas has joined #asahi-dev
07:40nesnas has quit [Ping timeout: 480 seconds]
07:44nesnas has joined #asahi-dev
07:59nesnas has quit [Ping timeout: 480 seconds]
08:06nesnas has joined #asahi-dev
08:18aditya has quit [Quit: Connection closed for inactivity]
08:38nesnas has quit [Ping timeout: 480 seconds]
08:46nesnas has joined #asahi-dev
08:59nesnas has quit [Ping timeout: 480 seconds]
09:08nesnas has joined #asahi-dev
09:18chaos_princess has quit [Quit: chaos_princess]
09:18chaos_princess has joined #asahi-dev
09:18nesnas has quit [Ping timeout: 480 seconds]
09:27nesnas has joined #asahi-dev
09:29xdbob has quit [Remote host closed the connection]
09:31xdbob has joined #asahi-dev
09:36pb17 has quit [Ping timeout: 480 seconds]
09:38nesnas has quit [Ping timeout: 480 seconds]
09:46nesnas has joined #asahi-dev
09:56nesnas has quit [Ping timeout: 480 seconds]
09:58yuka has quit [Remote host closed the connection]
10:04nesnas has joined #asahi-dev
10:12dylantaylor has joined #asahi-dev
10:13dylantaylorchadmed: I did not need to tweak anything to get this working at all. The PR to correct the node name is just aesthetic.
10:13pb17 has joined #asahi-dev
10:14nesnas has quit [Ping timeout: 480 seconds]
10:14chaos_princessi somewhat expect this to not be our best sounding machine, since the configs won't fully match the mic array parameters, but it is very cool that it works that well
10:15dylantaylorI really just cloned the asahi-audio repository, did a sudo make install, and then followed your instructions on IRC as logged here. https://oftc.irclog.whitequark.org/asahi-dev/2025-03-21
10:17dylantaylorI didn't realize that tuning is needed in the configuration to match the mic array parameters. What's involved with that? In my initial testing (see the filebin link I posted earlier), I feel it was of reasonable quality.
10:18dylantaylorIn mu opinion, it sounds reasonable enough to ship it. I think users of this machine will appreciate mic support earlier followed by fine-tuning down the line
10:19chaos_princesshttps://github.com/AsahiLinux/asahi-audio/commit/221a10c0e9dc1a3d7651760b3bc8cbc053062bfa#diff-d2f83af17b7a0e7b864451baa5acadd85ae2d72f5e95596166b39cf0240a9d62R38 - this is the mic array parameters, those should match the physical locations, but if the current ones work well enough - ship it
10:20nesnas has joined #asahi-dev
10:21chadmedchaos_princess: those are the ones dylantaylor tested
10:21chaos_princessbut if i understood it correct, you copied those from j313, and those arent a perfect match, right?
10:21chadmednah those are my guesstimate based on the actual j293 mic array teardown by ifixit
10:21chadmedhave a look at the other commit on mics branch, j313 was wrong :p
10:23chadmedalright if we're happy ill merge dylantaylor's MR, pull those commits into main, do the same for the ucm thingy, then tag releases
10:23dylantaylorwell, I'm not going to teardown my machine, but if I can tell you anything about it to help you figure out the correct parameters let me know
10:23chaos_princesschadmed: do you think the frequencies and gains are ok?
10:23chadmedchaos_princess: they sound okay in the recording that i got yesterday but ill try and source a j293 machine and fine tune things. i want to "properly" tune all the mics on all the machines with FIRs like we do for the speakers
10:24chaos_princessmaybe get dylantaylor to play a frequency sweep?
10:24chadmednah its not useful to do that for mics. all you're hearing is the speaker's frequency response
10:24yuka has joined #asahi-dev
10:24chadmedmics have to be tuned by ear or with stupidly expensive reference gear
10:25chaos_princessits probably would be cheaper to expense you a j{2,4}93 then :P
10:25chadmedyeah. or someone else can have a crack at tuning it first :p
10:26chaos_princessi still have the dang audacity issue on my install
10:26dylantaylorI know how expensive it is acquiring hardware for developing this project is, so if I can save you several hundred USD on a used MacBook, I'd be happy to
10:26chadmedsmdh before i tag another release ill try to work around this stupid shit in our vendored version of the script
10:26chadmedi blame equinix for this still being an issue
10:27chaos_princessfdo gitlab is up already, no?
10:27chaos_princessthey just dont have ci runners/s3
10:27chadmedbanner still says "consider repos readonly" or something to that effect
10:27chadmedim hoping we'll be back in action tomorrow
10:27dylantaylorI think they're still syncing the artifacts from the old GitLab install
10:27chadmeddylantaylor: that finished earlier today i think
10:28chaos_princessalso fdo gitlab is finally no longer absurdly slow. though we shall see what will happen once they start runners
10:28dylantaylorI set up GitLab CI/CD at an old job - getting the runners up is actually really easy. I bet the historical data is the bottleneck
10:28chadmedyeah they had like 100 trillion terabytes of logs and artefacts
10:28chaos_princessprobably would be faster to hire an aws snowmobile or sth at that point :P
10:29chadmedtake the disks out of the equinix rack, mail them to hetzner
10:29nesnas has quit [Ping timeout: 480 seconds]
10:29dylantaylorI saw that AWS offered to host FDO for free, I'm surprised they didn't do that. EKS would have probably been a great approach. I understand that they wanted to not have infrastructure tied to a sponsorship though.
10:30chaos_princessaws is _expensive_ if they drop the sponsorship
10:30chaos_princessand moving out of there in that case is a yikes
10:31dylantaylorOh, I know. I'm a DevOps engineer professionally and manage AWS at work. I've seen our cloud bills. :)
10:32chadmedyeah migrating off AWS or Azure services is just.... so painful
10:32dylantaylorIt is very easy to get vendor-locked too.
10:32chadmedoh dont i know it :)
10:32chadmedthe flog at work i replaced was a full azure+power apps shill
10:33chadmedgot "asked to leave" from here, went to another place promising to replace their entire ESM platform with fucking power automate, got fired after like 8 months
10:34chaos_princessi dont get people who use azure tbh
10:34chadmedms graph is a _really_ nice API to be fair, and if youre a legacy business with a whole bunch of microsoft services its a really easy migration
10:34chadmedAD->Entra is so easy
10:35chadmedunfortunately in a lot of established businesses that have existed longer than like 15-20 years, whatever microsoft is offering is just the default and youre "wrong" if you suggest using anything else
10:35chaos_princessnobody got fired for suggesting msft, and so on?
10:35svenjannau: https://github.com/AsahiLinux/m1n1/pull/453 hope it's fine that i also added you to CODEOWNERS since you know the m1n1 codebase quite well
10:35chadmedwell except the guy above :p
10:36chadmedbut yeah its basically that. no one gets fired for deploying exchange or o365 even if it costs $5,000,000 and takes 18 months
10:36nesnas has joined #asahi-dev
10:36dylantaylorWhere I work, we've gone through some mergers, so we have multiple competing solutions in the same org. For instance, for business intelligence, it's SAP or Power BI. Last I heard, we want to evaluate also having QuickSight. You mentioning power apps reminded me of how annoying the administration component of that mess is. I don't love the Windows server requirement, and of course none of it supports WS core or
10:36dylantaylorcontainerization.
10:37svenalso, #asahi-offtopic please
10:38jannausven: approved
10:38svenand merged :)
10:43dylantaylorjannau, would you be good with approving https://github.com/AsahiLinux/linux/pull/380 too? That should probably be coordinated with merging the mics branches of the other projects into main.
10:44dylantaylorFull disclosure, I've never written a proper kernel patch, but this is straight-forward enough that I don't have any worries about breakage.
10:47nesnas has quit [Ping timeout: 480 seconds]
10:50nesnas has joined #asahi-dev
10:52jannaudylantaylor: we can change the kernel only after the working user space is deployed
10:53dylantaylorOh, that makes sense. I'm not familiar with the development process.
10:53jannauplan is to revert the commits adding the "apple,no-beamforming;" first and then to drop them on the next rebase
10:54dylantaylorThat makes sense. In which case, my PR isn't needed. No big deal. Having a small commit with my name on it would have been neat from a vanity point of view, but your approach sounds better.
10:56dylantaylorThe way you're doing it sounds cleaner and therefore easier to upstream, which I understand is a big priority now.
10:56chadmedall these commits will be squashed/lost on upstreaming anyway. this is just so we can control the rollout
10:56dylantaylorMakes sense.
11:08jannaurecordings with j493 sound compared to j314 comparison if it could use more tuning. (or beamforming changes). not sure how they sound in macos though
11:10chadmedit's probably both
11:10chadmedon one hand, the mics are probably just worse but also i did basically guess for the parameters so....
11:11nesnas has quit [Remote host closed the connection]
11:11nesnas has joined #asahi-dev
11:15dylantaylorI don't know how you guys keep track of all of these codenames. I have to pull up https://en.wikipedia.org/wiki/List_of_Apple_codenames just to tell what device you're chatting about. I guess after a while it becomes second nature?
11:16svenyeah, same thing usually happens at $work with domain specific language and abbreviations. At the beginning you’re completely lost but after working for a few months you end up speaking in the same code
11:19sventhough I guess that doesn’t list the jXXX names
11:20nesnas has quit [Ping timeout: 480 seconds]
11:22svenhah, that’s what I was looking for :)
11:22svenwas starting to doubt my memories of that page
11:30nesnas has joined #asahi-dev
11:33linuxgemini is now known as Guest11941
11:33Guest11941 has quit [Remote host closed the connection]
11:33linuxgemini has joined #asahi-dev
12:01dylantaylorThat list seems to be missing the M4 Mac Studio
12:03dylantaylor(and M3 ultra mac studio for that matter)
12:04dylantaylorThose Mac Studios would probably make great CI machines for M3/M4 - basically Mac Minis on steroids.
12:04svenhttps://github.com/AsahiLinux/docs/blob/main/docs/hw/devices/device-list.md that should be the source file, you can add them and submit a PR to that repo
12:05zumi_ has joined #asahi-dev
12:05zumi has quit [Remote host closed the connection]
12:10zumi_ is now known as zumi
12:13pb17 has quit [Ping timeout: 480 seconds]
12:13sveni'd put the M3 device below the other M3s instead of at the end of the list
12:14dylantaylorOh, alright. I'll update it
12:14svenmight even be sorted by release date or something like that? dunno
12:16dylantaylorwell if it is by release date, the M3 ultra Mac Studio just came out this year
12:16dylantaylor has quit [Remote host closed the connection]
12:17dylantaylor has joined #asahi-dev
12:18svenas i said, i dunno if there's any specific order to the list more than "keep M3s together"
12:21svenor put differently: please briefly check if there's any additional order in that table. if there's nothing obvious i'm happy with "keep the M3 studio below the other M3 machines"
12:32pb17 has joined #asahi-dev
12:37dylantaylor has quit [Remote host closed the connection]
12:39dylantaylor has joined #asahi-dev
12:42nesnas has quit [Ping timeout: 480 seconds]
12:51nesnas has joined #asahi-dev
13:04nesnas has quit [Ping timeout: 480 seconds]
13:12nesnas has joined #asahi-dev
13:13dylantaylor has quit [Ping timeout: 480 seconds]
13:23chadmedi really really dont any excuses for a v5 since i already need to rewrite large chunks of macaudio to accommodate the requested changes as it is
13:23nesnas has quit [Ping timeout: 480 seconds]
13:26chadmeda couple of the patches in the series got pulled for stable so ill wait for those to work their way in before resubmitting anyway
13:30nesnas has joined #asahi-dev
13:33chaos_princessalso make sure you run yamllint on all that stuff
13:36chadmedit didnt complain
13:36chaos_princessprobably fine then
13:39nesnas has quit [Ping timeout: 480 seconds]
13:39nesnas has joined #asahi-dev
13:48dylantaylor has joined #asahi-dev
13:49nesnas has quit [Remote host closed the connection]
13:50nesnas has joined #asahi-dev
13:59dylantaylor| is correct syntax for a YAML multi-line string
14:00pb17 has quit [Ping timeout: 480 seconds]
14:01dylantaylorIt can also be > if you want it to not add new lines
14:04dylantaylorHuh. I think in this case, it makes sense as it is not a multi-line string - just a short literal. | makes sense if you have a whole block of text
14:04dylantaylorFor the longer one, | should be okay
14:05dylantaylor"Apple is not unique, special or exceptional." Ouch, that feels personal lol
14:17lynndotpy has quit [Quit: bye bye]
14:19lynndotpy has joined #asahi-dev
14:21nesnas has quit [Ping timeout: 480 seconds]
14:22pb17 has joined #asahi-dev
14:24dylantaylor has quit [Quit: Leaving]
14:29nesnas has joined #asahi-dev
14:31aditya has joined #asahi-dev
14:39nesnas has quit [Ping timeout: 480 seconds]
14:48nesnas has joined #asahi-dev
14:56chadmed has quit [Quit: Konversation terminated!]
14:56chadmed has joined #asahi-dev
14:57chadmed has quit []
14:57chadmed has joined #asahi-dev
15:02nesnas has quit [Remote host closed the connection]
15:02nesnas has joined #asahi-dev
15:08opticron has quit [Read error: Connection reset by peer]
15:09opticron has joined #asahi-dev
15:21dylantaylor has joined #asahi-dev
15:56mischa85 has joined #asahi-dev
16:02mischa85well i'm on t6041 duties again. fresh start. BRINGUP trying to see what's going on in cpu_init(). already freezes when we try to set SYS_IMP_APL_EHID4 / SYS_IMP_APL_HID4 which seemingly works on every other soc m1n1 has ever seen? is t6041 just an exception to the rule or is there something else going on?
16:03mischa85also freezes on the NEX powergating part: SYS_IMP_APL_HID13 / SYS_IMP_APL_HID14
16:12chaos_princessyea, you might want to skip SYS_IMP_APL_EHID4, SYS_IMP_APL_HID4, SYS_IMP_APL_CYC_OVRD, and probably a few more
16:12chaos_princess(and nex powergating)
16:19mischa85yeah it's frustrating. i'll see if *anything* in chickens.c works on t6041
16:21pb17 has quit [Ping timeout: 480 seconds]
16:26svenrealistically the only way to get the chickens is to grab them from xnu
16:30chaos_princessno, you need to run it in hv
16:30chaos_princessor, y'know, grep the disassembly for the register writes
16:30mischa85but that's what i'm trying lol
16:31chaos_princessfor hv, just skip all chickens for now, only enable 1 ecore and hope that is enough to reach macos
16:34mischa85this one e-core should be enabled already right? as it's what m1n1 is running on?
16:34aditya has quit [Quit: Connection closed for inactivity]
16:36chaos_princessjust make sure you are not starting other ones
16:36chaos_princessnot like you can, but in the sense that you should skip that code
16:40mischa85ok i'll take out smp_start_secondaries() completely
16:41mischa85just using the core we got powered on for free is not something i tried yet
16:43sventhe chicken setup happens fairly early inside xnu so you don’t even need many thing to work
16:47mischa85 has quit [Quit: leaving]
16:47mischa85 has joined #asahi-dev
16:47pb17 has joined #asahi-dev
16:56rrendec has joined #asahi-dev
17:04jannaudoesn't m4* start on a performance core like m3?
17:05mischa85i think i've seen it having core 0.4 started up
17:08mischa85but i think i has e and p cores swapped earlier, MIDR is 0x611f0591 which i think suggest the e-cores are 0x59 and p-cores are 0x60
17:11nesnas has quit [Ping timeout: 480 seconds]
17:18jannaushould be visible from the device adt. the running core has 'status = "running"';
17:21nesnas has joined #asahi-dev
17:22gladiac has joined #asahi-dev
17:22mischa85yep, cpu4. everest core
17:27mischa85just trying to fix this stupid pyserial thing which somehow doesn't work on linux but does on macos
17:27nicolas17I was going to submit the newest devices but I waited until we actually knew details on M3 Ultra, then I forgot >.>
17:28mischa85so i can actually use the cs on my main rig and test to see if hv works
17:36nesnas has quit [Ping timeout: 480 seconds]
17:41nesnas has joined #asahi-dev
17:53nesnas has quit [Ping timeout: 480 seconds]
17:54nesnas has joined #asahi-dev
18:01catred has quit [Remote host closed the connection]
18:03nesnas has quit [Ping timeout: 480 seconds]
18:04zumi_ has joined #asahi-dev
18:05zumi has quit [Remote host closed the connection]
18:09zumi_ is now known as zumi
18:12nesnas has joined #asahi-dev
18:15dylantayloroh, cool to see that's up already. I guess it's just staticly published to github pages. Pretty clean design.
18:20fl0_idmischa85 which thing are you having trouble with? the pyserial that the proxyclient uses with picocom or which part? Pretty sure I used it from Linux and it worked, maybe I can check it there
18:21mischa85yeah it's probably an rtscts or dsrdtr thing, but i just cannot get my head around the python code in proxy.py, where does it even open the port and how are the settings parsed
18:21mischa85minicom works totally fine
18:22mischa85every 4 tries it receives some data but the checksum is wrong
18:22nesnas has quit [Ping timeout: 480 seconds]
18:22mischa85i cannot stand python sometimes
18:25mischa85it sets a "device =" as a environment variable but then goes on to say device = Serial(serial.devpath, baud)
18:25mischa85how does that syntax even make sense
18:25mischa85where is the pyserial open() call then
18:25mischa85so confused
18:29mischa85 has quit [Quit: Lost terminal]
18:30nesnas has joined #asahi-dev
18:36nesnas has quit [Remote host closed the connection]
18:37nesnas has joined #asahi-dev
18:40pb17 has quit [Ping timeout: 480 seconds]
18:41catred has joined #asahi-dev
18:44mischa85 has joined #asahi-dev
18:46nesnas has quit [Ping timeout: 480 seconds]
18:53nesnas has joined #asahi-dev
19:03nesnas has quit [Ping timeout: 480 seconds]
19:12nesnas has joined #asahi-dev
19:23dylantaylor has quit [Quit: Konversation terminated!]
19:24pb17 has joined #asahi-dev
19:25nesnas has quit [Ping timeout: 480 seconds]
19:33nesnas has joined #asahi-dev
19:37xal has quit [Quit: bye]
19:37xal has joined #asahi-dev
19:43nesnas has quit [Ping timeout: 480 seconds]
19:52nesnas has joined #asahi-dev
20:03nesnas has quit [Ping timeout: 480 seconds]
20:10nesnas has joined #asahi-dev
20:20nesnas has quit [Ping timeout: 480 seconds]
20:26nesnas has joined #asahi-dev
20:43MountainRose has joined #asahi-dev
21:14pb17 has quit [Ping timeout: 480 seconds]
21:21opticron has quit [Read error: Connection reset by peer]
21:21opticron has joined #asahi-dev
21:34greguu has quit [Ping timeout: 480 seconds]
21:46zerozerozero has joined #asahi-dev
22:01pb17 has joined #asahi-dev
22:36fl0_idmischa85 there is this... https://www.mypy-lang.org/ - it's like static types based on python type hints
22:37ddxtanx has quit [Remote host closed the connection]
22:44fl0_idmischa85 prob you are a bit further now, but pyserial docs say "The port is immediately opened on object creation, when a port is given. It is not opened when port is None and a successive call to open() is required." so the open() is in pyserial presuambly
22:46mischa85yes i am back on my trusty macbook which consistently gave me errors on the cleaned up m1n1 i had. only wanted to work on 115200 kbps. now back on the mess i made which is working fine. probably still not on my main rig on linux but i can't have too many variables right now
22:46mischa85at least i can now get to disabling enough m1n1 so i can run xnu kernel on hv
22:47mischa85it's consistenly booting on cpu4
22:48mischa85still waterfalls after Mapping MMIO range so let's see what's causing that
22:48mischa85at least now i can run it on 1.5 mbaud again which will come in handy once we're actually goint to transfer that xnu blob
22:49fl0_idsounds good :)
22:49fl0_idout of context waterfalling sounds nice haha
22:49PaulFertserGood old strace can give a quick hint about the differences between minicom and pyserial, sometimes it's faster to view the log of syscalls to see what exactly happens there.
22:49mischa85that's a nifty idea
22:53mischa85i just gotta accept my m1n1 branch is a total mess for now
22:55chaos_princessimo, skip memory mapping too, and launch xnu as-is
22:55chaos_princessit will most likely blow up, but hopefully you will be able to capture msr write traces before it does
22:55mischa85ack, on it
22:57nesnas has quit [Ping timeout: 480 seconds]
23:01balrog has joined #asahi-dev
23:02balrog_ has quit [Ping timeout: 480 seconds]
23:06nesnas has joined #asahi-dev
23:10mischa85alright progress. i can get to to the Loading kernel image (0x6dd0000 bytes)... part
23:10mischa85had to disable amx and guest ap keys part tho
23:11mischa85but now i'm getting a serialexception from serialposix.py
23:11chaos_princessamx problably no longer exists on m4, since they have sme
23:12chaos_princesscan you modify the upload code to give you percentage process, to see when exactly it goes wrong
23:16pb17 has quit [Ping timeout: 480 seconds]
23:19pb17 has joined #asahi-dev
23:22mischa85first try stopped at 0x2187450, going to try a second time to check if it's consistent
23:24mischa85again, 0x2187450
23:25nesnas has quit [Ping timeout: 480 seconds]
23:25mischa850x6dd0000
23:25chaos_princesscan you generate a random file of that length and try uploading that?
23:29zerozero1 has joined #asahi-dev
23:31zerozero1 has quit []
23:33mischa85construct.core.StreamError: Error in path (parsing) -> cmds -> args
23:33nesnas has joined #asahi-dev
23:33mischa85the random file doesn't upload at all as it fails some parsing (makes sense)
23:33chaos_princessRight, i think it has to be a mach-o
23:34chaos_princessOk, can you find a different kernel image
23:35chaos_princessdifferent version or something
23:35zerozerozero has quit [Ping timeout: 480 seconds]
23:35chaos_princesswant to figure out if it is a uart problem and some pattern in the file breaks it, or m1n1 crashes due to some other reason
23:36chadmedi had trouble with m1n1's heap not being big enough for certain payloads a while ago but i dont think it's that unless the kernel is now 1 GB
23:38mischa85the one i use right now matches the one on the macos partition m1n1 is running from
23:38mischa85but lemme gather a different one for science
23:39mischa85i still have a seperate partition on 15.1 because anything newer bootloops before m1n1 even loads
23:40chadmed has quit [Quit: Konversation terminated!]
23:41chadmed has joined #asahi-dev
23:45nesnas has quit [Ping timeout: 480 seconds]
23:54nesnas has joined #asahi-dev
…