View previous topic :: View next topic |
Author |
Message |
Progman3K l33t
Joined: 03 Jan 2004 Posts: 773
|
Posted: Mon Apr 22, 2019 1:37 pm Post subject: X (gdm) black screen, nouveau [SOLVED] |
|
|
Hi,
I can't get X to start on a new install.
uname -a
Linux svt 4.19.23-gentoo #4 SMP Tue Mar 5 08:46:00 EST 2019 x86_64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz GenuineIntel GNU/Linux
Running
Xorg :0 -configure
gives this output:
https://pastebin.com/FSvwsDXd
dmesg output:
https://pastebin.com/DWZxz8HL
However, if I run
X -config /root/xorg.conf.new -retro
I get a screen with the old-style XWindows grey (black/white moiré) background and the old-style X mouse-pointer. I can move the mouse pointer OK.
X applications CAN be run remotely over ssh.
X just won't start locally.
EDIT
The machine is a DELL desktop. Here is the output of lspci -v
https://pastebin.com/QjbjRBVy
Any help welcome, thank you
Last edited by Progman3K on Tue May 14, 2019 11:58 am; edited 2 times in total |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
Posted: Mon Apr 22, 2019 1:52 pm Post subject: |
|
|
Quote: | Running
Xorg :0 -configure |
Uh, this is how they did it in 19th century.
FYI, it does not even work with KMS - and KMS is mandatory with open source drivers.
Anyhow, you managed to leave out the hardware information. What is it, a desktop? Perhaps a laptop with hybrid graphics? _________________ My Gentoo installation notes.
Please learn how to denote units correctly!
Last edited by Jaglover on Mon Apr 22, 2019 2:01 pm; edited 1 time in total |
|
Back to top |
|
|
Progman3K l33t
Joined: 03 Jan 2004 Posts: 773
|
Posted: Mon Apr 22, 2019 2:00 pm Post subject: |
|
|
You mean the 20th century, we're in the 21st century now
All the same, you're right, but I'm not sure how to get X running properly, so I tried the old method.
I've edited the parent with more information in case someone else reads the thread, so they won't have to piece too much of it together. |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
Posted: Mon Apr 22, 2019 2:06 pm Post subject: |
|
|
I meant 19th century, to emphasize how outdated this approach is.
Anyhow, make sure your kernel is configured properly (Gentoo Wiki), log in as user and start X. Make sure there is something set up to run on X, otherwise it will find there is nothing to do and terminate. Do not generate any conf files, these are needed only for fine tuning and you can do it later if needed. Also, make sure you have libinput enabled. It will handle both keyboard and mouse. _________________ My Gentoo installation notes.
Please learn how to denote units correctly! |
|
Back to top |
|
|
Progman3K l33t
Joined: 03 Jan 2004 Posts: 773
|
Posted: Mon Apr 22, 2019 3:45 pm Post subject: |
|
|
Hi Jaglover,
Oddly enough, even if gdm won't start X, running the startx command results in a graphical screen with three xterms and one xclock running in it with the mouse and keyboard also working...
So it must be close to functional...
I don't get why the greeter won't come up...
EDIT: One thing; the windows that open when I invoke startx, none of them have titlebars... Like if there is no window-manager... |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54266 Location: 56N 3W
|
Posted: Mon Apr 22, 2019 3:55 pm Post subject: |
|
|
Progman3K,
That's Xorg working then.
How do you intend to start gdm?
There are two ways.
Edit your ~/.xinitrc, so startx brings up gdm.
Configure xdm to start gdm and add xdm to the default runlevel.
The former is per user, the latter is system wide. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Progman3K l33t
Joined: 03 Jan 2004 Posts: 773
|
Posted: Mon Apr 22, 2019 5:26 pm Post subject: |
|
|
Hi Neddy!
I've added gdm to the default runlevel with
systemctl enable gdm
but
systemctl status gdm
Quote: | ● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2019-04-22 11:10:36 EDT; 2h 21min ago
Main PID: 2731 (gdm)
CGroup: /system.slice/gdm.service
└─2731 /usr/sbin/gdm
Apr 22 11:10:56 svt gdm-launch-environment][5789]: pam_systemd(gdm-launch-environment:session): Unknown parameter 'kill-session-processes=1', ignoring
Apr 22 11:10:56 svt gdm[2731]: Child process -5792 was already dead.
Apr 22 11:10:56 svt gdm[2731]: Child process 5789 was already dead.
Apr 22 11:10:56 svt gdm[2731]: Unable to kill session worker process
Apr 22 11:10:56 svt gdm-launch-environment][5795]: pam_systemd(gdm-launch-environment:session): Unknown parameter 'kill-session-processes=1', ignoring
Apr 22 11:10:56 svt gdm[2731]: Could not start command '/usr/libexec/gdm-session-worker': Too many open files
Apr 22 11:10:56 svt gdm[2731]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
Apr 22 11:10:56 svt gdm[2731]: Child process -5798 was already dead.
Apr 22 11:10:56 svt gdm[2731]: Child process 5795 was already dead.
Apr 22 11:10:56 svt gdm[2731]: Unable to kill session worker process
|
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54266 Location: 56N 3W
|
Posted: Mon Apr 22, 2019 7:06 pm Post subject: |
|
|
Progman3K,
I'm not a systemd user.
Is there anything in dmesg or in Xorg.0.log after gdm fails to start? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Progman3K l33t
Joined: 03 Jan 2004 Posts: 773
|
Posted: Wed Apr 24, 2019 12:24 pm Post subject: |
|
|
Hi Neddy!
Even under systemd, there is an Xorg.0.log created in /var/log, here are the contents
https://pastebin.com/CtEJi7nT
I'm not seeing any EE codes in there...
Here's the dmesg log
https://pastebin.com/1NrcQ7wY
Longshot, but here are the groups the user belongs to:
tty wheel uucp audio dialout video kvm users locate plugdev svt
As you pointed out, X does start, so it's something to do with GDM, but I can't imagine what
EDIT
There does seem to be problems though, I've copied the last few pages of the systemd log and there are a bunch of errors in there, I just don't know what the root-cause is
https://pastebin.com/2zZ2UxKr
EDIT 2
Since startx does work, and installing twm (along with font-adobe-100dpi and font-adobe-75dpi), I can get along. It's not Gnome, which was the original target, but X with twm isn't half-bad |
|
Back to top |
|
|
Leio Developer
Joined: 27 Feb 2003 Posts: 494 Location: Estonia
|
Posted: Wed May 08, 2019 3:46 pm Post subject: |
|
|
Progman3K wrote: | Even under systemd, there is an Xorg.0.log created in /var/log, here are the contents
https://pastebin.com/CtEJi7nT
I'm not seeing any EE codes in there...
|
It's probably some ancient leftover log from openrc times. Under systemd it doesn't get logged in there, you need to look in the journal.
GDM issue should be logged in there too. _________________ GNOME team lead; GStreamer; MIPS/ARM64 |
|
Back to top |
|
|
Progman3K l33t
Joined: 03 Jan 2004 Posts: 773
|
Posted: Tue May 14, 2019 11:58 am Post subject: Solved I know not how |
|
|
Hello!
I'm marking this post as SOLVED, even though I don't know what the solution was:
I've kept updating the system with
emerge --sync
and
emerge -u world
And after restarting, GDM now starts as it should, I can log in and Gnome starts as expected.
I didn't change anything...
In any case, thanks to all for helping |
|
Back to top |
|
|
|