Librem mini V2 (Pureboot) / Qubes 4.1 refuses correct disk password .

. . . sometimes.

Does anyone else with a mini V2 with Pureboot running Qubes os 4.1 get this?

You start up and the Pureboot (beautiful software) does it’s thing, reads the boot files, all is correct and it takes you to the Qubes disk decryption password box.
You enter your password (phrase) and normally all is well, the disk decrypts, etc, etc.
But sometimes - perhaps 1 time in 5 - your password is rejected. If it is, even if you’re sure you got it correct with no typos, etc. and you try again, being very careful to make no mistakes, it is rejected again.
No matter how many times you try, you’re not getting in.
So you shut off the power. Reboot and try again.
Almost always the problem is cleared and your password is accepted.

But once it’s been rejected, that’s it, you’re going to have to reboot.

I don’t know if I should be posting this here or in the Qubes forum but I have / have had Qubes running on 3 different machines and it has never happened on either of the other 2.

As far as I can remember version of Pureboot is 21.

Anyone have any suggestions, does it happen to you?

Thanks.

If you have a second keyboard, does the issue persist if you swap keyboards when this happens? Or even just reconnecting the keyboard instead of rebooting? I’ve seen reports of different keyboard issues with regard to the boot firmware, though normally they’re either always an issue or never, this would be the first intermittent if that even turns out to be related.

Just a thought.

Yes, thanks, I wondered if it was a keyboard connection issue and I have changed the keyboard for another of the same make and type but the problem is exactly the same. (I don’t have any others with USB connectors to try).

It used to be worse but I think then I had left the mouse’s USB connected and it seemed to be made worse by my moving either the keyboard or the mouse about - like there was some random signal getting sent just by moving one or other device - perhaps indicating a faulty USB connection at the mini’s end but, as I recall, the problem is the same via others of the mini’s USBs.

I’ll have to try changing which USB socket the keyboard is connected to and see if it makes any difference because I don’t remember if I did try that for sure; it’s been doing this for the year I’ve had it.

I upgraded Pureboot and now remember to never connect the mouse or move the keyboard about and it seems to have reduced the incidents to the occasional 1 in about 5 logins. So either the Pureboot upgrade helped or, more likely, it looks like it is to do with having something connected via USB.

But of course I have to have the keyboard connected to enter the decryption pass-phrase.

I don’t think moving the keyboard about has any effect anymore - I’ll have to experiment over the next week or so to see.

@MrChromebox may be able to shed some light on diagnostic options on this front.

I had this problem and found that typing in my password really slooooowly got me in. Like 2 secs between characters. I posted about with no replies on the qubes forum. It kept doing it so I reinstalled in the end.

I don’t think he works for Purism anymore.

I figure he’s still part of the forum community and still has the knowledge to help with the software he’s been involved with for years. Whether he chooses to visit an contribute his time to the forum is up to him regardless of his status with purism, the same as anyone else on these forums though that’s heading toward a conversation for another thread :slight_smile:

Thanks guys,

So @Brad you had this same problem on a mini V2 with Pureboot, right?

And the re-install of Qubes sorted it out?

I know what you mean about typing the disk phrase in very slowly. It can take 2 seconds for each little black circle - representing an entered character - to show up in the entry box. I’m guessing you had that, too?

Have you (or anyone else) had this issue on any computer other than the mini V2?

Thanks.

No. Mine is on a Lenovo with coreboot, but I found reference to the problem somewhere with that “solution”. And yes, a reinstall fixed it.

2 Likes