After updating Fedora and dom0 yesterday, today my laptop entered into a boot 
loop, stopping some seconds right after the initramfs line and re-booting

Hardware: Lenovo X1 Carbon 6th Gen
Booting with UEFI, dual boot with Windows

After a lot of unsuccessful googling I booted the laptop with a Qubes-OS USB 
drive and checked the content of xen.cfg located on the EFI partition:

--------
[global]
default=4.14.103-1.pvops.qubes.x86_64

[4.14.74-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx 
ucode=scan smt=off
kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root 
rd.luks.uuid=luks-9b85a28f-01a5-4914-be0b-0605d066b610 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb 
quiet rd.qubes.hide_all_usb
ramdisk=initramfs-4.14.74-1.pvops.qubes.x86_64.img
[4.14.103-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx 
ucode=scan smt=off
kernel=vmlinuz-4.14.103-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root 
rd.luks.uuid=luks-9b85a28f-01a5-4914-be0b-0605d066b610 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb 
quiet rd.qubes.hide_all_usb
ramdisk=initramfs-4.14.103-1.pvops.qubes.x86_64.img
----------

Only after changing to default=4.14.74-1.pvops.qubes.x86_64 can boot my system 
again.
NOTE: deleting 'iommu=no-igfx' did not solve the problem

Does anybody know what is the problem? 
Is this a problem with the upated kernel version?
What is happening with future updates? Shall I apply them?

Thank you in advance for your time!

-- 
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/c389d3d6-077f-46d9-9442-acac887548ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to