New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not starting Dom0 after updates with 4.9.56-21.pvops.qubes.x86_64 #3625

Closed
loadcorp opened this Issue Feb 23, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@loadcorp

Qubes OS version:

R3.2

Affected TemplateVMs:

Dom0


Steps to reproduce the behavior:

  1. Install Qubes 3.2.
  2. Update all (from Dom0 to all VM).

Expected behavior:

Normal loading like older kernel.

Actual behavior:

Not loading the kernel version 4.9.56-21.pvops.qubes.x86_64.

General notes:

After updating I have 2 options in Grub Boot Menu:

  1. Qubes, with Xen 4.6.6 and Linux 4.4.14-11.pvops.qubes.x86_64
  2. Qubes, with Xen 4.6.6 and Linux 4.9.56-21.pvops.qubes.x86_64

First one working like before updates, but second just rebooting computer.

@tonsimple

This comment has been minimized.

Show comment
Hide comment
@tonsimple

tonsimple Feb 24, 2018

Do you happen to have an Intel video card by any chance?

Because there is a "won't boot" problem with most recent kernels and Intel integrated graphics #3165

tonsimple commented Feb 24, 2018

Do you happen to have an Intel video card by any chance?

Because there is a "won't boot" problem with most recent kernels and Intel integrated graphics #3165

@loadcorp

This comment has been minimized.

Show comment
Hide comment
@loadcorp

loadcorp Feb 24, 2018

@tonsimple Yes, I have the Intel integrated video card in motherboard.

You wan't to tell me that I must to try with discrete video card? Is it will resolve the problem? Or is there another solution to the problem?

@tonsimple Yes, I have the Intel integrated video card in motherboard.

You wan't to tell me that I must to try with discrete video card? Is it will resolve the problem? Or is there another solution to the problem?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 25, 2018

Member

Duplicate of #3165

Member

andrewdavidwong commented Feb 25, 2018

Duplicate of #3165

@andrewdavidwong andrewdavidwong marked this as a duplicate of #3165 Feb 25, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 25, 2018

Member

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Member

andrewdavidwong commented Feb 25, 2018

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment