#
…

2024-02-25

00:00hdbngr has quit [Ping timeout: 480 seconds]
00:07hdbngr has joined #asahi
00:12chadmed has quit [Ping timeout: 480 seconds]
00:23hdbngr has quit [Ping timeout: 480 seconds]
00:29Charlie has joined #asahi
00:29Charlie has left #asahi [#asahi]
00:30Charlie has joined #asahi
00:31hdbngr has joined #asahi
00:37CharlieHey all! I'm a data engineer/software dev with tons of experience with both linux and MacOS, kubernetes/cluster development/managed/debgging, python/pyspark, bash/zsh, the list goes on. As a new M3 Pro owner what's the best way I can start making contributions to this project? Mainly thinking having an M3 will be beneficial but happy to do non-m3 related dev work as well.
00:41hdbngr has quit [Ping timeout: 480 seconds]
00:50hdbngr has joined #asahi
00:53kidplayer666 has quit [Quit: Connection closed for inactivity]
01:04hdbngr has quit [Ping timeout: 480 seconds]
01:06julio7359 has joined #asahi
01:08Bertrand___ has quit [Ping timeout: 480 seconds]
01:11hdbngr has joined #asahi
01:13Bertrand___ has joined #asahi
01:21hdbngr has quit [Ping timeout: 480 seconds]
01:28Charlie has quit [Quit: Textual IRC Client: www.textualapp.com]
01:30hdbngr has joined #asahi
01:31Bertrand___ has quit [Remote host closed the connection]
01:34linuxgemini has joined #asahi
01:35Bertrand___ has joined #asahi
01:39hdbngr has quit [Ping timeout: 480 seconds]
01:47julio7359 has quit [Ping timeout: 480 seconds]
01:50hdbngr has joined #asahi
01:56julio7359 has joined #asahi
01:58hdbngr has quit [Ping timeout: 480 seconds]
02:00KxCORP has quit [Quit: Bye!]
02:01overholts has quit [Quit: overholts]
02:01KxCORP has joined #asahi
02:02overholts has joined #asahi
02:04jeisom has quit [Ping timeout: 480 seconds]
02:06hdbngr has joined #asahi
02:07Bertrand___ has quit [Ping timeout: 480 seconds]
02:14skipwich has quit [Ping timeout: 480 seconds]
02:15hdbngr has quit [Ping timeout: 480 seconds]
02:20possiblemeatball has quit [Quit: Quit]
02:21possiblemeatball has joined #asahi
02:21dylanchapell has quit [Read error: Connection reset by peer]
02:23Bertrand___ has joined #asahi
02:23hdbngr has joined #asahi
02:26possiblemeatball has quit [Quit: Quit]
02:42hdbngr has quit [Ping timeout: 480 seconds]
02:52hdbngr has joined #asahi
02:56dylanchapell has joined #asahi
03:00hdbngr has quit [Ping timeout: 480 seconds]
03:10hdbngr has joined #asahi
03:17Szadek6367007078972554 has quit []
03:20hdbngr has quit [Ping timeout: 480 seconds]
03:21hdbngr has joined #asahi
03:21Szadek6367007078972554 has joined #asahi
03:27julio7359 has quit [Ping timeout: 480 seconds]
03:30hdbngr has quit [Ping timeout: 480 seconds]
03:33hdbngr has joined #asahi
03:43hdbngr has quit [Ping timeout: 480 seconds]
03:43julio7359 has joined #asahi
03:53hdbngr has joined #asahi
04:00kdb4244 has joined #asahi
04:02Bertrand___ has quit [Read error: Connection reset by peer]
04:02Bertrand___ has joined #asahi
04:04kdb424 has quit [Ping timeout: 480 seconds]
04:04kdb4244 is now known as kdb424
04:06hdbngr has quit [Ping timeout: 480 seconds]
04:14hdbngr has joined #asahi
04:24hdbngr has quit [Ping timeout: 480 seconds]
04:32hdbngr has joined #asahi
04:33shiggitay_ has joined #asahi
04:43hdbngr has quit [Ping timeout: 480 seconds]
04:45rvalue has joined #asahi
04:46rvalue has quit [Read error: Connection reset by peer]
04:47rvalue has joined #asahi
04:51hdbngr has joined #asahi
05:00hdbngr has quit [Ping timeout: 480 seconds]
05:01marvin24 has joined #asahi
05:04marvin24_ has quit [Ping timeout: 480 seconds]
05:07hdbngr has joined #asahi
05:17hdbngr has quit [Ping timeout: 480 seconds]
05:26hdbngr has joined #asahi
05:59eiln has quit [Ping timeout: 480 seconds]
06:01nela has quit [Ping timeout: 480 seconds]
06:06chadmed has joined #asahi
06:19hdbngr has quit [Ping timeout: 480 seconds]
06:28hdbngr has joined #asahi
06:45hdbngr has quit [Ping timeout: 480 seconds]
06:51nela has joined #asahi
06:54hdbngr has joined #asahi
06:58rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
06:58Guest455 has quit [Quit: Bridge terminating on SIGTERM]
07:00rhysmdnz has joined #asahi
07:01Guest932 has joined #asahi
07:03hdbngr has quit [Ping timeout: 480 seconds]
07:04hdbngr has joined #asahi
07:10shiggitay_ has quit [Ping timeout: 480 seconds]
07:13hdbngr has quit [Ping timeout: 480 seconds]
07:22hdbngr has joined #asahi
07:31hdbngr has quit [Ping timeout: 480 seconds]
07:36hdbngr has joined #asahi
07:46hdbngr has quit [Ping timeout: 480 seconds]
07:54hdbngr has joined #asahi
08:03hdbngr has quit [Ping timeout: 480 seconds]
08:08arahael has joined #asahi
08:12hdbngr has joined #asahi
08:21hdbngr has quit [Ping timeout: 480 seconds]
08:30Bertrand___ has quit [Remote host closed the connection]
08:30Bertrand___ has joined #asahi
08:30hdbngr has joined #asahi
08:38JayBeeFOSS has quit [Ping timeout: 480 seconds]
08:39JayBeeFOSS has joined #asahi
08:47hdbngr has quit [Ping timeout: 480 seconds]
08:56hdbngr has joined #asahi
09:06hdbngr has quit [Ping timeout: 480 seconds]
09:07hdbngr has joined #asahi
09:15hdbngr has quit [Ping timeout: 480 seconds]
09:20vx has quit [Quit: G-Line: User has been permanently banned from this network.]
09:20vx has joined #asahi
09:21mkurz_ has quit [Ping timeout: 480 seconds]
09:23hdbngr has joined #asahi
09:32mkurz_ has joined #asahi
09:49mkurz_ has quit [Read error: No route to host]
09:50mkurz_ has joined #asahi
10:00hdbngr has quit [Ping timeout: 480 seconds]
10:10hdbngr has joined #asahi
10:13quimah has joined #asahi
10:22hdbngr has quit [Ping timeout: 480 seconds]
10:31hdbngr has joined #asahi
10:33PaulFertser has joined #asahi
10:34Bertrand___ has quit [Ping timeout: 480 seconds]
10:34Bertrand___ has joined #asahi
10:45hdbngr has quit [Ping timeout: 480 seconds]
10:46hdbngr has joined #asahi
10:56hdbngr has quit [Ping timeout: 480 seconds]
11:04bingoChecker has joined #asahi
11:05hdbngr has joined #asahi
11:14hdbngr has quit [Ping timeout: 480 seconds]
11:15hpar has joined #asahi
11:18hpar has quit [Quit: Konversation terminated!]
11:23hdbngr has joined #asahi
11:25mort_I wonder what it would take to get proper "s3" sleep on these machines
11:29j`eybeing able to properly save/restore the state of all the coprocessors
11:30mort_sounds non-trivial
11:31Nefsen402having linux start up on bespoke aarch64 hardware sounds non-trivial
11:32mort_hmm would s4 idle possibly be easier? Since that actually properly shuts down and does a cold boot
11:32Brainium has joined #asahi
11:33hdbngr has quit [Ping timeout: 480 seconds]
11:34hdbngr has joined #asahi
11:40mort_ has quit [Ping timeout: 480 seconds]
11:43mort_ has joined #asahi
11:45chadmedits really not productive to think in terms of acpi power states
11:46chadmedthe system is not abstracted at that level and there is no system-wide "please put the machine in x state" that we can do
11:46mort_with the caveat that I may have missed some discussion because my irc client got sad and I had to hard reboot the VPS (!!):
11:46mort_I think the ACPI power states give us a language to talk about different kinds of sleep, even on systems which don't implement ACPI
11:47chadmedyeah but they are totally unrelated to how you would ever implement anything that even "looks" like those states on non-acpi hardware
11:47mort_e.g "store RAM contents to disk, power off completely, then recover RAM from disk on boot" makes sense as a concept regardless of ACPI, and we call that S4 sleep
11:49chadmedmhmm and without platform firmware implementing that interface where do you implement it
11:49chadmedit makes absolutely no sense even as a concept
11:50mort_the kernel?
11:51bingoChecker has quit [Remote host closed the connection]
11:51ketteniseven with ACPI, S4 doesn't do much more than powering off the machine
11:51kettenisthe OS does all the hard work
11:53kettenisthere used to be a separate S4BIOS state where the firmware would do the hard work, but that hasn't been implemented by any vendor in the last decade
11:55kettenisso implementing a suspend-to-disk for these machines should be entirely possible
11:55kettenisdoes Linux implement suspend-to-disk on other arm64 hardware?
11:56chadmedbah im sorry i need to sleep, s4 is hibernate of course
11:56chadmedim an idiot
11:56mort_I guess that's the downside of using the acpi state names heh
11:58hdbngr has quit [Ping timeout: 480 seconds]
11:59hdbngr has joined #asahi
11:59mort_Phoronix says suspend to disk for ARM64 was added in 4.7
12:02chadmeds2idle Shouldn't(tm) be materially worse than STR in any case. our issue is not something innate to s2idle but rather that some stuff isn't being quiesced/put into low power states
12:02j`eyand being to actually turn off CPUs would be nice
12:04kettenisthe only real difference between suspend-to-RAM and suspend-to-idle is that you hand off to some lower-power CPU to turn off the last few things
12:04mort_it's true that s2ram is in principle no better than s2idle + perfect power management in all drivers for all hardware, but there's something to be said about guarantees here
12:05ketteniswell, even ACPI S3 doesn't give you those guarantees
12:05mort_this kind of thinking is what causes even Windows laptops these days to randomly just get super hot in your backpack because some driver messed up a power management thing
12:05mort_"everything is turned off except for RAM" is a fairly decent guarantee isn't it?
12:05chadmedno, thats bugs in windows
12:05kettenisthe OS is still responsible for turning off tons of stuff first
12:05chadmedthis has been proven time and time again
12:05chadmedshitty buggy winblows code and shitty buggy ACPI BIOS code have nothing to do with us
12:05mort_chadmed: those bugs in Windows wouldn't be possible if Windows wasn't running because only the RAM was powered on
12:05kettenisand it is entirely unspecified *what* the OS is responsible for
12:06mort_regardless I trust Linux to be bug-free even less than I trust NT to be bug-free
12:07mort_I have sooooo much experience with random kernel bugs on various bits of hardware causing things like lock-ups and kernel memory leaks and whatever else
12:07chadmedand yet you trust us to emulate ACPI power states?
12:08mort_I trust a kernel that's not running more than I trust a kernel that is to some extent running
12:08hdbngr has quit [Ping timeout: 480 seconds]
12:08chadmedthe codepaths would be exactly the same for s2ram and s2idle
12:09chadmeds2ram would require even more kernel intervention on this platform because we cant simply call into firmware to do the last few bits for us in fact
12:09mort_but no, I don't trust that either, my previous laptop would sometimes randomly just get super hot when I closed the lid and then not come to life again until I held down the power button
12:10chadmedthen what exactly is the point here?
12:11j`eybetter sleep :P
12:11mort_the bug I mentioned with my previous laptop would at least happen while the kernel was suspending, and I could be relatively sure that once it was actually suspended, it would stay that way
12:13chadmedj`ey: of course but at the point where we're splitting hairs over what exactly is slept and how is totally irrelevant so long as the end result is good sleep
12:13chadmedwhich is what i was getting at when saying that acpi power states as a frame of reference are unhelpful and a bad idea
12:13chadmedthey just lead to arguments like this
12:14chadmedit literally does not matter in the slightest how the platform is suspended when all the drivers are just gated behind PM_SLEEP and not any particular implementation of "sleep"
12:14mort_to be clear, I am not saying "the Asahi Linux project should implement s2ram"
12:15mort_just that, I believe that this idea of "we can just make sure every driver perfectly implements power management and do s2idle" is a common trend in the industry and is responsible for quite a lot of grief
12:15chadmedi mean, the hardware we're working with is clearly capable of doing it. it's not like we're trying to work with fundamentally broken hardware or firmware implementations that cant handle perfect s2idle
12:16chadmedif we were trying to support some bumass thinkpad or asus motherboard youd have a point though
12:16mort_and perfect s2idle might very well be the right approach for Asahi, especially given that the set of hardware is so limited
12:17hdbngr has joined #asahi
12:17chadmedthe main power hogs during s2idle right now are the pcore clusters anyway
12:17mort_and I'm not blind to the fact that work on general PM means better battery performance in both s2idle *and* in normal tasks, while work on s3 sleep would benefit only sleep
12:18chadmediirc we need psci to turn the clusters off and restore them or something like that
12:18chadmedso its not a problem we dont know how to fix, we just need to actually do it
12:18j`eywell the problem there is how to hanlde PSCI in the same EL
12:18j`eyI prototyped this, with efi and keeping m1n1 in memory and stuff, was fun, but very hacky
12:19kettenischadmed: technically there is no problem for just adding code in Linux to turn off the P-clusters
12:19j`eywell upstream is the problem :P
12:19chadmedkettenis: yeah well thats what we did in our idle driver but thats never ever getting upstreamed :p
12:20mort_*if* my understanding is correct that suspend-to-disk is more or less handled generically by the kernel, it could be an interesting stop-gap for those of us who want to be able to not wake up to a dead laptop in the morning even as perfect s2idle is a work in progress
12:23mort_meh it seems like hector martin has already commented on hibernate a few times and there are challenges there too
12:25svenif it was very easy it would already be supported
12:26mort_I guess I could work around this in userspace instead, make firefox save its session, then power off in a way which tells the system to auto power on and open firefox on the next boot
12:26hdbngr has quit [Ping timeout: 480 seconds]
12:27j`eyIs that much different than just having the WM/DE always open ff?
12:27mort_maybe not
12:30ketteniseven if driver code to turn off the P-clusters would never be upstreamable it would be useful to have
12:30mort_alright with auto login + auto launch firefox + firefox session restore I successfully have "hibernate" 😅
12:31j`eymort_: just do that overnight, and during the day normal s2idle hopefully doesnt draw enough
12:31kettenisit could be used as example code for PSCI emulation
12:32mort_I wonder if I could automatically shut down after some period of time in s2idle
12:35hdbngr has joined #asahi
12:44paps__ has quit [Quit: Connection closed for inactivity]
12:47f_ is now known as funderscore
12:47funderscore is now known as f_
12:48hdbngr has quit [Ping timeout: 480 seconds]
12:49hdbngr has joined #asahi
12:51Fischmiep has quit [Read error: Connection reset by peer]
12:59hdbngr has quit [Ping timeout: 480 seconds]
13:01jeisom has joined #asahi
13:03possiblemeatball has joined #asahi
13:05mort_is speakersafetyd used for both the voice coil temperature model safety stuff and the eq stuff? Or is it only responsible for safety and some other system is used for eq
13:07leiosome stuff using lsp-plugins, bankstown and co do eq via automatic pipewire setup
13:09hdbngr has joined #asahi
13:10mort_so pipewire (with plugins) ends up doing the actual DSP stuff?
13:12j`eywireplumber too whatever that thing is responsible for. I think that's the pipewire related thing that I see using the most cpu
13:15mort_the description "session and policy manager" doesn't immediately scream "responsible for the heavy lifting for DSP" but htop output doesn't lie, it's there, behind only firefox in cpu utilization while playing videos in firefox
13:25hdbngr has quit [Ping timeout: 480 seconds]
13:33hdbngr has joined #asahi
13:42hdbngr has quit [Ping timeout: 480 seconds]
13:43quimah has quit [Quit: Konversation terminated!]
13:47hdbngr has joined #asahi
13:56hdbngr has quit [Ping timeout: 480 seconds]
14:00jeisom has quit [Ping timeout: 480 seconds]
14:05hdbngr has joined #asahi
14:16tobhe_ has joined #asahi
14:17hdbngr has quit [Ping timeout: 480 seconds]
14:20tobhe has quit [Ping timeout: 480 seconds]
14:27hdbngr has joined #asahi
14:40hdbngr has quit [Ping timeout: 480 seconds]
14:43hdbngr has joined #asahi
14:57axt has joined #asahi
14:58hdbngr has quit [Ping timeout: 480 seconds]
15:00yuyichao has joined #asahi
15:01yuyichao_ has quit [Read error: Connection reset by peer]
15:07hdbngr has joined #asahi
15:12fossdd has quit [Ping timeout: 480 seconds]
15:13fossdd has joined #asahi
15:15cisco87 has quit [Remote host closed the connection]
15:26delsol has joined #asahi
15:28delsol has quit [Remote host closed the connection]
15:28delsol has joined #asahi
15:32wintp has joined #asahi
15:32eiln has joined #asahi
15:33fossdd has quit [Ping timeout: 480 seconds]
15:39fossdd has joined #asahi
15:57fossdd has quit [Ping timeout: 480 seconds]
16:01fossdd has joined #asahi
16:19fossdd has quit [Ping timeout: 480 seconds]
16:26fossdd has joined #asahi
16:27eiln has quit [Quit: WeeChat 4.2.1]
16:37Szadek6367007078972554 has quit []
16:37Szadek6367007078972554 has joined #asahi
16:48tobhe_ has quit [Remote host closed the connection]
16:51leif has joined #asahi
16:56leif has quit []
16:57ydalton has joined #asahi
16:57ydalton has left #asahi [#asahi]
16:58tobhe has joined #asahi
17:08fossdd has quit [Ping timeout: 480 seconds]
17:09nicolas17 has quit [Read error: Connection reset by peer]
17:15fossdd has joined #asahi
17:32wintp has quit [Ping timeout: 480 seconds]
17:35fossdd has quit [Ping timeout: 480 seconds]
17:37fossdd has joined #asahi
17:41wintp has joined #asahi
17:44rvalue has quit [Ping timeout: 480 seconds]
17:47rvalue has joined #asahi
17:49wintp has quit [Ping timeout: 480 seconds]
17:53eldondevHi all, sorry if this has already been asked or if it's newbie stuff. I was hoping to get out of tethered-to-apple MacOS world with Asahi and I feel a little stuck.
17:54fossdd has quit [Ping timeout: 480 seconds]
17:54eldondevI have an older install of asahi with an earlier MacOS Ventura install.
17:56eldondevMy understanding is that the newer installer requires newer boot files, so I am trying to upgrade to Sonoma 14.1 on my 2020 Mac Mini m1 8GB via a usb disk create via the createinstallmedia command from another macbook (air, M1)
17:56fossdd has joined #asahi
17:57eldondevUnfortunately, the install begins, then I get a modal that tells me that installing macOS requires an internet connection, and the installer was unable to personalize my macos experience or something along those lines.
17:57PaulFertsereldondev: why are you not upgrading directly via the Internet?
17:57wintp has joined #asahi
17:58eldondevPaulFertser: Because it's not locally reproducible.
17:59eldondevFor the same reason I do things like compile firefox from source locally.
17:59eldondevI like to be able to understand what my computers are doing, reproduce it, and change it if I want.
17:59PaulFertsereldondev: in general the idea is that mac hardware has plenty of additional CPUs each running their own firmware and Asahi needs binaries for those additional CPUs, and the regular way to to get those binaries is copying from existing macOS system to the EFI partition that's accessible later to Linux.
18:00eldondevPaulFertser: Is there a plan on packaging those binaries some other way?
18:00j`ey'A bootable installer doesn't download macOS from the internet, but it does require an internet connection to get firmware and other information specific to the Mac model.'
18:01j`eyeldondev: we can't package those, theyre not redistributable
18:01eldondevOk, is there an alternative source for that firmware?
18:01j`eyhttps://support.apple.com/en-us/101578 seems to suggest you can't install without internet?
18:02PaulFertsereldondev: you can use a "test" device and then package everything needed yourself for your own use. That's how Apple wants it I'm afraid.
18:03eldondevDoes asahi enumerate the blobs that it requires from macos in a specific way?
18:03j`eyeldondev: theyre in a tarball
18:03j`eyon the ESP
18:03j`eyat least the ones that asahi has to load, macOS loads some for us
18:04eldondev> macOS loads some for us
18:04eldondevYou mean, in a nonvolatile way?
18:04j`eythey get loaded on each boot I think? not 100% sure tbh
18:04svennot sure what you meant by that. the firmware for most coprocessors is already loaded and running before we get control
18:04svenyeah, on every boot
18:05j`eyI was trying to think of firmware we load.. USB, wifi, bt? (or is that just part of wifi)
18:05mkurz_ has quit [Ping timeout: 480 seconds]
18:05j`eytouch/keyboard, ISP
18:05svenwifi and bt is separate and those have to be loaded by us
18:06j`eythis is how the installer extracts the fw
18:07eldondevMy concern is that, rather than getting out of the business of maintaining macOS, and using normal linux maintenance strategies,
18:07j`eymost of that applies, apart from firmware
18:07eldondevSo, is this just kindof a one time thing, you think?
18:07j`eyit's kinda like how the other x86 etc have firmware for some parts that are done by the BIOS I guess
18:07wintp has quit [Ping timeout: 480 seconds]
18:08PaulFertsereldondev: normal Linux strategies assume firmware is redistributable and can be added to linux-firmware at git.kernel.org ...
18:08eldondevRight, I guess my question is,
18:08eldondevdo we expect Linux going forward to require new versions of macOS firmwares,
18:08j`eyeldondev: not sure exactly what you mean. some firmware is extracted by the installer and linux has to deal with it and some is already done for us by iboot
18:09j`eyfor example we require 13.5 for HDMI support
18:09j`eyso people on older fw had to upgrade
18:09eldondevlike, when I upgrade to linux 7, will it be incompatible with Apple firmwares for macOS <15?
18:09j`eybut I think there will be some backwards compatability
18:09PaulFertserBut is it likely the required macOS version is likely to change in the future?
18:09j`eyeldondev: Im hoping they wont break things, but maybe new features will require neweer fw
18:10svenwe generally try to support everything we can with the current set of firmware
18:11svendepending on Apple that may or may not work every time
18:11eldondevOk, thanks.
18:11eldondevI guess I'm mostly just interested in my little m1 mini from 2020,
18:11j`eyeventually the installer will hopefully gain the ability to upgrade the fw
18:12svenyeah, was just about to write that the installer will sometime in the far future be able to do the update as well
18:12j`eyI cant remember what m3's come with, but that will also be a fw that needs to be supported
18:12fossdd has quit [Ping timeout: 480 seconds]
18:13j`ey(the gpu and display controller driver already have support for multiple versioning in the code)
18:14eldondevOk, I guess for now I will just (a) perform a full wipe of the machine, (b) install sonoma via the online installer,
18:14eldondev(c) reinstall asahi.
18:14j`eyeldondev: whichever gives you the 13.5 fw
18:15eldondevj`ey: or the 14.1 firmware, right?
18:15j`eyok sonoma is 14, I never remember the names
18:15j`eysonoma will be fine
18:15eldondevCan I just dd/blkdiscard over the entire NVMe drive for a wipe?
18:15wintp has joined #asahi
18:16j`eyyou dont want to delete the first and last partitions
18:16eldondevI will still be able to boot from the USB installer even if I do, or no?
18:16j`eyyou need to DFU then
18:16mohit8158226 has quit [Quit: mohit8158226]
18:17fossdd has joined #asahi
18:17mohit8158226 has joined #asahi
18:18eldondevj`ey: Is DFU from linux going to be possible at some point? I thought I heard it was being considered?
18:18j`eyyou can do that with idevicerestore
18:20jannegI wouldn't rely on idevicerestore since I fear it is not a well tested path, m1 mini should be fine
18:22eldondevOk, seems like this is really what I wanted all along.
18:24wintp has quit [Ping timeout: 480 seconds]
18:24Axenntio has joined #asahi
18:24eldondevIs there any way to enter DFU mode without just already breaking everything?
18:29eldondevhttps://maclovin.org/blog-native/2021/putting-an-m1-mac-in-dfu-mode seems to indicate that I just need to hold down the power button while I plug in.
18:34wintp has joined #asahi
18:35fossdd has quit [Ping timeout: 480 seconds]
18:41fossdd has joined #asahi
18:43wintp has quit [Ping timeout: 480 seconds]
18:45tiagom has joined #asahi
18:46f_ is now known as funderscore
18:48funderscore is now known as f_
18:52wintp has joined #asahi
19:01fossdd has quit [Ping timeout: 480 seconds]
19:13fossdd has joined #asahi
19:17wintp has quit [Ping timeout: 480 seconds]
19:18julio7359 has quit [Ping timeout: 480 seconds]
19:25wintp has joined #asahi
19:33wintp has quit [Ping timeout: 480 seconds]
19:36fossdd has quit [Ping timeout: 480 seconds]
19:41wintp has joined #asahi
19:42fossdd has joined #asahi
19:43jeisom has joined #asahi
19:49julio7359 has joined #asahi
19:49wintp has quit [Ping timeout: 480 seconds]
19:50delsol has quit [Remote host closed the connection]
19:53Bertrand___ has quit [Ping timeout: 480 seconds]
19:53Bertrand___ has joined #asahi
19:53eldondevOk, I am trying to do the upgrade, opened it to the internet, and the sonoma installer is telling me "failed to download a required asset (SFR)"
19:54eldondevI don't know what SFR is, nor how to make the macos recovery download it.
19:54j`eysystem firmware recovery
19:55eldondevAny idea why it wouldn't be able to do this?
19:56eldondevIt doesn't give me any suggestions at remediation steps or anything.
19:58WorgIRC has joined #asahi
19:58wintp has joined #asahi
19:58WorgIRC has quit [Read error: Connection reset by peer]
19:59eldondevI assume the system firmware recovery isn't specific to my particular device.
19:59Axenntio has quit [Quit: Axenntio]
20:00fossdd has quit [Ping timeout: 480 seconds]
20:02fossdd has joined #asahi
20:03nicolas17 has joined #asahi
20:07wintp has quit [Ping timeout: 480 seconds]
20:17wintp has joined #asahi
20:18fossdd has quit [Ping timeout: 480 seconds]
20:19fossdd has joined #asahi
20:26wintp has quit [Ping timeout: 480 seconds]
20:29creechy has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
20:35wintp has joined #asahi
20:36mkurz_ has joined #asahi
20:37Guest986 has joined #asahi
20:37fossdd has quit [Ping timeout: 480 seconds]
20:37Guest986 has quit [Remote host closed the connection]
20:38creechy has joined #asahi
20:39julio7359 has quit [Ping timeout: 480 seconds]
20:43leioeldondev: sometimes that download is just not stable and a retry works iirc
20:43Brainium has quit [Remote host closed the connection]
20:44wintp has quit [Ping timeout: 480 seconds]
20:45shiggitay_ has joined #asahi
20:47fossdd has joined #asahi
20:48Bertrand___ has quit [Read error: Connection reset by peer]
20:49Bertrand___ has joined #asahi
20:53wintp has joined #asahi
20:54eldondevI booted into my old macos system and am attempting the update from there.
20:55shiggitay_ has quit [Read error: Connection reset by peer]
20:55shiggitay has joined #asahi
20:56eldondevI guess this is just the crux of why I want to put the apple (software) ecosystem in a very tight box for my person usage.
20:56leiooh, I was referring to when asahi-installer pulls them
20:58eldondevRestarting into sonoma I hope.
20:59eldondevcontemplating if I am not permitted to disconnect network, or if it will fail if I do :,D
21:03shiggitay has quit [Remote host closed the connection]
21:03wintp has quit [Ping timeout: 480 seconds]
21:05eldondevThe thing that makes me most frustrated: If I own the device, I should be able to mitm the update procedure.
21:06eldondevBut all this chatter is over TLS.
21:07eldondevAnd I don't think it's possible for me to install my custom CA in the update procedure.
21:07eldondevAlthough I guess I didn't try....
21:07sventhe earliest boot stages also need a machine specific signature from Apple
21:08svenhttps://github.com/AsahiLinux/docs/wiki/SW:Boot Stage 1 / everything that’s on the NOr
21:11wintp has joined #asahi
21:12fossdd has quit [Ping timeout: 480 seconds]
21:12eldondevYeah, I kinda wish I had the setup and time here to try the idevicerestore strategy,
21:13eldondevbut I don't :shrug:
21:16svenwhat I’m saying is that even if you could mitn TLS you still wouldn’t be able to install or update a “full security” macOS because that requires a machine specific signature
21:16eldondevYeah, I'm more interested in understanding/inspecting what it's doing.
21:19fossdd has joined #asahi
21:20eldondevThe whole point is recoverability.
21:20wintp has quit [Ping timeout: 480 seconds]
21:20eldondevAs this went today for me, if Apple's servers had been down, there was a 0% chance of success.
21:22eldondevEven if all FW is signed (as it should be!) if I can MITM TLS, I can still replay the environment for the most part to recover a working system.
21:28svenpart of a full security installation is a machine specific signature that you *cannot* replay
21:28sveneven if you can MITm TLS
21:29eldondevsven: is that descriptive of Apple, or normative?
21:30karlskewes has joined #asahi
21:30wintp has joined #asahi
21:30svenI don’t understand that question
21:31shiggitay has joined #asahi
21:37eldondevsven: like, are you saying that's necessary for the full security of any system,
21:37eldondevor that's just how Apple does it?
21:37sventhat how Apple does it
21:38eldondevYeah, sorry, Apple software has not treated me kindly today,
21:38wintp has quit [Ping timeout: 480 seconds]
21:39svenone of their security policies is called “full security”, https://support.apple.com/en-gb/guide/deployment/dep5810e849c/web
21:39eldondevBut now I've upgraded from ancient-ventura-asahi-arch to latest-sonoma-asahi-fedora, so just hoping I never have to do that again :grin:
21:39eldondevAnd all I had to do was open all the ports and ignore their suggestions about bootable media!
21:40wintp has joined #asahi
21:40chaos_princesscan't you pass a special flag to createinstallmedia so it creates an offline-capable installer?
21:44svenmaybe, it’ll still need to talk to Apple’s server during installation for that personalized full security signature though
21:46eldondevI wish there was a "turn off full security" bit that I could flip.
21:46j`eythere is, but im not sure if that helps you here
21:47j`eyasahi is run with "reduced security"
21:47eldondevRight, that's what the installer told me ;)
21:47eldondevI would rather have no security than get locked out and have a machine be trashed.
21:48chaos_princessEh, apple has an okay history with keeping recovery servers online.
21:48chaos_princessLike, you can still do internet recovery on earliest intel macs
21:49chaos_princessAnd iirc macos still can restore clickwheel ipods from the apple servers.
21:49wintp has quit [Ping timeout: 480 seconds]
21:50TramtristProbably a fedora specific question but what are the odds well see sway 1.9 released in asahi fedora 39?
21:52j`eythe fact it isnt even in testing for fc39 makes me wonder
21:52Tramtristah its not.. probably fc40 then
21:55nicolas17chaos_princess: afaik all Apple hardware remains recoverable to *some* software
21:56nicolas17if you install iPhone OS 1.0 on a first-gen iPhone (which you *can* do because they didn't have the anti-replay restore mechanism yet), it will fail to activate, because it used an older activation server that has since been shut down
21:56nicolas17but the last supported version (3.x) will work
21:59wintp has joined #asahi
22:09wintp has quit [Ping timeout: 480 seconds]
22:11shiggitay has quit [Remote host closed the connection]
22:12shiggitay has joined #asahi
22:15shiggitay has quit [Remote host closed the connection]
22:18shiggitay has joined #asahi
22:20wintp has joined #asahi
22:27hdbngr has quit [Ping timeout: 480 seconds]
22:31hdbngr has joined #asahi
22:32wintp has quit [Ping timeout: 480 seconds]
22:40Bertrand___ has quit [Ping timeout: 480 seconds]
22:40hdbngr has quit [Ping timeout: 480 seconds]
22:41wintp has joined #asahi
22:48hdbngr has joined #asahi
22:49julio7359 has joined #asahi
22:50wintp has quit [Ping timeout: 480 seconds]
22:53tiagom has quit [Ping timeout: 480 seconds]
22:56hdbngr has quit [Ping timeout: 480 seconds]
23:00wintp has joined #asahi
23:05hdbngr has joined #asahi
23:06tiagom has joined #asahi
23:07axt has left #asahi [#asahi]
23:08wintp has quit [Ping timeout: 480 seconds]
23:15hdbngr has quit [Ping timeout: 480 seconds]
23:16wintp has joined #asahi
23:24hdbngr has joined #asahi
23:32wintp has quit [Ping timeout: 480 seconds]
23:32hdbngr has quit [Ping timeout: 480 seconds]
23:40hdbngr has joined #asahi
23:41wintp has joined #asahi
23:49hdbngr has quit [Ping timeout: 480 seconds]
23:50wintp has quit [Ping timeout: 480 seconds]
23:58hdbngr has joined #asahi
…