Hi, I have config file in /etc/X11/xorg.conf.d that is listing modelines for all resolutions that xrandr indicates is supported by the vmware video driver. With that file existing can anyone suggest why Gnome in Xorg will scale to 4k resolution when the desktop is scaled, but Plasma in X11 will not scale?
regards, Steve
On 1/6/21 19:19, Stephen Morris wrote:
Hi, I have config file in /etc/X11/xorg.conf.d that is listing modelines for all resolutions that xrandr indicates is supported by the vmware video driver. With that file existing can anyone suggest why Gnome in Xorg will scale to 4k resolution when the desktop is scaled, but Plasma in X11 will not scale?
The issue with this was that Gnome and KDE resolutions in the vm are not the same. Under Gnome, when the vm window is maximised to 3840x2160 (4K) the maximum available space that Gnome can be scaled to without getting horizontal or vertical bars is 3840x2075, but under KDE, for the same vm window size, the maximum resolution KDE can be scaled to is 3840x2069. The question now is why is there this sizing difference between Gnome and KDE? In order to get KDE to scale properly, even to fullscreen when the vm conf was set to full screen, was to add more modelines into the xorg config file for the additional resolutions (these were not required with Gnome). The other issue I encountered was that Fedora is not setting up valid video resolutions for the monitor I have. Part of this could be that Fedora has no idea what the monitor is because it doesn't have specific support for it, the other part is it is making invalid assumptions about the monitor capabilities. A lot of the resolutions Fedora is setting up are 16:10 resolutions, which for my monitor which is 16:9 are not valid.
regards, Steve
regards, Steve _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 10 Jun 2021, at 00:42, Stephen Morris samorris@netspace.net.au wrote:
On 1/6/21 19:19, Stephen Morris wrote:
Hi, I have config file in /etc/X11/xorg.conf.d that is listing modelines for all resolutions that xrandr indicates is supported by the vmware video driver. With that file existing can anyone suggest why Gnome in Xorg will scale to 4k resolution when the desktop is scaled, but Plasma in X11 will not scale?
The issue with this was that Gnome and KDE resolutions in the vm are not the same. Under Gnome, when the vm window is maximised to 3840x2160 (4K) the maximum available space that Gnome can be scaled to without getting horizontal or vertical bars is 3840x2075, but under KDE, for the same vm window size, the maximum resolution KDE can be scaled to is 3840x2069. The question now is why is there this sizing difference between Gnome and KDE? In order to get KDE to scale properly, even to fullscreen when the vm conf was set to full screen, was to add more modelines into the xorg config file for the additional resolutions (these were not required with Gnome). The other issue I encountered was that Fedora is not setting up valid video resolutions for the monitor I have. Part of this could be that Fedora has no idea what the monitor is because it doesn't have specific support for it, the other part is it is making invalid assumptions about the monitor capabilities. A lot of the resolutions Fedora is setting up are 16:10 resolutions, which for my monitor which is 16:9 are not valid.
The monitor is responsible for reporting it’s mode information to the operating system using EDID packages. I don’t recall that kernel having any quirks for monitors, but it has been a while since I worked closely with EDID.
If the mode lines are wrong then the monitor is first thing to suspect. Look in dmesg for errors include edid in the line.
Under x11 you can use xrandr —verbose to get the EDID information. There is tool ediddecode (?) that will decode the hex dump you get.
Barry
regards, Steve
regards, Steve _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 11/6/21 03:18, Barry wrote:
On 10 Jun 2021, at 00:42, Stephen Morris samorris@netspace.net.au wrote:
On 1/6/21 19:19, Stephen Morris wrote:
Hi, I have config file in /etc/X11/xorg.conf.d that is listing modelines for all resolutions that xrandr indicates is supported by the vmware video driver. With that file existing can anyone suggest why Gnome in Xorg will scale to 4k resolution when the desktop is scaled, but Plasma in X11 will not scale?
The issue with this was that Gnome and KDE resolutions in the vm are not the same. Under Gnome, when the vm window is maximised to 3840x2160 (4K) the maximum available space that Gnome can be scaled to without getting horizontal or vertical bars is 3840x2075, but under KDE, for the same vm window size, the maximum resolution KDE can be scaled to is 3840x2069. The question now is why is there this sizing difference between Gnome and KDE? In order to get KDE to scale properly, even to fullscreen when the vm conf was set to full screen, was to add more modelines into the xorg config file for the additional resolutions (these were not required with Gnome). The other issue I encountered was that Fedora is not setting up valid video resolutions for the monitor I have. Part of this could be that Fedora has no idea what the monitor is because it doesn't have specific support for it, the other part is it is making invalid assumptions about the monitor capabilities. A lot of the resolutions Fedora is setting up are 16:10 resolutions, which for my monitor which is 16:9 are not valid.
The monitor is responsible for reporting it’s mode information to the operating system using EDID packages. I don’t recall that kernel having any quirks for monitors, but it has been a while since I worked closely with EDID.
If the mode lines are wrong then the monitor is first thing to suspect. Look in dmesg for errors include edid in the line.
Under x11 you can use xrandr —verbose to get the EDID information. There is tool ediddecode (?) that will decode the hex dump you get.
Thanks Barry, I'll check that out. I am using a 4K monitor that has HDR capabilities which, like windows, I won't get that functionality in linux without a monitor specific driver, which doesn't exist for linux. I'm not sure whether the issue I'm seeing is Fedora or the vmware video driver, but I also get the same issues if I use Virtualbox instead of Vmware Player. Before I put the xorg modelines in place xrandr would not list the 4K resolution as being a resolution that was achievable.
regards, Steve
Barry
regards, Steve
regards, Steve _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Fri, 2021-06-11 at 09:35 +1000, Stephen Morris wrote:
I am using a 4K monitor that has HDR capabilities which, like windows, I won't get that functionality in linux without a monitor specific driver, which doesn't exist for linux.
Is it really a case of needing a "driver," or is it just that we need a way to supply new EDID info to the system? There are EDID editors.
In most cases, you just need to set information like pixel dimensions, screen dimensions, and clock rate, to get the graphics chipset to output the right things. It's not like you're also remote controlling the buttons that a monitor might have (well, not usually).
On 11/06/2021 12:46, Tim via users wrote:
On Fri, 2021-06-11 at 09:35 +1000, Stephen Morris wrote:
I am using a 4K monitor that has HDR capabilities which, like windows, I won't get that functionality in linux without a monitor specific driver, which doesn't exist for linux.
Is it really a case of needing a "driver," or is it just that we need a way to supply new EDID info to the system? There are EDID editors.
In most cases, you just need to set information like pixel dimensions, screen dimensions, and clock rate, to get the graphics chipset to output the right things. It's not like you're also remote controlling the buttons that a monitor might have (well, not usually).
Or, since he is using a VM, could it be the same behavior I see in my qemu VM's?
If I run a KDE or GNOME desktop with gdm as my display manager the display will resize to whatever the VM's window size is.
If I use sddm, then it doesn't. And I have to pick the resolution from what the system-settings has determined to be available. I've not gone so far as to try adding modlines since for what I'm doing with my VMs the available resolutons are just fine.
On 11/6/21 15:04, Ed Greshko wrote:
On 11/06/2021 12:46, Tim via users wrote:
On Fri, 2021-06-11 at 09:35 +1000, Stephen Morris wrote:
I am using a 4K monitor that has HDR capabilities which, like windows, I won't get that functionality in linux without a monitor specific driver, which doesn't exist for linux.
Is it really a case of needing a "driver," or is it just that we need a way to supply new EDID info to the system? There are EDID editors.
In most cases, you just need to set information like pixel dimensions, screen dimensions, and clock rate, to get the graphics chipset to output the right things. It's not like you're also remote controlling the buttons that a monitor might have (well, not usually).
I don't know whether its a design of the monitor, but under windows, windows does not provide HDR capability natively, I have to install a monitor specific driver supplied by the vendor, which unfortunately they don't supply for linux.
Or, since he is using a VM, could it be the same behavior I see in my qemu VM's?
If I run a KDE or GNOME desktop with gdm as my display manager the display will resize to whatever the VM's window size is.
I'm using gdm and with Gnome under xorg the display scales when I expand the vm window dimensions, but if I start the vm with the window maximised the display does not scale. I have to unmaximize the window and then remaximize it for the display to scale. With kde it doesn't scale at all unless I put modelines in.
If I use sddm, then it doesn't. And I have to pick the resolution from what the system-settings has determined to be available. I've not gone so far as to try adding modlines since for what I'm doing with my VMs the available resolutons are just fine.
My issue with the system settings under both gnome and kde, is I am using a 4K monitor and the system settings don't offer a 4K resolution, even if the vm is running fullscreen, and also neither does xrandr specify that a 4K resolution is available. The system settings only show that a 4K resolution is accessible when I put in the relevant modeline. The system settings also only show a resolution of 3840x2075 which is the maximum resolution under gnome if I run the vm windowed, or 3840x2069 which is the same maximum resolution under KDE (I'm not sure yet why there is this difference), if I put in modelines.
regards, Steve
On 11/06/2021 18:08, Stephen Morris wrote:
My issue with the system settings under both gnome and kde, is I am using a 4K monitor and the system settings don't offer a 4K resolution, even if the vm is running fullscreen, and also neither does xrandr specify that a 4K resolution is available. The system settings only show that a 4K resolution is accessible when I put in the relevant modeline. The system settings also only show a resolution of 3840x2075 which is the maximum resolution under gnome if I run the vm windowed, or 3840x2069 which is the same maximum resolution under KDE (I'm not sure yet why there is this difference), if I put in modelines.
Are you running KDE and GNOME from the same VM image? Meaning you're running KDE with gdm?
Sometimes the below works, and sometimes it doesn't. With nVidia drivers it fails, with nouveau it works.
Can you install monitor-edid. Then do something like I've done on laptop.
[root@acer ~]# monitor-get-edid | monitor-parse-edid EISA ID: CMO1552 EDID version: 1.3 EDID extension blocks: 0 Screen size: 33.1 cm x 20.7 cm (15.37 inches, aspect ratio 16/10 = 1.60) Gamma: 2.2 Digital signal
# Monitor preferred modeline (59.9 Hz vsync, 49.3 kHz hsync, ratio 16/10, 98 dpi) ModeLine "1280x800" 71 1280 1328 1360 1440 800 803 809 823 -hsync -vsync
On Fri, 2021-06-11 at 20:08 +1000, Stephen Morris wrote:
I don't know whether its a design of the monitor, but under windows, windows does not provide HDR capability natively, I have to install a monitor specific driver supplied by the vendor, which unfortunately they don't supply for linux.
What do you mean by HDR? High Display Resolutions, High Dynamic Range?
For what it's worth, most manufacturers don't supply any drivers for the hardware that Linux runs. Other people have figured them out.
On 11/6/21 20:25, Ed Greshko wrote:
On 11/06/2021 18:08, Stephen Morris wrote:
My issue with the system settings under both gnome and kde, is I am using a 4K monitor and the system settings don't offer a 4K resolution, even if the vm is running fullscreen, and also neither does xrandr specify that a 4K resolution is available. The system settings only show that a 4K resolution is accessible when I put in the relevant modeline. The system settings also only show a resolution of 3840x2075 which is the maximum resolution under gnome if I run the vm windowed, or 3840x2069 which is the same maximum resolution under KDE (I'm not sure yet why there is this difference), if I put in modelines.
Are you running KDE and GNOME from the same VM image? Meaning you're running KDE with gdm?
I'm running KDE and GNOME from the same vm image and using logout, restart or cold start to switch between the two. I'm using vmware player at the moment, but I also had the same issues when running under virtualbox. I was using virtualbox because it supports UEFI whereas vmware player doesn't, but I stopped using it a while ago when an antivirus program broke the virtualbox program because it removed what it considered to be malware.
Sometimes the below works, and sometimes it doesn't. With nVidia drivers it fails, with nouveau it works.
It looks like it doesn't work for me with the vmware driver, I get the following issues: [root@localhost ~]# sudo su - [root@localhost ~]# monitor-get-edid mmap /dev/mem: Permission denied
I tried putting an acl on /dev/mem to give myself rwx access but that made no difference to the above issue.
Below are the modelines that I had to add into the config over and above what xrandr provided as the supported resolutions, coincidentally the supported resolutions that xrandr displayed also happened to match the resolutions that Wayland uses (I've forgotten the name of the Wayland location I would have to look it up on the net again. As a side issue, when I was looking for info on how to get KDE to auto-scale like Gnome does, I found a bug report that someone raised for scaling issues in F34 and I thought they were saying that the Wayland support in KDE was not stable, is that still the case?):
# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz Modeline "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync # 3840x2075 59.99 Hz (CVT) hsync: 128.92 kHz; pclk: 682.75 MHz Modeline "3840x2075_60.00" 682.75 3840 4152 4568 5296 2075 2078 2088 2149 -hsync +vsync # 3840x2071 59.99 Hz (CVT) hsync: 128.68 kHz; pclk: 681.50 MHz Modeline "3840x2071_60.00" 681.50 3840 4152 4568 5296 2071 2074 2084 2145 -hsync +vsync # 3840x2069 59.98 Hz (CVT) hsync: 128.54 kHz; pclk: 680.75 MHz Modeline "3840x2069_60.00" 680.75 3840 4152 4568 5296 2069 2072 2082 2143 -hsync +vsync
The 3840x2075 is the resolution that Gnome auto-scales to when I have the vm window maximised to 4K. The 3840x2160 is the 4K resolution I need for Xorg to scale to 4K when I am running the vm fullscreen. The 3840x2071 was the modeline I was playing around with the get KDE to scale to the maximum window size without the horizontal and vertical scroll bars and 3480x2069 is maximum resolution I could get KDE to scale to without producing the scrollbars, and as I said earlier, I don't know why KDE doesn't work without scrollbars at the 3840x2071 resolution that Gnome works with.
regards, Steve
Can you install monitor-edid. Then do something like I've done on laptop.
[root@acer ~]# monitor-get-edid | monitor-parse-edid EISA ID: CMO1552 EDID version: 1.3 EDID extension blocks: 0 Screen size: 33.1 cm x 20.7 cm (15.37 inches, aspect ratio 16/10 = 1.60) Gamma: 2.2 Digital signal
# Monitor preferred modeline (59.9 Hz vsync, 49.3 kHz hsync, ratio 16/10, 98 dpi) ModeLine "1280x800" 71 1280 1328 1360 1440 800 803 809 823 -hsync -vsync
On 11/6/21 21:48, Tim via users wrote:
On Fri, 2021-06-11 at 20:08 +1000, Stephen Morris wrote:
I don't know whether its a design of the monitor, but under windows, windows does not provide HDR capability natively, I have to install a monitor specific driver supplied by the vendor, which unfortunately they don't supply for linux.
What do you mean by HDR? High Display Resolutions, High Dynamic Range?
For what it's worth, most manufacturers don't supply any drivers for the hardware that Linux runs. Other people have figured them out.
It's High Dynamic Range, its a methodology for improving the colour range, brightness range and detail. I think it is the video equivalent of HDR for photography. Windows would not say the Monitor was HDR compatible and hence provide configuring of it in its monitor settings until I installed the BENQ driver for this monitor.
regards, Steve
On 2021-06-11 6:46 p.m., Stephen Morris wrote:
Below are the modelines that I had to add into the config over and above what xrandr provided as the supported resolutions, coincidentally the supported resolutions that xrandr displayed also happened to match the resolutions that Wayland uses (I've forgotten the name of the Wayland location I would have to look it up on the net again. As a side issue, when I was looking for info on how to get KDE to auto-scale like Gnome does, I found a bug report that someone raised for scaling issues in F34 and I thought they were saying that the Wayland support in KDE was not stable, is that still the case?):
# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz Modeline "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync # 3840x2075 59.99 Hz (CVT) hsync: 128.92 kHz; pclk: 682.75 MHz Modeline "3840x2075_60.00" 682.75 3840 4152 4568 5296 2075 2078 2088 2149 -hsync +vsync # 3840x2071 59.99 Hz (CVT) hsync: 128.68 kHz; pclk: 681.50 MHz Modeline "3840x2071_60.00" 681.50 3840 4152 4568 5296 2071 2074 2084 2145 -hsync +vsync # 3840x2069 59.98 Hz (CVT) hsync: 128.54 kHz; pclk: 680.75 MHz Modeline "3840x2069_60.00" 680.75 3840 4152 4568 5296 2069 2072 2082 2143 -hsync +vsync
I use kvm for my VMs and this is what I get with a default workstation install. I'm using the virtio display option in qemu. I've attached a screenshot of the default list of resolutions that Gnome has. I don't have a 4K display, but all the standard resolutions are included anyway. I can pick the display size and the VM resizes, with scrollbars if necessary.
But if I turn on the "auto-resize VM with window" option, then whenever I resize the VM window or go full-screen, Gnome will switch to the resolution to fit it exactly without scrollbars. This works for both the virtio and QXL display options, but not VGA. So the problem is just with vmware and virtualbox not properly communicating the screen size changes to the VM.
Default window size: # monitor-get-edid | monitor-parse-edid Name: QEMU Monitor EISA ID: RHT1234 EDID version: 1.4 EDID extension blocks: 1 Screen size: 26.0 cm x 19.5 cm (12.80 inches, aspect ratio 4/3 = 1.33) Gamma: 2.2 Digital signal Max video bandwidth: 1200 MHz
HorizSync 30-160 VertRefresh 50-125
# Monitor preferred modeline (75.0 Hz vsync, 59.5 kHz hsync, ratio 4/3, 100 dpi) ModeLine "1024x768" 82.29 1024 1280 1310 1382 768 771 774 794 -hsync -vsync
# Monitor supported CEA modeline (50.0 Hz vsync, 56.2 kHz hsync, ratio 16/9, 187x140 dpi) (bad ratio) ModeLine "1920x1080" 148.5 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Maximized window: # Monitor preferred modeline (75.0 Hz vsync, 82.4 kHz hsync, ratio 1.81, 101 dpi) ModeLine "1920x1062" 213.64 1920 2400 2457 2592 1062 1067 1072 1099 -hsync -vsync
Fullscreen: # Monitor preferred modeline (75.0 Hz vsync, 93.1 kHz hsync, ratio 16/10, 101 dpi) ModeLine "1920x1200" 241.44 1920 2400 2457 2592 1200 1206 1212 1242 -hsync -vsync
On Sat, 2021-06-12 at 11:59 +1000, Stephen Morris wrote:
It's High Dynamic Range, its a methodology for improving the colour range, brightness range and detail. I think it is the video equivalent of HDR for photography.
With photography, it's generally the combination of two photos one where the exposure is made to favour dark end of the scale, the other where the exposure is made to favour the bright end of the scale, and they're combined together, giving you an image that doesn't have blown out highlights and crushed blacks.
With video it could simply be that there's more individual steps between black and full white (mimicing the above photography technique), but often it's engineered to simply add brighter and brighter steps above the original video range. Which seems to be how my bluray player and TV make use of it.
You see that on TV sets where they can be used in full daylight, and you can almost feel the picture across the room. By the time you've turned the contrast down to acceptable levels to watch a movie or tv show, there isn't much advantage in the scheme, the way of lot of things are filmed. And they really do need to be produced with HDR in mind, if they're to take proper advantage of it (i.e. every shot is not exposed for full contrast, only really bright objects should hit peak intensity). A lot of the more recent British TV programs are often filmed that way, the ones trying for a cinematic look. Any scene that's not supposed to be a bright summer's day is often only half contrast.
With computing, not only would you need to tell the graphic system to work in that mode, you'd also need programs with the ability (e.g. your media player, and other programs that display things).
On 12/6/21 14:29, Samuel Sieb wrote:
On 2021-06-11 6:46 p.m., Stephen Morris wrote:
Below are the modelines that I had to add into the config over and above what xrandr provided as the supported resolutions, coincidentally the supported resolutions that xrandr displayed also happened to match the resolutions that Wayland uses (I've forgotten the name of the Wayland location I would have to look it up on the net again. As a side issue, when I was looking for info on how to get KDE to auto-scale like Gnome does, I found a bug report that someone raised for scaling issues in F34 and I thought they were saying that the Wayland support in KDE was not stable, is that still the case?):
# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz Modeline "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync # 3840x2075 59.99 Hz (CVT) hsync: 128.92 kHz; pclk: 682.75 MHz Modeline "3840x2075_60.00" 682.75 3840 4152 4568 5296 2075 2078 2088 2149 -hsync +vsync # 3840x2071 59.99 Hz (CVT) hsync: 128.68 kHz; pclk: 681.50 MHz Modeline "3840x2071_60.00" 681.50 3840 4152 4568 5296 2071 2074 2084 2145 -hsync +vsync # 3840x2069 59.98 Hz (CVT) hsync: 128.54 kHz; pclk: 680.75 MHz Modeline "3840x2069_60.00" 680.75 3840 4152 4568 5296 2069 2072 2082 2143 -hsync +vsync
I use kvm for my VMs and this is what I get with a default workstation install. I'm using the virtio display option in qemu. I've attached a screenshot of the default list of resolutions that Gnome has. I don't have a 4K display, but all the standard resolutions are included anyway. I can pick the display size and the VM resizes, with scrollbars if necessary.
But if I turn on the "auto-resize VM with window" option, then whenever I resize the VM window or go full-screen, Gnome will switch to the resolution to fit it exactly without scrollbars. This works for both the virtio and QXL display options, but not VGA. So the problem is just with vmware and virtualbox not properly communicating the screen size changes to the VM.
The problem I have is Gnome scales when the windows size changes, but KDE does not, which is why I put the modelines in the conf file, and then KDE does scale. How did you you get the monitor-get-edid to work, when I switch to root with "sudo su -" and issue the command I get access denied, have I done something wrong?
regards, Steve
Default window size: # monitor-get-edid | monitor-parse-edid Name: QEMU Monitor EISA ID: RHT1234 EDID version: 1.4 EDID extension blocks: 1 Screen size: 26.0 cm x 19.5 cm (12.80 inches, aspect ratio 4/3 = 1.33) Gamma: 2.2 Digital signal Max video bandwidth: 1200 MHz
HorizSync 30-160 VertRefresh 50-125
# Monitor preferred modeline (75.0 Hz vsync, 59.5 kHz hsync, ratio 4/3, 100 dpi) ModeLine "1024x768" 82.29 1024 1280 1310 1382 768 771 774 794 -hsync -vsync
# Monitor supported CEA modeline (50.0 Hz vsync, 56.2 kHz hsync, ratio 16/9, 187x140 dpi) (bad ratio) ModeLine "1920x1080" 148.5 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Maximized window: # Monitor preferred modeline (75.0 Hz vsync, 82.4 kHz hsync, ratio 1.81, 101 dpi) ModeLine "1920x1062" 213.64 1920 2400 2457 2592 1062 1067 1072 1099 -hsync -vsync
Fullscreen: # Monitor preferred modeline (75.0 Hz vsync, 93.1 kHz hsync, ratio 16/10, 101 dpi) ModeLine "1920x1200" 241.44 1920 2400 2457 2592 1200 1206 1212 1242 -hsync -vsync
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 12/06/2021 21:45, Stephen Morris wrote:
The problem I have is Gnome scales when the windows size changes, but KDE does not, which is why I put the modelines in the conf file, and then KDE does scale.
I think it is going to be "difficult" to track down the actual culprit. I say that because of my following experience.
1. qemu VM, Gnome on Xorg, gdm display manager. Display changes size depending on the qemu console window size.
2. qemu VM, Plasma on Xorg, sddm display manager. Display does not change as the qemu console is resized. I need to add modelines to get what I want and select it in System-Settings.
3. qemu VM, Plasma on Xorg, gdm display manager. Display changes size depending on the qemu console window size.
4. VirtualBox VM, both Gnome on Xorg with gdm and Plasma on Xorg with sddm the Display changes size depending on the VirutalBox console window size.
When it comes to the qemu cases I thought it may have been due to the video driver. But in all cases lsmod shows the same set of virtio modules loaded.
Also, in VirtualBox the modules are all vmwgfx.
I suspect it may be somehow related to kwin_x11 and how it is integrated.
How did you you get the monitor-get-edid to work, when I switch to root with "sudo su -" and issue the command I get access denied, have I done something wrong?
I don't think you've done anything wrong. I think it has to do with the drivers in use. As I mentioned in another post, I can get the correct output with nouveau but not with nVidia. Also having to do with accessing /dev/mem. It also works fine in a qemu/virtio environment. I forgot to check with VirtualBox. I don't have VMware in order to test that.
On 13/6/21 00:33, Ed Greshko wrote:
On 12/06/2021 21:45, Stephen Morris wrote:
The problem I have is Gnome scales when the windows size changes, but KDE does not, which is why I put the modelines in the conf file, and then KDE does scale.
I think it is going to be "difficult" to track down the actual culprit. I say that because of my following experience.
1. qemu VM, Gnome on Xorg, gdm display manager. Display changes size depending on the qemu console window size.
2. qemu VM, Plasma on Xorg, sddm display manager. Display does not change as the qemu console is resized. I need to add modelines to get what I want and select it in System-Settings.
3. qemu VM, Plasma on Xorg, gdm display manager. Display changes size depending on the qemu console window size.
In my case I am running Plasma on Xorg, gdm display manager. Before I put in the xorg config file with the modelines, Gnome would scale with window resizes but Plasma would not.
4. VirtualBox VM, both Gnome on Xorg with gdm and Plasma on Xorg with sddm the Display changes size depending on the VirutalBox console window size.
When it comes to the qemu cases I thought it may have been due to the video driver. But in all cases lsmod shows the same set of virtio modules loaded.
As far as I can see from lsmod, both Gnome and Plasma are loading vmwgfx. Also in both Gnome and Plasma, the xorg log file says that the vmware_drv.so module is being loaded, and then vmware displays a message about the vmware drivers for vmware SVGA being VMWARE05, VMWARE0710, so I'm not sure what it is loading as I can't find and entry in lsmod for either of those "drivers", nor can I find an entry for the vmware driver module xorg said it loaded.
Also, in VirtualBox the modules are all vmwgfx.
I suspect it may be somehow related to kwin_x11 and how it is integrated.
How did you you get the monitor-get-edid to work, when I switch to root with "sudo su -" and issue the command I get access denied, have I done something wrong?
I don't think you've done anything wrong. I think it has to do with the drivers in use. As I mentioned in another post, I can get the correct output with nouveau but not with nVidia. Also having to do with accessing /dev/mem. It also works fine in a qemu/virtio environment. I forgot to check with VirtualBox. I don't have VMware in order to test that.
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
regards, Steve
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable" would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia drivers. It is OK, but should get better when the nVidia driver are updated. I tried this not long after F34 was released but I didn't take notes. Except for the clipboard issues I don't recall what else was bothersome to me.
I would follow https://community.kde.org/Plasma/Wayland_Showstoppers and check and see if anything there is a showstopper for you.
On Tue, 2021-06-15 at 21:42 +0800, Ed Greshko wrote:
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable" would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia drivers. It is OK, but should get better when the nVidia driver are updated. I tried this not long after F34 was released but I didn't take notes. Except for the clipboard issues I don't recall what else was bothersome to me.
Session restore didn't work when I tried it. Don't know about now as I went back to Xorg.
poc
On 15/6/21 23:42, Ed Greshko wrote:
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable" would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia drivers. It is OK, but should get better when the nVidia driver are updated. I tried this not long after F34 was released but I didn't take notes. Except for the clipboard issues I don't recall what else was bothersome to me.
I would follow https://community.kde.org/Plasma/Wayland_Showstoppers and check and see if anything there is a showstopper for you.
I haven't read that article yet, but the thing that is a show stopper for me is that with both Gnome and Plasma is that Wayland will not scale above 2560x1600, which was the maximum resolution reported by xrandr until I put in the xorg modelines. The article I found about Wayland not being ready with Plasma yet, also mention a video config file that Wayland uses and when I looked at that it listed all the same resolutions as those reported by xrandr under both Xorg and Wayland.
regards, Steve
On 16/6/21 01:42, Patrick O'Callaghan wrote:
On Tue, 2021-06-15 at 21:42 +0800, Ed Greshko wrote:
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable" would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia drivers. It is OK, but should get better when the nVidia driver are updated. I tried this not long after F34 was released but I didn't take notes. Except for the clipboard issues I don't recall what else was bothersome to me.
Session restore didn't work when I tried it. Don't know about now as I went back to Xorg.
I'm using Xorg because I can put in modelines, but I think from memory I once was able to get Wayland to run at 4K resolution and that was when I managed to get gdm to run at 4K resolution where upon starting up Wayland it ran in that resolution, but other than that it won't scale. The question I would have is, if Fedora is standardising on Wayland, how long are they going to provide Xorg for?
regards, Steve
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 2021-06-15 4:58 p.m., Stephen Morris wrote:
On 15/6/21 23:42, Ed Greshko wrote:
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable" would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia drivers. It is OK, but should get better when the nVidia driver are updated. I tried this not long after F34 was released but I didn't take notes. Except for the clipboard issues I don't recall what else was bothersome to me.
I would follow https://community.kde.org/Plasma/Wayland_Showstoppers and check and see if anything there is a showstopper for you.
I haven't read that article yet, but the thing that is a show stopper for me is that with both Gnome and Plasma is that Wayland will not scale above 2560x1600, which was the maximum resolution reported by xrandr until I put in the xorg modelines. The article I found about Wayland not being ready with Plasma yet, also mention a video config file that Wayland uses and when I looked at that it listed all the same resolutions as those reported by xrandr under both Xorg and Wayland.
Something to keep in mind is that "Wayland" is a protocol. Each provider implements it independently although I believe there is a common helper library. When I tested F34 Gnome under qemu, it offered resolutions up to 5120x2160. I included a screenshot of that in an earlier email. If you're still talking about running it under vmware, then that's where the problem is. Vmware isn't providing the resolutions you want.
On 6/15/21 6:02 PM, Stephen Morris wrote:
The question I would have is, if Fedora is standardising on Wayland, how long are they going to provide Xorg for?
Well, I expect them to provide Xorg as long as Wayland is only able to work with Gnome and KDE, unless they want everybody who uses any of the other DMs to abandon Fedora. Personally, I use Xfce and I won't use any distro that doesn't support it.
On 16/6/21 10:25, Samuel Sieb wrote:
On 2021-06-15 4:58 p.m., Stephen Morris wrote:
On 15/6/21 23:42, Ed Greshko wrote:
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for information on video resizing, I found an entry for a person raising an issue with video resizing in KDE on Wayland in F34. One of the responses in the issue said that KDE on Wayland was not stable. I remember that in F33 you mentioned to me that KDE on Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable" would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia drivers. It is OK, but should get better when the nVidia driver are updated. I tried this not long after F34 was released but I didn't take notes. Except for the clipboard issues I don't recall what else was bothersome to me.
I would follow https://community.kde.org/Plasma/Wayland_Showstoppers and check and see if anything there is a showstopper for you.
I haven't read that article yet, but the thing that is a show stopper for me is that with both Gnome and Plasma is that Wayland will not scale above 2560x1600, which was the maximum resolution reported by xrandr until I put in the xorg modelines. The article I found about Wayland not being ready with Plasma yet, also mention a video config file that Wayland uses and when I looked at that it listed all the same resolutions as those reported by xrandr under both Xorg and Wayland.
Something to keep in mind is that "Wayland" is a protocol. Each provider implements it independently although I believe there is a common helper library. When I tested F34 Gnome under qemu, it offered resolutions up to 5120x2160. I included a screenshot of that in an earlier email. If you're still talking about running it under vmware, then that's where the problem is. Vmware isn't providing the resolutions you want.
What I'm trying to figure out how to determine is, is the issue vmware, or its it the driver which may be supplied by Fedora or vmware (I'm not entirely sure which), or is it the monitor not honouring the EDID requests?
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 2021-06-16 2:15 a.m., Stephen Morris wrote:
What I'm trying to figure out how to determine is, is the issue vmware, or its it the driver which may be supplied by Fedora or vmware (I'm not entirely sure which), or is it the monitor not honouring the EDID requests?
If the monitor is working on the host system, then it's out of the picture. The VM does not actually talk to the monitor at all. The vmwgfx driver is part of the kernel, nothing specific to Fedora. You would be much better off taking this question to a vmware-specific forum since it's not really Fedora-related.
On 17/6/21 05:01, Samuel Sieb wrote:
On 2021-06-16 2:15 a.m., Stephen Morris wrote:
What I'm trying to figure out how to determine is, is the issue vmware, or its it the driver which may be supplied by Fedora or vmware (I'm not entirely sure which), or is it the monitor not honouring the EDID requests?
If the monitor is working on the host system, then it's out of the picture. The VM does not actually talk to the monitor at all. The vmwgfx driver is part of the kernel, nothing specific to Fedora. You would be much better off taking this question to a vmware-specific forum since it's not really Fedora-related.
Thanks Samuel, I'll do that. I tried installing F34 in virtualbox, and Gnome and KDE on Xorg both scale with window size changes without the requirement for an "xorg.conf" file, but Fedora's performance under virtualbox is hopeless (I've tried various combinations of the acceleration options and nothing makes any difference) and audio doesn't work properly either, anything playing audio hangs the vm. I don't know if it is Windows 10, virtualbox or F34, as F32 used to run fine when I was running that under virtualbox.
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-
Barry -
Ed Greshko -
Joe Zeff -
Patrick O'Callaghan -
Samuel Sieb -
Stephen Morris -
Tim