I don’t have 4K display, so I don’t about the quality of 4K resolution, but if I stream 1080p video on 3 monitors at the same time the video starts to have performance issues.
I don’t think you should be surprised if true 4K is going to give you issues.
Thank you for your reply. We can know 4K may have performance issue too, it’s about 1.34 times of three 1080P by calculating 1.34 = 3840 * 2160 / (1920 * 1080 * 3)
It seems like even the powerful 12900K CPU can’t software render 4K video on Qubes OS well.
My motherboard doesn’t have PS/2 ports so I can only use USB keyboard/mouse.
I’m talking about motherboard having only one PCI USB controller so you can’t have one dedicated USB controller for dom0 to use it for USB keyboard/mouse and have another USB controller for sys-usb to assign USB devices to your qubes.
With one USB controller attached to sys-usb you can assign USB input devices to dom0 but this will have security risks.
Or you can add second PCI USB controller in motherboard and use it.
It seems like Qubes OS can only work with PCI USB from your posts although the motherboard has multiple other USB ports. Or you can use non PCI USB but only use PCI USB for USB security consideration? I am not familiar with this because I haven’t run Qubes OS on a desktop.
They are all connected to the same USB controller.
Qubes 4.1: How to enable a USB keyboard on a separate USB controller
When using a USB keyboard on a system with multiple USB controllers, we recommend that you designate one of them exclusively for the keyboard (and possibly the mouse) and keep other devices connected to the other controller(s). This is often an option on desktop systems, where additional USB controllers can be plugged in as PCIe cards. In this case, the designated controller for input devices should remain in dom0 but be limited to input devices only.
@renehoj The MSI PRO Z690-A DDR4 does not write-protect any flash regions, so it is possible and you are free to try and set the HAP in the flash descriptor. However, if you don’t have any way to recover in case of some failure I wouldn’t recommend it.
You can disable Intel Management Engine by manually setting the bit a 0x1DE, which should be possible using flashrom with the internal programmer.
Keep in mind, doing this incorrectly can brick the board unless you have an external programmer. I have been able to flash the chip with the ch341a_spi, but it requires a special wson probe to interface with the chip.
I have done it on my system, and it removes mei from lsmod and device reference in /sys/class/mei. It’s been running for some hours now, so I believe it’s stable. The onboard wifi seems to need mei to work, and disabling mei makes the onboard wifi stop working.
I have only tested it with Dasharo, and it might not work with the stock MSI firmware. I’ve seen one person say it makes the stock firmware boot loop, which could be some protection in the msi firmware that detects the modification.
SMM BIOS Write Protection support and enable/disable option
AcpiView command to UEFI Shell
Platform will beep 12 times and blink HDD led on critical firmware errors, e.g. if memory training failed
PCIe 5.0 firmware caching in flash which allows to disable ME without losing PCIe 5.0 port functionality
cbmem logging from UEFI Payload is now supported and one can check complete firmware logs from OS using coreboot’s cbmem utility
Added Intel default settings for missing Alder Lake S CPUs
Changed
Added new ACPI Platform driver that installs coreboot exposed ACPI tables and all allows native EDK2 ACPI table protocol to install new tables, e.g. Firmware Performance Data Table, BGRT (Boot Logo) of VFCT (AMD GPU ACPI table)
Secure Boot is now disabled by default with all keys erased
Disabled PCIe ASPM and Clock PM for better PCIe device compatibility
Disabled GPIO programming by FSP, coreboot handles the GPIO completely. This additionally fixes a bug in FSP which did not enable SATA DEVSLP properly.
Changed Super I/O pin for PECI mode to reflect vendor firmware setting
Switched from IOT FSP to public ADL Client FSP
Switched to include microcode from public Intel microcode repository
Disabled PCIe hotplug
Network boot disabled by default, now configurable via menu option
Fixed
Vboot recovery popup is displayed before logo, so that logo do not disappear after popup is displayed
Incorrect USB2 PHY tuning values for USB-C ports causing hard USB controller lockups during USB enumeration and resulting in firmware hangs as long as USB Type-C devices were plugged or devices being unable to detect and enumerate in OS