Actionless Loveless

Results 931 comments of Actionless Loveless

also some after-thoughts: 1) would we also need --disable-root flag probably? (or it's logical to assume that with --no-wm) 2) since multi-threading was mentioned couple of times, i'll also add...

thanks for sharing, @Aire-One i'm overall looking positive towards merging smth like that - as it would decrease the "diff surface" of things which would need to be changed for...

and regarding the awexygen i thought i wrote it in previous messages but apparently either forgot or mistakenly removed while typing other paragraphs: yeah, it looks similar to that final...

no, as CI currently broken: https://github.com/awesomeWM/awesome/issues/3994

now it's finally fixed, so you could rebase πŸ‘ŒπŸ˜Έ

@diegodorado it works if you apply also this patch as well: https://gitlab.archlinux.org/archlinux/packaging/packages/cool-retro-term/-/blob/main/0001-nvidia-fix.patch?ref_type=heads ![2024-07-13--1720830457_3840x2160_scrot](https://github.com/user-attachments/assets/0a7eb9bd-50c8-4c84-905c-2000a049359b) ![2024-07-13--1720830489_3840x2160_scrot](https://github.com/user-attachments/assets/3568441b-fe37-4e03-baf9-4910fd0dc8d0)

it seems smth is off with it, that same t5xxl step on ryzen 5600x the python cpu implementation (from diffusers lib) running 67 seconds faster (237%) than CPP implementation and...

i found the solution for my problem with high condition graph computing time, mb would be useful for someone else: because i was building the package on old xeon server,...

> Also I'm using a q4_k quantization for t5xxl that must be it, i can confirm that quantization affects the time a lot

i can see 2 GPUs on the left side of the app (with the graph), but on the right side it shows only GPU0 and a blank line following it...