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

[d.j.yotta]

So I pressed C at boot and typed vbeinfo into the grub prompt.

There were various screen resolutions listed including (surprisingly) 1920x1440 and down to 640x480.
The resolution 1280x1024 is highlighted with an (*).

Cheers.

[aus9]

ahhh...I "TRY" clear up confusion on xorg.conf

when I asked about xorg.conf I was specifically asking are you using an xorg.conf file that you created or was created for you by
running the xserver reconfigure command you mentioned in the past.

if you run

Code: Select all

man xorg
# also worth a read
man Xserver

you can get a hint on what xorg tries first.....but if you have a /etc/X11/xorg.conf then that over rides confless
Is that clearer?

so unless I am wrong...you are claiming you did not create or use with 18 series or 19 series any /etc/X11/xorg.conf?

MX has a simple way to create this file but first lets just clarify what your resolutions might be capable of for your current best driver

post the output of

Code: Select all

xrandr

[aus9]

and one reply to post 40.

thanks for the detailed info.

It might be an idea....as I suggested it...what that kernel parameter is attempting. I looked at the Debian wiki but prefer Arch
https://wiki.archlinux.org/index.php/ke ... de_setting

Basically we have 2 opposite effects

we have i915.modeset=1 kernel paramenter and we are attempting to bypass normal xorg confless setup and use the kernel modesetting

or we can use i915.modeset=0......and hope we use xorg setup.

I have not looked into my init ram filesystem to see if modules for i915 are pre-loading but
if you scroll down in that arch wiki you will see a max size of resolutions.......and this is one of the issues you claim to have

and arch says

If you are doing early KMS, you must include the custom EDID file in the initramfs, otherwise you will run into problems.

but I could not find 1920x1080.bin on my system.

Therefore....I now offer a reverse suggestion

use a kernel parameter to disable and force the system to use xorg
that will then allow us to make an real xorg.conf........if we have the correct drivers installed etc
and with the results of xrandr

[aus9]

I have now had to time to do slightly more research....do not proceed unless you are happy to take notes because you will be at the console login screen for some of these commands

first I attempted the MX simple script as described here
https://mxlinux.org/wiki/hardware/xorg-conf/
It does not IMHO give you a lot to tweak....file is bare minimum.

so here are my notes on creating a full xorg.conf with the usual caveats....TRY AT OWN RISK
However, as I know you have a live product you can mount the internal drive and use root powers to delete the xorg.conf if you find
you system crashes. BTW I am typing away on a real xorg.conf.

first setup
You will need to change your kernel parameter to i915.modeset=0 to force Xorg to be used instead of kernel mode setting
and
leave the 20-intel.conf under /etc/X11/xorg.conf.d please

steps when logged in to Xorg (X)
step one write detailed notes on what you will need to type at the console, they are non-intuitive.
Each command after typing it....you press enter....sorry if that sounds childish but I am trying to be specific.
I have deliberately not showing console commands in code boxs but quote boxes

step two In Xorg (or in X)

Code: Select all

sudo /etc/init.d/lightdm stop

this immediately kicks you out of X to a console prompt

step 3 login as a local user at this prompt screen

step 4 at the console prompt type command...sudo su to save prefacing sudo for some more commands

sudo su
Xorg :1 -configure

The forum may truncate space so its
Xorg space :1 space -configure.....OK?

You will see output to the screen and that a xorg.conf.new is sitting under /root

step 5...As you claim you never used a real xorg.conf in past attempts......type new command

mv /root/xorg.conf.new /etc/X11/xorg.conf

step 6 ....altho we could restart the lightdm daemon I prefer you do a full reboot

reboot

#################
Normal GUI login should appear....and then you can check

Code: Select all

inxi -Gxxx

and check your Xorg.log.0 at /var/log

good luck

My attachment is my log but to save you downloading it ....it says
[ 10.155] (==) Using config file: "/etc/X11/xorg.conf"
[ 10.155] (==) Using config directory: "/etc/X11/xorg.conf.d"
SNIP

Code: Select all

 inxi -Gxxx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5912 
  Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
  v: 4.5 Mesa 18.3.6 compat-v: 3.0 direct render: Yes 

You may notice my xorg.conf still lacks modelines....that we can fix with a manual edit.....coupled with xrandr or other tools if your default resolution is not yet available

[d.j.yotta]

ahhh...I "TRY" clear up confusion on xorg.conf

when I asked about xorg.conf I was specifically asking are you using an xorg.conf file that you created or was created for you by
running the xserver reconfigure command you mentioned in the past.

if you run

Code: Select all

man xorg
# also worth a read
man Xserver

you can get a hint on what xorg tries first.....but if you have a /etc/X11/xorg.conf then that over rides confless
Is that clearer?

so unless I am wrong...you are claiming you did not create or use with 18 series or 19 series any /etc/X11/xorg.conf?

MX has a simple way to create this file but first lets just clarify what your resolutions might be capable of for your current best driver

post the output of

Code: Select all

xrandr

Ok, so I never used a an xorg.conf - I only ever put conf snippets in xorg.conf.d
I did actually do: X -configure and copy the auto generated conf into xorg.conf.d at one point but it didn't help any. I guess because I put it in xorg.conf.d instead of just a file at xorg.conf

On MX 18, I never used xorg.conf or any modifications to xorg.conf.d or any X related configuration. Everything just worked.

Regarding Xorg jargon etc, I'll RTFM harder.

Here is the output of xrandr:

Code: Select all

$ xrandr
Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 32767 x 32767
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 470mm x 300mm
   1680x1050     59.95*+
   1600x1200     60.00  
   1280x1024     75.02    60.02  
   1440x900      74.98    59.89  
   1280x800      59.81  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    59.94  
   720x400       70.08  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Note that that output was obtained on my current (almost) stable solution of using i915.modset=1 kernel param and just the 20-intel.conf in /etc/X11/xorg.conf.d/.
Did you want me to post the output of xrandr from the live stick?

[d.j.yotta]

Here is what I've done.
I left the 20-intel.conf in /etc/X11/xorg.conf.d/
To clarify, 20-intel.conf reads:

Code: Select all

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   #Option      "AccelMethod" "uxa"  #could also use the default "sna"
   #Option      "TearFree"     "true"
EndSection

Then:
1. Reboot
2. Edited boot line to change i915.modeset=1 to i915.modeset=0
3. No graphics at all
4. didn't stop lightdm as I had no graphics
5. Xorg :1 -configure failed: see attached output
6. tried to do /etc/init.d/lightdm stop (just in case)
7. Xorg :1 -configure failed again: failed with the same errors
8. Reboot (back to my current working -ish solution)

Oh, and then I noticed I had this file:

Code: Select all

$ cat /etc/X11/xorg.conf
#-----------------------------------------------------------------------------
# xorg.conf file
#
# Generated by make-xorg-conf sometime around Thu Dec  5 02:25:01 EST 2019
#
# If you want to save customizations, delete the line above or this
# file will get automatically deleted on the next live boot.
#
# Command line parameters: --output=/etc/X11/xorg.conf vesa
#-----------------------------------------------------------------------------

Section "Device"
    Identifier "Device0"
    Driver     "vesa"
EndSection

I didn't put it there! must have come installed... should I remove it?

EDIT: I think I must have run that make-xorg-conf script ignorantly when I first was having issues. Sorry about that. I moved the /etc/X11/xorg.conf to .bak and tried those steps again. Same errors doing Xorg :1 -configure.

[aus9]

Hi

EDIT AFTER POST 49

post 45 vga shows up as 1680x1050 which is pretty good.
number 3 no graphics....can you confirm you have intel xserver package installed...edit....might be the kernel parameter see post 49

Code: Select all

dpkg -l | grep intel

should get a hit for xserver-xorg-video-intel

EDIT and

Code: Select all

dpkg -l | grep xserver-xorg-core

so we get the libglx.so

I am concerned that you show ....Driver "vesa"
and the log shows ....."/root/xorg.conf.new"

this means ....you did not put the new xorg into /etc/X11 and that may explain why your log is showing modprobe errors

then I noticed...failed to notice earlier that you are using kernel 5.4.0-antix.1-amd64-smp and yes that is what you used post 31.

Is there any reason why you can not try kernel = 4.19.0-6-amd64?

Did you want me to post the output of xrandr from the live stick?

No not at this stage.....I think 1680-1050 exceeds what you wanted to we know your card is capable of good resolutions.

post 46

I didn't put it there! must have come installed... should I remove it?

yes please.

now the attachment to post 46 does NOT say you are using /etc/X11/xorg.conf
which is not what I was expecting.

therefore I will wait to see your reasons for using that kernel,
I am tempted to say....if you want a higher kernel to use the liquorix kernel

but first we must get your xorg to use intel.....which will then load i915

its UGLY.....but delete that /etc/X11/xorg.conf
delete any mention of i915 kernel parameter
keep the 20-intel conf file
look at your xorg and see if Xorg log shows intel
-----thats our first aim

I know this might be frustrating for you.
It might take a number of reboots with and without various kernel parameters
and yes I still do not know why your intel video card does not want to play fair.

I know you will say you have done these before....but I want you to do them with my kernel.

PS I have download liquorix and will post my test of that shortly

[aus9]

separate post on testing the liquorix kernel

at bootloader menu....I enter advance to get to liquorix after installing it

Code: Select all

inxi -Gxxx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5912 
  Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
  v: 4.5 Mesa 18.3.6 compat-v: 3.0 direct render: Yes 
gordon@box:~
$ uname -r
5.3.0-13.1-liquorix-amd64

log snippets
Kernel command line: audit=0 BOOT_IMAGE=/boot/vmlinuz-5.3.0-13.1-liquorix-amd64 root=UUID=2e7f6c93-92d9-4fd9-acea-4ae1550ffbec ro quiet splash
Using config file: "/etc/X11/xorg.conf"
[ 7.868] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 7.868] (==) Using system config directory "/usr/share/X11/xorg.conf.d"........contains the 20-intel file
LoadModule: "glx"------------------------------package xserver-xorg-core supplies this
Loading /usr/lib/xorg/modules/drivers/intel_drv.so-------package xserver-xorg-video-intel supplies this

[aus9]

OK so now I have removed my /etc/X11/xorg.conf

and using kernel parameter i915.modeset=0 borks the loading of plymouth splash so I can not get to a GUI login on either my normal kernel or the liqzuorix kernel......good to know

so this confirms your post 46 steps 2 and 3.

so I amend my request to

remove /etc/X11/xorg.conf or /root/xorg.conf*
keep /etc/xorg.conf.d/X11/20-intel.conf
either have no kernel parameter (boot code) or later try i915.modeset=1

with the goal of getting inxi -Gxxx to show intel as the driver rather than modesetting.

[d.j.yotta]

Hi

EDIT AFTER POST 49

post 45 vga shows up as 1680x1050 which is pretty good.
number 3 no graphics....can you confirm you have intel xserver package installed...edit....might be the kernel parameter see post 49

Code: Select all

dpkg -l | grep intel

should get a hit for xserver-xorg-video-intel

EDIT and

Code: Select all

dpkg -l | grep xserver-xorg-core

so we get the libglx.so

I am concerned that you show ....Driver "vesa"
and the log shows ....."/root/xorg.conf.new"

this means ....you did not put the new xorg into /etc/X11 and that may explain why your log is showing modprobe errors

then I noticed...failed to notice earlier that you are using kernel 5.4.0-antix.1-amd64-smp and yes that is what you used post 31.

Is there any reason why you can not try kernel = 4.19.0-6-amd64?

Did you want me to post the output of xrandr from the live stick?

No not at this stage.....I think 1680-1050 exceeds what you wanted to we know your card is capable of good resolutions.

post 46

I didn't put it there! must have come installed... should I remove it?

yes please.

now the attachment to post 46 does NOT say you are using /etc/X11/xorg.conf
which is not what I was expecting.

therefore I will wait to see your reasons for using that kernel,
I am tempted to say....if you want a higher kernel to use the liquorix kernel

but first we must get your xorg to use intel.....which will then load i915

its UGLY.....but delete that /etc/X11/xorg.conf
delete any mention of i915 kernel parameter
keep the 20-intel conf file
look at your xorg and see if Xorg log shows intel
-----thats our first aim

I know this might be frustrating for you.
It might take a number of reboots with and without various kernel parameters
and yes I still do not know why your intel video card does not want to play fair.

I know you will say you have done these before....but I want you to do them with my kernel.

PS I have download liquorix and will post my test of that shortly

Here is the dpkg output:

Code: Select all

das@yottaLbox:~
$ dpkg -l | grep xserver-xorg-core
ii  xserver-xorg-core                     2:1.20.4-1                          amd64        Xorg X server - core server
das@yottaLbox:~
$ dpkg -l | grep intel
ii  dtrx                                  7.1-2                               all          intelligently extract multiple archive types
ii  firmware-intel-sound                  20190717-1~mx19+1                   all          Binary firmware for Intel sound DSPs
ii  firmware-intelwimax                   20190717-1~mx19+1                   all          Binary firmware for Intel WiMAX Connection
ii  intel-media-va-driver:amd64           18.4.1+dfsg1-1                      amd64        VAAPI driver for the Intel GEN8+ Graphics family
ii  intel-microcode                       3.20191112.1~deb10u1                amd64        Processor microcode firmware for Intel CPUs
ii  libdrm-intel1:amd64                   2.4.97-1                            amd64        Userspace interface to intel-specific kernel DRM services -- runtime
ii  libdrm-intel1:i386                    2.4.97-1                            i386         Userspace interface to intel-specific kernel DRM services -- runtime
ii  rpl                                   1.5.7-1                             all          intelligent recursive search/replace utility
ii  whois                                 5.4.3                               amd64        intelligent WHOIS client
ii  wvdial                                1.61-5                              amd64        intelligent Point-to-Point Protocol dialer
ii  xserver-xorg-video-intel              2:2.99.917+git20180925-2            amd64        X.Org X server -- Intel i8xx, i9xx display driver

I am concerned that you show ....Driver "vesa"
and the log shows ....."/root/xorg.conf.new"

this means ....you did not put the new xorg into /etc/X11 and that may explain why your log is showing modprobe errors

Me too, but it looks like the Xorg -configure generates that on-the-fly.
I tried deleting /root/xorg.conf.new and double checked my /etc/X11 was clean (how I noticed the rouge xorg.conf that was in there) and made sure /root was clean too.
Rerunning the command yielded the same messagges (and a new /root/xorg.conf.new).

this means ....you did not put the new xorg into /etc/X11 and that may explain why your log is showing modprobe errors

I couldn't put the "new xorg conf" into /etc/X11 as the Xorg -configure step failed to generate one. Well, it did generate /root/xorg.conf.new - and uses it too apparently, but exited with errors - which is what would happen if I copied that xorg.conf into /etc/X11 and tried rebooting.
I could copy the assumed to be broken generated /root/xorg.conf.new over to /etc/X11 and reboot in any case if you like,...?

then I noticed...failed to notice earlier that you are using kernel 5.4.0-antix.1-amd64-smp and yes that is what you used post 31.

Is there any reason why you can not try kernel = 4.19.0-6-amd64?

I tried all the kernel I could download as far back as I could. I *think* I tried the same one that shipped with MX 18.3 (any place that documents exactly which kernel 18.3 ships with? I had to go off of hear-say on forums...)

I will try those exact steps again on 4.19.0-6-amd64 kernel.

EDIT: OK, so I did try kernel 4.19.0-6 already, but it looks like I installed 4.19.0-6-amd64-unsigned by mistake. I used synaptic to install 4.19.0-6-amd64, which also removed 4.19.0-6.amd64-unsigned.
I rebooted and took off the i915.modeset kernel param for a clean boot.... no graphics at all ie, just a command prompt (although I think this is due to the 20-intel.conf - if I remove that I probably get 640x480 resolution - that has been my experience so far - 640x480 or nothing...)
I've just realised I forgot to try with i915.modeset=0 for the 4.19.0-6-amd64 kernel... I'll try that too.
I'll also try booting up with i915.modeset=1 for the 4.19-6-amd64 kernel and see if I get better graphics (ie, transparency, which I get on the live USB, would indicate some improvement...).

EDIT2: OK, so here is the results
1. 4.19.0-6.amd64 kernel with no kernel params, and the 20-intel.conf in /etc/X11/xorg.conf.d/ <--> no graphics on boot, Xorg :1 -configure fails (see xorg.configure.txt)
2. 4.19.0-6.amd64 kernel with i915.modeset=0, and the 20-intel.conf in /etc/X11/xorg.conf.d/ <--> no grahpics on boot, Xorg :1 -configure failes (see xorg.configure2.txt)
3. 4.19.0-6.amd64 kernel with i915.modset=1, and the 20-intel.conf in /etc/X11/xorg.conf.d/ <--> grahpics is OK (same as on kernel 5.x) but not as nice looking as the live USB graphics.

Also, I'm still having a complete graphics crash from time to time (not every day, but weekly) and requires full powercycle to come right).
So to clarify, even with the i915.modeset=1 on the 5.x kernel, I get graphics locking up from time to time AND on the live USB I have seen the graphics freeze (but not garbled) and lock up. In both cases I have to just power off - I couldn't even switch to a virtual terminal with Alt+F2 etc...
So something is up.

I'm wondering, since it doesn't seem to be a kernel issue, is it the xserver-xorg-video-intel driver? Can I try a different version of that one and see if it helps? I can never recall how to do this in synaptic or apt-get.... I could google it I guess....