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

Qubes doesn't boot with kernel 4.4.12 and 4.4.14 on skylake notebook #2186

Closed
minad opened this Issue Jul 20, 2016 · 16 comments

Comments

Projects
None yet
4 participants
@minad

minad commented Jul 20, 2016

Qubes OS version (e.g., R3.1):

R3.2rc1 with 4.4.12 and 4.4.14 from unstable

Affected TemplateVMs (e.g., fedora-23, if applicable):

dom0


Expected behavior:

I would expect the default kernel to work on recent hardware.

Actual behavior:

R3.2rc1 has the 4.4.12 kernel by default. However with this kernel the notebook doesn't boot. After grub the notebook just restarts. The kernel 4.2.8 works but the system doesn't run very stable. Since Linux starting from 4.4 has proper Skylake support, I guess using a newer kernel would make sense?

Steps to reproduce the behavior:

Boot 4.4.12 or 4.4.14 on skylake.

General notes:

It might be that some binary blobs are missing from the initramfs as was suggested on the mailing list (see below).


Related issues:

@minad minad changed the title from Qubes OS doesn't boot with kernel 4.4.12 and 4.4.14 on skylake notebook to Qubes doesn't boot with kernel 4.4.12 and 4.4.14 on skylake notebook Jul 20, 2016

@andrewdavidwong andrewdavidwong added this to the Release 3.2 milestone Jul 20, 2016

@thomwiggers

This comment has been minimized.

Show comment
Hide comment
@thomwiggers

thomwiggers Aug 3, 2016

Qubes R3.2-rc2 is working for me on an XPS 13 with i5-6200U

Qubes R3.2-rc2 is working for me on an XPS 13 with i5-6200U

@minad

This comment has been minimized.

Show comment
Hide comment
@minad

minad Aug 4, 2016

I am using a Lenovo Yoga X1 with i5, for which it didn't work with rc1. I have rc2 installed, but didn't try the new kernel yet. I will do so later.

minad commented Aug 4, 2016

I am using a Lenovo Yoga X1 with i5, for which it didn't work with rc1. I have rc2 installed, but didn't try the new kernel yet. I will do so later.

@minad

This comment has been minimized.

Show comment
Hide comment
@minad

minad Aug 5, 2016

I just tried it again with 4.4.14-11 and i915.preliminary_hw_support=0 and i915.preliminary_hw_support=1. My cpu is also i5-6200U

@thomwiggers which kernel version and kernel arguments are you using? Did you do generate your own initial ram disk with some special binary blobs (I think something like this was suggested in the aforementioned mailing list posts)?

minad commented Aug 5, 2016

I just tried it again with 4.4.14-11 and i915.preliminary_hw_support=0 and i915.preliminary_hw_support=1. My cpu is also i5-6200U

@thomwiggers which kernel version and kernel arguments are you using? Did you do generate your own initial ram disk with some special binary blobs (I think something like this was suggested in the aforementioned mailing list posts)?

@thomwiggers

This comment has been minimized.

Show comment
Hide comment
@thomwiggers

thomwiggers Aug 5, 2016

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Sep 24, 2016

Contributor

@minad Have you made any progress on this? I'm having the same problem.

Contributor

jpouellet commented Sep 24, 2016

@minad Have you made any progress on this? I'm having the same problem.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Sep 25, 2016

Contributor

The 4.4 initramfs contains usr/lib/firmware/i915/skl_{dmc_ver1{,_23},guc_ver4{,_3}}.bin, the 4.1 initramfs does not contain any i915 firmware. The issue appears to be elsewhere, idk.

Contributor

jpouellet commented Sep 25, 2016

The 4.4 initramfs contains usr/lib/firmware/i915/skl_{dmc_ver1{,_23},guc_ver4{,_3}}.bin, the 4.1 initramfs does not contain any i915 firmware. The issue appears to be elsewhere, idk.

@thomwiggers

This comment has been minimized.

Show comment
Hide comment
@thomwiggers

thomwiggers Sep 25, 2016

Are you perhaps using that Yoga that doesn't support Linux / anything without Intel RST RAID drivers? See this comment on this thread and also this post

thomwiggers commented Sep 25, 2016

Are you perhaps using that Yoga that doesn't support Linux / anything without Intel RST RAID drivers? See this comment on this thread and also this post

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Sep 25, 2016

Contributor

Nope. 4th gen x1 carbon, runs other OSes just fine (non-qubes linux, pre-4.4-kernel qubes, OpenBSD, etc.). Just problems with qubes with kernels > 4.1 (/ >= 4.4, idk. i haven't started bisecting yet. Hoping for an easier solution.

Contributor

jpouellet commented Sep 25, 2016

Nope. 4th gen x1 carbon, runs other OSes just fine (non-qubes linux, pre-4.4-kernel qubes, OpenBSD, etc.). Just problems with qubes with kernels > 4.1 (/ >= 4.4, idk. i haven't started bisecting yet. Hoping for an easier solution.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@minad

This comment has been minimized.

Show comment
Hide comment
@minad

minad Sep 26, 2016

No progress from my side. I didn't dig deeper. Bisecting is the right thing to do but too time consuming for me right now. I am still using the old 4.2.8 kernel in dom0

minad commented Sep 26, 2016

No progress from my side. I didn't dig deeper. Bisecting is the right thing to do but too time consuming for me right now. I am still using the old 4.2.8 kernel in dom0

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Sep 26, 2016

Contributor

Seems my issue was actually UEFI trouble. @minad see if https://www.qubes-os.org/doc/uefi-troubleshooting/ fixes it for you. It appears to have fixed it for me.

Contributor

jpouellet commented Sep 26, 2016

Seems my issue was actually UEFI trouble. @minad see if https://www.qubes-os.org/doc/uefi-troubleshooting/ fixes it for you. It appears to have fixed it for me.

@minad

This comment has been minimized.

Show comment
Hide comment
@minad

minad Oct 24, 2016

@jpouellet Could you please post your xen.cfg, mine is empty and the documentation talks about kernel sections? If I understand correctly the changes to the xen.cfg are the only changes necessary since my system is already installed.

minad commented Oct 24, 2016

@jpouellet Could you please post your xen.cfg, mine is empty and the documentation talks about kernel sections? If I understand correctly the changes to the xen.cfg are the only changes necessary since my system is already installed.

@minad

This comment has been minimized.

Show comment
Hide comment
@minad

minad Oct 24, 2016

Ok, found the problem. I had a legacy bios installation. Legacy and UEFI were activated and it seems that qubes did a bios install back then. After a reinstall with UEFI in the bios everything works without tweaking. Stability seems to be improved compared to the 4.2.8 kernel.

I guess it is ok to close this. It might be good to mention in the install instructions that UEFI should be preferred?

minad commented Oct 24, 2016

Ok, found the problem. I had a legacy bios installation. Legacy and UEFI were activated and it seems that qubes did a bios install back then. After a reinstall with UEFI in the bios everything works without tweaking. Stability seems to be improved compared to the 4.2.8 kernel.

I guess it is ok to close this. It might be good to mention in the install instructions that UEFI should be preferred?

@minad minad closed this Oct 24, 2016

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Oct 24, 2016

Contributor

That looks more like the config you have in the actual installer image rather than the one installed to your running machine.

Mine looks like:

[global]
default=4.4.14-11.pvops.qubes.x86_64

[4.4.14-11.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-XXX-your-disk-guid-here-XXX rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet rd.qubes.hide_all_usb
ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img

[4.4.14-11.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-XXX-your-disk-guid-here-XXX rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet rd.qubes.hide_all_usb
ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img
Contributor

jpouellet commented Oct 24, 2016

That looks more like the config you have in the actual installer image rather than the one installed to your running machine.

Mine looks like:

[global]
default=4.4.14-11.pvops.qubes.x86_64

[4.4.14-11.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-XXX-your-disk-guid-here-XXX rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet rd.qubes.hide_all_usb
ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img

[4.4.14-11.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-XXX-your-disk-guid-here-XXX rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet rd.qubes.hide_all_usb
ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img
@minad

This comment has been minimized.

Show comment
Hide comment
@minad

minad Oct 24, 2016

@jpouellet Thx! Yes you are right about the installer configuration. I was able to generate a similar configuration like yours by using the installer xen.cfg and then reinstalling the kernel.
Then I tried to convert my installation from bios to uefi, but it proved to be too time consuming. Finally I just did a fresh reinstall.

minad commented Oct 24, 2016

@jpouellet Thx! Yes you are right about the installer configuration. I was able to generate a similar configuration like yours by using the installer xen.cfg and then reinstalling the kernel.
Then I tried to convert my installation from bios to uefi, but it proved to be too time consuming. Finally I just did a fresh reinstall.

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