[unsolved-redone] Black screen with cursor or console frozen

[flyerone]

Hi all,

my installation had 42 of 50GB in / when I've done the unmentionable and did the re-install.

I'll need to use the Nvidia driver and can't get on the desktop. I've tried the usual tricks with the removal of .xinitrc and twm, xterm and xclock and the machine hangs no matter what i've tried. Each time I'll try to startx I'm not able to open VTs and have to magic-key the machine to the reboot.

From what I can glean from the logs the Nvidia drivers seem to be loaded and happy, I can't start the desktop at all.

My .xinitrc:

[Jaglover]

[flyerone]

Thanks, I've set up for openrc and have no intention of using systemd which is my sole reason for using Gentoo.

Can you put the first bit in English please, the suid bit isn't on for xorg-server. I've tried to re-emerge this in case something wasn't built correctly in turn.

I was aware I've built windowmaker and xorg without the desktop profile which has worked before, switched the profile, updated and then built xfce4 with elogind.

[Jaglover]

I think you have to double-check everything is right for -suid setup. The Xorg log was with systemd-login, if you still need help show us the new log with elogind.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

[flyerone]

rc-update says elogind is in the boot level and is started at each boot.

The elogind emerge asked me to move it from default to boot. Is it usual to have it both in boot and default? I'll stick with boot.

I've grepped the X binary for systemd and there are several even though +elogind -suid -systemd, if you're on a systemd barred machine could you have a look?

The util-linux is built with USE="suid" and I think I should leave it. What's going on if I've left -suid in make.conf?

I'm at 262 of 533 of an emerge -qe @world, it might be a while as I'll grab some vitamin D outside.

[flyerone]

Had a successful vitamind-logout:ok

The machine on the other hand has had an all day rebuild.

Here's the new crash: http://dpaste.com/ACV4CDHFP

[flyerone]

There's good news, I've been running Gentoo and X-Plane for three days now.

It still puzzles me because at the first attempt I had a console installer and followed the "current-stage3-amd64" link to copy the stage tarball with links, I've assumed it runs openrc ok and the tarball without openrc in the name sounds like "stage3-amd64-YMDT.tar.xz".. I'm a kinda console guy and I have the Gentoo usb with the driver that handles the nvme nowdays.

After four weeks I decided to restage using Ubuntu and then I've followed the other link.

ftp://mirrors.dotsrc.org/gentoo/releases/amd64/autobuilds/current-stage3-amd64/stage3-amd64-20210630T214504Z.tar.xz

See what happened here? At the other attempt I did miss the other openrc tarball further down between the -musl and that -systemd version.

A user here gave me a heads up about the systemd messages that gave me the headache, well the new log is brimming with them when I'm running startx:

http://dpaste.com/5LR2Z5MN9

When I'm started at display-manager the messages arent that bad.

http://dpaste.com/HK9P32E62

The Logitech warnings are nothing to worry about. The keyboard is old and I'll keep it, it's working. My installation is ok with openrc and why does it shout at me about systemd while running startx?

I was without running X-Plane for four weeks, when also Ubuntu had decided to not accelerate graphics anymore. Well, I was also getting vitamin D's while hiking anyway.

When I grabbed the tarball without -openrc (in the name at least) what's the purpose of that tarball vs the one with -openrc? I can't remember how I was thinking (did I..) and would like to know the subtle difference.

ftp://mirrors.dotsrc.org/gentoo/releases/amd64/autobuilds/current-stage3-amd64/stage3-amd64-20210630T214504Z.tar.xz

Can I install the desktop with this? BTW I'm up and running again with XFCE4 just as I've left it and I'll need to learn a lesson from this.