2023-03-25
00:18fortich has quit [Quit: Leaving]
00:27turo has joined #asahi
00:27turo has quit []
01:12Hibyehello has quit [Ping timeout: 480 seconds]
01:29Hibyehello has joined #asahi
01:29derzahl has joined #asahi
01:45Urriellu has joined #asahi
01:45Urriellu has quit []
01:45julio7359 has joined #asahi
01:46Urriellu has joined #asahi
01:46Urriellu has quit []
01:47Urriellu has joined #asahi
01:50brad_ has quit [Ping timeout: 480 seconds]
02:08dorkbutt has joined #asahi
02:10dorkbutt has quit [Max SendQ exceeded]
02:11derzahl has quit [Remote host closed the connection]
02:20Emantor has quit [Quit: ZNC - http://znc.in]
02:20Emantor has joined #asahi
02:21brad_ has joined #asahi
02:34possiblemeatball has joined #asahi
02:42Urriellu has quit [Remote host closed the connection]
03:34brad_ has quit [Ping timeout: 480 seconds]
03:34chadmed has quit [Read error: Connection reset by peer]
03:47psykose has quit [Remote host closed the connection]
03:47psykose has joined #asahi
04:05brad_ has joined #asahi
04:35possiblemeatball has quit [Quit: Quit]
04:36marvin24_ has joined #asahi
04:37possiblemeatball has joined #asahi
04:39possiblemeatball has quit []
04:40marvin24 has quit [Ping timeout: 480 seconds]
04:47Zopolis4 has joined #asahi
04:48chadmed has joined #asahi
05:16bisko has quit [Ping timeout: 480 seconds]
05:18overholts has quit [Quit: overholts]
05:19overholts has joined #asahi
05:25brad_ has quit [Ping timeout: 480 seconds]
05:26akemin_dayo has quit [Ping timeout: 480 seconds]
05:26akemin_dayo has joined #asahi
05:30chadmed has quit [Quit: Konversation terminated!]
05:31chadmed has joined #asahi
05:42blackMysticCat has quit [Ping timeout: 480 seconds]
05:43i509vcb has quit [Quit: Connection closed for inactivity]
05:51isabella has quit [Remote host closed the connection]
05:56thePineapple has joined #asahi
05:57lucenera has quit [Quit: The Lounge - https://thelounge.chat]
05:58lucenera has joined #asahi
06:03thePineapple has left #asahi [WeeChat 3.8]
06:04reillyeon has quit [Quit: The Lounge - https://thelounge.github.io]
06:06reillyeon has joined #asahi
06:08bisko has joined #asahi
06:14ptudor has quit [Ping timeout: 480 seconds]
06:31MichaelLong has quit [Remote host closed the connection]
06:32MichaelLong has joined #asahi
06:41ptudor has joined #asahi
06:52chip_x has joined #asahi
06:54chip_x has quit [Max SendQ exceeded]
06:54chip_x has joined #asahi
06:54chipxxx has quit [Ping timeout: 480 seconds]
07:15pg12 has quit [Quit: pg12]
07:57ptudor has quit [Ping timeout: 480 seconds]
07:57ptudor has joined #asahi
08:05axt has joined #asahi
08:12giskard has joined #asahi
08:38Zopolis4 has quit []
08:39mkurzI think I found another bug (?): I had A LOT of chrome windows and tabs open and also three IntelliJ instances. Suddenly I was not able anymore to open more browser windows or activate any other application windows (like HexChat which had it's windows hidden). In the logs I got "RM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory"
08:39jelly has quit []
08:40mkurzThe strange thing is I cold open more chromium tabs of existing windows but couldn't create new windows. I mean I could see the window in the kde task bar but I couldn't "activate" it, I could see the window border but could not interact with it.
08:43jelly has joined #asahi
08:45mkurz has quit [Quit: Leaving]
09:01pg12 has joined #asahi
09:03mkurz has joined #asahi
09:09mkurz has quit [Quit: Leaving]
09:15mkurz has joined #asahi
09:16mkurz has quit []
09:17mkurz has joined #asahi
09:17c10l has quit [Ping timeout: 480 seconds]
09:19nsklaus has joined #asahi
09:20mkurz has quit []
09:34nsklausif i remember correctly, recently marcan talked about a base distro change for asahi, replacing arch for something else. was there any news about that ?
09:37nsklausi had a 2 or 3 more general questions, one about speaker support, i saw a livestream about marcan trying to tackle it, but i was wondering if that was made available for the general public yet or is it still living only on marcan's personal tree ?
09:38nsklausanother question about the shortcomings of metal and moltenvk compared to vulkan, there's missing functions, like geometry shaders, transform_feedback and little things like that. i was wondering if we were at the point of having asahi trying to fill those gaps yet ?
09:39marcanthe speaker stuff will not be made available to anyone who isn't building their own kernels until it is fully tested and validated on all platforms we intend to enable it on. this is a safety thing and I will *not* be blowing up anyone's speakers.
09:40marcantransform feedback is already implemented in dev trees, other stuff will come in due time
09:41nsklausso there's hope for a full vulkan implementation on asahi, i take it ? if yes then awesome
09:43mpsjannau: few days ago we talked about u-boot and fonts. this one is merged https://lore.kernel.org/u-boot/20230307171649.0ef05dc5@crub/ for next
09:45nsklausmarcan: yes, sorry for the confusion, i meant lina. but both are doing good job on the gpu front
09:46dottedmagnsklaus: that's one of many advantages of talking to hardware instead of talking to metal driver talking to hardware
09:47nsklausdottedmag : i see. makes sense. i hadn't thought of it but now that you mention it, of course linux do not use apple gfx stack.
09:47marcanthere's this pervasive myth that Apple GPUs are "Metal GPUs" or something, which is completely wrong
09:48marcanj`ey_: it definitely talks to hardware, all the command streams are processed by hardware
09:48ChaosPrincessisn the 'metal gpu' meme mostly because they are 1. tilers, 2. lack hardware support to do geometry shaders and need it emulated in sw?
09:49marcanthe meme is just because people make stuff up about apple stuff, along the same lines as "m1s are amazingly only because macos is so optimized for them"
09:50nsklausfor what it's worth, i'm not sure if you followed the nintendo switch emulator ryujinx, they made a release implementing all the missing stuff from moltenvk and it works fast.
09:51marcanevidently you *can* emulate geometry shaders and TF, there's just many ways of doing it and your options are better when you're talking directly to hardware
09:51marcan(apple didn't even try though, their GL runs geometry shaders on the CPU as far as I know)
09:54marcanj`ey_: actually come to think of it, there is *less* firmware on apple than on AMD, as far as what the firmware actually does
09:54marcanAMD has a pile of little blobs running the actual 3D command pipeline on their custom F32 cores, on Apple that's all hardware.
09:55marcanthe firmware on apple GPUs just handles scheduling and submission and preemption etc, not the actual rendering
09:58nyilas has joined #asahi
09:59nsklausi was also wondering about the recent change marcan did about removing mailbox system for underlying infrastructure inter processes communication (if i understand correctly) i was wondering if there was some feedback about it yet ? (if it's available for everyone to try it out ? )
10:00mkurz has joined #asahi
10:00nsklausj`ey_ yes, except for general stability, in relation to race conditions, and missing timeframes things like that, if i understand it correctly
10:02mkurz has quit [Remote host closed the connection]
10:03nsklausif there were problem folks would be discussing it, i take that change went well. seemed pretty deep
10:05Retr0idis it just me or does firefox have some really janky text input behaviour sometimes? I've just tried to send a tweet and a) the cursor keeps disappearing b) the contents of the tweet as-sent were different to the content I saw when I was editing! (it sent a prior version) I still haven't figured out what's triggering it but it seems to be related
10:06chip_x has quit [Ping timeout: 480 seconds]
10:07nsklausbut i remember wondering why i could not really change resolutions, there was just an option on zoom or dpi something something.. not real resolution change. was it just me or there still a limitation on that front ?
10:09mkurz has joined #asahi
10:10nsklausbut, when i tried asahi last time it was maybe two months ago, maybe 3.. and i tested the dev tree for accelerated gfx stack (which was working well)
10:10nsklausi was under the assumption that this dev tree gfx stack was not using the framebuffer either, was i wrong about it ?
10:14nsklausabout the speakers, if i build kernel with speaker support, and i generaly keep volume to a low to mid level at all time (i mean never max up the levels) would that still be considered hazardous ?
10:14ah-just got a reproducible firefox GPU crash, when using mapbox: https://docs.mapbox.com/mapbox-gl-js/example/simple-map/
10:14ah-zoom around a little and you'll get "FWLog: ERROR: PIO poll from agfPollFenderReg timeout after 250us [type:0 reg:0x10080 expected:0x0 got:0x3 max:250us], continue wait"
10:15nsklausmarcan : ok i will not try that then. i don't have enough money to buy a new laptop or pay for expensive repairs
10:15ah-not sure if you're looking for bug reports like this yet, probably it's too early and there's too much known issues too fix
10:17marcanchanging the resolution is supported on desktops/external monitors. changing the resolution of the internal panel is not supported nor does it make any sense.
10:18nsklausmarcan : ah so i remembered right. so things and behavior changed ? we don't change resolution anymore ?
10:19nsklausbut, in terms of bandwidth, usualy, when we use high (fixed) resolution, things are less fast than when we use a lower resolution, is it not ?
10:20marcanyes, which is why games *do* usually let you render at a lower resolution than the display, and that all works perfectly fine on wayland
10:20yuka_ has quit [Remote host closed the connection]
10:20yuka has joined #asahi
10:21nsklausmarcan : ok, i take note: we don't change resolution anymore, and games will be able to make necessary resolution changes to work as they should
10:23marcanapproximately zero laptop panels support changing the resolution, intel/AMD/nvidia drivers just emulate it with internal scaling. there's no reason to emulate that in the driver any more since compositors can configure scaling like that themselves if they really want to.
10:23marcanso if you really want to render your UI at a lower resolution and scale it, in principle nothing stops wayland compositors from offering that option
10:23marcanbut it no longer is the driver's job to pretend a screen that only has one mode can do more modes like other laptops do
10:24marcanremember x86 is a pile of legacy upon legacy upon legacy in all dimensions, and our job here is to not be burdened by that kind of stuff and do things right
10:25nsklausi understand, i'm not fighting it, it's just i didn't know those details. you give proper reasoning on how things actualy work. i was still stuck on these old concept and took them for some sort of general rule that would not change. and it seems i was wrong. thank you for giving the details.
10:25marcanlike literally on Intel you can xrandr switch to an 800x600 mode on a 1080p laptop screen, or xrandr create a virtual 800x600 screen and scale it to 1080p with a 1080p mode selected, and they are the *same thing* as far as I know, at the hardware.
10:28chipxxx has joined #asahi
10:28marcanI think in principle if say $game sets up a 1024x768 framebuffer and wants to present via DCP on Wayland it should be possible for the compositor to configure that surface as the primary plane if all the moving parts work right (not sure if they do)
10:29jannaunot right now, the frembuffers dcp sees are always panel resolution so the scaling has to happen in the gpu
10:30marcanbut I meant that one specifically because DCP and AGX need to agree on the compression format
10:32ChaosPrincessplease do rewrite dcp in rust, i wouldnt mind writing mipi in that and not have to write all the bindings :P
10:33jannauit's not tested in the sense that I haven't seen an application using differently sized src/dest rects
10:36nsklausso, considering i need to refresh my outdated concept on that subject, how would you name that issue you're talking about right now ? if i cannot call it "resolution change" ?
10:38nsklausin case i want to check what's happening on that front later on, how do i even name it ?
10:38jannaumarcan: is it just kwin/kscreen under x11? under wayland it shows jsut the native panel resolution
10:39nsklausjannau : for what it's worth, when i last tested asahi, i tested both x11 and wayland, and had the same issue which i erroneously called "inability to change resolution"
10:42marcanjannau: https://invent.kde.org/plasma/kwin/-/blob/master/src/backends/drm/drm_connector.cpp#L338
10:42nsklausi see .. i have now a 14" macbookpro m2 pro (had an original 13" macbookpro M1 base model before, but i could not stand the touchbar, i had to get rid of the darn thing)
10:42jannauit has an info text next to resolution saying 3024x1890 is the only supported resolution and that changing to an unsupported resolution was possible in the plasmay x11 session
10:43nsklausi have a french azerty keyboard by the way if that's of any interest for testing keymapping issues.. i think i saw a request for feedback on that front recently
10:47nsklauswhere can i get a list of the different models in the same wording as jannau is using ? (was about to ask which model is j493 ;)
10:51j`ey_nsklaus: https://github.com/AsahiLinux/linux/tree/asahi/arch/arm64/boot/dts/apple dont seem to be on the wiki
10:51nsklausi'd still be interested in a proper naming for the issue you folks are discussing. since i was wrong to call it "resolution changes"
10:55nsklausis asahi support for 14" macbookpro "M2 pro" on par with what it was for original 13" macbookpro M1 base models by the way ? can i just proceed with install like i did before with the m1 and all will be working ?
10:58chadmedi managed to get the m2 pro mini to boot headless and tethered but getting pcie and dcp to work is beyond my pay grade so we just sit and wait patiently
10:58jannaulooks like even before 9130b947e02bd9f only the refresh rates saved us from the fake modes on j314/j316. 13" mbp and air would have the fake modes since thay report only a single mode
11:03marcanjannau: AMD also supports scaling (I know because I use it on amdgpu on xorg) so this fake mode business still makes no sense
11:04mohit8 has quit []
11:04mohit8 has joined #asahi
11:05jannauI suppose behavior like kwin might be blamed for that. I just spotted it while looking at the AMD driver and remembered it due to its weirdness
11:14nsklausanyone knows if multitouch support for the trackpad allows replicating macos 3fingers drag behavior ? anyone tested that ? that's one of the thing i grew quite fond of, alongside using cmd+c and cmd+v instead of ctrl+c and ctrl+v, that 3fingers drag feature is neat.. for moving windows around, using 3finger drag on windows border, or for selecting text too, those kind of things
11:17nsklausi was able to make it long time ago using modified libinput, iirc but that was a bit hacky
11:18nsklausfor example: https://www.reddit.com/r/linux/comments/eu6k4x/i_have_patched_libinput_to_provide_3finger_drag/
11:26giskard has quit [Ping timeout: 480 seconds]
11:27nsklausah- thanks for the link, i'll look for it all and tinker with that idea of having 3fingers drag on linux when i'll be able to install asahi again on that laptop. that's a side thing. i just wondered about it. but there's more pressing issues first i guess. priorities makes the order.
11:36axt has quit [Quit: Leaving.]
11:38nsklausi have kept having to try an up to date gentoo desktop experience in the todo list for some time
11:40nsklausi said it before but, last time i tried gentoo, was just before they introduced use flags
11:44Moprius has joined #asahi
11:44nsklausbut yes, using fedora as new base would provide substantial improvements in terms of infrastructure, and people, some big names too, behind the distro releases, in support and all
11:48amarioguy has joined #asahi
11:51Brainium has joined #asahi
12:00MichaelLongchadmed, oh another gentoo user, still some left I see :)
12:00MichaelLonggreat to hear, thanks for your effort!
12:13chipxxx has quit [Ping timeout: 480 seconds]
12:15chipxxx has joined #asahi
12:15chipxxx has quit [Remote host closed the connection]
12:16chipxxx has joined #asahi
12:39thenemesis has joined #asahi
12:44Moprius has quit [Quit: bye]
12:53thenemesis has quit [Ping timeout: 480 seconds]
13:20systwi_ has joined #asahi
13:24systwi has quit [Ping timeout: 480 seconds]
13:50rosefromthedead has joined #asahi
14:22bcrumb has joined #asahi
14:27possiblemeatball has joined #asahi
14:33bcrumb has quit [Quit: WeeChat 3.8]
14:36jacksonchen666 has joined #asahi
15:03Hibyehello has quit [Quit: ZNC 1.8.2 - https://znc.in]
15:03Hibyehello has joined #asahi
15:05sdomi has quit [Ping timeout: 480 seconds]
15:13Brainium has quit [Quit: Konversation terminated!]
15:14sdomi has joined #asahi
15:31linuxgemini13 has joined #asahi
15:36giskard has joined #asahi
15:36linuxgemini1 has quit [Ping timeout: 480 seconds]
16:04brad_ has joined #asahi
16:21winterjannau: did you see my messages wrt the HiDPI issue btw? just curious what the issue is :) thanks again!
16:23brad_ has quit [Quit: Konversation terminated!]
16:32chipxxx has quit [Remote host closed the connection]
16:33jannauwinter: the issue is that the panel dimensions are parsed on startup from the device tree but is overwritten when the display powers down
16:35chipxxx has joined #asahi
16:36chipxxx has quit [Remote host closed the connection]
16:36chipxxx has joined #asahi
16:41tpw_rulesmarcan: i am pretty certain something did change with nvme on the latest kernels which has created an incompatibility
16:44tpw_rulesare you saying that hack is not complete? because if it's in the PKGBUILDs then my kernel does have it
16:47tpw_rulesok we will see. the problem seemed to be hit persistently. do the older kernels hit it less often?
16:54marcanI think the way it works is drivers regiter in initcall order which depends on link order and such, but then the actual probing is parallelized or something since some time ago
17:08winterjannau: interesting, thanks. it looks like an issue isn't filed for this (in the main repo or the edge thread), should i file one so this is tracked?
17:26julio7359 has quit [Read error: Connection reset by peer]
17:32Brainium has joined #asahi
17:37artemist has quit [Ping timeout: 480 seconds]
17:45julio7359 has joined #asahi
17:46possiblemeatball has quit [Quit: Quit]
17:46i509vcb has joined #asahi
17:50jamespmo_ has quit [Ping timeout: 480 seconds]
17:52julio7359 has quit [Remote host closed the connection]
17:56julio7359 has joined #asahi
18:04artemist has joined #asahi
18:17pthariensflame has joined #asahi
18:27pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
18:36Urriellu has joined #asahi
18:38Urriellu has quit []
18:39Urriellu has joined #asahi
18:51Urriellu has quit [Remote host closed the connection]
18:56Urriellu has joined #asahi
18:59pthariensflame has joined #asahi
19:01nyilas has quit [Remote host closed the connection]
19:06pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
19:07Urriellu has quit [Ping timeout: 480 seconds]
19:17Techcable has quit [Ping timeout: 480 seconds]
19:28WindowPa- has joined #asahi
19:31Brainium has quit [Remote host closed the connection]
19:33WindowPain has quit [Ping timeout: 480 seconds]
19:35Techcable has joined #asahi
19:35dax has quit [Quit: dax]
19:50Zopolis4 has joined #asahi
19:59nyilas has joined #asahi
20:08nyilas has quit [Remote host closed the connection]
20:22seb4nihel has quit [Quit: ZNC 1.8.2 - https://znc.in]
20:23seb4nihel has joined #asahi
20:30Brainium has joined #asahi
20:48janrinze has quit [Remote host closed the connection]
21:19seb4nihel has quit [Quit: ZNC 1.8.2 - https://znc.in]
21:21seb4nihel has joined #asahi
21:25Brainium has quit [Quit: Konversation terminated!]
21:27seb4nihel has quit [Quit: ZNC 1.8.2 - https://znc.in]
21:29seb4nihel has joined #asahi
21:40Urriellu has joined #asahi
23:07Retr0id has quit [Read error: Connection reset by peer]
23:15possiblemeatball has joined #asahi
23:29jacksonchen666 has quit [Quit: WeeChat 3.8]
23:42Retr0id has joined #asahi
23:52itsjustdj has joined #asahi
23:57itsjustdj has left #asahi [#asahi]