Hello, all!
I used the Resolute Daily ISO from 03/12/2026 on my laptop.
It was interesting to try to enable TPM-FDE “out of the box”, right at the installation stage.
I used the UEFI (BIOS) options to hide the primary NVMe drive from the system, gave the Live Installer the entire second additional NVMe drive, and tried various ways (monkey-testing until you succeed) to get the installer to accept my system as “available for installation using TPM-FDE”.
I also tested my laptop in quite detail for compatibility with 26.04 in general.
I was pleased that the keyboard backlight worked like in Windows, set to turn off after 30 seconds, and the backlight does turn back on when you press a key. It didn’t turned on after turning off on 24.04.
My attempts to use TPM-FDE ended with an error about “you have very new hardware, we haven’t seen anything like this before”. That is:
“PCR_UNUSABLE
error with secure boot policy (PCR7) measurements: generating secure boot profiles for systems with timestamp revocation (dbt) support is currently not supported”
If I understood GhatGPT correctly, he advised me to appear in two places: WithSecureBootPolicyProfile should accommodate systems that support timestamp revocation · Issue #306 · canonical/secboot · GitHub and TPM-backed FDE: Take 2 minutes to help widen Ubuntu compatibility with your TPM configuration! - #29 by dnxb42 , there were no additional questions here, I offered help on the first link, and on the second I sent 2 answers to the form, as requested.
But my testing of the Ukrainian translation was super successful, there is nothing to complain about here. There is a place for a few corrections, thought.
In addition, I saw some screens with translations for the first time after conducting initial testing in Hyper-V for quite a long time.
Regarding installation issues: they were minimal.
First, I’ll add a suggestion to include in the Troubleshooting section of the Release Notes:
If you have a laptop, and when booting from an ISO in Live mode, after the initial screen with the laptop manufacturer’s logo (for example, Acer Nitro) and the “round boot indicator” the image disappears, then perhaps it is because the Radeon video adapter does not behave very well at startup. If the system has two video adapters and Optimus/Advanced Optimus, then it may happen that the system needs to be rebooted into UEFI, and there enable the Nvidia GPU Only mode in the Display mode switch. (see pictures)
In general, on Windows I already had a problem installing reference Radeon drivers, and I already know that AMD themselves recommend installing the OEM version of the Adrenaline driver, and with AI we once figured out why this is so and how to deal with it, here, (for additional reading, you can skip it, because for this post it can be considered a bit offtopic): https://www.reddit.com/r/AMDHelp/comments/1op3i71/amd_reccommends_to_stick_with_vendor_laptop/ - my personal experience and conclusions on Radeon graphics in the laptop mentioned in this post, applies to Windows.
Let’s go back to Resolute.
I think that the problem with MUX (Optimus) is a problem in this case too.
There is no OEM Acer driver for Linux.
And the driver that “comes with the installer” has the same symptom as when installing the reference driver on Windows, that is, a black screen at some stage of system boot.
It is worth noting that when I booted in Live mode, the external display connected to the HDMI output worked without additional options.
Therefore, another recommendation for the Troubleshooting section - advise connecting an external display that is switched to the Nvidia video adapter.
If the display receives an image, and the mascot - Raccoon - appears there, then all that remains is to press the Win+P+P key combination (hold down Win, press P twice, release Win), this key combination will switch the graphics output to the “External display only” mode, and you will see the desktop that was displayed on the black screen, including the installer window.
After the installation is complete, after rebooting, when you see a gray background on the secondary display, this is a sign that the login screen has loaded on the main display, and since the system uses the secondary display in extended mode, you need to perform the following sequence of actions: after the gray background appears on the secondary display, count to 10, press Enter (confirm that we want to log in to our first account), count to 5, enter the account password, press Enter (login attempt). If you see Raccoon, then all that remains is to press the aforementioned Win+P+P to switch the main screen to the secondary display.
It is also worth noting that the current version of amdgpu refused to install for me.
In fact, my graphics on the primary display work fine just in Nvidia GPU Only mode - for my current experiments with Cursor, AI Agents, and Figma, this is enough for me right now.
I think it should be noted that I saw the PCR_UNUSABLE error after wiping the TPM module and even resetting the Secure Boot settings (including the “factory reset” option).
I think it would be more appropriate to immediately inform the owner that he will have a PCR_UNUSABLE error and the owner will not be able to do anything about it.
There won’t be screenshots, there will be screen shots, but I edited them a bit so they wouldn’t be too big.
Acer Latop used in testing: https://www.acer.com/ua-uk/support/product-support/AN17-41/NH.QL1EU.003/
PCR_UNUSABLE which stopped my attempts to enable TPM-FDE, I used Passphrase-FDE instead, and it succeeded.