Arch Linux

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Laptop resolution issue

Hi all,

I am trying to change my display resolution, but except "native" resolution, every change ends up with black screen.
Also I d prefer to only use the intel gpu (I d prefer longer runtime and currently have no graphic intensive apps...)

- Alienware 17r5
- intel/nvidia gpus
- no BIOS setting to disable integrated gpu
- using nouveau drivers
- using i3 (no display manager)

xrandr --listproviders

Providers: number : 2
Provider 0: id: 0xd1 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 4 outputs: 3 associated providers: 1 name:nouveau
Provider 1: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 1 name:Intel

xrandr -q

Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 382mm x 214mm
   2560x1440    120.05*+  60.02  
   1920x1200    119.92  
   1920x1080    119.96  
   1600x1200    119.92  
   1680x1050    119.95  
   1400x1050    119.95  
   1280x1024    119.96  
   1280x960     119.89  
   1152x864     119.91  
   1024x768     119.93  
   800x600      119.93  
   640x480      119.80  
   720x400      119.86  
   640x400      119.86  
   640x350      119.98  
HDMI-4 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

I have tried to add new modes ( eg cvt 1920 1080) with xrandr
-> switching output to new/added mode -> black screen

scale is working - but using modes is preferred due to several reasons...

xrandr --output eDP-1 --scale ... // works

xinitrc

...
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
exec i3

mkinticpio.conf

...
MODULES=(i915)
...

grub

...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
...

/etc/X11/xorg.conf.d/10-monitor.conf (I am not using xorg.conf)

Section "Monitor"
    Identifier             "DP1"
    DisplaySize            382 214
#    Modeline "1920x1200_x119.9"  410.57  1920 2080 2288 2656  1200 1203 1209 1289 -hsync +vsync
#   Option "PreferredMode" "1920x1080_119.9"
EndSection

Section "Extensions"
    Option      "DPMS" "Disable"
EndSection

pastebin Xorg.0.log
pastebin Xorg.0.log

I am still clueless where this issues result from. Is it from xorg or is it the two gpus that issue the trouble.
Any help highly appreciated. (Also for tips for deactivating the discrete (nvidia) card.
Thanks in advance

Ailen

Member

Registered: 2014-05-01

Posts: 32

Re: Laptop resolution issue

I looked at the Xorg.0.log you pastebinned. Is this log from a good run, or with the error?
How are you changing resolution?
The modeline and preferred mode in 10-monitor.conf is commented out. I'm assuming you did that so it used the default resolution?

Open a terminal.
Run

xrandr --output DP1 --mode 1920x1080

or however you were changing resolution.
Hit ctrl-alt-f2 and grab the logged output from xorg. Specifically, what X has to say for itself after you change the resolution.
Post that log here.

I couldn't see any actual errors or anything that would explain why you're having that problem. And most of the information you provided wasn't exactly useful. Provide a log showing the change of display resolution and any errors X throws as a result.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

Do you also use compton (or any compositor)?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

a) How are you changing resolution?
b) Run

xrandr --output DP1 --mode 1920x1080

or however you were changing resolution.
c) Provide a log showing the change of display resolution and any errors X throws as a result.

a) b)
As I have written I use cvt and xrandr to add a new mode.
If I try to use one of the listed modes from xrandr - like in your example - I get: cannot find mode 1920x1080

here is how I try to change resolution

cvt 1920 1080 119.92
xrandr --newmode "1920x1080_119.92"  369.25  1920 2080 2288 2656  1080 1083 1088 1160 -hsync +vsync
xrandr --addmode eDP-1 "1920x1080_119.92"
xrandr --output DP1 --mode 1920x1080_119.92

c) log after black screen / changing resolution

[  1818.208] (II) NOUVEAU(0): EDID vendor "AUO", prod id 5270
[  1818.208] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[  1818.208] (II) NOUVEAU(0): Modeline "2560x1440"x0.0  499.60  2560 2608 2640 2720  1440 1443 1448 1530 +hsync -vsync (183.7 kHz eP)
[  1818.208] (II) NOUVEAU(0): Modeline "2560x1440"x0.0  499.60  2560 2608 2640 2720  1440 1443 1448 3060 +hsync -vsync (183.7 kHz e)
[  1818.265] (II) NOUVEAU(0): EDID vendor "AUO", prod id 5270
[  1818.265] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[  1818.265] (II) NOUVEAU(0): Modeline "2560x1440"x0.0  499.60  2560 2608 2640 2720  1440 1443 1448 1530 +hsync -vsync (183.7 kHz eP)
[  1818.265] (II) NOUVEAU(0): Modeline "2560x1440"x0.0  499.60  2560 2608 2640 2720  1440 1443 1448 3060 +hsync -vsync (183.7 kHz e)
[  1866.711] resize called 1920 1080
[  1873.397] (**) Option "fd" "28"
[  1873.397] (II) event2  - Power Button: device removed
[  1873.398] (**) Option "fd" "45"
[  1873.398] (II) event3  - Video Bus: device removed
[  1873.398] (**) Option "fd" "20"
[  1873.398] (II) event4  - Video Bus: device removed
[  1873.399] (**) Option "fd" "31"
[  1873.399] (II) event1  - Power Button: device removed
[  1873.399] (**) Option "fd" "27"
[  1873.399] (II) event19 - Integrated_Webcam_FHD: Integrat: device removed
[  1873.399] (**) Option "fd" "23"
[  1873.399] (II) event17 - Synaptics TM3394-001: device removed
[  1873.400] (**) Option "fd" "24"
[  1873.400] (II) event6  - Intel HID events: device removed
[  1873.400] (**) Option "fd" "29"
[  1873.400] (II) event9  - Dell WMI hotkeys: device removed
[  1873.401] (**) Option "fd" "25"
[  1873.401] (II) event5  - AT Translated Set 2 keyboard: device removed
[  1873.401] (**) Option "fd" "26"
[  1873.401] (II) event18 - PS/2 Generic Mouse: device removed
[  1873.401] (II) AIGLX: Suspending AIGLX clients for VT switch
[  1873.402] (II) NOUVEAU(0): NVLeaveVT is called.
[  1873.402] (II) systemd-logind: got pause for 13:68
[  1873.403] (II) systemd-logind: got pause for 13:81
[  1873.403] (II) systemd-logind: got pause for 13:70
[  1873.403] (II) systemd-logind: got pause for 13:69
[  1873.403] (II) systemd-logind: got pause for 13:82
[  1873.403] (II) systemd-logind: got pause for 13:83
[  1873.403] (II) systemd-logind: got pause for 13:66
[  1873.403] (II) systemd-logind: got pause for 13:73
[  1873.403] (II) systemd-logind: got pause for 13:65
[  1873.403] (II) systemd-logind: got pause for 226:1
[  1873.403] (II) systemd-logind: got pause for 226:0
[  1873.403] (II) systemd-logind: got pause for 13:67

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

Do you also use compton (or any compositor)?

yep I used compton - but have uninstalled few days ago in context of the testings .
Not aware of any other compositors (checked xinitrc and i3 conf for possible referrals)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

I assume it's because you're running on the nvidia chip, but the output is on the intel one and the res change doesn't get mapped properly. You might try dropping xf86-video-intel and/or xf86-video-nouveau and see whether the modesetting driver performs better.
Since you seem to have configured https://wiki.archlinux.org/index.php/NV … phics_only but that contradicts your stated desires, i'd suggest to just stop that configuration and apply one of the available methods to dynamically invoke the nvidia chip and likely "fix" errr… sidestep this issue btw.

nb. that the mentioned configuration in the link doesn't have to be xorg.conf - any file in /{etc,usr/share}/X11/xorg.conf.d with a matching content would cause this.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

Thanks seth! Got one step further. As you recommended I removed intel and noeuveau to test out
the modesetting drivers. The first difference is that I now have a lots more possible modes (which is nice)

So current status:
- xf86-video-intel - installed (but module not loaded via mkinitcpio)
- xf86-video-nouveau
- removed all *confs from /xorg.conf.d

Now the fun part. After testing new modes I got my usual black screen.
For that reason I opened a new terminal to check the Xorg log.
After switching back again to tty1 the new resolution worked (I tested 1600x1200)
So I checked if I simply did not wait long enough for the new resolution, but
the resolution only gets active when I switch from another console.

I assume it's because you're running on the nvidia chip, but the output is on the intel one and the res change doesn't get mapped properly.

Looks like your assumption is correct and the AIGLX needs some manual refresh to resume.
From my Xorg.log - I guess this is the part where I switch between ttys

25.153] (II) AIGLX: Suspending AIGLX clients for VT switch
[    25.260] (II) systemd-logind: got pause for 13:65
[    25.260] (II) systemd-logind: got pause for 13:66
[    25.260] (II) systemd-logind: got pause for 13:83
[    25.260] (II) systemd-logind: got pause for 13:72
[    25.260] (II) systemd-logind: got pause for 226:1
[    25.260] (II) systemd-logind: got pause for 13:67
[    25.260] (II) systemd-logind: got pause for 226:0
[    25.260] (II) systemd-logind: got pause for 13:82
[    25.260] (II) systemd-logind: got pause for 13:70
[    25.260] (II) systemd-logind: got pause for 13:69
[    25.260] (II) systemd-logind: got pause for 13:68
[    25.260] (II) systemd-logind: got pause for 13:73
[    26.895] (II) systemd-logind: got resume for 13:65
[    26.935] (II) systemd-logind: got resume for 13:66
[    26.962] (II) systemd-logind: got resume for 13:83
[    26.984] (II) systemd-logind: got resume for 13:72
[    26.984] (II) systemd-logind: got resume for 226:1
[    27.015] (II) systemd-logind: got resume for 13:67
[    27.015] (II) systemd-logind: got resume for 226:0
[    27.015] (II) Open ACPI successful (/var/run/acpid.socket)
[    27.015] (II) AIGLX: Resuming AIGLX clients after VT switch
[    27.154] (II) modeset(0): EDID vendor "AUO", prod id 5270

So may the systemd-logind somehow be the reason that pauses the resolution switch or
issues with AIGLX?
Your opinion?

Last edited by aliedtke (2019-08-27 18:12:04)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

You cannot block xf86-video-intel via mkinitcpio (or any kernel related stuff unless you successfully block i915, what means the intel chip cannot be used at all) - also that doesn't really address the optimus situation.

Please post an updated xorg log so we can see where you're at.
And please use "code" tags, not "quote" tags (unless you're actually quoting somebody - shell output and file contents etc. are more readable and scrollable in code tags)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

Sure - sorry for the formatting.
The intel part was only for your information. As initially remarked I d even prefer
to deactivate the nvidia card for reasons.

However here the xorg log

[    70.731] (II) modeset(0): Allocate new frame buffer 1600x1200 stride
[    73.421] (**) Option "fd" "22"
[    73.422] (II) event2  - Power Button: device removed
[    73.422] (**) Option "fd" "25"
[    73.422] (II) event3  - Video Bus: device removed
[    73.422] (**) Option "fd" "26"
[    73.422] (II) event4  - Video Bus: device removed
[    73.422] (**) Option "fd" "27"
[    73.422] (II) event1  - Power Button: device removed
[    73.422] (**) Option "fd" "28"
[    73.422] (II) event8  - Integrated_Webcam_FHD: Integrat: device removed
[    73.422] (**) Option "fd" "29"
[    73.422] (II) event10 - Synaptics TM3394-001: device removed
[    73.422] (**) Option "fd" "30"
[    73.422] (II) event6  - Intel HID events: device removed
[    73.423] (**) Option "fd" "31"
[    73.423] (II) event9  - Dell WMI hotkeys: device removed
[    73.423] (**) Option "fd" "32"
[    73.423] (II) event5  - AT Translated Set 2 keyboard: device removed
[    73.423] (**) Option "fd" "33"
[    73.423] (II) event19 - PS/2 Generic Mouse: device removed
[    73.423] (II) AIGLX: Suspending AIGLX clients for VT switch
[    73.527] (II) systemd-logind: got pause for 13:83
[    73.527] (II) systemd-logind: got pause for 226:0
[    73.527] (II) systemd-logind: got pause for 13:65
[    73.527] (II) systemd-logind: got pause for 13:68
[    73.527] (II) systemd-logind: got pause for 13:67
[    73.527] (II) systemd-logind: got pause for 13:74
[    73.527] (II) systemd-logind: got pause for 13:69
[    73.527] (II) systemd-logind: got pause for 13:73
[    73.527] (II) systemd-logind: got pause for 13:70
[    73.527] (II) systemd-logind: got pause for 13:66
[    73.527] (II) systemd-logind: got pause for 226:1
[    73.527] (II) systemd-logind: got pause for 13:72
[    75.575] (II) systemd-logind: got resume for 13:83
[    75.575] (II) systemd-logind: got resume for 226:0
[    75.609] (II) systemd-logind: got resume for 13:65
[    75.626] (II) systemd-logind: got resume for 13:68
[    75.655] (II) systemd-logind: got resume for 13:67
[    75.682] (II) systemd-logind: got resume for 13:74
[    75.709] (II) systemd-logind: got resume for 13:69
[    75.735] (II) systemd-logind: got resume for 13:73
[    75.762] (II) systemd-logind: got resume for 13:70
[    75.789] (II) systemd-logind: got resume for 13:66
[    75.789] (II) systemd-logind: got resume for 226:1
[    75.789] (II) Open ACPI successful (/var/run/acpid.socket)
[    75.789] (II) AIGLX: Resuming AIGLX clients after VT switch
[    75.930] (II) modeset(0): EDID vendor "AUO", prod id 5270
[    75.930] (II) modeset(0): Printing DDC gathered Modelines:
[    75.930] (II) modeset(0): Modeline "2560x1440"x0.0  499.60  2560 2608 2640 2720  1440 1443 1448 1530 +hsync -vsync (183.7 kHz eP)
[    75.930] (II) modeset(0): Modeline "2560x1440"x0.0  499.60  2560 2608 2640 2720  1440 1443 1448 3060 +hsync -vsync (183.7 kHz e)
[    76.409] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    76.409] (II) event2  - Power Button: device is a keyboard
[    76.410] (II) event3  - Video Bus: is tagged by udev as: Keyboard
[    76.410] (II) event3  - Video Bus: device is a keyboard
[    76.410] (II) event4  - Video Bus: is tagged by udev as: Keyboard
[    76.410] (II) event4  - Video Bus: device is a keyboard
[    76.411] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    76.411] (II) event1  - Power Button: device is a keyboard
[    76.411] (II) event10 - Synaptics TM3394-001: is tagged by udev as: Touchpad
[    76.412] (II) event10 - Synaptics TM3394-001: device is a touchpad
[    76.413] (II) event6  - Intel HID events: is tagged by udev as: Keyboard
[    76.413] (II) event6  - Intel HID events: device is a keyboard
[    76.413] (II) event9  - Dell WMI hotkeys: is tagged by udev as: Keyboard
[    76.413] (II) event9  - Dell WMI hotkeys: device is a keyboard
[    76.414] (II) event5  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    76.414] (II) event5  - AT Translated Set 2 keyboard: device is a keyboard
[    76.415] (II) event19 - PS/2 Generic Mouse: is tagged by udev as: Mouse
[    76.415] (II) event19 - PS/2 Generic Mouse: device is a pointer
[    76.415] (II) systemd-logind: got resume for 13:72
[    76.415] (II) event8  - Integrated_Webcam_FHD: Integrat: is tagged by udev as: Keyboard
[    76.416] (II) event8  - Integrated_Webcam_FHD: Integrat: device is a keyboard

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

That's not an xorg log. At best a fraction.

About the nvidia chip, did you review the link I posted before?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

That is the part that shows the log from the resolution switch - however here the complete Xorg.0.log.
As a comment - I have meanwhile put the xrandr mode in the xinitrc
Xorg.0.log pastebin

About the nvidia chip, did you review the link I posted before?

Yeah - already tested this and several similar (eg with both cards listed) confs  in the past.
Nothing worked. Either black screen or no effect.
I also tested prime & Co
I also experimented with bbswitch.
Additional I tried nvidia-settings, which shows modes but does not allow to select
a different one than the native.

If you think its worth to give the link another try I ll go for it and set it up again.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

You're still using xf86-video-intel for the intel chip and yes, I'm pretty sure configuring the optimus system correctly is worth a shot.

Instead of "Nothing worked." please first figure what behavior you prefer and if you want to use the nvidia or the nouveau driver (which to some extent will define your further options)
Then list your exact steps, where you struggle and the results (incl. the xorg logs)

nvidia-settings won't work for display config since you're dealing w/ an intel output (it probably would if you were running on the nvidia chip, using the prop. kernel module/driver and dealing w/ an nvidia output, likely the hdmi ones)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

sure - step by step plus updated Xorg.0.log:

- removed intel drivers
- installed latest nvidia drivers
- black screen login / login working and xorg took
- adding nvidia nvidia_modeset nvidia_uvm nvidia_drm to mkinitcpio.conf
- run/update mkinitcpio
- lspci | egrep 'VGA|3D'
-> 01:00.0 VGA compatible controller: NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] (rev a1)
- create /etc/X11/xorg.conf

Section "Module"
    Load "modesetting"
EndSection

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

- editing ~/.xinitrc

#!/bin/sh
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
exec i3

- reboot
- still black boot screen (gonna edit grub for that later - blind login OK for the moment)
- startx
- xrandr -q

Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
HDMI-0 disconnected primary (normal left inverted right x axis y axis)
DP-0 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 382mm x 214mm
   2560x1440    120.05*+  60.02
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)

- xrandr --output DP-0 --mode 1600x1200
-> xrandr: cannot find mode 1600x1200

cvt 1920 1080
xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync
xrandr --addmode DP-0 "1920x1080_60.00"
xrandr --addmode DP-0 "1920x1080_60.00"                                                           
X Error of failed request:  BadMatch (invalid parameter attributes)
Major opcode of failed request:  140 (RANDR)
Minor opcode of failed request:  18 (RRAddOutputMode)
Serial number of failed request:  54
Current serial number in output stream:  55

new Xorg.0.log

loqs

Member

Registered: 2014-03-06

Posts: 19,100

Re: Laptop resolution issue

The new Xorg.log does not show /etc/X11/xorg.conf or nvidia being used.  Could it be the wrong log?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

 lspci | egrep 'VGA|3D'
-> 01:00.0 VGA compatible controller: NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] (rev a1)

Wowwaitwhat? There's no intel VGA chip in lspci??

Adding to loqs' comment: it's the same xorg log you posted before.

The posted /etc/X11/xorg.conf is not suitable for a setup that tries to avoid the nvidia GPU (nor are the xrandr calls in your xinitrc)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

Sorry - for some reason the .local Xorg.0.log is no longer updated (didnt recheck before posting) - instead it now uses /var/log/Xorg.0.log...

new nvidia Xorg.0.log

xrandr lists both cards

xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x1f1 cap: 0x1, Source Output crtcs: 4 outputs: 4 associated providers: 1 name:NVIDIA-0
Provider 1: id: 0x47 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 5 associated providers: 1 name:modesetting

Last edited by aliedtke (2019-08-27 21:09:08)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

The log fits the present setup towards X11 on the nvidia chip.
a) do you have a "black screen" issue with this?
b) did you try whether the original problem persists?
c) what did you (intend to) try to gear towards a "prefer intel" setup?

The nvidia blob doesn't support rootless X11, thus the relocated log - https://wiki.archlinux.org/index.php/Xorg#General

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

The log fits the present setup towards X11 on the nvidia chip.
a) do you have a "black screen" issue with this?
b) did you try whether the original problem persists?
c) what did you (intend to) try to gear towards a "prefer intel" setup?
The nvidia blob doesn't support rootless X11, thus the relocated log - https://wiki.archlinux.org/index.php/Xorg#General

a) No - but I can not change the resolution at all.
As posted before there is only one resolution available and adding new modes with xrandr does not work.
b) do not understand. can you explain first
c) no - atm I only did the changes in regards of your link and nothing else

Thanks for the info on the nvidia/Xorg log.

I didnt know about the optimus-manager so far, however maybe this also of your interest,
because it includes some useful additional info on that topic in general.
https://github.com/Askannz/optimus-mana … leshooting
https://github.com/Bumblebee-Project/Bu … issues/764

I meanwhile think it is probably not some kind of misconfiguration or the drivers itself - its more
some bad or individual hardware design for that specific notebook

If you have further ideas - they are well welcome. So far thanks y lot for your efforts and support.
I will continue tomorrow with testing further different setups and report the outcome

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

b) referred to the resolution issue. Given there's only one resolution that's oc. moot (though you could try adding some by hand)

The optimus wiki page has a thorough description of all possible setups of an optimus system, so please review it, make up your mind for a preferred scenario and setup your system accordingly. I'm pretty sure that this will work once you're running on the intel chip (as you intend to do anyway)

Regardless of that, we might have to discuss what you're actually trying to achive by reducing the resolution, because this is most likely an xy-problem.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

Update on my journey to make only intel run. bbswitch is not a real option cause I have to the install bumblebee and then there still remain a lot of ifs and whens,
that make it somehow improbable for my hardware...
So I decided to go via the acpi_call but unfortunately ran into the next problems.
Installation and execution is working, however the module does not start correct at boot time.

journalctl -o short-precise -k | grep "acpi"
Aug 28 21:37:04.084582 000 kernel: acpi_call: loading out-of-tree module taints kernel.
Aug 28 21:37:04.084589 000 kernel: acpi_call: module verification failed: signature and/or required key missing - tainting kernel

Nevertheless of the issues of acpi_call  I gave it at try and disabled the nivdia bus, which then rewarded me with a complete black screen on boot... (expected)
Meanwhile I start to get used to switch between ttys to make the resolution change work

I will now tryout the optimus-manager.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

That's not "incorrect" behavior, the kernel informs you that you're loading an unverified out of tree module. You can ignore that.
If you still have the xorg config and xrandr calls in place, you'll get no output from X11 if the nvidia chip doesn't work.

Before even trying to deactivate the nvidia chip, you should move the X11 server config to the intel chip.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

If you still have the xorg config and xrandr calls in place, you'll get no output from X11 if the nvidia chip doesn't work. Before even trying to deactivate the nvidia chip, you should move the X11 server config to the intel chip.

My current setup is only the intel driver installed (Because the driver setup is unclear, I decided to go with intel drivers, cos they offer same modes like pure modesetting drivers, which is far more that nvidia or noouveau offers atm).
Further on I currently do not use any xorg.conf and no xrandr calls in xintitrc.
So in summary - current setup "raw" with only intel drivers installed.

That's not "incorrect" behavior, the kernel informs you that you're loading an unverified out of tree module. You can ignore that.

Thanks - was not sure about it. I give it another try now then.

PS optimus-manager directly led me into another boot black screen...

Last edited by aliedtke (2019-08-28 20:41:27)

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

/usr/share/acpi_call/examples/turn_off_gpu.sh

Trying \_SB.PCI0.P0P1.VGA._OFF: works!
Trying \_SB.PCI0.P0P2.VGA._OFF: works!
Trying \_SB_.PCI0.OVGA.ATPX: works!
Trying \_SB_.PCI0.OVGA.XTPX: works!
Trying \_SB.PCI0.P0P3.PEGP._OFF: works!
Trying \_SB.PCI0.P0P2.PEGP._OFF: works!
Trying \_SB.PCI0.P0P1.PEGP._OFF: works!
Trying \_SB.PCI0.MXR0.MXM0._OFF: works!
Trying \_SB.PCI0.PEG1.GFX0._OFF: works!
Trying \_SB.PCI0.PEG0.GFX0.DOFF: works!
Trying \_SB.PCI0.PEG1.GFX0.DOFF: works!
Trying \_SB.PCI0.PEG0.PEGP._OFF: works!
Trying \_SB.PCI0.XVR0.Z01I.DGOF: works!
Trying \_SB.PCI0.PEGR.GFX0._OFF: works!
Trying \_SB.PCI0.PEG.VID._OFF: works!
Trying \_SB.PCI0.PEG0.VID._OFF: works!
Trying \_SB.PCI0.P0P2.DGPU._OFF: works!
Trying \_SB.PCI0.P0P4.DGPU.DOFF: works!
Trying \_SB.PCI0.IXVE.IGPU.DGOF: works!
Trying \_SB.PCI0.RP00.VGA._PS3: works!
Trying \_SB.PCI0.RP00.VGA.P3MO: works!
Trying \_SB.PCI0.GFX0.DSM._T_0: works!
Trying \_SB.PCI0.LPC.EC.PUBS._OFF: works!
Trying \_SB.PCI0.P0P2.NVID._OFF: works!
Trying \_SB.PCI0.P0P2.VGA.PX02: works!
Trying \_SB_.PCI0.PEGP.DGFX._OFF: works!
Trying \_SB_.PCI0.VGA.PX02: works!
Trying \_SB.PCI0.PEG0.PEGP.SGOF: works!
Trying \_SB.PCI0.AGP.VGA.PX02: works!

Far more working than expected.
Which one would you recommend to deactivate? This one: \_SB.PCI0.P0P2.NVID._OFF ?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,420

Re: Laptop resolution issue

None for now.
Try to force the server to use the intel device and post Xorg logs for a "black screen" session as well as w/ the snippet below.
(nb: that there must be NO /etc/X11/xorg.conf present as it would probably dominate the below)

/etc/X11/xorg.conf.d/20-force_intel.conf

Section "Device"
    Identifier "intel"
#    Driver "modesetting" # optional, also optionally "intel" instead of modesetting.
    BusID "PCI:0:2:0"
EndSection

Section "Screen"
    Identifier "IntelScreen"
    Device     "intel"
EndSection

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

aliedtke

Member

Registered: 2018-11-18

Posts: 27

Re: Laptop resolution issue

OK - no bus deactivated atm (however acpi_call running on boot)
I do not use an xorg.conf

Xorg log black screen

just rechecked BusID

sudo lshw -C display

 *-display                 
       description: VGA compatible controller
       product: GP104BM [GeForce GTX 1070 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:145 memory:9c000000-9cffffff memory:70000000-7fffffff memory:80000000-81ffffff ioport:5000(size=128) memory:c0000-dffff
  *-display
       description: Display controller
       product: UHD Graphics 630 (Mobile)
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm bus_master cap_list
       configuration: driver=i915 latency=0
       resources: irq:137 memory:9b000000-9bffffff memory:60000000-6fffffff ioport:6000(size=64)