3 Screen Set up issue

[betty]

I dont know, I not understand that one?

[apparatus]

Open Q → Gear icon → System Settings → Display
There you’ll see the current layout of your monitors.

[betty]

yes thats where i am, it shows all 3 monitors in my fav layout, laptop bottom middle, xtrat 2 monitors directly above a little left and a little right and it knows the laptop is the primary monitor also if that helps.
In the advanced tab i have the set up named as 3monitor set up and all 3 options in that tab are toggled on.

[apparatus]

Run command for your new monitor layput:

qvm-features dom0 gui-videoram-min $((3840 * 2160 * 4 / 1024))

And restart qubes.

[betty]

i did that, i then opened up Dom0 CLI and checked;
$ xrandr --verbose | grep “Screen 0”
and the current is = 3840 x 2160 but i thought it should read 5760 x 3240 ?

Yet what makes even less sense to me right now is also that all 3 screens seem to be running normally right now

[apparatus]

The layout of your monitors on the screen changed for some reason, I don;t know why.
Here:

@betty

Screen 0: minimum 320 x 200, current 5760 x 1080, maximum 16384 x 16384

It was like this:

@apparatus

Your monitors layout on the screen is like this:

| monitor1 | monitor2 | monitor3 | 1080
    1920   +   1920   +   1920   = 5760

But now it changed to this:

@betty

$ xrandr --verbose | grep “Screen 0”
and the return was the same as last time when i was expecting it to now say that the current screen was; 5760 somewhere it didnt, it stated the current was; 3840 x 2160

@apparatus

If your current screen size is 3840 x 2160 that means that your current layout is:

    1920   +   1920     = 3840
| monitor1 | monitor2 | 1080 +
| monitor3 |            1080 = 2160

[betty]

@apparatus

If your current screen size is 3840 x 2160 that means that your current layout is:

    1920   +   1920     = 3840
| monitor1 | monitor2 | 1080 +
| monitor3 |            1080 = 2160

i dont quite understand this part of your message, does it mean all 3 monitors should be working correct or only 2 as all 3 seem to be ok now in actuality?

[apparatus]

All 3 of them are working but the position of monitors differs.
You can move monitors on the screen however you want so one monitor would be to the left/right/up/down of the other monitor.
Move the mouse cursor between the monitors to see that if you will move the mouse from monitor1 down out of the monitor1 display it’ll move to monitor3 etc.

[betty]

i still not understand, yet all 3 monitors most certainly are working as should and the curser does go from screen to screen as i like, so i am most pleased, i will log this as sorted and sign off of this issue for now and await the issue to return and then i shall re-read all of this again and try and re-sort out as you have been extremely helpful and explicit and i am most grateful for your help and guidance, more so that you may realise, thanks and much love to you

[ddevz]

@betty

Ill write out the Output below;
$ free -h

Mem Total: 2.6Gi Used: 963Mi Free: 940Mi Shared: 250Mi Buff/Cache: 776Mi Available: 1.4Gi

Swap Total: 3.9Gi Used: 0B Free: 3.9Gi

If the available number gets to 0, then swapping will start and things will slow down (often in a extreme way). And if your wondering what if you didn’t have swap, then it got to 0 it would just pick a process to kill in order to free up memory.

multiple screen can be hard on memory, so running the command occasionally can be insightful.

[betty]

@ddevz

If the available number gets to 0, then swapping will start and things will slow down (often in a extreme way). And if your wondering what if you didn’t have swap, then it got to 0 it would just pick a process to kill in order to free up memory.

multiple screen can be hard on memory, so running the command occasionally can be insightful.

when you say “number gets to 0” what is the number you refer to please?
I dont know what is bad or good when im looking at any number

When any number is bad then how do i make it good again, presumable i need to clear a cache or something? Thanks

[ddevz]

@betty

when you say “number gets to 0” what is the number you refer to please?

@betty

$ free -h

Mem Total: 2.6Gi Used: 963Mi Free: 940Mi Shared: 250Mi Buff/Cache: 776Mi Available: 1.4Gi

Swap Total: 3.9Gi Used: 0B Free: 3.9Gi

The part that says: Available: 1.4Gi. That is the “available number” I was referring to.

You do not want that one to ever get to zero. (the “Available” number getting to zero is seriously bad, as mentioned before)

Also, when the “Used: 0B” part of the “Swap Total” goes above 0B, you should keep a eye on it. If the swap line says “Used: 20Mi”, i wouldn’t be too worried about it, but i’d keep a eye on it. If the swap line says “Used: 1.0Gi”, then your system is probably crawling to a point that you end up rebooting it without shutting it down.

[betty]

@ddevz

You do not want that one to ever get to zero. (the “Available” number getting to zero is seriously bad, as mentioned before)

Also, when the “Used: 0B” part of the “Swap Total” goes above 0B, you should keep a eye on it. If the swap line says “Used: 20Mi”, i wouldn’t be too worried about it, but i’d keep a eye on it. If the swap line says “Used: 1.0Gi”, then your system is probably crawling to a point that you end up rebooting it without shutting it down.

how do i increase it to prevent the issue ever happening or how do i resolve the issue when i encounter the issue pls?

[ddevz]

Here’s how to set the dom0 memory, but increasing dom0 memory can reduce the amount of memory you have for VMs, so I’d recommend waiting till you have a problem before doing it.

How to increase dom0 RAM size?

As @renehoj says, the 4GB is a limit on the memory available to dom0. The remaining memory is allocated to the qubes you run. Qubes actively allocates memory between qubes. In most cases 4GB should be fine in dom0, because it isn’t doing much work. If you do want to change the maximum allocated to dom0, you can do so temporarily, by interrupting the boot and editing the boot parameters: the default parameter is dom0_mem=max:4096M To make the change permanent, edit /etc/default/grub, chan…