qubes-issues VS coreboot

Are you using an Nvidia GPU?

https://github.com/QubesOS/qubes-issues/issues/5104

https://github.com/QubesOS/qubes-issues/issues/7591

If not, try this: https://github.com/QubesOS/qubes-issues/issues/6880#issuecom...

There is no tearing on my Librem laptops.

> The gnome desktop will be important for adoption

Gnome is too opinionated to adjust it for Qubes: https://github.com/QubesOS/qubes-issues/issues/1806#issuecom...

However you can easily install KDE.

Are we still getting a second RC for 4.2? I remember originally we were told that we would because of the new Qubes builder tool, but I see the milestone jumped to 96% since last I checked, are we getting a full release at the 100% github milestone? Or what happens when it hits 100? https://github.com/QubesOS/qubes-issues/milestone/26

This project was never stagnant, a lot of things are always happening here: https://github.com/QubesOS/qubes-issues.

Concerning the certified hardware, few vendors try to make the certification, and also coreboot is required: https://www.qubes-os.org/doc/certified-hardware/#hardware-ce...

Not precisely, but a lot is going on in this direction: https://github.com/QubesOS/qubes-issues/issues/1939.

I read that there is a plan to implement per-VM encryption (https://github.com/QubesOS/qubes-issues/issues/1293)

Looks like a fix might be close at hand: This pull request is linked to the issue "Hardware support: Ryzen 7000 series / Zen 4 / AM5."

This bug report indicates that "kernel-latest" will be in the next official build of the Qubes 4.1 install ISO. Thing is on the mirrors the last release of 4.1 (actually 4.1.1) was July 18th 2022, and thus the title of this post.

Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.

1: https://www.coreboot.org/

Coreboot is 0.6% C++.

NovaCustom ; some models come with Dasharo a coreboot distribution.

You can also use Mr. Chromebox Script to install Coreboot on your chromebook to get a UEFI BIOS on your Chromebook and then you can go an install either a linux distro or even Windows if you want. It's a pretty straightforward process and also reversable if you want to go back to just using ChromeOS.

Some models are available with Dasharo a [coreboot]https://www.coreboot.org/) distribution.

why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c

use croshfirmware.sh from https://github.com/coreboot/coreboot/tree/master/util/chromeos

There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.

does anyone know what is https://github.com/coreboot/coreboot/blob/b12caef23bc1b29c2e658f2b728cc4beac1e62b9/src/northbridge/intel/haswell/vcu_mailbox.c

Download crosfirmware.sh and run it from command line: bash crosfirmware.sh droid