#
…

2022-10-26

00:01Etrien___ has quit [Ping timeout: 480 seconds]
01:45Etrien has quit [Read error: Connection reset by peer]
01:46Etrien has joined #asahi-alt
01:57pthariensflame has joined #asahi-alt
02:06pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
04:11caden has joined #asahi-alt
04:11cadenHello. I am looking for assistance in the "Fedora Desktop" alt release
04:21caden has quit [Quit: caden]
04:22caden has joined #asahi-alt
04:24caden has quit [Remote host closed the connection]
04:38Glanzmann has joined #asahi-alt
04:39Glanzmanncaden: I will upgrade the Fedora as soon as it is released. I'll also update the kernel with the new features as soon as marcan has updated alarm with it.
04:55Etrien has quit [Read error: Connection reset by peer]
04:55Etrien has joined #asahi-alt
04:56chadmed has joined #asahi-alt
05:08chadmedsam_: has there been any discussion upstream regarding rust BDEPENDs for kernel builds? since i suspect we're going to need that sooner than most i'd like your thoughts on how we should approach that
05:11chadmedactually i guess its an RDEPEND since building the kernel happens at runtime from portage's point of view
05:15Glanzmannjannau: I tried to build a kernel with dcp/gpu. But I think I'm missing a config option or more. Can you tell me what I'm doing wrong? Or if it is not supposed to work on the mini (where I tested) or it still to early, I'll wait until it is alarm. This is what I tried: https://tg.st/u/gpu.sh dmesg: https://tg.st/u/f64b8e2ca30361db9601505ad28ec485a85a50a8051f1dfdcb7343865ecf040.txt build output:
05:43chadmedyou didnt build the dcp kernel module
05:44Etrien has quit [Read error: Connection reset by peer]
05:45Etrien has joined #asahi-alt
06:01Glanzmannchadmed: I see. Lets fix that.
06:12Etrien__ has joined #asahi-alt
06:17Etrien has quit [Ping timeout: 480 seconds]
06:21Glanzmannchadmed: I enabled DRM_APPLE the kernel boots, x starts but I don't have mouse, keyboard (via usb-c or usb-a) or network. Either it crashed or all the devices no longer work (they worked before, but reboot did not work). Maybe someone else has an idea, otherwise I'll wait a little bit longer till things are ready for enduser consumption.
06:22GlanzmannInteresting. So the power button worked. So all usb-a/usb-c and network seems to be the issue. Now it ahngs on shutdown.
06:22chadmedtry doing a cold boot. theres an issue with DARTs locking on soft reboots which need a full poweroff to fix (at least for t600x, no clue on t8103)
06:23GlanzmannTried that. After the reboot I still don't have a single I/O device (usb-a, usb-c, network).
06:24GlanzmannSo I just revert back to the old kernel and wait a little bit longer.
06:26Etrien__ has quit [Read error: Connection reset by peer]
06:26Etrien has joined #asahi-alt
06:41jannauGlanzmann: there is a probing issue with DART and drivers using an iommu, try building apple-dart built-in instead of module as workaround
06:42Glanzmannjannau: Thank you, I'll try the same.
06:49jannaunote that internal displays come back with minimal brightness from DPMS on M1 devices but not M1 Max (and I assume Pro)
06:50GlanzmannYes, I read that. I just tried on the mini for now. Not planing on the notebooks at the moment.
06:50GlanzmannI still read all the backlog of IRC every day. :-)
07:02cy8aerGlanzmann: just a question from an unitiated: For the core dcp/gpu no mesa is needed? And if it is needed: is there a special version to be compiled with Debian?
07:03cy8aer(just a question what must be prepared if it is on the official kernel)
07:14chadmedmesa is required for the gpu since it contains the userspace portion of the driver (GLES implementation etc). DCP doesnt do rendering and so doesnt "require" mesa to operate, but mesa provides llvmpipe which software renders your desktop
07:15chadmedsomeone will need to provide a mesa debian package with the asahi driver compiled. they might just already build all possible drivers for a platform upstream so best to check there
07:20mpsdid anyone tested 4K page size with current asahi-wip branch
07:20cy8aerchadmed: Ok, then it would be some libdrm-apple I guess. How deep is it in the upstream codebase are the patches still beside the upstream?
07:22chadmedupstream master branch tracks pretty closely since alyssa submits stuff to the CI bot and it gets merged, not sure what the go is with dot number releases though
07:28cy8aerThen I will look at the packaging stuff of the other mesa modules how it is done. If it is simple to build I try it, otherwise I will report a wishlist bug.
07:29cy8aer(it must be build officially anyways)
07:42_jannau_changes to work with the linux kernel driver are not upstream though
07:48cy8aer_jannau_: yes just pre preparation and having an overview.
07:48cy8aer... how the packaging works for mesa.
08:05psydroid[m] has quit []
08:06Dcow has joined #asahi-alt
08:18ashi has joined #asahi-alt
08:24ashiGlanzmann: wouldn't it make sense to strip all the other arm platforms (amlogic, imx etc) from the kernel config. Also amdgpu noveau and other drm drivers can be removed I think. Helps compilation time a lot. :)
08:24Glanzmannashi: I aggree. But I tried to stay as close to the debian config as I could. THat is the reason why the Debian config is so bloated.
08:25Glanzmanncy8aer: I had the same question, that you asked, and now it is a little bit clearer.
08:25Glanzmannmps: I did not try 4k for a while.
08:25ashiGlanzmann: Yes, that makes sense somehow, but also assumes that the kernel should work everywhere. At least my local config is now without a lot of stuff because I lack patience ;)
08:26Glanzmannmps: But probably rmk (Russel King) did because he needs it.
08:26Glanzmannashi: I have very fast build machines and ccache. So for me it is fast. But I'm crosscompiling. But If I had to build my kernels on a m1, I would also be to impatient.
08:27ashiGlanzmann: I also do cross-compilation but on a fanless x86-86 which is slower than the m2 macbook air, but I do not want to let this run hot so long.
08:29ashiGlanzmann: another thing... is there a reason you went for CONFIG_DRM_APPLE which is disabled in the official config?
08:30ashioffical=asahilinux arch
08:31j`eyashi: to try it out!
08:32ashij`ey: okay, I enabled PM_SUSPEND to try it out :P - *seems* to work at least somehow
08:33j`eythats good
08:35ashiI did not stay suspended last time I tried, but this time it seems to stay somehow suspended, there are some errors in dmesg that something could not reach a power saving state but I do not know the impact
08:35j`eybefore the fixes it was *obviously* broken ;)
08:35ashiNow it is probably not perfect but at least not obviously ;)
08:38ashidumb question, does having dcp support now means brighness support on a laptop screen?
08:38Glanzmannashi: Because dcp was only very recenlty merged.
08:38_jannau_unless by brighttness support you mean switching to minimal brightness after suspend
08:40ashi_jannau_: no I prefer "last brightness from macos" behaviour
08:46Dcow_ has joined #asahi-alt
08:48chadmedi need to have a think about how to bring the new fw handling across to gentoo. i like to think we have some latitude in terms of outright guarantees that stuff works with no intervention since... well, its gentoo
08:49chadmedbut getting the firmware into the initramfs in a way that is consistent with asahi by default is good, users who gun for nonstandard setups are on their own though
08:50_jannau_I'd just make a dracut module for it, can probably shared with fedora. anyone using something else has to deal
08:51_jannau_also see if bootloader options to add the cpio are feasible
08:52chadmedwe can just add to /etc/default/grub for the bootloader, or whatever sd-boot does (been meaning to look into that)
08:52j`eymarkan mentioned GRUB_EARLY_INITRD_LINUX_STOCK
08:52chadmedyeah thats the one
08:53chadmedat the same time if we have a dracut module (akin to mkinitcpio hooks) we can just copy the firmware into the initramfs proper and disregard bespoke bootloader configs
08:53Dcow has quit [Ping timeout: 480 seconds]
08:56chadmedthe main thing is that the firmware gets loaded on first boot, which already isnt a problem for us because the gentoo install script i wrote runs update-vendor-firmware inside the chroot so that all the firmware is where the kernel modules expect it to be when you reboot into the rootfs
08:58_jannau_firmware handling in the initramfs instead of copying allows us to distribute installer images
08:59chadmedyeah, the idea appeals to me
09:18chadmedoh wow yeah ok this will be quite easy with a dracut module
09:19mpsGlanzmann: thanks for info
09:31ashi has quit [Ping timeout: 480 seconds]
09:40marve has joined #asahi-alt
09:49chadmed has quit [Quit: Page closed]
09:50marve has quit [Quit: Leaving]
09:59chadmed has joined #asahi-alt
10:29ashi has joined #asahi-alt
10:31chadmed has quit [Quit: Konversation terminated!]
10:32chadmed has joined #asahi-alt
10:34chadmed has quit []
10:43ashi has quit [Quit: Leaving]
10:56leif has joined #asahi-alt
10:58leifchadmed I started including the firmware in my image with a similar method. IIRC I though you said dracut wasn't working for you.
11:00chadmed has joined #asahi-alt
11:00sam_chadmed: gentoo-kernel it'd be BDEPEND, for gentoo-sources it's more complicated but it's still pretty much a BDEPEND because nobody installs a binpkg of *gentoo-sources*
11:00chadmeddracut module works
11:00sam_but no, no discussion yet
11:02chadmedunderstandable, ill keep thinking. i think the most annoying thing is going to be having to pull in a specific version since rust_is_available complains if your rustc/bindgen is too new
11:05_jannau_it complains but builds fine, I'd restrict the version only if there are problems
11:05leifInteresting, I'd like how you approach that. I'll take a stab at this weekend.
11:05leif has quit [Quit: Leaving]
11:06leif has joined #asahi-alt
11:06leifs/like/like to see/
11:06leif has quit []
11:07chadmedserendipitous timing :P
11:07chadmedive just pushed a dracut module to https://github.com/chadmed/asahi-gentoosupport under the branch dracut-module for handling firmware in the initramfs
11:08sam_chadmed: ultimately we want to do a RUST_MAX_SLOT like LLVM
11:08sam_so this might be good motivation for that
11:08chadmedhappy to share with fedora of course, if there are any issues with it though please let me know
11:08chadmedyeah that sounds like a good idea
11:08_jannau_asahi uses the packaged rustc/bindgen
11:09chadmedi built the driver with a 1.64 toolchain and there were no complaints, cant test at runtime though since i only have a t6001
11:12leif has joined #asahi-alt
11:14leifcool, thanks! I'll let you know.
11:14leif has quit []
11:41leif has joined #asahi-alt
11:44leifThere's something about the firmware that I don't quite understand. After the all_firmware.tar.gz file gets created during the install process -- does ever get updated after that? Just trying to work out whether the firmware extraction piece is just a one-time operation.
11:48Glanzmannleif: Currently not, but there are plans to do so.
11:48chadmed has quit [Read error: No route to host]
11:48GlanzmannBut there might be later on needed to be extracted additional firmware from all_firmware.tar.gz in order to support previously unsupported hardware.
11:49GlanzmannThat happened before with bluetooth.
11:49Glanzmannleif: markan planned on creating a stub upgrader if it becomes necessary for example once the gpu code is shipped.
11:50_jannau_leif: yes, it get's updated. asahi ships asahi-fwextract. used to extract the bluetooth and the usb pcie hcd firmware
11:54leifI get that. I've created a fwextract rpm based off of that https://www.leifliddy.com/asahi-linux/36/aarch64/ that implements the same post_trans script https://github.com/AsahiLinux/PKGBUILDs/blob/main/asahi-fwextract/asahi-fwextract.install
11:54leifHowever, this only extracts firmware from all_firmware_tar.gz. What I was asking is whether there was a process in place to update the all_firmware_tar.gz file itself.
11:54leifGlanzmann Thanks
11:56_jannau_ah, sorry. I misread that. yes, that will only be updated by non-existing stub update progress
12:00leif has quit [Quit: Leaving]
12:07chadmed has joined #asahi-alt
13:37chadmed has quit [Read error: No route to host]
16:13GlanzmannAbout the kernel and rust. Is a newer version fine or should I install exactly the version the kernel expects?
16:34GlanzmannSo, I was able to compile the rust gpu driver and the kernel boots, but: https://pbot.rmdir.de/tJKXXuiRuLD3HCMczTfOFQ
16:34GlanzmannGuess, I'll try it later and revert back for now. Interesting how to set up a rust build environment. But I went the unsuported way with gcc ...
16:37tobheGlanzmann: did you manage to build a deb or just plain mainline kernel?
16:39mpshmm, interesting, I've built kernel and got appledrm.ko without any change in build env, even didn't knew this module is build
16:39_jannau_Glanzmann: you need GPU support in m1n1
16:40mpsis the appledrm.ko gpu driver
16:40_jannau_tobhe: isn't 'make deb-pkg' in the kernel dir enough
16:40_jannau_no, appledrm is dcp
16:40Glanzmannjannau: I hope that I have it because I use the 'origin/lina/gpu-wip' branch of m1n1. This is how I build it: https://tg.st/u/gpu.sh
16:40tobhe_jannau_: depends on how you package i guess
16:41tobhei was assuming debian use their own kernel build infrastructure
16:41Glanzmanntobhe: I did not create a deb, but I could do that.
16:42Glanzmanntobhe: You can use 'make; make modules_install; make install' on Debian if you want to redistribute it, you would use make bindeb-pkg (what I normally do).
16:43tobheah ic. Ubuntu doesn't use the upstream bindeb infrastructure and i wasn't sure about Debian
16:45Glanzmanntobhe: I'm not sure if Debian does, but I usually do it like this. At least since it is available. Before that I used something different.
16:48_jannau_Glanzmann: see "memremap attempted on ram 0x0000000bfff74000 size: 0x4000". unfortunately little information why there's a problem with that
16:50Glanzmannjannau: Do you think it makes a difference if I update my first stage m1n1?
16:51Glanzmannjannau: I have the 16 GB m1n1. IIRC markan has the 8 GB m1n1. Maybe there is a subtle difference.
16:54Glanzmannmps: As j said before. apple_drm is dcp and asahi_drm is the gpu.
16:57Glanzmannjannau: You did a nice job on dcp. I tested it only on the mini but the resolution is detected and powering off and on the monitor brings back the picture. I worked the whole day with it.
16:59Glanzmannjannau: Modeswitching also appears to be working nicely. :-)
17:04mpshmm, lets try build again then
17:05mpsthough I don't need gpu for now
17:07Glanzmannmps: Let me know, if it works for you.
17:10mpsuh, I see it will not work, probably have to add some things to build env. have to look what
17:11mpsmaybe need to add rust to makedepends
17:12jannauGlanzmann: I can't see how 1st stage m1n1 would make a difference, running here with random 1st stage m1n1, probably from the 1st alpha release
17:13Glanzmannmps, I used https://rustup.rs/ and than I followed the https://www.kernel.org/doc/html/next/rust/quick-start.html to downgrade it to the version the kernel wants.
17:13jannauno, should work with 16GB, and the failing address is at the end of 16GB physical ram as expected
17:13Glanzmannjannau: I see, maybe I should try to build it with clang than.
17:14jannaubuild 2nd stage m1n1 with clang? makes no difference. mine is build with gcc
17:15GlanzmannI see, I thought about building the kernel with clang. Because I'm using gcc for the kernel and the rust kernel quickstart said gcc is experimental.
17:23Glanzmannjannau: If you want you can send me your kernel config and I'll give it a spin. But this time I started fromt he PKGBUILDS/asahi config and only added apple_drm and asahi_drm + plus dependencies.
17:24GlanzmannBut I can also wait a little bit longer until it is in the official installation and than try again.
17:28GlanzmannAnother dmesg after a complete power off and recompiled from scratch usingt the script: https://pbot.rmdir.de/qrV1yIVk80_UpljpRPZicg
17:38caden has joined #asahi-alt
17:39caden has quit [Remote host closed the connection]
17:46jannauGlanzmann: oh, I wasn't aware that the kernel even builds with gccrs
17:47jannauor gcc + rustc? wasn't aware that that was working either
18:31Dcow_ has quit [Remote host closed the connection]
18:31Dcow has joined #asahi-alt
18:40Dcow has quit [Ping timeout: 480 seconds]
19:11Dcow has joined #asahi-alt
20:41Dcow has quit [Remote host closed the connection]
20:42Dcow has joined #asahi-alt
20:43Dcow has quit [Remote host closed the connection]
20:43Dcow has joined #asahi-alt
21:15Etrien__ has joined #asahi-alt
21:20Etrien has quit [Ping timeout: 480 seconds]
21:31Etrien__ has quit [Read error: Connection reset by peer]
21:31Etrien has joined #asahi-alt
21:31jacksonchen666 has joined #asahi-alt
21:58ayke_ has joined #asahi-alt
…