2021-07-29
00:04MTecknologyThat question went a bit over my head, particularly the *util stuff. I don't care to leave mac on here either (if it's not required, I think I read that m1n1 is sorta mini s/unix/mac/).
00:06marcanMTecknology: you probably want to leave macos on there for updates, we're going to recommend dual-boot for a long while until we figure out a way to do firmware updates from linux
00:08pipcet[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
00:08marcanMTecknology: but yeah, right now the recommended thing to do is follow the dev guide to get things installed
00:08marcanthe main purpose of the dev guide is to get people to install a second macos partition to replace with linux; our installer will eventually do that without the macos step, but for now this is how it goes
00:09MTecknologyDoes the dev guide still apply to a dual boot?
00:10marcanand the reason for that is that dual-booting is a low level feature on these machines; you need multiple "native" macOS installs (from the POV of the machine) to do it sanely
00:10marcanright *now* it doesn't matter much and you can do what pipcet[m] says and just stuff m1n1 on top of a single macOS install
00:10MTecknologywhew... if I were still drinking (unfortunate project name for me... many fond memories where that beer was involved), I'd be grabbing a few cans of asahi to drink while reading the guide
00:11marcananyway, the dual boot thing will start mattering soon, among other things because I'm going to be requiring people to use specific macOS versions as a base (for firmware ABI reasons; it's unstable) and because the SEP will be very unhappy if two OSes try to use the security stuff in one context
00:12marcanbasically Apple designed the thing for dual-boot at *their* level and we have to use it if we want to keep things sane :)
00:12MTecknologyWhy do I suspect that even underneath, they treat every minor revision number as an excuse for absolutely any changes they feel like?
00:13marcanhalf the firmwares are part of the OS boot bundle, so yes, they don't care about stability
00:13MTecknologyjust like golang! :P
00:13marcanin fact, uh, I've been ranting about this recently but the way they did their display controller firmware is to just take their driver and move *half* of the classes to firmware, then build an RPC mechanism that lets them call back methods on the other side, in both directions, with multiple execution threads even
00:14marcanthis is why I've decided there will be "blessed" macOS bootloader bundles (=firmware bundles) that Linux supports
00:15marcanthankfully none of this matters if you do native dual-boot, as the OSes have separate bundles, so the real macOS install can be updated separately
00:16marcanthe eventual installer will prompt you for a bundle/version to use out of the list of blessed ones, and handle installing all that without involving a full macOS install
00:17marcanand the idea is that it'll prompt you for a distro image to install out of a list of supported ones (whatever people feel like maintaining), or you can just install the base m1n1+u-boot and make space on the partition table, and then handle the actual distro install like on any other ARM64 UEFI system, since you could boot from USB after that point
00:19MTecknologyany thoughts toward disk encryption? Will it be possible to use native mac utilities for that?
00:20* MTecknologyis getting excited and starts going through the documentation
00:20marcanI'm not sure how that's done at the NVMe level, but at the very lease you could hook the SEP into dm-crypt and get secureboot-tied disk encryption that way
00:21marcanI think macOS does some fun stuff with per-file keys and such, or can (for iOS use cases), which is one reason why they extended (=broke in incompatible ways) their NVMe implementation
00:22marcaneventually I want to get PAM integration with the SEP so you can use hardware password verification, Touch ID, and all that from linux
00:23marcanparticularly interested in whether we can us ed25519 keys in that framework; right now you can create ecdsa ssh keys on macOS backed by the SEP, because that's all their user API supports, but I think the low level API probably does ed25519 too
00:39MTecknologyrevive, eh?
00:40MTecknologythat's an interesting feature only possible by limiting the hardware your OS can run on
00:42MTecknologywow... I now wish I got the 500GB model.
00:48MTecknologyAccording to the disk utility, I'm only using 15.4 GB. Can I just make my first command 'diskutil apfs resizeContainer disk0s2 50GB' instead and leave the rest the same?
00:51marcanwhich means plugging it into another linux box with a USB cable and running idevicerestore, for us :)
00:51marcanthankfully the libimobiledevice guys already implemented M1 support into it some time ago
00:53MTecknologythere isn't going to be a whole lot of room for linux after 70 for the main os plus 70 for the stub... I had planned (and might still plan on) trying to run my work VM from within linux on this hardware.
00:54MTecknologyI'll just appreciate it that much more when it's no longer needed. :D
00:59MTecknologycrud, I didn't read far enough in advance of running commands and just ran the addPartition commands. I didn't realize I should have been looking at diskutil list to figure out what the right disk name was.
01:01MTecknologyI /think/ it looks like the docs are perfect for a default setup so they worked anyway. At least, I see that the LR volume created is 104 GB, which is what I expected. 70+70+1+104 == 245 ~= 250 GB
01:02* MTecknologyreads more betterer from now on
01:02MTecknology(+5 GB recovery)
01:04MTecknologyRDR2 is already over 100 GB, and you can't expect me to not be playing that through linux on M1, can you?
01:06MTecknologyred dead redemtion 2; a game that actually has better performance through valve's compatibility layer than on native windows
01:11MTecknologylucky bastards... once it starts crashing for me, it doesn't stop crashing. At best, I might get 5 minutes without rebooting back into windows and back into linux to clear whatever with nvidia
01:11MTecknologyor something like that... irunno
01:12MTecknologyWhen it actually works, I can get weeks of play time (I leave it loaded once it's working) without a crash.
01:15MTecknologyWhat crash were you referring to?
01:16marcanthough at this point, by the time I start writing the DCP driver and fixing the firmware version required, I'll probably spend a few days writing an install/update script that can avoid having to do a full macos install
01:16marcanbeen thinking a lot about that in the background, just haven't started writing the code :)
01:17marcanjust needs to be enough for the paired recovery (new thingy required in 12.0...) and the bootloader/firmware blobs
01:21flying_sausages has quit []
01:22flying_sausages has joined #asahi
01:29MTecknologyyep, that'll be quite the savings indeed
01:42chadmedmarcan: 70GB? i cant believe how inefficient macos has become. i remember back in the day when i got snow leopard running on my phenom ii pc off a single layer installer dvd and a 16gb root partition. bringing across all the ios apis really has been a mistake
02:10MTecknologyThe craziest part of 70 GB is how the final install isn't /that/ big.
02:10hashcheck has joined #asahi
02:12chadmedmacos userspace is based on gentoo now, and so it requires space for all the sources to be downloaded and built :-P
02:26MTecknologyawe... "If everything went well, you can restart and boot into m1n1!" --> "Custome kernel failed to boot."
02:27MTecknologyoh, I missed a step, where was that..
02:29MTecknologyah, the thing I thought I missed was the environment variable for the other option.
02:31PhilippvK has joined #asahi
02:34phiologe has quit [Ping timeout: 480 seconds]
02:56hashcheck has quit [Quit: Textual IRC Client: www.textualapp.com]
03:18MTecknologym1n1!!!
03:19marcanchadmed: it's their updater. it has to download the update once, then install it to a snapshot, on top of the existing OS
03:58klangelooking forward to finally joining the club... between august 9th and 11th, because I had to have an US-QWERTY keyboard instead of a JIS one that would have been in stock locally... also maybe that joke about 'm1 toaruos when' might be less of a joke
04:27yuyichao_ has quit [Ping timeout: 480 seconds]
05:07yuyichao has joined #asahi
05:07quarkyalice has joined #asahi
05:51quarkyalice has quit [Ping timeout: 480 seconds]
05:51bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:17svenalso, please double check the endpoint id -> class assignment. iirc they were wrong at some point and i'm not sure i fixed them
06:47hashcheck has joined #asahi
06:52MTecknologyhrm... where was I, before my cat decided to get hurt and crap all over a room (plus a vet visit)?
06:55MTecknologyI have my mac mini booted up to m1n1 with the last line saying 'Running proxy...' I built linux from the asahi/linux branch, grabbed the debian initrd, and.... I'm getting a python error. Definitely not the kind of error I expected getting so close to what should be actually running something.
07:03MTecknologyrm -rf ~/.pip_dir; then replacing that pip install serial w/ pyserial seems to have worked. Now it's complaining about 'could not open port /dev/ttyACM0:' which I imagine has to do with the thunderbolt cable or something.
07:03MTecknologyjix: nice, thanks! :)
07:05MTecknologyWith this thing booted up to m1n1, if I connect my (linux) laptop to the thunderbolt port closest to the power plug using a cable that I'm super confident is a proper thunderbolt cable (but possibly not that spec thing...), should I expect to see something showing up in dmesg?
07:06MTecknology(spec thing --> SBU1/2 pins)
07:07MTecknologyI had two 4k displays running using this same cable, so I'm pretty confident about everything except that bit.
07:07marcanMTecknology: you don't need to use any fancy cables for USB mode, which I presume is what you want to use
07:08MTecknologyYeah, usb mode
07:10MTecknologyooooh, there's the usb device!
07:11svenmarcan: can you check if you can write these? i believe the DAPF lockdown bit is different from the DART lockdown bit
07:11MTecknologyaye, thanks for mentioning that. I just got to the installer! :D
07:12bisko has joined #asahi
07:13MTecknologyno keyboard... I saw something about not being able to use the on-board usb-a ports, so I thought using my dock (thunderbolt/usb-c) would work.
07:14svenso on ANS it asks for a physical address and then also sends the same one back but that's expected because it goes through SART
07:14svenon SMC it never asks for an address, it just sends me an address in that mmio shared memory window
07:14_jannau_MTecknology: thunderbolt/pci-e will not work. USB-C should work but has the same contraint of being connected at boot
07:19MTecknology_jannau_: I assume that means "usb-c should work, but not via any usb-c/tb dock"?
07:22MTecknologyI don't have any hub, and the one I used to have was flaky on the best of days. I was going to live with just the keyboard if it had to be connected at boot, but my only usb-a->c adapter is one of those tiny things, so... thanks to apples brilliant orientation of those ports, I can only stick exactly one device in the port closest to the power plug.
07:23MTecknologywhich I need for booting up, so... it seems to proceed further I kinda have to get that dumb hub.
07:24MTecknologyMost docks are basically just a not-dumb usb hub, aren't they?
07:27_jannau_MTecknology: a tb dock will not work unless it can be somehow forced into usb3 mode on the dock side
07:29MTecknologyheheh... that just made me wonder if I can "force" it to usb3 mode by using a cheap cable.
07:29MTecknology(cheap + no tb claim)
07:41MTecknology_jannau_: excellent, it'll be here on tuesday :)
07:43* MTecknologyshould make some docs notes now before forgetting where I stumbled... may as well make a pull request from all of the extra help/info. :)
07:50aleasto has joined #asahi
08:35bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:36ella-0[m] has joined #asahi
08:36bisko has joined #asahi
08:40bisko has quit []
08:41bisko has joined #asahi
08:43bisko has quit []
08:48bisko has joined #asahi
09:00bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:09hashcheck has quit [Quit: Textual IRC Client: www.textualapp.com]
09:15norwoodites has joined #asahi
09:16pinskia has quit [Remote host closed the connection]
09:53pinskia has joined #asahi
09:59norwoodites has quit [Ping timeout: 480 seconds]
10:56bisko has joined #asahi
12:06svenyou can also NMI the coprocessor if the crashlog msg is too slow fwiw. write32(asc_base + 0x10004, 0x11) followed by write32(asc_base + 0x10024, 0x1) i think
12:33cth451_desktop has quit [Remote host closed the connection]
12:33cth451_desktop has joined #asahi
12:50dougallanyone know if it's possible to load modified AGX (or other) firmware? I'm not clear on whether or not that's a security boundary
12:52alyssamarcan: The good news is that with all this firmware tucked away in iBoot, Asahi GNU/Linux-libre will be FSF endorsed 😂
12:56klangewhy is wifi so universally cursed... [don't answer that, I know it's radio transmission laws / paranoia about them]
12:58pipcet[m]I'm a bit surprised Apple actually licensed a broadcom chip instead of doing their own thing entirely, though.
13:01dougall(thanks - bit of a shame from the perspective of exploring the hardware, but probably to be expected since that's effectively what intel and nvidia do)
13:02pipcet[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
13:04_jannau_in addition developing their own 5G modem has probably much higher priority than wifi/bt
13:33phireI do wonder if Apple gets paranoid in their interactions, assuming that other companies will treat Apple like they treat everyone else
13:50Ariadnemodems though, like there are many options that are good on the market now (almost all from qualcomm :p)
13:54cth451_desktop has quit [Remote host closed the connection]
13:55cth451_desktop has joined #asahi
14:04pinskia has quit [Remote host closed the connection]
14:05pinskia has joined #asahi
14:08yuyichao has quit [Quit: Konversation terminated!]
14:23bps has quit [Ping timeout: 480 seconds]
14:36roxfan2 has joined #asahi
14:42roxfan has quit [Ping timeout: 480 seconds]
14:42roxfan has joined #asahi
14:44roxfan2 has quit [Ping timeout: 480 seconds]
15:00yuyichao has joined #asahi
15:06bps has joined #asahi
15:06arndAriadne: I don't think Intel has any modem development left, maybe they just retained the rights to keep selling the old SKUs to existing customers?
15:08Ariadnetho i could be wrong on that claim, should verify with the pmOS crew to see what their picture looks like
15:16arndIIRC most others that build their own chips (spreadtrum->unisoc, samsung, via->intel, infinion->intel->apple, hisilicon, mediatek) license the DSP plus 4g/5g software stack from CEVA
15:22Ariadnei mean i just interact with these things, i admittedly don’t fully understand the supply chain
15:33bps has quit [Ping timeout: 480 seconds]
15:35hablerentand[m]What USB-C to USB-A adapter/hub do you use for keyboard support? I still have not been able to get the USB keyboard to work on my mac mini, and I'd like to rule out that it is not an adapter issue. Thanks in advance!
15:35alyssamarcan: Otherwise if you change multiple properties in a row and you're unlucky with the timing w.r.t vsync you'll get a junk frame in the middle
15:36Spectrejan[m] is now known as GatekeeperJanwithoutBeer[m]
15:40alyssanot just the "first swap", I expect a swap is needed for changing any property at any time
15:45svenunrelated to that, can i just download some $random-distro userland from somewhere? i wanna use nvme-cli and adding that to my initrd sounds painful
15:58sven[ 0.448653] apple-mailbox 277400000.mbox: syslog message: nvme_admin_ans2.c:2729: Invalid namespace 0 <-- i wonder what that's about. afaik this, 0 should be valid namespace :/
16:23bps has joined #asahi
16:28jannausven: https://gist.github.com/jannau/0af6697bb8b08a847ecc32a8a3d3a4f2 is based on the arch linux arm distro config
16:59jbowen has quit [Quit: leaving]
18:42robinp has quit [Remote host closed the connection]
19:37bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:37bisko has joined #asahi
19:44bisko has quit [Quit: Textual IRC Client: www.textualapp.com]
20:00Raqbit has joined #asahi
20:40aleasto has quit [Ping timeout: 480 seconds]
20:40aleasto has joined #asahi
20:47svenpipcet[m]: you've had some issues with nvme, haven't you? any simple way to reproduce them?
20:48sventhe worst i managed to do were these syslog message when trying to read from one of the other two namespaces:
20:48svenapple-mailbox 277400000.mbox: syslog message: util.c:4121: element=PANICLOG written size=2097152, host request trimmed to end of written content
20:48svenapple-mailbox 277400000.mbox: syslog message: util.c:4145: Util read unmap element: 8, lba: 512, size : 24
21:28roxfan2 has joined #asahi
21:34roxfan has quit [Ping timeout: 480 seconds]
21:42kenzie has quit [Quit: The Lounge - https://thelounge.chat]
21:48kenzie has joined #asahi
22:19grange_c has quit [Ping timeout: 480 seconds]
22:19hl` has joined #asahi
22:30grange_c has joined #asahi
23:29aleasto has quit [Quit: Konversation terminated!]
23:40alyssasven: +"coprocessor sent shmem buffer with 0x%zx bytes at 0x%llx outside of the configured region 0x%llx...0x%llx",
23:59yuyichao has quit [Ping timeout: 480 seconds]