Szczurek

I'm not the author, but to my knowledge this will probably going to be added, but currently Quibble can't even support latest windows 10 due to a some change in...

For quibble being stuck on booting windows it's probably this issue: #88

Hmm Locally the tests also failed (before making the change) so probably something is wrong with master branch.

Today I woke up with no icons on my screen except few of the built in google apps. Whyyyyy 😐 I think neo could have got updated by f droid...

> Seems like the Nobara Driver manager doesn't install the rocm package itself and only the rocm-meta package. After installing rocm, it seems to be working fine now. It's probably...

You were right that rocm wasn't installed, and it's no wonders to me that it isn't by default, when it takes 19GB of space. I don't have much free time...

I just updated to Nobara 41, and a note in the changelog saying that they now use rocm from fedora repos instead of amd, made me think of trying this...

`grep amdgpu /proc/bus/pci/devices` 2f00 1002731f 51 d000000c 0 e000000c 0 f001 fce00000 c0002 10000000 0 200000 0 100 80000 20000 amdgpu `lspci | grep -i "Advanced Micro Devices"` output 00:00.0...

No problem But isn't this using rocm5.2? Or is it that the pytorch rocm5.2 package is using rocm6.2 os install? I don't know how these interact together. Would you mind...

For me it doesn't work too with 22H2, on AMD CPU, on QEMU with virt-manager, on Nobara 38 (fedora linux optimized for games). So I think it doesn't matter if...