#
…

2022-07-27

00:07Brainium has quit [Quit: bye]
00:29bisko has quit [Read error: Connection reset by peer]
00:30bisko has joined #asahi
01:20chadmed_did you recompile the DT and make a new stage 2 m1n1 with it?
01:58probieNot yet. Given that there's a chance to break the speakers I'm trying to get a clear idea of what's involved before attempting anything
02:13probieIs that harmless to do as long as I don't do anything else?
02:15chadmed_ive done the procedure myself quite a few times and ive never busted anything but you must make absolutely certain that your machine will play no audio until youve had a chance to turn the levels down in alsamixer
02:29bisko has quit [Read error: Connection reset by peer]
02:29ciggi has quit [Read error: Connection reset by peer]
02:30ciggi has joined #asahi
02:30bisko has joined #asahi
02:45phiologe has joined #asahi
02:48PhilippvK has quit [Ping timeout: 480 seconds]
02:48jx0 has joined #asahi
02:49jx0 has quit []
02:50jx0 has joined #asahi
02:53zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:53zzywysm has joined #asahi
03:21pyropeter3 has joined #asahi
03:22jx0 has quit [Quit: poof!]
03:23pyropeter2 has quit [Ping timeout: 480 seconds]
03:27marvin24_ has joined #asahi
03:31marvin24 has quit [Ping timeout: 480 seconds]
03:44krirogn[m] has quit [Quit: Client limit exceeded: 20000]
03:46kov has quit [Quit: Coyote finally caught me]
04:10gladiac has quit [Ping timeout: 480 seconds]
04:12falconhash[m]Never depend on a single income to get financial freedom. I can teach you how you can earn from $5,000 to $6,000 weekly,without sending money to me or anyone, but you will pay me 10% commission when you receive your profit. if you are interested, ask me how via Whatsapp
04:12falconhash[m]👇👇👇
04:12falconhash[m]+1 (570) 801-0862
04:24bisko has quit [Read error: Connection reset by peer]
04:25bisko has joined #asahi
04:32falconhash[m] has quit [autokilled: Spambot. Mail support@oftc.net if you think this is in error. (2022-07-27 04:32:45)]
04:52nesnass has joined #asahi
04:58nesnass has quit [Remote host closed the connection]
04:59gladiac has joined #asahi
05:28ciggi_ has joined #asahi
05:28ciggi has quit [Read error: Connection reset by peer]
05:53the_lanetly_052__ has joined #asahi
06:13gladiac is now known as Guest6166
06:13gladiac has joined #asahi
06:19Guest6166 has quit [Ping timeout: 480 seconds]
06:24bisko has quit [Read error: Connection reset by peer]
06:25bisko has joined #asahi
06:30thevar1a- has quit [Ping timeout: 480 seconds]
06:33thevar1able1 has joined #asahi
06:34doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:42Lizard[m] has quit [Quit: Client limit exceeded: 20000]
06:44circularsprojects[m] has joined #asahi
06:45thevar1able1 has quit [Ping timeout: 480 seconds]
06:45ptudor has quit [Quit: Strict-Transport-Security: max-age=48211200; preload]
06:45thevar1able1 has joined #asahi
06:51ptudor has joined #asahi
06:52lucifer178[m] has quit [Quit: Client limit exceeded: 20000]
07:03thevar1a- has joined #asahi
07:05thevar1able1 has quit [Read error: Connection reset by peer]
07:35bngs[m] has quit [Quit: Client limit exceeded: 20000]
07:58mpsanyone have issue that qemu 7 can't use more than 3GB of RAM on macos 12.5
08:04MajorBiscuit has joined #asahi
08:15mazmps: qemu + hvf?
08:16mazdo you have highmem=off on the command line?
08:19mpsmaz: yes, with hvf
08:19bisko has quit [Read error: Connection reset by peer]
08:19mpsI think highmem=off is set
08:19mazthen get rid of it.
08:19mpshave to reboot to macos to check
08:20mpsmaz: thanks will check soon
08:21bisko has joined #asahi
08:22GlanzmannFedora users: I updaed Fedora build with a Fresh kernel, u-boot, m1n1. Testers on m2 welcome. https://thomas.glanzmann.de/fedora/
08:23mazmps: highmem=off was a workaround to deal with some internal qemu nonsense. I fixed it for both KVM and hvf. shout if it doesn't work with 7.0, and ping agraf in the process.
08:24mpsmaz: thanks for info
08:25mpswill report results back
08:27mazfunnily, someone is shouting about the same thing on #qemu. I guess some package must have been updated for macos...
08:31mpsmaz: yes. ncopa asked me on #alpine-infra do I have same issue
08:32mpsbut I don't boot to macos often, about three weeks ago I tested qemu with disk partition and noticed this problem but didn't looked further because it is not so important to me
08:49leitao has joined #asahi
08:51neatsquirrel has quit [Ping timeout: 480 seconds]
08:54mpsmaz: fyi ncopa is alpine linux creator/founder
09:00KonradHoh has joined #asahi
09:02MajorBiscuit has quit [Quit: WeeChat 3.5]
09:03KonradHohHi, I was wondering if anyone with an M2 could help me identify which ARM PAC/Memory Tagging Features are enabled?
09:03KonradHohShould be relatively easy by running inline assembly that prints out the configuration registers
09:08MajorBiscuit has joined #asahi
09:12neatsquirrel has joined #asahi
09:13neatsquirrel has quit []
09:14KonradHohThank you so much!
09:14mpsI'm trying to select new machine to buy, what is better M1pro or M2 for linux (I don't use macos). I don't need much GPU or neural engine
09:16ptudor_ has joined #asahi
09:21ptudor has quit [Ping timeout: 480 seconds]
09:22_jannau_mps: depends on what you want do do with it. 8/2 high perf/efficiency m1 cores are faster than 4/4 m2 cores
09:29mps_jannau_: aha, thanks
09:29mpsI mostly need machine for fast compiling programs
09:30j`ey8/2 with more RAM then. m2 currently only goes up to 24G
09:30leitao has quit [Ping timeout: 480 seconds]
09:31mpsj`ey: what 8/2 means. I don't see anything about this on reseller pages
09:31_jannau_24G should be sufficient for 8 cores, 16G for 10 cores probably not
09:31maz8 fast cores, 2 "slow" cores.
09:32_jannau_mps: 8 high performnce 2 high efficiency cores
09:32maz(they should call them red and blue, really...)
09:33mpsI'm thinking to buy m1pro with 16GB ram
09:33_jannau_mps: I can look for kernel compilation benchmarks comparing m1 max vs m2 tonight
09:34Glanzmannmps: You can see the performance / efficency cores when you go to apple.com, select the product and click on 'technical specification' and scroll down to the cpu.
09:34mps_jannau_: I'm not in hurry and you don't need to waste precious time on this for me (anyway thanks)
09:35_jannau_m1 max and m1 pro should not differ much wrt. cpu performance
09:35mpsGlanzmann: ah, will look. thanks
09:35_jannau_mps: I did the benchmarks already I just need to look up the results
09:35mps_jannau_: ah, ok then
10:09fetsorn[m] has quit [Quit: Client limit exceeded: 20000]
10:20bisko has quit [Read error: Connection reset by peer]
10:21bisko has joined #asahi
10:22the_lanetly_052___ has joined #asahi
10:29the_lanetly_052__ has quit [Ping timeout: 480 seconds]
10:32thevar1a- has quit []
10:32thevar1able1 has joined #asahi
10:51Brainium has joined #asahi
11:50kov has joined #asahi
11:51janrinze has joined #asahi
12:00KonradHoh has quit [Quit: Connection closed]
12:00lockna has quit [Quit: Client limit exceeded: 20000]
12:01janrinzemarcan: the USB3 firmware for the Mac Studio Ultra, is it a lot of work to get that extracted and working with the Asahi Linux kernel?
12:05janrinzeGlanzmann: grub attaches the 'quiet' parameter on the kernel command line i.i.r.c. so you don't see what's happening during boot, right?
12:09Glanzmannjanrinze: Yes, but of course can you change the grub config to remove the parameter. I do it most of the time.
12:09Glanzmannjanrinze: In Debian it is /etc/default/grub
12:10chadmed_janrinze: usb3 isnt working at all on any machine yet. the problem isnt the firmware it's reversing apple's PHY IP block
12:11j`eychadmed_: usb2 doesnt even work on some ports though
12:11chadmed_oh that sucks then lmao
12:11j`eyon the ultra, and on the imac
12:12chadmed_oh the ones on pcie?
12:15bisko has quit [Read error: Connection reset by peer]
12:17bisko has joined #asahi
12:26janrinzeUSB2 works fine on the Ultra
12:27j`eyjanrinze: I thought that not all ports worked?
12:27janrinzeonly the USBA ports don't work
12:28j`eyjanrinze: USB A is the plug, it can also support USB 3
12:28j`eyA B C are the type of connector, 1 2 3 are the type of signals/protocol or whatever
12:28janrinzeUSBA physical ports on the Ultra don't work.......
12:29janrinzeUSBC physical ports on the Ultra all work in USB2 mode
12:32janrinzeOn the mac mini the USBA ports work fine in USB3 mode.
12:33janrinzeThe USBC ports on the mac mini will only do USB2
12:33Brainium has quit [Quit: bye]
12:38janrinzespecifically for the mac mini i got a USBC to USBA converter so that the dock can be used with USB3. This allows me to use the SSD in the dock at full speed.
12:49qyousef has joined #asahi
12:57mazI've been using sven's patches on the Ultra (together with a bunch of u-boot and DT changes) for about 2 months now, and USB3 on the USBC connectors is doing fine. I wish these patches made it upstream.
12:58svenI wish so as well, but the entire ATC thing is too entangled with the thunderbolt mess and I'm not confident enough the DT can stay this way :(
13:00mazfair enough.
13:00janrinzemaz: where to get those patches?
13:01mazI guess that this makes the FW loader for the PCIe USB slightly more urgent that we'd like it.
13:02mazjanrinze: in one of sven's branches on the Asahi repo.
13:02svenI think jannau also has a branch that actually works on 5.19
13:02janrinzemaz: how can i see which branches are sven's?
13:02sventhere's one fix to the phy subsystem I submitted which got un-fixed during a merge conflict
13:03_jannau_but does not include changes for m1 pro/max/ultra
13:04* svenshould finish bluetooth and finally figure out that thunderbolt mess
13:04_jannau_I should send out the refix for that
13:05pyropeter3but those commits are not trivial to rebase on top of the current asahi kernel
13:05svenplease only use these commits if you know what you're doing
13:05sventhey're called WIP and HACK for a reason
13:07_jannau_yes, those have to be redone on top of asahi
13:09janrinzesven: which part do you worry about?
13:10janrinze_jannau_: best rout is to use the PR for testing a.t.m.?
13:10sventhat stuff randomly breaks and/or is not backwards/forwards compatible at some point
13:10sven*sigh*
13:10sveni think i'll actually stop pushing WIP branches
13:10svennothing there is "ready for testing"
13:10svenit's meant for developers
13:11janrinzesven: please don't worry.
13:11qyousef has quit [Ping timeout: 480 seconds]
13:11janrinzeI'm doing kernel stuff on ARM Linux since 1996
13:12svenfair enough, have fun then :)
13:12janrinzeThat's the whole purpose of this excercise isn't it ? ;-)
13:13svenyeah. i've just had a few people without kernel development experience trying to use WIP branches
13:13svenand i'd really like to avoid that
13:13janrinzesven: fair enough.
13:14janrinzemaz: you're running the kernel built from jannau's branch?
13:15janrinzesven: there are very few people with an Ultra so it's probably going to generate useful info on the state of affairs on the Ultra (whatever the outcome may be)
13:16svennot really. that branch isn't ready to be used so any information will become obsolete once I start changing it again
13:16janrinzesven: okay.
13:18_jannau_janrinze: no, pushed that branch just last weekend, not really compatible with using it for 2 months, also that branch works only on m1 (non pro/max/ultra) devices
13:20_jannau_sigh, why didn't use more distinct marketing names for their tablet and laptop/desktop chips
13:20qyousef has joined #asahi
13:21svenjust wait for M2 Ultra Max :D
13:22janrinze_jannau_: the atc-WIP-5.19 branch looks like a set of patches atop ahasi. Are you worried that it won't work with the Ultra?
13:23_jannau_it does not contain the necessary device tree changes for any t600x device
13:23janrinze_jannau_: thanks for the heads-up there. saves me a lot of time.
13:24janrinzesimplest route to take a.t.m. is to test the PR. right?
13:25_jannau_no, that PR is not compatible with with the way the t600x devicetree looks after adding m1 ultra support
13:28mazjanrinze: not really. I cherry-picked what I needed, and hacked the rest myself.
13:29mazplus I'm still running some old 5.18-rc.
13:43Brainium has joined #asahi
13:43Brainium has quit []
13:51janrinzeSpagetti :-) thanks for the pointers and info. The biggest step for most of us will be when GPU support arrives.
13:58janrinzemarcan surely doesn't have the time to do everything himself. Is there some basic overview of who works on what?
13:59maz(this is starting to sound like project management... ;-)
14:01janrinzeLOL.. i've been accused of that before ;-)
14:01svenlet's not introduce any project management. i have to deal with that at $work already ;)
14:02qyousef has quit [Ping timeout: 480 seconds]
14:06Moprius has joined #asahi
14:06neatsquirrel has joined #asahi
14:11bisko has quit [Read error: Connection reset by peer]
14:13bisko has joined #asahi
14:22MajorBiscuit has quit [Ping timeout: 480 seconds]
14:24janrinzesven: how about small incremental changes that will be acceptable upstream to prepare for the USB3 changes?
14:26_jannau_janrinze: from earlier: "the entire ATC thing is too entangled with the thunderbolt mess and I'm not confident enough the DT can stay this way"
14:27janrinzeyeah. complicated.
14:27svenplease don't try to be my manager or project manager or whatever else
14:27sventhanks.
14:27janrinzeoops.. sorry about that.
14:33janrinzeto be honest, compared to a huge amount of SBCs from the past asahi linux is doing a great job. I have far too many paperweights on the shelves that were promised to be useable by their respective manufacturers.. So no complaints here! I'm very grateful for all the work done already by you people!
14:34the_lanetly_052___ has quit [Ping timeout: 480 seconds]
14:45mini0n has joined #asahi
14:52Glanzmann has quit [Quit: leaving]
15:16bocekcombatbow[m]<opticron> "and I fixed the wiki feature..." <- Thank you! I mentioned this and got no reponse
15:21jasper0 has joined #asahi
15:21jasper0 has left #asahi [#asahi]
15:32kettenisGlanzmann: I suspect this is a particular issue with the u-boot usb code not playing well with one of your usb devices
15:33Moprius has quit [Quit: bye]
15:33kettenisscanning the usb bus seems to take a long time for you
15:34kettenisI'm unlikely to look into this unless I run into this issue myself
15:45jluthra has quit [Remote host closed the connection]
15:45jluthra has joined #asahi
15:46qyousef has joined #asahi
15:58doggkruse has joined #asahi
16:08qyousef has quit [Ping timeout: 480 seconds]
16:08bisko has quit [Read error: Connection reset by peer]
16:10MajorBiscuit has joined #asahi
16:12bisko has joined #asahi
16:14doggkruse has quit [Read error: Connection reset by peer]
16:14doggkruse_ has joined #asahi
16:15MajorBiscuit has quit []
16:18zv has quit [Ping timeout: 480 seconds]
16:31qyousef has joined #asahi
16:35bocekcombatbow[m]Honestly, I am very suprised with what is working already. So many things already work! And they work well.
16:35bocekcombatbow[m]*Cries in changable screenbrightness though*
16:36bocekcombatbow[m]Might be daily driving this soon
16:46zv has joined #asahi
16:49ptudor_ is now known as ptudor
17:04MrGigio has joined #asahi
17:14MrGigio91 has joined #asahi
17:15thevar1able1 has quit [Ping timeout: 480 seconds]
17:16MrGigiuz has joined #asahi
17:17MrGigio has quit [Ping timeout: 480 seconds]
17:20bluetail has joined #asahi
17:22bluetailI think I'm in love with Asahilinux
17:22bluetailit runs so well
17:22thevar1able1 has joined #asahi
17:22pimeys[m]is it already good enough to get a macbook air, wipe the macos completely and start working with your favorite distro?
17:22bluetailAlso what the heck. Asahi Lina did a 6h20 stream
17:23MrGigio91 has quit [Ping timeout: 480 seconds]
17:23j`eybluetail: thats a short stream :p
17:23bluetailpimeys[m], depends on what you mean with that. It is certainly not as user friendly as macos. Without Docker I wouldnt love it
17:23pimeys[m]I mean I'm a sway + emacs
17:23pimeys[m]+ firefox guy
17:23qylissyou need macos for firmware updates and things I think
17:23j`eypimeys[m]: it's recommended to keep macOS for now
17:23pimeys[m]using anything else is not really an option for me anymore
17:24bluetailyou cant run asahilinux standalone yet
17:24pimeys[m]mm, so I'll wait a few years then :)
17:24bluetailPerhaps you could but you shouldnt
17:24bluetailI just discovered Asahilina wears the LGBT thingy
17:24pimeys[m]I want the hardware but none of the apple software
17:26bluetailunderstandable
17:27pimeys[m]what would also be really awesome is linux base and macos virtual machines, then we could virtualize much more easily some CI builds
17:27mpspimeys[m]: I run linux on m1 from november as daily driver
17:27bluetailpimeys[m], I dont think thats impossible.
17:27mpsrarely boot to macos, for upgrades, setting brightness
17:28bluetailpimeys[m], theres ONE dealbreaker as of why I wouldnt want to use a m1 device as main rig
17:28pimeys[m]we have a pile of mac studios in the office, we'd like to use them to speed up some github actions, but making them to act as servers with macos is just so much pain
17:28mpspimeys[m]: so it is quite good
17:28bluetailIt's the actual I/O performance
17:28pimeys[m]yeah the SSD trick they do
17:28pimeys[m]I read about that
17:28bluetailcall me weird but I still believe the image is different...
17:28thevar1a- has joined #asahi
17:28bluetailI could reproduce that weird difference on windows tho
17:29bluetailwhat did I do? Add 4 monitors, then one would look as awkward as on the m1
17:29bluetailIt seems that if a certain bandwidth is taken, the display is altered. I know that occams razor stuff...
17:29bluetailIt's just that I'm so sensitive
17:30MrGigiuz has quit [Ping timeout: 480 seconds]
17:30bluetailall of that was solved by... shorter cables, less active monitors and thats it
17:30bluetailat least for the PC
17:30thevar1able1 has quit [Ping timeout: 480 seconds]
17:30bluetailI didnt solve it for m1 -> monitor. Perhaps its just one peripheral of mine causing it to look different.
17:30pimeys[m]it's not that I miss some CPU power currently, having a 3950x and 5950x and they are fast, the 5950x in the office uses exactly the same amount of time to compile our big rust project than the mac studio with 20 cores
17:31bluetailI use a 5800x3d+6950xt
17:34bisko has quit [Ping timeout: 480 seconds]
17:37MrGigio has joined #asahi
17:37thevar1a- has quit [Ping timeout: 480 seconds]
17:37ptudor_ has joined #asahi
17:39thevar1able1 has joined #asahi
17:39artemist has quit [Read error: Connection reset by peer]
17:42ptudor has quit [Ping timeout: 480 seconds]
17:45MrGigio91 has joined #asahi
17:48Glanzmann has joined #asahi
17:49MrGigio has quit [Ping timeout: 480 seconds]
17:49Glanzmannkettenis: I'll try if I can reproduce it with another usb stick and let you know.
17:50thevar1able1 has quit [Ping timeout: 480 seconds]
17:52bluetail has quit [Quit: Leaving]
17:56thevar1able1 has joined #asahi
17:57MrGigio has joined #asahi
18:03MrGigio91 has quit [Ping timeout: 480 seconds]
18:10thevar1able1 has quit []
18:10thevar1able1 has joined #asahi
18:19artemist has joined #asahi
18:27chir4gm has quit []
18:27chir4gm has joined #asahi
18:39___nick___ has joined #asahi
18:39___nick___ has quit []
18:39GlanzmannLeif, Linus and I try to get Fedora running on m2 air. What is strange is, on a m1 the software does not crash (asahi branch), but on the m2 xorg does not start. Any idea what the issue is? I'm currently reproducing the issue on a friends m2 air laptop who has installed fedora and I'm remotely logged in using ssh.
18:39GlanzmannSo kernel boots, wifi works. xorg does not start (on m1 it does with the very same binary).
18:41___nick___ has joined #asahi
18:42j`eyGlanzmann: can you try fedora 36?
18:42GlanzmannThis is on fedora 36.
18:43GlanzmannSo I have updated my fedora build with asahi upstream tree and u-boot/m1n1 and it is currently runnong m2 air of a friend. I'm logged on to that system using a reverse ssh tunnel.
18:44GlanzmannI have this very same fedora running on m1 mini without any issues whatsoever.
18:44j`eyGlanzmann: your webpage, and the log sayd fedora 35
18:44j`ey"I downloaded Fedora-Workstation-35-1.2.aarch64.raw.xz"
18:44GlanzmannOh sorry, I mean fedora 35.
18:44Glanzmannj`ey: Can I upgrade Fedora 35 to Fedora 36 without reinstalling or do I have to reinstall?
18:45j`eyno idea, dont use fedora, just remember reading about ^
18:51jannaumaybe libunwind but that should affect m1 as well
18:51Glanzmannjannau: Exactly, we thought that at first, too.
18:51GlanzmannBut I think I found the issue.
18:52jannaumaybe the trackpad due to not loaded firmware?
18:52GlanzmannMight be the issue, that on the m2 it loads efifb instead of simplefb? https://tg.st/u/bla2.txt
18:54Glanzmannjannau: Full dmesg of the m2 air is here: /dev/input/mice is there.
18:57jannauGlanzmann: possibly efifb but I do not understand why that only happens on m2
18:57mpsGlanzmann: try alpine :)
18:57GlanzmannNeither do I, but I had the issue before.
19:00kettenisbut even efifb should just work...
19:01GlanzmannNope, I had this issue before, I don't remeber the details, but x was not working for me. I spent several days finding out why ...
19:01jannauefifb might not work due to r10b10g10x2
19:01GlanzmannExactly, thanks.
19:02GlanzmannThat was it.
19:04m6wiq has quit [Quit: ZNC - https://znc.in]
19:05jannauasahi kernel has efifb disabled
19:05GlanzmannOkay, than we might have multiple issues. I used my kernel config, but Linus installed Lifes Fedora which used the asahi kernel config and he has also issues.
19:06m6wiq has joined #asahi
19:06kettenisdon't immediately see why efifb wouldn't work with r10b10g10x2
19:07ketteniswould be good if someone could check it isn't an issue with u-boot
19:07jannauthe xorg modeset driver has issues r10b10g10x2
19:07mpshm, I have CONFIG_FB_EFI=y for alpine kernel
19:07GlanzmannSo, I blacklisted the efifb module, but still have issues.
19:08mpsbut I don't have M2
19:08Glanzmannmps: If simpledrm initialized the fb before efifb does, than you don't have issues.
19:11mpsGlanzmann: `dmesg | grep "efifb\|simpledrm"` => https://tpaste.us/5k1B
19:11riker77 has quit [Quit: Quitting IRC - gone for good...]
19:12Glanzmannmps: [ 0.456691] efi-framebuffer efi-framebuffer.0: efifb: a framebuffer is already registered
19:12mpsthat is on M1
19:12GlanzmannTHat is also on m1.
19:13mpshm, iirc with 5.18 I couldn't switch from X to console without enabling efifb
19:14mpsbecause this i enabled it
19:15___nick___ has quit [Ping timeout: 480 seconds]
19:22jannauGlanzmann: reproduced, Xorg dies with SIGILL. maybe an issue with a new CPU instruction extension
19:23riker77 has joined #asahi
19:25Glanzmannjannau: I see, how did you reproduce it?
19:26Glanzmannjannau: I tried blackilisting efifb, did not help, than I tried to force fbdev that starts x but not cpu output.
19:26Glanzmanns/cpu/monitor output/
19:28jannauinstalling fedora on the m2 macbook pro
19:29j`eygdb it? should tell you if it's a weird instruction, but not sure what that would be..
19:29GlanzmannI see, cool. ;-)
19:31jannauit fails on the very unusual "stp x1, x0 [sp, #-16]!"
19:31thevar1a- has joined #asahi
19:33thevar1able1 has quit [Ping timeout: 480 seconds]
19:35svenunusual?
19:35jannauthat was sarcastic
19:35sventhat makes much more sense
19:36jannaumight be an issue with pointer authentication
19:37svenoh, because it’s the first instruction of some function it just jumped to?
19:38jannauand gdb shows that the modesetting driver uses pointer authentication but libGL doesn't
19:38svenlooks like SIGILL is triggered on pac failure in userspace
19:39jannaumodesetting driver tries to use glamor
19:40j`eym1 has PAC too.. doesnt it?
19:40fny[m] has left #asahi [#asahi]
19:40jannauI thought so too
19:41svenpretty sure it does :/
19:43GlanzmannTried Debian live on m2, xorg works.
19:43j`eyjannau: try 'arm64.nopauth' on the command line
19:43j`ey*kernel command line
19:43j`ey(if you want..)
19:43jannauthanks, I was looking for that
19:44j`eyf8da5752fd1b25f1ecf78a79013e2dfd2b860589 added it
19:45jannaugah, no keyboard in grub
19:46j`eynot even usb?
19:47Glanzmannusb keyboard works in grub.
19:48Glanzmannjannau: grubby --update-kernel=ALL --args="video=efifb:off"
19:48jannauI had to fetch/connect it it
19:48GlanzmannThan reboot, to put the kernel command line ...
19:49Glanzmannbut of course with: grubby --update-kernel=ALL --args="arm64.nopauth"
19:51LaurentiuCosma[m] has quit [Quit: Client limit exceeded: 20000]
19:53jannauit was not pauth, same crash but no more PAC in the backtrace
19:53Glanzmannjannau: We also tried it, also doesn't work for us.
19:54j`eysven: btw the first instruction thing would be BTI, not PAC
19:55svenoh, true
19:56j`ey(which m2 does have!)
19:58GlanzmannI try the 4k patch and let you know the results. Takes a lot of time, because I need to compile it.
20:02thevar1able1 has joined #asahi
20:02thevar1a- has quit []
20:04joske has joined #asahi
20:04joske has quit []
20:05MrGigio has quit [Read error: Connection reset by peer]
20:21mini0n has quit [Read error: Connection reset by peer]
20:25jannauwith glamor disabled (https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU) Xorg starts but I get a "oh no! something has gone wrong" screen
20:28svenI’m still confused about the SIGILL on that stp
20:29jannaugnome-shell segfaults now in mesa
20:30j`eytry arm64.nobti too?
20:30j`eylooks like that also ends up with SIGILL do_bti() arch/arm64/kernel/traps.c
20:31jannaume, only thing which looked fishy to me is that prvious frame made the call via 'blr x1' but x1 was not anywhere near pc
20:35jannau'arm64.nobti arm64.nopauth' in the kernel command line works
20:36svenmaybe this is finally a good excuse to actually understand how this pointer authentication business works
20:37j`eyjannau: just to confirm.. remove nopauth?
20:37svenso far my extremely superficial understanding has been enough
20:37Glanzmannjannau: Trying to reproduce.
20:38Glanzmannjannau: Did you also disable 'glamor'?
20:38Glanzmannbtw. kernel with 4k-iommu patch did not work, but that was probably be expected.
20:38Glanzmannjannau: You fixed it.
20:38GlanzmannIt works for us.
20:39qyousef has quit [Quit: WeeChat 2.8]
20:41jannauj`ey fixed it
20:41GlanzmannDebian users: m2 work out of the box. Fedora users: grubby --update-kernel=ALL 'arm64.nobti arm64.nopauth'
20:41j`eyjannau: and did you reenable glamour? (whatever that is!)
20:41sventhis also sounds more like a workaround than a fix
20:42j`eybut cool, it's a BTI issue then
20:42Glanzmannjannau: Works without disabling glamour.
20:42j`eyGlanzmann: ok
20:42j`eysven: yes definitely, but at least they can continue!
20:43sveni just don’t like calling something a fix when we don’t even truly understand the root cause yet
20:43j`eyah right yeah
20:44jannauGlanzmann: arm64.nopauth is not necessary
20:44GlanzmannOkay, I'll update my documentation. Thanks.
20:44jannaunot is disabling glamor
20:44kettenisso fedora is shipping xorg compiled with bti/pauth enabled but mesa with bti/pauth disabled?
20:44kettenisthat is just broken
20:45jannaupauth seems to be there, I saw a pac* instruction in mesa
20:47Lucy[m]1 has quit [Quit: Client limit exceeded: 20000]
20:51Glanzmannjannau / j`ey: Thank you for finding the workaround.
20:52j`eyif it helps linus just merge asahi right away.. :P
20:53akira128 has joined #asahi
20:54akira128 has quit []
20:54GlanzmannNo more upstreaming issues, upstream will upstream itself or shame that it is not already upstreamed will upstream it.
20:54GlanzmannNow I have to read up on what BTI is about.
20:54leif has joined #asahi
20:55GlanzmannHey there.
20:55leifgreat work guys!
20:55j`eybranch target identification, to help kickstart your reading
20:55Glanzmannj`ey: THanks.
21:02jannaushouldn't bti be reported in cpuinfo's flags on a BTI enabled kernel. it doesn't on m1 or m2
21:04lemonsus[m] has quit [Quit: Client limit exceeded: 20000]
21:06j`eyjannau: it should, that's weird
21:06j`ey(if you mean /proc/cpuinfo)
21:06j`eyit was in Glanzman's dmesg "[ 0.000000] CPU features: detected: Branch Target Identification
21:08jannauwith arm64.nobti it's of course missing. if m1 doesn't has it that would at least explain why m1 machines where working
21:09leifahhh...so that's why it affects the m2 and not the m1?
21:10j`eyjannau: oh heh
21:10Glanzmannjannau: Yep, I can't find it in my dmesg on m1 systems.
21:10jannauyes, but I was under the impression that m1 has it
21:10Glanzmannleif: Yep, it appears to be. And xorg is horrible broken on fedora.
21:10Glanzmannand maybe in general.
21:10jannaunothing to do with xorg
21:10GlanzmannBut Debian started xorg on m2 without any issue.
21:11jannaudebian doesn't use BTI
21:11jannaubti is reported in /proc/cpuinfo if I don't disable it
21:11Glanzmannjannau: So BTI must be compiled in the binary. But xorg jumps somewhere it should branch, doesn't it?
21:11Glanzmannjannau: Ah.
21:12jannauthe issue is in mesa and not in xorg
21:13GlanzmannThere is another feature which only m2 has: +CPU features: detected: Enhanced Counter Virtualization
21:14kettenisunlikely to be relevant
21:14GlanzmannJust mentioning, while I was diffing the cpu features of m1 and m2.
21:14j`eyjannau: the question is, if it's a build bug.. or an actual bug in mesa
21:14j`eybut im not sure if that's the right package
21:20jannauhttps://kojipkgs.fedoraproject.org/packages/mesa/22.1.4/2.fc36/data/logs/aarch64/build.log should be correct package which has -mbranch-protection=standard as well
21:21j`eyok thanks, I used https://packages.fedoraproject.org/search?query=mesa but it didnt show that one
21:37GlanzmannTime to hit bed. jannau/j'ey thanks again for getting to the bottom of this.
21:38j`eynot the bottom yet!
21:42GlanzmannThat is true, but enough to onboard upstream. And now that we know what triggers it, easier to isolate and fix. I'm eager to hear the end of the story.
21:44GlanzmannOh my god, I sent upstream an incorrect workaround. Shame on me. Time to hit bed.
21:48jannauare there already other CPU cores with bti? should be every armv8.5 or armv9 core, I guess nobody is running fedora on cortex-x2/a710/a510 phones
21:49GlanzmannProbably not.
21:49j`eycould test with QEMU
21:49Glanzmannjannau: One last question, before I go sleeping. My friend with the m2 air tried to do a right click but was unable to do so. Have you managed on a m2 device to do a right-click (two fingers) or middle-click (three fingers). We connected an external usb mouse as workaround.
21:50Glanzmannleif: Did you see that I screwed up the command line?
21:53qyousef has joined #asahi
21:53jannauGlanzmann: should work in the same way as on m1 can be configred through libinput
21:53Glanzmannjannau: This was on Debian testing with m2 air and a 4k-iommu kernel. x worked. We used a minimal environment: apt-get install lightdm blackbox xterm firefox-esr big-cursor; startx
21:54leif has quit [Quit: Leaving]
21:54Glanzmannjannau: I see, let me check on m1 air using the same setup if right click works for me, but I already know the answer because I use all the time, but will double check.
21:56jannaudefault in gnome/fedora seems to be 2 finger click == right mouse button
21:56GlanzmannWe tried two and three finders. and shift-click no dice. But that was on Debian, not fedora.
21:58jannaualternative behaviour is click on the right half of the touchpad is right button
22:00GlanzmannI see. Will try it on Saturday.
22:00mpsI switched to mtrack from libinput
22:02Glanzmannjannau: Just tested with the exact same config on the m1, there the right-click works. On the m2 it did not. Will verify myself once I'm in front of the machine on Saturday.
22:02GlanzmannMy friends lives in Stuttgart, I'm in Nuremberg. So we did a phone and reverse tunnel ssh session ...
22:02GlanzmannEveryone sleep well and have sweet dreams.
22:03mpsGlanzmann: you too
22:16qyousef has quit [Quit: Updating details, brb]
22:16qyousef has joined #asahi
…