[SOLVED] New install, X isn't working

PsychoHermit · 05-26-2022, 03:00 PM

Greetings folks,

New install, gentoo newbie. X isn't working and searching for the solution isn't working out.

Code:

dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)

parse_vt_settings: Cannot open /dev/tty0 (Permission denied)

Any assistance would be greatly appreciated.

Thanks,
--glenn

mrmazda · 05-27-2022, 01:08 AM

When you need help with X trouble, it's important to provide some data points about your GPU and display(s), and X's log. Pastebin /var/log/Xorg.0.log, and paste here output from inxi -GSa using code tags.

hazel · 05-27-2022, 09:59 AM

Does your X run suid in the traditional way or not? If not, you will need elogind as well. See https://wiki.gentoo.org/wiki/Xorg/Guide, https://wiki.gentoo.org/wiki/Non_root_Xorg

PsychoHermit · 05-27-2022, 02:10 PM

Code:

System:
  Host: GentooBox Kernel: 5.15.41-gentoo-dist x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/vmlinuz-5.15.41-gentoo-dist root=/dev/sda9
  Console: tty 1 Distro: Gentoo Base System release 2.7
Graphics:
  Device-1: AMD Richland [Radeon HD 8650G] vendor: Hewlett-Packard driver: radeon v: kernel
    bus-ID: 00:01.0 chip-ID: 1002:990b class-ID: 0300
  Device-2: Cheng Uei Precision Industry (Foxlink) HP Truevision HD type: USB driver: uvcvideo
    bus-ID: 1-2:3 chip-ID: 05c8:036d class-ID: 0e02
  Display: server: X.org 1.21.1.3 driver: loaded: ati,fbdev,modesetting,radeon,vesa tty: 170x48
  Message: Advanced graphics data unavailable in console for root.

Xorg.0.log https://pastebin.com/CQVjd3mu

Thanks,
--glenn

mrmazda · 05-27-2022, 02:39 PM

Quote:

Originally Posted by PsychoHermit

Code:

  Display: server: X.org 1.21.1.3 driver: loaded: ati,fbdev,modesetting,radeon,vesa tty: 170x48

This is ambiguous output from a broken old inxi version. inxi has -U switch to upgrade itself. Please use it to upgrade to current upstream version, then post inxi -Ga output here again.

The log suggests you should try simply starting X as root user, just to see if it's an authorization issue that needs correction. If it starts, exit. We're only looking for proof X can run.

Most users use a display manager that provides a GUI login greeter, as its safer and preferred. Installing and using a DM should solve this. Examples include GDM, LightDM, SDDM & XDM.

PsychoHermit · 05-27-2022, 03:46 PM

Code:

Graphics:
  Device-1: AMD Richland [Radeon HD 8650G] vendor: Hewlett-Packard driver: radeon v: kernel
    ports: active: eDP-1 empty: DVI-D-1,HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:990b class-ID: 0300
  Device-2: Cheng Uei Precision Industry (Foxlink) HP Truevision HD type: USB driver: uvcvideo
    bus-ID: 1-2:3 chip-ID: 05c8:036d class-ID: 0e02
  Display: server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1 driver: X:
    loaded: fbdev,modesetting,radeon,vesa gpu: radeon tty: 170x48
  Monitor-1: eDP-1 model: AU Optronics 0x46ec built: 2011 res: 1366x768 dpi: 101 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: max: 1366x768 min: 640x480
  Message: GL data unavailable in console for root.

X will not start for root

Thanks,
--glenn

PsychoHermit · 05-27-2022, 04:01 PM

I'm not completely convinced I have a valid install of X. How to install x11 when it is masked by ~amd64?

Thanks,
--glenn

mrmazda · 05-27-2022, 08:04 PM

Inxi output suggests X is fully working, but failure to run again suggests authorization to use it is not. An Xorg.0.log from that root attempt further enlighten. I don't know how to fix this, other than possibly as I already wrote, to install a DM and start X from it instead of from a shell prompt. I don't have a current Gentoo installation with AMD video, but Xorg 21.1.3 and older are all working OK here with my HD 8570.

h2-1 · 05-27-2022, 08:45 PM

There's clearly something wrong with the xorg install, it loaded 4 different drivers, and failed to unload any of them after the initial load sequence, which is what it's supposed to do, so it's not surprising that xorg crashed.

I would politely suggest that you try a different distro that is more readily debugged, gentoo isn't really for newbies in general, I've actually never seen an xorg exhibit this behavior and I wouldn't even begin to try to guess what the cause is, beyond noting it's not normal behavior, but I wouldn't try to guess at what it is since it can be so many various things.

Modern xorg if left basically to itself 'just works', as long as it has the right xorg drivers installed. Nouveau might give issues on latest nvidia cards, and amdgpu on latest amd cards, but otherwise, it tends to just work, assuming the package is reasonably well built.

The log file indicates clearly the cause of the crash, but I personally would not even try to guess at what was done wrong to generate that cause. Xorg doesn't like being started as root, for one thing, if I remember right, that behavior has changed significantly, so that is a warning already, but like I said, I'm not personally going to try to guess at this, I'd put it in the you break it, you fix it camp, lol, which is how you learn.