This is copied over from linuxboot#1545
Please identify some basic details to help process the report
A. Provide Hardware Details
1. What board are you using (see list of boards here)?
Novacustom NV41 (Nitrokey branded)
2. Does your computer have a dGPU or is it iGPU-only?
3. Who installed Heads on this computer?
4. What PGP key is being used?
5. Are you using the PGP key to provide HOTP verification?
B. Identify how the board was flashed
I deleted this section because I purchased this machine from Nitrokey
C. Identify the rom related to this bug report
1. Did you download or build the rom at issue in this bug report?
2. If you downloaded your rom, where did you get it from?
Please provide the release number or otherwise identify the rom downloaded
Nitrokey heads v2.2
3. If you built your rom, which repository:branch did you use?
4. What version of coreboot did you use in building?
5. In building the rom where did you get the blobs?
Please describe the problem
Describe the bug
I did a dom0 update in Qubes and now the disk unlock passphrase doesn't work anymore. Kernel 6.5.8 works fine, but kernel 6.6.2 won't boot with the unlock passphrase, only the recovery passphrase. I presume something changed with dracut or the kernel boot process preventing concatenated cpios from overriding each other, but I have no idea how I would begin to go about debugging that.
To Reproduce
Steps to reproduce the behavior:
- Update Qubes dom0, installing kernel 6.6.2
- Attempt to boot using the disk unlock passphrase
- Observe that Plymouth still prompts for the recovery passphrase
- Observe further that in the initramfs
/etc/crypttab has not been patched and that /secret.key is missing
Expected behavior
Booting Qubes with the disk unlock passphrase does not prompt for the recovery passphrase. Also I would expect /etc/crypttab to be patched and /secret.key to be present in the initramfs if/when it drops into the OS recovery shell.
I apologize in advance if this should've gone in the Qubes forum.
This is copied over from linuxboot#1545
Please identify some basic details to help process the report
A. Provide Hardware Details
1. What board are you using (see list of boards here)?
Novacustom NV41 (Nitrokey branded)
2. Does your computer have a dGPU or is it iGPU-only?
3. Who installed Heads on this computer?
4. What PGP key is being used?
5. Are you using the PGP key to provide HOTP verification?
B. Identify how the board was flashed
I deleted this section because I purchased this machine from Nitrokey
C. Identify the rom related to this bug report
1. Did you download or build the rom at issue in this bug report?
2. If you downloaded your rom, where did you get it from?
Please provide the release number or otherwise identify the rom downloaded
Nitrokey heads v2.2
3. If you built your rom, which repository:branch did you use?
4. What version of coreboot did you use in building?
5. In building the rom where did you get the blobs?
Please describe the problem
Describe the bug
I did a dom0 update in Qubes and now the disk unlock passphrase doesn't work anymore. Kernel 6.5.8 works fine, but kernel 6.6.2 won't boot with the unlock passphrase, only the recovery passphrase. I presume something changed with dracut or the kernel boot process preventing concatenated cpios from overriding each other, but I have no idea how I would begin to go about debugging that.
To Reproduce
Steps to reproduce the behavior:
/etc/crypttabhas not been patched and that/secret.keyis missingExpected behavior
Booting Qubes with the disk unlock passphrase does not prompt for the recovery passphrase. Also I would expect
/etc/crypttabto be patched and/secret.keyto be present in the initramfs if/when it drops into the OS recovery shell.I apologize in advance if this should've gone in the Qubes forum.