#asahi · 2023-05-29 15:27
marcanFoxboron: yeah, I'm not saying it's easy#asahi · 2023-05-29 15:26
marcan(refer to my previous discussion on marketing/PR as to why this matters)#asahi · 2023-05-29 15:26
marcanI'm just trying to leave the official announcement for when it's all ready and shiny#asahi · 2023-05-29 15:26
marcananyone who has been paying a modicum of attention already knows what distro it is :p#asahi · 2023-05-29 15:25
marcanI'm not talking about ARM support in general, I mean working with us getting everything integrated.#asahi · 2023-05-29 15:24
marcaneh, I don't think RH cares about apple silicon :p#asahi · 2023-05-29 15:23
marcanit's just that we've grown up a bit since then and at least one Actual Real Distro has stepped up to do it officially ;)#asahi · 2023-05-29 15:23
marcanand I intend to continue maintaining the packages and PKGBUILDs to that extent too, it's easy to navigate for anyone who wants to see what's up#asahi · 2023-05-29 15:23
marcaneven with this outcome, I still think ALARM was the right choice for what Asahi intended to be (a reference distro real distros could use as an example of how to integrate support)#asahi · 2023-05-29 15:22
marcanregardless of how it is homed, there needs to be a team in charge of this#asahi · 2023-05-29 15:21
marcanit is a human problem#asahi · 2023-05-29 15:21
marcanit is not a technical problem#asahi · 2023-05-29 15:21
marcaneasy to hack on, rolling distro, reasonably shippable to end users (i.e. not Gentoo or Nix :p), mostly vanilla packages so no weird surprises, I'm already familiar with Arch, and I thought the maintenance situation wasn't this dire.#asahi · 2023-05-29 15:18
marcannot to my knowledge#asahi · 2023-05-29 15:17
marcanit is made by ~one person#asahi · 2023-05-29 15:17
marcanit is not#asahi · 2023-05-29 15:16
marcanI think the real answer here is the upstream Arch project needs to adopt arm64 support themselves#asahi · 2023-05-29 15:16
marcanand there are missing packages from Arch that should be available because they work just fine#asahi · 2023-05-29 15:15
marcanlike right now there are a whole bunch of packages on ALARM you can't install due to broken dependencies and nobody is fixing them#asahi · 2023-05-29 15:14
marcanit's just numbers, you can't single-handedly run a fork of something as big as Arch with one person#asahi · 2023-05-29 15:14
marcanI don't blame them, but unless that team drastically grows, it will not be a viable distro you can depend on#asahi · 2023-05-29 15:14
marcanwhich is to be expected when it's basically run by one person without enough free time#asahi · 2023-05-29 15:14
marcanbad QA in general#asahi · 2023-05-29 15:13
marcanbut I highly doubt debian would put out outright broken packages missing files like alarm did, several times#asahi · 2023-05-29 15:12
marcanwell gentoo doesn't even care since you build your own packages :p#asahi · 2023-05-29 15:12
marcangentoo and debian have official arm64 support with teams of size greater than one#asahi · 2023-05-29 15:12
marcanno, it does not#asahi · 2023-05-29 15:11
marcanreally though, given the state ALARM is in, I just can't recommend it. you *will* run into problems that have nothing to do with Asahi and there will be no solution. we're already in that situation, that's a big reason for the change.#asahi · 2023-05-29 15:10
marcannsklaus, j`ey: the arch packages will remain maintained, but obviously will get less testing going forward. there will probably be less integration work going into the Arch side going forward though.#asahi · 2023-05-25 09:08
marcandoesn't look like it got backported to 114 so you'll probably have to wait for chromium 115 for a real fix#asahi · 2023-05-25 09:05
marcanalternatively the next kernel update will include a workaround for that bug#asahi · 2023-05-25 09:05
marcantry PIPEWIRE_DEBUG=4 as a (very dumb and not guaranteed but worked for me by luck) workaround, until the change is released#asahi · 2023-05-25 05:57
marcanmaybe I should move ssh to 495#asahi · 2023-05-25 05:57
marcan:D#asahi · 2023-05-25 05:47
marcanI was tempted to reply "well of *course* Patchy wouldn't allow you to delete her library^Wfilesystem"#asahi · 2023-05-25 05:46
marcannicolas17: yesterday I was reading ceph-users and someone had Touhou character hostnames... we're all nerds here :p#asahi · 2023-05-25 02:17
marcanluke-jr: looking into your post history, I am not comfortable having you be a part of this community. please leave.#asahi · 2023-05-25 01:47
marcanpsykose: I'm sorry, what is this about?#asahi · 2023-05-25 01:42
marcanthe vmkernel requires paravirt metal#asahi · 2023-05-25 01:42
marcanthe real kernels don't require paravirt metal, they require a real AGX GPU#asahi · 2023-05-25 01:42
marcanyes#asahi · 2023-05-25 01:41
marcanluke-jr: macos *userspace* requires metal if you want graphics at all#asahi · 2023-05-25 01:40
marcanalyssa: because we only support dual mode because the whole thing is kind of a mess (cc sven)#asahi · 2023-05-24 16:06
marcanit's pretty easy to manually run the installer to pull the IPSW from a local HTTP server/copy (and the asahi stuff too if you're so inclined) and then it would truly be 100% offline, we just don't have a user friendly flow for it#asahi · 2023-05-24 16:04
marcan(can't promise recovery mode itself won't phone home but it's certainly lower risk than full macos)#asahi · 2023-05-24 16:04
marcanbut if you install from recovery mode (after going through macos initial setup, which you can do fully offline) it won't phone home to apple during install, it'll only grab stuff from their CDN.#asahi · 2023-05-24 16:03
marcan*offline#asahi · 2023-05-24 16:03
marcanhowever, we don't really have a flow for 100% online in the installer#asahi · 2023-05-24 16:03
marcanyou can also technically install asahi without ever putting the device online iff it comes with a firmware new enough already, and if it doesn't just DFU it (that tells apple someone did so but it's not like they can do anything about it after)#asahi · 2023-05-24 16:02
marcanthere is no all-powerful backdoor CPU like on x86 (ME, PSP)