ChanServ changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
beeblebrox has quit [Quit: Konversation terminated!]
jamespmo_ has joined #asahi-alt
jamespmorgan has quit [Ping timeout: 480 seconds]
amw has joined #asahi-alt
leafpawz has joined #asahi-alt
leafpaw has quit [Ping timeout: 480 seconds]
benzmac16v has joined #asahi-alt
benzmac16v has quit [Remote host closed the connection]
Avaflow has quit [Quit: why do they call it oven when you of in the cold food of out hot eat the food?]
chadmed_ has joined #asahi-alt
pthariensflame has joined #asahi-alt
pthariensflame has quit []
chadmed has quit [Remote host closed the connection]
chadmed_ has quit [Remote host closed the connection]
Avaflow has joined #asahi-alt
Glanzmann has joined #asahi-alt
<Glanzmann>
amw: The update script does not deinstall the old kernel and makes a backup copy of the old m1n1. So I would jurst revert back the boot.bin from the macos and boot the old kernel.
lawrence has joined #asahi-alt
arnd has joined #asahi-alt
<arnd>
Glanzmann: I did a fresh Debian install the other day, and ran into two problems, not sure where you track those, or if they are known:
<arnd>
When I installed a second image to a separate partition, both installs got the same UUID on the rootfs, and I had to manually change one with tune2fs to be able to boot both
<Glanzmann>
arnd: Can you elaborate on the first point? I have dcp not enabled in the default kernel. And dcp works for me on the mini with the latest version.
<Glanzmann>
arnd: Second issues is known. I decided to only create a new uuid everytime I build a new image. These days I rarely build them new.
<Glanzmann>
In order to rewrite the uuid I need to disable ext4 metadata checksumming which I don't feel comfortable with.
<arnd>
Glanzmann: sorry I should have mentioned I used a custom .config. The problem I saw is that after kernel commit 314199f7b863 ("drm/apple: Check if DCP firmware is supported"), I get a warning "Could not read 'apple,firmware-version'" followed by a probe failure
<arnd>
the property was added after v1.1.8 in m1n1
<Glanzmann>
Do I need to update stage1 m1n1 or stage2?
<arnd>
stage2
<_jannau_>
arnd: was the dcp failure benign? i.e. simpledrm continued to work?
<_jannau_>
2nd stage m1n needs to be 1.2.2
<arnd>
_jannau_: yes, I could still boot with a 1080p framebuffer, just not switch to 4k
<arnd>
Glanzmann: on the uuid thing, would it be possible to do the 'tune2fs -U random' as part of the installation process, or do you need the UUID to be hardcoded in grub.cfg/fstsab/... inside of the image?
<Glanzmann>
arnd: The tooling in Debian unstable is to old to do that without disabling metadata checksumming in ext4.
<arnd>
_jannau_: the first time I actually got into 4k mode with the install, I had a slightly older kernel that I built last week, and that ended up hanging a few seconds after logging into xfce, but I think that was either a bug in the kernel, or a mismatched firmware version
<arnd>
Glanzmann: ok, I see
<Glanzmann>
arnd: Maybe the tooling is now ready to rune tune2fs -U random wit metadata checksumming enabled, I'll try it later and if that is the case I'll fix it.
<Glanzmann>
arnd: I bumped m1n1 to v1.2.2 for new builds, but did not build it yet, so in the future you won't have issues with that anymore.
<Glanzmann>
arnd: What I don't understand is that I did not hit the issue with my 'dcp.sh' which I run on the Mac mini.
<Glanzmann>
arnd: IIRC correctly the issue was that tune2fs -U random only works when metadata checksumming is disabled or the filesystem is not mounted. But that would result in a very complicated initrd and as a result I said I'm not going to do it. But there was a upstream commit which allowed to do it with mounted ext4 which have metadata checksumming enabled which was not yet in Debian testing.
chadmed_ has joined #asahi-alt
digicyc has joined #asahi-alt
leafpawz has quit [Ping timeout: 480 seconds]
<arnd>
Glanzmann: what I was thinking here was to change the UUID on the installer side in 1TR, by shipping a macos compiled tune2fs, but I don't know enough about how the installation procedure works
<arnd>
Glanzmann: for you mac mini, it's possible that the kernel only just changed. _jannau_'s commit is dated Dec 4 11:36, so maybe your latest kernel is older than that?
<arnd>
oh, in that case I would simply be confused, as you are on 6.1-rc6-5, and it only fails in 6.1-rc8-2
<arnd>
I think the 6.1-r6-5 must be the version that crashed for me, and then I updated to HEAD (rc8-2), which caused dcp to not load
jamespmorgan has joined #asahi-alt
jamespmo_ has quit [Ping timeout: 480 seconds]
janrinze has joined #asahi-alt
<ahdeb[m]>
Glanzmann (IRC): FWIW if there are things you'd like to see updated inside Debian, I can try to help facilitate that if you give me details about what you need. (I'm a DD, but can't promise random maintainers will always listen to my suggestions. If I get a no I could report back with reasons here atleast.)
<ahdeb[m]>
(Also, the freeze is coming..... so if there's anything to change in Debian, it needs to start ASAP.)
<Glanzmann>
arnd: Yes, I'm older than that. I saw the changes yesterday or the day before yesterday in the repositories, but did not yet build the new version.
<Glanzmann>
ahdeb[m]: I see. From my point of view Debian is fine. The only thing that was very unstable for me was the Debian installer. But since we're nolonger using it.
<Glanzmann>
Of course at some point we need a newer mesa once the GPU is ready. But I don't know the timeline for that.
<Glanzmann>
arnd: Change the uuid from 1tr would require to change the installer. I use m a r c a n s installer without any modification and do not want to change that.
<Glanzmann>
arnd: So I need to change it in the initrd or from the running system. Or I just build the Debian assets on a daily basis. That way we have every day new uuids.
<arnd>
right, that's probably not worth it then, or possibly the installer could be changed for everyone, in case the same thing can happen on arch, fedora, etc
<arnd>
having a daily build with a new uuid would not have helped me, as I did both installs on the same day. What happened is that I tried to set things up on the first install, made a mistake that i couldn't recover and installed a second debian in order to fix the first
chadmed_ has quit [Remote host closed the connection]
<Glanzmann>
arnd: There is a debian live system which is quiet versatile.
<Glanzmann>
You can use it to fix things.
<Glanzmann>
It runs from a ramdisk and you can install all packages as long as you don't run out of RAM.
Glanzmann has quit [Quit: leaving]
<opticron>
I wonder if the GPU driver will move to asahi-dev before or after the UAPI changes necessary for vulkan support
<jannau>
before, UAPI changes are months but imo the driver and mesa is useful/stable enough for the preview Lina hinted for before the end of this year
beeblebrox has joined #asahi-alt
<opticron>
I guess the need for mesa packaging may be coming sooner than glanzmann thinks
jacksonchen666 has quit [Remote host closed the connection]