Blank screen on boot after installation

Shashank

unread,

Mar 23, 2018, 9:56:05 AM3/23/18

to qubes-users

Hi,

I am trying to run qubes 4.0-5 on my HP ENVY TS sleekbook 4. I am able to get past the installation successfully but on reboot after installing the system goes blank after initial set of text flow.

System config:
Processor: Intel i5-3337u @ 1.80 GHZ
Memory : 4.0 GHZ
Intel(R) HD Graphics 4000
Virtualization enabled

Is there anything I can do to get Qubes running on my machine?

Thanks

awokd

unread,

Mar 23, 2018, 10:15:56 AM3/23/18

to Shashank, qubes-users

Can you confirm you have "i915.alpha_support=1" in your config file? See
https://www.qubes-os.org/doc/intel-igfx-troubleshooting/.

Shashank

unread,

Mar 23, 2018, 10:44:18 AM3/23/18

to qubes-users

I am not able to boot into the qubes system so I wouldn't be able to use the terminal in dom0. But I did use debian to check the /boot/efi/EFI/qubes/xen.cfg file. The file did not have i915.... Either I am looking in the wrong place or doing something wrong. Should I be looking else where?

Thanks

Shashank

unread,

Mar 23, 2018, 10:59:44 AM3/23/18

to qubes-users

I also looked into xen.efi but I couldn’t find the i915 line

awokd

unread,

Mar 23, 2018, 11:00:05 AM3/23/18

to Shashank, qubes-users

Sounds like you are in the right spot. Can you try to add it there?

Shashank

unread,

Mar 23, 2018, 11:06:41 AM3/23/18

to qubes-users

Any specs as to where that needs to be added? Specific line?
And i915.alpha_support=1 needs to be added right?

awokd

unread,

Mar 23, 2018, 11:12:28 AM3/23/18

to Shashank, qubes-users

On Fri, March 23, 2018 3:06 pm, Shashank wrote:

> Any specs as to where that needs to be added? Specific line?

kernel= line in xen.cfg. If you want to copy & paste what you're looking
at, I can tell you exactly.

> And i915.alpha_support=1 needs to be added right?

That is my theory, but I'm not 100% positive it will fix it!

Shashank

unread,

Mar 23, 2018, 11:17:38 AM3/23/18

to qubes-users

So below is exactly what is in /boot/efi/EFI/qubes/xen.cfg file:

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

[4.14.18-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd$
ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img

awokd

unread,

Mar 23, 2018, 11:29:07 AM3/23/18

to Shashank, qubes-users

On Fri, March 23, 2018 3:17 pm, Shashank wrote:

> So below is exactly what is in /boot/efi/EFI/qubes/xen.cfg file:
>
>
> [global]
> default=4.14.18-1.pvops.qubes.x86_64
>
> [4.14.18-1.pvops.qubes.x86_64]
> options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
> kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64
> root=/dev/mapper/qubes_dom0-root rd$
> ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img
>
> [4.14.18-1.pvops.qubes.x86_64]
> options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
> kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64
> root=/dev/mapper/qubes_dom0-root rd$
> ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img

Do your kernel= lines actually end with just "rd$", or it that your editor
telling you there is more there and you have to arrow right to see it?

If they do actually end with "rd$" (or if they don't but you scroll all
the way right and still don't see the option), try adding the i915 option
before it, like:

kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64
root=/dev/mapper/qubes_dom0-root i915.alpha_support=1 rd$

Shashank

unread,

Mar 23, 2018, 12:00:50 PM3/23/18

to qubes-users

Sorry for the missing info, there was i915... in the full file before it wasn't missing!! 'MY BAD!!!'. But below is how the full file looks. Without me adding the i915.. manually.

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

[4.14.18-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx

kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-9ebf6c19-501d-4120-b5ac-06123c5bc68a rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb quiet
ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img

[4.14.18-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root

rd.luks.uuid=luks-9ebf6c19-501d-4120-b5ac-06123c5bc68a rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb quiet
ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img

Anything you can guide me to do for qubes to boot correctly

Thanks.

Shashank

unread,

Mar 23, 2018, 12:20:00 PM3/23/18

to qubes-users

Is it something with the graphics that is causing the problem?

thanks

awokd

unread,

Mar 23, 2018, 12:24:12 PM3/23/18

to Shashank, qubes-users

On Fri, March 23, 2018 4:00 pm, Shashank wrote:

> Sorry for the missing info, there was i915... in the full file before it
> wasn't missing!! 'MY BAD!!!'. But below is how the full file looks.
> Without me adding the i915.. manually.

No problem! These files look fine to me, but that means my theory is no
good. Is VT-x and VT-d enabled in your BIOS?

> [global]
> default=4.14.18-1.pvops.qubes.x86_64
>
> [4.14.18-1.pvops.qubes.x86_64]
> options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
> kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64
> root=/dev/mapper/qubes_dom0-root
> rd.luks.uuid=luks-9ebf6c19-501d-4120-b5ac-06123c5bc68a
> rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1
> rhgb quiet ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img
>
> [4.14.18-1.pvops.qubes.x86_64]
> options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
> kernel=vmlinuz-4.14.18-1.pvops.qubes.x86_64
> root=/dev/mapper/qubes_dom0-root
> rd.luks.uuid=luks-9ebf6c19-501d-4120-b5ac-06123c5bc68a
> rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1
> rhgb quiet ramdisk=initramfs-4.14.18-1.pvops.qubes.x86_64.img
>
> Anything you can guide me to do for qubes to boot correctly
>
>
> Thanks.
>
>

> --
> 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...@googlegroups.com. To post to this group,
> send email to qubes...@googlegroups.com. To view this discussion on the
> web visit
> https://groups.google.com/d/msgid/qubes-users/6ac58ca5-815b-4da8-bab4-33d
> 076e49fea%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>

Shashank

unread,

Mar 23, 2018, 12:32:10 PM3/23/18

to qubes-users

Yes in the bios settings the virtualization is enabled. I don't see anything else that is required by qubes os to run on the computer.

Installation completes without a hitch so this has got me confused as to what could be wrong!!!

awokd

unread,

Mar 23, 2018, 1:07:45 PM3/23/18

to Shashank, qubes-users

On Fri, March 23, 2018 4:32 pm, Shashank wrote:

> Yes in the bios settings the virtualization is enabled. I don't see
> anything else that is required by qubes os to run on the computer.
>
> Installation completes without a hitch so this has got me confused as to
> what could be wrong!!!

If you installed in UEFI mode, you might try step #11 under
https://www.qubes-os.org/doc/uefi-troubleshooting/#cannot-start-installation-installation-completes-successfully-but-then-bios-loops-at-boot-device-selection-hangs-at-four-penguins-after-choosing-test-media-and-install-qubes-os-in-grub-menu
.
Or switching to legacy mode and reinstalling.

Shashank

unread,

Mar 23, 2018, 2:15:08 PM3/23/18

to qubes-users

I think Legacy mode is the only option now.

Reply all

Reply to author

Forward