#
…

2022-11-20

00:59capta1nt0ad has joined #asahi-gpu
01:16jlco has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
02:00Dcow has joined #asahi-gpu
02:40capta1nt0ad has quit [Quit: Konversation terminated!]
02:50user982492 has joined #asahi-gpu
03:48capta1nt0ad has joined #asahi-gpu
05:54bluetailAssuming this belongs in GPU since I have not found it in my monitors EDID: Is temporal dithering a feature of the GPU one can turn on or off? If so, is it something that can be achieved with relatively low effort? If it is not possible, are there other options possible, such as limiting the range of colors by software?
06:54capta1nt0ad has quit [Remote host closed the connection]
07:05marcanbluetail: We've already talked about this. Dithering is a feature of monitors themselves, there is no way to control it from software. Given the same signal timings and colorspace settings, monitors will react identically regardless of what device is on the other side.
07:14yukaalyssa: feel free to use those screenshots
07:15yukaIf you want you can also tag @yuka@fedi.yuka.dev
07:19bluetailmarcan I ask since I was able to disable dithering on my other nvidia machine and it affected the display output in the way that was required
07:19bluetailthe other system I talk about has a nvidia card...
07:20marcanbluetail: laptop or desktop?
07:22bluetailI even found somebody else on #sway the other day that fixed his issue on a TN panel disabling temporal dithering. And I found a screenshot of somebody else this year that uses the option. https://forum.manjaro.org/uploads/default/original/3X/9/3/937268fb73fe05b48a508454b6b9b1fd488c015d.jpeg
07:23bluetail( I did recommend to search in the nvidia settings to disable temporal dithering, fixing the same issue
07:26marcanThat looks like a workaround for crappy monitors
07:26marcanThe GPU is *not* supposed to be doing 6-bit dithering except on some embedded panels
07:27marcanI'm not aware that Macs do that, they shouldn't, it doesn't make any sense
07:27marcanit's the monitor's job to dither 8-bit or 10-bit input appropriately for its panel
07:29bluetailI see. So I can state two things now: 1. I am only happy with "crappy" displays 2. I am having difficulties with 'good' displays often times and fail to set them to behave like the 'crappy' ones. 3. I am particularly unhappy with apple style displays, assuming PWM flicker to be the cause.
07:30bluetails/two/three
07:31user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:31bluetailI guess it makes no sense to further discuss my issue, because its pretty niche
07:32bluetailI just brought it up because the other day I could fix somebody with the same issue
07:32marcanIf you don't want the flickering, get a true 8-bit IPS panel. 6-bit panels will always have dithering or banding, depending on whether you can find a way to turn the built-in dithering off or have to rely on GPU dithering.
07:39marcanbluetail: Apple tends to use high quality displays these days. I am not detecting any flicker, PWM nor temporal dithering, nor any banding, on my M1 Air, with my phone recording in slow-mo mode.
07:42bluetailmarcan what difference does a 'new tech' apple display and a EIZO EV2785 have? I can adjust brightness downwards on the EIZO and do not see 'flies' or get headache. And they are less reflective. I only wished the EIZO's were truly matte! I tried different brands and they appeared to be similar to apple. As much as I like the discussion, I'd like to
07:42bluetailvisit a eye specialist. But to my dismay, they do NOT provide any support.
07:52bluetailI have no knowledge about the newer apple displays. But what I can say my issues do not apply to smartphones and tablets. I do not know any of the reasons.
07:53marcanbluetail: That is an 8-bit IPS panel, which is the same technology apple uses
07:53marcansmartphones and tablets also tend to use IPS displays
07:54bluetailSo the >only< difference might be the coating and the maximal amount of nits?
07:54bluetailOr is there difference in backlighting as well?
07:55marcanthey both use LEDs, how those leds are driven varies. monitors don't exactly list that in their spec sheet.
07:55marcanas I said, I am not detecting any PWM flicker on this one with a phone in high speed mode. I can try with my Blackmagic.
07:55bluetailthe PWM flicker was meant for older apple-tech. I cannot either on the newer ones
07:55bluetailI'm sorry I was being unclear
07:56marcanthen what's your concern with the backlight?
07:59bluetailIts that if I turn down brightness to 60% on the EV2785 that I can still see everything and do not see flies on a white background. I do the same things on a macbook pro 2016 or a imac 2019, I see flies. I visited the eye specialist, said everything okay. I asked him if he has some explanation about why I am so sensitive to light and particular see
07:59bluetailflies if I look into newer apple displays... Or even slightly into the sun. And they did not provide an answer or a solution. I tried some glasses and it didnt help. The only thing that seems to work are 'some' monitors. This seems to be a medical issue, yes.
08:00marcandid you compare the EV2785 and the Apple displays side by side in the same setting?
08:00marcandisplaying the same image, like a white background with the white balance adjusted similarly?
08:01bluetailYes. I set it to 5000K. The issue got worse the more 'cold' the whitepoint was
08:02marcanthat sounds like you might be more sensitive to certain wavelengths
08:02marcanthe Eizo only has sRGB color gamut. Apple displays have significantly more.
08:02marcanthat means they need to use more saturated primaries
08:03marcanit sounds like that might be causing a problem for you, at the wavelength level (not the color mix level)
08:03bluetailJust remembered: I used the sRGB profile on the EIZO because I preffered it
08:03bluetailThank you for your thorough explanation, I appreciate it!
08:05marcanthe Eizo claims 98% sRGB and 75% Adobe RGB. Modern Apple displays are more like ~100% sRGB and 94% Adobe RGB.
08:06marcanthis is just conjecture, but it's the only steady-state difference in output that I think you'd get in a plain white image, once you eliminate the backlight modulation as a factor.
08:07marcanbluetail: have you tried Night Mode type stuff to reduce the blues? does that help?
08:08marcanyou might also find blue-cut glasses to be an improvement, if blue is the problem (although green purity is where most of the color gamut difference is, blue is more physiologically relevant)
08:09bluetailIt does help yes. I might have tried the wrong glasses before. I will try some more.
08:32SSJ_GZ has joined #asahi-gpu
08:56yukanot a complaint, just an info for other people who want to try things: running chromium or minecraft xwayland quickly crashes the compositor, while running as native wayland client usually works fine
08:57yukabut maybe this is specific to the nixos setup I have here
09:00capta1nt0ad has joined #asahi-gpu
09:12capta1nt0ad has quit [Remote host closed the connection]
09:16capta1nt0ad has joined #asahi-gpu
09:19jannauI would in genral recommend to use wayland with dcp/appledrm since it's 1) much closer to how macOS uses it 2) better tested
09:19jannauthis seems to be unrelated though
09:39kode54is this with gpu tree?
09:39kode54I assume that junky frame rate is software rendered
10:11thepigguy has joined #asahi-gpu
10:56yukaminecraft 1.19 runs too 🎉
10:57bluetail has quit [Ping timeout: 480 seconds]
10:58bluetail has joined #asahi-gpu
11:01chadmed has quit [Ping timeout: 480 seconds]
11:44thepigguy has quit [Quit: thepigguy]
11:50Dcow has quit []
11:53jlco has joined #asahi-gpu
13:40Dcow has joined #asahi-gpu
14:01Dcow has quit [Remote host closed the connection]
14:26ah- has joined #asahi-gpu
14:33fallenchromium has joined #asahi-gpu
14:37bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:37bisko has joined #asahi-gpu
14:48bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:01bisko has joined #asahi-gpu
15:08Dcow has joined #asahi-gpu
15:09Dcowcould someone share .config from kernel with DRM_ASAHI?
15:09DcowI want kernel closest to -edge + GPU
15:12bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:14ah-I'd love that too, just managed to build a kernel on gpu/rust-wip with DRM_ASAHI=y but even though the gpu is in the device tree it doesn't seem to probe
15:17Dcowyou also need to update m1n1.bin with dtbs
15:18DcowI've done that and been able to boot kernel with GPU, but only without initramfs
15:18ah-yep, I'm using m1n1 from lina/gpu-wip
15:19ah-and "dtc -I fs /sys/firmware/devicetree/base" shows the gpu node, but I can't find anything related to it in dmesg
15:19bisko has joined #asahi-gpu
15:23Dcowall is built-in?
15:32gustav8 has joined #asahi-gpu
15:34simon_ has joined #asahi-gpu
15:43Dcow has quit [Remote host closed the connection]
15:46simon_ is now known as NewNickname
15:46NewNickname is now known as siontx
15:50Dcow has joined #asahi-gpu
15:51Dcownope. stuck on initramfs also with this (almost) config
15:51DcowI just enabled modules + changed default governor to performance
15:51Dcowsudo mkinitcpio -k 6.1.0-rc5-asahi-GPU+ -g /boot/initramfs-linux-asahi-gpu.img
15:52Dcowis it correct way to create initramfs in asahi?
15:52DcowI guess my initramfs is pain point with all configs
16:36Dcow has quit [Remote host closed the connection]
16:41ah-oh, my issue was that I had outdated rust installed so it didn't actually build DRM_ASAHI
16:41ah-now I have a kernel that gets all the way to "asahi 406400000.gpu: MMU: Kernel page tables created" \o/
16:42Dcow has joined #asahi-gpu
16:44Dcowah: do you use initramfs?
16:46ah-yes, but now i don't seem to get any display/fb output. just retrying with DRM_APPLE=y rather than m
16:48Dcowhow are you making initramfs?
16:48DcowIt feels like I am doing something stupid with it
16:53Dcow has quit [Remote host closed the connection]
17:01siontx has quit [Remote host closed the connection]
17:12siontx has joined #asahi-gpu
17:20siontx has quit [Ping timeout: 480 seconds]
18:05siontx has joined #asahi-gpu
18:13siontx has quit [Ping timeout: 480 seconds]
18:16fallenchromium has quit [Ping timeout: 480 seconds]
18:35Glanzmann has joined #asahi-gpu
18:36GlanzmannHello; I tried alyssa config and the kernel boots for me, dmesg: https://pbot.rmdir.de/-RvC3QV8fLgn3sIExVthZw however, xorg does not with: https://pbot.rmdir.de/zIUNVLMMak0x9QK8VBY1aw does someone have a tip for me how to get it running?
18:41bisko has quit [Read error: Connection reset by peer]
18:42bisko has joined #asahi-gpu
19:01siontx has joined #asahi-gpu
19:04ah-oh interesting, so my kernel halfway boots, but the last log line with any reference to asahi/gpu is "asahi 406400000.gpu: MMU: Kernel page tables created", it then just continues with "nvme-apple 393cc0000.nvme: RTKit: Initializing (protocol version 12)"
19:09ah-on a j316c
19:58fallenchromium has joined #asahi-gpu
20:16jlco has quit [Ping timeout: 480 seconds]
20:16jlco has joined #asahi-gpu
20:29Glanzmann has quit [Quit: n8]
20:45gustav8 has quit [Quit: Quit]
20:48fallenchromium1 has joined #asahi-gpu
20:48fallenchromium has quit [Read error: Connection reset by peer]
20:52fallenchromium2 has joined #asahi-gpu
20:58erik3424 has quit [Quit: erik3424]
20:59fallenchromium1 has quit [Ping timeout: 480 seconds]
21:18amarioguy2 has joined #asahi-gpu
21:18amarioguy2 has quit [Remote host closed the connection]
21:18bisko has quit [Read error: Connection reset by peer]
21:19bisko has joined #asahi-gpu
21:31user982492 has joined #asahi-gpu
21:34siontx has quit []
21:43Dcow has joined #asahi-gpu
21:52ah-hmm, as far as I can tell it gets stuck in the inner UAT handoff init, probably the magic? maybe the FW doesn't run as expected or it's reading from the wrong address?
21:54yukaVery weirdly what made the difference for getting the gpu-enabled kernel to boot was loglevel
21:55yukanixos sets loglevel=4 by default and just changing that to loglevel=7 seemingly fixed the boot
22:00ah-yuka: !!! i can confirm, mine boots as well with loglevel=7
22:01ah-the m1n1 handoff impl mentions barriers, maybe it's missing some?
22:04fallenchromium2 has quit [Quit: WeeChat 3.7.1]
22:19alyssaoh man, I thought I just screwed up building my kernel
22:19alyssayeah, mine only boots in verbose with that config ...
22:19alyssalina: am I doing a stupid?
22:38user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:51Dcow__ has joined #asahi-gpu
22:53Dcow has quit [Quit: dcow]
22:56SSJ_GZ has quit [Ping timeout: 480 seconds]
23:00ah-omg it works :O
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:12alyssanew policy-- i will not be taking bug reports except for bisected regressions
23:12alyssai don't even know if i'm joking about that or not
23:39alyssaBO cache: 29565184 KiB (+16 KiB from Executable)
23:39alyssasorry what
23:39alyssathe BO cache is.... 28 gigabytes large?! somehow I doubt that
23:44alyssacd.cd BO cache: 1506688 KiB (+32 KiB from Resource)
23:44alyssaok that is more preasonable
23:44alyssabut still, 1.4 GiB in the cache?! that seems massive
23:46chadmed has joined #asahi-gpu
23:49unko has joined #asahi-gpu
23:53alyssaBO cache: 1077536 KiB (+256 KiB from Pool, hit/miss 880759/14693)
23:54alyssaso the hit/miss ratio is excellent, actually
23:55alyssa98% hit rate. Not worried about that.
23:55alyssaI am worried about a literal gigabyte of unused memory hanging around
23:55alyssalots of little allocations from the pools
23:56alyssabut also some big ones too?
23:56alyssafrom reosurces getting created/destroyed? hum
23:56alyssalike why are there piles of 16MB resources getting alloc'd/freed
23:59alyssaBO cache: 2793072 KiB (+16320 KiB from Pool, hit/miss 642177/2468)
…