wespiard

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Cannot create a new display #45344
    wespiard
    Participant

    Apparently I couldn’t upload the .log file, so I renamed it as .txt and am attaching it here for Xorg.1.log.

    Also, I have an update for my issue.

    I am able to get a desktop connected with NoMachine if I use a barebones local user account. If I use my Active Directory login with sssd, it doesn’t work. So it could be something related to my AD user configuration, or something with sssd specifically.

    Attachments:
    in reply to: Cannot create a new display #45307
    wespiard
    Participant

    I don’t have an Nvidia GPU installed, just the basic Matrox integrated graphics.

    I have no output for sudo journalctl -x |grep -i gdm.

    There exists no /var/log/Xorg.0.log, but I do have $HOME/.local/share/xorg/Xorg.1.log, which has some warnings/errors. I have attached it below.

     

    The warnings/errors are here for a quick reference:

    [1057801.835] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    
    [1057801.835] (II) Module vesa: vendor="X.Org Foundation"
    
    [1057801.835]   compiled for 1.20.2, module version = 2.4.0
    
    [1057801.835]   Module class: X.Org Video Driver
    
    [1057801.835]   ABI class: X.Org Video Driver, version 24.0
    
    [1057801.835] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    
    [1057801.835] (II) FBDEV: driver for framebuffer: fbdev
    
    [1057801.835] (II) VESA: driver for VESA chipsets: vesa
    
    <strong>[1057801.835] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)</strong>
    
    [1057801.835] (II) modeset(0): using drv /dev/dri/card0
    
    <strong>[1057801.835] (WW) Falling back to old probe method for fbdev</strong>
    
    [1057801.835] (II) Loading sub module "fbdevhw"
    
    [1057801.835] (II) LoadModule: "fbdevhw"
    
    [1057801.835] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    
    [1057801.835] (II) Module fbdevhw: vendor="X.Org Foundation"
    
    [1057801.835]   compiled for 1.20.11, module version = 0.0.2
    
    [1057801.835]   ABI class: X.Org Video Driver, version 24.1
    
    <strong>[1057801.835] (EE) open /dev/fb0: Permission denied</strong>

    [1057801.835] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support`

     

    inxi -aG yields the following:
    Graphics:

    Device-1: Matrox Systems G200eR2 vendor: Dell driver: mgag200 v: kernel ports: active: VGA-1

    empty: none bus-ID: 0b:00.0 chip-ID: 102b:0534 class-ID: 0300

    Display: server: X.org v: 1.20.11 with: Xwayland v: 21.1.3 driver: gpu: mgag200 tty: 166×32

    Monitor-1: VGA-1 size-res: N/A in console modes: max: 1024×768 min: 640×480

    API: OpenGL Message: GL data unavailable in console for root.

    Output of inxi --admin --verbosity=7 --filter --no-host --width is also attached.

    Attachments:
    in reply to: Cannot create a new display #45271
    wespiard
    Participant

    @Britgirl, any updates or ideas?

    in reply to: Cannot create a new display #45228
    wespiard
    Participant

    I have [removed]server installed as well, that’s probably where the nx-libs and nxagent packages are from. I uninstalled it now for testing and am getting the same error with NoMachine.

    There is no .xsession-errors file or similar in my user folder.

    The following is all that I see in /var/log/messages after attempting to connect with NoMachine:

    Aug 23 15:55:33 systemd[1]: Started Session 139 of user wespiard.
    Aug 23 15:55:33 systemd[1]: session-139.scope: Succeeded.
    Aug 23 15:55:34 systemd-logind[1241]: New session 140 of user wespiard.
    Aug 23 15:55:34 systemd[1]: Started Session 140 of user wespiard.
    Aug 23 15:55:35 systemd-logind[1241]: Session 140 logged out. Waiting for processes to exit.
    Aug 23 15:55:38 systemd[1]: session-140.scope: Succeeded.
    Aug 23 15:55:38 systemd-logind[1241]: Removed session 140.

    in reply to: Cannot create a new display #45217
    wespiard
    Participant

    I collected them the other day — I’ll attach them now.

    Again, I’m running RHEL 8.8 and NoMachine 8.8.1-1. If it matters, nx-libs and nxagent are version 3.5.99.26-1.

    in reply to: Cannot create a new display #45194
    wespiard
    Participant

    I am actually in the same situation. Running RHEL 8.8 and NoMachine 8.8.1-1.

    I started getting this error recently as well. My guess is from some package(s) that updated in RHEL, as my issues started happening after I ran a dnf update.

Viewing 6 posts - 1 through 6 (of 6 total)