04:08 <M0x8FFshulkk[m]> are there plans of graphic drivers coming in the future?

04:08 <M0x8FFshulkk[m]> like so i could run vulkan emulators without the moltenvk translation

04:09 <M0x8FFshulkk[m]> for example "mediocre" ones (noveau)

05:31 <opticron> M0x8FFshulkk[m], the kernel side of the GPU drivers is the current target afaict

08:04 <jannau> M0x8FFshulkk[m]: the asahi mesa 3D gpu driver is currently only opengl/opengl es though

11:48 <kettenis> jannau: having the devices on die 0 under /soc and the devices on die 1 under /soc/die1 feels a bit weird to me

11:48 <kettenis> but maybe this assymetric view does represent best what the hardware looks like

11:49 <kettenis> with the "die1" node representing the "UltraFusion" connect

11:57 <jannau> kettenis: yes, it is weird. maybe I need to organize the sharing of the t6001 stuff differently. I didn't want to add a pointless "die0" to m1 pro/max machines

12:02 <jannau> we could move everything to separate dtsi files and include them for t6000/t6001 under /soc and for the t6002 under /soc/die0 and /soc/die1

12:08 <kettenis> that would satisfy my OCD for symmetry a bit more

12:08 <kettenis> but I'm not sure that would reflect the actual hardware better

12:11 <kettenis> anyway, I think you're defenitely on the right path

12:14 <jannau> representing it as die0 / die1 would make sense imo. die0 is clearly the primary die. the ADT has a couple of die1-* nodes

12:17 <jannau> the hardware setup is a little strange though. the nvme on die1 is wirred to the die0 nvme interrupt but the nvme mbox irqs are not

12:20 <jannau> I need to remember to add a comment for that

12:21 <kettenis> probably a good idea to document that (and explicitly point out it isn't a mistake)

18:05 <Serentty[m]> I just installed Asahi. Since the installer enforces badnames (urgh), the first thing I went to do was change my username to what I actually wanted it to be... but I forgot to enable the root account first. So now I have no sudoers at all. How can I get to a root shell to fix this? My first thought was to deliberately mess up my kernel boot parameters in GRUB so that it would drop me at a recovery shell, but for some reason it does not accept

18:05 <Serentty[m]> any keyboard input in GRUB, so it just counts down until it boots normally.

18:06 <tpw_rules> m1 mac mini?

18:07 <Serentty[m]> It’s a MacBook Pro 13. I am using a USB keyboard since the internal one stopped working and I have been too lazy to get it fixed.

18:07 <tpw_rules> oh, not sure what the keyboard situation is like on that. but u-boot is not the friendliest to usb devices and keyboards

18:09 <Serentty[m]> Can you think of any other way to get root access? Logging in as my account doesn’t work anymore either. I could always run the installer again, but I’m hoping there is something simpler. This kind of thing is so easy to fix on most machines.

18:09 <tpw_rules> try another one if you have it

18:11 <Serentty[m]> Yeah, I have no others to try. Do I have to reinstall then?

18:11 <tpw_rules> you could edit the grub.cfg on the efi partition from macos

18:11 <Serentty[m]> Oh, good idea! Thanks.

18:11 <tpw_rules> (hoping that asahi linux puts it there, i don't recall...)

18:12 <tpw_rules> it probably doesn't, actually

18:18 <Cy8aer[m]> Or get the [Debian Live stick](https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/), boot it, chroot into your system partition and set the root password...

18:19 <Cy8aer[m]> sorry install and init grub from there...

18:19 <tpw_rules> well then you have to gamble on a working flash drive, although i haven't really heard of compatibility problems with those

18:38 <mps> keyboard works for me in u-boot and grub on mbp

19:57 <Serentty[m]> Alright, I just did it the long way around and completely reinstalled. Since the installer seems to be hardcoded to want to shrink your MacOS partition, I deleted the Linux on, grew the MacOS one again, yada yada. Anyway, this time I made sure to set a root password before I changed my username to start with a capital letter. Phew.

20:20 <MichaelRose[m]> Hi question: Is Asahi able to be installed on an M1 Macs internal storage? If not does it have access to internal storage?

20:21 <j`ey> MichaelRose[m]: yes it can be installed on the nvme

20:21 <j`ey> that's all the current installer supports

20:22 <j`ey> and parts of it (bootloader..) *have* to be installed on the nvme

20:22 <MichaelRose[m]> I remember there being a challenge previously did that change at some point?

20:22 <j`ey> maybe youre confusing it with external storage?

20:24 <hectour[m]> MichaelRose[m]: It was with the intel Macs with T2 chips I believe where you could boot Linux from external storage but not install it on the internal SSD

20:24 <MichaelRose[m]> Thank you

20:25 <hectour[m]> * > <@michaelmrose:matrix.org> I remember there being a challenge previously did that change at some point?

20:25 <hectour[m]> It was with the Intel Macs with T2 chips I believe where you could boot Linux from external storage but not install it on the internal SSD

20:25 <j`ey> https://twitter.com/marcan42/status/1355015462099148803

22:22 <hectour[m]> <j`ey> "https://twitter.com/marcan42/..."; <- Interesting. I just remembered it from a LTT video but didn’t know about this