Upgrades for dom0-Qubes 4; on system reboot skips plymouth, usb kb dies, can't enter decrypt pw
qubert
[FAILED] Failed to start Setup Virtual Console
Second vis error:
[FAILED] Failed to start Show Plymouth Boot Screen.
No problem, eh? Because a few lines later, it prompts me for the passphrase for the encrypted disk. Awesome.
But every time, as soon as it gets there, my keyboard light goes dead, and I of course can't type anything in.
I have tried four different keyboards. All keyboards are USB, three are wired, one wireless. Have also tried multiple different usb ports, some usb 2.0 and some usb 3.
Have been using the system just like this for many months with two different usb keyboards. Nothing changed except running the dom0 upgrade (from qubes manager right-click), and I rebooted immediately after.
When I edit the boot options by eliminating "quiet" I get exactly the same prompt for the luks decrypt password, except it adds this as the final logging line (this line also overwrites the area in which I should be entering the decrypt pw):
[ 3.407261] clocksource: Switched to clocksource tsc
Removing 'rhgb' in addition to quiet eliminates the plymouth boot error, but I still get dumped out onto the terminal password entry line and as soon as that line comes up the keyboard light goes off every time!
Obviously without a keyboard, I can't even get tty, much less enter the unlock passphrase.
I'm effectively locked out, and before I start messing with it and changing things, thought I would ask to see if anyone out there knows what might be wrong????
Thanks!
Lorenzo Lamas
You can try removing rd.qubes.hide_all_usb from boot options, if it is present.
swco...@gmail.com
Thanks for the suggestion. I don't have that setting. :(
swco...@gmail.com
Update:
I was able to boot into the system from a usb drive running qubes (rescue).
In /mnt/sysimage/boot I can see that the update likely went from 4.14.18-1 to 4.14.74-1.
I can also successfully mount the vm's in /dev/qubes_dom0/ -- at least the few that I've tried, and can access their folder structures.
Obviously since I can now access this via the latest qubes build in rescue mode, and I'm back to my original hardware and rescue is running, there must be something in the update that hosed the system--drivers? I AM running an nvidia card--and I'm aware they can be troublesome. I have an AMD I can try if necessary.
Thanks in advance for any advice!
qubert
Swapped out the nvidia for an amd card. No change. So, switched back.
I'm running out of time. This has now been down over a week.
Tons of research on plymouth boot and the other error, but nothing relevant.
Ideas?
Aly Abdellatif
Try to update to kernel 4.19
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel kernel-qubes-vm
This will download the newer kernel and the kernel for your vms(this version is in the current testing repository which means it’s not the stable version yet(4.14* is).
I’ve been using 4.19 for 2 weeks without a problem.
You will then install it with sudo dnf install kernel-4.19*
And dnf install kernel-qubes-vm-4.19* if it didn’t install it in the previous command.
After that if you are in uefi , check in the xen.cfg that default= your new version of kernel
Nouveau is enabled by default , you should add that to your kernel line :
nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off.
This will disable nouveau and your discrete card(nvidia).
For the keyboard and mouse, Did you create a sys-usb vm(qube vm for usbs)?
Can you show us the output of dmesg -l err ?
Aly