Re: [qubes-users] Re: Last dom0 update broke 3.2
On Sun, Nov 12, 2017 at 5:18 PM, Yuraeitha wrote: > On Sunday, November 12, 2017 at 7:52:10 PM UTC, Francesco wrote: > > After last dom0 update it properly restarted but gave some qubes manager > errors. > > > > > > Second restart keeps restarting on a loop Every time giving the enclosed > screen. > > > > > > Best > > Fran > > I'd suspect you can probably bypass it by selecting your old kernel before > the update. I've had that issue a few times my self on Qubes and various > other Linux systems. If you run Grub, then instead select "Advanced" and go > in and select the second kernel instead of the top one (which is the newly > installed and now default kernel). > The lowest kernel is the one installed before the one that worked before. > Qubes saves up to 3 kernels by default, if needed it can be extended > indefinitely, but 3 is usually enough. > It worked. Many thanks. I had to use supergrubdisk.org USB booting key and with that was able to choose which kernel to boot on. Many thanks it saved my work. Best Fran > > If you installed Qubes over EFI/UEFI instead of Legacy BIOS, then you'll > need to pick a live boot medium, or use the Qubes installer to enter rescue > mode, and then navigate to your /boot/efi/'somewhere here abouts' and find > your xen.cfg file. In this file you can edit which kernel EFI boot mode > should boot with. > > If any of the associated kernel/module updates broke something else, like > for example a hardware like Wifi/networking, then it becomes much more > tricky. It's often, in my experence at least, typically easy to recover > from bad kernels and at least boot it up. The question is more, if > something else stopped working too, albeit in my experience it's typically > enough to just pick the last kernel. > > Also, if you succesfully get into Qubes again, then I'd recommend you > increase your max saved kernels with 'sudo nano /etc/dnf/dnf.conf' and > locate the line called Installonly_limit=3 to 5 or abouts. > > The reasoning for this, is because if another future kernel upgrade also > fails, then you'll get no more chances of easy recovery if all working > kernels were automatically deleted during the update. If you set it to 5, > it'll then save 5 kernels. > > Just be sure your kernel partition has enough disk space to house older > kernels associated with the number of kernels you choose to save. > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/qubes-users/0db23e3e-aa44-4e91-85f3-4eacb4467abd%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAPzH-qA%2BG0NQKmQgjLUEhM5pHgwX1q2WMXaSZrmwfN4E8eYrdw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Last dom0 update broke 3.2
On Nov 18, 2017 17:36, "Ron Qubed" wrote: On Sunday, November 12, 2017 at 12:52:10 PM UTC-7, Francesco wrote: > After last dom0 update it properly restarted but gave some qubes manager errors. > > > Second restart keeps restarting on a loop Every time giving the enclosed screen. > > > Best > Fran I ran into something similar after my first Qubes 3.2 install. I did some tinkering with the USB to get my USB keyboard and mouse working again after setting up sys-usb the default way (having missed the warning). I think I broke something along the way. It worked for a while with some warnings messages during boot. But finally, one of the updates broke it completely, and I couldn't boot without a kernel panic. I just re-installed and did the USB setup right the second time around. Didn't lose anything essential thanks to having moved the appvms to a separate drive (though it took me a little while to figure out how to restore them). Thanks, but I did not move the appvms to a separate drive. Just default installation. Is there a way to reinstall without loosing them? Ron -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/qubes-users/63d8d582-7bbb-40e1-aa03-1b4458bdc047%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAPzH-qBOfYBXCDeGGFb4zt18YPRP9Aq7uhuF4DzJnDHcG8q6QQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Last dom0 update broke 3.2
On Nov 12, 2017 17:18, "Yuraeitha" wrote: On Sunday, November 12, 2017 at 7:52:10 PM UTC, Francesco wrote: > After last dom0 update it properly restarted but gave some qubes manager errors. > > > Second restart keeps restarting on a loop Every time giving the enclosed screen. > > > Best > Fran I'd suspect you can probably bypass it by selecting your old kernel before the update. I've had that issue a few times my self on Qubes and various other Linux systems. If you run Grub, Many thanks. Sorry for the late reply. Only now I am seeing your post and replying with a cellphone because computer does not start. How may I run Grub if the computer does not start? then instead select "Advanced" and go in and select the second kernel instead of the top one (which is the newly installed and now default kernel). The lowest kernel is the one installed before the one that worked before. Qubes saves up to 3 kernels by default, if needed it can be extended indefinitely, but 3 is usually enough. If you installed Qubes over EFI/UEFI instead of Legacy BIOS, I remember installed it over Legacy BIOS then you'll need to pick a live boot medium, or use the Qubes installer to enter rescue mode, Understand that thanks. I will try Monday when back home where do have the Qubes installer. But may I run Grub with a Qubes installer? and then navigate to your /boot/efi/'somewhere here abouts' and find your xen.cfg file. In this file you can edit which kernel EFI boot mode should boot with. If any of the associated kernel/module updates broke something else, like for example a hardware like Wifi/networking, then it becomes much more tricky. It's often, in my experence at least, typically easy to recover from bad kernels and at least boot it up. The question is more, if something else stopped working too, albeit in my experience it's typically enough to just pick the last kernel. Hope so Also, if you succesfully get into Qubes again, then I'd recommend you increase your max saved kernels with 'sudo nano /etc/dnf/dnf.conf' and locate the line called Installonly_limit=3 to 5 or abouts. The reasoning for this, is because if another future kernel upgrade also fails, then you'll get no more chances of easy recovery if all working kernels were automatically deleted during the update. If you set it to 5, it'll then save 5 kernels. Got it. Thanks Just be sure your kernel partition has enough disk space to house older kernels associated with the number of kernels you choose to save. Which is the name of kernel partition? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/qubes-users/0db23e3e-aa44-4e91-85f3-4eacb4467abd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAPzH-qDDVX4DSWks7qrswUKAC35GeqLh9cYhbmEa9Z2esaT0Aw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Last dom0 update broke 3.2
On Sunday, November 12, 2017 at 12:52:10 PM UTC-7, Francesco wrote: > After last dom0 update it properly restarted but gave some qubes manager > errors. > > > Second restart keeps restarting on a loop Every time giving the enclosed > screen. > > > Best > Fran I ran into something similar after my first Qubes 3.2 install. I did some tinkering with the USB to get my USB keyboard and mouse working again after setting up sys-usb the default way (having missed the warning). I think I broke something along the way. It worked for a while with some warnings messages during boot. But finally, one of the updates broke it completely, and I couldn't boot without a kernel panic. I just re-installed and did the USB setup right the second time around. Didn't lose anything essential thanks to having moved the appvms to a separate drive (though it took me a little while to figure out how to restore them). Ron -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/63d8d582-7bbb-40e1-aa03-1b4458bdc047%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Last dom0 update broke 3.2
On Sunday, November 12, 2017 at 7:52:10 PM UTC, Francesco wrote: > After last dom0 update it properly restarted but gave some qubes manager > errors. > > > Second restart keeps restarting on a loop Every time giving the enclosed > screen. > > > Best > Fran I'd suspect you can probably bypass it by selecting your old kernel before the update. I've had that issue a few times my self on Qubes and various other Linux systems. If you run Grub, then instead select "Advanced" and go in and select the second kernel instead of the top one (which is the newly installed and now default kernel). The lowest kernel is the one installed before the one that worked before. Qubes saves up to 3 kernels by default, if needed it can be extended indefinitely, but 3 is usually enough. If you installed Qubes over EFI/UEFI instead of Legacy BIOS, then you'll need to pick a live boot medium, or use the Qubes installer to enter rescue mode, and then navigate to your /boot/efi/'somewhere here abouts' and find your xen.cfg file. In this file you can edit which kernel EFI boot mode should boot with. If any of the associated kernel/module updates broke something else, like for example a hardware like Wifi/networking, then it becomes much more tricky. It's often, in my experence at least, typically easy to recover from bad kernels and at least boot it up. The question is more, if something else stopped working too, albeit in my experience it's typically enough to just pick the last kernel. Also, if you succesfully get into Qubes again, then I'd recommend you increase your max saved kernels with 'sudo nano /etc/dnf/dnf.conf' and locate the line called Installonly_limit=3 to 5 or abouts. The reasoning for this, is because if another future kernel upgrade also fails, then you'll get no more chances of easy recovery if all working kernels were automatically deleted during the update. If you set it to 5, it'll then save 5 kernels. Just be sure your kernel partition has enough disk space to house older kernels associated with the number of kernels you choose to save. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0db23e3e-aa44-4e91-85f3-4eacb4467abd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
