I hesitate to ask this, because I really haven’t got a good record of the failures and successes I had, but…
I bought a Ryzen 7 3700X and an MSI B550G3 motherboard, because they were on sale, and looking cheap per core. I didn’t really look at the potential compatibility with Qubes.
After a mistake or two with the rather un-intuitive “gaming” BIOS, Qubes 4.2 ran OK, but with occasional unexpected behaviour - particularly hard lockups when trying suspend, and some kernel messages about amdgpu for my cheap Radeon GPU.
Noticing some messages in xen/console/hypervisor.log about “AMD family 23 is not supported” I downloaded one of the 4.3 weekly build ISOs previously made available by the generosity of @fepitre - just to test.
After a fair while of light testing, I feel fairly sure that things are working far better than before. Suspend seems solid, and I haven’t seen any major problems. I even did an update from the testing repo without problems.
Before I start getting into more serious investigation of qubes-builder, I have a whole lot of questions, starting with the one in the title.
Apart from the obvious - why would I want to run pre-release test software - does anyone have any comments, tips, or hints about the best way to keep a maximum of 4.2 tried-and-trustedness and still get 4.3 hardware compatibility, or any other strategy?
I went through the first steps of an HCL fairly early on, but then I didn’t find any other reports relative to such a pre-release moving-target version of Qubes, without even an RC version number.
I’m not really sure how to make effort I put in to 4.3 be useful, either to our Devs or to potential users… that’s why I’m interested to know if anyone else has tried going in a similar direction.
I do have a spare disk available now, so I can go back and do one for 4.2 now, which I expect will be fairly dismal when it comes to suspend/resume(TBC).
For testing future developments, should I just start regular updates and watch out for regressions, or is there more to do?
