I see prices are getting better on 4K monitors (samsung has one on sale for $599 at the moment), but I still find it impossible to figure out if any given video card will actually work with one :-(.
Is anyone using a 4K monitor on fedora with open source video drivers and actually getting a 60HZ 3840x2160 image of a single desktop?
If so, care to share which video card and monitor you use?
On Mon, Jun 30, 2014 at 1:18 PM, Tom Horsley horsley1953@gmail.com wrote:
Is anyone using a 4K monitor on fedora with open source video drivers and actually getting a 60HZ 3840x2160 image of a single desktop?
If so, care to share which video card and monitor you use?
Not on a single monitor, but I have a quad headed system running at 7920x1920 from a single Nvidia GK107 using Nouveau drivers.
Tet
On 06/30/14 05:37, Tethys wrote:
On Mon, Jun 30, 2014 at 1:18 PM, Tom Horsley horsley1953@gmail.com wrote:
Is anyone using a 4K monitor on fedora with open source video drivers and actually getting a 60HZ 3840x2160 image of a single desktop?
If so, care to share which video card and monitor you use?
Not on a single monitor, but I have a quad headed system running at 7920x1920 from a single Nvidia GK107 using Nouveau drivers.
Tet
Can you tell me where documentation exists on how to set up the XWindow system. I used /etc/X11/xorg.conf in the past, but that all appears to have been replaced by something I cannot find.
Thanks, sorry for off topic Don
On Thu, 03 Jul 2014 15:11:34 -0700 don fisher wrote:
Can you tell me where documentation exists on how to set up the XWindow system. I used /etc/X11/xorg.conf in the past, but that all appears to have been replaced by something I cannot find.
You don't, it "just works" (except when it doesn't). All the info is supposed to come from the EDID reported by the monitor. Any tweaks are done at runtime via xrandr, xinput, etc. (which may or may not be supported by some GUI setting tool that (maybe) remembers and reproduces the settings via things like the gnome settings daemon).
On my system at home, I have to override the EDID info to make the system believe I have a 47 inch monitor and not a 7 inch monitor with incredibly dense resolution :-). This has all the same info you used to be able to put in xorg.conf, but now it comes in a semi-documented binary file with no good tools to edit it instead of an ascii text file. Such an improvement :-(.
On 07/03/14 15:26, Tom Horsley wrote:
On Thu, 03 Jul 2014 15:11:34 -0700 don fisher wrote:
Can you tell me where documentation exists on how to set up the XWindow system. I used /etc/X11/xorg.conf in the past, but that all appears to have been replaced by something I cannot find.
You don't, it "just works" (except when it doesn't). All the info is supposed to come from the EDID reported by the monitor. Any tweaks are done at runtime via xrandr, xinput, etc. (which may or may not be supported by some GUI setting tool that (maybe) remembers and reproduces the settings via things like the gnome settings daemon).
On my system at home, I have to override the EDID info to make the system believe I have a 47 inch monitor and not a 7 inch monitor with incredibly dense resolution :-). This has all the same info you used to be able to put in xorg.conf, but now it comes in a semi-documented binary file with no good tools to edit it instead of an ascii text file. Such an improvement :-(.
Thanks for getting back. I have a laptop that attach an external monitor to when I am at home. Until today, it always came up in single screen mode, duplicated on both monitors. I had a power failure, and now the system is treating them as two monitors side by side. I am an old timer an prefer the days of the xorg.conf setup. Any ideas on where the button for single screen is hidden?
Thanks Don
Allegedly, on or about 03 July 2014, don fisher sent:
I have a laptop that attach an external monitor to when I am at home. Until today, it always came up in single screen mode, duplicated on both monitors. I had a power failure, and now the system is treating them as two monitors side by side. I am an old timer an prefer the days of the xorg.conf setup. Any ideas on where the button for single screen is hidden
If you're using Gnome, there's a "displays" option in the system settings set of configurators, or a "screen resolution" item in one of the system menus, in it is a "mirror displays" option, which really means both displays show the same as each other, rather than showing a mirror (backwards) image.
Most of these things are easy to find if people just look at the menus.
On 07/03/14 21:13, Tim wrote:
Allegedly, on or about 03 July 2014, don fisher sent:
I have a laptop that attach an external monitor to when I am at home. Until today, it always came up in single screen mode, duplicated on both monitors. I had a power failure, and now the system is treating them as two monitors side by side. I am an old timer an prefer the days of the xorg.conf setup. Any ideas on where the button for single screen is hidden
If you're using Gnome, there's a "displays" option in the system settings set of configurators, or a "screen resolution" item in one of the system menus, in it is a "mirror displays" option, which really means both displays show the same as each other, rather than showing a mirror (backwards) image.
Most of these things are easy to find if people just look at the menus.
Do you know what file the setting are maintained in? I do not use Gnome and would like to be able to edit the appropriate files rather than being so dependent on GUI interfaces.
Thanks for any info, Don
Allegedly, on or about 04 July 2014, don fisher sent:
Do you know what file the setting are maintained in? I do not use Gnome and would like to be able to edit the appropriate files rather than being so dependent on GUI interfaces.
I have to say that there's a certain level of irony in avoiding using a graphical tool for configuring your graphical user interface...
I'm not sure if this file works with every type of desktop: ~/.config/monitors.xml
For system things, like GDM (the logon screen for Gnome), it goes into *that* thing's homespace, rather than /home/username:
i.e. /var/lib/gdm/.config/monitors.xml
KDM may do something similiar (it'll have a different path).
The file begins like this, and may have multiple sections, if you've switched monitors around:
<monitors version="1"> <configuration> <clone>no</clone> ...[snip]...
If each monitor clones each other, it has "yes" in there. Otherwise, "no" cloning spreads the picture across the monitors.
On Sat, 05 Jul 2014 20:42:57 +0930 Tim wrote:
I have to say that there's a certain level of irony in avoiding using a graphical tool for configuring your graphical user interface
I know why I hate it: Because the devs are constantly changing the GUI interface, so you can't find it or figure out how to use it from one release to the next. If you learn how to fix things at a lower level, that changes much less frequently (though that changes too, unfortunately).
On 07/05/14 04:12, Tim wrote:
Allegedly, on or about 04 July 2014, don fisher sent:
Do you know what file the setting are maintained in? I do not use Gnome and would like to be able to edit the appropriate files rather than being so dependent on GUI interfaces.
I have to say that there's a certain level of irony in avoiding using a graphical tool for configuring your graphical user interface...
I'm not sure if this file works with every type of desktop: ~/.config/monitors.xml
For system things, like GDM (the logon screen for Gnome), it goes into *that* thing's homespace, rather than /home/username:
i.e. /var/lib/gdm/.config/monitors.xml
KDM may do something similiar (it'll have a different path).
The file begins like this, and may have multiple sections, if you've switched monitors around:
<monitors version="1"> <configuration> <clone>no</clone> ...[snip]...
If each monitor clones each other, it has "yes" in there. Otherwise, "no" cloning spreads the picture across the monitors.
If you do not use the Gnome or KDE you are SOL. Why should a particular user interface be responsible for things way below the UI level. I do a certain kind of image processing that Gnome is entirely unsuited to. There used to be an system-config-display, or something similar, that you could run from the command line. Why did they feel anybody would be served by restricting the setup to Gnome. Sounds like Apple.corp mentality to me. You can do it, just as long as you do it my way:-(
Allegedly, on or about 05 July 2014, don fisher sent:
If you do not use the Gnome or KDE you are SOL. Why should a particular user interface be responsible for things way below the UI level.
I'm not particularly sure that I agree that it's below that level. It is controlling the graphics in a way that directly suits the graphical user interface (number of screens and their arrangement), which can easily need to be a per-user, or per-situation, configuration.
I tend to agree regarding things like resolution. Screen dimensions and resolutions are fixed entities, and should be set to exactly match the hardware involved. For people who don't like the size of what's on the screen, their ought to be a *SEPARATE* sizing option, one that takes graphics and text into account. And, no, I don't mean buggering up DPI to false values.
These days, we have the ability to have some really high resolution screens, and we often have digital photography that is well in excess of the screen resolutions. So simply playing with screen is X by Y pixels to set things up is really inadequate.
Tim ignored_mailbox@yahoo.com.au writes:
I tend to agree regarding things like resolution. Screen dimensions and resolutions are fixed entities, and should be set to exactly match the hardware involved.
Many people still don't see it that way. And in a way, they are right: Nobody prevents you to use 800x600 on a display which is capable of 1920*1200.
So simply playing with screen is X by Y pixels to set things up is really inadequate.
When you consider screen resolutions as fixed entities, what other choice do you have but to set up the resolutions of your displays as X by Y pixels? Since the display can not display more than what it is capable of, it is irrelevant that you may have content to display the dimensions of which exceed the limits of the hardware.
In any case, I would never want to be forced to use gnome or kde or the like just to set up the display. That doesn't work anyway because kde and gnome are useless without a display.
Tim:
I tend to agree regarding things like resolution. Screen dimensions and resolutions are fixed entities, and should be set to exactly match the hardware involved.
lee:
Many people still don't see it that way. And in a way, they are right: Nobody prevents you to use 800x600 on a display which is capable of 1920*1200.
However, modern displays only work well at one resolution, their native resolution. Exact halves can work, but odd divisions do not work well. Some of them are bloody awful.
So simply playing with screen is X by Y pixels to set things up is really inadequate.
When you consider screen resolutions as fixed entities, what other choice do you have but to set up the resolutions of your displays as X by Y pixels?
None, to be pedantic. But people bodge the resolution to solve other problems:
The size of the fonts The size of the icons The size of graphics
Which really ought to be controlled, directly, and individually.
Tim ignored_mailbox@yahoo.com.au writes:
Tim:
I tend to agree regarding things like resolution. Screen dimensions and resolutions are fixed entities, and should be set to exactly match the hardware involved.
lee:
Many people still don't see it that way. And in a way, they are right: Nobody prevents you to use 800x600 on a display which is capable of 1920*1200.
However, modern displays only work well at one resolution, their native resolution. Exact halves can work, but odd divisions do not work well. Some of them are bloody awful.
Yes, I know --- and many ppl don't realise.
So simply playing with screen is X by Y pixels to set things up is really inadequate.
When you consider screen resolutions as fixed entities, what other choice do you have but to set up the resolutions of your displays as X by Y pixels?
None, to be pedantic. But people bodge the resolution to solve other problems:
The size of the fonts The size of the icons The size of graphics
Which really ought to be controlled, directly, and individually.
The ppl who don't realise that they are supposed to use the resolution their display was made for probably tend to think that reducing the resolution makes everything bigger and easier to read. You might have to remove an obvious way to change the resolution and give them obvious way to adjust these things.
Besides, ppl tend not to realise that there is a relationship between the size of the display and a reasonable resolution. A 21" display made for 1920x1200 is silly because you have to make everything so large that the advantage of the relatively high resolution is negated. And displays that are much wider than high (1920x1050 or whatever that is) suck --- probably even if you turn them by 90 degrees because they aren't wide enough then ... That's particularly awful with laptops nowadays.
On 04/07/14 00:26, Tom Horsley wrote:
On Thu, 03 Jul 2014 15:11:34 -0700 don fisher wrote:
Can you tell me where documentation exists on how to set up the XWindow system. I used /etc/X11/xorg.conf in the past, but that all appears to have been replaced by something I cannot find.
You don't, it "just works" (except when it doesn't). All the info is supposed to come from the EDID reported by the monitor. Any tweaks are done at runtime via xrandr, xinput, etc. (which may or may not be supported by some GUI setting tool that (maybe) remembers and reproduces the settings via things like the gnome settings daemon).
On my system at home, I have to override the EDID info to make the system believe I have a 47 inch monitor and not a 7 inch monitor with incredibly dense resolution :-). This has all
[...]
If you're using GNOME, did you try setting "org.gnome.desktop.interface scaling-factor" to 1? there were some problems with gnome-shell and hiDPI issues.
(I am not sure if those issues were fixed by subsequent updates to gnome-shell).
[....]
On Fri, 04 Jul 2014 17:27:08 +0200 Ahmad Samir wrote:
If you're using GNOME, did you try setting "org.gnome.desktop.interface scaling-factor" to 1? there were some problems with gnome-shell and hiDPI issues.
All the gnome settings are utterly useless. They are based only on the user. If you change the scaling factor to suit one monitor, then it is hopelessly screwed up when you login via NX or run apps remotely on a different display.
Overriding the EDID is the only solution that works consistently since it is per-monitor, which is where the problem is, not per-user, which is the wrong place to change the settings.
On Thu, 3 Jul 2014, Tom Horsley wrote:
On my system at home, I have to override the EDID info to make the system believe I have a 47 inch monitor and not a 7 inch monitor with incredibly dense resolution :-). This has all the same info you used to be able to put in xorg.conf, but now it comes in a semi-documented binary file with no good tools to edit it instead of an ascii text file. Such an improvement :-(.
Which binary file?
On Fri, 4 Jul 2014 11:30:56 -0500 (CDT) Michael Hennebry wrote:
Which binary file?
You have to install one in the firmware directory after modifying it by hook or by crook.
You can read about it in the kernel docs EDID subdir (yum install kernel-doc will stick a local copy of the docs on your system in /usr/share/doc/kernel-doc-* directory).
On my system I have the kernel parameter:
drm_kms_helper.edid_firmware=edid/zootyrgb.bin
and the file /usr/lib/firmware/edid/zootyrgb.bin which I cobbled up using various edid dumping tools, edid docs on wikipedia, and hexedit mode in emacs :-). It is a modified edid from my Samsung TV hacked to give actual dimensions for the modes I use.
Tom Horsley horsley1953@gmail.com writes:
On Fri, 4 Jul 2014 11:30:56 -0500 (CDT) Michael Hennebry wrote:
Which binary file?
You have to install one in the firmware directory after modifying it by hook or by crook.
Huh? You can't just specify a resolution in xorg.conf anymore?
On Fri, 04 Jul 2014 22:58:27 +0200 lee wrote:
Huh? You can't just specify a resolution in xorg.conf anymore?
Nope. After proudly ignoring EDID for 20 years, linux switched gears completely. Now it basically pays no attention to anything you have to say in xorg.conf (though you can occasionally put little fragments of things it is willing to look at in the xorg.conf.d directory for maybe doing things like tweaking options in the video driver).
Tom Horsley horsley1953@gmail.com writes:
On Fri, 04 Jul 2014 22:58:27 +0200 lee wrote:
Huh? You can't just specify a resolution in xorg.conf anymore?
Nope.
man xorg.conf says otherwise.
After proudly ignoring EDID for 20 years, linux switched
20 years ago there was no EDID --- if there was, monitors that supported it were not widely used. And it's supported since a long time now.
gears completely. Now it basically pays no attention to anything you have to say in xorg.conf (though you can occasionally put little fragments of things it is willing to look at in the xorg.conf.d directory for maybe doing things like tweaking options in the video driver).
The man page says otherwise. Without an xorg.conf, my keyboard won't work right, neither would my old trackball. I don't know if you can still do mode lines as you had to before there was EDID. It would be a pity if not.
On 04.07.2014 23:06, Tom Horsley wrote:
On Fri, 04 Jul 2014 22:58:27 +0200 lee wrote:
Huh? You can't just specify a resolution in xorg.conf anymore?
Nope. After proudly ignoring EDID for 20 years, linux switched gears completely. Now it basically pays no attention to anything you have to say in xorg.conf (though you can occasionally put little fragments of things it is willing to look at in the xorg.conf.d directory for maybe doing things like tweaking options in the video driver).
Section "Device" Identifier "card" EndSection
Section "Monitor" Identifier "monitor" Option "PreferredMode" "<xres>x<yres>" EndSection
Section "Screen" Identifier "Default Screen" Device "card" Monitor "monitor" EndSection
"<xres>x<yres>" is one from the built-in set of VESA standard modes, which is normally sufficient. However, if someone needs a non-standard mode, it can be supplied as 'ModeLine' as part of the Section "Monitor". There may be additional directives, but the point is this works with a broken EDID. Therefore this is another solution.
poma
On 06.07.2014 15:09, poma wrote:
On 04.07.2014 23:06, Tom Horsley wrote:
On Fri, 04 Jul 2014 22:58:27 +0200 lee wrote:
Huh? You can't just specify a resolution in xorg.conf anymore?
Nope. After proudly ignoring EDID for 20 years, linux switched gears completely. Now it basically pays no attention to anything you have to say in xorg.conf (though you can occasionally put little fragments of things it is willing to look at in the xorg.conf.d directory for maybe doing things like tweaking options in the video driver).
Section "Device" Identifier "card" EndSection
Section "Monitor" Identifier "monitor" Option "PreferredMode" "<xres>x<yres>" EndSection
Section "Screen" Identifier "Default Screen" Device "card" Monitor "monitor" EndSection
"<xres>x<yres>" is one from the built-in set of VESA standard modes, which is normally sufficient. However, if someone needs a non-standard mode, it can be supplied as 'ModeLine' as part of the Section "Monitor". There may be additional directives, but the point is this works with a broken EDID. Therefore this is another solution.
Actually, I just checked, no need for the Section "Device", so this could be a bare minimum for the selected resolution.
Section "Monitor" Identifier "monitor" Option "PreferredMode" "<xres>x<yres>" EndSection
Section "Screen" Identifier "Default Screen" Monitor "monitor" EndSection
poma
On 04.07.2014 00:26, Tom Horsley wrote:
On Thu, 03 Jul 2014 15:11:34 -0700 don fisher wrote:
Can you tell me where documentation exists on how to set up the XWindow system. I used /etc/X11/xorg.conf in the past, but that all appears to have been replaced by something I cannot find.
You don't, it "just works" (except when it doesn't). All the info is supposed to come from the EDID reported by the monitor. Any tweaks are done at runtime via xrandr, xinput, etc. (which may or may not be supported by some GUI setting tool that (maybe) remembers and reproduces the settings via things like the gnome settings daemon).
On my system at home, I have to override the EDID info to make the system believe I have a 47 inch monitor and not a 7 inch monitor with incredibly dense resolution :-). This has all the same info you used to be able to put in xorg.conf, but now it comes in a semi-documented binary file with no good tools to edit it instead of an ascii text file. Such an improvement :-(.
At least https://www.kernel.org/doc/Documentation/EDID/HOWTO.txt works, right Tom-Sung? :)
$ curl -s https://www.libreoffice.org/bugzilla/attachment.cgi?id=99224 | monitor-parse-edid Name: TOMSUNG EISA ID: TOM0469 EDID version: 1.3 EDID extension blocks: 1 Screen size: 102.0 cm x 57.4 cm (46.08 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Digital signal Max video bandwidth: 230 MHz
HorizSync 26-76 VertRefresh 23-60
# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 47 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
# Monitor supported modeline (60.0 Hz vsync, 47.7 kHz hsync, ratio 16/9, 33 dpi) ModeLine "1360x768" 85.5 1360 1424 1536 1792 768 771 777 795 +hsync +vsync
Besides "Screen size: 16.0 cm x 9.0 cm (7.23 inches, aspect ratio 16/9 = 1.78)" is a known issue for some of the Samsung Smart(?) TVs, so it is best to contact Samsung directly.
poma
On Fri, 04 Jul 2014 22:56:06 +0200 poma wrote:
"Screen size: 16.0 cm x 9.0 cm (7.23 inches, aspect ratio 16/9 = 1.78)" is a known issue for some of the Samsung Smart(?) TVs, so it is best to contact Samsung directly.
It is not only a known issue, it is perfectly legit for Samsung to do that according to the CEA specs they follow. The problem comes from moron programmers who persist in believing that EDID is gospel. New crops of these programmers seem to spring up with great regularity.
Anyway, I've thwarted them all now - I've actually provided an EDID that meets their expectations. Maybe they won't discover any way to break that :-).
On 07/04/14 14:10, Tom Horsley wrote:
On Fri, 04 Jul 2014 22:56:06 +0200 poma wrote:
"Screen size: 16.0 cm x 9.0 cm (7.23 inches, aspect ratio 16/9 = 1.78)" is a known issue for some of the Samsung Smart(?) TVs, so it is best to contact Samsung directly.
It is not only a known issue, it is perfectly legit for Samsung to do that according to the CEA specs they follow. The problem comes from moron programmers who persist in believing that EDID is gospel. New crops of these programmers seem to spring up with great regularity.
Anyway, I've thwarted them all now - I've actually provided an EDID that meets their expectations. Maybe they won't discover any way to break that :-).
I would like to pose I hope a simple question. If you desire something different than the default computed from the EDID data, what can you do. Unix variants have always had a configuration file with preferences that allow one to override the default. I think you said you made your own EDID. Where did you put it so the system pays attention. When the Gnome display manager configures the monitor, where does it put that data? Where in the process is the EDID read. I do not use Gnome and am looking for a way to get back to the flexibility xorg.conf provided. When I tried to run X -configure it referred me to "Please consult the Fedora Project support at http://wiki.x.org" web page that described the old xorg.conf setups. Fedora is becoming too opaque to be useful:-(
On 05.07.2014 00:48, don fisher wrote:
On 07/04/14 14:10, Tom Horsley wrote:
On Fri, 04 Jul 2014 22:56:06 +0200 poma wrote:
"Screen size: 16.0 cm x 9.0 cm (7.23 inches, aspect ratio 16/9 = 1.78)" is a known issue for some of the Samsung Smart(?) TVs, so it is best to contact Samsung directly.
It is not only a known issue, it is perfectly legit for Samsung to do that according to the CEA specs they follow. The problem comes from moron programmers who persist in believing that EDID is gospel. New crops of these programmers seem to spring up with great regularity.
Anyway, I've thwarted them all now - I've actually provided an EDID that meets their expectations. Maybe they won't discover any way to break that :-).
I would like to pose I hope a simple question. If you desire something different than the default computed from the EDID data, what can you do. Unix variants have always had a configuration file with preferences that allow one to override the default. I think you said you made your own EDID. Where did you put it so the system pays attention. When the Gnome display manager configures the monitor, where does it put that data? Where in the process is the EDID read. I do not use Gnome and am looking for a way to get back to the flexibility xorg.conf provided. When I tried to run X -configure it referred me to "Please consult the Fedora Project support at http://wiki.x.org" web page that described the old xorg.conf setups. Fedora is becoming too opaque to be useful:-(
Fedora only use what is already generally defined.
For the umpteenth time, :)
https://www.kernel.org/doc/Documentation/kernel-parameters.txt drm_kms_helper.edid_firmware=[<connector>:]<file> Broken monitors, graphic adapters and KVMs may send no or incorrect EDID data sets. This parameter allows to specify an EDID data set in the /lib/firmware directory that is used instead. Generic built-in EDID data sets are used, if one of edid/1024x768.bin, edid/1280x1024.bin, edid/1680x1050.bin, or edid/1920x1080.bin is given and no file with the same name exists. Details and instructions how to build your own EDID data are available in Documentation/EDID/HOWTO.txt. An EDID data set will only be used for a particular connector, if its name and a colon are prepended to the EDID name.
https://www.kernel.org/doc/Documentation/EDID/HOWTO.txt
poma
...
https://www.kernel.org/doc/Documentation/kernel-parameters.txt drm_kms_helper.edid_firmware=[<connector>:]<file> Broken monitors, graphic adapters and KVMs may send no or incorrect EDID data sets. This parameter allows to specify an EDID data set in the /lib/firmware directory that is used instead. Generic built-in EDID data sets are used, if one of edid/1024x768.bin, edid/1280x1024.bin, edid/1680x1050.bin, or edid/1920x1080.bin is given and no file with the same name exists. Details and instructions how to build your own EDID data are available in Documentation/EDID/HOWTO.txt. An EDID data set will only be used for a particular connector, if its name and a colon are prepended to the EDID name.
Also, this can be achieved via 'udev' - Dynamic device management
$ cat /etc/udev/rules.d/69-edid-swap.rules # This is a custom udev rule which engages an EDID swap after the device is added. # # VGA compatible controller ACTION=="add", ATTRS{vendor}=="0x1234", ATTRS{device}=="0xabcd", RUN+="/bin/sh -c '/bin/echo DVI-I-1:edid/1920x1080.bin > /sys/module/drm_kms_helper/parameters/edid_firmware'" # # udevadm info -a -p /sys/class/drm/card0
$ ls /lib/firmware/edid/1920x1080.bin ls: cannot access /lib/firmware/edid/1920x1080.bin: No such file or directory
$ dmesg [drm] Got built-in EDID base block and 0 extensions from "edid/1920x1080.bin" for connector "DVI-I-1"
$ cat /sys/module/drm_kms_helper/parameters/edid_firmware DVI-I-1:edid/1920x1080.bin
$ monitor-parse-edid /sys/class/drm/card0-DVI-I-1/edid Name: Linux FHD EDID version: 1.3 EDID extension blocks: 0 Screen size: 50.0 cm x 28.1 cm (22.58 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Analog signal Max video bandwidth: 150 MHz
HorizSync 66-68 VertRefresh 59-61
# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 97 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
$ monitor-edid Name: Linux FHD EDID version: 1.3 EDID extension blocks: 0 Screen size: 50.0 cm x 28.1 cm (22.58 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Analog signal Max video bandwidth: 150 MHz
HorizSync 66-68 VertRefresh 59-61
# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 97 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
$ xrandr --prop | monitor-parse-edid Name: Linux FHD EDID version: 1.3 EDID extension blocks: 0 Screen size: 50.0 cm x 28.1 cm (22.58 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Analog signal Max video bandwidth: 150 MHz
HorizSync 66-68 VertRefresh 59-61
# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 97 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
$ monitor-parse-edid /var/log/Xorg.0.log Name: Linux FHD EDID version: 1.3 EDID extension blocks: 0 Screen size: 50.0 cm x 28.1 cm (22.58 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Analog signal Max video bandwidth: 150 MHz
HorizSync 66-68 VertRefresh 59-61
# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 97 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
/var/log/Xorg.0.log ... (II) NOUVEAU(0): EDID vendor "LNX", prod id 0 (II) NOUVEAU(0): Using EDID range info for horizontal sync (II) NOUVEAU(0): Using EDID range info for vertical refresh (II) NOUVEAU(0): Printing DDC gathered Modelines: (II) NOUVEAU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) (II) NOUVEAU(0): EDID vendor "LNX", prod id 0 (II) NOUVEAU(0): Using hsync ranges from config file (II) NOUVEAU(0): Using vrefresh ranges from config file (II) NOUVEAU(0): Printing DDC gathered Modelines: (II) NOUVEAU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) resize called 1920 1080
poma
On Sat, 05 Jul 2014 02:35:19 +0200 poma wrote:
Also, this can be achieved via 'udev' - Dynamic device management
Cool. I hadn't seen that it could be done dynamically. Good to know.
Back on the original topic of 4K monitors. I'll find out tomorrow how much trouble it is to get one working on Fedora. My Samsung UHD monitor and GTX 750Ti video card should arrive (from my reading, I suspect I'll be forced to use the binary nvidia driver).
On 04.07.2014 23:10, Tom Horsley wrote:
On Fri, 04 Jul 2014 22:56:06 +0200 poma wrote:
"Screen size: 16.0 cm x 9.0 cm (7.23 inches, aspect ratio 16/9 = 1.78)" is a known issue for some of the Samsung Smart(?) TVs, so it is best to contact Samsung directly.
It is not only a known issue, it is perfectly legit for Samsung to do that according to the CEA specs they follow. The problem comes from moron programmers who persist in believing that EDID is gospel. New crops of these programmers seem to spring up with great regularity.
Anyway, I've thwarted them all now - I've actually provided an EDID that meets their expectations. Maybe they won't discover any way to break that :-).
Whatever is followed or not, is it technically correct or not, certainly it is done correctly with at least some of the monitors. e.g. "Screen size: 53.1 cm x 29.9 cm (23.99 inches, aspect ratio 16/9 = 1.78)"
Do not be too harsh to fellow developers, it is a difficult life. :)
poma
$ curl -s https://www.libreoffice.org/bugzilla/attachment.cgi?id=99224 | monitor-parse-edid Name: TOMSUNG EISA ID: TOM0469 EDID version: 1.3 EDID extension blocks: 1 Screen size: 102.0 cm x 57.4 cm (46.08 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Digital signal Max video bandwidth: 230 MHz
HorizSync 26-76 VertRefresh 23-60
# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 47 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
# Monitor supported modeline (60.0 Hz vsync, 47.7 kHz hsync, ratio 16/9, 33 dpi) ModeLine "1360x768" 85.5 1360 1424 1536 1792 768 771 777 795 +hsync +vsync
BTW, respected Tom-Sung, how did you manage to insert additional ModeLine?
poma
On Sat, 05 Jul 2014 03:15:57 +0200 poma wrote:
BTW, respected Tom-Sung, how did you manage to insert additional ModeLine?
I don't think I did, I just edited the attributes of the existing info for the 1920x1080 mode lines I got from the dump of the EDID for the Samsung TV I started with. I'm more curious how that attachment wound up in the libreoffice bugzilla? Is it just an alias for the freedesktop bugzilla or something?
(I thought about fixing all the mode lines, but decided that would take way too much time in hexedit mode in emacs :-).
On 05.07.2014 03:39, Tom Horsley wrote:
On Sat, 05 Jul 2014 03:15:57 +0200 poma wrote:
BTW, respected Tom-Sung, how did you manage to insert additional ModeLine?
I don't think I did, I just edited the attributes of the existing info for the 1920x1080 mode lines I got from the dump of the EDID for the Samsung TV I started with.
Respected Tom-Sung, you're a wizard! :)
I'm more curious how that attachment
wound up in the libreoffice bugzilla? Is it just an alias for the freedesktop bugzilla or something?
http://lmgtfy.com/?q=zootyrgb.bin :)
(I thought about fixing all the mode lines, but decided that would take way too much time in hexedit mode in emacs :-).
Ayayayaaaa :)
poma
To all that aided me in my search, I wanted to say that my xorg.conf file works! I have attached the xorg.conf file I used to get back to my single head configuration. I also attached the Xorg.0.log file from /var/log so you can read how it was digested.
If I did anything wrong here, please advise.
Thanks again, Don
On Mon, 30 Jun 2014 08:18:43 -0400 Tom Horsley wrote:
If so, care to share which video card and monitor you use?
To drag this thread back on topic, I have achieved success with a Samsung U28D590D monitor and a EVGA GTX 750Ti video card.
The main stumbling block was the very very old versions of the nvidia binary driver on rpmfusion, but I found an alternate packager of the latest version at negativo17.org, and they worked perfectly. Details here:
http://home.comcast.net/~tomhorsley/hardware/pixels/pixels.html
(I do hope that someday I can switch back to the nouveau driver, but at the moment it has no support for the video card).
-
Ahmad Samir -
don fisher -
lee -
Michael Hennebry -
poma -
Tethys -
Tim -
Tom Horsley