A fresh Mint is installed, and volume control shows "no cards available for configuration"; it's an Asus NUC 14 Essential connected via HDMI to a SONY television.

$ aplay -l
aplay: device_list:277: no soundcards found...

$ dmesg | grep -i audio
[    5.761793] sof-audio-pci-intel-tgl 0000:00:1f.3: enabling device (0000 -> 0002)
[    5.762023] sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   15.928887] sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   15.929527] pci 0000:00:1f.3: deferred probe pending: sof-audio-pci-intel-tgl: init of i915 and HDMI codec failed

My system has problems with the displayport connection. This is indicated by several problems that, at the first glance, do not have anything in common. The reason why I claim DP for being the cause, is that when I connect another monitor via DVI these problems just vanish. When I put monitor into sleep it won't wake up. Journal contains: [drm:intel_dp_start_link_train] *ERROR* failed to enable link and sometimes [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Qt applications need a few seconds to start. And meanwhile freeze X. Today I had a complete never-ending system freeze. As a followup KDE start is painfully slow and accompanied by multiple freezes. I use an up-to-date Arch System on an i5-4590, using the Intel HD4600. Here is dmesg with drm.debug=0xe comandline. I cut about a million "[drm:drm_dp_i2c_do_msg] native defer" lines to make it cleaner. Intel drivers are installed. The config: # for i in /sys/module/i915/parameters/*; do echo $i=$(cat $i); done /sys/module/i915/parameters/disable_display=N /sys/module/i915/parameters/disable_power_well=1 /sys/module/i915/parameters/enable_cmd_parser=0 /sys/module/i915/parameters/enable_fbc=-1 /sys/module/i915/parameters/enable_hangcheck=Y /sys/module/i915/parameters/enable_ips=1 /sys/module/i915/parameters/enable_ppgtt=1 /sys/module/i915/parameters/enable_psr=0 /sys/module/i915/parameters/enable_rc6=-1 /sys/module/i915/parameters/fastboot=N /sys/module/i915/parameters/invert_brightness=0 /sys/module/i915/parameters/lvds_channel_mode=0 /sys/module/i915/parameters/lvds_downclock=0 /sys/module/i915/parameters/lvds_use_ssc=-1 /sys/module/i915/parameters/modeset=-1 /sys/module/i915/parameters/panel_ignore_lid=1 /sys/module/i915/parameters/powersave=1 /sys/module/i915/parameters/prefault_disable=N /sys/module/i915/parameters/preliminary_hw_support=0 /sys/module/i915/parameters/reset=Y /sys/module/i915/parameters/semaphores=-1 /sys/module/i915/parameters/vbt_sdvo_panel_type=-1

The chosen answer in this post mentions the installation of the i915_bo driver. I have the same OS (Linux Mint 17.3), but I'm running the i915 driver. Can someone please tell me where do I find it and how to install the i915_bo?

I am experiencing issues with rendering in Kubuntu 22.04 after an update of various packages. The issue is that in booting with the i915 driver, the plasma task bar and also other items using direct rendering are not shown correctly (things like desktop effects work correctly funnily enough). The only way to get the system to go to a usable state is a detour via the recovery mode boot. Setting i915.modeset=0 in the grub config makes the system stuck on boot. The output of inxi -G for the normal boot sequence is: Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 2560x1600~60Hz OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 22.0.5 the recovery mode boot gives: Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: N/A Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: vesa unloaded: fbdev,modesetting gpu: N/A resolution: 3840x2400~88Hz OpenGL: renderer: llvmpipe (LLVM 13.0.1 256 bits) v: 4.5 Mesa 22.0.5 Note that in a previous question (now deleted), I seemed to have issues mostly in the plasmashell and tried things mentioned in other questions to fix problems with it, but they seem unrelated. trying to add some more information about the normal boot, in case it can be helpful. I grep'ed for i915 in the dmesg and you can find the output below. sudo dmesg | grep -i i915 [ 1.368894] i915 0000:00:02.0: enabling device (0006 -> 0007) [ 1.369521] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 1.369529] fb0: switching to i915 from EFI VGA [ 1.369693] i915 0000:00:02.0: vgaarb: deactivate vga console [ 1.370285] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=mem [ 1.370914] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12) [ 1.502406] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 [ 1.512816] fbcon: i915drmfb (fb0) is primary device [ 1.561743] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device [ 4.381622] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 4.457265] sof-audio-pci-intel-tgl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) some of these seem unrelated to graphics, but at any rate, nothing hints at an issue. I am including a picture below to try and illustrate the rendering issues. It is not very clear, but on top of the empty firefox window there is a frame around the window title. This is actually the ALT+F2 launcher which does not get rendered at all. It _is_ functional though which I can verify by e.g. typing gimp or sth like this blindly. Similar things happen for mouseover overlays from the plasmashell task bar I tried switching sddm to lightdm but also this did not bring about any change in behavior. Any hints on how to resolve this issue are gladly appreciated. Let me know if I can provide other information to narrow down the problem. EDIT: looking around some issues with the i915 drivers seem to be solvable by changing kernel boot parameters. Rather unmotivated I changed a few of them without any change, listed below i915.enable_psr=0 # no change i915.enable_fbc=0 # no change EDIT 2: further parameters I tried: intel_iommu=igfx_off to switch off the internal graphics engine according to e.g. this post . I also tried installing and running the OEM kernel with no change. Note that the problem can be circumnavigated somewhat e.g. for the plasmashell by forcing software rendering. I can get a functional plasmashell environment by running pkill plasmashell && LIBGL_ALWAYS_SOFTWARE=1 plasmashell question originally posted on askubuntu but deleted there

I get the error message > snd_hda_intel 0000:00:1f.3: failed to add i915 component master (-19) at boot up (along with some other error messages at shut down) on a system running Ubuntu 14.04. If I restore a backup where no Nvidia drivers were installed the system boots up and shuts down just fine. Any suggestions how I can fix this?

I recently setup a new PC I intend to use for Video Encoding. I'm running an new I-series processor with integrated graphics and a rtx3000 series NVIDIA card. I want to use the NVIDIA nvenc hardware encoder as well as Intel's Quick-sync. My old PC already ran a NVIDIA GTX1000 series card and I reused my SSD with an existing Manjaro installation. The NVIDIA GPU worked out of the box with the proprietary NVIDIA driver. For the QSV encoder I tried following the Arch wiki Articles on Hardware Acceleration and Intel Graphics , but have not been successful so far. The Mainboard (Gigabyte Z690UD) does not have any Display connectors for the Intel GPU. vainfo DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 param: 4, val: 0 libva error: /usr/lib/dri/iHD_drv_video.so init failed vaInitialize failed with error code 18 (invalid parameter),exit > /etc/X11/xorg.conf.d/90-mhwd.conf Section "Device" Identifier "Device0" Driver "intel" VendorName "Intel Corporation" EndSection As shown below, lspci does not list a Kernel module loaded for the Intel GPU: lspci -k | grep -A 3 VGA 0000:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) DeviceName: Onboard - Video Subsystem: Gigabyte Technology Co., Ltd Device d000 0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3881 Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia I manually added the Intel driver: >/etc/modules-load.d/mhwd-gpu.conf ## ## Generated by mhwd - Manjaro Hardware Detection ## i915 nvidia nvidia-drm and added it to: >/etc/mkinitcpio.conf MODULES="intel_agp i915 nvidia nvidia_modeset nvidia_uvm nvidia_drm" I checked the modules blacklists, ran mkinitcpio and updated grub, but lspc still doesn't show a driver in use. I don't really know where to go from here as I'm not too knowledgeable on inner workings of the OS.

I'm getting this kernel error on 5.19 **and 6.0** **and 6.1** all the time, is there anything that can be done to mitigate it. Seems like it's a i915 driver problem. The screen frequently goes black.

------------[ cut here ]------------
i915 0000:00:02.0: drm_WARN_ON(new_crtc_state->do_async_flip && !plane->async_flip)
WARNING: CPU: 4 PID: 1565 at drivers/gpu/drm/i915/display/intel_display.c:7505 intel_atomic_check+0x2947/0x2fe0 [i915]
Modules linked in: tun snd_usb_audio snd_usbmidi_lib usbhid snd_rawmidi hid_logitech_hidpp uhid veth nf_conntrack_netlink xt_nat xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nft_chain_nat xt_MASQUERADE vxlan ip6_udp_tunnel udp_tunnel nft_log nft_limit ipt_REJECT nf_reject_ipv4 xt_limit xt_NFLOG nfnetlink_log xt_physdev xt_conntrack xt_mark xt_multiport xt_addrtype xt_comment nft_compat nf_tables ip_set nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc ctr ccm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device overlay qrtr bnep snd_ctl_led snd_soc_skl_hda_dsp binfmt_misc snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic mei_hdcp intel_rapl_msr snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence
 x86_pkg_temp_thermal snd_sof_intel_hda intel_powerclamp snd_sof_pci coretemp snd_sof_xtensa_dsp snd_sof kvm_intel snd_sof_utils snd_soc_hdac_hda btusb snd_hda_ext_core btrtl snd_soc_acpi_intel_match snd_soc_acpi kvm btbcm iwlmvm snd_soc_core btintel btmtk irqbypass snd_compress snd_intel_dspcfg snd_intel_sdw_acpi intel_cstate bluetooth mac80211 snd_hda_codec intel_uncore snd_hda_core iTCO_wdt snd_hwdep intel_pmc_bxt libarc4 serio_raw pcspkr efi_pstore soundwire_bus jitterentropy_rng iTCO_vendor_support mei_me wmi_bmof iwlwifi snd_pcm watchdog sha512_ssse3 mei sha512_generic snd_timer uvcvideo drbg ansi_cprng videobuf2_vmalloc videobuf2_memops ucsi_acpi processor_thermal_device_pci_legacy cfg80211 videobuf2_v4l2 typec_ucsi processor_thermal_device ecdh_generic processor_thermal_rfim videobuf2_common ecc roles processor_thermal_mbox processor_thermal_rapl typec intel_rapl_common intel_soc_dts_iosf thinkpad_acpi nvram platform_profile ledtrig_audio snd soundcore rfkill
 int3403_thermal soc_button_array int340x_thermal_zone ac evdev int3400_thermal intel_pmc_core acpi_tad acpi_thermal_rel intel_hid acpi_pad sparse_keymap v4l2loopback(OE) videodev mc msr parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod hid_sensor_custom hid_sensor_hub hid_generic intel_ishtp_hid hid i915 drm_buddy crc32_pclmul i2c_algo_bit crc32c_intel drm_display_helper ghash_clmulni_intel cec nvme rc_core nvme_core ttm t10_pi xhci_pci drm_kms_helper crc64_rocksoft_generic crc64_rocksoft crc_t10dif xhci_hcd crct10dif_generic aesni_intel i2c_i801 intel_ish_ipc crct10dif_pclmul crc64 crypto_simd usbcore drm psmouse thunderbolt cryptd i2c_smbus intel_ishtp usb_common crct10dif_common wmi button battery video
CPU: 4 PID: 1565 Comm: Xorg Tainted: G        W  OE     5.19.0-2-amd64 #1  Debian 5.19.11-1
Hardware name: LENOVO 20XW003GUS/20XW003GUS, BIOS N32ET80W (1.56 ) 08/29/2022
RIP: 0010:intel_atomic_check+0x2947/0x2fe0 [i915]
Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 42 e6 e5 cd 48 c7 c1 80 c1 b4 c0 4c 89 e2 48 c7 c7 0b c6 b6 c0 48 89 c6 e8 5d d4 11 ce  0b c7 45 a0 ea ff ff ff e9 9e de ff ff 49 8b 47 08 48 8b 88 90
RSP: 0018:ffffa8e5c1d6fbb8 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff8f36ee29 RDI: 00000000ffffffff
RBP: ffffa8e5c1d6fc60 R08: 0000000000000000 R09: 0000000100bda3eb
R10: ffffa8e5c1d6fa58 R11: ffffffff8fabfd28 R12: ffff9c48c1b433d0
R13: ffffffffc0400ed0 R14: 0000000000000000 R15: ffff9c49a42f1800
FS:  00007fd13281fa80(0000) GS:ffff9c4c0f700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000022a80162a000 CR3: 0000000128634004 CR4: 0000000000770ee0
PKRU: 55555554
Call Trace:
 
 drm_atomic_check_only+0x5b1/0xa20 [drm]
 drm_atomic_nonblocking_commit+0x13/0x60 [drm]
 drm_atomic_helper_page_flip+0x60/0xd0 [drm_kms_helper]
 drm_mode_page_flip_ioctl+0x573/0x5d0 [drm]
 ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
 drm_ioctl_kernel+0xb2/0x140 [drm]
 drm_ioctl+0x224/0x3e0 [drm]
 ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
 __x64_sys_ioctl+0x87/0xc0
 do_syscall_64+0x38/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd1322ffe9b
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05  89 c0 3d 00 f0 ff ff 77 1b 48 8b 44 24 18 64 48 2b 04 25 28 00
RSP: 002b:00007ffc0b2255b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000559f70456b50 RCX: 00007fd1322ffe9b
RDX: 00007ffc0b225640 RSI: 00000000c01864b0 RDI: 000000000000000d
RBP: 00007ffc0b225640 R08: 000000000019c78d R09: 0000559f7041f010
R10: 0000000000000003 R11: 0000000000000246 R12: 00000000c01864b0
R13: 000000000000000d R14: 0000559f70458630 R15: 000000000019c78d
 
---[ end trace 0000000000000000 ]---

This is from version [20210818-1 of firmware-misc-nonfree from Debian 11 - Bookworm](https://packages.debian.org/bookworm/firmware-misc-nonfree)

❯ modinfo i915
filename:       /lib/modules/5.19.0-2-amd64/kernel/drivers/gpu/drm/i915/i915.ko
license:        GPL and additional rights
description:    Intel Graphics
author:         Intel Corporation
author:         Tungsten Graphics, Inc.
import_ns:      DMA_BUF

**TL;DR: I'm using Pop 20.10. I'm on a Dell G5 5590 w/ RTX 2070mq (working well) and an i7-9750H. I have a 144hz built-in screen. It works when using nvidia proprietary drivers, but does not work (nor even appear in xrandr) when the nvidia card is disabled (i.e., using i915/integrated intel gpu instead).** In windows, I see the screen is 144hz when using nvidia, can be manually set to 64hz if desired. If i disabled the nvidia card, I see the screen running at 64hz automatically. In Pop, it auto-defaults to using the nvidia drivers for my machine. This works perfectly, but has poor battery life characteristics. In this mode, xrandr shows only a 144hz setting for the built in screen, which matches what I see in windows in the nvidia control panel: When I try to switch to 'integrated' and reboot, I can only get video through my external monitors connected via usb-c. DP-0, which xrandr shows as the internal screen when using nvidia, doesn't even show up in xrandr when the nvidia is disabled. xrandr with nvidia disabled: I've [filed an issue with i915](https://gitlab.freedesktop.org/drm/intel/-/issues/3307) , but have seen no response. I've tried a number of things, [all documented](https://github.com/pop-os/system76-power/issues/221) , including 1915.modeset=0 and attempts at xorg.conf files, but nothing seems successful--all shots in the dark for me, though, as this isn't an area I am terribly knowledgeable in. My guess is that the EDID (or perhaps the DisplayPort Configuration Data/DPCD?) is 'incorrect', similar to the issue referenced [here](https://bbs.archlinux.org/viewtopic.php?id=230541&p=2) . But I'm pretty over my head trying to debug this on my own, and I'm a bit at a loss of where to go next. I would also guess, and have in the past, that the iGPU just can't handle the 144hz. But: 1) if that's the case, wouldn't I still see it in xrandr? 2) 144hz of 1080p should be well within the range of what the iGPU is capable of, in theory, but if it won't do that in windows, maybe this is a wrong assumption In any case, what can I try to get my internal monitor working (perferably at 60~hz, I'd like to maximize battery life) with my intel UHD 630 iGPU? I would guess that I could add /usr/share/X11/xorg.conf.d/20-intel.conf with a 60hz modeline, but that hasn't seemed to work for me. I've tried many variations, but I just don't see my monitor. (You can see me giving an example of what conf file I have tried [here](https://github.com/pop-os/system76-power/issues/221#issuecomment-787119673)) . What logs should I look at here? Here's my boot logs for an 'integrated' boot, grepped for modeset: https://pastebin.ubuntu.com/p/zXsjcpMdMY/ . No mention of DP-0 whatsoever... However, when I grep through a an nvidia boot, I also see that modeset doesn't ever mention a DP-0 then, either; instead, in an nvidia boot only, I see this line:

Apr 07 16:29:28 pop-os /usr/libexec/gdm-x-session: (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @1920x1080 +2160+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

Based on what I'm reading [here](https://download.nvidia.com/XFree86/Linux-x86_64/100.14.23/README/chapter-19.html#:~:text=The%20NVIDIA%2DAuto%2DSelect%20Mode&text=The%20%22nvidia%2Dauto%2Dselect%22%20mode%20is%20intended%20to,detailed%20timings%20from%20the%20EDID.) when I look up nvidia-auto-select, it seems the nvidia driver is told to manage DP-0, and then does, successfully. However, since I don't see DP-0 mentioned at all in xrandr when not booting with nvidia, I'm unable to debug that issue further than this without figuring out _where_ knowledge of DP-0 comes from in the system, _how_ it gets to be told to use nvidia-auto-select, etc., so that I could instead start telling DP-0 to get utilized when the nvidia card/driver are not active. I think the parent process running is [this code](https://gitlab.gnome.org/GNOME/gdm/blob/master/daemon/gdm-x-session.c) , but I'm not able to get much value from that, as I'm just not a C developer and don't know much about how this kind of project is organized. If some other logs would be helpful, let me know.

Currently my kernel log has these errors,

i915: [drm] *ERROR* CPU pipe C FIFO underrun: transcoder,
i915: [drm] *ERROR* [ENCODER:350:DDI TC3/PHY TC3][DPRX] Failed to enable link training
i915: [drm] *ERROR* Step 2 of creating MST payload for 0000000095f4377a failed: -5
i915: [drm] *ERROR* CPU pipe C FIFO underrun: transcoder,
i915: [drm] *ERROR* [ENCODER:350:DDI TC3/PHY TC3][DPRX] Failed to enable link training
i915: [drm] *ERROR* Step 2 of creating MST payload for 0000000095f4377a failed: -5
i915: [drm] *ERROR* CPU pipe C FIFO underrun: transcoder,

What do they mean? Should they be concerning?

I have i7-10875H processor on my laptop. I have disabled the NVIDIA dGPU, so the problem is only about intel drivers. I'm using Debian 11. Tested with Kernels: - 5.10.0-9-amd64 - 5.14.0-0.bpo.2-amd64 I have used both Xorg and Wayland, the notebook screen is **stuck at 40hz.** **But the screen is 165hz.** I think it is something about driver level because it doesn't matter about the Xorg configs or xrandr settings. Even if I set the hertz value 165 on xrandr, the screen still runs at 40hz. How can I make it run at 165hz like on Windows? --- Here is my lshw -c video: *-display description: VGA compatible controller product: CometLake-H GT2 [UHD Graphics] vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 logical name: /dev/fb0 version: 05 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list fb configuration: depth=32 driver=i915 latency=0 mode=2560x1440 visual=truecolor xres=2560 yres=1440 resources: iomemory:600-5ff iomemory:400-3ff irq:138 memory:6002000000-6002ffffff memory:4000000000-400fffffff ioport:6000(size=64) memory:c0000-dffff Here is my lspci -k: 00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05) DeviceName: Onboard - Video Subsystem: Tongfang Hongkong Limited UHD Graphics Kernel driver in use: i915 Kernel modules: i915 Here is my glxinfo: OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.3.5 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.3.5 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.3.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:

I can't switch tty from tty2 to tty6 in Arch Linux. When I switch outside the GUI, the screen doesn't change (the text from tty1 remains, only the cursor disappears completely). And in the GUI (sddm, xfce4), the graphical cursor simply disappears. What I did: 1. Restarted the computer. There is no result. 2. Launched getty@tty2-tty6 services (it used to help in the VM). There is no result again. 3. Removed quiet, splash and other GRUB arguments for plymouth. The result is that it is possible to enter tty1 and GUI, but it is not possible to enter tty2-6. I found out that tty2-6 are working for me, but they are invisible. Blindly I was able to create a file in tty2. Laptop: Lenovo IdeaPad Y570 (yes, not new). Video card: I don't know exactly which one works, there is Intel Integrated Graphics with i915 and NVIDIA Geforce GT 555M with nouveau. System: Arch Linux 2022.10.01, fully updated.

The problem is that very often (not always) after I supend to disk (hibernate) and try to wake up the machine using the power button, the display freezes and nothing more is happening, it just hangs at a black screen. Even the login-shells at ALT F1-6 are in a hanging state and do not responding. It does not matter if I use echo disk > /sys/power/state, systemctl hibernate, hibernate-disk (from the debian package hibernate) or s2disk (from the debian package uswusp) - the behaviour is always the same. I enabled no_console_suspend initcall_debug ignore_loglevel in GRUB and could see that it always hangs at the same point: If I wait a while, I get the following message: I disabled RC6 in GRUB (i915.enable_rc6=0) and it did not helped. It hangs at the same point, but this time it says [drm] RC6 off. Then I read here , that I should boot with intel_pstate=no_hwp - so I did that, but it did not help. I also tried to boot with nomodeset i915.modeset=0 which I removed as I can not change the resolution anymore and with acpi=off (resource ) which also did not help. The very strange thing is, that with the same laptop, on Debian 8 it work flawlessly. The problem with hibernate began when I moved to Debian 9. Here is my data: Lenovo Thinkpad L460 CPU: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz OS: Debian 9, 4.14.0-0.bpo.2-amd64 RAM: 16GB, SWAP: 20GB Graphics: VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller]) Kernel-Module: i915 # lspci 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-LM (rev 21) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) # dpkg --list | grep -i xorg ii xserver-xorg 1:7.7+19 amd64 X.Org X server ii xserver-xorg-core 2:1.19.2-1+deb9u2 amd64 Xorg X server - core server ii xserver-xorg-input-all 1:7.7+19 amd64 X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 0.23.0-2 amd64 X.Org X server -- libinput input driver ii xserver-xorg-video-all 1:7.7+19 amd64 X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 1.2.0-1+b1 amd64 X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:7.8.0-1+b1 amd64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.4.4-1+b5 amd64 X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20161206-1 amd64 X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau 1:1.0.13-3 amd64 X.Org X server -- Nouveau display driver ii xserver-xorg-video-radeon 1:7.8.0-1+b1 amd64 X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.3.4-1+b2 amd64 X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:13.2.1-1+b1 amd64 X.Org X server -- VMware display driver ii xserver-xorg-video-ati 1:7.8.0-1+b1 amd64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.4.4-1+b5 amd64 X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20161206-1 amd64 X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau 1:1.0.13-3 amd64 X.Org X server -- Nouveau display driver ii xserver-xorg-video-radeon 1:7.8.0-1+b1 amd64 X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.3.4-1+b2 amd64 X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:13.2.1-1+b1 amd64 X.Org X server -- VMware display driver # lsmod Module Size Used by vhost_net 24576 1 vhost 45056 1 vhost_net tap 24576 1 vhost_net tun 32768 3 vhost_net bridge 139264 0 stp 16384 1 bridge llc 16384 2 bridge,stp nf_log_ipv4 16384 1 nf_log_common 16384 1 nf_log_ipv4 xt_LOG 16384 1 xt_limit 16384 1 ipt_MASQUERADE 16384 1 nf_nat_masquerade_ipv4 16384 1 ipt_MASQUERADE xt_tcpudp 16384 29 xt_conntrack 16384 28 iptable_mangle 16384 0 iptable_nat 16384 1 nf_conntrack_ipv4 16384 30 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_nat_ipv4 16384 1 iptable_nat nf_nat 32768 2 nf_nat_masquerade_ipv4,nf_nat_ipv4 nf_conntrack 139264 6 nf_conntrack_ipv4,ipt_MASQUERADE,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_i pv4,nf_nat libcrc32c 16384 2 nf_conntrack,nf_nat iptable_filter 16384 1 nls_ascii 16384 1 nls_cp437 20480 1 vfat 20480 1 fat 65536 1 vfat snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 94208 1 snd_hda_codec_generic 73728 1 snd_hda_codec_realtek arc4 16384 2 snd_soc_skl 86016 0 snd_soc_skl_ipc 65536 1 snd_soc_skl snd_soc_sst_ipc 16384 1 snd_soc_skl_ipc snd_soc_sst_dsp 32768 1 snd_soc_skl_ipc snd_hda_ext_core 24576 1 snd_soc_skl snd_soc_sst_match 16384 1 snd_soc_skl snd_soc_core 225280 1 snd_soc_skl snd_compress 20480 1 snd_soc_core iwlmvm 249856 0 wmi_bmof 16384 0 intel_rapl 20480 0 x86_pkg_temp_thermal 16384 0 mac80211 671744 1 iwlmvm intel_powerclamp 16384 0 coretemp 16384 0 snd_hda_intel 40960 0 iwlwifi 192512 1 iwlmvm kvm_intel 200704 4 snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek kvm 589824 1 kvm_intel i915 1359872 3 snd_hda_core 81920 7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek irqbypass 16384 3 kvm efi_pstore 16384 0 intel_cstate 16384 0 snd_hwdep 16384 1 snd_hda_codec rtsx_pci_ms 20480 0 snd_pcm 98304 7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core thinkpad_acpi 81920 1 intel_uncore 122880 0 pcspkr 16384 0 efivars 20480 1 efi_pstore intel_rapl_perf 16384 0 cfg80211 610304 3 iwlmvm,iwlwifi,mac80211 drm_kms_helper 163840 1 i915 memstick 16384 1 rtsx_pci_ms nvram 16384 1 thinkpad_acpi battery 20480 0 snd_timer 32768 1 snd_pcm rfkill 28672 3 thinkpad_acpi,cfg80211 evdev 24576 15 snd 81920 11 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,thinkpad_acpi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_soc_core,snd_pcm video 40960 2 thinkpad_acpi,i915 soundcore 16384 1 snd drm 372736 4 i915,drm_kms_helper wmi 24576 1 wmi_bmof ac 16384 0 shpchp 36864 0 i2c_algo_bit 16384 1 i915 sg 32768 0 intel_pch_thermal 16384 0 button 16384 1 i915 nbd 36864 0 parport_pc 28672 0 ppdev 20480 0 lp 20480 0 parport 49152 3 lp,parport_pc,ppdev sunrpc 331776 1 efivarfs 16384 1 ip_tables 24576 3 iptable_mangle,iptable_filter,iptable_nat x_tables 36864 8 xt_LOG,iptable_mangle,ip_tables,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_conntrack autofs4 40960 2 ext4 622592 7 crc16 16384 1 ext4 mbcache 16384 1 ext4 jbd2 102400 1 ext4 crc32c_generic 16384 0 fscrypto 28672 1 ext4 ecb 16384 0 algif_skcipher 16384 0 af_alg 24576 1 algif_skcipher dm_crypt 36864 1 dm_mod 118784 25 dm_crypt hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid sd_mod 49152 4 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 crc32c_intel 24576 11 ghash_clmulni_intel 16384 0 pcbc 16384 0 rtsx_pci_sdmmc 24576 0 ahci 36864 3 aesni_intel 188416 2 libahci 32768 1 ahci mmc_core 139264 1 rtsx_pci_sdmmc aes_x86_64 20480 1 aesni_intel crypto_simd 16384 1 aesni_intel glue_helper 16384 1 aesni_intel libata 237568 2 ahci,libahci e1000e 245760 0 rtsx_pci 57344 2 rtsx_pci_sdmmc,rtsx_pci_ms xhci_pci 16384 0 mfd_core 16384 1 rtsx_pci xhci_hcd 212992 1 xhci_pci cryptd 24576 4 crypto_simd,ghash_clmulni_intel,aesni_intel ptp 20480 1 e1000e usbcore 249856 3 usbhid,xhci_pci,xhci_hcd psmouse 143360 0 pps_core 20480 1 ptp scsi_mod 221184 3 sd_mod,libata,sg usb_common 16384 1 usbcore thermal 20480 0 Additional information: I use a second monitor, which I turn off (xrandr --output DP-1 --off) before I go to hibernate state. Also some KVMs are running when entering hibernate state. Also I installed the packages firmware-misc-nonfree firmware-linux-nonfree intel-microcode and the original drivers from intel, found here and here . Please help me, I'm really frustrated. Thank you very much!

I am trying to install Gentoo GNU/Linux on my laptop as a dual boot, the other OS being Devuan GNU/Linux (Chimaera). Devuan is already installed and works properly. In particular, the video card works (text mode and X11 with mate desktop) without a problem. In Gentoo, I have built the kernel without changing the default configuration. When booting Gentoo, after seeing the GRUB menu and the first kernel messages, the screen goes black and stays like that. The OS works though: I can ssh to the laptop and work on it remotely. Here is the output of lshw on Gentoo (run inside an ssh session): $ sudo lshw -c video *-display description: VGA compatible controller product: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 35 width: 64 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:118 memory:80000000-80ffffff memory:90000000-9fffffff ioport:f000(size=64) memory:c0000-dffff and here is what the command says on Devuan: $ sudo lshw -c video *-display description: VGA compatible controller product: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 35 width: 64 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:126 memory:80000000-80ffffff memory:90000000-9fffffff ioport:f000(size=64) memory:c0000-dffff So both use the same driver and report the same information about the controller. This or similar problems seem to occur now and then, and I have found a few sources (see e.g. this question ) that suggest to pass the following to the kernel: i915.modeset=0 If I do this, I can get to the login console, but the image is flickering all the time and, from what I read in the arch forum, I won't be able to run X. On the other hand, Devuan works without this option, so I guess it is not needed. So is there some other option that I can use to make my graphics card work on Gentoo? **Additional information** Here is some more information about my Gentoo environment. During the installation, I followed the Gentoo AMD64 Handbook . I used stage3-amd64-openrc-20221023T170534Z.tar.xz. I installed the kernel sources (see Configuring the Linux kernel ) with # emerge --ask sys-kernel/gentoo-sources and got version linux-5.15.75-gentoo. I then started the kernel configuration tool with # make menuconfig Here, I did not change any options and just saved. This is what I meant above by saying that I have built the kernel without changing the default configuration. I then built and installed with # make && make modules_install # make install I built the ramfs with: # emerge --ask sys-kernel/dracut # dracut --kver=5.15.75-gentoo **Another test** Since my Gentoo installation is on an external USB disk, I tried booting on another laptop. This has the following graphics card: $ sudo lshw -c video *-display description: VGA compatible controller product: UHD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:124 memory:af000000-afffffff memory:b0000000-bfffffff ioport:4000(size=64) memory:c0000-dffff This uses again the i915 driver and the screen turns black during boot (I ran lshw inside an ssh session). As with the other laptop, with i915.modeset=0 the problem goes away.

When my Dell XPS 15 9570 laptop is on, the monitor plugged in the HDMI port is correctly detected. Unplugging the monitor also works as expected. However, when waking up from suspend by briefly lifting the lid open, the HDMI port is not reconfigured. Whatever was plugged at the time it was suspended is still considered connected after resuming. That means that the resolution of the previously plugged monitor is kept, causing "not supported resolution" on the new monitor if the monitors expect different resolutions. Re-connecting the new monitor fixes the issue in this case. I have not figured out exactly how, but leaving the lid open when suspended or after resuming seems to change this behavior. **How can I force the HDMI ports to be scanned again on resume?** or otherwise work around this annoying issue. ### Some more context: * Dual GPU, integrated Intel UHD 630 in use (i915) * Discrete nvidia GPU disabled, no proprietary drivers loaded * Debian 10 (buster) * Linux 4.19.0-2: nouveau.runpm=0 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 scsi_mod.use_blk_mq=1 mem_sleep_default=deep * Wayland 1.16, Gnome 3.30 * /sys/power/mem_sleep: s2idle [deep] ### UPDATE This keeps happening with newer BIOS and Kernel: * Debian 11 (bullseye) * Linux 5.2.0-3 * Wayland client 1.17, Gnome 3.30 * newest Dell XPS BIOS: 1.13.0

When running sudo apt-get upgrade I get this output:

Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-16-amd64
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_dmc_ver1_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915
W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_02.bin for module i915
Processing triggers for hicolor-icon-theme (0.17-2) ...

and when booting I get this output:

i915...: firmware: failed to load i915/kb1_dmc_ver1_04.bin (-2)
firmware_class: See https://wiki.debian.org/Firmware  for information about missing firmware

From other questions about similar messages like this , it seems like one needs to install firmware-misc-nonfree. However, that isn't free software. Furthermore, the graphics card seems to work without any non-free packages so I don't know if this would be useful / needed for anything. * If it's not needed, how can one make these messages disappear without installing any non-free packages? If that is the case, then those messages shouldn't show. * If it's needed for anything, what is it needed for and is it possible to make these things work with FOSS only? How to make it work with FOSS only? For example, one probably only needs a package contained in firmware-misc-nonfree and that package may be free software by now or there are plans for it so it'll be free in the future or there is a FOSS alternative to it (that is under development, planned or finished).

I have a laptop with a peculiar screen setup. The machine has an i915-based graphics adapter, and the screen is configured to be sideways by default. Everything looks good in rEFInd, but when booting up, the console output is completely garbled and sideways. I can set the resolution by passing video=1200x1920,rotate=270 as init options, and have proper output once _init_ is reached. But during the kernel/initramfs loading phase of the boot process, the screen is still garbled and sideways. Is there a way to specify the resolution/rotation of the screen for the kernel/initramfs loading phase of bootup? Can I pass options at that point, or do I need to compile my own kernel?

I've installed Void Linux on Xiaomi Redmibook Pro 15 2022. I'm experiencing the strange graphic issue: In X11 UI works slow. It's even hard to manipulate mouse cursor: it freezes and gets stuck. But if I start video on youtube or run glxgears everything starts to work normal. Also in TTY if I hold any button screen is not been updated at real time. Letters appear after I release the button. And if I start X, wallpapers and bar appear only after I move cursor or press any button. I assume that the problem is with Intel driver. Because on kernels 5.13 and 5.15 lswh marks iGPU "UNCLAIMED" and I can't start X, but TTY works properly and letters appears immediately. Prerequisites: CPU: i7-12650 dGPU: Nvidia RTX2050 Kernel: 5.18.9 with nvidia-drm.modeset=1 mode setting WM: Qtile(same thing with i3) Display: 3200x2000p, 90Hz No DM. Also I did not configure DPI yet, UI is very small, but I don`t think it could be a problem. My ~/.xinitrc

xrandr --setprovideroutputsource modesetting NVIDIA-0  
xrandr --auto   
exec qtile start

Output of glmark2

GL_VENDOR: Intel
GL_RENDERER: Mesa Intel(R) Graphics (ADL GT2) 
GL_VERSION: 4.6 (Compatibility Profile) Mesa 22.1.3

Output of prime-run glmark2

GL_VENDOR: NVIDIA Corporation
GL_RENDERER: NVIDIA GeForce RTX 2050/PCIe/SSE2 
GL_VERSION: 4.6.0 NVIDIA 515.48.07

I've installed Ubuntu alongside with Void and everything works out of the box with kernel 5.15. If needed I can provide any additional information(maybe some outputs from Ubuntu vs Void) I tried to find any differences in dmesg and lshw outputs between Ubuntu and Void. I did not find something significant, except: 1)Void: setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:1U buntu: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:1 2) Void dmesg does not contain these lines:

[    0.140758] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[    0.140875] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations 
[    0.140999] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations

3)In Ubuntu lshw list devices models, but void lists only vendors. I would really appreciate any suggestion! There are the files containing outputs of corresponding programs/OS dmesg ubuntu dmesg void lshw-ubuntu lshw-void

I'm running Ubuntu on a new system with a GPU that uses the i915 kernel module. Unfortunately several times a week the gui crashes and dumps me to a terminal. journalctl shows the problem is: kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:859fddff, in budgie-wm I'm working on diagnosing the problem, but that's not my question today. Today I simply want to disable Xorg from using the GPU at all, so I can use Xorg without crashing. (I tried kernel parameter nomodeset which indeed disabled the GPU but then I couldn't even dim the screen backlight, so that's too extreme of a method for me. This is why I'm now looking at the Xorg layer.) I read from the ArchLinux wiki that sometimes [GPU hanging can be solved](https://wiki.archlinux.org/title/intel_graphics) by setting Option "NoAccel" "True" in Xorg.conf. That's what I want to try. There's some missing explanation, however. I think I should add this by creating a file under /etc/X11/xorg.conf.d/90-noaccel.conf. man xorg.conf explains that xorg.conf is organized into sections. What section should NoAccel go in? Maybe it should go in the Device section, but does that mean I have to put other lines in the same section to identify the device? And how can I tell whether NoAccel is recognized successfully in Xorg?

As I understand, most Intel GPUs are supported on Linux by two different components : i965 (the Mesa/OpenGL part, supporting all recent Intel GPUs) and i915 (kernel part, similarly supporting all recent Intel GPUs). The relationship between the two is not very clearly explained anywhere I found, especially now that names like iHD (for VAAPI), or Iris (newer chips) are mixed in, but essentially I understand that i965 uses features exposed from the kernel by i915 (syscalls/ioctls?) to expose the OpenGL API to applications. While https://unix.stackexchange.com/questions/224240/why-is-the-intel-hd-graphics-driver-called-i915 answers the question about the kernel part, why use a similar yet different product name for the Mesa component that supports all Intel GPUs anyway? Is there a reason behind it, or just history?

I have CentOS 7 running the 4.7.1 kernel (elrepo-ml) on an Intel NUC with Intel HD Graphics i915. I'm trying to run Chrome in full screen mode google-chrome --full-screen --kiosk http:192.168.2.20 (just a local server with the default Apache2 page) and it works most of the time, but randomly (every second to fifth time) it doesn't fully display the page and looks like this: You can see that chrome "thinks" it's full screen because of the way that the page is rendered. One interesting behavior is that if I Alt+Tab to another window (hidden in the screen shot), then the page will render full screen under the window just brought to the front. There is nothing interesting in X.org logs – the same lines are repeated in both successful and unsuccessful full-screen attempts. (The same lines are logged in /var/log/gdm/ when gdm is in debug mode).

[352467.250] GetModeLine - scrn: 0 clock: 148500
[352467.250] GetModeLine - hdsp: 1920 hbeg: 2008 hend: 2052 httl: 2200
[352467.250]               vdsp: 1080 vbeg: 1084 vend: 1089 vttl: 1125 flags: 5

I've tried to force a refresh (which may be what Alt+Tab) programmatically with xrefresh, but that doesn't make any difference. What could be causing this behavior and what can I do to consistently get a full screen image? Edited to add more system details: - Hardware: Intel NUC NUC5CPYH Processor - Intel Celeron N3050 with Intel HD Graphics Driver:

$ modinfo i915 | grep version
srcversion:     4F4A9108A6D94B8919E3154
vermagic:       4.7.1-1.el7.elrepo.x86_64 SMP mod_unload modversions

Hardware:

$ dmesg | egrep "i915|[Gg]raphic"
[    0.000000] Reserving Intel graphics stolen memory at 0x7cf00000-0x7eefffff
[    2.356158] [drm] Memory usable by graphics device = 2048M
[    2.498705] [drm] Initialized i915 1.6.0 20160425 for 0000:00:02.0 on minor 0
[    3.284294] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    6.301736] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])