#
✕ nick:arnd
#asahi · 2021-05-10 09:14
arndhttps://www.irccloud.com/pastebin/2iDeDXg5/
#asahi · 2021-05-10 09:13
arndI have only one partition on the external drive now, installed it from a 11.3.1 USB installation medium, everything works after initial setup, but then the 'kmutil' command fails with the credentials of the user account I created:
#asahi · 2021-05-09 23:19
arndAnyway, I should go sleep now, will try more tomorrow
#asahi · 2021-05-09 23:15
arndIt shows a picture of an external drive, but a different color compared to the USB one
#asahi · 2021-05-09 23:13
arndThere was clearly a difference between the long-press and the 1TR menu, in that the latter does not show USB drives, only TB3/nvme
#asahi · 2021-05-09 23:11
arndI think I got into different scenarios there, but could never boot more than one of the external partitions
#asahi · 2021-05-09 23:10
arndI did try various boot pickers (from running OS, from 1tr, from long pressing power button without 1TR and from the failed-boot screen)
#asahi · 2021-05-09 23:08
arndI suspect they wouldn't really provide support for users on external drives, afaik it only works by accident on TB3 disks but should be disabled on removable drives otherwise
#asahi · 2021-05-09 23:06
arndI always did the First-Boot setup, and that worked, but just couldn't get back to the other partition after that
#asahi · 2021-05-09 23:06
arnd1TR says something like "this partition has no privileged user, pick one now" when trying to boot back into a partition that stopped working
#asahi · 2021-05-09 23:04
arndAfter a partition gets messed up, 1TR also complains about missing permissions, in various ways
#asahi · 2021-05-09 23:03
arndYes
#asahi · 2021-05-09 23:02
arndMy current theory of what went wrong with my external drive is that this all broke down because of nonmatching credentials: I had to provide an Admin password for the internal drive when installing to the external drive, but then after booting into that, the new Admin account lacked permissions to change the boot setup back to another external partition
#asahi · 2021-05-09 22:57
arndFor some reason I assumed I had to build m1n1 under MacOS, but that is clearly not the case
#asahi · 2021-05-09 22:56
arndmarcan: the MacOS on the internal disk isn't mine, it has to stay functional and I don't have root access on it. I have no need for MacOS on the external drive other than to try to follow your how-to document.
#asahi · 2021-05-09 15:29
arndCould be. I'm trying a third macos partition now to see which ones and how many I can boot after that
#asahi · 2021-05-09 15:22
arndThe internal drive still boots, and the "Linux" partition on the external drive (which contains the unmodified MacOS 11.3.1) also boots, but the "Macintosh HD" on the external drive does not
#asahi · 2021-05-09 15:20
arndI tried erasing the first install on the external drive and reinstalling to it. The reinstall also worked, but after rebooting, it still fails with "The version of macOS on the selected disk needs to be reinstalled. Use Recovery to ereinstall macOS or select another startup disk."
#asahi · 2021-05-09 15:17
arndPartitioning and installing macos once works great, but after I install macos a second time, the first installation on the same drive fails
#asahi · 2021-05-09 15:16
arndI've finally gotten to the point of trying install the Mac mini, going through the newbie setup at https://github.com/AsahiLinux/docs/wiki/Developer-Quickstart, but I'm failing at the basic MacoOS install. I got an external TB3 drive so I can leave the working installation on the internal drive alone
#asahi · 2021-05-05 07:10
arndkrbtgt: the Sony PS3 was the original target for petitboot, and it could already boot a linux kernel that would only run on the ps3, so kexec was the easiest way to load a distro kernel
#asahi · 2021-04-21 12:09
arndthe patch does a bunch of things, it also adds the PCI device ID (that part is probably fine), and some bits for interrupt handling that I didn't understand but that are probably needed in some form
#asahi · 2021-04-21 12:04
arndcorellium have a fairly small patch for drivers/net/wireless/broadcom/brcm80211/brcmfmac/ to add support
#asahi · 2021-04-21 12:03
arndnimroot[m]: bcm4378
#asahi · 2021-04-19 12:49
arndpipcet[m]: I'm fairly sure the Unix-like parts of MacOS use the normal 1970-based epoch, though there are still some traditional MacOS parts like HFS+ that use an epoch using unsigned integers starting in 1904, which means 32-bit time values are a little over 2 years off -- 1904 to 2040 instead of 1902 to 2038
#asahi · 2021-04-17 17:16
arndIn that case, I suspect it could be modeled as a platform specific rfkill device, as long as pcie hotplug works correctly to bring it back up
#asahi · 2021-04-17 17:14
arnd(i.e. airplane mode)
#asahi · 2021-04-17 17:14
arndor is this possibly needed for RFKILL functionality?
#asahi · 2021-04-17 17:13
arndif the power savings are not substantial, I'd just turn it on during boot
#asahi · 2021-04-17 17:13
arndit probably comes down to how much power we can save by turning it off then, compared to just doing the regular PCIe ASPM
#asahi · 2021-04-17 17:11
arndIn theory, SDIO is not different from USB or PCI here, but I don't recall it being needed on these so far
#asahi · 2021-04-17 17:10
arndcompliant MMC/SDIO devices shouldn't need any of those, but it's fairly common to have to kick an SDIO device in some for (clock-enable, reset, regulator, ...) before it can be probed
#asahi · 2021-04-17 17:09
arndMMC currently has a generic "simple" power sequencing driver that handle almost all devices, plus two device specific ones for those that are not as easily abstracted
#asahi · 2021-04-17 17:07
arndif we decide that it is needed, then a copy of Documentation/devicetree/bindings/mmc/mmc-pwrseq-simple.yaml for PCI should work
#asahi · 2021-04-17 17:06
arndany idea if macos toggles it at runtime? if not, it's probably enough again to have u-boot turn it on before starting Linux
#asahi · 2021-04-17 17:02
arndok, I see
#asahi · 2021-04-17 15:45
arndkettenis: regarding the MSI mapping, I'm aware that this needs to be done somewhere, but as I said that does not involve registers, so it could be outside of the PCI host bridge driver if that ends up being easier
#asahi · 2021-04-17 15:44
arndif the power needs to be enabled first, we may have to add the equivalent of drivers/mmc/core/pwrseq.c for pci
#asahi · 2021-04-17 15:43
arndkettenis: does the wifi device show up at all if you don't enable the power? As long as the driver can bind to the device, it can read a custom property to do whatever is necessary
#asahi · 2021-04-17 15:10
arndbut isn't that someting that could be done in m1n1 or u-boot rather than having the OS know about it?
#asahi · 2021-04-17 15:07
arndwhat do the registers do? I think when I read the corellium driver a while back, it didn't touch any registers for MSI, just passed everything down to the AIC
#asahi · 2021-04-17 15:05
arndMSI doesn't have to be done in the pci host bridge driver, I think it's usually done in there because it shares the register space, but in this case there are no registers for MSI
#asahi · 2021-04-17 15:03
arndkettenis: so what is left beyond what the generic pcie host support gives us? only suspend mode, or something beyond that?
#asahi · 2021-04-17 14:50
arnd'dw_pcie' contains the information for both modes, while 'pcie_port' only contains the bits that are specific to host mode
#asahi · 2021-04-17 14:49
arndI suppose the current split exists in order to separate endpoint from host most
#asahi · 2021-04-17 14:48
arndThere is already a 'struct dw_pcie' that is looks like it should represent the root complex, but it contains a single 'struct pcie_port', along with members that should be port specific (num_lanes, link_gen, ...), while the 'struct pcie_port' seems to only have members that should be part of the root complex
#asahi · 2021-04-17 14:45
arndor possibly just renamed if it turns out that everything in there is common to all ports
#asahi · 2021-04-17 14:44
arndNot sure how much this needs to be reworked, but if we need to introduce the concept of actual ports, the dw_pcie 'struct pcie_port' probably needs to be split into the port specific bits and those that are shared for the root complex
#asahi · 2021-04-17 14:42
arndthat might actually help here. In the Linux driver, the common code for dw-pcie makes the assumption that port==root_complex==host_bridge, unlike the tegra driver you found and the mvebu driver that fakes a root complex
#asahi · 2021-04-17 14:38
arndkettenis: is the u-boot driver for dw-pcie derived from the Linux driver?

plus ›