| View previous topic :: View next topic |
| Author |
Message |
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
 Posted: Sun Jun 26, 2022 2:13 pm Post subject: Screen freeze after startx on NVIDIA, KDE with SDDM DM |
 |
|
Hi. I'm trying to install KDE on Gentoo.
After booting the system image just hangs, nothing happening - the last image before starting X session is showing
If I'm switching to TTY2, log in there, and type `startx`, everything hangs in that case also.
I was trying to fix by following this one https://wiki.gentoo.org/wiki/SDDM#SDDM_service_starts_but_yields_a_black_screen
Applied kernel settings from here: https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers#Kernel_compatibility
But nothing helps.
There are no errors at /var/log/Xorg.0.log
| Code: |
#: dmesg | grep nvidia
[ 1.668115] nvidia: loading out-of-tree module taints kernel.
[ 1.669036] nvidia: module license NVIDIA taints kernel.
[ 1.694004] nvidia-nvlink: Nvlink Core is being initialized, major device number 245
[ 1.695249] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[ 1.747937] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 510.73.05 Sat May 7 05:21:20 UTC 2022
[ 1.749495] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 1.750156] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[ 3.355071] nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
[ 3.396475] nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
[ 3.685720] nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
|
Log of sddm service from journalctl
| Code: |
-- Boot be8ab88969df41e7ab23283ff1a538e4 --
Jun 26 18:09:47 blackmorse systemd[1]: Started Simple Desktop Display Manager.
Jun 26 18:09:47 blackmorse sddm[540]: Initializing...
Jun 26 18:09:47 blackmorse sddm[540]: Starting...
Jun 26 18:09:47 blackmorse sddm[540]: Logind interface found
Jun 26 18:09:47 blackmorse sddm[540]: Adding new display on vt 1 ...
Jun 26 18:09:47 blackmorse sddm[540]: Loading theme configuration from
Jun 26 18:09:47 blackmorse sddm[540]: Display server starting...
Jun 26 18:09:47 blackmorse sddm[540]: Adding cookie to /var/run/sddm/{4497172d-80a5-4357-82e8-8117fddecfc2}
Jun 26 18:09:47 blackmorse sddm[540]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{4497172d-80a5-4357-82e8-8117fddecfc2} -background none -noreset -displayfd 17 -seat seat0 vt1
Jun 26 18:09:47 blackmorse sddm[540]: Setting default cursor
Jun 26 18:09:47 blackmorse sddm[540]: Running display setup script /usr/share/sddm/scripts/Xsetup
Jun 26 18:09:47 blackmorse sddm[540]: Display server started.
Jun 26 18:09:47 blackmorse sddm[540]: Socket server starting...
Jun 26 18:09:47 blackmorse sddm[540]: Socket server started.
Jun 26 18:09:47 blackmorse sddm[540]: Loading theme configuration from
Jun 26 18:09:47 blackmorse sddm[540]: Greeter starting...
Jun 26 18:09:47 blackmorse sddm-helper[557]: [PAM] Starting...
Jun 26 18:09:47 blackmorse sddm-helper[557]: [PAM] Authenticating...
Jun 26 18:09:47 blackmorse sddm-helper[557]: [PAM] returning.
Jun 26 18:09:47 blackmorse sddm-helper[557]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=219) by (uid=0)
Jun 26 18:09:48 blackmorse sddm[540]: Greeter session started successfully
Jun 26 18:09:48 blackmorse sddm[540]: Message received from greeter: Connect
|
|
|
| Back to top |
|
 |
davidbryant
Tux's lil' helper
Joined: 11 Jun 2020
Posts: 137
Location: Canyon Lake, Texas
|
| Posted: Sun Jun 26, 2022 4:50 pm Post subject: Have you tried using Nouveau driver? |
|
|
I'm no expert, but it sounds like a problem with the video driver. I can see that you're using systemd. I'm using openRC. So our sddm logs look different. But the underlying process should be the same. Here's what my sddm log looks like when KDE starts up successfully, commencing at the point where your system hangs.
| Code: | [11:21:42.337] (II) DAEMON: Greeter starting...
[11:21:42.508] (II) HELPER: [PAM] Starting...
[11:21:42.508] (II) HELPER: [PAM] Authenticating...
[11:21:42.508] (II) HELPER: [PAM] returning.
[11:21:42.634] (II) DAEMON: Greeter session started successfully
[11:21:43.988] (II) DAEMON: Message received from greeter: Connect
[11:22:03.093] (II) DAEMON: Message received from greeter: Login
[11:22:03.093] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[11:22:03.095] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[11:22:03.095] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11"
[11:22:03.298] (II) HELPER: [PAM] Starting...
[11:22:03.298] (II) HELPER: [PAM] Authenticating...
[11:22:03.310] (II) HELPER: [PAM] Preparing to converse...
[11:22:03.310] (II) HELPER: [PAM] Conversation with 1 messages
[11:22:03.334] (II) HELPER: [PAM] returning.
[11:22:03.375] (II) DAEMON: Authenticated successfully
[11:22:03.791] (II) HELPER: [PAM] Closing session
[11:22:03.792] (II) HELPER: [PAM] Ended.
[11:22:03.792] (II) DAEMON: Auth: sddm-helper exited successfully
[11:22:03.792] (II) DAEMON: Greeter stopped.
[11:22:04.034] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
[11:22:04.092] (II) HELPER: Adding cookie to "/home/david/.Xauthority"
[11:22:04.196] (II) DAEMON: Session started
|
Anyway, it looks as if the greeter is dying because it can't display the login screen. The next thing that ought to happen is you enter a password, etc. That's the "login" line above.
You say you're trying to install KDE in Gentoo. Is thiis the first graphical interface you have installed on the system? I suppose it must be, but I just want to verify.
My only suggestion is to drop the proprietary driver, and use the nouveau (open source) driver instead. I have an Nvidia GPU (GE Force RTX 2060), and the nouveau driver works just fine for me.
_________________
David Bryant
Canyon Lake, Texas |
|
| Back to top |
|
|
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
| Posted: Mon Jun 27, 2022 12:21 pm Post subject: |
|
|
davidbryant, Thanks for the response.
You're right, I'm using systemd, and It is a first graphical interface that I've tried to install.
I've dropped proprietary drivers and have installed nouveau instead, and It didn't help. Anyway I think It is not appropriate solution for me, because I should use proprietary nvidia drivers for gaming (at my previous laptop nouveau didn't work with couple of games).
In case no one have any other ideas I will try to install system from scratch with nouveau drivers, may be this will help |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54234
Location: 56N 3W
|
| Posted: Mon Jun 27, 2022 1:28 pm Post subject: |
|
|
Blackmorse,
You are trying to eat a whole elephant at one meal.
It's best done one plateful at a time.
Installing Gentoo is the same. Build on what you know works.
Move your ~/.xinitrc out of the way.
| Code: | | emerge -1av twm xclock xterm |
That will install a number of small packages without recording anything in the world file.
startx should now start three xterms and an analogue clock all wrapped up in twm.
You need to know that twm only uses the primary mouse button.
If that works, Xorg is probably in good shape but use wgetpaste to share dmesg and Xorg.0.log
Once that's all OK, we have made the problem space smaller and can move on to our next plateful of Gentoo :)
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
| Posted: Tue Jun 28, 2022 5:23 pm Post subject: |
|
|
NeddySeagoon,
First of all, thanks a lot for this kind of help,
I got rid of all of the kde stuff, installed twm, xlock and xterm with one-shot
startx showed three terminals and clock, as you said.
dmesg log:
https://dpaste.com/7XL4VBWXN |
|
| Back to top |
|
|
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
| Posted: Thu Jun 30, 2022 4:49 pm Post subject: |
|
|
| NeddySeagoon wrote: | Blackmorse,
You are trying to eat a whole elephant at one meal.
It's best done one plateful at a time.
Installing Gentoo is the same. Build on what you know works.
Move your ~/.xinitrc out of the way.
| Code: | | emerge -1av twm xclock xterm |
That will install a number of small packages without recording anything in the world file.
startx should now start three xterms and an analogue clock all wrapped up in twm.
You need to know that twm only uses the primary mouse button.
If that works, Xorg is probably in good shape but use wgetpaste to share dmesg and Xorg.0.log
Once that's all OK, we have made the problem space smaller and can move on to our next plateful of Gentoo  |
Hi, NeddySeagoon,
After removing /etc/X11/xorg.conf file with configuration copied from https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers#The_X_server or https://wiki.gentoo.org/wiki/NVIDIA/Optimus/xorg.conf KDE finally started to work.
But when I'm putting back nvidia config to xorg.conf screen freezes again, and I can see the next errors at dmesg:
| Code: |
[ 3.071609] nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
[ 3.230438] nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
[ 3.645984] nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54234
Location: 56N 3W
|
| Posted: Thu Jun 30, 2022 6:08 pm Post subject: |
|
|
Blackmorse,
Your last working Xorg.0.log (before going to nvidia-drivers) and the Xorg.0.log with nvidia-drivers would be good to see.
| Code: | | [ 3.071609] nvidia-modeset: WARNING: GPU:0: ... |
is a warning about something that was managed automatically.
Its not an error.
It quite possible that it can be safely ignored. Your Xorg.0.log will tell more.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
| Posted: Thu Jun 30, 2022 6:50 pm Post subject: |
|
|
| NeddySeagoon wrote: | Blackmorse,
Your last working Xorg.0.log (before going to nvidia-drivers) and the Xorg.0.log with nvidia-drivers would be good to see.
| Code: | | [ 3.071609] nvidia-modeset: WARNING: GPU:0: ... |
is a warning about something that was managed automatically.
Its not an error.
It quite possible that it can be safely ignored. Your Xorg.0.log will tell more. |
Xorg.0.log with KDE working (without nvidia ): https://dpaste.org/PJiKq
Xorg.0.log with nvidia: https://dpaste.com/HQQWLPZ26 |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54234
Location: 56N 3W
|
| Posted: Thu Jun 30, 2022 8:01 pm Post subject: |
|
|
Blackmorse,
| Code: | [ 3.152] (II) NVIDIA(0): Validated MetaModes:
[ 3.152] (II) NVIDIA(0): "NULL"
[ 3.152] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[ 3.152] (WW) NVIDIA(0): Unable to get display device for DPI computation. |
Tells that there an no displays connected to the nVidia card. That may be OK.
| Code: | [ 2.414] (--) PCI: (1@0:0:0) 10de:1f9d ...
[ 2.414] (--) PCI:*(5@0:0:0) 1002:164c ... |
and you have two GPUs
The first one is a | Code: | | TU117M [GeForce GTX 1650 Mobile / Max-Q], |
the second a | Code: | | RS880M [Mobility Radeon HD 4225/4250] |
Even with nVidia-drivers not in use, its still loaded but the modeset driver is doing all the work.
| Code: | [ 2.449] (II) modeset(0): Output None-1 has no monitor section
[ 2.449] (II) modeset(0): EDID for output None-1
[ 2.449] (II) modeset(0): Printing probed modes for output None-1
[ 2.449] (II) modeset(0): Modeline "1920x1080"x60.0 124.42 1920 1920 1920 1920 1080 1080 1080 1080 (64.8 kHz eP)
[ 2.449] (II) modeset(0): Output None-1 connected |
it finds the display and
| Code: | [ 3.178] (II) NVIDIA(G0): Validated MetaModes:
[ 3.178] (II) NVIDIA(G0): "NULL"
[ 3.178] (II) NVIDIA(G0): Virtual screen size determined to be 640 x 480 |
the nVidia card does not.
I have not seen an AMD/nVidia combination before. Intel/nVidia is common in Optimus but that's always Intel/nVidia.
I'm aware of a few upmarket laptops, where the nVidia card can only drive external displays too but they are fairly rare.
It may be possible to use nVidia GPU as a helper for the AMD GPU, in the manner of Optimus.
There are too many unknowns at the moment.
With two mobile GPUs this has to be a laptop. What is the make and model number, so I can read the manual?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
| Posted: Fri Jul 01, 2022 2:32 pm Post subject: |
|
|
| NeddySeagoon wrote: | Blackmorse,
| Code: | [ 3.152] (II) NVIDIA(0): Validated MetaModes:
[ 3.152] (II) NVIDIA(0): "NULL"
[ 3.152] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[ 3.152] (WW) NVIDIA(0): Unable to get display device for DPI computation. |
Tells that there an no displays connected to the nVidia card. That may be OK.
| Code: | [ 2.414] (--) PCI: (1@0:0:0) 10de:1f9d ...
[ 2.414] (--) PCI:*(5@0:0:0) 1002:164c ... |
and you have two GPUs
The first one is a | Code: | | TU117M [GeForce GTX 1650 Mobile / Max-Q], |
the second a | Code: | | RS880M [Mobility Radeon HD 4225/4250] |
Even with nVidia-drivers not in use, its still loaded but the modeset driver is doing all the work.
| Code: | [ 2.449] (II) modeset(0): Output None-1 has no monitor section
[ 2.449] (II) modeset(0): EDID for output None-1
[ 2.449] (II) modeset(0): Printing probed modes for output None-1
[ 2.449] (II) modeset(0): Modeline "1920x1080"x60.0 124.42 1920 1920 1920 1920 1080 1080 1080 1080 (64.8 kHz eP)
[ 2.449] (II) modeset(0): Output None-1 connected |
it finds the display and
| Code: | [ 3.178] (II) NVIDIA(G0): Validated MetaModes:
[ 3.178] (II) NVIDIA(G0): "NULL"
[ 3.178] (II) NVIDIA(G0): Virtual screen size determined to be 640 x 480 |
the nVidia card does not.
I have not seen an AMD/nVidia combination before. Intel/nVidia is common in Optimus but that's always Intel/nVidia.
I'm aware of a few upmarket laptops, where the nVidia card can only drive external displays too but they are fairly rare.
It may be possible to use nVidia GPU as a helper for the AMD GPU, in the manner of Optimus.
There are too many unknowns at the moment.
With two mobile GPUs this has to be a laptop. What is the make and model number, so I can read the manual? |
I thought it is possible use Nvidia card only without swithching to AMD..
Laptop is Acer Aspire 7 n19c5 |
|
| Back to top |
|
|
Blackmorse
n00b
Joined: 28 Mar 2021
Posts: 52
|
| Posted: Thu Jul 07, 2022 6:53 pm Post subject: |
|
|
No help on this? 
Tried to install nouveau drivers instead of nvidia ones. nouveau module can not be loaded:
https://dpaste.org/QTUUZ |
|
| Back to top |
|
|
avgen2
n00b
Joined: 27 Jun 2022
Posts: 37
|
| Posted: Tue Jul 19, 2022 11:46 am Post subject: |
|
|
| NeddySeagoon wrote: | Blackmorse,
You are trying to eat a whole elephant at one meal.
It's best done one plateful at a time.
Installing Gentoo is the same. Build on what you know works.
Move your ~/.xinitrc out of the way.
| Code: | | emerge -1av twm xclock xterm |
That will install a number of small packages without recording anything in the world file.
startx should now start three xterms and an analogue clock all wrapped up in twm.
You need to know that twm only uses the primary mouse button.
If that works, Xorg is probably in good shape but use wgetpaste to share dmesg and Xorg.0.log
Once that's all OK, we have made the problem space smaller and can move on to our next plateful of Gentoo |
İs this mean comment or delete all .xinitrc or we can use exec twm in .xinitrc? Are we need to delete wm manager, xorg or anything?
_________________
English is not my native language; please excuse typing errors. You are free to correct me if you want. |
|
| Back to top |
|
|
|
Desktop Environments
