2023-04-13
00:47zerdox has quit [Remote host closed the connection]
01:42hightower3 has joined #asahi-alt
01:49hightower2 has quit [Ping timeout: 480 seconds]
01:59zerdox has joined #asahi-alt
02:03zerdoxMichaelLong did you encounter `thread 'main' panicked at '"ftrace_branch_data_union_`? I am trying to compile the kernel finally. I found one guy in rust-for-linux zulip chat, he met this error 2 months ago. and i also googled some email from 5 april mentioning my error
02:46zerdoxit doesn't matter if i run genkernel or make LLVM=1. i get thread panicked while compiling kernel
02:50zerdoxhttps://rust-for-linux.zulipchat.com/#narrow/stream/291565-Help/topic/make.20LLVM.3D1.20error
02:58zerdoxnothing interesting in logs actually. i am using default asahi kernel config just with rust enabled. my rustc and bindgen versions are exact required. i am using 16 llvm
02:59chadmed_also just building the config in /proc/config.gz wont enable the gpu or dcp. you need to go and set those options in menuconfig.
03:03zerdoxhow can i see it? i've pinned rustc version as in quick start and then added rust-src component
03:04chadmed_but as a standard user you dont have write perms to /usr/src so ofc its gonna fail writing bindings there
03:06zerdoxi've already set all this up. running make rustavailable as root gives me "rust is available "
03:10chadmed_you should probably just install all of this as root instead of trying to kludge its CARGO_HOME to your local user tbh
03:10chadmed_like i said from the outset it becomes very hard to offer support to people when they start doing weird nonstandard things and stuff starts breaking
03:12chadmed_the fact that its trying to call into bidngen from your own home dir instead of /root/.cargo/ suggests you have not set any of this up properly
03:34zerdoxthere is nothing to install in bindgen because it has no binaries. cargo install is only for installing programs, and can't be used with libraries
03:39zerdoxyay. it's doing something... i will try to login to my user now and continue the work with the newer bindgen. could you please share which settings do i need to change so my gpu would work properly?
03:41chadmed_ you already have dracut installed which has the appropriate firmware and driver hooks set up from the install script, so instead of using genkernel to generate an initramfs use dracut --kver $(make -s kernelrelease)
03:50cylm has joined #asahi-alt
04:50zerdoxchadmed_: ty. i successfully compiled and applied new kernel. but as soon as i boot in, see some linux init logs and login prompt, screen goes black. nomodeset "fixes" it
04:52chadmed_xorg relies on features that are not present in the hardware because its not 100 quadrillion years old
04:53chadmed_your display manager (i assume sddm) probably uses xorg so when openrc goes to start it, it causes issues
04:59possiblemeatball has quit [Quit: Quit]
05:00chadmed_assuming you didnt nuke the old kernel and initramfs grub should still have a boot option for it under advanced settings
05:02chadmed_you can write a little shell function/alias to pipe the output of some command into tpaste
05:04zerdoxmaybe i can also ssh from my phone to the system without nomodeset so you can actually see the errors?
05:08chadmed_well you just need another machine with ssh installed, then just ssh [username]@[mac hostname/ip address]
05:18jamespmo_ has joined #asahi-alt
05:23jamespmorgan has quit [Ping timeout: 480 seconds]
05:39zerdoxfor the context by black i mean i get no backlight. like it's completely off, when you turn down brightness to zero on macos
06:22zerdoxi've installed `light` package and it says 33.33 on apple-panel-lb and 100.00 on gpio-bl. so this is not the case
06:36chadmed_ has quit [Remote host closed the connection]
06:41zerdox has quit [Read error: Connection reset by peer]
06:42zerdox has joined #asahi-alt
07:31cylm has quit [Ping timeout: 480 seconds]
08:02jn has quit [Read error: No route to host]
08:03ktz_ has joined #asahi-alt
08:03jn has joined #asahi-alt
08:06ktz_hello, on the conversation we had on #asahi, I mounted esp on /boot/efi and installed m1n1 and u-boot-asahi, when restarting I've had the exact problem I described when the same thing happened from an alarm update. I can get to boot and get to my DE but everything is incredible sluggish and I can't even use it. I'm currently booted from alarm now
08:07ktz_my problem is that alarm at least didn't entirely replace boot.bin, it was also leaving a boot.bin.old behind which I could replace the new one with and boot back normally, but alpine doesn't do that so I need to find some other way to fix it
08:09ktz_on a positive note I'm getting no errors on dmesg and a different one when trying to start an ap on alarm. keyboard and mousepad are also working as expected
08:14ktz_I'm using alpine mainly, I've got the alarm installation for situations like these just for debugging
08:15ktz_I haven't had any of those problems for months to this point and I've always had both installed
08:17ktz_that's a good question, I assumed its correctly mapped to the corresponding one up to this point
08:30ktz_ has quit [Remote host closed the connection]
08:32ktz has joined #asahi-alt
08:36ktz has quit [Remote host closed the connection]
08:40ktz has joined #asahi-alt
08:40jannaudo you have two entries for alpine and asahi in the macos boot picker you get when you keep the power button pressed?
08:40ktz_ has joined #asahi-alt
08:42jannauthen you should get different values in /proc/device-tree/chosen/asahi,efi-system-partition for alarm and alpine
08:49jannau/proc/device-tree/chosen/asahi,efi-system-partition has PARTUUID not a UUID so it might not be a problem
08:51nsklaus has joined #asahi-alt
08:58jannauyou should be fine if you change "UUID=F7C9-0138" to "PARTUUID=80281940-c4e6-40d8-b83f-f509a98c9338" in fstab
09:00ktz_this is on alarm (nvme0n1p5) shouldn't it point to nvme0n1p4 instead? the one you suggested is nvme0n1p7 instead, alpine's esp
09:03jannau/proc/device-tree/chosen/asahi,efi-system-partition is what m1n1 cares about. if the OS doesn't match it will cause problems. can you verify that it differs between alarm and alpine
09:05ktz_ has quit [Remote host closed the connection]
09:05ktz has quit [Remote host closed the connection]
09:12ktz has joined #asahi-alt
09:16ktz has quit [Remote host closed the connection]
09:20ktz has joined #asahi-alt
09:26zerdox has quit [Ping timeout: 480 seconds]
09:28ktzmps: any idea at least on how to fix my alpine installation? its unusable as of now after adding u-boot-asahi and m1n1 packages and having m1n1 upgraded
09:31mpsktz: no idea for stable solution. you could mount proper ESP and /usr/sbin/update-u-boot-asahi
09:32ktz has quit [Remote host closed the connection]
09:33mpsbut my real advice is 'use alpine only', not because alpine is perfect (it is not) but other distros are worse (sorry if I offend someone)
09:36_jannau_m1n1 does that. the only problems we had where distro packaging unpatched u-boot which doesn't use the slected ESP
09:37ktz has joined #asahi-alt
09:41ktzso the way to fix my issue is having alarm deleted? that won't really bring back the boot.bin version which makes my boot functional in the alpine esp, am I wrong?
09:42ktzthe m1n1 is lastly updated via alpine so even if both use it, it should likely be fine with alpine I suppose
09:44_jannau_a patched u-boot will not help as long as both installs report the same "asahi,efi-system-partition" when selected through the macos boot picker
09:45mpsktz: if you want you can install linux-asahi-edge and mesa-asahi for alpine from my private repo
09:47cylm has joined #asahi-alt
09:47_jannau_ktz: that can not work and probably explains your problems. you have to use the macos boot picker for multi alternative os support
09:53ktzokay, good to know thanks. I'll try mps' edge kernel and hopefully this fixes the issues on my alpine installation
09:54cylm_ has joined #asahi-alt
09:56cylm has quit [Ping timeout: 480 seconds]
10:06mpsktz: add this 'https://www.arvanta.net/mps/aports-local' to /etc/apk/repositories and download https://www.arvanta.net/mps/aports-local/mps%40arvanta.net-5a88c744.rsa.pub and put it to /etc/apk/keys
10:08mpsthough you will need different script which will set m1n1+dtbs+u-boot if you install linux-asahi-edge
10:18mpsmarcan: I ported PKBUILDs for asahi-scripts and asahi-fwextract from asahi to alpine APKBUILD. but I'm not sure what to do with 'Maintainer' field. on one side all credits belongs to you because porting was easy
10:20stipa is now known as Guest10828
10:20stipa has joined #asahi-alt
10:22Guest10828 has quit [Read error: Connection reset by peer]
10:23chadmedmps: i assume the convention is the maintainer of the package, not the maintainer of the code
10:24ktz has quit [Remote host closed the connection]
10:25mpschadmed: I agree, but because PKGBUILD and APKBUILD are nearly same I though it would be polite to ask author (marcan) of these two PKBUILDs
10:27jamespmorgan has joined #asahi-alt
10:28_jannau_I'd sugest to take the maintainership and add a comment that it is based on the asahi PKGBUILD
10:29ktz has joined #asahi-alt
10:29mps_jannau_: this sounds reasonable to me, I thought to do this but again wanted to ask original author
10:33jamespmo_ has quit [Ping timeout: 480 seconds]
10:33ktzits unusable, for instance it takes 2 sec to spawn foot and when you type a letter it registers 3+ times
10:34chadmed has quit [Ping timeout: 480 seconds]
10:34ktzits the same exact issue I had with the last kernel, its not related to the upgraded kernel, its the boot.bin which causes it
10:37chadmed has joined #asahi-alt
10:38psykose has joined #asahi-alt
10:39psykoseyou would need all of the mesa-asahi-* packages as overrides, in that case you are missing mesa-asahi-dri-gallium
10:41ktzyes I see mesa-glapi-23.0.2-r2 aarch64 {mesa} (MIT SGI-B-2.0 BSL-1.0) [installed], let me replace it with the asahi version and I'll try to boot again
10:45ktzalways alpine, I only use alarm when I can't boot into alpine, and when booted on alarm I'm talking alpine chroot so alpine
10:46ktz has quit [Remote host closed the connection]
10:47j`ey__jannau_: you've said before that DCP is slow without the GPU right? So I guess that's what they're seeing
10:49ktz has joined #asahi-alt
10:49_jannau_it slower than software rendering but not 2 seconds to launch foot slow. that could the subotimal kmsro behavior people where seeing on fedora with many kmsro drivers enabled
10:51dottedmag has joined #asahi-alt
10:56ktz has quit [Remote host closed the connection]
10:58ktz has joined #asahi-alt
11:00ktzmps: yes I use an external one but I'm trying to get the builtin one functioning as well so its portable, same for mousepad, not sure whats wrong with them
11:02mpshave no idea, internal keyboard and touchpad works for me from the beginnig (year and a half ago) without problems
11:03ktzby the way is this https://gitlab.alpinelinux.org/alpine/aports/-/issues/14577 akms thing any easy to fix? psykose:
11:04ktzyes its strange, even the other firmware errors are gone from dmesg now... but still no luck. Maybe its something to do with wayland/sway in the end
11:05mpsktz: you could try to install linux-asahi-edge-dev and fix this to use it and then try to build
11:53ktz has quit [Remote host closed the connection]
11:58marcanfeel free to note the origin of the script if you want, though I personally don't particularly care
11:58marcanI don't think we have a license on that repo explicitly, we probably should, but I basically consider everything in there (except for patches subject to upstream licensing) public domain for any distro to adapt as they wish
12:01marcanand linux-asahi and mesa-asahi which will probably live forever as downstream bleeding edge packages if nothing else
12:06jannaualso questionable if they fall at all under copyright (depending on the legislation). not much freedom to express them differently and still have working packages
12:24chadmedinformation should be free (unless it can make me a billion dollars in which case people should pay me a billion dollars for it)
12:24possiblemeatball has joined #asahi-alt
12:49ChaosPrincessdisney or nestle
12:50ChaosPrincessits always one of these two
12:59zerdox has joined #asahi-alt
13:29zerdox has quit [Read error: Connection reset by peer]
14:03j`ey_ is now known as j`ey
14:22zerdox has joined #asahi-alt
15:38possiblemeatball has quit [Quit: Quit]
15:39possiblemeatball has joined #asahi-alt
16:00cylm_ has quit [Quit: WeeChat 3.6]
16:05jn has quit [Remote host closed the connection]
16:06jn has joined #asahi-alt
17:23lawrence8 has joined #asahi-alt
17:29lawrence has quit [Ping timeout: 480 seconds]
17:29lawrence8 is now known as lawrence
17:58possiblemeatball has quit [Quit: Quit]
18:07avi has joined #asahi-alt
18:09avi has quit []
18:42pthariensflame has joined #asahi-alt
19:00pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
19:36possiblemeatball has joined #asahi-alt
21:41nsklaus has quit [Quit: ZZZzzz…]
22:04possiblemeatball has quit [Quit: Quit]
22:49chadmed_ has joined #asahi-alt