Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
sddm won't start. Console window flickers badly
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1108
Location: Stuart, Florida

PostPosted: Wed Jun 13, 2018 8:46 pm    Post subject: sddm won't start. Console window flickers badly Reply with quote

I am having a problem logging into my amd64 system.

The sequence of my problem follows:
1. After being gone for 2 weeks. I logged in and updated my system. There was a message that I needed to add a line to package.keywords so that gentoo-sources-4.17.0 would build. I did that and rebuilt my system, updating nvidia-drivers as usual. I believe it updated to 396.24-r1. Later when I tried to rebuild nvidia-drivers, I thought I saw a message about incompatibility with my nvidia card.

2. When I rebooted, I got dumped into the console prompt, which is flickering so badly that it is extremely difficult to log in.

3. I have experimented with reverting to my previous system, gentoo-sources-4.14.17, and back to nvidia-drivers=390.59. I still have the problem. I have concluded that something else is the problem.

At the moment I am running linux Mint, but can chroot into my unusable gentoo system.
Back to top
View user's profile Send private message
steve_v
Guru
Guru


Joined: 20 Jun 2004
Posts: 388
Location: New Zealand

PostPosted: Thu Jun 14, 2018 8:47 am    Post subject: Reply with quote

The flickering is probably xorg restarting repeatedly. If this is the case, and you run openrc with a display manager, pass 'nox' on the kernel command line to get a usable text console.

Then pull the xorg log file, the answer is almost certainly in there.

When logs are absent, all that remains is speculation.
Back to top
View user's profile Send private message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1108
Location: Stuart, Florida

PostPosted: Thu Jun 14, 2018 4:36 pm    Post subject: Reply with quote

Thank you for the insight. I looked at Xorg.0.log.old (Xorg.0.log was empty.)
It shows that the system is trying to load nouveau rather than nvidia.
I checked make.conf. It specifies only nvidia as it always has.

/etc/conf.d/modules specifies nvidia. See below.

Some startup files have clearly changed and I didn't get the memo.ls


From Xorg.0.log.old:
Code:

  60.814] (II) LoadModule: "glx"
[    60.814] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    60.815] (II) Module glx: vendor="X.Org Foundation"
[    60.815]    compiled for 1.19.5, module version = 1.0.0
[    60.815]    ABI class: X.Org Server Extension, version 10.0
[    60.815] (==) Matched nouveau as autoconfigured driver 0
[    60.815] (==) Matched nv as autoconfigured driver 1
[    60.815] (==) Matched modesetting as autoconfigured driver 2
[    60.815] (==) Matched fbdev as autoconfigured driver 3
[    60.815] (==) Matched vesa as autoconfigured driver 4
[    60.815] (==) Assigned the driver to the xf86ConfigLayout
[    60.815] (II) LoadModule: "nouveau"
[    60.815] (WW) Warning, couldn't open module nouveau
[    60.815] (II) UnloadModule: "nouveau"
[    60.815] (II) Unloading nouveau
[    60.815] (EE) Failed to load module "nouveau" (module does not exist, 0)
[    60.815] (II) LoadModule: "nv"
[    60.815] (WW) Warning, couldn't open module nv
[    60.815] (II) UnloadModule: "nv"
[    60.815] (II) Unloading nv
[    60.815] (EE) Failed to load module "nv" (module does not exist, 0)
[    60.815] (II) LoadModule: "modesetting"
[    60.815] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[    60.815] (II) Module modesetting: vendor="X.Org Foundation"
[    60.815]    compiled for 1.19.5, module version = 1.19.5
[    60.815]    Module class: X.Org Video Driver
[    60.815]    ABI class: X.Org Video Driver, version 23.0
[    60.815] (II) LoadModule: "fbdev"
[    60.816] (WW) Warning, couldn't open module fbdev
[    60.816] (II) UnloadModule: "fbdev"
[    60.816] (II) Unloading fbdev
[    60.816] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    60.816] (II) LoadModule: "vesa"
[    60.816] (WW) Warning, couldn't open module vesa
[    60.816] (II) UnloadModule: "vesa"
[    60.816] (II) Unloading vesa
[    60.816] (EE) Failed to load module "vesa" (module does not exist, 0)
[    60.816] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    60.816] (++) using VT number 7

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


Make.conf still has nvidia specified:
Code:

VIDEO_CARDS="nvidia"


Here is my /etc/conf.d/modules file:
Code:
bopper /etc/conf.d # cat modules
# You can define a list modules for a specific kernel version,
# a released kernel version, a main kernel version or just a list.
# The most specific versioned variable will take precedence.
#modules_2_6_23_gentoo_r5="ieee1394 ohci1394"
#modules_2_6_23="tun ieee1394"
#modules_2_6="tun"
#modules_2="ipv6"
#modules="ohci1394"

# You can give modules a different name when they load - the new name
# will also be used to pick arguments below.
#modules="dummy:dummy1"

# Give the modules some arguments if needed, per version if necessary.
# Again, the most specific versioned variable will take precedence.
#module_ieee1394_args="debug"
#module_ieee1394_args_2_6_23_gentoo_r5="debug2"
#module_ieee1394_args_2_6_23="debug3"
#module_ieee1394_args_2_6="debug4"
#module_ieee1394_args_2="debug5"

# You should consult your kernel documentation and configuration
# for a list of modules and their options.

### START: Auto-converted from kernel-2.6

#jc
modules="nvidia snd_hda_intel xc5000"
### END: Auto-converted from kernel-2.6

Back to top
View user's profile Send private message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1108
Location: Stuart, Florida

PostPosted: Thu Jun 14, 2018 5:24 pm    Post subject: Reply with quote

Once I got X out of the way, I tried to re-emerge nvidia-drivers and noticed what seemed to be an error message at the beginning. It basically informed me that the cujrrent versions of nvidia-drivers I was using were incompatible with my old but expensive graphics card. Once I had the correct version of nvidia running things are better.

KDE isn't running right, but that might be a different problem.
Back to top
View user's profile Send private message
Nreal
Apprentice
Apprentice


Joined: 06 Jan 2009
Posts: 265

PostPosted: Fri Jun 15, 2018 5:14 am    Post subject: sddm is a bad joke Reply with quote

Its very difficult to understand why kdm was replaced with sddm - a small step backwards - no multiseat until version 1.0 or smthng.. Very bad joke.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming 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