#
…

2024-05-09

00:15ddxtanx has quit [Remote host closed the connection]
00:16ddxtanx has joined #asahi
00:56pb17 has quit [Ping timeout: 480 seconds]
01:00DragoonAethis has quit [Quit: hej-hej!]
01:00KxCORP5894 has quit [Quit: Bye!]
01:00DragoonAethis has joined #asahi
01:00KxCORP5894 has joined #asahi
01:12pb17 has joined #asahi
01:16john-cabaj has quit [Ping timeout: 480 seconds]
01:19matteo has joined #asahi
01:27matteo has quit [Ping timeout: 480 seconds]
02:20rossy has quit [Remote host closed the connection]
02:21rossy has joined #asahi
02:26shiggitay has joined #asahi
02:31DarkShadow44 has quit [Quit: ZNC - https://znc.in]
02:31DarkShadow44 has joined #asahi
02:37ten15723774324630506 has joined #asahi
02:41hightower4 has joined #asahi
02:43ten1572377432463050 has quit [Ping timeout: 480 seconds]
02:43ten15723774324630506 is now known as ten1572377432463050
02:48hightower3 has quit [Ping timeout: 480 seconds]
02:53kode54 has quit [Quit: The Lounge - https://thelounge.chat]
02:53KDDLB has quit [Quit: The Lounge - https://thelounge.chat]
02:54kode54 has joined #asahi
02:58pb17 has quit [Ping timeout: 480 seconds]
03:04pbsds has quit [Quit: The Lounge - https://thelounge.chat]
03:05pb17 has joined #asahi
03:10ChaiTRex has quit [Remote host closed the connection]
03:10ChaiTRex has joined #asahi
03:14ipatch has quit [Quit: WeeChat 4.2.2]
03:21matteo has joined #asahi
03:22ipatch has joined #asahi
03:29matteo has quit [Ping timeout: 480 seconds]
03:35marvin24_ has joined #asahi
03:39marvin24 has quit [Ping timeout: 480 seconds]
04:01matteo has joined #asahi
04:09matteo has quit [Ping timeout: 480 seconds]
04:24ddxtanx has quit [Quit: Konversation terminated!]
04:47pb17 has quit [Ping timeout: 480 seconds]
04:58eroc1990 has quit [Quit: The Lounge - https://thelounge.chat]
05:09nicolas17 has quit [Ping timeout: 480 seconds]
05:12pb17 has joined #asahi
05:16eroc1990 has joined #asahi
05:18bdju_ has joined #asahi
05:22bdju has quit [Ping timeout: 480 seconds]
05:26ipatch_ has joined #asahi
05:28ipatch has quit [Ping timeout: 480 seconds]
05:33bdju_ has quit [Quit: Reconnecting]
05:33bdju has joined #asahi
05:44fooxiSo I upgraded to F40. It is still super choppy in KDE.
05:48matteo has joined #asahi
05:56matteo has quit [Ping timeout: 480 seconds]
06:13fooxiIt is not noticeable Kwin was fixed, or this is another issue - not sure.
06:13fooxiBut it's so bad I will have to downgrade again.
06:15rvalue has quit [Remote host closed the connection]
06:16rvalue has joined #asahi
06:17vadorovsky has quit [Ping timeout: 480 seconds]
06:18jannaujust to make sure `es2_info | grep GL_RENDERER` reports something like "Apple Macbook Pro 13-in (G13G ...)"
06:19jannauhow do you notice the chopiness? just general use? moving windows for example
06:25fooxiGL_RENDERER: Apple M1 (G13G B1)
06:25fooxiIt is particularly noticeable when scrolling in firefox. It was smooth in F39.
06:25fooxiNow it's like every X amount of frames it freezes for a short moment.
06:30jannauI can't reproduce. any website there this is particularly noticeably?
06:30aradhya7 has joined #asahi
06:30fooxiIt's every website for me. Hmm.
06:35jannauhmm, the show fps effect still shows drops to ~55 fps for fast scrolling but I barely notice those
06:36fooxiLet's see if I can record the screen.
06:37fooxiMine goes to 40.
06:38fooxi37 <-> 58 when scrolling.
06:38jannaudo you scroll fast or slow
06:39fooxiEither one. When I scroll as slow as I can, it still goes to 40.
06:39fooxiAnd that's moving it a tiny length.
06:39fooxiEven hit 34 now.
06:39fooxiWhen I do as fast as I can, I get 38<->58.
06:40fooxiAll of this is on the reddit subpage.
06:41jannaureproduced by disabling icc profile
06:43fooxiyay! So it's something I'm doing wrong or haven't enabled?
06:44pb17 has quit [Ping timeout: 480 seconds]
06:46jannauno, it's an issue with the system
06:47jannauyou can download the zip at the bottom of https://www.color.org/chardata/rgb/DisplayP3.xalter extract it and use it as Color Profile in KDE's display settings
06:48jannauthat seems to improve the behavior surprisingly for me (and will give more accurate colors)
06:49chadmedf40 doesnt have the kwin guard interval patch does it
06:51jannaufedora uses unpatched kwin-6.0.4.1
06:52jacksonchen666 has joined #asahi
06:53fooxijannau: Do you mean system settings - color management -> import profile?
06:53chadmedfooxi: no, the colour management profile is set on the display settings now
06:54fooxiah, found it.
06:54jannaunot sure if that does the same, I ment "Color Profile" on the display setting
06:54fooxiDo I need to reboot because that b0rked my screen :D
06:54fooxiNow it's white
06:54fooxiand I can barely tell what Im doing
06:54fooxiOk reverted.
06:55jannaujust hitting the power button and escape should be enough
06:55jannauit needs a full redraw after changing the color profile
06:56pb17 has joined #asahi
06:58fooxiCan confirm the fps is now much more stable, but I still get a more choppy experience than in F39, so not entirely sure it's fps related hmm. Do you have default scroll settings in firefox?
07:01fooxiExcellent.
07:01fooxiThanks a million, jannau!
07:02LarstiQinteresting that lack of a color profile causes choppy scrolling
07:03matteo has joined #asahi
07:06hspak416327 has quit []
07:06hspak416327 has joined #asahi
07:08fooxiSomething I am noticing, however, is that all my efforts to recreate macos-like scrolling is worse now.
07:09fooxiIt still has a random "chop" every now and again.
07:09fooxiMuch better, but still present although very subtle.
07:11matteo has quit [Ping timeout: 480 seconds]
07:11chadmedfooxi: are you noticing this in other apps
07:12chadmedi know that not a lot of kde stuff supports kinetic scrolling though
07:12fooxiYeah, not sure I have something I can compare with, but I am noticing it when moving windows around.
07:12fooxiThere's an occasional, random stutter.
07:15chadmedim noticing stutter when doing a controlled scroll in system settings
07:17chadmedswitching to the performance governor completely eradicates it
07:18fooxiHow do I do that?
07:18chadmednot for users
07:18chadmedyour battery will evaporate/machine will run very hot
07:22fooxiSetting mousewheel.default.delta_multiplier_y and mousewheel.default.delta_multiplier_x to 100->20 makes it easier to notice in firefox.
07:23fooxiThere's 1-3 micro stutters every scroll.
07:30fooxiDo you want me to test anything else? If not, I'm gonna downgrade again.
07:31DarkShadow44 has quit [Quit: ZNC - https://znc.in]
07:31DarkShadow44 has joined #asahi
07:37fooxiNot sure if it's related, but in youtube (even on F39) videos would freeze entirely every now and again, and only the sound would play).
07:37fooxiThere'a at least one other user with a similar experience on the subreddit.
07:37fooxiThere's
07:38j`eyI get videos freezing, but only on twitch at 1080p
07:45fooxij`ey: in both 39 and 40?
07:45j`eyhaven't upgraded to 40 yet
07:45jeisom has quit [Quit: Leaving]
07:51matteo has joined #asahi
07:53jeisom has joined #asahi
07:57bluetailAbout the HDD Enclosure 10 Bay IcyBox - by now is believed broken. Will use a HBA.
07:57bluetailBecause I recreated the RAID level and disks were ejected despite having no defect.
08:22pb17 has quit [Ping timeout: 480 seconds]
08:24shiggitay_ has joined #asahi
08:30shiggitay has quit [Ping timeout: 480 seconds]
08:33shiggitay_ has quit [Ping timeout: 480 seconds]
08:35PaulFertserbluetail: you came to conclusion the bay itself is broken?
08:36bluetailNo, the whole shelf
08:36bluetailjust eff it, I am going to build a 20 bay rig
08:37matteo has quit [Remote host closed the connection]
08:40bluetailmy plan is RM43-320-RS + Supermicro X13SEI-TF
08:42matteo has joined #asahi
08:48matteo has quit [Remote host closed the connection]
08:56matteo has joined #asahi
09:00pb17 has joined #asahi
09:06thansen has quit [Read error: No route to host]
09:08thansen has joined #asahi
09:23jacksonchen666 has quit [Quit: WeeChat 4.2.2]
09:25wm4 has joined #asahi
09:30wm has quit [Ping timeout: 480 seconds]
09:31wm has joined #asahi
09:32bluetailor, use my current setup, and just change the case.
09:34bluetailbut then I would need a mini SAS HBA, for which I dont have a port for, other than NVMe [...]
09:35bluetailnah, I better keep separate devices.
09:35chadmedim running an icybox 4 bay usb thing into a mac mini
09:35chadmedworks a treat
09:35matteo has quit [Remote host closed the connection]
09:35matteo has joined #asahi
09:35matteo has quit [Remote host closed the connection]
09:35bluetailmine did for 3 years, too
09:35matteo has joined #asahi
09:36chadmedi was originally going to build an affront to nature and get a thunderbolt to pcie dev board and secondhand HBA on ebay then shove them, a mac mini and a whole mess of drives into a rack mount case
09:36matteo has quit [Remote host closed the connection]
09:36bluetailbut smartctl does not report any, reseating doesnt help, and from the start hotswap did not work
09:36chadmedbut my old server bit the dust before tbt support was ready :c
09:36wm4 has quit [Ping timeout: 480 seconds]
09:38bluetailI guess its a nice temporary solution!
09:38bluetailmore than anything, I am glad I got lots of backups
09:38chadmed has quit [Quit: Konversation terminated!]
09:44sventhat tbt to PCIe to sata abomination is my plan
09:44matteo has joined #asahi
09:45svenprobably three Mac minis and ceph then
09:48bluetailgood luck sven. I am mentally kind of done with doing this 'partial, half-breed' setup
09:49chadmed has joined #asahi
09:50svenI only have my own code to blame if something doesn’t work ;)
09:51chadmedno pressure or anything, but your code will be entrusted with my family's life memories :)
09:53svenI actually have a long weekend and want to finally get back to the usb mess now
09:54chadmedi have money on NHI breaking at least one more time
09:54svenim not gonna bet against that
09:54j`eysven: it's going to be a looong weekend
09:56matteo has quit [Remote host closed the connection]
09:56jannaudid you find anyhing on maz' 6.9-rc usb issue? I was thinking of rebasing onto 6.9-rc7 to hopefully catch any regression before 6.9
09:56svenI tried reproducing it but couldn’t do far :/
10:05hspak416327 has quit []
10:06hspak416327 has joined #asahi
10:10pb17 has quit [Ping timeout: 480 seconds]
10:19f_ has joined #asahi
10:20ah- has quit [Ping timeout: 480 seconds]
10:23ah- has joined #asahi
10:24bluetailI hope you are not going to try to reproduce that translation error issue
10:26jannauwe have to. that one is (probably if it is the same issue) not limited to your setup
10:34fooxichadmed: If the performance governor that you have in dev mode fixes the problem, does that mean the issue is fixable by optimization at some point and that this may have caused you guys to create a ticket in some system somewhere? :)
10:34fooxiJust trying to figure out if it's reasonable to wait for a fix, or if I should downgrade.
10:35ah- has quit [Ping timeout: 480 seconds]
10:35chadmedwe may have already found part of the problem so just sit tight i guess :)
10:35fooxi<3 thank you!
10:43loki_val has quit []
10:44pb17 has joined #asahi
10:45crabbedhaloablut has joined #asahi
10:46matteo has joined #asahi
10:48ah- has joined #asahi
10:48aradhya7 has quit [Quit: Connection closed for inactivity]
10:48opticron has quit [Read error: Connection reset by peer]
10:49opticron has joined #asahi
10:50cylm has joined #asahi
11:22matteo has quit [Quit: Leaving...]
11:35hightower4 has quit [Ping timeout: 480 seconds]
11:45sproed has joined #asahi
11:56sproed has quit [Quit: Konversation terminated!]
12:39mazsven: I'll try to have a look when I get a chance. it could also be that my DT is out of whack with what the driver wants (the u-boot build is over a year old).
12:41pb17 has quit [Ping timeout: 480 seconds]
12:44hightower2 has joined #asahi
13:04bluetailjannau the translation fault is not present on my x86 machine, but the behavior of disconnecting is.
13:04bluetailI am just careful when making a statement about what the cause may be
13:05bluetailI do think it could be related to the type of the enclosure
13:06bluetailI do think, with the translation error fixed, the issue disconnecting will still be present, but the unit will be sent back tomorrow, anyways.
13:06bluetail( enclosure )
13:07jannauah, the translation fault is an issue though
13:08bluetailIs the impact foreseeable, or will it result in a random issue?
13:08bluetail( trying to understand the implication of such fault to learn from it )
13:09pb17 has joined #asahi
13:22mazsven: I just realised I'm also getting messages that say "[ 4.068348] phy-apple-atc 703000000.phy: pipehandler lock not acked, this type-c port is probably dead until the next reboot."
13:25svenyeah, that I one I know about
13:25svenand also how to fix it
13:26svenit’s surprising usb3 worked _at all_ the way I implemented it
13:34mazdon't underestimate the power of default values... ;-)
13:34fooxij`ey: any idea what is causing the video freezing? codec?
13:34leiofwiw, I don't get and usb data with phone, only charging, with one cable in any of the back type-c ports at least, complains about "can't set config #1, error -71", but works with a fatter cable
13:38yuyichao has quit [Ping timeout: 480 seconds]
13:42j`eyfooxi: I think it's a CPU speed/scheduling type thing, when I put firefox on the perf cores, it was fine
13:43j`eybut the E cores should be fast enough for 1080p, so Im not sure
13:44fooxij`ey: interesting! thanks
13:44j`eyfooxi: taskset is the program that can help you try that
13:45fooxicheers!
13:50nicolas17 has joined #asahi
13:56fooxij`ey: do you know the core # for the performance cores?
14:00leiofooxi: i recently found `lscpu -e` to be helpful for this, instead of manually figuring it out from cpuinfo or default lscpu
14:00leiothe p cores would have higher max MHZ listed than the rest
14:01leiotaskset numbers are the first CPU column then
14:03fooxioh, excellent.
14:04fooxiSo 4:7 then.
14:06fooxiThat fixed my 1080p @ twitch freezing issue, indeed. Thanks leio & j`ey!
14:16fooxiThat causes some visual glitches though.
14:19fooxi... and it persists on reboot.
14:20fooxiAreas go black and doesnt revert back, making the system unusable.
14:20fooxiWhich doesnt make sense since taskset is no longer running, so I guess something else borked?
14:21fooxiHow do I even fix this, lol.
14:21fooxiRebooting doesnt help. Reinstall?
14:24fooxiThe bottom panel disappears whenever i minimize something.
14:25vx has quit [Quit: G-Line: User has been permanently banned from this network.]
14:25vx has joined #asahi
14:28iyes has joined #asahi
14:30iyeshi! i wanted to try to see if my bluetooth headset mic would be usable under asahi. i connected the headset, but only an audio output device showed up (and it worked fine), but no input. i couldnt find any way to enable the input.
14:31iyesnow i know this is probably not an issue with asahi, but with pipewire or something
14:31iyesbut here is something asahi-specific that happened:
14:31iyesafter i paired and connected the headset on asahi, i cannot get it to connect on macos anymore
14:32iyesi tried to reboot into macos, and when i tried to connect to the headset from macos, it just didnt work
14:32iyesi tried pairing mode on the headset, no difference
14:32iyeswhat could be the explanation for this behavior?
14:36PaulFertseriyes: does this headset work with any other GNU/Linux device? BTW, take into consideration that for sound playback you want A2DP Bluetooth profile while for two way communication you want HSP or HFP profile. And a headset can't do both at the same time so if you've connected it as a music playback device then you can't record it, that's just how those Bluetooth profiles are designed.
14:37iyeswait so how can i be in a discord call in macos and use the headset for both output and input then?
14:38iyeswhat mode/profile does that use?
14:38jannaufooxi: disable the "Blur" desktop effect, if you have multiple virtual desktops switching the desktop will fix it
14:39PaulFertseriyes: HFP with shitty sound quality
14:39iyesaha, so i guess i never noticed that because i wasnt listening to music or something while using the headset mic
14:40iyesokay so i guess i should look into how to switch bluetooth profiles under linux
14:40iyesthanks for the info
14:40iyesand does anyone have any idea why i can no longer connect the headset on macos?
14:42iyesis it possible that the headset is confused or something, because i paired it from two different OSs on the same machine? or is it possible that asahi somehow left things in a state that macos doesnt like?
14:43pb17 has quit [Ping timeout: 480 seconds]
14:43mazsven: just checked with a newer u-boot, and I get the exact same SError when dwc3 initialises.
14:43fooxijannau: <3
14:44fooxijannau: Thank you! That fixed it.
14:44svenhen, le me try to boot through u boot
14:45PaulFertseriyes: yeah, it has limited amount of pairings, you need to make it forget all the old ones before pairing in that case. There's also a way to share pairing keys between different OSes but you need to pre-plan that.
14:46j`eythere is an asahi-btsync tool to do that
14:47iyesi need to somehow find a way to make the headset forget all its pairings?
14:47iyesor the mac's bluetooth chip?
14:47iyesis the limited number pairings for the host or the device
14:47PaulFertseriyes: the headset
14:48iyesah okay well uhm i sure hope that is possible to do
14:49PaulFertserSure, just RTFM...
14:49jannaunot sure if asahi-btsync can handle more than (apple-)input devices
14:50iyeswell thats the thing, this bluetooth device is kinda awful and the user manual has no info about this
14:50iyesanyway, i will have to investigate
14:50iyesthanks for the help
14:51PaulFertserjannau: this https://docs.rs/crate/asahi-btsync/latest/source/src/main.rs ? You mean you suspect macOS keeps only input devices keys in that NVRAM but the other keys elsewhere?
14:54PaulFertserBluetoothUHEDevices /sounds/ generic enough...
14:56svenI‘d assume it stores everything but the ADT can’t be trusted much
14:57mazsven: seems related to dwc3_power_off_all_roothub_ports(). commenting it out prevents the SError, but I'm then stuck with USB2. maybe related to the above PHY issue?
14:57JayBeeFOSS has quit [Ping timeout: 480 seconds]
14:58svenyeah, if the phy is somehow in an unexpected state wrt dwc3 that might explain why things explode
14:58svenI’ve seen the SoC reboot on such cases as well
14:58mazwell, that's one way to fix it! :)
14:58JayBeeFOSS has joined #asahi
15:07foolman has joined #asahi
15:08iyes has quit [Ping timeout: 480 seconds]
15:09fooxichadmed: running firefox on one of the performance cores solves my scrolling-stutter issue, too.
15:14pb17 has joined #asahi
15:22john-cabaj has joined #asahi
15:22john-cabaj has quit []
15:22john-cabaj has joined #asahi
15:25checkfoc_us has quit []
15:27checkfoc_us has joined #asahi
15:41KxCORP5894 has quit [Quit: Bye!]
15:42KxCORP5894 has joined #asahi
15:43KxCORP5894 has quit []
15:44foolman has left #asahi [#asahi]
15:44KxCORP5894 has joined #asahi
16:03rvalue has quit [Remote host closed the connection]
16:03rvalue has joined #asahi
16:13shiggitay_ has joined #asahi
17:18hightower3 has joined #asahi
17:24c10l7 has joined #asahi
17:24c10l has quit [Ping timeout: 480 seconds]
17:26hightower2 has quit [Ping timeout: 480 seconds]
17:43iyes has joined #asahi
17:54pb17 has quit [Ping timeout: 480 seconds]
18:14ipatch_ has quit [Read error: Connection reset by peer]
18:16ipatch has joined #asahi
18:22pb17 has joined #asahi
18:25nyaomixyz has joined #asahi
18:27ipatch has quit [Quit: WeeChat 4.2.2]
18:28shiggitay_ has quit [Ping timeout: 480 seconds]
18:32Brainium has joined #asahi
18:39ipatch has joined #asahi
18:42ipatch has quit []
18:49ipatch has joined #asahi
18:55iyes has quit [Ping timeout: 480 seconds]
19:18iyes has joined #asahi
19:26Simonx22 has quit []
19:27Simonx22 has joined #asahi
19:32Simonx22 has quit []
19:33Simonx22 has joined #asahi
19:33Simonx22 has quit [Remote host closed the connection]
19:39Simonx22 has joined #asahi
20:04pb17 has quit [Ping timeout: 480 seconds]
20:23nyaomixyz has quit [Quit: Konversation terminated!]
20:43pb17 has joined #asahi
20:56KDDLB has joined #asahi
21:00iyes has quit [Ping timeout: 480 seconds]
21:03f_ has quit [Ping timeout: 480 seconds]
21:23iyes has joined #asahi
21:36cylm has quit [Ping timeout: 480 seconds]
22:01pb17 has quit [Ping timeout: 480 seconds]
22:04yuyichao has joined #asahi
22:17pb17 has joined #asahi
22:29ten1572377432463050 has quit [Remote host closed the connection]
22:29ten1572377432463050 has joined #asahi
22:46nela has quit [Quit: bye!]
22:47ddxtanx has joined #asahi
22:47nela has joined #asahi
22:51ddxtanxDoes anyone have the fedora-asahi-remix-hotfixes.repo file thats in /etc/yum.repos.d? I accidentally overwrote it w/ tee and couldnt find it anywhere online like I could for the other ones
22:55Georgemoody has joined #asahi
22:56lynndotpy has quit [Quit: bye bye]
22:57lynndotpy has joined #asahi
22:58Georgemoodylooks like there's alreadt a thread on the forums about the bluetooth issues after upgrading to 40, glad i'm not alone
22:59tramtristfirefox keeps crashing/disappearing on 40
23:00j`eyGeorgemoody: fix/revert has been identified
23:00iyes has quit [Ping timeout: 480 seconds]
23:00chadmed_ has joined #asahi
23:01chadmed_Arbifox: not every piece of software is poorly engineered and assumes 4K pages. the lack of bare-metal 4K page support does not negate the raison d'etre of asahi lmao wtf
23:02chadmed_most of the important IOMMUs on these SoCs do not support 4K pages and some others dont support bypass mode (rightfully so, it's insecure for e.g. pcie), so when you apply the 4K iommu patches you will lose wifi, bluetooth, gpu, thunderbolt (when it arrives) and usb-a ports
23:03chadmed_you also lose like 20% performance on the application cores
23:03chadmed_the microvm stuff has a lower performance penalty than trying to run those 4K patches
23:06ddxtanx has quit [Quit: Konversation terminated!]
23:08iyes has joined #asahi
23:12chadmed_nvm that was meant for #asahi-alt :/
23:14nicolas17I was trying to find what you were replying to
23:16nicolas17they aren't here so you should re-send your messages there :P
23:18iyes has quit [Ping timeout: 480 seconds]
23:54pb17 has quit [Ping timeout: 480 seconds]
23:57ddxtanx has joined #asahi
…