I looked up how I can use commands to resize the display, but all of them seem to require a window manager or a desktop environment, for example‌, xrandr, but it says No display found. I'm assuming that just means that I didn't install Xorg (but I could be wrong though.) I am using the Arch Linux installation ISO. Since I don't have a desktop environment or a window manager, it seems that I can't resize the display. Is it possible that even without a desktop environment or window manager, I can change the screen resolution, let's say from something like 1280x800 to 1366x720? If yes, how? Does the installation ISO already let me do that?

I'm on a laptop with no additional monitors connected, but when I run xrandr -q, the output lists two connected devices. Xfce's Display settings dialog also shows two monitors, and so does Xorg.0.log. Here's the xrandr -q output:

0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     60.00*+  59.97    59.96    59.93    48.00  
   1680x1050     59.95    59.88  
   1600x1024     60.17  
   (omitting many more resolutions)
DP-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*  
   800x600       60.32    56.25  
   848x480       60.00  
   640x480       59.94  
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

Is this normal? If not, what can I do to remove this imaginary monitor? Restarting the laptop (with no external monitors connected at any point) doesn't change anything. (My guess it that something about this is causing a weird display problem I have - my login screen starts at the wrong resolution, and afterward the resolution gets corrected but the virtual desktop sizes are wrong.) Here are related Xorg.0.log lines - DP-1 (the imaginary monitor) does not have an EDID, but it is listed as connected with initial mode 1024x768, and also seems to somehow cause eDP-1 (the actual laptop monitor) to use initial mode 1024x768 instead of 1920x1080; then it gets classified as a keyboard for some reason:

[    13.093] (II) modeset(0): Output eDP-1 has no monitor section
[    13.921] (II) modeset(0): Output DP-1 has no monitor section
[    13.921] (II) modeset(0): Output DP-2 has no monitor section
[    13.921] (II) modeset(0): Output DP-3 has no monitor section
[    13.923] (II) modeset(0): EDID for output eDP-1
[    13.923] (II) modeset(0): Manufacturer: BOE  Model: 853  Serial#: 0
[    13.923] (II) modeset(0): Year: 2018  Week: 48
[    13.923] (II) modeset(0): EDID Version: 1.4
(skipping a bunch more EDID information for eDP-1)
[    13.924] (II) modeset(0): Printing probed modes for output eDP-1
[    13.924] (II) modeset(0): Modeline "1920x1080"x60.0  141.72  1920 1968 2000 2124  1080 1083 1089 1112 +hsync -vsync (66.7 kHz eP)
[    13.924] (II) modeset(0): Modeline "1920x1080"x119.9  266.50  1920 1944 1960 2000  1080 1081 1084 1111 doublescan +hsync -vsync (133.2 kHz d)
[    13.924] (II) modeset(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync (67.2 kHz d)
(skipping a lot more modelines for eDP-1)
[    14.754] (II) modeset(0): EDID for output DP-1
[    14.754] (II) modeset(0): Printing probed modes for output DP-1
[    14.755] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    14.755] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    14.755] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    14.755] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[    14.755] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    14.755] (II) modeset(0): EDID for output DP-2
[    14.755] (II) modeset(0): EDID for output DP-3
[    14.755] (II) modeset(0): Output eDP-1 connected
[    14.755] (II) modeset(0): Output DP-1 connected
[    14.755] (II) modeset(0): Output DP-2 disconnected
[    14.755] (II) modeset(0): Output DP-3 disconnected
[    14.755] (II) modeset(0): Using fuzzy aspect match for initial modes
[    14.755] (II) modeset(0): Output eDP-1 using initial mode 1024x768 +0+0
[    14.755] (II) modeset(0): Output DP-1 using initial mode 1024x768 +0+0
(skipping a bunch of lines that seem unrelated - let me know if I should paste the whole thing)
[    15.141] (II) config/udev: Adding input device DP-1 (/dev/input/event10)
[    15.142] (**) DP-1: Applying InputClass "libinput keyboard catchall"
[    15.142] (II) Using input driver 'libinput' for 'DP-1'
[    15.142] (**) DP-1: always reports core events
[    15.142] (**) Option "Device" "/dev/input/event10"
[    15.142] (**) Option "_source" "server/udev"
[    15.144] (II) event10 - DP-1: is tagged by udev as: Keyboard Pointingstick
[    15.144] (II) event10 - DP-1: device is a pointer
[    15.144] (II) event10 - DP-1: device is a keyboard
[    15.145] (II) event10 - DP-1: device removed
[    15.161] (II) libinput: DP-1: needs a virtual subdevice
[    15.162] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.0/rc/rc0/input11/event10"
[    15.162] (II) XINPUT: Adding extended input device "DP-1" (type: MOUSE, id 9)
[    15.162] (**) Option "AccelerationScheme" "none"
[    15.162] (**) DP-1: (accel) selected scheme none/0
[    15.162] (**) DP-1: (accel) acceleration factor: 2.000
[    15.162] (**) DP-1: (accel) acceleration threshold: 4
[    15.164] (II) event10 - DP-1: is tagged by udev as: Keyboard Pointingstick
[    15.165] (II) event10 - DP-1: device is a pointer
[    15.165] (II) event10 - DP-1: device is a keyboard

Unfortunately my Xorg.0.log.old is from the same day and has the same issues, but I found an Xorg.1.log.old from last year which doesn't. It lists the same eDP-1, but doesn't list any information for DP-1 or classify it as a keyboard or list it as connected, and the initial display mode was 1920x1080 (which is what it should be):

[   942.577] (II) modeset(0): EDID for output DP-1
    [   942.577] (II) modeset(0): EDID for output DP-2
    [   942.577] (II) modeset(0): EDID for output DP-3
    [   942.577] (II) modeset(0): Output eDP-1 connected
    [   942.577] (II) modeset(0): Output DP-1 disconnected
    [   942.577] (II) modeset(0): Output DP-2 disconnected
    [   942.577] (II) modeset(0): Output DP-3 disconnected
    [   942.577] (II) modeset(0): Using exact sizes for initial modes
    [   942.577] (II) modeset(0): Output eDP-1 using initial mode 1920x1080 +0+0

I'm on a ThinkPad P1 with Xubuntu 20.04 and Xfce 4.14.

I have two screens with different native resolution connected to my Gentoo/systemd machine. since the VTs try to mirror the outputs, they do not use the whole size of the higher resolution screen. I never use virtual terminals on the lower resolution screen, so I'd like to have them use the whole high resolution monitor. If I disable the lower resolution screen with the video kernel command line parameter, I cannot switch it on in X11, since the kernel thinks the output is not connected. Nevertheless, on X11 I want to be able to enable the second monitor whenever I need it. Is there an option on the kernel command line, in systemd, or somewhere I can't think of at them moment, to disable the virtual terminals on one output, to have different virtual terminals on different outputs (kind of multiseat), to force the vts to use the whole size of one connected screen, or to disable an output on virtual terminals in such a way that xrandr can reenable it?

I bought an odroid n2+ and use the os that was already installed I want to convert the display screen rotation and size, how do I do it? In the display settings, all values are fixed. I try to do it like this, but I can't because I can't get hdmi

$ xrandr --output HDMI-1 --rotate left
xrandr: Failed to get size of gamma for output default
warning: output HDMI-1 not found; ignoring

$ xrandr --verbose
Screen 0: minimum 0 x 0, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm

it's the os version

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/ "
SUPPORT_URL="https://help.ubuntu.com/ "
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/ "
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-  ... acy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

My goal is to rotate the screen and adjust it like 1080*1920

I have the *Mirror Displays* enabled on my Linux Mint 15 Cinnamon 64-bit box, which has a GTX 680 graphics card installed with recommended drivers. I selected [the top green one in this screenshot](http://linuxmint.com/pictures/screenshots/olivia/mintdrivers.png) . However, when on the login screen, the display is not mirrored; it's displayed on the primary monitor only. I really would like to have the WebGL clouds (the flyover one) MDM login screen projected on a 108″ screen before login. Is there any way I could do this? --- **Edits for updates:** I notice that the *Mirror Displays* setting is account-specific. Is there a "default" user at the login screen whose settings I could tweak to enable this? I've tried sudo su -l mdm in an attempt to cinnamon-settings the display to mirrored, but sudo su -l mdm has no effect (very strangely): I retain my shell prompt, and a single exit kills the terminal.

I have a USB 3.0 docking station connected with my laptop having LinuxMint 17.3. I can't manage to install DisplayLink driver on it. I could make it work with Ubuntu 15.04, but with LinuxMint it wan't recognize external monitor, even though there is no error message during the install procedure. I tried to follow some proposal on DisplayLink forum , and I tried to modify installation file so SYSTEMINITDAEMON had systemd or upstart values, but none of these worked. Since I already found some posts reported it worked for LinuxMint 17.2, I guess it's possible, but I couldn't find exact instructions if something else should be changed in installation script.

I am using remote desktop on a windows machine to connect to a CentOS 7 machine running a Xrdp server. Recently I had a problem with an application, where the avaialable openGL version (2.1) was not enough and it suggested either updating it, or using VNC. While trying to make a VNC connection to work I made several updates inlcuding a Kernel update. I could not get the turboVNC to work at the same time than Xrdp, and damaged the settings somehow. Now, when I connect to the Xrdp session the Gnome shell window is very small and has a weird aspect ratio, making it unusable (see picture below, the black area is the the size of my screen). Even if logged out of the gnome session, where I am able to select other shell (KDE, for example) I still have the same window size. Since I could not find a similar problem, I am not sure what is causing the problem. How could I return the size of the window to its original shape and size?

I am running Fedora Linux on an ASUS G14. When my laptop goes to sleep, and then wakes up again, and then is unplugged, it will be stuck at 0 brightness. The screen will get very dim, and I will be unable to adjust the brightness. When I run: brightnessctl set 50%, the output is:

Updated device 'amdgpu_bl1':
Device 'amdgpu_bl1' of class 'backlight':
	Current brightness: 128 (50%)
	Max brightness: 255

but the actual brightness is still 0 When I view: /sys/class/backlight/amdgpu_bl1/actual_brightness the value is 0. And then when I view: /sys/class/backlight/amdgpu_bl1/brightness the value is what it _should_ be. I can't modify any of the files in /sys/class/backlight/amdgpu_bl1/ as they are all read only. Finally, when I change the power mode nothing changes. When I plug my laptop back in, the brightness goes back up and is able to be adjusted as normal. Here is my laptop and OS information:

OS: Fedora Linux 41 (Workstation Edition) x86_64
Host: ROG Zephyrus G14 GA401QM_GA401QM (1.0)
Kernel: Linux 6.12.6-200.fc41.x86_64
Uptime: 7 hours, 28 mins
Packages: 2177 (rpm), 10 (flatpak)
Shell: bash 5.2.32
Display (NCP005E): 1920x1080 @ 144 Hz (as 1536x864) in 14" [Built-in]
DE: GNOME 47.2
WM: Mutter (Wayland)
WM Theme: Adwaita
Theme: Adwaita [GTK2/3/4]
Icons: Adwaita [GTK2/3/4]
Font: Cantarell (11pt) [GTK2/3/4]
Cursor: Adwaita (24px)
Terminal: Ptyxis 47.6
Terminal Font: Source Code Pro (10pt)
 CPU: AMD Ryzen 9 5900HS (16) @ 4.68 GHz
GPU 1: NVIDIA GeForce RTX 3060 Mobile / Max-Q [Discrete]
GPU 2: AMD Radeon Vega Series / Radeon Vega Mobile Series [Integrated]
Memory: 10.32 GiB / 15.02 GiB (69%)
Swap: 1.27 GiB / 8.00 GiB (16%)
Disk (/): 18.96 GiB / 373.02 GiB (5%) - btrfs

I am also using proprietary nvidia drivers if that is relevant

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 565.77                 Driver Version: 565.77         CUDA Version: 12.7     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3060 ...    Off |   00000000:01:00.0 Off |                  N/A |
| N/A   34C    P0             21W /   80W |      13MiB /   6144MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      2474      G   /usr/bin/gnome-shell                            2MiB |
+-----------------------------------------------------------------------------------------+

Here is my situation: I have two (sudo) users on a machine: 1. userA (created first on the machine. This is also where display :0 is attached) 2. userB (created later) Being on userA I do:

export DISPLAY=:0.0
xclock

And the clock opens on DISPLAY:0 as intended. Now, I want the same steps to work on userB. But unfortunately, it shows:

No protocol specified
xhost:  unable to open display ":0.0"

What I tried: 1. Creating a trusted xauth key using: xauth generate :0.0 . trusted which again shows unable to open display ":0.0" 2. Copying the /home/userA/.Xauthority to /home/userB/.Xauthority. (Note: I did not see any key pertaining to display :0 in the userA xauth list, even though it works.) 3. Creating trusted xauth key for :0 on userA and copying that key to userB. None of these worked. **What worked:** 1. I log-in to userA. I export DISPLAY=:0.0 and then xhost + to enable access from all clients. 2. I log back in to userB. I export DISPLAY=:0.0 and then xclock. I want to eliminate Step 1. I do NOT want to log-in to userA each time. And I did try to xhost + from userB, which shows error already shown above. How can I run xhost + from userB, while also making it think it has the DISPLAY:0 access? **Edit**: As mentioned by @user414777, I was able to:

# On userA
$ xhost +si:localuser:userB

# On userB
$ export DISPLAY=:0.0 ; xclock

And make it work. But these changes don't stay post-reboot.

# After rebooting, on userB
$ export DISPLAY=:0.0 ; xclock
Invalid MIT-MAGIC-COOKIE-1 keyError: Can't open display: :0.0

I'm running Ubuntu 18.04 LTS, 4.18.0-15-generic **SOLVED** I eventually went with a slightly insecure and modified suggestion by @user414777. Instead of adding the change in ~/.xsession or Xsession.d, I added that line in /etc/profile, which applies the change for all users.

I want to create a virtual monitor, add it to my current display as a seperate screen (In X sense) and share it over VNC. Now what I want to do is neatly described below in Arch Linux Wiki article on [Multihead](https://wiki.archlinux.org/title/Multihead#Separate_screens) setup > This is the original way of configuring multiple monitors with X, and it has been around for decades. Each physical monitor is assigned as an X screen, and while you can move the mouse between them, they are more or less independent. Normally the X display has a single identifier such as :0 set in the DISPLAY environment variable, but in this configuration each screen has a different $DISPLAY value. The first screen is :0.0, the second is :0.1 and so on. With this configuration, it is not possible to move windows between screens, apart from a few special programs like GIMP and Emacs which have multi-screen support. For most programs you must change the DISPLAY environment variable when launching to have the program appear on another screen:

# Launch a terminal on the second screen
$ DISPLAY=:0.1 urxvt &

> Alternatively, if you have a terminal on each screen launching programs will inherit the DISPLAY value and appear on the same screen they were launched on. But moving an application between screens involves closing it and reopening it again on the other screen. Working this way does have certain advantages, such as windows popping up on one screen will not steal the focus away from you if you are working on another screen - each screen is quite independent. Tl;dr: A display like :0.1 I have created virtual displays at past which are extenstion of current screen, with xrandr.

xrandr --newmode "1024x768_60.00"  64.11  1024 1080 1184 1344  768 769 772 795  -HSync +Vsync
xrandr --addmode VIRTUAL1 1024x768_60.00  
xrandr --output VIRTUAL1

The problem which arise that I need to pull the windows between monitors (Pull from actual monitor to VNC monitor). How can I specify to make the new display to be a new screen ? I want to do thing opposite to this [question](https://unix.stackexchange.com/questions/239220/possible-to-move-a-window-from-one-x-screen-to-another-on-same-host) , inducing the "problem", so that windows open in same monitor it is called from.

So I've encountered this problem every time I installed linux on my laptop. I've asked it before here , but that didn't go well. Now I'v installed Pop OS (22.04) and I'm fully committed to it, it's not dual boot anymore and it's the only OS I currently run. I did try gaming on it and works just fine, I actually have no problem right now with it, except the brightness of course xd The situation: Brightness of the screen is stuck at maximum (I think, it's really bright), the actual_brightness file has 100 in it, the brightness slider changes the brightness file (both files on /sys/class/backlight/nvidia_0).
I CAN change the brightness using xrandr --output DP-2 --brightness 0.5 for example, but it won't stay that way and none of the files I mentioned change when I use xrandr.
Also, the keyboard backlight works just fine, I didn't install any RGB related software and it has the default red color but the brightness level is working perfect. Changing the brightness of the keyboard backlight will return the display brightness to maximum, if I've used xrandr before and changed it. What I have done: I did dual boot Pop OS before wiping windows from the laptop, and in dual boot mode, I've changed the permissions of brightness and actual_brightness files (chmod 777), and also tried to manually write numbers in them but it didn't work (Used nano and vim for it, in sudo mode). I've searched for solutions but couldn't find working ones. There were somethings about older versions of nvidia drivers solving these problems, but: 1. I need up to date drivers, because I game on it and can't keep an outdated driver for gaming. Basically everything I need to install (steam, wine, lutris) will update the drivers or need up to date drivers. 2. This problem is not new, I had it every single time I've installed linux on this laptop (multiple times Ubuntu, I think I did manjaro one time and probably Pop OS before), and I think it's something related to how my hardware interacts with linux or something. My specs: ASUS ROG GL503VS, Intel Corei7-7700HQ, Nvidia Geforce GTX 1070 (The only GPU on my laptop, and it is dedicated of course), 1920x1080 144hz GeSync capable display (I don't know if it helps at all).
Software: Pop OS 22.04, nvidia-smi output:

$ nvidia-smi
Mon Nov 20 16:50:39 2023       
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.02              Driver Version: 545.29.02    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1070        Off | 00000000:01:00.0  On |                  N/A |
| N/A   60C    P0              35W / 115W |    380MiB /  8192MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
                                                                                         
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      2130      G   /usr/lib/xorg/Xorg                          139MiB |
|    0   N/A  N/A      2234      G   /usr/bin/gnome-shell                         57MiB |
|    0   N/A  N/A      5027      G   ...RunOnOsLogin,WebAssemblyTrapHandler       88MiB |
|    0   N/A  N/A      5593      G   ...,WinRetrieveSuggestionsOnlyOnDemand       90MiB |
+---------------------------------------------------------------------------------------+

And uname -r output:

$ uname -r
6.5.6-76060506-generic

If any other information is needed, I can happily give it to you. I'm quite new to linux (despite many tries) and know a thing or two but not much at all. I really want to use it as my main OS, but I think I'm gonna lose my eyes in the process if I can't solve this problem XD. Many thanks in advance.

**Short version**: Rebooted for the first time in months, following daily updates; proprietary **Nvidia** drivers; **no GUI** (KDE); no smoking gun (so far) in logs. **Specs**: - openSUSE 13.2 (64-bit), fully up to date - kernel 3.16.7-35-desktop - Nvidia GeForce 970 - G04 drivers v361.28-33.1.x86_64 (latest version at download.nvidia.com/opensuse/13.2) - but latest version available by direct download from Nvidia is 361.42 **Long version**: I have a desktop computer with an Nvidia GeForce 970 video card, and two monitors connected to it, one via DVI and the other one via HDMI. I am running openSUSE 13.2, which I update almost daily. Currently at kernel 3.16.7-35-desktop, and use the proprietary Nvidia drivers, currently at 361.28-33.1.x86_64, for the sake of games. That is the latest version of the drivers available from the official repository for openSUSE 13.2, although v361.42 is available for direct download and installation *the hard way*. Kernel and video drivers had been updated at least once since the last time I rebooted (or even logged out), which was at least a few months ago. Now I have rebooted, and cannot get into the GUI - KDE. The console output (on the DVI monitor, which is where grub2 normally runs; the HDMI monitor, which is my primary display, now doesn't get any signal at all. From the boot process is not perfectly consistent in where it stops: sometimes: Reached target Graphical Interface Sometimes: Starting Command Scheduler Sometimes: Started SuSEfirewall2 phase 2 But it is always *after* I *Started X Display Manager*. CTRL+ALT+F7 shows a completely blank screen. 1 through 6 are normal console terminals, and 8 shows just a flashing underscore. I have force-reinstalled the four Nvidia driver packages (G04) to make sure that they are compiled for my current kernel. Interestingly, some of the package names are 361.28.k3.16.6_2-33.1.x86_64, which suggests that they are meant for kernel 3.16.6-2, whereas I am running 3.16.7-35. And compiling for 3.16.6-2 fails, with files-not-found /lib/modules/3.16.6-2-desktop/modules.{order|builtin}, although otherwise that folder looks the same as the modules for 3.16.7-35-desktop and 3.16.7-32-desktop. journalctl --full -b Shows messages from kdm indicating a successful start - e.g.: plymouth is active on VT7, reusing for :0. And kdeinit5: opened connection to :0. The only messages I can find in the boot logs that *might* be a cause for concern are: - NVRM: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text0mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. - Registry: Xlib: extension "XEVIE" missing on display :0 - QXcbConnection: XCB error: 148 (Unknown) /var/log/Xorg.0.log Has only one message, right at the end of the file, that looked in any way suspicious to me: NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon may not be running or the "AcpidSocketPath" X configuration option may not be set correctly. When the ACPI daemon is available, the NVIDIA X display driver will try to use it to receive ACPI event notifications. Booting into Windows, everything works as expected, so I am ruling out an issue with the video card and/or HDMI monitor. I have not yet tried uninstalling the Nvidia drivers and switching to nouveau, nor manually updating the Nvidia drivers to 361.42. I can get into the GUI as normal by rolling the system back to an earlier snapper snapshot, but would rather figure out the current issue than potentially lose months of files. I am willing to dist-upgrade the system to Leap 42.1, but not without good reason to think that doing so would fix the GUI issue. Interestingly, the version of the Nvidia drivers from the official repository is the same for 42.1 as it is for 13.2: 361.28.

I'm running MX Linux and Windows on the same machine. I'm using an LCD television screen connected via HDMI to the graphics card (NVIDIA GeForce RTX 2070 SUPER). **My problem:** - On Windows, I can select resolutions way higher than 1024x768 (i.e. 1920x1080 and above). - However, on MX Linux, 1024x768 is the highest resolution (800x600 and 640x480 are also selectable). - Display settings in MX Linux only show one screen labelled "default". **I tried:** - using xrandr as described here . - "xrandr --newmode (...)" gives the error(/warning?): "Failed to get size of gamma for output default". - "xrandr --addmode default "1920x1080_60.00"" also gives "Failed to get size of gamma for output default". - "xrandr --output default --mode "1920x1080_60.00"" gives the **additional** message: "Configure crtc 0 failed". - no change in display happened after that. - using arandr (GUI) *after* typing the above commands: - "default" is shown as screen - right-click --> resolution: shows the 3 resolutions mentioned above, *and also* "1920x108060.00" - selecting "1920x108060.00" and hitting the check sign --> pop-up error message: "(...) error code 1: xrandr: Failed to get size of gamma for output default" and "xrandr: Configure crtc 0 failed". - no change in display happened after that. I would appreciate any help. It is kind of inconvient having to work with this low (and stretched!) resolution on a 42'' LCD TV screen ;)

I have an external monitor connected to a thunderbolt dock which I would like to utilize. For whatever reason, the monitor appears to be recognized by the system but fails to display anything. - I can confirm that the cable and monitor are fine, as it works perfectly when booted into Windows - The thunderbolt dock seems to not be the issue, as USB peripherals are working fine - Running swaymsg -t get_outputs shows the built in monitor as eDP-1 and the external monitor as DP-2. There is no indication here that the second monitor would not be working. - Running wdisplays shows a preview of what the second display should look like, so evidently the system is rendering what is meant to be sent to the monitor - When I reboot the machine, the tty output is mirrored onto the second monitor. So evidently it is recognized. - There are no errors in sway --debug - There are no entries in dmesg which appear related to the issue - Running lspci -k | grep -A 4 VGA shows that the video driver is loaded

00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
	DeviceName:  Onboard IGD
	Subsystem: Hewlett-Packard Company Device 86f9
	Kernel driver in use: i915
	Kernel modules: i915

- I have set the environment variable WLR_DRM_NO_MODIFIERS=1 as has been recommended to solve related issues - I have attempted to install other versions of wlroots to no avail, though I honestly don't know whether this would be expected to fix the problem. - While the refresh rate is very bad during normal use (hence why I am attempting this method), I can successfully use this monitor with an external Nvidia RTX 2060 GPU, connected via thunderbolt 3, with the the noveau driver. I don't really have a sense of how to best approach troubleshooting this problem, so any advice would be appreciated! If there is any additional information that would be relevant, I am more than happy to provide it. System information: - OS: Manjaro 21.1.6 Pahvo - WM: sway 1.6.1 - wlroots 0.14.1-2

It seems that my current environment (Arch Linux and KDE) is forcing me to use only the native display resolution and frequency for my laptop. My laptop is a gaming laptop, a Dell G15 with both Intel integrated graphics and an Nvidia RTX 3050m. This is what KDE outputs: This is what xrandr outputs: Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 340mm x 190mm 1920x1080 120.04*+ DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) I want to lower my refresh rate to 60 Hz, I even tried manually adding it to xrandr using the command line, but, sadly, it did not work. What is happening here?  It works as expected on the Windows side (I have a dual boot). On a side note, both nvidia-settings and nvidia-smi refuse to open.  Maybe it's a driver problem?

QEMU documentation describes the options -nographic vs -display none. However I'm confused by them. What exactly they are supposed to do and which is the difference ?

I know there are many questions about this but none are this exact case. I have this debian: Linux rodolf 6.1.0-30-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.124-1 (2025-01-12) x86_64 GNU/Linux and I've been using this laptop for maybe years now. Suddenly it started to do this out of nowhere. It's not after logging in, it just happens randomly. I suspend and turn on the laptop and it runs, until it happens again. The last thing I remember doing that is aside the normal is create a profile for when I connect a monitor (and possibly change something there), though I highly doubt that would cause this. Any ideas? EDIT: It seems to only happen when I have a program/window open/focused a while and then click another program/window.

I'm configuring a server with linux Arch using Manjaro (I know, not ideal, but I have my valid reasons). The issue at hand is that I'm unable to change the resolution of the display from the configuration app (currently set at 480p). I tried using Xrandr to change the resolution but the last error I got was "xrandr: Configure crtc 0 failed". When I boot from a live USB with manjaro the resolution is set correctly (1280 x 720) and looks great, so I'm really lost about what the issue could be. clearly the video adapter is not the issue, could it be a issue with video drivers? if so, how do i check and change the propietary driver to an open source one. Info: Video Adapter: H1171x Series (iBCM) VGA controller CPU: 2X Xeon E5

I'm trying to install the nvidia drivers for my T1000 Quadro on my Rhel 8.6 Lenovo p15. However I'm running into errors when trying to build and install the driver. System info? root:Downloads# hostnamectl | grep Kernel Kernel: Linux 4.18.0-372.9.1.el8.x86_64 root:Downloads# lshw -c video *-display UNCLAIMED description: VGA compatible controller product: TU117GLM [Quadro T1000 Mobile] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list configuration: latency=0 resources: memory:ad000000-adffffff memory:80000000-8fffffff memory:90000000-91ffffff ioport:3000(size=128) memory:ae080000-ae0fffff *-display description: VGA compatible controller product: CometLake-H GT2 [UHD Graphics] vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 logical name: /dev/fb0 version: 05 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list fb configuration: depth=32 driver=i915 latency=0 mode=3840x2160 resolution=3840,2160 visual=truecolor xres=3840 yres=2160 resources: iomemory:600-5ff iomemory:400-3ff irq:163 memory:6040000000-6040ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff root:Downloads# cat /etc/redhat-release Red Hat Enterprise Linux release 8.6 (Ootpa) I got my driver from nvidia, here . root:Downloads# ls -l | grep NVIDIA -rwxr-xr-x. 1 brad brad 110600229 May 29 22:22 NVIDIA-Linux-x86_64-430.26.run When I run the run script I get the following for the DKMS step: ERROR: Failed to run /sbin/dkms build -m nvidia -v 430.26 -k 4.18.0-372.9.1.el8.x86_64: Building module: cleaning build area... 'make' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=4.18.0-372.9.1.el8.x86_64 IGNORE_CC_MISMATCH='' modules....(bad exit status: 2) Error! Bad return status for module build on kernel: 4.18.0-372.9.1.el8.x86_64 (x86_64) Consult /var/lib/dkms/nvidia/430.26/build/make.log for more information. What does the make log say? This (pastebin) and sample below. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-mmap.o] Error 1 make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-i2c.o] Error 1 make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-mempool.o] Error 1 In file included from /var/lib/dkms/nvidia/430.26/build/nvidia/nv-p2p.c:15: /var/lib/dkms/nvidia/430.26/build/common/inc/nv-linux.h:118:10: fatal error: asm/kmap_types.h: No such file or directory #include /* page table entry lookup */ ^~~~~~~~~~~~~~~~~~ compilation terminated. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-p2p.o] Error 1 make[2] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/Makefile:1577: _module_/var/lib/dkms/nvidia/430.26/build] Error 2 make[2] : Leaving directory '/usr/src/kernels/4.18.0-372.9.1.el8.x86_64' make[1] : *** [Makefile:157: sub-make] Error 2 make[1] : Leaving directory '/usr/src/kernels/4.18.0-372.9.1.el8.x86_64' make: *** [Makefile:81: modules] Error 2 What if you don't try to install it with dkms? Well I want to, but ok... ERROR: An error occurred while performing the step: "Building kernel modules". See /var/log/nvidia-installer.log for details. and ERROR: An error occurred while performing the step: "Checking to see whether the nvidia kernel module was successfully built". See /var/log/nvidia-installer.log for details. and of course ERROR: The nvidia kernel module was not created. ... ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. Well what does that log say? Alright, the nvidia-installer (pastebin) and sample. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia/nv-instance.o] Error 1 CC [M] /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia/nv-procfs.o In file included from /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia/nv-acpi.c:15: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/common/inc/nv-linux.h:118:10: fatal error: asm/kmap_types.h: No such file or directory #include /* page table entry lookup */ ^~~~~~~~~~~~~~~~~~ compilation terminated. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-uvm/uvm8_fault_buffer_flush_test.o] Error 1 CC [M] /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-modeset.o In file included from /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-fb.c:29: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-fb.h:30:10: fatal error: drm/drmP.h: No such file or directory #include ^~~~~~~~~~~~ compilation terminated. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-uvm/uvm8_peer_identity_mappings_test.o] Error 1 make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-helper.o] Error 1 CC [M] /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.o In file included from /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.c:27: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:33:30: error: field 'base' has incomplete type struct nv_drm_gem_object base; ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:37:5: error: unknown type name 'bool' bool dumb_buffer; ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h: In function 'to_nv_nvkms_memory': /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: error: 'NULL' undeclared (first use in this function) if (nv_gem != NULL) { ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: note: 'NULL' is defined in header ''; did you forget to '#include '? /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:31:1: +#include /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: if (nv_gem != NULL) { ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: note: each undeclared identifier is reported only once for each function it appears in /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:47:16: error: implicit declaration of function 'container_of' [-Werror=implicit-function-declaration] return container_of(nv_gem, struct nv_drm_gem_nvkms_memory, base); ^~~~~~~~~~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:47:37: error: expected expression before 'struct' return container_of(nv_gem, struct nv_drm_gem_nvkms_memory, base); ^~~~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h: In function 'to_nv_nvkms_memory_const': /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:56:19: error: 'NULL' undeclared (first use in this function) if (nv_gem != NULL) { ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:56:19: note: 'NULL' is defined in header ''; did you forget to '#include '? Finally, what if any status does your nvidia driver have? root:Downloads# nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. How about dkms? root:Downloads# dkms status nvidia/430.26: added So I'm not too sure of what is wrong here but it looks like I have some missing modules a kmap_types.h and a drmP.h. What are these? Where can I find them for RHEL 8.6? How can I install them? Also I assume once the driver builds and installs correctly, I should no longer have an UNCLAIMED display? Tanks in advance for any insight!

What does the -dpi option of Xephyr do. I'm trying different values like this: Xephyr -dpi 20 -screen 640x480 :1 and the programs running in the session don't look different in any way.