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

[d.j.yotta]

I was thinking I'm happy enough with what I have working with the i915.modeset=1 kernel param.

But now I get this when trying to load a game I would play on MX 18.3 just fine:

Code: Select all

0009:err:wgl:init_opengl Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory
0009:err:wgl:init_opengl OpenGL support is disabled.
0009:err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found: width=640 height=480 bpp=8 (NoRes)

[d.j.yotta]

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

Does it find the full resolution if you remove all X.Org configuration files and let X auto-configure?

The log shows that the VESA driver is trying (and failing) to load, which isn't right.

No, if I remove any xorg configs, nothing works.
NOTE: I have never moved the 10-evdev.conf or the synaptics.conf - do you want me to move them out of the way also?

So far the only combinations that yield any graphics at all is:

1. i915.modeset=1 kernel param with Xorg 20-intel.conf provided by MXTweak
2. /etc/default/grub to set grub resolution and linux set to "keep" plus Xorg config forcing framebuffer device

The latter is very poor quality (1024x768), and the former is ok (1680x1050).

[d.j.yotta]

and to your last reply....Head_on_a_Stick and others have attempted to see you with results for a normal system
and I attempted in post 20 at the bottom to make it clearer....what I would like you to try.

(grumbles) but nearly every normal person tends to shorten their replies so it hard to know exactly what you did.
Hint!

Similarly, on the live USB it froze after a few minutes

this appears to be new information....that might explain why you varied from what I might think is a normal install....EDIT....oops you already posted in bugs

Oh, I just figured out what you are talking about.

So when I first tried your kernel param i915.modeset=1, it seemed to work great.

Then after I was just about to call the issue solved, my graphics borked. I tried to upload a photo, but I couldn't get it small enough.

I don't know how that issue got resolved but it hasn't happened since. Not confident I've fixed it - I think I just got "unlucky" when it borked.

In an attempt to aid y'all in figuring out what may be the cause of the broken initial install, here is an Xorg log from a Live USB stick with MX 19 installer on.

[d.j.yotta]

I was thinking I'm happy enough with what I have working with the i915.modeset=1 kernel param.

But now I get this when trying to load a game I would play on MX 18.3 just fine:

Code: Select all

0009:err:wgl:init_opengl Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory
0009:err:wgl:init_opengl OpenGL support is disabled.
0009:err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found: width=640 height=480 bpp=8 (NoRes)

EDIT: fixed this issue by doing: sudo apt-get install libgl1-mesa-glx:i386 (it's a 32bit game)

[aus9]

Hi

comments

post 28

11. Saw vesa failing to load so removed all related packages.

I will comment on your missing gl file later as this is related.

what does this mean?
Are you seeing inxi -G that vesa is unloaded....so you are doing something like

Code: Select all

sudo apt-get remove --purge xserver-xorg-video-vesa

additional comment....generally speaking xorg tries to use ....unless their is an
xorg.conf.....the highest driver....then fallbacks to the next highest until
it gets to the basic drivers.

21. Install non-free intel drivers.

how and which ones....its ok to talk about them...just not attach the binaries to your post

post 30

Can verify that with no kernel param, I get 650x480 wether xorg conf or fully automatic

can you post what xorg.conf you created please?

Normally...on most modern distros....xorg does not set a fixed xorg.conf but it conf-less
but using confs....in the deamon dir called /etc/X11/xorg.conf.d

I do not have xorg.conf......and suspect most other MX users do not need one either

post 31

Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory

to search which package has missing file ..Either use your web browser and search
"debian package libGL.so.1" OR

Code: Select all

sudo su
apt install apt-file
apt-file update
apt-file search libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.7.0
libgl1-nvidia-glx: /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1
libgl1-nvidia-legacy-340xx-glx: /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
libgl1-nvidia-legacy-390xx-glx: /usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGL.so.1
primus-libs: /usr/lib/x86_64-linux-gnu/primus/libGL.so.1
virtualbox-guest-x11: /usr/lib/virtualbox/additions/libGL.so.1

we have intell so on my system I have it already installed

Code: Select all

dpkg -l | grep libgl1
ii  libgl1:amd64   1.1.0-1    amd64        Vendor neutral GL dispatch library -- legacy GL support
ii  libgl1-mesa-dri:amd64  18.3.6-2   amd64        free implementation of the OpenGL API -- DRI modules

and this one of the reasons why I prefer you do not uninstall packages without checking what breakages might occur.

post 31 xorg log
----OP post 1....wish 1920x1440
your log shows only ...put in a code for display purposes only

Code: Select all

 27.176] (II) intel(0): Modeline "1680x1050"x0.0  146.25  1680 1960 2136 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    27.176] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    27.176] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    27.176] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    27.176] (II) intel(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    27.176] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    27.176] (II) intel(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    27.176] (II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    27.176] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    27.176] (II) intel(0): Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync +vsync (70.6 kHz e)
[    27.176] (II) intel(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[    27.176] (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[    27.176] (II) intel(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz e)

post 33 shows you are using an xorg.conf

post 34

libgl1-mesa-glx:i386

Nope please uninstall that one.....and try

Code: Select all

sudo apt install  libgl1:amd64 libgl1-mesa-dri:amd64

sorry its a long post

[aus9]

extra to post 28 number 11....and related posts that discuss removals of packages

I forgot to mention....unless you are manually removing files and dirs instead of packages....in which case PLEASE say so
there is an easy way of seeing your removal logs

Code: Select all

cd /var/log/apt/

attach the uncompressed history.log to your reply
but you may have more history logs ending in gz
I have only one....so here is one way to get it

Code: Select all

zcat history.log.1.gz > /tmp/history-1.txt

then attach that file from /tmp too.

here is an example of one of my removals put in a code box for display purposes only

Code: Select all

Start-Date: 2019-11-29  15:34:31
Commandline: apt remove --purge libreoffice*
Requested-By: gordon (1000)
Purge: libreoffice-math:amd64 (1:6.1.5-3+deb10u4), libreoffice-report-builder-bin:amd64 (1:6.1.5-3+deb10u4), libreoffice-gtk3:amd64 (1:6.1.5-3+deb10u4), libreoffice-java-common:amd64 (1:6.1.5-3+deb10u4), libreoffice-base:amd64 (1:6.1.5-3+deb10u4), libreoffice-core:amd64 (1:6.1.5-3+deb10u4), libreoffice-base-core:amd64 (1:6.1.5-3+deb10u4), libreoffice-impress:amd64 (1:6.1.5-3+deb10u4), libreoffice-help-common:amd64 (1:6.1.5-3+deb10u4), libreoffice-style-colibre:amd64 (1:6.1.5-3+deb10u4), libreoffice-writer:amd64 (1:6.1.5-3+deb10u4), libreoffice-common:amd64 (1:6.1.5-3+deb10u4), libreoffice-pdfimport:amd64 (1:6.1.5-3+deb10u4), libreoffice-style-tango:amd64 (1:6.1.5-3+deb10u4), libreoffice-help-en-us:amd64 (1:6.1.5-3+deb10u4), libreoffice-gnome:amd64 (1:6.1.5-3+deb10u4), libreoffice-calc:amd64 (1:6.1.5-3+deb10u4), libreoffice-base-drivers:amd64 (1:6.1.5-3+deb10u4), libreoffice-draw:amd64 (1:6.1.5-3+deb10u4), libreoffice-avmedia-backend-gstreamer:amd64 (1:6.1.5-3+deb10u4)
End-Date: 2019-11-29  15:34:42

[aus9]

and I am thinking out aloud....your resolution was good on MX18.3

can you boot that back up....as live product....and post its Xorg.log?
and confirm you were or not using kernel parameter
and confirm you had no /etc/X11/xorg.conf.d ...intel conf

we should be able to work this out by comparing what driver you were truly using on MX18.3
what settings etc

2) IN addition....if you feel like it.....
at any live boot up or any install boot up....at the bootloader menu screen

press C (for command mode)
type vbeinfo and press enter

what is the asterisk (*) against....1920x1440 or something else

then press the Escape to get back to menu and confinue your boot up

[d.j.yotta]

and I am thinking out aloud....your resolution was good on MX18.3

can you boot that back up....as live product....and post its Xorg.log?
and confirm you were or not using kernel parameter
and confirm you had no /etc/X11/xorg.conf.d ...intel conf

we should be able to work this out by comparing what driver you were truly using on MX18.3
what settings etc

2) IN addition....if you feel like it.....
at any live boot up or any install boot up....at the bootloader menu screen

press C (for command mode)
type vbeinfo and press enter

what is the asterisk (*) against....1920x1440 or something else

then press the Escape to get back to menu and confinue your boot up

I'll answer this first as it's the easiest.

On MX18.3 I had no Xorg conf, and no kernel parameters. Just stock standard MX.
I can boot it back up as a live product with some small difficulty... I'll see if I get time.

I'll post vbeinfo in a separate post.

[d.j.yotta]

extra to post 28 number 11....and related posts that discuss removals of packages

I forgot to mention....unless you are manually removing files and dirs instead of packages....in which case PLEASE say so
there is an easy way of seeing your removal logs

Code: Select all

cd /var/log/apt/

attach the uncompressed history.log to your reply
but you may have more history logs ending in gz
I have only one....so here is one way to get it

Code: Select all

zcat history.log.1.gz > /tmp/history-1.txt

then attach that file from /tmp too.

here is an example of one of my removals put in a code box for display purposes only

Code: Select all

Start-Date: 2019-11-29  15:34:31
Commandline: apt remove --purge libreoffice*
Requested-By: gordon (1000)
Purge: libreoffice-math:amd64 (1:6.1.5-3+deb10u4), libreoffice-report-builder-bin:amd64 (1:6.1.5-3+deb10u4), libreoffice-gtk3:amd64 (1:6.1.5-3+deb10u4), libreoffice-java-common:amd64 (1:6.1.5-3+deb10u4), libreoffice-base:amd64 (1:6.1.5-3+deb10u4), libreoffice-core:amd64 (1:6.1.5-3+deb10u4), libreoffice-base-core:amd64 (1:6.1.5-3+deb10u4), libreoffice-impress:amd64 (1:6.1.5-3+deb10u4), libreoffice-help-common:amd64 (1:6.1.5-3+deb10u4), libreoffice-style-colibre:amd64 (1:6.1.5-3+deb10u4), libreoffice-writer:amd64 (1:6.1.5-3+deb10u4), libreoffice-common:amd64 (1:6.1.5-3+deb10u4), libreoffice-pdfimport:amd64 (1:6.1.5-3+deb10u4), libreoffice-style-tango:amd64 (1:6.1.5-3+deb10u4), libreoffice-help-en-us:amd64 (1:6.1.5-3+deb10u4), libreoffice-gnome:amd64 (1:6.1.5-3+deb10u4), libreoffice-calc:amd64 (1:6.1.5-3+deb10u4), libreoffice-base-drivers:amd64 (1:6.1.5-3+deb10u4), libreoffice-draw:amd64 (1:6.1.5-3+deb10u4), libreoffice-avmedia-backend-gstreamer:amd64 (1:6.1.5-3+deb10u4)
End-Date: 2019-11-29  15:34:42

When I saw vesa failing to load, AND that Xorg failed to find a fallback driver (even though I knew fb would work), I removed packages with vesa in the name and opted for mesa ones (I was trying to understand from just the descriptions). Yes, this was a bit dumb, but I didn't force anything or break any dependencies - I trusted synaptic to do something sensible.

So to clarify, I only removed packages via apt-get or synaptic.

I removed:

Code: Select all

xserver-xorg-video-vesa

I swapped:

Code: Select all

i965-va-driver

for

Code: Select all

i965-va-driver-non-free

I installed:

Code: Select all

xserver-xorg-video-fbdev

I've attached my history if you care to look.

I probably installed a few other unrelated packages because it was hard to tell just from the description if it may help Xorg find the right drivers. I guess the history will tell all.

[d.j.yotta]

Hi

comments

post 28

11. Saw vesa failing to load so removed all related packages.

I will comment on your missing gl file later as this is related.

what does this mean?
Are you seeing inxi -G that vesa is unloaded....so you are doing something like

Code: Select all

sudo apt-get remove --purge xserver-xorg-video-vesa

additional comment....generally speaking xorg tries to use ....unless their is an
xorg.conf.....the highest driver....then fallbacks to the next highest until
it gets to the basic drivers.

21. Install non-free intel drivers.

how and which ones....its ok to talk about them...just not attach the binaries to your post

post 30

Can verify that with no kernel param, I get 650x480 wether xorg conf or fully automatic

can you post what xorg.conf you created please?

Normally...on most modern distros....xorg does not set a fixed xorg.conf but it conf-less
but using confs....in the deamon dir called /etc/X11/xorg.conf.d

I do not have xorg.conf......and suspect most other MX users do not need one either

post 31

Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory

to search which package has missing file ..Either use your web browser and search
"debian package libGL.so.1" OR

Code: Select all

sudo su
apt install apt-file
apt-file update
apt-file search libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.7.0
libgl1-nvidia-glx: /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1
libgl1-nvidia-legacy-340xx-glx: /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
libgl1-nvidia-legacy-390xx-glx: /usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGL.so.1
primus-libs: /usr/lib/x86_64-linux-gnu/primus/libGL.so.1
virtualbox-guest-x11: /usr/lib/virtualbox/additions/libGL.so.1

we have intell so on my system I have it already installed

Code: Select all

dpkg -l | grep libgl1
ii  libgl1:amd64   1.1.0-1    amd64        Vendor neutral GL dispatch library -- legacy GL support
ii  libgl1-mesa-dri:amd64  18.3.6-2   amd64        free implementation of the OpenGL API -- DRI modules

and this one of the reasons why I prefer you do not uninstall packages without checking what breakages might occur.

post 31 xorg log
----OP post 1....wish 1920x1440
your log shows only ...put in a code for display purposes only

Code: Select all

 27.176] (II) intel(0): Modeline "1680x1050"x0.0  146.25  1680 1960 2136 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    27.176] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    27.176] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    27.176] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    27.176] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    27.176] (II) intel(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    27.176] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    27.176] (II) intel(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    27.176] (II) intel(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    27.176] (II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    27.176] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    27.176] (II) intel(0): Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync +vsync (70.6 kHz e)
[    27.176] (II) intel(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[    27.176] (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[    27.176] (II) intel(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz e)

post 33 shows you are using an xorg.conf

post 34

libgl1-mesa-glx:i386

Nope please uninstall that one.....and try

Code: Select all

sudo apt install  libgl1:amd64 libgl1-mesa-dri:amd64

sorry its a long post

What I mean by, "11. Saw vesa failing to load" is that the Xorg showed the driver being loaded, and then logs like "couldn't find matching config" or something similar to that and then "unloading vesa". Which I assumed was Xorg's way of saying that it tried vesa and that didn't work and was trying something else.
So yes, I removed the xorg-video-vesa package (no purge though).

My thinking was if I could manipulate which drivers it tried first, I may actually get a driver (any driver) to load, because I was either getting 640x480 or no graphics at all no matter which drivers it picked. Xorg never seemed to try framebuffer or dri drivers.
Part of my confusion as to what the hell Xorg was trying to do was due to seemingly totally ignoring my Xorg conf (ie, the MX Tweak conf AND my framebuffer conf). So I resorted to removing the drivers I knew weren't working to try and force it's hand.
I see now that what was the real issue was the drivers not being loaded at all (in terms of framebuffer) or not soon enough (in terms of the i915 modesetting driver).

Regarding post 34, I have these installed already:

Code: Select all

sudo apt install  libgl1:amd64 libgl1-mesa-dri:amd64

I regret post 34 as I had just tried to run a game I used to play, and it's 32 bit, and my googling revealed it was because I didn't have the 32 bit drivers installed (only the 64 bit ones). Nevertheless, installing the 32bit glx drivers immediately solved the issue.
Sorry about that, I jumped to conclusion without first looking deeper into the real issue there.


Regarding my res being 1920x1440 vs 1680x1050 - it's possible I've confused myself on my specific screen resolution. I'm happy with the 1680x1050 in any case. I have a niggly suspicion I have seen 1440x900 in the past and mistaken this for 1920x1440 or something...

Yes, I'm using xorg.conf atm, (tried the MX Tweak - but I don't think it is helping or hindering).

1. NO kernel param, NO Xorg.conf ---- doesn't work
2. NO kernel param, YES Xorg.conf ---- doesn't work (neither intel nor framebuffer Xorg help any)
3. YES kernel param, NO Xorg.conf ---- I *think* this doesn't work (just need an Xorg conf with "intel" driver specified)
4. YES kernel param, YES Xorg.conf ---- works (currently using the Xorg conf provided by MXTweak video acceleration method uxa or sna doesn't seem to make a difference)

Either of the methods:
a) the GRUB config to "keep" the bootloader settings - results in framebuffer or
b) the i915.modeset=1 work.
The latter works better.
I have been unsuccessful getting any graphics at all other than 640x480 res with no kernel parameter specified.

Furthermore, I believe that I still need the Xorg.conf with a device set to use "intel" for any graphics even with the i915.modeset=1 kernel param.