Arch Linux

marrz

Member

Registered: 2012-08-28

Posts: 5

SDDM and GRUB on wrong screen !

I have a fresh X86 64 install running Repo-CK kernel, nvidia-ck-kx driver and  updated kde/plasma/sddm setup.

Linux 4.1.10-3-ck #1 SMP PREEMPT Wed Oct 7 16:42:29 EDT 2015 x86_64

Unfortunately both GRUB and SDDM login ONLY show up on my "secondary" display.
...which is usually OFF making boot and login a real pain.

I tried making changes to xorg.conf manually, then with "kdesu nvidia-settings" .and with xrandr but had no luck.
So I after all that I just recreated an xorg.conf  with "nvidia-xconfig"  now once the desktop is loaded it works well, it's just getting there thats the issue.

my xorg.conf

                                               
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 355.11  (buildmeister@swio-display-x86-rhel47-07)  Wed Aug 26 17:15:49 PDT 2015

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

SDDM conf is default except for the theme .. (it works)
my sddm.conf 

                                                         
[Autologin]
Relogin=false
Session=
User=

[General]
HaltCommand=/usr/bin/systemctl poweroff
Numlock=none
RebootCommand=/usr/bin/systemctl reboot

[Theme]
Current=archlinux-simplyblack
CursorTheme=Adwaita
FacesDir=/usr/share/sddm/faces
ThemeDir=/usr/share/sddm/themes

[Users]
DefaultPath=/bin:/usr/bin:/usr/local/bin
HideShells=
HideUsers=
MaximumUid=60000
MinimumUid=1000
RememberLastSession=true
RememberLastUser=true

[WaylandDisplay]
SessionCommand=/usr/share/sddm/scripts/wayland-session
SessionDir=/usr/share/wayland-sessions

[XDisplay]
DisplayCommand=/usr/share/sddm/scripts/Xsetup
DisplayStopCommand=/usr/share/sddm/scripts/Xstop
MinimumVT=7
ServerArguments=-nolisten tcp
ServerPath=/usr/bin/X
SessionCommand=/usr/share/sddm/scripts/Xsession
SessionDir=/usr/share/xsessions
XauthPath=/usr/bin/xauth
XephyrPath=/usr/bin/Xephyr

Im not sure if my grub config is needed but I would like to have my boot options and logins on my LCD (primary) screen ..
Thanks in advance for any help.

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: SDDM and GRUB on wrong screen !

Selecting a screen for Grub? I don't think that's possible.
But perhaps you can prioritize outputs in your bios setup.
Other than that - switch connectors.

---

1000

RJQ

Member

From: Los Angeles

Registered: 2010-06-25

Posts: 70

Website

Re: SDDM and GRUB on wrong screen !

Grub as Byte mentioned is going to follow the video card device order, and usually bios would not have options to change this, unless you are one the lucky ones, if not, for grub on a specific screen you need to change the order (hdmi, dvi, vga), if you can't due to having only one type of input in your devices then you can buy a cheap adapter (like hdmi to vga).

As for sddm, its been buggy on nvidia and more than one monitor, you can tweak the xorg further to make it behave, use an old version of sddm (I am still on 0.11.0-3) or switch loging manager. They (upstream) are aware of this bug, a fix is likely coming. Check this:

https://github.com/sddm/sddm/issues/496

---

Natural Spanish speaker person babbling English...
Natural Linux user babbling Archlinux...