Re: [qubes-users] AEM boot = GPU hang, no graphics display
On 24.05.2018 04:12, awokd wrote: Not sure if it's related or why AEM would have modified it, but try changing that i915 option to i915.alpha_support=1 (like https://www.qubes-os.org/doc/intel-igfx-troubleshooting/#software-rendering-or-video-lags). As noted on qubes-issues, I had to remove "iommu=no-igfx" from Xen options to get graphics working. Another side-effect that AEM/tboot has, unfortunately, is that sleep/suspend no longer works (now it causes an unintended reboot when entering sleep). But its been a long time since this combination worked. Chris -- 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/97d31bc76ff997cbe3722cad70d1b089%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] AEM boot = GPU hang, no graphics display
After setting up anti-evil-maid in R4.0 my laptop is unable to boot into a usable desktop: The resulting display is just a static wall of random stripes appearing before passphrase prompts; here I can press Esc for text mode. After the disk comes online the graphics stripes return and I can't use the GUI. I can log in to a console terminal and access dmesg which has the following messages (grep i915): [0.00] Kernel command line: placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-dcf904cf-4f9e-4f06-9bb1-a95de63936f7 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet aem.uuid=390847c2-50ec-40d9-af24-f9f34a52a209 rd.luks.key=/tmp/aem-keyfile rd.luks.crypttab=no [4.969412] i915: unknown parameter 'preliminary_hw_support' ignored [5.158667] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [5.364560] [drm] Initialized i915 1.6.0 20170818 for :00:02.0 on minor 0 [6.601641] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 10.722959] i915 :00:02.0: Resetting chip after gpu hang [ 12.704533] i915 :00:02.0: Resetting chip after gpu hang [ 12.704743] [drm:i915_reset [i915]] *ERROR* GPU recovery failed [ 96.864496] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) The GPU is Intel integrated HD graphics (Ivy Bridge). Qubes is updated using current/stable and the kernel version is 4.14.35-1. I wonder if there is a kernel parameter I should be using to get the GPU working? BTW, one alteration I had made to get around issue #2155 (lockup on boot) is to manually upgrade the tboot component (initially 1.9.4 then 1.9.6) - Fedora 25's tboot version is very old. I don't know if the tboot update has an impact on graphics but thought I'd mention it. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/ce1351af-7940-1ff5-a80f-b64fa7919356%40posteo.net. For more options, visit https://groups.google.com/d/optout.
