2022-08-16
04:14chadmed has quit [Quit: Konversation terminated!]
07:13amwGlanzmann: I did the re-install and it created a small FAT "EFI - UEFI" partition with uboot, m1n1 and the firmware.tar in it
07:13amwIt left the rest of the free space un-allocated - so I have added another 200GB partition to my Linux boot!
09:17pjakobsson has quit [Ping timeout: 480 seconds]
09:25pjakobsson has joined #asahi-alt
10:25pjakobsson has quit [Ping timeout: 480 seconds]
11:48pjakobsson has joined #asahi-alt
13:04mpsis there a way to apply plain diff in git tree, someone posted me diff for config of kernel as plain diff
13:14_jannau_patch should detect the format automatically. does `patch -n` work? if not the diff is probably corrupted
13:26mps`patch -p1 --dry-run < ~/config-asahi.aarch64.diff` => patch: **** Only garbage was found in the patch input
15:51isoriano has joined #asahi-alt
15:52Glanzmannisoriano: Can you try this kernel and let me know if it improves? https://tg.st/u/linux-image-5.19.0-asahi-00002-ga120b858ebeb_5.19.0-asahi-00002-ga120b858ebeb-1_arm64.deb
17:36isoriano 3.356969] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_pwr.c:484: failed waiting on Touch reset completion event
17:36isoriano[ 3.459951] rtkit-helper 24e400000.mtp: RTKit: syslog message: bootloader.c:452: Failed to attach to AFE (-6)
17:36isoriano[ 3.459967] rtkit-helper 24e400000.mtp: RTKit: syslog message: bootloader.c:453: AFE Chip Boot Failure: No HINT_L
17:36isoriano[ 3.459974] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_pwr.c:496: AFE bootload failed
17:36isoriano[ 3.459982] rtkit-helper 24e400000.mtp: RTKit: syslog message: mac_touch_pwr_mgr.c:235: [TPM] Mac Power Manager State Machine Stopped
17:36isoriano[ 3.460017] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_transport.c:179: afe_transport_stop already stopped
17:36isoriano[ 3.460071] dockchannel-hid 24eb30000.input: Got GPIO command for bad GPIO multi-touch#167
17:36isoriano[ 3.460161] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_pwr.c:302: AFE reset request failed
17:36isoriano[ 3.470089] rtkit-helper 24e400000.mtp: RTKit: syslog message: touch.c:88: Touch Reset Ext Request: OK
17:36isoriano[ 4.203735] ieee80211 phy0: brcmf_p2p_set_firmware: failed to update device address ret -52
17:36isoriano[ 4.207199] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-52
17:36isoriano[ 4.470151] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_pwr.c:484: failed waiting on Touch reset completion event
17:36isoriano[ 4.573284] rtkit-helper 24e400000.mtp: RTKit: syslog message: bootloader.c:452: Failed to attach to AFE (-6)
17:36isoriano[ 4.573297] rtkit-helper 24e400000.mtp: RTKit: syslog message: bootloader.c:453: AFE Chip Boot Failure: No HINT_L
17:36isoriano[ 4.573311] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_pwr.c:496: AFE bootload failed
17:36isoriano[ 4.573329] rtkit-helper 24e400000.mtp: RTKit: syslog message: mac_touch_pwr_mgr.c:235: [TPM] Mac Power Manager State Machine Stopped
17:36isoriano[ 4.573343] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_transport.c:179: afe_transport_stop already stopped
17:36isoriano[ 10.608295] dockchannel-hid 24eb30000.input: Interface multi-touch is already starting
17:36isoriano[ 21.102095] dockchannel-hid 24eb30000.input: Interface multi-touch is already starting
17:36isoriano[ 7232.674162] macsmc-rtkit 23e400000.smc: RTKit: syslog message: charger.cpp:1976: Not charging:400001
19:04Votes78 has quit [Killed (NickServ (Too many failed password attempts.))]
19:05Votes78 has joined #asahi-alt
19:19isoriano has quit [Quit: Leaving]
19:20isoriano has joined #asahi-alt
19:20isoriano has quit []
19:31isoriano has joined #asahi-alt
19:32isorianoLinux m2mbp-debian 5.19.0-asahi-00002-ga120b858ebeb #1 SMP Sat Aug 13 21:22:23 CEST 2022 aarch64 GNU/Linux
19:41j`ey[ 2.730988] rtkit-helper 24e400000.mtp: RTKit: syslog message: afe_pwr.c:484: failed waiting on Touch reset completion event
19:42isorianoIt worked initially and I was updating from time to time via @Glanzmann's script .. curl -sL https://tg.st/u/ksh | bash
19:54Glanzmannisoriano: Could you run the 'ksh' script again. I rebuild all artefacts with the 5.19 tree that asahi-dev uses.
19:55Glanzmannj`ey: No, I don't have packages. I just have a script that overwrites the to-be-chainloaded m1n1+dtb+u-boot in /boot/efi/m1n1/boot.bin
19:56Glanzmannisoriano: Can you please run 'curl -sL https://tg.st/u/ksh | bash' again and reboot and see if that fixes your issues?
19:58Glanzmannj`ey: Maybe I should build packages for m1n1. But I hope that soon Debian upstream will take care of that and I can go back to sleep. :-) I'm also afraid that everything breaks if u-boot/m1n1/dtb is not in sync with the kernel.
19:59GlanzmannSo I did not build packages, because I was afraid that someone updated m1n1 without the kernel or vice versa and as a result break their system.
20:00isorianoW: Possible missing firmware /lib/firmware/apple/tpmtfw-*.bin for built-in driver dockchannel_hid
20:02isoriano has quit [Quit: Leaving]
20:03Glanzmannj`ey: I also throught about putting m1n1 in the kernel package, but than you can not install multiple kernels...
20:04Glanzmannj`ey: Probably not going to happen, but I think the cleanest way would be to teach our boot chain to pick the right device tree on a per kernel basis. Or just wait until the device tree settles.
20:05isoriano has joined #asahi-alt
20:06isorianoLinux m2mbp-debian 5.19.0-asahi-00002-g84ad91b47c9c #1 SMP Tue Aug 16 18:27:52 CEST 2022 aarch64 GNU/Linux
20:08Glanzmannisoriano: Can you please run 'last' and identify the kernel version that worked for you?
20:14GlanzmannHere is the latest rc7: https://tg.st/u/linux-image-5.19.0-rc7-asahi-00002-g174f375813fe_5.19.0-rc7-asahi-00002-g174f375813fe-1_arm64.deb
20:15GlanzmannCan you install that kernel in addition to the one you already have and pick the rc7 in grub?
20:20isoriano has quit [Quit: Leaving]
20:23isoriano has joined #asahi-alt
20:25Glanzmannj`ey: I used the u-boot 'asahi' branch from kettenis, but switched to the asahi branch once I realized that there was keyboard support in.
20:31Glanzmannisoriano: Here is a u-boot without the keyboard support: https://tg.st/u/u-boot-2022-08-16.bin
20:33isoriano has quit [Quit: Leaving]
20:33Glanzmannj`ey: What I don't get is, I'm using the same u-boot/m1n1/kernel as asahi-dev and jannau has tested it. So I wonder what breaks the touchpad. When I was debugging the systemd issue for Linus, I also used that branch under Fedora and the keyboard and touchpad worked. Strange.
20:35isoriano has joined #asahi-alt
20:36GlanzmannI mean good, that it works for you, but shit that somehow the new u-boot breaks the touchpad under Linux.
20:37isorianoLinux m2mbp-debian 5.19.0-rc7-asahi-00002-g174f375813fe #1 SMP Wed Jul 27 10:48:38 CEST 2022 aarch64 GNU/Linux
20:37Glanzmannisoriano: Can you try the latest kernel as well? You can find it here: https://tg.st/u/k.deb
20:39isoriano has quit []
20:41isoriano has joined #asahi-alt
20:41isorianoback for good ... Linux m2mbp-debian 5.19.0-asahi-00002-g84ad91b47c9c #1 SMP Tue Aug 16 18:27:52 CEST 2022 aarch64 GNU/Linux
20:43isorianobtw .. one prob still exists which I did not have with Asahi is that BT is not working as well. Lists the device but cannot connect
20:45GlanzmannOh, okay. I never tried it myself, but there are others that report that it worked at least on m1.
20:47Glanzmannisoriano: Have you tested on Asahi/Alarm also if the u-boot with keyboard and touchpad works?
20:47Glanzmannisoriano: I mean we could test the u-boot that ships with alarm. Let me extract it for you.
20:54Glanzmannisoriano: Can you drop me your email in a msg or via email and than I get back to you once I found the -dev u-boot?
20:55j`eyGlanzmann: https://cdn.asahilinux.org/aarch64/asahi-dev/uboot-asahi-2022.07_rc100.asahi3-1-aarch64.pkg.tar.xz
20:56GlanzmannHere is the m1n1: https://cdn.asahilinux.org/aarch64/asahi-dev/m1n1-1.1.4-1-aarch64.pkg.tar.xz
20:59Glanzmannisoriano: Can you put https://tg.st/u/uboot-dev-2022-08-16.bin into /boot/efi/m1n1/boot.bin and make a backup copy of the old boot.bin just in case?
21:02isoriano has quit [Quit: Leaving]
21:03isoriano has joined #asahi-alt
21:05Glanzmannj`ey: I think he means that the keyboard in u-boot works, but the touchpad in linux does not.
21:06j`eyyes but 'kbd works in uboot .. touchpad does not work' isnt worded the best. im trying to be as clear as possible
21:06Glanzmannjannau: Do you have by any chance a m2 mbp 13" and does the touchpad work for you with the asahi-dev repository?
21:08Glanzmannisoriano: When you boot linux, and the touchpad does not work in linux, does the keyboard work?
21:09GlanzmannBecause I think if it does, that would be strange, because it is the same device, isn't it j`ey?
21:10j`eyGlanzmann: they communicate over different endpoints, so it does seem like they have different 'devices' behind it
21:10isorianoTo be precise. While I can use the kbd in uboot, once Linux boot i cannot use the touchpad but the kbd as usual.
21:12Glanzmannisoriano: Have you still the official asahi installed so that we can rule out Debian as the culprit?
21:15j`eysomewhere in here I guess https://elixir.bootlin.com/linux/latest/source/drivers/gpio/gpiolib-of.c#L306
21:20isorianook. i will leave my email with glanzmann and you can let me know if there is something I can test. Thanks for your support.
21:23GlanzmannBut I could build isoriano a kernel with the asahi kernel config and see if that fixes it.
21:26jannaucould be dtb mismatch regarding rtk-helper, that's in the aahi-dev u-boot but only in the 5.19 release kernel
21:27jannaunot sure what's exactly is tested but asahi-dev u-boot is not compatible with 5.19.0-rc7-asahi
21:35Glanzmannisoriano: Can you try https://tg.st/u/linux-image-5.19.0-asahi+_5.19.0-asahi+-1_arm64.deb ?
21:36Glanzmannjannau / j`ey: The kernels I ship for Debian still have the 4k-iommu patch, maybe that is the culprit somehow.
21:38isoriano has quit [Remote host closed the connection]
21:45isoriano has joined #asahi-alt
21:46isorianoOk. so I could not boot the kernel. It fails just after uboot wit a blinking cursor and then it pops up with error initramfs
21:47isorianoI booted .. Linux m2mbp-debian 5.19.0-asahi-00002-g84ad91b47c9c #1 SMP Tue Aug 16 18:27:52 CEST 2022 aarch64 GNU/Linux
21:49GlanzmannSo now the touchpad works for you. What I don't get is, I thought we have tried that before.
21:50isorianoAnd honestly I am astonished as well! Or did we test uboot-dev with the 5.19rc7 kernel?
21:51GlanzmannBut we at some point tried the very same tree as uboot-dev with the 5.19 which did not work.
21:54isoriano has quit [Quit: Leaving]
21:59isoriano has joined #asahi-alt
22:00isorianoSo it did not work with the latest boot.bin you send (touchpad) and now it is not working anymore with the configuration that was working just before I switched boot.bin
22:00Glanzmannhere it is: https://tg.st/u/linux-image-5.19.0-asahi-00002-gea9c265f2f30_5.19.0-asahi-00002-gea9c265f2f30-1_arm64.deb
22:07isoriano has quit [Quit: Leaving]
22:10isoriano has joined #asahi-alt
22:18jannauthat explains the probe order difference but the isue seems to be that the dockchannel driver can not deal EPROBE_DEFER for the gpios. based on the dockchannel debug mesages the gpios might have to requested earlier so that EPROBE_DEFER can be handled by deferring dockchannel probe as well
22:18Glanzmannisoriano: https://tg.st/u/linux-image-5.19.0-asahi-00002-gbceb3b08f1bc_5.19.0-asahi-00002-gbceb3b08f1bc-1_arm64.deb
22:20isoriano has quit [Remote host closed the connection]
22:22j`eyjannau: https://github.com/AsahiLinux/linux/blob/asahi/drivers/hid/dockchannel-hid/dockchannel-hid.c#L1050
22:23j`eyjannau: looks like https://github.com/AsahiLinux/linux/blob/asahi/drivers/hid/dockchannel-hid/dockchannel-hid.c#L1067
22:23isoriano has joined #asahi-alt
22:23isorianoVoila ... Linux m2mbp-debian 5.19.0-asahi-00002-gbceb3b08f1bc #1 SMP PREEMPT Wed Aug 17 00:16:37 CEST 2022 aarch64 GNU/Linux
22:24j`eymarcan: https://termbin.com/86wv (woops left in the first chunk, but maybe leave it in anyway)
22:26jannaumarcan: there is 'return -PTR_ERR(dchid->dc);' on https://github.com/AsahiLinux/linux/blob/asahi/drivers/hid/dockchannel-hid/dockchannel-hid.c#L1108 looking wrong as well
22:30Glanzmannisoriano: Compiling a kernel with j'eys patch and DOCHCHANNEL options set to =y and see if it fixes your touchpad issue.
22:30Glanzmannisoriano: https://tg.st/u/linux-image-5.19.0-asahi-00003-g32d9ca049454_5.19.0-asahi-00003-g32d9ca049454-1_arm64.deb
22:32isoriano has quit [Remote host closed the connection]
22:33isoriano has joined #asahi-alt
22:42Glanzmannisoriano: https://tg.st/u/linux-image-5.19.0-asahi-00003-g1acfd29fe218_5.19.0-asahi-00003-g1acfd29fe218-1_arm64.deb
22:43isoriano has quit [Remote host closed the connection]
22:47isoriano has joined #asahi-alt
22:48isorianook. BT enabled, but does not connect to the external soundbox. ok, maybe we can check that at a later point in time.
22:55GlanzmannThanks, I'll try to get bt working tomorrow for me and than we talk another time about bt.
22:57isoriano has quit [Quit: Leaving]
23:53psykose has left #asahi-alt [#asahi-alt]