#
…

2021-01-11

00:01amw1 has quit [Ping timeout: 256 seconds]
00:04aratuk has joined #asahi
00:08Bublik has quit [Remote host closed the connection]
00:09aratuk has quit [Ping timeout: 265 seconds]
00:09Bublik has joined #asahi
00:13amw1 has joined #asahi
00:17Bublik has quit [Ping timeout: 256 seconds]
00:17amw1 has quit [Ping timeout: 240 seconds]
00:18rwhitbytoday I'm going to get the pre and post external boot partition layouts for marcan, and test installation to 128GB USBA flash stick for whoever was asking about that yesterday
00:23Bublik has joined #asahi
00:28Bublik has quit [Ping timeout: 260 seconds]
00:34Bublik has joined #asahi
00:34amw1 has joined #asahi
00:39amw1 has quit [Ping timeout: 256 seconds]
00:49davidrysk[m]it appears that during DFU, macOS sets the passwords of the setup user account _mbsetupuser uniquely which are then used for initial setup... I don't think anyone's dug into how this process works
00:49davidrysk[m](thanks rwhitby for doing some tests)
00:51Bublik has quit [Ping timeout: 264 seconds]
00:53amw1 has joined #asahi
00:53Bublik has joined #asahi
00:53rwhitbynow testing whether you can boot from a setup external disk when the internal disk has been freshly DFU's and not gone through initial setup yet
00:56rwhitbyinteresting. I'm pretty sure I had the external disk set to reduced security and then DFU'd only the internal disk. I have now booted successfully from the external disk (while the internal disk is freshly DFU'd and no gone through initial setup) and the external disk seems to be set back to full security.
00:56davidrysk[m]I think it's likely that they are
00:56davidrysk[m]if they are, we can read /etc/kcpassword, extract the _mbsetupuser password, "decrypt" it, and then use that for bputil
00:57amw1 has quit [Ping timeout: 240 seconds]
00:57davidrysk[m]<rwhitby "interesting. I'm pretty sure I "> hm, I wonder if DFU resets the SEP state in some way
00:57davidrysk[m](e.g. breaking all signatures)
00:58rwhitbyI'm going to check the external disk state in 1TR and then go through the whole process again to confirn what I saw.
00:59Bublik has quit [Ping timeout: 240 seconds]
00:59davidrysk[m]https://github.com/jmahlman/uarts-scripts/blob/master/DEP%20Scripts/com.uarts.DEPprovisioning.public I found a provisioning script that someone uses that seems to run in the context of the _mbsetupuser user and at the end of its execution it deletes /etc/kcpassword
01:01rwhitbyhttps://gist.github.com/rwhitby/9c9ead6b89794702c0007c2f059eaeee <- can't run bputil -d on external disk after internal disk has been DFU'd.
01:02davidrysk[m]rwhitby: does that change if you boot (2) once?
01:02rwhitby(2) has already been booted many times
01:02rwhitby(including just before I did this, yes)
01:02davidrysk[m]grr, interesting
01:02davidrysk[m]we're basically mapping out all the edge cases that Apple didn't test
01:03davidrysk[m]which means we probably should be writing them up to report to Apple as bugs
01:03davidrysk[m]does bputil let you set full/reduced/permissive security on that installation?
01:04Bublik has joined #asahi
01:05rwhitbyit did before I DFU'd the internal disk, and the external disk was disconnected during the DFU
01:07rwhitbygoing to go through this again from scratch, installing to a USBA flash stick external this time, then reducing it's security, then DFUing the internal drive and seeing what the security on the external drive ends up as.
01:09Bublik has quit [Ping timeout: 246 seconds]
01:11Bublik has joined #asahi
01:11rwhitbyinstallation to USBA 126GB Sandisk Ultra seems to be proceeding fine. Didn't have a 64GB handy to test whether that would be big enough.
01:12rwhitbys/126GB/128GB/
01:12jamadazi has quit [Ping timeout: 260 seconds]
01:16Bublik has quit [Ping timeout: 246 seconds]
01:16Bublik has joined #asahi
01:20mark21 has joined #asahi
01:22amw1 has joined #asahi
01:23Bublik has quit [Ping timeout: 264 seconds]
01:25mark21 has quit [Quit: Connection closed]
01:26amw1 has quit [Ping timeout: 240 seconds]
01:32czero64 has joined #asahi
01:34Bublik has joined #asahi
01:39amw1 has joined #asahi
01:39dibas has quit [Ping timeout: 260 seconds]
01:40mrksz has quit [Ping timeout: 264 seconds]
01:44amw1 has quit [Ping timeout: 246 seconds]
01:44czero64 has quit [Ping timeout: 256 seconds]
01:52davidrysk[m]rwhitby: nice
01:57amw1 has joined #asahi
01:58shuffle2 has quit [Quit: WeeChat 2.9]
02:02amw1 has quit [Ping timeout: 240 seconds]
02:02Shizrwhitby: this makes complete sense, the policies are stored on the internal disk after all
02:02Shizno policies to display if they've been wiped
02:03rwhitbyis there an easy way to fingerprint the internal disk before and after changing the security on an external disk to see the difference?
02:04ShizI'd expect the iSCPreboot partition to change and not much else
02:04Shiz(where the policy is stored)
02:04Shizwhat are you looking to know :p
02:04Bublik has quit [Ping timeout: 256 seconds]
02:04klaus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:06rwhitbymarcan asked me to take an internal disk partition map before and after booting an external drive. I didn't see any new partitions or volumes.
02:07rwhitbyso next step is to compare iSCPreboot before and after
02:08Shizah right, /me more awake now
02:09Shizyeah so comparing the internal & external policies would be interesting
02:09Shizas well as the Preboot partition of the internal macOS install
02:09Shizyou can use my tool to dump the policies https://github.com/Shizmob/img4/
02:09Shiz(note that they contain your ECID and such)
02:09rwhitbymy ECID is already public :-)
02:11rwhitbybut point taken, thanks.
02:14amw1 has joined #asahi
02:14Bublik has joined #asahi
02:18amw1 has quit [Ping timeout: 260 seconds]
02:21amw1 has joined #asahi
02:25amw1 has quit [Ping timeout: 246 seconds]
02:27mrksz has joined #asahi
02:27rwhitbyUSBA external flash stick install stuck at 2 minutes remaining for some time now. will cancel and try it again tonight. last message from osinstallersetupd in the last was 15 minutes ago marking 93.9%
02:28rwhitbys/in the last/in the log/
02:28dibas has joined #asahi
02:28dibas has joined #asahi
02:32rwhitbyso back to external disk security. Boot to 1TR, set Security Policy on external disk to Reduced+kext using the Startup Security Utility.
02:32rwhitby(this is with a freshly DFU'd internal disk still)
02:33rwhitby"Recovery is trying to change system settings. No administrator was found." Unable to change security settings.
02:34rwhitbyFYI: scp from 1TR to another machine works well for transferring information
02:35rwhitby(thx davidrysk[m] for the tip)
02:35davidrysk[m]rwhitby: can you look for a /etc/kcpassword file on the macOS partition of a fresh DFU'd Mac?
02:37rwhitbyyep, will do so after I finish initial setup of this internal disk, then reducing the external disk security, then DFUing internal disk again
02:38brentr123[m]This might sounda kinda dumb, but can we just back 1tr so we can do whatever tf we want to it
02:39Shizit's signed and only runs signed code
02:39Shizif it was hackable it would lose its entire purpose as a controlled environment for more privileged SEP access
02:39amw1 has joined #asahi
02:39Shiznot saying 1TR is flawless, but you bet if you exploited a vuln in 1TR to run unsigned code apple would have it patched before you can blink :p
02:40Shizso it's an unstable strategy to begin with
02:41Shizrwhitby: but how are you booting to 1TR if the internal disk is wiped
02:41Shizor is this post-revival
02:41rwhitbyI think many people involved in this project are well past playing cat and mouse with vendors
02:42rwhitbyShiz: oh, I haven't wiped anything yet, I've only been doing DFU full restores.
02:43rwhitbyso 1TR is always there for what I'm doing at the moment. I do intend to do a full wipe at some stage to really test the DFU
02:43amw1 has quit [Ping timeout: 246 seconds]
02:44rwhitbyinteresting. I went through internal disk initial macOS setup, and then back into 1TR and I still can set security on external disk
02:45rwhitbys/still can/still can't/
02:45rwhitbyhmm, now trying to set boot from external disk as startup disk in 1TR and it asks for admin password
02:47davidrysk[m]It's better to figure out what functionality is missing from 1TR and asking Apple to add it
02:48rwhitbybut setting reduced security on external disk with bputil on command line is fine (it asks for password)
02:51rwhitbyReduced Security enabled (smb0): 1
02:52rwhitbyso external disk is clearly marked as reduced security in 1TR
02:54rwhitbyBut boot that external drive and look in System Information->Hardware->Controller says Secure Boot: Full Security
02:54rwhitbyso that's inconsistent with what 1TR reported
02:56amw1 has joined #asahi
03:00amw1 has quit [Ping timeout: 240 seconds]
03:01rwhitbygonna DFU and wipe external disk and start again fresh
03:11addcninblue has quit [Ping timeout: 256 seconds]
03:15amw1 has joined #asahi
03:19amw1 has quit [Ping timeout: 240 seconds]
03:32amw1 has joined #asahi
03:33amboar has joined #asahi
03:36amw1 has quit [Ping timeout: 265 seconds]
03:44ky0ko has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
03:48amw1 has joined #asahi
03:50ransom has joined #asahi
03:52Tokamak has joined #asahi
04:04Bublik has quit [Quit: Bublik]
04:05aratuk has joined #asahi
04:06amw1 has quit [Ping timeout: 246 seconds]
04:06djb has quit [Ping timeout: 260 seconds]
04:11aratuk has quit [Ping timeout: 264 seconds]
04:16Bublik has joined #asahi
04:23amw1 has joined #asahi
04:28amw1 has quit [Ping timeout: 272 seconds]
04:39amw1 has joined #asahi
04:41Bublik has quit [Quit: Bublik]
04:41Bublik has joined #asahi
04:44amw1 has quit [Ping timeout: 256 seconds]
04:56amw1 has joined #asahi
04:59rwhitbydavidrysk[m]: I now have a freshly DFU'd internal drive and a freshly installed external drive. What information do you want before I start testing the security setting stickiness again?
04:59davidrysk[m]can you look if there is a file called /etc/kcpassword on the macOS partition?
04:59davidrysk[m](don't send me the contents)
05:00amw1 has quit [Ping timeout: 246 seconds]
05:01rwhitbydavidrysk[m]: there is no /etc/kcpasswd in 1TR on the DFU'd internal drive, nor in the internal OS drive after DFU but before initial setup.
05:02davidrysk[m]huh, then I sure wonder where the OS is getting the autologin password for initial setup
05:04rwhitbyFirst test: can you boot an external drive before the internal drive has gone through initial setup (i.e. when there's no administrator password set anywhere)
05:09rwhitbyweird: bputil -d reports info for the external drive, but not the internal drive
05:10rwhitbybputil -d then select internal drive installation reports "Could not detect whether selected local policy was BAA signed. Failed to obtain values from the current local policy."
05:11rwhitbybputil -d then select external drive shows the normal current local policy details
05:13rwhitbyRemoving external drive to ensure the mapping is correct confirms that internal drive cannot detect the local policy. Note that neither the internal or external drive have gone through initial macOS setup yet. Internal drive is fresh DFU restore and external drive is fresh macOS reinstall.
05:13amw1 has joined #asahi
05:18amw1 has quit [Ping timeout: 256 seconds]
05:21porky has joined #asahi
05:30rwhitbyStartup Security Utility is unable to modify either internal or external disk.
05:32ransom has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:34hspak has quit [Quit: Ping timeout (120 seconds)]
05:34hspak has joined #asahi
05:34rwhitby(bputil can't set either as well, since we don't know the password for _mbsetupuser)
05:36Tokamak has quit [Remote host closed the connection]
05:37Tokamak has joined #asahi
05:38rwhitbyConfirmed ability to boot and run initial macOS setup on external drive even when internal drive has not yet gone through initial macOS setup.
05:39marcanthis is how it is supposed to work I believe; you need a user on the drive to use bputil
05:40rwhitbySo now I have a user on the external drive, but not on the internal drive. Let's see what 1TR can do with that ...
05:41Tokamak has quit [Ping timeout: 264 seconds]
05:41rwhitbyNext test: 1TR with only internal drive and external drive disconnected - still can't do anything with bputil as expected, so adding a user to the external drive didn't create a user on the internal drive.
05:42amw1 has joined #asahi
05:42rwhitbymarcan: what's strange is that bputil -d was able to display the policy for the external drive before the external drive had a user, but couldn't do the same for the internal drive
05:43marcanwas the internal drive ever booted?
05:43marcan(and the external drive?)
05:44Tokamak has joined #asahi
05:45rwhitbyinternal drive has not gone through initial setup. external drive has.
05:45rwhitbyactually, that was the case even when neither had gone through initial setup
05:45rwhitbyand both wanted _mpsetupuser credentials to change security.
05:46rwhitbybut that was good enough to display the external, but not to display the internal.
05:47amw1 has quit [Ping timeout: 264 seconds]
05:47rwhitbyNext interesting thing: internal is fresh DFU restore, not gone through initial setup, so has no admin user. external has gone through initial setup, has a known admin username and password (verified by logging into external drive using that). back into 1TR and bputil does not accept the external drive's username and password as valid.
05:49marcanyeah I saw that coming
05:49marcanpretty sure that's a bug
05:50rwhitby"Failed to create ACM context with provided username and password"
05:50marcanbooting "foreign" OSes like that is kind of broken
05:50marcan(and by DFU restoring you made it foreign)
05:50marcanthere should be other problems with that external OS
05:51rwhitbySo the next test is to see what happens if I go through initial setup on the internal OS, does that repair things for the external drive?
05:51marcanunlikely
05:51rwhitbySo that would mean the external drive is not useable on another machine?
05:52rwhitbyAn installation of macOS on an external drive is tied to the host on which it was created, and becomes invalid if that host is restored?
05:53marcanright now, yeah
05:53marcanI assume they intend for this to work at some point
05:53marcanbut right now it's kinda broken
05:53marcanif they fix it though, we can take advantage of that support in principle for our install flow
05:54rwhitbyyeah, that's why I was testing it
05:58mrksz has quit [Ping timeout: 240 seconds]
05:58rwhitbyLogged into internal disk and did initial setup, so it now has an admin user. Back to 1TR. bputil -d can now display internal disk, but can no longer display external disk (where as this was reversed previously before the internal drive went through initial setup).
05:59amw1 has joined #asahi
05:59rwhitbybputil can change internal drive but still does not accept valid password for external drive.
05:59mrksz has joined #asahi
06:00rwhitbyAnd now booting the external drive asks for an admin password, whereas it did not previously.
06:01rwhitbywhich indicates that it wants to write something to the internal disk
06:03amw1 has quit [Ping timeout: 260 seconds]
06:05rwhitbybputil mounts disk3s3 when changing security, so it's likely writing there?
06:07rwhitbydisk3s3 is the Recovery volume
06:10rwhitbyis there a way to identify which volume is having files modified in it selecting the external disk for boot (and needing to enter admin password to do so) ?
06:14rwhitbyBTW, "df" also shows the volumes hidden in 1TR by diskutil
06:17rwhitbyHere's the test I did: run "df" before selecting another boot disk. scp that file to safety. select another boot disk. hold power in during the restart to get back to 1TR. run "df" again, and compare with before
06:19rwhitbyI see an extra inode in iSCPreboot. xarts, Hardware, Preboot all have the same number of inodes as before.
06:22rwhitbySo, another DFU restore and this time I'll capture the full contents of iSCPreboot before and after.
06:26amw1 has joined #asahi
06:30amw1 has quit [Ping timeout: 240 seconds]
06:33marcaniSCPreboot should have one file per boot policy (you can see the files, the paths are really obvious)
06:34marcanbut other than that there should be some kind of blatant copying of stuff (iBoot etc) into *somewhere* on SSD when you boot from an external disk
06:36addcninblue has joined #asahi
06:40ransom has joined #asahi
06:41justMaku has quit [Remote host closed the connection]
06:41q3k|m has quit [Remote host closed the connection]
06:43amw1 has joined #asahi
06:46Empus has joined #asahi
06:48amw1 has quit [Ping timeout: 264 seconds]
06:57ransom has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:59amw1 has joined #asahi
07:04amw1 has quit [Ping timeout: 256 seconds]
07:05rwhitbyLooks like iSCPreboot is the place. New UUID directory inside there for the external disk
07:06rwhitbyanother DFU restore and this time I'll tarball before and after (should have done that from the start)
07:08Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:08rwhitbyand I'll use dummy username and password so I can share the tarballs with those who can make use of them
07:16amw1 has joined #asahi
07:24amw1 has quit [Ping timeout: 260 seconds]
07:40klaus_ has joined #asahi
07:44addcninblue has quit [Ping timeout: 240 seconds]
07:46addcninblue has joined #asahi
07:50amw1 has joined #asahi
07:58amw1 has quit [Ping timeout: 246 seconds]
08:07aratuk has joined #asahi
08:12aratuk has quit [Ping timeout: 264 seconds]
08:18rwhitbyYep, looks like enough stuff to boot the external drive is cached in iSCPreboot/<UUID>/boot ...
08:20jaXvi has joined #asahi
08:20addcninblue has quit [Ping timeout: 260 seconds]
09:07raster has joined #asahi
09:33marcanso this actually tells us something more: if we wanted a linux-only machine with the minimum garbage, we could probably just copy our boot files to iSCPreboot and ditch the entire second APFS container
09:33marcanit also tells us exactly what files are needed by iBoot - just the boot subdirectory
09:33marcaneverything else is needed only by the graphical boot picker in 1TR and other tooling
09:35marcanso now there's one more thing to investigate that I'm curious about: where is the currently selected boot volume stored?
09:35marcanis it flags in the localpolicy files, or something higher level?
09:35rwhitbythere was an "active" flag file in there
09:35marcanyes, but that's within that volume
09:36marcanI'm asking about what picks the volume
09:36marcani.e. outside the (uuid) level
09:39rwhitbyok, I'm going to install on a flash stick, and then I can investigate how the current boot target is chosen by comparing iscPreboot with different targets selected
09:40rwhitby(and test this USBA not working rumour at the same time)
09:40rwhitbyit's interesting that a complete macOS restore via DFU is much much faster than the "reinstall macOS" option in the recovery chooser
09:42* rwhitbybbl ~2h
10:00amw1 has joined #asahi
10:03lewurm has joined #asahi
10:09Shizmarcan: as per SW:Boot, localpolicy is selected *after* the boot volume is chosen
10:09Shizbecause the boot volume vgid is part of the localpolicy path
10:09Shizmy guess is 'nvram, somehow'
10:10Shizoh right, by flags you mean it'd iterate over every file?
10:10ShizI don't think so, it does get the current local policy hash from the SEP without vgid input
10:11Shizit might just iterate all directories looking for the local policy file with that hash
10:14Shizthere was some opaque iboot-related blob in nvram that i wonder is related
10:14marcanbtw, has anyone noticed stuff connected to their USB A ports dying?
10:15marcanI've had my keyboard stop working on macos until a reboot several times now
10:15marcan(on the mini)
10:15marcanno log entries on connect/disconnect
10:18robinpI had issues with my Apple A1243 keyboard - I now have it connected via a USB3 dock and its been fine
10:20robinpit wouldn't get power (i.e. caps lock wouldn't turn on and off)
10:23Shizno issues here yet
10:26marcanrobinp: that's not no power, keyboard do not toggle LEDs autonomously
10:26marcanmy ThinkPad keyboard doesn't even turn on its power LED until it enumerates
10:26marcanso probably the same issue I have
10:28marcanPSA: we have added some sections to the copyright/re policy at: https://alx.sh/re
10:28marcan1) we are banning GPU userspace stack binary reverse engineering, because it doesn't seem like that will be necessary, and therefore the risks are not worth it
10:30marcan2) we're treating possibly-RE'd code (i.e. anything that deals with undocumented apple hardware/formats) as if it were license-incompatible, because effectively we cannot trust that it is *policy*-compatible
10:30marcanyou can use it, you can look at it, but you can't combine it with our own repos/merge the code
10:30marcanI do no expect this to be a significant limitation, exceptions will be asessed on a case by case basis
10:32marcan(not stated, but obviously if you come across that looks like it is *obvious* decompilation/disassembly output, that is as good as looking at the binaries and that part of the policy applies, i.e. stop looking at it; this deals with code that isn't *obviously* decompiled but could plausibly be the product of such due to circumstances)
10:37CDFHThanks for that, especially the paragraph labelled important in the second to last section
10:38marcanwe've had that since the beginning (though we just removed #asahi-gpu from that list given 1) above)
10:41CDFHMakes sense :) just want to be sure I'm in the clear and that clears it up I think
10:59amw1 has quit [Ping timeout: 256 seconds]
11:03DarthCloud has quit [Ping timeout: 240 seconds]
11:05DarthCloud has joined #asahi
11:30rwhitbyLooks like there is indeed an issue installing to a flash stick. It seems to complete (the last 1% takes forever), but when it restarts to boot the flash stick it says "The versin of macOS on the selected disk needs to be reinstalled."
11:31rwhitbyAnd trying to select the flash stick as the startup disk results in "Unable to set startup disk" (SDErrorDomain error 104)
11:53burra has joined #asahi
11:54burra has quit [Client Quit]
12:09aratuk has joined #asahi
12:13aratuk has quit [Ping timeout: 265 seconds]
12:33amw1 has joined #asahi
12:35jamadazi has joined #asahi
12:55amw1 has quit [Ping timeout: 246 seconds]
13:15ephe_meral has joined #asahi
13:34dstzd has quit [Quit: ZNC - https://znc.in]
13:35dstzd has joined #asahi
13:40mogery has joined #asahi
14:00aratuk has joined #asahi
14:05aratuk has quit [Ping timeout: 272 seconds]
14:07justMaku has joined #asahi
14:13robher has joined #asahi
14:17HoneyTubes has joined #asahi
14:22justMaku has quit [Quit: Client limit exceeded: 150]
14:24dstzd has quit [Quit: ZNC - https://znc.in]
14:24dstzd has joined #asahi
14:32q3k|m has joined #asahi
14:32raster has quit [Quit: Gettin' stinky!]
14:34raster has joined #asahi
15:06sumoon[m] has joined #asahi
15:08Shizdo we know where nvram comes from/is stored in the m1?
15:08Shizfor iphones it's in the NOR apparently
15:11davidrysk[m]we don't... we can use the nvram command to read/write it
15:11davidrysk[m]on Intel Macs it's in the same chip as the EFI (which is a serial EEPROM/flash)
15:12davidrysk[m]there is a `boot-info-payload` key in the nvram
15:12davidrysk[m]before posting nvram dumps — note that they contain wifi network data
15:12davidrysk[m]so you may want to redact that for your privacy
15:13Shizyah, I alluded to that key above :p
15:14Shizit seems to be high-entropy binary tho
15:16Shizthere's also a boot-volume nvram variable, but i'm not sure if that's *set* or *used* by iBoot
15:16Shizif it's only used, that might be how iBoot decides which volume to boot form
15:18Shiz --setBoot Set the system to boot off the specified partition. This is implemented in a platform-specific manner. On Open Firmware-based systems, the boot-device variable is modified. On EFI-
15:18Shiz based systems, the efi-boot-device variable is changed. This is not supported on Apple Silicon based systems.
15:19klaus_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:24Shizokay, figured out the structure
15:25Shizboot-volume is in the format <efi-partition-type-uuid>:<partition-uuid>:<volume-group-uuid>
15:27Shizecept the partition UUID is mangled and the first 3 components are byteswapped?
15:30HeN has quit [Quit: Connection closed for inactivity]
15:34Tokamak has joined #asahi
15:37Shizokay, setting nvram auto-boot to false gives you a nice "cant boot, visit apple.com/restore" prompt on boot :)
15:37Shizcan still boot into 1TR
15:43davidrysk[m]there has to be some way they set it for repairs
15:43lothwen has joined #asahi
15:44Shizalso, fun fact, you can't write to boot-volume, even from 1TR
15:44Shizmaybe something special needs to be done?
15:52jamadazi has quit [Quit: WeeChat 3.0]
15:58klaus_ has joined #asahi
16:01aratuk has joined #asahi
16:04Shizah, the nvram is inside the NOR according ot the device tree
16:04Shizthat, firmware and syscfg
16:05Shizso right now my guess is stage1 iboot reads boot-volume from nvram and goes from there
16:06aratuk has quit [Ping timeout: 264 seconds]
16:11ransom has joined #asahi
16:16frode_0xa has joined #asahi
16:26ransom_ has joined #asahi
16:29ransom has quit [Ping timeout: 272 seconds]
16:34marcanyeah, that would make sense
16:56ransom has joined #asahi
16:57modwizcode has joined #asahi
16:57ransom_ has quit [Ping timeout: 256 seconds]
17:03mogeryy has joined #asahi
17:04mogery has quit [Ping timeout: 260 seconds]
17:08plainbits has joined #asahi
17:19addcninblue has joined #asahi
17:20lothwen has quit [Quit: Leaving]
17:21frode_0xa has quit [Quit: leaving]
17:30plainbits has quit [Quit: Bye!]
17:50HeN has joined #asahi
18:02aratuk has joined #asahi
18:06aratuk has quit [Ping timeout: 256 seconds]
18:14ephe_meral has quit [Ping timeout: 240 seconds]
18:15tiagom has joined #asahi
18:23djb has joined #asahi
18:25ky0ko has joined #asahi
18:32saaam has quit [Remote host closed the connection]
18:39tiagom has quit [Quit: tiagom]
18:41tiagom has joined #asahi
19:02HoneyTubes has quit [Read error: Connection reset by peer]
19:02HoneyTubes has joined #asahi
19:18AgentPurple[m] has joined #asahi
19:56ephe_meral has joined #asahi
20:13ephe_meral has quit [Ping timeout: 272 seconds]
20:59HoneyTubes has quit [Quit: Quit]
21:04nyx_o has joined #asahi
21:12mogeryy has quit [Quit: Leaving]
21:20wolf511[m] has joined #asahi
21:20ransom has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:22DarthCloud has quit [Ping timeout: 240 seconds]
21:28DarthCloud has joined #asahi
21:33etaShiz: apple.com/restore doesn't go anywhere
21:34Shizi typed the url from the top of my head, it was possibly not exactly that
21:45Shizi wonder what's up with xnu's latest version number
21:45Shizxnu-7195.50.7.100.1
21:45Shiz5 components?
21:45j`eyi assume it;s just random
21:45j`eyto annoy us :P
21:53djb has quit [Ping timeout: 256 seconds]
21:57marcanrwhitby: so I just realized I'm an idiot
21:57marcanof course the PD link / serial stuff goes down on reboot
21:58marcanI've been playing UFP all along
21:58marcanI should've been playing DFP
21:58marcanthis thing's a *device* until the OS decides it's time to turn on all the dual role negotiation machinery
21:58marcan(e.g. DFU mode needs to work, so the Mac needs to default to UFP when the main CPU is not up yet)
21:59marcanI can confirm there's something alive when I switch to DFP role, though right now all I'm seeing is HARDRESETs
22:00marcanrwhitby: I need to get some sleep, but if you have some time, can you try putting it into DFU mode (power it down, unplug it, hold down the power button and plug it in; LED should be orange) and seeing if it'll negotiate a PD contract with another Mac / a source / something, and get me a trace?
22:03aratuk has joined #asahi
22:04djb has joined #asahi
22:07aratuk has quit [Ping timeout: 240 seconds]
22:28guillaume_ has joined #asahi
22:28guillaume_ has quit [Client Quit]
22:41tiagom has quit [Quit: tiagom]
22:44rwhitbymarcan: yes, for dead battery support reasons a macbook will always be a sink/UFP in this type of situation.
22:53rwhitbymarcan: I assume you just want a simple PD contract trace so you can fake being a DFP/source with vdmtool?
22:55rwhitbyNote that there are timing constraints that need to be met, otherwise you'll end up with hard reset loops. A source needs to send source caps within a certain time or else the sink will hard reset it. If a sink responds with GoodCRC to a source caps, then it needs to send a request within a certain time or else the source will hard reset it. Getting to a stable contract requires both these conditions being met or else you'll end up in a hard
22:55rwhitby reset loop.
22:56rwhitbyThis is never an issue when you have a PD controller at each end. But if you're doing this with a bare PHY and vdmtool driving it, then vdmtool will need to do this stuff.
23:00rwhitbymarcan: see PM for trace upload
23:04rwhitbyA M1 Mini in DFU mode will negotiate a full PD contract on both ports. On the DFU port it will stop before entering an alternate mode, and does not advertise TBT3 support. On the other port, it will enter Thunderbolt mode but not engage in LSTX/RX side band data path negotiation.
23:05czero64 has joined #asahi
23:05AnCaRioN has joined #asahi
23:05j`eyyou can only DFU from a specific port?
23:06ephe_meral has joined #asahi
23:07j`eyinteresting
23:07rwhitbywell, only one of the USB-C mux chips connected to each port is going to be connected to the NOR flash
23:12raster- has joined #asahi
23:18raster- has quit [Quit: Gettin' stinky!]
23:18raster has quit [Remote host closed the connection]
23:18raster has joined #asahi
23:19ephe_meral has quit [Ping timeout: 256 seconds]
23:27ransom has joined #asahi
23:39ransom has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:49Calchan has joined #asahi
23:49Calchan has quit [Changing host]
23:50raster has quit [Quit: Gettin' stinky!]
…