#asahi · 2021-07-30 18:44
pipcet[m]but at least I know your kernel starts fine and sees the nvme#asahi · 2021-07-30 18:44
pipcet[m]and now I'm failing to trigger it deliberately :-(#asahi · 2021-07-30 18:44
pipcet[m]MacBook Pro#asahi · 2021-07-30 18:31
pipcet[m]alyssa: the problem here is a reboot doesn't help us recover from this condition, which I think is a tad worse than anything panfrost might reasonably break :-)#asahi · 2021-07-30 16:35
pipcet[m]what, why not? Does it break nvme?#asahi · 2021-07-30 16:30
pipcet[m]you're right, if it's only a broken driver that upsets things to the point your driver can't recover, the solution is not to use the broken driver in the first place :-)#asahi · 2021-07-30 16:29
pipcet[m]sven: thanks! I'll give it a try#asahi · 2021-07-30 12:59
pipcet[m]the failure to flush might actually be an issue on intel as well, it's hard to tell since it's rare to have a fat-only nvme, I think...#asahi · 2021-07-30 12:56
pipcet[m]I can still start m1n1 in the persistent broken state, so if there's a specific kernel I could test to see whether it's fixed with or by your driver, that would be perfect.#asahi · 2021-07-30 12:56
pipcet[m]sven: indeed. two issues: one's the persistent broken state that only goes away if I boot into Recovery Mode, the other's a failure to flush if the only filesystem mounted on the nvme is fatfs (Linux flushes things differently for different filesystems and the btrfs/ext4 way works while the fat way doesn't)#asahi · 2021-07-29 16:17
pipcet[m]really? I have no namespace 0 on the M1, and no namespace 0 on the intel machine...#asahi · 2021-07-29 13:02
pipcet[m]it's a broadcom chip that's decidedly weird compared to the others, though, and I don't think that's just different firmware#asahi · 2021-07-29 12:58
pipcet[m]I'm a bit surprised Apple actually licensed a broadcom chip instead of doing their own thing entirely, though.#asahi · 2021-07-29 00:10
pipcet[m]when in doubt, listen to marcan :-)#asahi · 2021-07-29 00:08
pipcet[m]sorry about that. I think all you need to play with m1n1 is the .macho, boot into recovery mode, open a terminal, run *util in the right order and with the right parameters, and reboot. you definitely do want to keep macos around on the nvme, though#asahi · 2021-07-28 23:59
pipcet[m]mtecknology: you mean the bputil/csrutil/kmutil stuff, or setting up a dual-boot environment?#asahi · 2021-07-28 23:53
pipcet[m]and UART on the fifth?#asahi · 2021-07-28 23:50
pipcet[m]so I'll just keep the power in one type-C port, the serial console for debugging in the other, and use the third one for audio? :-)#asahi · 2021-07-28 23:45
pipcet[m]it is backwards, I'm using the M1 for everything but music since I can't figure out how to get audio working :-)#asahi · 2021-07-28 23:41
pipcet[m]hi! my debootstrap stuff is currently broken, I'm afraid, if you're looking at that. You can install debian from it, I'm pretty sure.#asahi · 2021-07-28 20:25
pipcet[m]sven: so much for things getting there "slowly" :-)#asahi · 2021-07-28 18:18
pipcet[m]oh, I see. that might mean I'm not definitely insane yet :-)#asahi · 2021-07-28 18:12
pipcet[m]does it do that too? what horrible kind of witchcraft is this?#asahi · 2021-07-28 18:11
pipcet[m]when macOS crashes hard enough (or I enter the hypervisor), the clickpad on the MBP stops clicking. It's the weirdest thing.#asahi · 2021-07-28 16:30
pipcet[m]that would be wonderful, at some point we're going to figure out how to make that thing produce audio :-)#asahi · 2021-07-28 16:28
pipcet[m]which ones are rtkit-based? SIO, DCP, AOP?#asahi · 2021-07-28 16:26
pipcet[m]that is awesome, though!#asahi · 2021-07-28 16:24
pipcet[m]probably not relevant yet, but there are just too many of those...#asahi · 2021-07-28 16:20
pipcet[m]sven: you've got a mini, right? How many SMC keys do you have?#asahi · 2021-07-28 16:19
pipcet[m]weird memory accesses that are probably never used for MMIO space, but are used for DMA memory#asahi · 2021-07-28 16:16
pipcet[m]I suppose no one's done any work towards making the HV trace LDNP, LDADDL, etc.?#asahi · 2021-07-28 16:07
pipcet[m]alyssa: sudden motion is just 0g detection, right? You're paying for my space trip.#asahi · 2021-07-28 16:06
pipcet[m]I've, uh, "tested" high temperature conditions by forgetting I was compiling stuff and putting my MBP back in the bag...#asahi · 2021-07-28 16:05
pipcet[m]set it on fire AND drop it on the floor#asahi · 2021-07-28 16:05
pipcet[m]have you tried setting your device on fire? It might be for high temperature conditions!#asahi · 2021-07-28 16:04
pipcet[m](possibly it's for the SMC when it needs to talk to ANS without involving the AP?)#asahi · 2021-07-28 16:03
pipcet[m]the ANS has an SMC endpoint?!#asahi · 2021-07-28 16:01
pipcet[m]I've been meaning to write code for the lid switch (which works the same way on the MBP)#asahi · 2021-07-28 16:01
pipcet[m]cool!#asahi · 2021-07-28 16:00
pipcet[m]you get different messages if you hold it for a while, IIRC :-)#asahi · 2021-07-28 13:19
pipcet[m]you're not using an initrd at all?#asahi · 2021-07-26 18:13
pipcet[m]alyssa: congratulations, you're famous. Seriously, though, all that attention has to be a good thing :-)#asahi · 2021-07-26 13:58
pipcet[m]yes!#asahi · 2021-07-26 13:57
pipcet[m]have you decided how to do the nvme yet? fake PCI bus, or adding non-PCI functions to the NVMe code?#asahi · 2021-07-26 13:55
pipcet[m]SMC and ANS have no-shutdown#asahi · 2021-07-26 13:50
pipcet[m]so...ASC might just describe the mailbox part?#asahi · 2021-07-26 13:38
pipcet[m]doesn't the definition of "panic" preclude its being recoverable? seriously, Apple terminology is hard.#asahi · 2021-07-26 13:34
pipcet[m]is it separate chips, though? I thought it was all one die?#asahi · 2021-07-26 13:32
pipcet[m]alyssa: the "gfx" has both "iop" and "asc" nodes in the ADT, but that's too many TLAs for me :-)#asahi · 2021-07-26 13:26
pipcet[m]er, the initrd is loaded with the kernel