Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED]Problems with getting X to work
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Sat Aug 18, 2018 10:04 pm    Post subject: [SOLVED]Problems with getting X to work Reply with quote

Hi,

I've been following the Handbook to install Gentoo on a new machine and am having trouble with Xorg. I don't have a graphics card, just the on-chip intel i7 graphics. I have VIDEO_CARDS="intel i965" in make.conf. I would appreciate any help or hints to get X working.

Thanks.


startx says this:
Code:

xauth:  file /root/.serverauth.4085 does not exist


X.Org X Server 1.19.5
Release Date: 2017-10-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.14.61-gentoo x86_64 Gentoo
Current Operating System: Linux artichoke 4.14.61-gentoo #1 SMP Tue Aug 14 21:26:38 PDT 2018 x86_64
Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.14.61-gentoo root=/dev/nvme0n1p3
Build Date: 18 August 2018  01:38:27AM
 
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 18 08:45:36 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module fbcon not found in directory /lib/modules/4.14.61-gentoo
intel: waited 2020 ms for i915.ko driver to load
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error


Xorg.0.log:
Code:

[   982.739]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[   982.739] X Protocol Version 11, Revision 0
[   982.739] Build Operating System: Linux 4.14.61-gentoo x86_64 Gentoo
[   982.739] Current Operating System: Linux artichoke 4.14.61-gentoo #1 SMP Tue Aug 14 21:26:38 PDT 2018 x86_64
[   982.739] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.14.61-gentoo root=/dev/nvme0n1p3
[   982.739] Build Date: 18 August 2018  01:38:27AM
[   982.739] 
[   982.739] Current version of pixman: 0.34.0
[   982.739]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[   982.739] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   982.740] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 18 08:45:36 2018
[   982.740] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   982.740] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   982.740] (==) No Layout section.  Using the first Screen section.
[   982.740] (==) No screen section available. Using defaults.
[   982.740] (**) |-->Screen "Default Screen Section" (0)
[   982.740] (**) |   |-->Monitor "<default monitor>"
[   982.740] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[   982.740] (==) Automatically adding devices
[   982.740] (==) Automatically enabling devices
[   982.740] (==) Automatically adding GPU devices
[   982.740] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   982.740] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[   982.740]    Entry deleted from font path.
[   982.740] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   982.740]    Entry deleted from font path.
[   982.740] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   982.740]    Entry deleted from font path.
[   982.740] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   982.740]    Entry deleted from font path.
[   982.740]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   982.740] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   982.740]    Entry deleted from font path.
[   982.740]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   982.740] (==) FontPath set to:
        /usr/share/fonts/misc/
[   982.740] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   982.740] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[   982.740] (II) Loader magic: 0x555ba543bc40
[   982.740] (II) Module ABI versions:
[   982.740]    X.Org ANSI C Emulation: 0.4
[   982.740]    X.Org Video Driver: 23.0
[   982.740]    X.Org XInput driver : 24.1
[   982.740]    X.Org Server Extension : 10.0
[   982.741] (--) PCI:*(0:0:2:0) 8086:3e92:1458:d000 rev 0, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[   982.741] (II) LoadModule: "glx"
[   982.741] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   982.742] (II) Module glx: vendor="X.Org Foundation"
[   982.742]    compiled for 1.19.5, module version = 1.0.0
[   982.742]    ABI class: X.Org Server Extension, version 10.0
[   982.742] (==) Matched intel as autoconfigured driver 0
[   982.742] (==) Matched modesetting as autoconfigured driver 1
[   982.742] (==) Matched fbdev as autoconfigured driver 2
[   982.742] (==) Matched vesa as autoconfigured driver 3
[   982.742] (==) Assigned the driver to the xf86ConfigLayout
[   982.742] (II) LoadModule: "intel"
[   982.742] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[   982.742] (II) Module intel: vendor="X.Org Foundation"
[   982.742]    compiled for 1.19.5, module version = 2.99.917
[   982.742]    Module class: X.Org Video Driver
[   982.742]    ABI class: X.Org Video Driver, version 23.0
[   982.742] (II) LoadModule: "modesetting"
[   982.742] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   982.742] (II) Module modesetting: vendor="X.Org Foundation"
[   982.742]    compiled for 1.19.5, module version = 1.19.5
[   982.742]    Module class: X.Org Video Driver
[   982.742]    ABI class: X.Org Video Driver, version 23.0
[   982.742] (II) LoadModule: "fbdev"
[   982.742] (WW) Warning, couldn't open module fbdev
[   982.742] (II) UnloadModule: "fbdev"
[   982.742] (II) Unloading fbdev
[   982.742] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   982.742] (II) LoadModule: "vesa"
[   982.742] (WW) Warning, couldn't open module vesa
[   982.742] (II) UnloadModule: "vesa"
[   982.742] (II) Unloading vesa
[   982.742] (EE) Failed to load module "vesa" (module does not exist, 0)
[   982.742] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
        i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
        915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
        Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[   982.742] (II) intel: Driver for Intel(R) HD Graphics
[   982.742] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[   982.742] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[   982.742] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   982.742] (--) using VT number 7

[   984.762] intel: waited 2020 ms for i915.ko driver to load
[   984.765] (EE) open /dev/dri/card0: No such file or directory
[   984.765] (WW) Falling back to old probe method for modesetting
[   984.765] (EE) open /dev/dri/card0: No such file or directory
[   984.765] (EE) Screen 0 deleted because of no matching config section.
[   984.765] (II) UnloadModule: "modesetting"
[   984.765] (EE) Device(s) detected, but none match those in the config file.
[   984.765] (EE)
Fatal server error:
[   984.765] (EE) no screens found(EE)
[   984.765] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[   984.765] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   984.765] (EE)
[   984.770] (EE) Server terminated with error (1). Closing log file.



lspci -k output:
Code:

00:00.0 Host bridge: Intel Corporation Device 3ec2 (rev 07)
        Subsystem: Gigabyte Technology Co., Ltd Device 5000
00:02.0 VGA compatible controller: Intel Corporation Device 3e92
        Subsystem: Gigabyte Technology Co., Ltd Device d000
        Kernel modules: i915
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
        Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH USB 3.0 xHCI Controller
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH CSME HECI
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH SATA controller [AHCI mode]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
        Kernel driver in use: pcieport
00:1b.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #19 (rev f0)
        Kernel driver in use: pcieport
00:1b.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #20 (rev f0)
        Kernel driver in use: pcieport
00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0)
        Kernel driver in use: pcieport
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
        Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0)
        Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #4 (rev f0)
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
        Kernel driver in use: pcieport
00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0)
        Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
        Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Device a2c9
        Subsystem: Gigabyte Technology Co., Ltd Device 5001
00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH PMC
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH HD Audio
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller
        Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH SMBus Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
        Subsystem: Gigabyte Technology Co., Ltd Ethernet Connection (2) I219-V
        Kernel driver in use: e1000e
        Kernel modules: e1000e
02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 71)
09:00.0 USB controller: ASMedia Technology Inc. Device 2142
        Subsystem: Gigabyte Technology Co., Ltd Device 5007
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
0b:00.0 Non-Volatile memory controller: Sandisk Corp Device 5001
        Subsystem: Marvell Technology Group Ltd. Device 1093
        Kernel driver in use: nvme
        Kernel modules: nvme


Last edited by Garbanzo on Sun Aug 26, 2018 5:33 am; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sat Aug 18, 2018 10:12 pm    Post subject: Reply with quote

Garbanzo,

Welcome to Gentoo.

Code:
[   984.762] intel: waited 2020 ms for i915.ko driver to load
[   984.765] (EE) open /dev/dri/card0: No such file or directory


It appears that you don't have Intel Direct Render Manager support in your kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
oreo
n00b
n00b


Joined: 14 Aug 2018
Posts: 31

PostPosted: Sat Aug 18, 2018 11:49 pm    Post subject: Reply with quote

This belongs under the Desktop Environments forum. :D

Edit: added smiley face to seem less like a douche.
_________________
"One does not simply, install gentoo."
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Aug 19, 2018 10:18 am    Post subject: Reply with quote

Moved from Installing Gentoo to Desktop Environments.

oreo,

There is a report button, so you need not post in topic about about being out of place.
Reports are public and seen by all the forum mods/admins.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Sun Aug 19, 2018 12:37 pm    Post subject: Reply with quote

Neddy, could this also be an issue with the variants of intel cards 915 and 965, I recall with at least one laptop that even after having the kernel capabilities built that the system would still not boot until the proper boot paramaters were provided for the graphics drivers via grub boot line.

EDIT: I was just adding in this possibility in case what is discovered somehow contradicts this idea, but from the look of the message I would guess that you are right about kernel driver missing :oops:
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Aug 19, 2018 12:46 pm    Post subject: Reply with quote

LIsLinuxIsSogood,

This may not be the only Gentoo learning opportunity but until the kernel driver is loaded /dev/dri/card0 will not exist, so its not possible to tell.

As always, only the first error matters. Later errors are often induced by the first error.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Sun Aug 19, 2018 1:33 pm    Post subject: Reply with quote

https://wiki.gentoo.org/wiki/Intel ...Some more helpful info...

I understand Neddy...with the most likely candidate for problem which is in the kernel, and going from there.

Also just to clarify has the system yet to have a working graphical session with X or did this happen to be working and then stop working? Begin with go back to the source directory for linux kernel /usr/src/linux and checking out whether the configuration file has correctly set the driver for intel915, which in the latest kernel tree is found just below the option for Nouveau
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Aug 19, 2018 1:49 pm    Post subject: Reply with quote

LIsLinuxIsSogood,

Its a new install, see the opening post. With a piece of the kernel missing, its never worked. At least not with that kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Sun Aug 19, 2018 10:47 pm    Post subject: Reply with quote

Hi,

I'm still stuck on this one. Any hints for setting the Kernel right? I've been using genkernel and looked at the Intel page. My latest kernel attempt config is here bpaste .config.

One thing that puzzles me is that live cd does not have /dev/dri/card0 either and has the same error, yet it works. However when I boot the same machine into KDE Neon (mostly Ubuntu 16.04) it does have /dev/dri/card0. So it can work either way?

Thanks.


Gentoo LiveCD Xorg.0.log:
Code:

[    78.066] (II) Module vesa: vendor="X.Org Foundation"
[    78.066]    compiled for 1.18.3, module version = 2.3.4
[    78.066]    Module class: X.Org Video Driver
[    78.066]    ABI class: X.Org Video Driver, version 20.0
[    78.066] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
        i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
        915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
        Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[    78.066] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[    78.066] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[    78.066] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[    78.066] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    78.066] (II) VESA: driver for VESA chipsets: vesa
[    78.066] (++) using VT number 7

[    78.825] (EE) open /dev/dri/card0: No such file or directory
[    78.825] (WW) Falling back to old probe method for modesetting
[    78.825] (EE) open /dev/dri/card0: No such file or directory
[    78.825] (EE) Screen 0 deleted because of no matching config section.
[    78.825] (II) UnloadModule: "modesetting"
[    78.825] (II) Loading sub module "vbe"
[    78.825] (II) LoadModule: "vbe"
[    78.825] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[    79.026] (II) Module vbe: vendor="X.Org Foundation"
[    79.026]    compiled for 1.18.3, module version = 1.1.0
[    79.026]    ABI class: X.Org Video Driver, version 20.0
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 12:16 am    Post subject: Reply with quote

Let's see you make.conf file, which can be displayed using emerge --info
EDIT: Or on the contrary instad of the longer ouptut just a uname -r can take the place of that.
Quick question did you make sure to reinstall xorg-server following the most recent activity in terms of updates, the modules can often not get installed too, so taking a look at a couple of the ways to emerge the module-rebuild set as well as xorg-server if it doesn't get pulled in automatically, which is should. If your fresh install though already had the most recent kernel and xorg was installed at the same time, then I guess this may not be the cause of much help, but still it seems worth doing since there is really no drawback to just reinstalling Xorg here.

This is a likely candidate for the explanation o what's going on:

Code:
[   984.765] (EE) Device(s) detected, but none match those in the config file.


So that suggests that X11 has found a device (not sure which one though since the driver for that could be provided by either the kernel or X11 server itself). Nonetheless I wonder if a missing config file could be to blame...if you have any files in /etc/X11/xorg.conf.d what are their contents please?
Back to top
View user's profile Send private message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Mon Aug 20, 2018 1:08 am    Post subject: Reply with quote

Hi

The emerge --info is here. (I did chroot from the liveCD so uname will give the wrong answer?)
emerge --info

Here is my make.conf. Ive tried it with and without i915 in the VIDEO_CARDS and it doesn't seem to change anything.
Code:

(chroot) livecd / # cat /etc/portage/make.conf
CFLAGS="-march=native -O2 -pipe"
# Use the same settings for both variables
CXXFLAGS="${CFLAGS}"

MAKEOPTS="-j12"
VIDEO_CARDS="intel i915 i965"
INPUT_DEVICES="evdev keyboard mouse"


# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C


The only xorg.conf.d is 20opengl.conf.
Code:

(chroot) livecd / # cat /etc/X11/xorg.conf.d/20opengl.conf
Section "Files"
EndSection


I'll try rebuilding Xorg too.

Thanks for any help.
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 1:17 am    Post subject: Reply with quote

Good idea, to be rebuilding.

So one more thing that I'm not completely sure about, but from the wiki says

Important
Beginning with x11-base/xorg-drivers-1.19, the x11-base/xorg-drivers package (in addition to the mesa package) includes support for the i965 USE flag. This will omit selection of the deprecating x11-drivers/xf86-video-intel driver in favor of the more maintained, generic modesetting DDX driver built into x11-base/xorg-server.


So I believe that depending on what generation processor you have, and stuff by adding i965 to the global USE or VIDEO_CARD variable that it will prefer maybe the wrong driver for this situation, but I'm not sure. Try to see if the packages mentioned above are installed in terms of x11-drivers and if not maybe emerge -1 xf86-video-intel will also be a temporary solution or fix.
Back to top
View user's profile Send private message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Mon Aug 20, 2018 1:36 am    Post subject: Reply with quote

Yea, I saw that on the wiki too, but wasn't sure what to do.

One thing, while building xorg some warnings went by. They were all similar to this. Should I try that?
Code:

libtool: warning: remember to run 'libtool --finish /usr/lib64/xorg/modules'


My processor is i7-8700, so if i read the documents right i should use i965. Should I add i965 to my make.conf? Then I need to rebuild everything with --newuse?
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 1:52 am    Post subject: Reply with quote

I don't know...for newer processors there's probably someone else with more experience as I am way back in upgrading mine.

For this purpose of testing I hope you at least have tried starting X with either xinit or X as the command without the front end scripts of startx etc. for the session.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 6958
Location: Saint Amant, Acadiana

PostPosted: Mon Aug 20, 2018 1:56 am    Post subject: Reply with quote

Start here.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 2:06 am    Post subject: Reply with quote

Quote:
start here


Duplicate of link previously included and already part of this discussion

What issue could help now is either knowing whether OP should be building modules with libtool as mentioned in warning during compile of xorg-server.

Do kernel drivers i965 seem to work out of the box usually with no x configuration file? That is the other thing about this situation which is somewhat doubtful in my opinion.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 6958
Location: Saint Amant, Acadiana

PostPosted: Mon Aug 20, 2018 3:59 am    Post subject: Reply with quote

If this link was posted before then why our OP is still asking what to put into VIDEO_CARDS variable?
There is kernel driver which loads without Xorg, normally when kernel boots. There is Xorg driver, Intel defaults to modesetting as far as I know, not intel driver. And there is MESA. This makes three drivers. MESA is not required to load X and have a GUI. So the step one is getting the kernel configured correctly and intel DRI loading. Then, and only then will be loading Xorg possible.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 4:11 am    Post subject: Reply with quote

Jaglover, I suppose you have a point with the OP about what to include in make.conf. The reason I assumed we were at that starting point (which is where the fix should be made with kernel settings as you explained) is because the missing information about processor's gen and with that was an opportunity to make sure VIDEO_CARDS is correctly set.

Looking at the X output when it fails to start, I get that the kernel is first point that needs to be properly setup so that it works, but why does X even look specifically for i915? How would you suggest that the OP (who seems like he is getting started for the first time maybe with this distribution) get a faster solution that would allow him to get up and running with X. Following the wiki is not really the advice that is needed when the wiki deals with so many different possibilities.
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 4:49 am    Post subject: Reply with quote

Alright, I think the situation is very confused like jaglover points out. When posting to the forum it is important that our OP understands that the more detail that is explained initially and the extent possible describing in detail the steps taken leading up to the point in which problems occurred.

something like this:
" I was towards the end of a installation from stage3 on architecture y with profile z and had already completed the process of adding users, groups, and installed kernel version x.x and grub. Upon booting into the system, and trying to start the graphical session with xorg installed (see below for X server information...then showing emerge -pv xorg-server and show emerge --info probably too but not from your livecd this should be from new installation environment). HERE's A REAL IMPORTANT PART: In order to install and configure Xorg I followed the steps in the Intel article on the wiki, and made the following edits to the make.conf file VIDEO_CARDS=i965 as instructed and then rebuilt the entire system with emerge --newuse --deep @world. (Of course I am just making this up I don't know what it says in there exactly). That is when I thought that just running X would work out of the box as promised, however instead (and show the output you did in the first place)."

If you can organize the questions in this more narrative approach that exposes the work done so far then I think you will get a more directly helpful response from the forums from those that can spot where it is your problem is that you having.

Also since this is hardly a DE question and is really more of a Installation question I think (chroot and livecd concerns) then I would move to have this relocated to Installation topic.
Back to top
View user's profile Send private message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Mon Aug 20, 2018 8:10 am    Post subject: Reply with quote

Yes, this is my first time installing Gentoo. I made it through the Handbook. It boots and I can ping the outside world. Ive been doing chroot from the liveCD so I can research things as I try them. I think I followed the linked Intel Wiki, but I am a little confused about Intel vs modesetting drivers and 915 vs 965. I think I am set up for modesetting but obviously I've done something wrong along the way.
Back to top
View user's profile Send private message
LIsLinuxIsSogood
l33t
l33t


Joined: 13 Feb 2016
Posts: 968

PostPosted: Mon Aug 20, 2018 8:57 am    Post subject: Reply with quote

Ok that makes sense, but did you start with rebuilding the kernel as NeddySeagoon suggested?

I think the steps you need to take are the following:
1. Build the kernel according to what is in the link for intel graphics
2. Check the other packages such as xorg-server and mesa, vesa etc. if you are using them (this step could require setting the correct VIDEO_CARD in make.conf)
3. Troubleshoot any remaining issues with the X configuration

Am I missing anything here...I really don't like to just point you towards finding a solution but I think that graphics and GUI related things are tricky so it may make sense to have you do more of the testing and then turning here to the forum with some of those more specific questions.

From my experience installing gentoo about a dozen or more times, but usually on the same set of hardware so I can't actually help further, sorry
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Mon Aug 20, 2018 9:18 am    Post subject: Reply with quote

Garbanzo,

The liveCD works and your install does not as when the intel driver fails, the liveCD tries another driver.
There are four that will work for your chipset.

Xorg.0.log:
[   982.742] (==) Matched intel as autoconfigured driver 0
[   982.742] (==) Matched modesetting as autoconfigured driver 1
[   982.742] (==) Matched fbdev as autoconfigured driver 2
[   982.742] (==) Matched vesa as autoconfigured driver 3


but you only have
make.conf:
VIDEO_CARDS="intel i915 i965"
in your own install, so there are no alternatives.
Only the Intel driver requires kernel support.
The order listed above is the performance preferred order.

Put your kernel .config file onto a pastebin or rebuild your kernel with
Code:
  ┌───────────────── Intel 8xx/9xx/G3x/G4x/HD Graphics ─────────────────┐
  │ CONFIG_DRM_I915:                                                    │ 
  │                                                                     │ 
  │ Choose this option if you have a system that has "Intel Graphics    │ 
  │ Media Accelerator" or "HD Graphics" integrated graphics,            │ 
  │ including 830M, 845G, 852GM, 855GM, 865G, 915G, 945G, 965G,         │ 
  │ G35, G41, G43, G45 chipsets and Celeron, Pentium, Core i3,          │ 
  │ Core i5, Core i7 as well as Atom CPUs with integrated graphics.     │ 
  │                                                                     │ 
  │ This driver is used by the Intel driver in X.org 6.8 and            │ 
  │ XFree86 4.4 and above. It replaces the older i830 module that       │ 
  │ supported a subset of the hardware in older X.org releases.         │ 
  │                                                                     │ 
  │ Note that the older i810/i815 chipsets require the use of the       │ 
  │ i810 driver instead, and the Atom z5xx series has an entirely       │ 
  │ different implementation.                                           │ 
  │                                                                     │ 
  │ If "M" is selected, the module will be called i915.                 │ 
  │                                                                     │ 
  │ Symbol: DRM_I915 [=m]                                               │ 
  │ Type  : tristate                                                    │ 
  │ Prompt: Intel 8xx/9xx/G3x/G4x/HD Graphics                           │ 
  │   Location:                                                         │ 
  │     -> Device Drivers                                               │ 
  │       -> Graphics support


Do check that your new kernel is in use. Compare the date/time in
Code:
uname -a
between the old and new kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Mon Aug 20, 2018 2:40 pm    Post subject: Reply with quote

I will give that a try and let you know how it goes.

My latest .config
https://bpaste.net/show/02a21a5ea2e5

Thanks,

And i have been runnig uname -a based on another of your posts.[/url] It has saved me a couple of times.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Mon Aug 20, 2018 3:29 pm    Post subject: Reply with quote

Garbanzo,

You have
Code:
CONFIG_DRM_I915=y
That gets you /dev/dri/card0.

You also have
Code:
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="i915/skl_dmc_ver1_26.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
to put the firmware into the kernel.
So far so good.

Check dmesg when you boot that kernel to make sure the firmware loads properly and the driver is not looking for more firmware files.

Put all of dmesg onto a pastebin if you want more eyes to look it over.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Garbanzo
n00b
n00b


Joined: 06 Aug 2018
Posts: 12

PostPosted: Tue Aug 21, 2018 2:12 am    Post subject: Reply with quote

Here is my dmesg. It does have quite a few errors but i'm not sure what they mean.

http://bpaste.net/show/aae6409536b4

Thanks.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum