[SOLVED] Intel i915 integrated graphics not working on MX 19

[d.j.yotta]

Hi all,

On MX Linux 18.3, everything worked out of the box.

Upon installing MX Linux 19 from the live USB (preserving the /home dir), my system came up with a 640x480 resolution.

I tried mucking around with Xorg config to no avail.

I reverted all my edits to Xorg config by copying the Xorg config files from the live USB.

I tried the MX Tweak that forces Intel driver over modesetting driver.

I resorted to the following:

1. adding these lines to /etc/default/grub:

   Code: Select all

   GRUB_GFXPAYLOAD_LINUX=keep
   GRUB_GFXMODE=1920x1440x24
   

• editing my xorg.conf to look like this:
  $ cat /etc/X11/xorg.conf.d/20-intel.conf

  Code: Select all

  Section "Device"
     Identifier  "Intel Graphics"
     Driver      "fbdev"
  EndSection
  

The result is that I get 1920x1440 res at boot menu (sweet!) but only 1024x768 on X.
I've tried numerous other resolution options both frame buffer and otherwise but the highest I've achieved is 1024x768.

Ideally, I'd like my 1920x1440 res back.

My graphics is integrated Intel i915.
I get a message like: Waited for xxx ms for i915.ko to load with default Xorg.conf

Output of inxi --graphics:

Code: Select all

Graphics:  Device-1: Intel 4 Series Integrated Graphics driver: N/A 
           Display: x11 server: X.Org 1.20.4 driver: none unloaded: fbdev 
           resolution: 1280x1024~N/A 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 

I have uninstalled i965-va-driver via synaptic in case it was confusing things (no difference whether installed or not it seems).
I have uninstalled xserver-xorg-video-vesa as most of the Xorg errors seemed to be due to vesa not understanding my graphics card.
I tried installing the intel-media-va-driver-non-free instead of intel-media-va-driver to no avail.
And several various combinations of the above.

Any help, I'd greatly appreciate it.

Thanks all,
d.j.yotta

[JayM]

Welcome. Please run MX Tools/Quick System Info, then right-click paste into a reply. (Quick System Info automatically copies the information to your clipboard, already formatted properly for pasting into the forum so all you have to do is a right-click/ paste, not a copy/paste.) Thanks.

[Head_on_a_Stick]

I have uninstalled xserver-xorg-video-vesa as most of the Xorg errors seemed to be due to vesa not understanding my graphics card.
I tried installing the intel-media-va-driver-non-free instead of intel-media-va-driver to no avail.
And several various combinations of the above.

Restore your system to the stock package list and try moving the X.Org configuration file out of the way:

Code: Select all

sudo mv /etc/X11/xorg.conf.d/20-intel.conf{,.bak}

Does it give you full resolution then?

The X.Org log will show exactly what is happening.

[aus9]

Hi

Ideally, I'd like my 1920x1440 res back

in case it not obvious to you....resolution at boot menu is independent of Xorg, so you never had Xorg resolution at 1920 etc.

but I wonder if your i915 needs firmware?

I am have a i915 but Xorg log does not show anything but maybe you could in addition to above suggestions look at posting the output for any positive hits for

Code: Select all

dmesg | grep error
dmesg | grep fw

cheers

[Huckleberry Finn]

What about different kernels? 4.9.200 and the latest stable 5.2.21 both in Stable Repo in MXPI.

[d.j.yotta]

Hi

Ideally, I'd like my 1920x1440 res back

in case it not obvious to you....resolution at boot menu is independent of Xorg, so you never had Xorg resolution at 1920 etc.

but I wonder if your i915 needs firmware?

I am have a i915 but Xorg log does not show anything but maybe you could in addition to above suggestions look at posting the output for any positive hits for

Code: Select all

dmesg | grep error
dmesg | grep fw

cheers

Right you are - I do realize the boot menu has nothing to do with Xorg - I was referring to the 1920x1440 res I had under Xorg with MX 18.

I got no hits in dmesg for either error or fw.
Thanks though.

[d.j.yotta]

What about different kernels? 4.9.200 and the latest stable 5.2.21 both in Stable Repo in MXPI.

I tried the latest 5.x and the earliest one I could find - though now you mention it, I think I only went back to 4.19
I guess 4.9 is earlier than that... I'll give it a go.

[d.j.yotta]

Welcome. Please run MX Tools/Quick System Info, then right-click paste into a reply. (Quick System Info automatically copies the information to your clipboard, already formatted properly for pasting into the forum so all you have to do is a right-click/ paste, not a copy/paste.) Thanks.

Code: Select all

System:    Host: yottaLbox Kernel: 5.4.0-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
           v: 8.3.0 
           parameters: BOOT_IMAGE=/vmlinuz-5.4.0-antix.1-amd64-smp 
           root=UUID=e3179ca3-2743-4b04-9b90-e9e17480de16 ro quiet splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5G41T-M LX v: Rev X.0x serial: <filter> 
           BIOS: American Megatrends v: 1001 date: 08/10/2011 
CPU:       Topology: Dual Core model: Pentium E6600 bits: 64 type: MCP arch: Penryn family: 6 
           model-id: 17 (23) stepping: A (10) microcode: A0B L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 13435 
           Speed: 1752 MHz min/max: 1603/3066 MHz Core speeds (MHz): 1: 1752 2: 1752 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 4 Series Integrated Graphics vendor: ASUSTeK driver: N/A 
           bus ID: 00:02.0 chip ID: 8086:2e32 
           Display: x11 server: X.Org 1.20.4 driver: none unloaded: fbdev alternate: vesa 
           resolution: 1280x1024~N/A 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k5.4.0-antix.1-amd64-smp 
Network:   Device-1: Qualcomm Atheros AR8131 Gigabit Ethernet vendor: ASUSTeK driver: atl1c 
           v: 1.0.1.1-NAPI port: ec00 bus ID: 01:00.0 chip ID: 1969:1063 
           IF: eth0 state: down mac: <filter> 
           IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac: <filter> 
Drives:    Local Storage: total: 2.27 TiB used: 131.31 GiB (5.6%) 
           ID-1: /dev/sda vendor: Seagate model: ST3500413AS size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> rotation: 7200 rpm serial: <filter> 
           rev: JC45 scheme: MBR 
           ID-2: /dev/sdb vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB block size: 
           physical: 4096 B logical: 512 B speed: <unknown> rotation: 7200 rpm serial: <filter> 
           rev: CC26 scheme: MBR 
Partition: ID-1: / raw size: 45.63 GiB size: 45.61 GiB (99.95%) used: 7.01 GiB (15.4%) fs: xfs 
           dev: /dev/sda2 
           ID-2: /boot raw size: 953.0 MiB size: 922.0 MiB (96.75%) used: 278.2 MiB (30.2%) 
           fs: ext4 dev: /dev/sda1 
           ID-3: /home raw size: 139.70 GiB size: 139.63 GiB (99.95%) used: 124.03 GiB (88.8%) 
           fs: xfs dev: /dev/sda5 
           ID-4: swap-1 size: 3.72 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 48.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 204 Uptime: 1h 09m Memory: 3.72 GiB used: 1.23 GiB (33.0%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

Thanks

[d.j.yotta]

I have uninstalled xserver-xorg-video-vesa as most of the Xorg errors seemed to be due to vesa not understanding my graphics card.
I tried installing the intel-media-va-driver-non-free instead of intel-media-va-driver to no avail.
And several various combinations of the above.

Restore your system to the stock package list and try moving the X.Org configuration file out of the way:

Code: Select all

sudo mv /etc/X11/xorg.conf.d/20-intel.conf{,.bak}

Does it give you full resolution then?

The X.Org log will show exactly what is happening.

Yes, I have tried the stock Xorg conf.

I've had the issue ever since first boot into the installed MX 19 system.

The Live USB had high res, but the first boot into the installed system had the 640x480 res.

I'll go ahead and restore the stock packages, and move my config to a backup, and post the Xorg log.

[d.j.yotta]

I have uninstalled xserver-xorg-video-vesa as most of the Xorg errors seemed to be due to vesa not understanding my graphics card.
I tried installing the intel-media-va-driver-non-free instead of intel-media-va-driver to no avail.
And several various combinations of the above.

Restore your system to the stock package list and try moving the X.Org configuration file out of the way:

Code: Select all

sudo mv /etc/X11/xorg.conf.d/20-intel.conf{,.bak}

Does it give you full resolution then?

The X.Org log will show exactly what is happening.

Yes, I have tried the stock Xorg conf.

I've had the issue ever since first boot into the installed MX 19 system.

The Live USB had high res, but the first boot into the installed system had the 640x480 res.

I'll go ahead and restore the stock packages, and move my config to a backup, and post the Xorg log.

Ok, I restored the packages I removed and restored the /etc/default/grub and /etc/X11/xorg.conf.d back to stock.

I rebooted and got 640x480 resolution again.

I've attached the Xorg log