Re: [qubes-users] F2 stoped working after last kernel update

2019-09-18 Thread dimi
> > It wasn't the boot sequence itself I thought might be unsafe, but the > process of converting a functioning UEFI Qubes install over to it could > pretty easily end up with a non-booting system. That could be painful to > recover from, depending on one's comfort level. Let's call it a

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-18 Thread Claudia
'awokd' via qubes-users: Claudia: So I'm not sure why it would be unsafe. In fact I'm thinking about manually enabling grub (in UEFI mode) just to ease troubleshooting in the future should I ever run into any boot issues. Just my take, but I could be wrong. It wasn't the boot sequence itself

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-18 Thread 'awokd' via qubes-users
Claudia: > So I'm not sure why it would be unsafe. In fact I'm thinking about > manually enabling grub (in UEFI mode) just to ease troubleshooting in > the future should I ever run into any boot issues. Just my take, but I > could be wrong. It wasn't the boot sequence itself I thought might be

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-18 Thread Claudia
'awokd' via qubes-users: dimi: Could not find a solution how, if even possible to pick which kernel to boot or/and modify kernel parameters before booting like i am used from grub by pressing 'e'. Does UEFI Boot support this or/and how can i safely switch my setup to grub boot? I would like to

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-18 Thread 'awokd' via qubes-users
dimi: > Could not find a solution how, if even possible to pick which kernel to > boot or/and modify kernel parameters before booting like i am used from > grub by pressing 'e'. > Does UEFI Boot support this or/and how can i safely switch my setup to grub > boot? I would like to see what

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-18 Thread dimi
> Looks like you're using UEFI boot instead of grub, so kernel options are > right next door to the Xen options in xen.cfg- look one line down for > "kernel=". :) This is where I see rhgb quiet. > Plymouth.ignore-serial-consoles is new; you might also try removing, but > it could be there

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-17 Thread 'awokd' via qubes-users
dimi: > There is no rhgb quiet in /boot/efi/EFI/qubes/xen.cfg > I have been pressing just F2 to unlock Kernel with passphrase for over a > year now and i was being able to read dmesg messages until XFCE login > prompt. > Already tried combinations of ctrl-alt-F2, alt-ctrl-Fx, alt-Fx and none

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-17 Thread dimi
> Check to make sure "rhgb quiet" didn't get added to your boot options. > Also, isn't it ctrl-alt-F2, or is that only once inside XFCE? > There is no rhgb quiet in /boot/efi/EFI/qubes/xen.cfg I have been pressing just F2 to unlock Kernel with passphrase for over a year now and i was being

Re: [qubes-users] F2 stoped working after last kernel update

2019-09-13 Thread 'awokd' via qubes-users
dimi: > We used to be able to switch to console when typing password or after to > see messages, now just black screen. > Pressing F2 again shows GUI. > Check to make sure "rhgb quiet" didn't get added to your boot options. Also, isn't it ctrl-alt-F2, or is that only once inside XFCE? -- -

[qubes-users] F2 stoped working after last kernel update

2019-09-11 Thread dimi
We used to be able to switch to console when typing password or after to see messages, now just black screen. Pressing F2 again shows GUI. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails