Don’t know if the onboard Wi-Fi works, suspend doesn’t work.
So fare, everything else seems to be working.
Not sure how many of the USB controllers can be used by Qubes OS, but I think it’s 3.
R4.2.2 needs latest kernel when installing, and don’t enable sys-usb during the installation. The motherboard firmware needs to be updated to the latest version, for the Ryzen 9000 to work.
Performance is very good, feels similar to an i9 K, but without the E cores.
It has been completely stable, I’ve not had any crashes. I’ve been running GPU pass-through, streaming video, etc., everything seems to work just fine.
The only really issue I’ve experienced, is that the latest version of the MSI firmware isn’t 100% stable. I don’t think it has anything to do with Qubes OS, It’s most likely because I’m running the memory overclocked at 6800 MT/s.
How did you get GeForce 4060 working with Qubes?
Or do you use GPU built into your CPU?
I’m having black screen when going to graphical manager with 4060.
Everything was fine with 750Ti before I had switched to 4060.
I see in “dmesg” this:
NVIDIA AD107
gsp ctor failed: -2
probe with driver nouveau failed with error -2
I have even updated Qubes kernel from 6.12.37-1 to 6.12.42-1 but it still doesn’t work despite the fact that Noveaue does have support of Ada architecture that 4060 has.
I tried. In this case, instead of the black screen, I get thrown to the load log with the text:
Starting plymouth-quit-wait.service - Hold until boot process finishes up...
and everything hangs on this terminal (though I can open a Ctrl+Alt+F2 terminal).
So, some of your displays (connected to the motherboard) work in Qubes OS only, and the others (connected to the GPU) - only in games (or similar)? I’m fine with using integrated graphics if I decide to upgrade a PC to have it, but I’m curious how I can use the same displays in different activities then.
P.S.: I’ve created another discussion about 4060, let’s move there to discuss it to avoid duplicates, thx.
Let’s say you have two displays, you connect one display to the HDMI port, and the other display to the Display Port, this allows you to use both display in dom0 using the internal graphics.
Your displays have two input, HDMI and Display Port, on one of the displays you use the free port to connect it to the GPU. When you want to use the GPU, you just switch the input on the screen, and when you are done using the GPU, you just switch it back to dom0 again.
@renehoj, hi again!
Sorry for one more question, but it looks like in the Hardware Compatibility List you are the only user with AMD 9xxxx I plan to buy for Qubes Another coincidence is that you are the only user of 4060 that I have (but don’t use yet), but this is unrelated, just fun fact.
Do you have any graphics performance issues when using a browser in VMs?
When I go to any page like GitHub in Firefox and scroll, I get maybe about 10 fps or less, very slow. When I drag the browser dialog, I also see things frame by frame.
My config is Ryzen 9 5900x + Nvidia 750Ti (no built-in GPU). The “nouveau” driver is quite buggy, but I’m not sure it’s guilty of poor graphics performance.
I wonder whether using AMD integrated graphics on 9xxx is stable and renders everything smoothly enough. I’m not interested in games at all, but I need really smooth scrolling of webpages and very long sources in IDE. Do you see any difference in graphics performance with a non-Qubes installation, let’s say Ubuntu or any other distro?
I’ve not had any issues with using the AMD internal graphics. I am using 3 QHD displays (7680x1440), not sure how well it works at higher resolutions.
In everyday use, I don’t think there is a difference between Qubes OS and traditional bare-metal Linux. Some video playback is worse, but still watchable, that is probably the most noticeable difference.
I get the same error, but xenpm also says Xen is using the old powernow driver. I don’t know if Xen 4.19 can use the amd_pstate driver, I think it might first be available in 4.21.
I also don’t know there is any performance improvement from using amd_pstate, or if it only improves power consumption.
Great, thanks. I researched it but found it confusing. Thought it might an issue due to SMT being off, good to know it’s a xen support thing.
And thanks for your posts about your AMD qubes experience. I just built one and it’s been a smooth transition. As you said, basically a bare metal experience. I wouldn’t have even thought to try AMD if not for your posts.
amd-cppc and amd-cppc-epp cpufreq drivers to enable fine-grained CPU performance scaling on AMD processors through Collaborative Processor Performance Control (CPPC)
To me, it sounds mostly like a power consumption improvement.
When running geekbench in a VM with all cores assigned, the benchmark score is close to an 9950X running bare-metal Linux, which is why I don’t think the powernow driver is a performance problem.