Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Optimus laptop
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
bandreabis
Advocate
Advocate


Joined: 18 Feb 2005
Posts: 2490
Location: イタリアのロディで

PostPosted: Tue Oct 30, 2018 10:27 am    Post subject: Optimus laptop Reply with quote

Did anyone succeed in having a working Optimus Laptop?

Now I have only i965 video card perfectly working loosing HDMI functionality.
_________________
Il numero di post non fa di me un esperto! Anzi!


Last edited by bandreabis on Tue Oct 30, 2018 12:53 pm; edited 1 time in total
Back to top
View user's profile Send private message
Fitzcarraldo
Advocate
Advocate


Joined: 30 Aug 2008
Posts: 2034
Location: United Kingdom

PostPosted: Tue Oct 30, 2018 11:41 am    Post subject: Reply with quote

My Clevo W230SS laptop has Optimus hardware. You probably have a different model of laptop, but, in case it's of any help to you, I explain in another thread (see link below) how I got my Clevo W230SS laptop working (including HDMI) with the NVIDIA closed-source driver and the Intel driver. I don't use Bumblebee, though; I switch between either driver by running a script then logging out of the Desktop Environment (KDE, in my case) and logging back in again.

https://forums.gentoo.org/viewtopic-p-8114450.html#8114450
_________________
Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
A.S. Pushkin
Guru
Guru


Joined: 09 Nov 2002
Posts: 418
Location: dx/dt, dy/dt, dz/dt, t

PostPosted: Sat Nov 03, 2018 5:53 pm    Post subject: Reply with quote

I've run across the Optimus name, but how does one determine if it is? I have a
MSI WS63 7RK, which has Intel i915 and Nvidia Quadro P3000. I've not been successful
in installing proprietary drivers, but though battery life is not great it works well
with the CAD application using Nouveau drivers.

I've not been able to prove tell if this is an Optimus laptop though.

Thanks
_________________
ASPushkin

"In a time of universal deceit - telling the truth is a revolutionary act." -- George Orwell
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Nov 03, 2018 6:33 pm    Post subject: Reply with quote

A.S. Pushkin,

Optimus is a label for one and a half graphics systems.
Its always intel and nVidia.

The intel graphics is the whole graphics system. Its the only chip that can refresh the screen, so its always used in Optimus.
Both GPUs share a pixel buffer. Either can draw images in the pixel buffer.

The advantages are lower cost and lower power consumption as there is no output video multiplexer.

If you can use the nvidia chipset without using the intel chipset, you don't have optimus.
Attempting to use the nvidia GPU alone will always result in a blank screen as the nvidia GPU is not connected to the display.

-- edit --

The specification for your system says
Code:
Graphics Nvidia® Quadro® P3000 with 6GB GDDR5

Opimus is always shared RAM with main memory, so that is not Optimus.
_________________
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
duane
Apprentice
Apprentice


Joined: 03 Jun 2002
Posts: 193
Location: Oklahoma City

PostPosted: Sat Nov 03, 2018 9:07 pm    Post subject: Reply with quote

I've had prime working on my acer e15 for quite a while now, and the HDMI out works, but I'm pretty sure the intel driver is running that without the nvidia gpu. (xrandr --listproviders shows 0 outputs from nvidia.) All I have to do is use xrandr to mirror the display -- I haven't bothered with anything more complicated.

I can get the nouveau driver to use the nvidia chip for games, but I have to set the power mode on the nvidia chip manually to get any acceleration. It doesn't really give me much better framerates than the intel driver, and it runs a lot hotter, so I don't use it much. If I cared to use the proprietary drivers, it might work better.

There wasn't any setup involved with my system except to enable the kernel drivers.
Back to top
View user's profile Send private message
Anton Gubarkov
n00b
n00b


Joined: 13 Mar 2008
Posts: 65

PostPosted: Thu Nov 08, 2018 7:19 am    Post subject: Reply with quote

I join the club with my Thinkpad P52 20M90019RT (to be exact about the hardware installed).

It has (in hybrid graphics mode)
Code:

00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GLM [Quadro P2000 Mobile] [10de:1cba] (rev a1)


UEFI setup has 2 configurations for graphics: hybrid and discrete. When in hybrid mode, both Intel and Nvidia are active and visible in lspci. When in discrete mode, Intel is not visible in lspci

In hybrid mode, the internal panel is wired to Intel, while DP, TB and HDMI are always wired to Nvidia.
In Discrete mode, I assume everything is wired to Nvidia as Intel is not present in lspci.

I'm successful in running a desktop on Intel in hybrid mode. It required minimal modification to /etc/X11/xorg.conf.d. I had to specify BusID for Intel device section and force modesetting driver as intel driver is buggy on my hardware:
Code:

Section "Device"
  Identifier  "Intel Graphics UHD 630 (Mobile)"
#  Driver      "intel"
   BusID      "PCI:0:2:0"
   Driver      "modesetting"
   Option      "AccelMethod"    "glamor"
   Option      "DRI"            "3"
EndSection


I also succeeded in setting up bumblebee to run graphics demanding programs on nvidia and display output on internal panel. /etc/bumblebee/xorg.conf.nvidia also required BusID in Device section
Code:

Section "Device"
    Identifier  "DiscreteNvidia"
    Driver      "nvidia"
    VendorName  "NVIDIA Corporation"
    BusID       "PCI:1:0:0"


I want to be able to use external monitors in Gnome like I used to do with my previous laptops - i.e. plug and play fashion. The screen should appear as soon as I connect the monitor, and desktop must be extended to the connected monitor.
I understand that I must run my Gnome session's Xorg on nvidia as the primary driver either via PRIME in hybrid mode or directly in discrete mode. I thought it would be easier to set up pure discrete mode first.

So I cleared /etc/X11/xorg.conf.d of all files, restarted and reconfigured my laptop for pure discrete mode and tried to start an X session.
Code:

[   279.910]
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[   279.912] Build Operating System: Linux 4.18.16-gentoo-zfs x86_64 Gentoo
[   279.913] Current Operating System: Linux PF16W6Y2 4.18.16-gentoo-zfs #9 SMP PREEMPT Fri Nov 2 10:31:33 MSK 2018 x86_64
[   279.913] Kernel command line: BOOT_IMAGE=/system/boot@/vmlinuz-4.18.16-gentoo-zfs root=ZFS=fast/system ro i915.enable_guc=3 i915.alpha_support=0 scsi_mod.use_blk_mq=1 init=/usr/lib/systemd/systemd vconsole.font=ter-v32n rd.shell
[   279.915] Build Date: 03 November 2018  10:18:24PM
[   279.916] 
[   279.917] Current version of pixman: 0.34.0
[   279.919]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   279.920] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   279.925] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov  7 19:17:25 2018
[   279.926] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   279.928] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   279.928] (==) No Layout section.  Using the first Screen section.
[   279.928] (==) No screen section available. Using defaults.
[   279.928] (**) |-->Screen "Default Screen Section" (0)
[   279.928] (**) |   |-->Monitor "<default monitor>"
[   279.928] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
[   279.928] (**) |   |-->Device "Card0"
[   279.928] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[   279.928] (==) Automatically adding devices
[   279.928] (==) Automatically enabling devices
[   279.928] (==) Automatically adding GPU devices
[   279.928] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   279.928] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[   279.928]    Entry deleted from font path.
[   279.928] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   279.928]    Entry deleted from font path.
[   279.928] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   279.928]    Entry deleted from font path.
[   279.928] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   279.928]    Entry deleted from font path.
[   279.928]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   279.928] (==) FontPath set to:
   /usr/share/fonts/misc/,
   /usr/share/fonts/100dpi/
[   279.928] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   279.928] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   279.928] (II) Loader magic: 0x55d739499d00
[   279.928] (II) Module ABI versions:
[   279.928]    X.Org ANSI C Emulation: 0.4
[   279.928]    X.Org Video Driver: 24.0
[   279.928]    X.Org XInput driver : 24.1
[   279.928]    X.Org Server Extension : 10.0
[   279.929] (++) using VT number 1

[   279.929] (--) controlling tty is VT number 1, auto-enabling KeepTty
[   279.930] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   279.930] (II) xfree86: Adding drm device (/dev/dri/card0)
[   279.931] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
[   279.932] (--) PCI:*(1@0:0:0) 10de:1cba:17aa:2262 rev 161, Mem @ 0xa3000000/16777216, 0x60000000/268435456, 0x70000000/33554432, I/O @ 0x00002000/128, BIOS @ 0x????????/524288
[   279.932] (II) LoadModule: "glx"
[   279.932] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   279.933] (II) Module glx: vendor="X.Org Foundation"
[   279.933]    compiled for 1.20.3, module version = 1.0.0
[   279.933]    ABI class: X.Org Server Extension, version 10.0
[   279.933] (II) LoadModule: "nvidia"
[   279.933] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[   279.933] (II) Module nvidia: vendor="NVIDIA Corporation"
[   279.933]    compiled for 4.0.2, module version = 1.0.0
[   279.933]    Module class: X.Org Video Driver
[   279.933] (II) NVIDIA dlloader X Driver  410.73  Sat Oct 20 22:19:41 CDT 2018
[   279.933] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   279.933] (II) systemd-logind: releasing fd for 226:0
[   279.933] (II) Loading sub module "fb"
[   279.933] (II) LoadModule: "fb"
[   279.934] (II) Loading /usr/lib64/xorg/modules/libfb.so
[   279.934] (II) Module fb: vendor="X.Org Foundation"
[   279.934]    compiled for 1.20.3, module version = 1.0.0
[   279.934]    ABI class: X.Org ANSI C Emulation, version 0.4
[   279.934] (II) Loading sub module "wfb"
[   279.934] (II) LoadModule: "wfb"
[   279.934] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[   279.934] (II) Module wfb: vendor="X.Org Foundation"
[   279.934]    compiled for 1.20.3, module version = 1.0.0
[   279.934]    ABI class: X.Org ANSI C Emulation, version 0.4
[   279.934] (II) Loading sub module "ramdac"
[   279.934] (II) LoadModule: "ramdac"
[   279.934] (II) Module "ramdac" already built-in
[   279.934] (II) NVIDIA(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[   279.934] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[   279.934] (==) NVIDIA(0): RGB weight 888
[   279.934] (==) NVIDIA(0): Default visual is TrueColor
[   279.934] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[   279.934] (**) NVIDIA(0): Enabling 2D acceleration
[   279.934] (II) Loading sub module "glxserver_nvidia"
[   279.934] (II) LoadModule: "glxserver_nvidia"
[   279.934] (II) Loading /usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so
[   279.982] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[   279.982]    compiled for 4.0.2, module version = 1.0.0
[   279.982]    Module class: X.Org Server Extension
[   279.983] (II) NVIDIA GLX Module  410.73  Sat Oct 20 22:16:49 CDT 2018
[   280.393] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[   280.393] (--) NVIDIA(0):     DFP-0
[   280.393] (--) NVIDIA(0):     DFP-1
[   280.393] (--) NVIDIA(0):     DFP-2
[   280.393] (--) NVIDIA(0):     DFP-3 (boot)
[   280.393] (--) NVIDIA(0):     DFP-4
[   280.393] (--) NVIDIA(0):     DFP-5
[   280.394] (II) NVIDIA(0): NVIDIA GPU Quadro P2000 (GP107GL-A) at PCI:1:0:0 (GPU-0)
[   280.394] (--) NVIDIA(0): Memory: 4194304 kBytes
[   280.394] (--) NVIDIA(0): VideoBIOS: 86.07.59.00.50
[   280.394] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[   280.394] (--) NVIDIA(GPU-0): DFP-0: disconnected
[   280.394] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[   280.394] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[   280.394] (--) NVIDIA(GPU-0):
[   280.394] (--) NVIDIA(GPU-0): DFP-1: disconnected
[   280.394] (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
[   280.394] (--) NVIDIA(GPU-0): DFP-1: 1440.0 MHz maximum pixel clock
[   280.394] (--) NVIDIA(GPU-0):
[   280.395] (--) NVIDIA(GPU-0): DFP-2: disconnected
[   280.395] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[   280.395] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[   280.395] (--) NVIDIA(GPU-0):
[   280.398] (--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): connected
[   280.398] (--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): Internal DisplayPort
[   280.398] (--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): 1440.0 MHz maximum pixel clock
[   280.398] (--) NVIDIA(GPU-0):
[   280.398] (--) NVIDIA(GPU-0): DFP-4: disconnected
[   280.398] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[   280.398] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[   280.398] (--) NVIDIA(GPU-0):
[   280.399] (--) NVIDIA(GPU-0): DFP-5: disconnected
[   280.399] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[   280.399] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[   280.399] (--) NVIDIA(GPU-0):
[   280.399] (==) NVIDIA(0):
[   280.399] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[   280.399] (==) NVIDIA(0):     will be used as the requested mode.
[   280.399] (==) NVIDIA(0):
[   280.400] (II) NVIDIA(0): Validated MetaModes:
[   280.400] (II) NVIDIA(0):     "DFP-3:nvidia-auto-select"
[   280.400] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160
[   280.403] (--) NVIDIA(0): DPI set to (286, 288); computed from "UseEdidDpi" X config
[   280.403] (--) NVIDIA(0):     option
[   280.403] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[   280.403] (II) NVIDIA:     access.
[   280.427] (II) NVIDIA(0): Setting mode "DFP-3:nvidia-auto-select"
[   281.613] (==) NVIDIA(0): Disabling shared memory pixmaps
[   281.613] (==) NVIDIA(0): Backing store enabled
[   281.613] (==) NVIDIA(0): Silken mouse enabled
[   281.613] (==) NVIDIA(0): DPMS enabled
[   281.614] (II) Loading sub module "dri2"
[   281.614] (II) LoadModule: "dri2"
[   281.614] (II) Module "dri2" already built-in
[   281.614] (II) NVIDIA(0): [DRI2] Setup complete
[   281.614] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   281.614] (II) Initializing extension Generic Event Extension
[   281.614] (II) Initializing extension SHAPE
[   281.615] (II) Initializing extension MIT-SHM
[   281.615] (II) Initializing extension XInputExtension
[   281.615] (II) Initializing extension XTEST
[   281.615] (II) Initializing extension BIG-REQUESTS
[   281.615] (II) Initializing extension SYNC
[   281.615] (II) Initializing extension XKEYBOARD
[   281.615] (II) Initializing extension XC-MISC
[   281.615] (II) Initializing extension XFIXES
[   281.615] (II) Initializing extension RENDER
[   281.615] (II) Initializing extension RANDR
[   281.615] (II) Initializing extension COMPOSITE
[   281.615] (II) Initializing extension DAMAGE
[   281.615] (II) Initializing extension MIT-SCREEN-SAVER
[   281.615] (II) Initializing extension DOUBLE-BUFFER
[   281.615] (II) Initializing extension RECORD
[   281.615] (II) Initializing extension DPMS
[   281.615] (II) Initializing extension Present
[   281.615] (II) Initializing extension DRI3
[   281.615] (II) Initializing extension X-Resource
[   281.615] (II) Initializing extension XVideo
[   281.615] (II) Initializing extension XVideo-MotionCompensation
[   281.615] (II) Initializing extension GLX
[   281.616] (II) Initializing extension GLX
[   281.616] (II) Indirect GLX disabled.
[   281.616] (II) GLX: Another vendor is already registered for screen 0
[   281.616] (II) Initializing extension XFree86-VidModeExtension
[   281.616] (II) Initializing extension XFree86-DGA
[   281.616] (II) Initializing extension XFree86-DRI
[   281.616] (II) Initializing extension DRI2
[   281.616] (II) Initializing extension NV-GLX
[   281.616] (II) Initializing extension NV-CONTROL
[   281.616] (II) Initializing extension XINERAMA
[   281.680] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[   281.680] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   281.680] (**) Power Button: Applying InputClass "system-keyboard"
[   281.680] (II) LoadModule: "libinput"
[   281.680] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[   281.682] (II) Module libinput: vendor="X.Org Foundation"
[   281.682]    compiled for 1.20.3, module version = 0.28.1
[   281.682]    Module class: X.Org XInput Driver
[   281.682]    ABI class: X.Org XInput driver, version 24.1
[   281.682] (II) Using input driver 'libinput' for 'Power Button'
[   281.683] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 37 paused 0
[   281.683] (**) Power Button: always reports core events
[   281.683] (**) Option "Device" "/dev/input/event2"
[   281.683] (**) Option "_source" "server/udev"
[   281.689] (II) event2  - Power Button: is tagged by udev as: Keyboard
[   281.689] (II) event2  - Power Button: device is a keyboard
[   281.690] (II) event2  - Power Button: device removed
[   281.690] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[   281.690] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   281.690] (**) Option "xkb_layout" "us,ru"
[   281.690] (**) Option "xkb_variant" ","
[   281.701] (II) event2  - Power Button: is tagged by udev as: Keyboard
[   281.701] (II) event2  - Power Button: device is a keyboard
[   281.701] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[   281.701] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[   281.701] (**) Video Bus: Applying InputClass "system-keyboard"
[   281.701] (II) Using input driver 'libinput' for 'Video Bus'
[   281.702] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 40 paused 0
[   281.702] (**) Video Bus: always reports core events
[   281.702] (**) Option "Device" "/dev/input/event3"
[   281.702] (**) Option "_source" "server/udev"
[   281.703] (II) event3  - Video Bus: is tagged by udev as: Keyboard
[   281.703] (II) event3  - Video Bus: device is a keyboard
[   281.703] (II) event3  - Video Bus: device removed
[   281.703] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input3/event3"
[   281.703] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[   281.703] (**) Option "xkb_layout" "us,ru"
[   281.703] (**) Option "xkb_variant" ","
[   281.703] (II) event3  - Video Bus: is tagged by udev as: Keyboard
[   281.703] (II) event3  - Video Bus: device is a keyboard
[   281.704] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[   281.704] (II) No input driver specified, ignoring this device.
[   281.704] (II) This device may have been added with another device file.
[   281.704] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[   281.704] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[   281.704] (**) Sleep Button: Applying InputClass "system-keyboard"
[   281.704] (II) Using input driver 'libinput' for 'Sleep Button'
[   281.705] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 41 paused 0
[   281.705] (**) Sleep Button: always reports core events
[   281.705] (**) Option "Device" "/dev/input/event0"
[   281.705] (**) Option "_source" "server/udev"
[   281.705] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[   281.705] (II) event0  - Sleep Button: device is a keyboard
[   281.705] (II) event0  - Sleep Button: device removed
[   281.705] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[   281.705] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[   281.705] (**) Option "xkb_layout" "us,ru"
[   281.705] (**) Option "xkb_variant" ","
[   281.706] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[   281.706] (II) event0  - Sleep Button: device is a keyboard
[   281.706] (II) config/udev: Adding input device Wacom Pen and multitouch sensor Finger (/dev/input/event5)
[   281.706] (**) Wacom Pen and multitouch sensor Finger: Applying InputClass "libinput touchscreen catchall"
[   281.706] (**) Wacom Pen and multitouch sensor Finger: Applying InputClass "Wacom USB touchscreen class"
[   281.706] (**) Wacom Pen and multitouch sensor Finger: Applying InputClass "Wacom touchscreen class"
[   281.706] (II) LoadModule: "wacom"
[   281.706] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
[   281.707] (II) Module wacom: vendor="X.Org Foundation"
[   281.707]    compiled for 1.20.3, module version = 0.36.0
[   281.707]    Module class: X.Org XInput Driver
[   281.707]    ABI class: X.Org XInput driver, version 24.1
[   281.707] (II) Build version:
[   281.707] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
   Graphire2 4x5, Graphire2 5x7, Graphire3 4x5, Graphire3 6x8,
   Graphire4 4x5, Graphire4 6x8, BambooFun 4x5, BambooFun 6x8,
   Bamboo1 Medium, Graphire4 6x8 BlueTooth, CTL-460, CTH-461, CTL-660,
   CTL-461/S, Bamboo Touch, CTH-460/K, CTH-461/S, CTH-661/S1, CTH-461/L,
   CTH-661/L, Intuos 4x5, Intuos 6x8, Intuos 9x12, Intuos 12x12,
   Intuos 12x18, PTU600, PL400, PL500, PL600, PL600SX, PL550, PL800,
   PL700, PL510, PL710, DTI520, DTF720, DTF720a, DTF521, DTU1931,
   DTU2231, DTU1631, DTH1152, DTH1152, Intuos2 4x5, Intuos2 6x8,
   Intuos2 9x12, Intuos2 12x12, Intuos2 12x18, Intuos2 6x8 , Volito,
   PenStation, Volito2 4x5, Volito2 2x3, PenPartner2, Bamboo, Bamboo1,
   Bamboo1 4x6, Bamboo1 5x8, Intuos3 4x5, Intuos3 6x8, Intuos3 9x12,
   Intuos3 12x12, Intuos3 12x19, Intuos3 6x11, Intuos3 4x6, Intuos4 4x6,
   Intuos4 6x9, Intuos4 8x13, Intuos4 12x19, Intuos4 WL USB Endpoint,
   Intuos4 WL Bluetooth Endpoint, Intuos5 touch S, Intuos5 touch M,
   Intuos5 touch L, Intuos5 S, Intuos5 M, Intuos Pro S, Intuos Pro M,
   Intuos Pro L, Cintiq 21UX, Cintiq 20WSX, Cintiq 12WX, Cintiq 21UX2,
   Cintiq 24HD, Cintiq 22HD, Cintiq 24HD touch (EMR digitizer),
   Cintiq 13HD, DTK2241, DTH2242, Cintiq 22HDT, Cintiq 27QHDT,
   Cintiq 27QHDT, Mobilestudio Pro 13, MobileStudio Pro 16,
   MobileStudio Pro 13, MobileStudio Pro 16, Cintiq 13 FHD Pro,
   Cintiq 16 UHD Pro, Cintiq Pro 24, Cintiq Pro 32, Cintiq 13 FHD Pro,
   Cintiq 16 UHD Pro, Cintiq Pro 24, Cintiq Pro 32, Cintiq Pro 24,
   TabletPC 0x90, TabletPC 0x93, TabletPC 0x97, TabletPC 0x9A,
   CapPlus  0x9F, TabletPC 0xE2, TabletPC 0xE3, TabletPC 0xE5,
   TabletPC 0xE6, TabletPC 0xEC, TabletPC 0xED, TabletPC 0xEF,
   TabletPC 0x100, TabletPC 0x101, TabletPC 0x10D, TabletPC 0x116,
   TabletPC 0x12C, TabletPC 0x4001, TabletPC 0x4004, TabletPC 0x5000,
   TabletPC 0x5002, usb:172f:0024, usb:172f:0025, usb:172f:0026,
   usb:172f:0027, usb:172f:0028, usb:172f:0030, usb:172f:0031,
   usb:172f:0032, usb:172f:0033, usb:172f:0034, usb:172f:0035,
   usb:172f:0036, usb:172f:0037, usb:172f:0038, usb:172f:0039,
   usb:172f:0051, usb:172f:0052, usb:172f:0053, usb:172f:0054,
   usb:172f:0055, usb:172f:0056, usb:172f:0057, usb:172f:0058,
   usb:172f:0500, usb:172f:0501, usb:172f:0502, usb:172f:0503,
   usb:1b96:0001, usb:17ef:6004
[   281.708] (II) Using input driver 'wacom' for 'Wacom Pen and multitouch sensor Finger'
[   281.709] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 42 paused 0
[   281.709] (**) Wacom Pen and multitouch sensor Finger: always reports core events
[   281.709] (**) Option "Device" "/dev/input/event5"
[   281.709] (EE) Wacom Pen and multitouch sensor Finger: Invalid type 'stylus' for this device.
[   281.709] (EE) Wacom Pen and multitouch sensor Finger: Invalid type 'eraser' for this device.
[   281.709] (EE) Wacom Pen and multitouch sensor Finger: Invalid type 'cursor' for this device.
[   281.709] (II) Wacom Pen and multitouch sensor Finger: type not specified, assuming 'touch'.
[   281.709] (II) Wacom Pen and multitouch sensor Finger: other types will be automatically added.
[   281.709] (**) Wacom Pen and multitouch sensor Finger touch: panscroll is 0
[   281.709] (**) Wacom Pen and multitouch sensor Finger touch: panscroll modified to 13
[   281.709] (--) Wacom Pen and multitouch sensor Finger touch: maxX=13768 maxY=7744 maxZ=0 resX=40000 resY=40000
[   281.709] (II) Wacom Pen and multitouch sensor Finger touch: hotplugging dependent devices.
[   281.709] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'stylus' for this device.
[   281.710] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'eraser' for this device.
[   281.710] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'cursor' for this device.
[   281.710] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'pad' for this device.
[   281.710] (II) Wacom Pen and multitouch sensor Finger touch: hotplugging completed.
[   281.710] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5191.0001/input/input12/event5"
[   281.710] (II) XINPUT: Adding extended input device "Wacom Pen and multitouch sensor Finger touch" (type: TOUCH, id 9)
[   281.710] (**) Wacom Pen and multitouch sensor Finger touch: (accel) keeping acceleration scheme 1
[   281.710] (**) Wacom Pen and multitouch sensor Finger touch: (accel) acceleration profile 0
[   281.710] (**) Wacom Pen and multitouch sensor Finger touch: (accel) acceleration factor: 2.000
[   281.710] (**) Wacom Pen and multitouch sensor Finger touch: (accel) acceleration threshold: 4
[   281.710] (II) config/udev: Adding input device Wacom Pen and multitouch sensor Finger (/dev/input/mouse0)
[   281.710] (II) No input driver specified, ignoring this device.
[   281.710] (II) This device may have been added with another device file.
[   281.710] (II) config/udev: Adding input device Wacom Pen and multitouch sensor Pen (/dev/input/event6)
[   281.710] (**) Wacom Pen and multitouch sensor Pen: Applying InputClass "libinput tablet catchall"
[   281.710] (**) Wacom Pen and multitouch sensor Pen: Applying InputClass "Wacom USB tablet class"
[   281.710] (**) Wacom Pen and multitouch sensor Pen: Applying InputClass "Wacom tablet class"
[   281.710] (II) Using input driver 'wacom' for 'Wacom Pen and multitouch sensor Pen'
[   281.711] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 43 paused 0
[   281.711] (**) Wacom Pen and multitouch sensor Pen: always reports core events
[   281.711] (**) Option "Device" "/dev/input/event6"
[   281.711] (II) Wacom Pen and multitouch sensor Pen: type not specified, assuming 'stylus'.
[   281.711] (II) Wacom Pen and multitouch sensor Pen: other types will be automatically added.
[   281.711] (--) Wacom Pen and multitouch sensor Pen stylus: using pressure threshold of 851 for button 1
[   281.711] (**) Wacom Pen and multitouch sensor Pen stylus: panscroll is 0
[   281.711] (**) Wacom Pen and multitouch sensor Pen stylus: panscroll modified to 1300
[   281.711] (--) Wacom Pen and multitouch sensor Pen stylus: maxX=34421 maxY=19362 maxZ=4095 resX=100000 resY=100000  tilt=enabled
[   281.711] (II) Wacom Pen and multitouch sensor Pen stylus: hotplugging dependent devices.
[   281.712] (EE) Wacom Pen and multitouch sensor Pen stylus: Invalid type 'cursor' for this device.
[   281.712] (EE) Wacom Pen and multitouch sensor Pen stylus: Invalid type 'touch' for this device.
[   281.712] (EE) Wacom Pen and multitouch sensor Pen stylus: Invalid type 'pad' for this device.
[   281.712] (II) Wacom Pen and multitouch sensor Pen stylus: hotplugging completed.
[   281.712] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5191.0002/input/input14/event6"
[   281.712] (II) XINPUT: Adding extended input device "Wacom Pen and multitouch sensor Pen stylus" (type: STYLUS, id 10)
[   281.712] (**) Wacom Pen and multitouch sensor Pen stylus: (accel) keeping acceleration scheme 1
[   281.712] (**) Wacom Pen and multitouch sensor Pen stylus: (accel) acceleration profile 0
[   281.712] (**) Wacom Pen and multitouch sensor Pen stylus: (accel) acceleration factor: 2.000
[   281.712] (**) Wacom Pen and multitouch sensor Pen stylus: (accel) acceleration threshold: 4
[   281.712] (II) config/udev: Adding input device Wacom Pen and multitouch sensor Pen (/dev/input/mouse1)
[   281.712] (II) No input driver specified, ignoring this device.
[   281.712] (II) This device may have been added with another device file.
[   281.712] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
[   281.712] (II) No input driver specified, ignoring this device.
[   281.712] (II) This device may have been added with another device file.
[   281.712] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event9)
[   281.712] (II) No input driver specified, ignoring this device.
[   281.712] (II) This device may have been added with another device file.
[   281.713] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[   281.713] (II) No input driver specified, ignoring this device.
[   281.713] (II) This device may have been added with another device file.
[   281.713] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
[   281.713] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[   281.713] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[   281.713] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[   281.714] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 44 paused 0
[   281.714] (**) AT Translated Set 2 keyboard: always reports core events
[   281.714] (**) Option "Device" "/dev/input/event4"
[   281.714] (**) Option "_source" "server/udev"
[   281.714] (II) event4  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[   281.714] (II) event4  - AT Translated Set 2 keyboard: device is a keyboard
[   281.714] (II) event4  - AT Translated Set 2 keyboard: device removed
[   281.714] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[   281.714] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[   281.714] (**) Option "xkb_layout" "us,ru"
[   281.714] (**) Option "xkb_variant" ","
[   281.715] (II) event4  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[   281.715] (II) event4  - AT Translated Set 2 keyboard: device is a keyboard
[   281.715] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event12)
[   281.715] (**) ETPS/2 Elantech Touchpad: Applying InputClass "libinput touchpad catchall"
[   281.715] (II) Using input driver 'libinput' for 'ETPS/2 Elantech Touchpad'
[   281.716] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 45 paused 0
[   281.716] (**) ETPS/2 Elantech Touchpad: always reports core events
[   281.716] (**) Option "Device" "/dev/input/event12"
[   281.716] (**) Option "_source" "server/udev"
[   281.717] (II) event12 - ETPS/2 Elantech Touchpad: is tagged by udev as: Touchpad
[   281.717] (II) event12 - ETPS/2 Elantech Touchpad: device is a touchpad
[   281.717] (II) event12 - ETPS/2 Elantech Touchpad: device removed
[   281.717] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input18/event12"
[   281.717] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 12)
[   281.717] (**) Option "AccelerationScheme" "none"
[   281.717] (**) ETPS/2 Elantech Touchpad: (accel) selected scheme none/0
[   281.717] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[   281.717] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[   281.718] (II) event12 - ETPS/2 Elantech Touchpad: is tagged by udev as: Touchpad
[   281.718] (II) event12 - ETPS/2 Elantech Touchpad: device is a touchpad
[   281.718] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse3)
[   281.718] (II) No input driver specified, ignoring this device.
[   281.718] (II) This device may have been added with another device file.
[   281.718] (II) config/udev: Adding input device ETPS/2 Elantech TrackPoint (/dev/input/event11)
[   281.718] (**) ETPS/2 Elantech TrackPoint: Applying InputClass "libinput pointer catchall"
[   281.718] (II) Using input driver 'libinput' for 'ETPS/2 Elantech TrackPoint'
[   281.719] (II) systemd-logind: got fd for /dev/input/event11 13:75 fd 46 paused 0
[   281.719] (**) ETPS/2 Elantech TrackPoint: always reports core events
[   281.719] (**) Option "Device" "/dev/input/event11"
[   281.719] (**) Option "_source" "server/udev"
[   281.720] (II) event11 - ETPS/2 Elantech TrackPoint: is tagged by udev as: Mouse Pointingstick
[   281.720] (II) event11 - ETPS/2 Elantech TrackPoint: device is a pointer
[   281.720] (II) event11 - ETPS/2 Elantech TrackPoint: device removed
[   281.720] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input22/event11"
[   281.720] (II) XINPUT: Adding extended input device "ETPS/2 Elantech TrackPoint" (type: MOUSE, id 13)
[   281.720] (**) Option "AccelerationScheme" "none"
[   281.720] (**) ETPS/2 Elantech TrackPoint: (accel) selected scheme none/0
[   281.720] (**) ETPS/2 Elantech TrackPoint: (accel) acceleration factor: 2.000
[   281.720] (**) ETPS/2 Elantech TrackPoint: (accel) acceleration threshold: 4
[   281.721] (II) event11 - ETPS/2 Elantech TrackPoint: is tagged by udev as: Mouse Pointingstick
[   281.721] (II) event11 - ETPS/2 Elantech TrackPoint: device is a pointer
[   281.721] (II) config/udev: Adding input device ETPS/2 Elantech TrackPoint (/dev/input/mouse2)
[   281.721] (II) No input driver specified, ignoring this device.
[   281.721] (II) This device may have been added with another device file.
[   281.721] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event7)
[   281.721] (**) ThinkPad Extra Buttons: Applying InputClass "libinput keyboard catchall"
[   281.721] (**) ThinkPad Extra Buttons: Applying InputClass "system-keyboard"
[   281.721] (II) Using input driver 'libinput' for 'ThinkPad Extra Buttons'
[   281.722] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 47 paused 0
[   281.722] (**) ThinkPad Extra Buttons: always reports core events
[   281.722] (**) Option "Device" "/dev/input/event7"
[   281.722] (**) Option "_source" "server/udev"
[   281.722] (II) event7  - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
[   281.722] (II) event7  - ThinkPad Extra Buttons: device is a keyboard
[   281.723] (II) event7  - ThinkPad Extra Buttons: device removed
[   281.723] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input17/event7"
[   281.723] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 14)
[   281.723] (**) Option "xkb_layout" "us,ru"
[   281.723] (**) Option "xkb_variant" ","
[   281.723] (II) event7  - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
[   281.723] (II) event7  - ThinkPad Extra Buttons: device is a keyboard
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: Applying InputClass "libinput tablet catchall"
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: Applying InputClass "Wacom USB tablet class"
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: Applying InputClass "Wacom tablet class"
[   281.725] (II) Using input driver 'wacom' for 'Wacom Pen and multitouch sensor Pen eraser'
[   281.725] (II) systemd-logind: returning pre-existing fd for /dev/input/event6 13:70
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: always reports core events
[   281.725] (**) Option "Device" "/dev/input/event6"
[   281.725] (**) Option "Type" "eraser"
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: panscroll is 1300
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: panscroll modified to 1300
[   281.725] (--) Wacom Pen and multitouch sensor Pen eraser: maxX=34421 maxY=19362 maxZ=4095 resX=100000 resY=100000  tilt=enabled
[   281.725] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5191.0002/input/input14/event6"
[   281.725] (II) XINPUT: Adding extended input device "Wacom Pen and multitouch sensor Pen eraser" (type: ERASER, id 15)
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: (accel) keeping acceleration scheme 1
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: (accel) acceleration profile 0
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: (accel) acceleration factor: 2.000
[   281.725] (**) Wacom Pen and multitouch sensor Pen eraser: (accel) acceleration threshold: 4
[   281.726] (--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): connected
[   281.726] (--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): Internal DisplayPort
[   281.726] (--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): 1440.0 MHz maximum pixel clock
[   281.726] (--) NVIDIA(GPU-0):
[   282.434] (**) Option "fd" "37"
[   282.434] (II) event2  - Power Button: device removed
[   282.434] (**) Option "fd" "40"
[   282.434] (II) event3  - Video Bus: device removed
[   282.434] (**) Option "fd" "41"
[   282.434] (II) event0  - Sleep Button: device removed
[   282.434] (**) Option "fd" "44"
[   282.434] (II) event4  - AT Translated Set 2 keyboard: device removed
[   282.434] (**) Option "fd" "45"
[   282.434] (II) event12 - ETPS/2 Elantech Touchpad: device removed
[   282.434] (**) Option "fd" "46"
[   282.434] (II) event11 - ETPS/2 Elantech TrackPoint: device removed
[   282.434] (**) Option "fd" "47"
[   282.434] (II) event7  - ThinkPad Extra Buttons: device removed
[   282.439] (II) UnloadModule: "wacom"
[   282.439] (II) systemd-logind: not releasing fd for 13:70, still in use
[   282.439] (II) UnloadModule: "libinput"
[   282.439] (II) systemd-logind: releasing fd for 13:71
[   282.454] (II) UnloadModule: "libinput"
[   282.454] (II) systemd-logind: releasing fd for 13:75
[   282.471] (II) UnloadModule: "libinput"
[   282.471] (II) systemd-logind: releasing fd for 13:76
[   282.487] (II) UnloadModule: "libinput"
[   282.487] (II) systemd-logind: releasing fd for 13:68
[   282.495] (II) UnloadModule: "wacom"
[   282.495] (II) systemd-logind: releasing fd for 13:70
[   282.511] (II) UnloadModule: "wacom"
[   282.511] (II) systemd-logind: releasing fd for 13:69
[   282.527] (II) UnloadModule: "libinput"
[   282.527] (II) systemd-logind: releasing fd for 13:64
[   282.535] (II) UnloadModule: "libinput"
[   282.535] (II) systemd-logind: releasing fd for 13:67
[   282.544] (II) UnloadModule: "libinput"
[   282.544] (II) systemd-logind: releasing fd for 13:66
[   283.781] (II) NVIDIA(GPU-0): Deleting GPU-0
[   283.794] (II) Server terminated successfully (0). Closing log file.


So, judging from the log file I can see that nvidia driver is initialized and discovered the attached internal display panel at DFP-3. I can also see the screen flicker and the text mode cursor disappear. But the screen remains blank.
I'm a bit clueless about possible way forward.
Back to top
View user's profile Send private message
Anton Gubarkov
n00b
n00b


Joined: 13 Mar 2008
Posts: 65

PostPosted: Thu Nov 08, 2018 12:13 pm    Post subject: Reply with quote

I managed to start a PRIME version of gnome-session on nvidia in hybrid mode. HDMI and DP ports work as expected, I can connect external monitors/projectors.
The main issue was that I forgot to switch opengl implementation to nvidia.

I'm working on starting a gnome-session selectively on Intel and Nvidia without doing eselect opengl set. The ultimate goal is to integrate this selection into gdm session chooser.
I plan to run gdm on intel (always). When I login, I want to be able to choose between 2 sessions: pure intel (for long battery) or nvidia+prime (speed and external ports enabled).

I'm looking to set everything up in the /etc/X11/Xsession script. If anyone can provide insights on how to achieve it - I'd be grateful.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Nov 08, 2018 10:10 pm    Post subject: Reply with quote

Anton Gubarkov,

I don't see any sign of Optimus in your log. You only have one graphics card listed.
Code:
[   279.932] (--) PCI:*(1@0:0:0) 10de:1cba:17aa:2262 rev 161, Mem @ 0xa3000000/16777216, 0x60000000/268435456, 0x70000000/33554432, I/O @ 0x00002000/128, BIOS @ 0x????????/524288

Further, with Optimus, the nVidia card has no connection to the display, so can't detect it.

The log reads as if Xorg started properly, found nothing to do, then shut down properly.

As a test
Code:
emerge -1 twm xclock xterm
then try startx
_________________
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
Anton Gubarkov
n00b
n00b


Joined: 13 Mar 2008
Posts: 65

PostPosted: Fri Nov 09, 2018 7:59 am    Post subject: Reply with quote

@NeddySeagoon, thanks for pointing out. My P52 allows 2 configs in UEFI - pure discrete and hybrid (i.e. optimus). The internal display panel is "re-wired" between intel and nvidia cards by UEFI. When in discrete mode, intel card cannot be seen on PCIe bus.

The log I attached was from pure discrete run.

I managed to run Gnome+GDM in both configs (with tweaking of /etc/X11/xorg.conf.d and eselect opengl) . The caveat in my case was incorrect setting of eselect opengl. When this setting does not match the main X server, I get blank screen.


  • I can run Gnome+GDM on Intel (loosing my external outputs DP and HDMI) and use bumblebee to run demanding apps on nvidia but displaying the window on laptop screen. I get approx 12W consumption in idle since bbswitch does awesome job managing nvidia card power.
  • I can run Gnome+GDM in PRIME mode on nvidia, intel card driving internal display, nvidia card driving the main X server and also external monitors. Brightness control works as expected. I get 35W consumption in idle
  • I can run in pure discrete mode - I couldn't make internal screen brightness control work in this scenario. I get 35W consumption in idle


My goal now is to be able to switch between pure intel and PRIME on nvidia without much fuzz with files and eselect opengl.
When I'm connected to an external monitor, that monitor must have power to work, so I can get power too and do not care too much about my consumption.
When I'm on the road, I don't need external ports working and would like to switch to Intel+bumblebee mode to have longer battery.

My plan is:


  • configure GDM to always run on Intel card via wayland
  • configure 2 gnome sessions to run: a) on Intel card via X; b) on Nvidia card + PRIME


I have the working X config with 2 Server layouts that I can use to start X sessions from the terminal:
Code:

Section "ServerLayout"
    Identifier "nvidia-prime"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "ServerLayout"
    Identifier "intel"
    Screen 0 "intel"
EndSection


Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration"
EndSection
Section "Screen"
    Identifier "intel"
    Device "intel"
    #Option "UseDisplayDevice" "none"
    Option "AllowEmptyInitialConfiguration"
EndSection


Section "Device"
   Identifier  "nvidia"
   Driver      "nvidia"
   BusID       "PCI:1:0:0"
EndSection


Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0:2:0"
    Option "DRI" "3"
EndSection



Code:
eselect opengl set xorg-x11; startx -- -layout intel
starts intel-only gnome session
Code:
eselect opengl set nvidia; startx -- -layout nvidia-prime
starts nvidia+PRIME gnome session


I'm looking for ways to influence the way gdm starts an X display server for the user session. I'd appreciate some guidance in this matter.
Back to top
View user's profile Send private message
Anton Gubarkov
n00b
n00b


Joined: 13 Mar 2008
Posts: 65

PostPosted: Fri Nov 09, 2018 12:28 pm    Post subject: Reply with quote

So I understood that gnome-session doesn't start any X server itself, it expects it is started by other means before gnome-session is invoked.

When I use startx, X server is started by startx script. When I use GDM, it is started by GDM.
I searched the source of GDM for traces of X server invocation. It turned out that the path to X server is determined by configure.ac at compile time

See https://gitlab.gnome.org/GNOME/gdm/blob/master/configure.ac at line 1123 ( at the time of writing)

Code:

dnl ---------------------------------------------------------------------------
dnl - Check for X Server location
dnl ---------------------------------------------------------------------------

# First check with "! -h" for /usr/X11R6 and /usr/X11 since they often
# symlink to each other, and configure should use the more stable
# location (the real directory) if possible.
#
# On Solaris, the /usr/bin/Xserver script is used to decide whether to
# use Xsun or Xorg, so this is used on Solaris.
#
# When testing for /usr/X11R6, first check with "! -h" for /usr/X11R6
# and /usr/X11 since they often symlink to each other, and configure
# should use the more stable location (the real directory) if possible.
#
if test -x /usr/bin/X; then
   X_PATH="/usr/bin"
   X_SERVER_PATH="/usr/bin"
   X_SERVER="/usr/bin/X"
elif test -x /usr/X11/bin/Xserver; then
   X_PATH="/usr/X11/bin"
   X_SERVER_PATH="/usr/X11/bin"
   X_SERVER="/usr/X11/bin/Xserver"
elif test ! -h /usr/X11R6 -a -x /usr/X11R6/bin/X; then
   X_PATH="/usr/X11R6/bin"
   X_SERVER_PATH="/usr/X11R6/bin"
   X_SERVER="/usr/X11R6/bin/X"
elif test ! -h /usr/X11 -a -x /usr/X11/bin/X; then
   X_PATH="/usr/X11/bin"
   X_SERVER_PATH="/usr/X11/bin"
   X_SERVER="/usr/X11/bin/X"
elif test -x /usr/X11R6/bin/X; then
   X_PATH="/usr/X11R6/bin"
   X_SERVER_PATH="/usr/X11R6/bin"
   X_SERVER="/usr/X11R6/bin/X"
elif test -x /usr/bin/Xorg; then
   X_PATH="/usr/bin"
   X_SERVER_PATH="/usr/bin"
   X_SERVER="/usr/bin/Xorg"
elif test -x /usr/X11/bin/X; then
   X_PATH="/usr/X11/bin"
   X_SERVER_PATH="/usr/X11/bin"
   X_SERVER="/usr/X11/bin/X"
elif test -x /usr/openwin/bin/Xsun; then
   # Do not add /usr/openwin/bin here because on Solaris you need
   # /usr/openwin/bin in your PATH even if you are using the Xorg
   # Xserver.  We add this to the path below.
   X_PATH="/usr/openwin/bin"
   X_SERVER_PATH="/usr/openwin/bin"
   X_SERVER="/usr/openwin/bin/Xsun"
elif test -x /opt/X11R6/bin/X; then
   X_PATH="/opt/X11R6/bin"
   X_SERVER_PATH="/opt/X11R6/bin"
   X_SERVER="/opt/X11R6/bin/X"
else
   # what to do, what to do, this is wrong, but this just sets the
   # defaults, perhaps this user is cross compiling or some such
   X_PATH="/usr/bin/X11:/usr/X11R6/bin:/opt/X11R6/bin"
   X_SERVER_PATH="/usr/bin"
   X_SERVER="/usr/bin/X"
fi


Further searching gdm repo for X_SERVER reveals https://gitlab.gnome.org/GNOME/gdm/blob/master/daemon/gdm-x-session.c at line 194 - a function spawn_x_server is defined, that is called later at https://gitlab.gnome.org/search?utf8=%E2%9C%93&search=X_SERVER&group_id=&project_id=1856&search_code=true&repository_ref=master#L873.
There is no other references to X_SERVER in the code. So I conclude that X server is started by GDM using spawn_x_server for every user/greeter session.

Looking further into spawn_x_server code I find out that the list of command line options for the X server is build in a very static fashion, only debug, log verbosity, network listen, virtual console, auth file. There is no code to parse additional comamnd line parameters, environment variables or anything like this.
So the conclusion is - GDM is not capable of starting different X servers in different sessions now. I'll try to discuss options with gdm developers
Back to top
View user's profile Send private message
Anton Gubarkov
n00b
n00b


Joined: 13 Mar 2008
Posts: 65

PostPosted: Wed Dec 19, 2018 7:11 pm    Post subject: Reply with quote

I continue my journey into making Optimus work well for my Thinkpad P52.

I can't still figure out how to manage this without restarting my PC, however I managed to make the Xorg follow the configuration set in UEFI firmware without further involvement from my side. This is not a universal works-everywhere approach. It is just a hack that allows me to switch between Intel+Bumblebee and pure Nvidia configs.

  • I had to create 2 xorg configs for the scenarios: (I've put them into a lib subdir of /etc/X11/xorg.conf.d to hide from Xorg)

    /etc/X11/xorg.conf.d/lib/10-intel.conf
    Code:
    Section "Device"
       Identifier  "Intel Graphics UHD 630 (Mobile)"
    #  intel/sna driver is broken for CoffeLake. BusID is required for modesetting driver to work
       BusID      "PCI:0:2:0"
       Driver      "modesetting"
       Option      "AccelMethod"    "glamor"
       Option      "DRI"            "3"
    EndSection

    /etc/X11/xorg.conf.d/lib/10-nvidia.conf
    Code:
    Section "Device"
            Identifier  "Nvidia Quadro P2000M"
            Driver      "nvidia"
            BusID       "PCI:1:0:0"
    EndSection

  • I use lspci output to see if I have an intel (vendor 8086) VGA device (device class 0300) and if it is found, I switch opengl to xorg-x11 and ln -s the intel xorg config to lib/10-intel.conf cited above. I achieve this with this new systemd service file:
    Code:
    [Unit]
    Description=switch opengl implementation between MESA and NVIDIA based on the presence of Intel integrated graphics
    Before=display-manager.service

    [Service]
    Type=oneshot
    # the following line contains systemd-escape'd strings for sed to remove double-quotes from lspci output
    ExecStart=/bin/bash -c 'if lspci\x20\x2dmn\x7csed\x20s-\x5c\x22--g|/bin/grep -F "0300\x208086"; then /usr/bin/eselect opengl set xorg-x11; /bin/ln -sf /etc/X11/xorg.conf.d/lib/10-intel.conf /etc/X11/xorg.conf.d/10-display.conf; else /usr/bin/eselect opengl set nvidia;  /bin/ln -sf /etc/X11/xorg.conf.d/lib/10-nvidia.conf /etc/X11/xorg.conf.d/10-display.conf ; fi'
    ExecStop=/bin/rm /etc/X11/xorg.conf.d/10-display.conf
    RemainAfterExit=true
    StandardOutput=journal

    [Install]
    WantedBy=graphical.target


Back to top
View user's profile Send private message
bandreabis
Advocate
Advocate


Joined: 18 Feb 2005
Posts: 2490
Location: イタリアのロディで

PostPosted: Tue Feb 09, 2021 11:49 am    Post subject: Reply with quote

duane wrote:
I've had prime working on my acer e15 for quite a while now, and the HDMI out works, but I'm pretty sure the intel driver is running that without the nvidia gpu. (xrandr --listproviders shows 0 outputs from nvidia.) All I have to do is use xrandr to mirror the display -- I haven't bothered with anything more complicated.

I can get the nouveau driver to use the nvidia chip for games, but I have to set the power mode on the nvidia chip manually to get any acceleration. It doesn't really give me much better framerates than the intel driver, and it runs a lot hotter, so I don't use it much. If I cared to use the proprietary drivers, it might work better.

There wasn't any setup involved with my system except to enable the kernel drivers.


Hi.
As I think nothing changed from 2018 about these strange hybrid, I resume this thread.
Do you have this Acer yet?
Could you describe me your configuration?

Many thanks.

andrea
_________________
Il numero di post non fa di me un esperto! Anzi!
Back to top
View user's profile Send private message
psycho
Guru
Guru


Joined: 22 Jun 2007
Posts: 534
Location: New Zealand

PostPosted: Tue Feb 09, 2021 2:03 pm    Post subject: Reply with quote

I have an ancient Optimus netbook (an Eee PC 1215n) that was fully working many years ago (booted into the Intel driver, but could activate the Nvidia chipset too). I remember it required a *lot* of fiddling to get it working: X always used the Intel driver for the desktop, but specific applications could be launched via a script that used the Nvidia hardware to draw them (I think some kind of Optimus software server had to be running to handle them...it was a headache to set up but worked nicely once it was). It wasn't a vast improvement, but it made enough of a difference (maybe three or four times higher frame-rates or something like that) that I did used to do things that way for a while. In the end though I chose to save power by switching the Nvidia hardware off (not possible in the BIOS but there was a software tool to do it after booting) because I wasn't doing anything on the netbook that justified the Nvidia's shortening my battery life.

That was many years ago and I'm curious to see if things have improved since then...I could dig out the netbook and see how things work with recent kernels/drivers. Not sure how relevant it will be to your setup, but I imagine different Optimus machines might work similarly.
Back to top
View user's profile Send private message
bandreabis
Advocate
Advocate


Joined: 18 Feb 2005
Posts: 2490
Location: イタリアのロディで

PostPosted: Tue Feb 09, 2021 3:14 pm    Post subject: Reply with quote

psycho wrote:
I have an ancient Optimus netbook (an Eee PC 1215n) that was fully working many years ago (booted into the Intel driver, but could activate the Nvidia chipset too). I remember it required a *lot* of fiddling to get it working: X always used the Intel driver for the desktop, but specific applications could be launched via a script that used the Nvidia hardware to draw them (I think some kind of Optimus software server had to be running to handle them...it was a headache to set up but worked nicely once it was). It wasn't a vast improvement, but it made enough of a difference (maybe three or four times higher frame-rates or something like that) that I did used to do things that way for a while. In the end though I chose to save power by switching the Nvidia hardware off (not possible in the BIOS but there was a software tool to do it after booting) because I wasn't doing anything on the netbook that justified the Nvidia's shortening my battery life.

That was many years ago and I'm curious to see if things have improved since then...I could dig out the netbook and see how things work with recent kernels/drivers. Not sure how relevant it will be to your setup, but I imagine different Optimus machines might work similarly.


I installed nouveau hoping at least to connect by HDMI, but cannot get through
_________________
Il numero di post non fa di me un esperto! Anzi!
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
Page 1 of 1

 
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