2022-12-04
00:06benzmac16v has joined #asahi-alt
00:11Dcow has joined #asahi-alt
00:19benzmac16v has quit [Remote host closed the connection]
00:25Dcow has quit [Quit: dcow]
00:27Dcow has joined #asahi-alt
00:54Dcow has quit [Quit: dcow]
00:58jacksonchen666 has quit [Remote host closed the connection]
01:04jacksonchen666 has joined #asahi-alt
02:55ma1 has joined #asahi-alt
03:01jamespmorgan has joined #asahi-alt
03:02ma has quit [Ping timeout: 480 seconds]
03:06jamespmo_ has quit [Ping timeout: 480 seconds]
03:27benzmac16v has joined #asahi-alt
03:31benzmac16v has quit [Remote host closed the connection]
03:36benzmac16v has joined #asahi-alt
03:57benzmac16v has quit [Remote host closed the connection]
04:02benzmac16v has joined #asahi-alt
04:02benzmac16v has quit []
04:06tobhe_ has joined #asahi-alt
04:10tobhe has quit [Ping timeout: 481 seconds]
04:16benzmac16v has joined #asahi-alt
04:40benzmac16v has quit [Remote host closed the connection]
04:42benzmac16v has joined #asahi-alt
04:45benzmac16v has quit [Remote host closed the connection]
04:46benzmac16v has joined #asahi-alt
04:48benzmac16v has quit [Remote host closed the connection]
05:06benzmac16v has joined #asahi-alt
05:09benzmac16v has quit [Remote host closed the connection]
05:31j`ey has quit [Server closed connection]
05:31j`ey has joined #asahi-alt
06:20jannau has quit [Server closed connection]
06:20jannau has joined #asahi-alt
07:14sven has quit [Server closed connection]
07:14sven has joined #asahi-alt
07:27chadmed_ has joined #asahi-alt
07:30chadmed_ has quit [Remote host closed the connection]
07:33chadmed_ has joined #asahi-alt
07:54sneak has quit [Server closed connection]
07:55sneak has joined #asahi-alt
08:25TellowKrinkle has quit [Server closed connection]
08:25TellowKrinkle has joined #asahi-alt
08:31highvoltage[m] has quit [Server closed connection]
08:32highvoltage[m] has joined #asahi-alt
08:41jamespmo_ has joined #asahi-alt
08:48jamespmorgan has quit [Ping timeout: 480 seconds]
10:59Dcow has joined #asahi-alt
11:41Dcow has quit [Quit: dcow]
12:01mps has quit [Quit: Lost terminal]
12:06mps has joined #asahi-alt
13:10xcpy0 has quit [Quit: The Lounge - https://thelounge.chat]
14:05xcpy0 has joined #asahi-alt
15:15chadmed_ has quit [Remote host closed the connection]
15:31lawrence has quit [Remote host closed the connection]
15:33lawrence has joined #asahi-alt
15:44ma2 has joined #asahi-alt
15:48ma1 has quit [Ping timeout: 480 seconds]
15:59ma2 has quit [Ping timeout: 480 seconds]
16:24Glanzmann has joined #asahi-alt
16:24ma2 has joined #asahi-alt
16:40benzmac16v has joined #asahi-alt
16:41ma2 has quit [Ping timeout: 480 seconds]
16:52cy8aerGlanzmann: I wonder if it would be worthwhile to put the dcp kernel on the debian-installer stick? With asahi_drm it should not have these text mode changing problems anymore.
16:52benzmac16v has quit [Ping timeout: 480 seconds]
16:57Glanzmanncy8aer: I think I rather wait until it is in the asahi distribution, because it is still now very widely tested.
16:58ma2 has joined #asahi-alt
17:01ma3 has joined #asahi-alt
17:07ma2 has quit [Ping timeout: 480 seconds]
17:17Chainfire has joined #asahi-alt
17:30Dcow has joined #asahi-alt
17:34Chainfire has quit [Remote host closed the connection]
17:49Chainfire has joined #asahi-alt
17:50Chainfire@Glanzmann> works like a charm. Any plans to make a full desktop image a la what Debian has for amd64 ?
17:53GlanzmannChainfire: Not really, I mean you can just install the packages you want including the desktop environmnt. So I don't see the reason to do so.
17:54GlanzmannBtw, I updated the Debian kernel to match the asahi one. Still no dcp or gpu. Someone requested that I publish all kernel packages. They can be found here: https://thomas.glanzmann.de/asahi/2022-12-04/
17:55Chainfireoh yeah its just a mild inconvenience I have to do that manually the once every 6 months I use this haha. Thanks for your work on that, that's twice it saved my bacon
17:55Dcow has quit [Quit: dcow]
17:55ChainfireSo the reason the old version (made probably >6 months ago) stopped working is probably that m1n1 file?
17:58GlanzmannChainfire: The kernel need to match the device tree which is besides m1n1 and u-boot in the boot.bin file. So if the kernel is incompatible to the device tree it won't boot or do stupid things or does not detect hardware or god knows what.
17:59GlanzmannChainfire: In the far future the device tree will hopefully stabilize and also be downward compatible, but currently it isn't.
18:10benzmac16v has joined #asahi-alt
18:18benzmac16v has quit [Ping timeout: 480 seconds]
18:21ChainfireGlanzmann> suggestions: (1) change docs to include doing an 'apt update' before 'apt-get install' because it just failed without that (2) put the url to the docs in the login message
18:27GlanzmannChainfire: I added the 'apt-get update' everywhere. When you log in there is a file called quickstart.txt which contains all information necessary.
18:34Chainfire has quit [Remote host closed the connection]
18:37Dcow has joined #asahi-alt
18:46janrinze has joined #asahi-alt
18:46janrinzeGlanzmann: the issue with u-boot is that is scans for EFI partitions and does not know which was the intended one.
18:48janrinzeI solved my issues by using the same boot.bin and BOOTAA64.EFI on both EFI partitions. also needed to have the same grub version and files on ARCH and Debian partitions.
18:50janrinzemakes me wonder if it's easier to have one EFI partition and use that for all Linux installations.
18:54janrinzesidenote : ARCH and Debian can't share the same initrd.img because those work differently on each distribution.
18:55sventhere’s a reason we decided for multiple of those partitions, see https://github.com/AsahiLinux/docs/wiki/Open-OS-Ecosystem-on-Apple-Silicon-Macs
18:57janrinzesven: u-boot scanning for EFI partitions might not be compatible with the description in that link.
18:58jacksonchen666_ has joined #asahi-alt
18:59Glanzmannjanrinze: Jannau wrote a patch that tells u-boot for which esp to look for. I reverted that patch in the Debian installer.
19:00Glanzmannjanrinze: So with asahi boot.bin you're good with debian you aren't. Until you start shuffling parition numbers, because I think Debian as well as Asahi grub have the partition number (not uuid) hardcoded in the efi binary: strings /boot/efi/EFI/BOOT/BOOTAA64.EFI | tail -1 | pbot - > https://pbot.rmdir.de/h0Jz-cz3E9CeShztJLQ0jA
19:01jacksonchen666 has quit [Ping timeout: 480 seconds]
19:03GlanzmannI updated the Debian kernel again - forgot to do a pull and ended up with an old version. All the other artefacts are also rebuild.
19:03jacksonchen666_ is now known as jacksonchen666
19:04janrinzeGlanzmann: yup.. so if after Asahi installation we should not resize the OSX partition again when installing another Linux OS.
19:08Glanzmannjanrinze: Exactly. When you add additional installations they need to be added behind the current installation, otherwise you need to install grub. In addition to that the u-boot that is shipped by me always picks the first esp. OpenBSD does the same.
19:10Glanzmannjanrinze: THe patch that j'ey just posted is used as the following m1n1.bin passes the part uuid of the esp to 'boot.bin aka m1n1 stage2' u-boot picks than the right esp. However if the partition numbers are shuffled than grub might pick the wrong boot partition. I know that marcan tried to use the partuuid by that. An Debian did that previously but currently nolonger does that (maybe because I use
19:10janrinzej`ey: so the issue was that Debian install did not comply with that way of working for u-boot. Correct?
19:11Glanzmannjanrinze: I think you had two issues: 1) debian u-boot picks first esp. 2). You first installed asahi, than made macos smaller and installed Debian. By doing that you shuffled the partition numbers which made the asahi grub choke on.
19:12Glanzmannjanrinze: Yes. It is a patch that is only used by asahi. Upstream u-boot, bsd and Debian and Fedora version does not use it, don't know about the others.
19:12janrinzeGlanzmann: hard to remember if my Asahi install was older than the patch from j`ey. If it was there was no way this could be prevented.
19:13GlanzmannThe reason I don't use it because Debian was available before the the patch and I did not want to annoy existing users. But the patch from jannau is very careful. If no esp part uuid is specified or it can't find it it lets the user know what to do.
19:13janrinzej`ey: in general Asahi Linux installations after the adoptin of your patch should not be having any trouble such as the one I experienced, right?
19:14jannaujanrinze: it was just committed in that branch on july 11th, the change was included in every asahi release since the alpha release
19:16Glanzmannjanrinze: Jannau pasted a strings from the grub.efi the other day. THere you could see two references. One ussing the uuid and one using the partition number.
19:19janrinzejannau: and if these modules don't match the version of grub then a lot more erros can be seen
19:21Glanzmannjanrinze: Perfect. That is how it should be. I thought about making a video explaining how to troubleshoot the different issues (manually upgrading the stub, reinstalling grub, exchanging u-boot, reinstalling the kernel, etc.)
19:22jannaufrom what I remember from the strings it was just the config, could be that grub needs the config to find its modules
19:23Glanzmannjanrinze: Debian live system is you friend. I like the Debian live cd so much, that I build an amd64 version of it (optionally with my desktop config). So I can turn any machine into my machine running from RAM in 60 - 120 seconds. I use that everytime I need a live system as well as when delivering trainings in training centers.
19:24janrinzejannau: there's no way how grub would know where to load the modules but from the search paths
19:26janrinzeit's quite a complicated tree of dependencies. I might just have scratched the surface..
19:28jamespmorgan has joined #asahi-alt
19:35jamespmo_ has quit [Ping timeout: 480 seconds]
19:35Glanzmannjanrinze: Yes, but not on apple silicon: git reset --hard asahi-v2022.10-1; git clean -f -x -d &> /dev/null
19:35Glanzmannhttps://superuser.com/questions/1683814/loading-windows-os-using-mainline-u-boot-bootloader
19:38Glanzmannjanrinze: The issue is that Windows 11 does not have any device drivers for apple silicon.
19:44Dcow has quit [Quit: dcow]
20:22Glanzmann has quit [Quit: n8]
20:23Dcow has joined #asahi-alt
20:25Dcow has quit [Remote host closed the connection]
20:26Dcow has joined #asahi-alt
20:30Dcow has quit [Remote host closed the connection]
20:30Dcow has joined #asahi-alt
20:53Dcow has quit [Remote host closed the connection]
21:03janrinzeI've noticed a small performance increase with the latest kernels .. or am i imagining things? ;-)
21:30lawrence has quit [Remote host closed the connection]
21:33lawrence has joined #asahi-alt
22:41Dcow has joined #asahi-alt