Any update on this?

I just encountered a similar problem:

- Qubes 3.2 indicated there was an update for dom0
- I updated via the graphical utility, installed kernel 
4.9.35-19.pvops.qubes.x86_64
- Rebooted

Upon reboot, `uname -a` indicates I'm still running the old kernel.

So I tried manually running: sudo qubes-dom0-update 
--enablerepo=qubes-dom0-unstable kernel kernel-qubes-vm --best --allowerasing

It downloaded stuff (for some reason from "Fedora 23" repo even though I 
thought I'd updated to Fedora 25? Or is that separate - just for TemplateVM?) 
and then said, among other things:

"Package kernel-qubes-vm-1000:4.9.35-19.pvops.qubes.x86_64 is already 
installed, skipping"


Makes no sense! What do I do?

Like this fellow below, I do not appear to have any GRUB related things on my 
system being used.

Is there a way to force the machine to switch to using GRUB? Perhaps some BIOS 
option?

This is the machine I'm using: 
https://groups.google.com/forum/#!topic/qubes-users/0JTfsfPVl9w 
<https://groups.google.com/forum/#!topic/qubes-users/0JTfsfPVl9w>

Thanks for any help!

- Greg

--
Please do not email me anything that you are not comfortable also sharing with 
the NSA.

> On Apr 22, 2017, at 12:15 PM, hft.huu...@gmail.com 
> <mailto:hft.huu...@gmail.com> wrote:
> 
> --UPDATE--
> So, I did try copying the new kernel to my /boot/efi/EFI/qubes/ directory and 
> edited the xen.cfg file. It broke my system. I got:
> [ TIME ] Timed out waiting for device <device name>
> [DEPEND] Dependency failed for Cryptography Setup for <luks-device>
> [DEPEND] Dependency failed for Encrypted Volumes.
> But luckily I could recover my system by editing xen.cfg back to original by 
> using rescue usb.
> 
> I tried to reinstall grub by: sudo grub2-install
> "grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. 
> Please specify --target or --directory"
> Is this a normal error while in UEFI mode? Or is there something not right 
> with my system?
> 
> I am to lazy to reinstall my system right now to see if the encrypted /boot 
> directory is the problem.
> 
> I'll keep this post updated whenever I decide to reinstall Qubes.
> 
> --
> 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 
> <mailto:qubes-users+unsubscr...@googlegroups.com>.
> To post to this group, send email to qubes-users@googlegroups.com 
> <mailto:qubes-users@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/b1417c4f-18a3-4653-9b95-6a9fce54d6fd%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/qubes-users/b1417c4f-18a3-4653-9b95-6a9fce54d6fd%40googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <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/4B494A8E-2B13-4696-B8EF-A279C260F86F%40taoeffect.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to