LinuxQuestions.org - [SOLVED] "no screens found" with Intel HD Graphics 520 after startx in 14.2

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - "no screens found" with Intel HD Graphics 520 after startx in 14.2 (https://www.linuxquestions.org/questions/slackware-14/no-screens-found-with-intel-hd-graphics-520-after-startx-in-14-2-a-4175594097/)

"no screens found" with Intel HD Graphics 520 after startx in 14.2

Hello all,
I'm trying to run Slackware64-14.2 in a new laptop (Asus ux330) but I cannot make Xorg starts. After launching startx I get the error:

Code:

Fatal server error:

(EE) no screens found(EE)

I have checked Xorg.0.log and I found some clues. It says:

Code:

[  4360.125] (EE) open /dev/dri/card0: No such file or directory

[  4360.125] (WW) Falling back to old probe method for modesetting

[  4360.125] (EE) open /dev/dri/card0: No such file or directory

[  4360.125] (EE) Screen 0 deleted because of no matching config section.

Then, I checked the PCI devices and the video card is present:

Code:

00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)

Reading here and there I learn that udev is the responsible of creating the missing file (/dev/dri/card0), so I gave a look to dmes and I found some messages related with the video card:

Code:

...

[    0.000000] Command line: BOOT_IMAGE=dev000:\EFI\SLACKWARE\vmlinuz  root=/dev/sda3 vga=normal ro ro

...

[    0.316201] pci 0000:00:02.0: [8086:5916] type 00 class 0x030000

[    0.316216] pci 0000:00:02.0: reg 0x10: [mem 0xee000000-0xeeffffff 64bit]

[    0.316223] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]

[    0.316227] pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]

...

[    0.327065] vgaarb: setting as boot device: PCI:0000:00:02.0

[    0.327068] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none

[    0.327073] vgaarb: loaded

[    0.327076] vgaarb: bridge control possible 0000:00:02.0

...

[    0.362881] pci 0000:00:02.0: Video device with shadowed ROM

...

[    0.377599] fb0: EFI VGA frame buffer device

...

[    4.021713] [drm] Initialized drm 1.1.0 20060810

... 

udevd[565]: Reading rules file: /lib/udev/rules.d/60-drm.rules

The I have not touched the 60-drm.rules file.

In lsmod, the i915 drives are loaded:

Code:

...

uvcvideo              76917  0

videobuf2_vmalloc      5260  1 uvcvideo

videobuf2_memops        2011  1 videobuf2_vmalloc

videobuf2_v4l2        19966  1 uvcvideo

videobuf2_core        23302  2 uvcvideo,videobuf2_v4l2

v4l2_common            4447  1 videobuf2_v4l2

videodev              153858  4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2

...

i915                1172583  0

...

drm_kms_helper        118940  1 i915

drm                  322902  2 i915,drm_kms_helper

...

intel_gtt              13810  1 i915

agpgart                31796  2 drm,intel_gtt

...

i2c_algo_bit            5962  1 i915

...

i2c_core              47925  11 drm,i915,i2c_i801,i2c_dev,i2c_hid,i2c_designware_core,i2c_designware_platform,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev

...

video                  27709  2 i915,asus_wmi

...

button                  5722  1 i915

Honestly, now I'm stuck and I don't know what should I do now. I tried updating to -current but I got the same error. I think, perhaps, I need to try with newest versions of the Intel drivers or with a newer Kernel, but I would like to understand the problem before building everything blindly. I read somewhere that maybe the drivers and kernel version are not compatible the with Kaby Lake generation, could be this the case?

¿Do you have any clue what could be the problem?

thanks!
felipe.-

Please attach a full Xorg.0.log after a failure to start X, so we know which drivers the server tried to use before giving up, and also post the output of this command, typed as root:

Code:

lspci -knn|grep -A3 VGA

So we will know the exact vendor and model ID and check if someone encoutered the same issue with the same chipset.

And I suggest that you do not fiddle with udev rules or settings, at least until we understand what happens.

Quote:

Originally Posted by felipeperona (Post 5633721)

Code:

00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)

--snip--

I think, perhaps, I need to try with newest versions of the Intel drivers or with a newer Kernel, but I would like to understand the problem before building everything blindly. I read somewhere that maybe the drivers and kernel version are not compatible the with Kaby Lake generation, could be this the case?

¿Do you have any clue what could be the problem?

Your lspci output is a sign that the kernel doesn't recognize your videocard. Otherwise it would provide more information than "Intel Corporation Device 5916". Since both -current and 14.2 use the same base kernel right now (the 4.4 series), there would be no difference in hardware support between the two. According to theinquirer, support for Kaby Lake was added to the kernel in the 4.5 series. So, at a minimum, you'd need to build a 4.5 series kernel or higher to add support. The 4.5-4.7 kernels are all EOL, so you'll want to build either 4.8 or one of the RCs for 4.9 (which should be released as stable any time now, since at least as of yesterday, it is at RC6). It is speculated that the 4.9 kernel will be the next LTS, but it depends on how much stuff developers try and cram into the kernel (possibly making it a poor choice for an LTS).

Pat does have a prepared config for the 4.6 kernels that you can use as a good starting point for a 4.8 (or newer) kernel in the testing/ directory of your favorite mirror (right now, it's the same config for both 14.2 and -current).

There's an in-depth article on the SlackWiki covering how to build a kernel.

Thank you Didier and Bassmadrigal,

Quote:

Originally Posted by Didier Spaier (Post 5633737)

Please attach a full Xorg.0.log after a failure to start X, so we know which drivers the server tried to use before giving up, and also post the output of this command, typed as root...

Ok, I have uploaded Xorg.0.log, but I don't the PC here now, I will run the command when I get back home.

Quote:

Originally Posted by bassmadrigal (Post 5633748)

Your lspci output is a sign that the kernel doesn't recognize your videocard. Otherwise it would provide more information than "Intel Corporation Device 5916".

Ok, I will give a more close look to kernel building, probably I will have to do it any way.

cheers!

Ok, here is the result of the command you suggest me Didier:

# lspci -knn|grep -A3 VGA

Code:

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02)

        Subsystem: ASUSTeK Computer Inc. Device [1043:1520]

00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:1903] (rev 02)

        Subsystem: ASUSTeK Computer Inc. Device [1043:1520]

I don't know if it gives you more information.

cheers,
felipe

Here:

Code:

root[/home/didier]# lspci -knn|grep -A3 VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

        Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d1]

        Kernel driver in use: i915

        Kernel modules: i915

root[/home/didier]# lspci -knn|grep -A3 VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

        Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d1]

        Kernel driver in use: i915

        Kernel modules: i915

I don't know why you are missing the lines about the kernel driver in use and kernel modules. That looks weird.

Other that that a quick Internet search with the arguments: "[8086:5916]" and "screen" doesn't give much clue.

I wonder if it won't use a driver if it doesn't recognize the device (although, I figured it would've at least loaded a vesa driver)... however that is just speculation, and I have no way to test this theory.

@bassmadrigal: so your idea of upgrading the kernel is worth trying.

No matter what, the kernel will need to be upgraded for proper Kaby Lake support. It just didn't exist in the 4.4 series. 4.5 was when it was introduced.

I just don't know if a lack of support would lead to no modules, including vesa, to be shown in lspci.

Yes, I'll upgrade the kernel. I found in another forum* someone who also had a problem with this video card and he solved it upgrading to 4.8.
I will let you know the result.

* https://forums.linuxmint.com/viewtopic.php?t=233554

thanks!!
felipe.-

For the records. The problem was solved after upgrading the kernel to 4.8.10. No special customisation was needed. As bassmadrigal suggested, I used the config-generic-4.6.x64 configuration file from a -current mirror as initial configuration, and then I followed the suggestion given by Alien's wiki.

I have not tested in details the system yet, but Xorg is starting as usual.

Thanks for your advice.
felipe.-