marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
cisco87_ has quit [Ping timeout: 480 seconds]
pb17 has quit [Ping timeout: 480 seconds]
faddat has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
pb17 has joined #asahi
rossy has quit [Remote host closed the connection]
rossy has joined #asahi
KxCORP589 has quit [Quit: Bye!]
KxCORP589 has joined #asahi
Brainium has quit [Quit: Konversation terminated!]
faddat has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
iyes has joined #asahi
faddat has joined #asahi
faddat has quit []
johey has joined #asahi
jnn has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
jn has quit [Ping timeout: 480 seconds]
jn has joined #asahi
jnn has quit [Ping timeout: 480 seconds]
skipwich_ has joined #asahi
skipwich has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
faddat has joined #asahi
benjinsm has joined #asahi
julio7359 has quit [Ping timeout: 480 seconds]
benjins has quit [Ping timeout: 480 seconds]
skipwich_ has quit [Ping timeout: 480 seconds]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #asahi
milky has joined #asahi
opticron has quit [Remote host closed the connection]
opticron has joined #asahi
<milky>
i am having issues with wifi, it tends to disconnect if i am using bluetooth, is this a known problem, or could it be an issue with my kernel config? dmesg is throwing some errors
<milky>
Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN.bin failed with error -2
skipwich has joined #asahi
<leio>
milky: yes, if you use 2.4GHz wifi, then that is likely to happen, for some reason more on asahi. bluetooth uses 2.4GHz too.
<chadmed>
milky: that error is a red herring and doesnt mean anything. the issue is that no one has reverse engineered the special sauce bt coexistence mode for these chips
<leio>
(right, I was referring to disconnects, not the specific error texts)
<milky>
thank you
milky has quit [Remote host closed the connection]
ChaiTRex has quit [Remote host closed the connection]
ChaiTRex has joined #asahi
iyes has quit [Ping timeout: 480 seconds]
iyes has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
jnn has joined #asahi
jn has quit [Ping timeout: 480 seconds]
baozich has joined #asahi
shiggitay has joined #asahi
baozich has quit [Ping timeout: 480 seconds]
jeisom has joined #asahi
iyes has quit [Ping timeout: 480 seconds]
shiggitay has quit [Ping timeout: 480 seconds]
thansen is now known as Guest2884
thansen has joined #asahi
Guest2884 has quit [Remote host closed the connection]
jeisom has quit [Remote host closed the connection]
jeisom has joined #asahi
skipwich has quit [Ping timeout: 480 seconds]
opticron has quit [Read error: Connection reset by peer]
opticron has joined #asahi
Brainium has joined #asahi
jeisom has quit [Ping timeout: 480 seconds]
Brainium has quit [Ping timeout: 480 seconds]
jeisom has joined #asahi
faddat has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
maxmatteo has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
maxmatteo has quit []
skipwich has joined #asahi
skipwich_ has joined #asahi
jeisom has quit [Ping timeout: 480 seconds]
ah- has quit [Ping timeout: 480 seconds]
skipwich has quit [Ping timeout: 480 seconds]
ah- has joined #asahi
gorane2 has quit [Ping timeout: 480 seconds]
gorane2 has joined #asahi
pb17 has joined #asahi
john-cabaj has joined #asahi
vmeson has quit [Ping timeout: 480 seconds]
frek has joined #asahi
faddat has joined #asahi
ChaiTRex has quit [Remote host closed the connection]
pb17 has quit [Remote host closed the connection]
<frek>
hej guys, i am using displaylink with the latest synaptic displaylink-driver-6.0.0-24 on my m1 air with fedora 39 (6.8.8-400.asahi.fc39.aarch64+16k) and it works pretty well visually, but as soon as i move an application to the external monitor, my audio get's very laggy and jerky to an extend, that it is not enjoyable to have anything else than a static image/frame/application without changing images on the external monitor. even
<frek>
mouse movement on the external monitor triggers it. here is the output of glxgears -info and you can see a heavy drop of framerates when the application is drawn on the external monitor after about 10s: https://hastebin.com/share/acosodocey has anybody else made similar experiences? is there a way to fix this? any help appreciated and thanks for this amazing work!
pb17 has joined #asahi
vmeson has joined #asahi
faddat has quit [Ping timeout: 480 seconds]
<PaulFertser>
frek: do you mean you move any application there and it affects audio playing elsewhere?
alarumbe has quit [Remote host closed the connection]
<PaulFertser>
frek: is it shown to be connected as a Super Speed device in dmesg?
<frek>
PaulFertser: well, let's say any application with moving images (e.g. also a browser with running youtube video) or manual movement of the cursor/windows on the ext. monitor affects the audio (independent of built in speakers/bluetooth/headphone out).
mintakka has joined #asahi
<PaulFertser>
frek: affects audio that an application that's not showing anything on the external display is outputting?
mintakka has quit [Remote host closed the connection]
<frek>
PaulFertser: yes, i just let a track play on elisa player on the m1 screen and it is enough to just move the cursor on the ext. monitor to cause audio jerks.
<PaulFertser>
frek: ok, wanted to make it clear. So hm, what about HS vs SS, can you confirm it's working as SS?
<toots>
Hi there! Thanks for the great work. Sorry if this has been asked before but I cannot find any documentation. Is there a nvram variable I can set to enable autorestart on power failure on a m1 mac mini using asahi linux?
<toots>
I did try system:autorestart=1 and it didn't seem to work
pb17 has quit [Ping timeout: 480 seconds]
Brainium has joined #asahi
<PaulFertser>
frek: ok, so it reports SS there. And evdi driver is used.
<PaulFertser>
frek: I would start "top" (or other kind of top if you prefer to see what kind of CPU load (per-core) is getting high during movement of cursor on the external display. And what processes stand out.
<frek>
moving the cursor constantly on ext. monitor directly puts %CPU of DisplayLinkMana to +-100%
<frek>
same as with other appliciations containing moving images
pb17 has joined #asahi
<PaulFertser>
frek: but it's just one core getting hogged?
<frek>
sometimes one (4) sometimes two (4+6)..
<frek>
in htop
jn has joined #asahi
kevinchrist20 has joined #asahi
jnn has quit [Ping timeout: 480 seconds]
<frek>
well, running a youtube video on ext.monitor puts up all cpu cores (mainly 0-3) at a base of ca. 20% with individual cores (mainly 4-7) going up to 30-80%. leaving the external monitor untouched results in core 0-3 mostly <10% and 4-7 mostly <5%.
frek has quit [Remote host closed the connection]
jnn has joined #asahi
frek has joined #asahi
<PaulFertser>
frek: I think the most interesting usecase is running a regular sound player on M1 display and some simple animation on external display.
jn has quit [Ping timeout: 480 seconds]
<PaulFertser>
frek: also interesting test would probably be to use a fast SS storage in the same port and trying to write or read data there to see if it might affect sound the same way.
<frek>
PaulFertser: ok, what kind of animation?
<PaulFertser>
frek: hm, probably just opening and closing another terminal window there in a loop to make it fully automated and reproducible?
<PaulFertser>
frek: I wonder if pinning that process to one of "performance" cores makes a difference.
<PaulFertser>
With "taskset"
<PaulFertser>
frek: you should be able to see in /proc/cpuinfo which core is which
<frek>
PaulFertser: "probably just opening and closing another terminal window there in a loop to make it fully automated and reproducible?" how to do that the best way?
<PaulFertser>
frek: probably something like this in bash: while true; do alarcritty & sleep .2; kill $!; sleep .2; done
<PaulFertser>
(not tested, just trying to show what I had in mind)
<PaulFertser>
frek: so what kind of core is getting hogged by that process?
<frek>
following command: while true; do konsole & sleep .2; kill $!; sleep .2; done
<PaulFertser>
toots: that doesn't work after shutdown, just after power failure.
<frek>
is putting all cores up, but especially 4-7 changing from 30-80 roughly..
<PaulFertser>
frek: what about just moving mouse cursor around manually? It still leads to sound stuttering, right? And you say DisplayLinkManager consumes all of its core while at it.
<toots>
PaulFertser: yeah thanks that's my next step. Guess that would be a good info to share. It's just that the keyboard/mouse and screens for it are far away now :-)
<frek>
but it's interchanging, so it's not hogging a specific one permanently i guess, but definitely cores 4-7 are on a higher load and are mostly close to 0 when ext.mon. is untouched..
<frek>
just moving the cursor leads to sound interruption and to an intermittend rise of CPU load of especially cores 4-7, but it goes down and sound works as soon as the cursor doesn't move anymore..
kevinchrist20 has quit [Remote host closed the connection]
<PaulFertser>
frek: are those the power cores or not?
jn has joined #asahi
jnn has quit [Ping timeout: 480 seconds]
pb17 has quit [Ping timeout: 480 seconds]
<frek>
PaulFertser: /proc/cpuinfo does not really give information about that, or i am missing something?