Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Picture climbs over the edge of the monitor
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Sun Jan 10, 2016 9:58 am    Post subject: Picture climbs over the edge of the monitor Reply with quote

Hello everybody! First of all, sorry for my english. It was quite worn out with the solution of one problem - the image climbs beyond the monitor (only the top and bottom) :cry: . After the upgrade, the next driver card nvidia gforce 760gtx image is climbs over the edge of the monitor and so for the past 2-3 stable releases of the driver. Options compressing images in the monitor is not present. With the acceleration of 3d all right. The monitor is connected to the adapter card via vga - dvi. OS - gentoo x64. Specification of my monitor is here: http://www.newegg.com/Product/Product.aspx?Item=N82E16824236040
Code:

Portage 2.2.26 (python 3.4.3-final-0, default/linux/amd64/13.0, gcc-4.9.3, glibc-2.21-r1, 4.1.12-gentoo-toi x86_64)
=================================================================
System uname: Linux-4.1.12-gentoo-toi-x86_64-Intel-R-_Core-TM-_i7-4770S_CPU_@_3.10GHz-with-gentoo-2.2

Installed sets: @system
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA dlj-1.1"
CBUILD="x86_64-pc-linux-gnu"
CC="gcc"
CFLAGS="-march=core-avx2 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /var/lib/hsqldb"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo"
CXX="g++"
CXXFLAGS="-march=core-avx2 -O2 -pipe"
DISTDIR="/home/searhey/gentoo"
EMERGE_DEFAULT_OPTS="--jobs=1 --keep-going"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs ccache config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync metadata-transfer news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS=" ftp://ftp.byfly.by/pub/gentoo-distfiles/ ftp://ftp.yandex.ru/gentoo-distfiles/ http://distfiles.gentoo.org/ ftp://xeon.gentoo.ru/ http://distfiles.gentoo.org/ "
LANG="ru_RU.UTF-8"
LC_ALL="ru_RU.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j8"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/home/searhey/tmp"
USE="X a52 aac acl alsa amd64 bash-completion berkdb bluetooth bzip2 cairo caps cli consolekit cracklib crypt cxx dbus dri dvd encode exif fbcon ffmpeg flac fontconfig fortran gdbm gif gtk hal iconv icu id3tag imagemagick jpeg kde kf5 kipi lame lm_sensors mad minimal mmx mmxext mng modules mp3 mpeg mtp multilib musepack ncurses nls nptl ogg opengl openmp pam pcre pdf plasma png policykit pvr qt3support qt4 qt5 quicktime rcc readline samba seccomp semantic-desktop session slang sndfile spell sse sse2 ssl svg taglib tcpd theora threads tiff truetype unicode usb v4l2 vdpau vorbis wavpack x264 xattr xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="ru ru_RU" LIRC_DEVICES="devinput" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby20 ruby21" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, INSTALL_MASK, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
That part of the config xorg.conf:
Code:
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Monitor Vendor"
    ModelName      "Monitor Model"
    HorizSync       30.0 - 82.0
    VertRefresh     55.0 - 76.0
    ModeLine       "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
EndSection
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    BusID          "PCI:1:0:0"
    Option         "DPI" "96 x 96"
EndSection

The latest stable release of xorg-server - 1.17.4. DE - plasma - 5.17.0-r2. Games are no problems (Metro redux steam, civilization 5 steam). Maybe you know how to solve the above problem? P.s. free video drivers do not offer because I play the game.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 11:29 am    Post subject: Reply with quote

Siarhei,

Welcome to Gentoo.

1680 x 1050 is a strange native resolution for a display. Video drivers should still detect it automatically using the EDID from the display.
It would be good to see your /var/log/Xorg.0.log so we can see what actually happens.
Please use wgetpaste to put it on a pastebin and past the link here.

You are on the right path to a fix with your ModeLine but the nvidia driver will ignore it unless you give more options in the Section "Device".
A few years ago there were a lot of displays around with faulty EDID data, so this was a common problem.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Sun Jan 10, 2016 12:19 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

Welcome to Gentoo.

1680 x 1050 is a strange native resolution for a display. Video drivers should still detect it automatically using the EDID from the display.
It would be good to see your /var/log/Xorg.0.log so we can see what actually happens.
Please use wgetpaste to put it on a pastebin and past the link here.

You are on the right path to a fix with your ModeLine but the nvidia driver will ignore it unless you give more options in the Section "Device".
A few years ago there were a lot of displays around with faulty EDID data, so this was a common problem.

Thank you for the answer. This is my log:http://pastebin.ca/3325397
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 12:35 pm    Post subject: Reply with quote

Siarhei,

This bit is correct ...
Code:
[    35.370] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    35.370] (**) NVIDIA(0):     device CRT-0 (Using EDID frequencies has been enabled on
[    35.370] (**) NVIDIA(0):     all display devices.)
[    35.386] (II) NVIDIA(0): Validated MetaModes:
[    35.386] (II) NVIDIA(0):     "CRT-0:1680x1050_60.00"
[    35.386] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[    35.386] (**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option
[    35.386] (--) Depth 24 pixmap format is 32 bpp


It looks like Xorg restarted
Code:
[    80.702] (--) NVIDIA(GPU-0):
[326826.688] (II) config/udev: removing device Logitech USB Keyboard


This isn't wrong but it points to the source of your issue.

Code:
[code][507768.361] (II) NVIDIA(0): Setting mode "DVI-I-0: 1400x1050 @1400x1050 +0+0 {ViewPortIn=1400x1050, ViewPortOut=1400x1050+0+0}"
[507809.898] (II) NVIDIA(0): Setting mode "DVI-I-0: 1680x1050_60.00 @1680x1050 +0+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[577603.938] (II) NVIDIA(0): Setting mode "DPY-0:1680x1050_60+0+0{viewportout=1660x1037+10+6}"
[577643.824] (II) NVIDIA(0): Setting mode "DPY-0:1680x1050_60+0+0"[/code]


Something is setting your viewport.
Why did Xorg restart?
What is setting your viewport?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Sun Jan 10, 2016 1:11 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

This bit is correct ...
Code:
[    35.370] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    35.370] (**) NVIDIA(0):     device CRT-0 (Using EDID frequencies has been enabled on
[    35.370] (**) NVIDIA(0):     all display devices.)
[    35.386] (II) NVIDIA(0): Validated MetaModes:
[    35.386] (II) NVIDIA(0):     "CRT-0:1680x1050_60.00"
[    35.386] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[    35.386] (**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option
[    35.386] (--) Depth 24 pixmap format is 32 bpp


It looks like Xorg restarted
Code:
[    80.702] (--) NVIDIA(GPU-0):
[326826.688] (II) config/udev: removing device Logitech USB Keyboard


This isn't wrong but it points to the source of your issue.

Code:
[code][507768.361] (II) NVIDIA(0): Setting mode "DVI-I-0: 1400x1050 @1400x1050 +0+0 {ViewPortIn=1400x1050, ViewPortOut=1400x1050+0+0}"
[507809.898] (II) NVIDIA(0): Setting mode "DVI-I-0: 1680x1050_60.00 @1680x1050 +0+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[577603.938] (II) NVIDIA(0): Setting mode "DPY-0:1680x1050_60+0+0{viewportout=1660x1037+10+6}"
[577643.824] (II) NVIDIA(0): Setting mode "DPY-0:1680x1050_60+0+0"[/code]


Something is setting your viewport.
Why did Xorg restart?
What is setting your viewport?

Here is my full xorg.conf https://bpaste.net/show/44f964beb139
Where can I find the settings viewport?

In the KDEs display settings my monitor has resolution with refresh 1680x1050_60. In NVIDIA X server in the same settings. My display does get EDID because connected via connector VGA-DVI. I had to manually register using modeline. Or I misunderstood something?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 1:49 pm    Post subject: Reply with quote

Siarhei,

Your xorg.conf says you have three displays connected.
Your Xorg.0.log only shows one.

Your three
Code:
Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"
talk about Card0, Card1 and Card2 but you don't have a matching
Code:
Section "Device"
called Card0. It looks like its called
Code:
Section "Device"
    Identifier     "nvidia"


For a single display, with a single video card, make a new xorg.conf that contains only
Code:
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    # BusID          "PCI:1:0:0"
    # Option         "DPI" "96 x 96"
EndSection
The BusID and Option "DPI" should not be needed.

Rename your existing xorg.conf so you can come back to it, if you want to connect three displays. The unneeded sections should be harmless but you need to fix the idenifiers if you want to keep them. Thats how Xorg puts the bits together.

The defaults will give you a USA key map but we can fix that later.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Sun Jan 10, 2016 3:48 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

Your xorg.conf says you have three displays connected.
Your Xorg.0.log only shows one.

Your three
Code:
Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"
talk about Card0, Card1 and Card2 but you don't have a matching
Code:
Section "Device"
called Card0. It looks like its called
Code:
Section "Device"
    Identifier     "nvidia"


For a single display, with a single video card, make a new xorg.conf that contains only
Code:
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    # BusID          "PCI:1:0:0"
    # Option         "DPI" "96 x 96"
EndSection
The BusID and Option "DPI" should not be needed.

Rename your existing xorg.conf so you can come back to it, if you want to connect three displays. The unneeded sections should be harmless but you need to fix the idenifiers if you want to keep them. Thats how Xorg puts the bits together.

The defaults will give you a USA key map but we can fix that later.

Did you recommend, but the result is the same. Here is photo my screen [url]http://savepic.ru/8259731.jpg
Here is log: http://pastebin.ca/3325694
Here is my new xorg.conf: http://codepad.org/tESP9N70. Without section "Screen" xorg-server does not start up.
And one more remark: If I make a print screen picture is correct
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 4:47 pm    Post subject: Reply with quote

Siarhei,

You still have the "Device" naming issue, so Xorg will not associate the two things.
Code:
Section "Device"
    Identifier     "nvidia"     # Here the Device is called "nvidia
    Driver         "nvidia"
    #BusID          "PCI:1:0:0"
    #Option         "DPI" "96 x 96"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"   # Here you tell X to use the Device called "Card0"


The idendifiers need to be unique among sections of the same type and used correctly to cross refer to one another.
Here you are using
Code:
Device         "Card0"
to refer to
Code:
Section "Device"
    Identifier     "nvidia"
Use Card0 or nvidia or anything else but it must be in both places.

You have some configuration information elsewhere too. At the top of the log
Code:
[  1983.307] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,


Then you have
Code:
[  1983.330] (**) NVIDIA(0): Option "TripleBuffer" "True"
...
[429899.882] (**) Option "xkb_rules" "evdev"
[429899.882] (**) Option "xkb_model" "pc104"
[429899.882] (**) Option "xkb_layout" "us,ru"
[429899.882] (**) Option "xkb_variant" ",winkeys"
[429899.882] (**) Option "xkb_options" "grp:caps_toggle,compose:rwin,terminate:ctrl_alt_bksp"

So those options all came from another configuration file somewhere. Probably in /etc/X11/xorg.conf.d/
What else is there?
It looks like you have some nvida options there.
When you make settings in both /etc/X11/xorg.conf.d/ and in xorg.conf, I don't know how the settings are applied.

The Section "InputDevice" with the kbd and mouse drivers in xorg.conf will be ignored an you are using evdev.

Print Screen works because it captures the entire pixel buffer in the video card, not what is actually visible on the display.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Sun Jan 10, 2016 5:52 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

You still have the "Device" naming issue, so Xorg will not associate the two things.
Code:
Section "Device"
    Identifier     "nvidia"     # Here the Device is called "nvidia
    Driver         "nvidia"
    #BusID          "PCI:1:0:0"
    #Option         "DPI" "96 x 96"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"   # Here you tell X to use the Device called "Card0"


The idendifiers need to be unique among sections of the same type and used correctly to cross refer to one another.
Here you are using
Code:
Device         "Card0"
to refer to
Code:
Section "Device"
    Identifier     "nvidia"
Use Card0 or nvidia or anything else but it must be in both places.

You have some configuration information elsewhere too. At the top of the log
Code:
[  1983.307] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,


Then you have
Code:
[  1983.330] (**) NVIDIA(0): Option "TripleBuffer" "True"
...
[429899.882] (**) Option "xkb_rules" "evdev"
[429899.882] (**) Option "xkb_model" "pc104"
[429899.882] (**) Option "xkb_layout" "us,ru"
[429899.882] (**) Option "xkb_variant" ",winkeys"
[429899.882] (**) Option "xkb_options" "grp:caps_toggle,compose:rwin,terminate:ctrl_alt_bksp"

So those options all came from another configuration file somewhere. Probably in /etc/X11/xorg.conf.d/
What else is there?
It looks like you have some nvida options there.
When you make settings in both /etc/X11/xorg.conf.d/ and in xorg.conf, I don't know how the settings are applied.

The Section "InputDevice" with the kbd and mouse drivers in xorg.conf will be ignored an you are using evdev.

Print Screen works because it captures the entire pixel buffer in the video card, not what is actually visible on the display.

Unfortunately, the changes xorg.conf have not helped.
Xorg.conf: http://codepad.org/d14PoTZG,
20opengl.conf from xorg.conf.d: http://codepad.org/XREImozq,
20-keyboard.conf form xorg.conf.d: http://codepad.org/Qb9me6jJ
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 7:58 pm    Post subject: Reply with quote

Siarhei,

How do you start your GUI?
From the command line or with a display manager?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Mon Jan 11, 2016 7:45 am    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

How do you start your GUI?
From the command line or with a display manager?

With help GUI (LightDM because I use OpenRC). But.. sometimes when I poking around in the system I run xorg-server through the console (/etc/init.d/xdm start). Once installed plasma 5, where I tried to use SDDM but failed. With the old version of the video driver all was fine
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 6965

PostPosted: Mon Jan 11, 2016 11:40 am    Post subject: Reply with quote

[ 2028.645] (II) NVIDIA(0): Setting mode "DVI-I-0: 1024x768_60 @1024x768 +0+0 {ViewPortIn=1024x768, ViewPortOut=1024x768+0+0}"

In none of your xorg.conf we can see any 1024 mode define, and any mode ending with _60 is because it's a modeline mode define by a user.
So either you are not displaying the right xorg, or not the right log of this one running, or you have define elsewhere this modeline...

Anyway, you should provide infos that are correct. None can help you if what you are providing is not accurate.
look how i have setup my monitors myself here: https://forums.gentoo.org/viewtopic-t-894978-highlight-.html

at least, check the way i found the right edid value for it. Because at this point, i just even doubt how you find that modeline values.
this is more than suspecious to me:
ModeLine "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync


here's my modeline to compare
Modeline "1680x1050_120" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 -HSync +VSync

However, DO NOT USE MINE, look how i get it, and reproduce the steps i did to get it, but don't use my modeline, don't mess with monitor settings!!! and my monitor is not your model.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Mon Jan 11, 2016 8:23 pm    Post subject: Reply with quote

krinn wrote:
[ 2028.645] (II) NVIDIA(0): Setting mode "DVI-I-0: 1024x768_60 @1024x768 +0+0 {ViewPortIn=1024x768, ViewPortOut=1024x768+0+0}"

In none of your xorg.conf we can see any 1024 mode define, and any mode ending with _60 is because it's a modeline mode define by a user.
So either you are not displaying the right xorg, or not the right log of this one running, or you have define elsewhere this modeline...

Anyway, you should provide infos that are correct. None can help you if what you are providing is not accurate.
look how i have setup my monitors myself here: https://forums.gentoo.org/viewtopic-t-894978-highlight-.html

at least, check the way i found the right edid value for it. Because at this point, i just even doubt how you find that modeline values.
this is more than suspecious to me:
ModeLine "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync


here's my modeline to compare
Modeline "1680x1050_120" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 -HSync +VSync

However, DO NOT USE MINE, look how i get it, and reproduce the steps i did to get it, but don't use my modeline, don't mess with monitor settings!!! and my monitor is not your model.

Yes you are right. I had bugs in ModeLine. Since the graphics card is not able to obtain EDID from the monitorhttp://postimg.org/image/q4ppxfn41/, I used "gtf 1680 1050 60" http://postimg.org/image/eiu9hemvv/.
Nothing has changed.
Okay, I will continue to meet this challenge. How to decide to write the same manual for newbies like me :D
Thank you all for your help!
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 6965

PostPosted: Tue Jan 12, 2016 8:53 am    Post subject: Reply with quote

While in theory you can get any resolution you wish by using the right values set in modeline, there should be more than one way to reach a resolution (and so many possibilities in values).
While it's not a problem for crt monitor, lcd use a native resolution, and that native resolution may be use only when the right values are set.
You should really try to query the monitor edid to get the right values the monitor expect to reach its native resolution, making sure it will run in it. When outside, my monitors goes from too big/too small or tearing the picture or full of dots on screen.
Did you read Dominique_71's comment in the thread, he shown hwinfo --monitor is a quicker way to grab them? While his crt monitor show many resolutions, on mine, it just gave the native one to use.
In our two case, at least, both methods confirm the values in the edid, making sure we get the values from the monitor edid.

Give hwinfo a try, or get them from nvidia the way i did.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Tue Jan 12, 2016 4:52 pm    Post subject: Reply with quote

krinn wrote:
While in theory you can get any resolution you wish by using the right values set in modeline, there should be more than one way to reach a resolution (and so many possibilities in values).
While it's not a problem for crt monitor, lcd use a native resolution, and that native resolution may be use only when the right values are set.
You should really try to query the monitor edid to get the right values the monitor expect to reach its native resolution, making sure it will run in it. When outside, my monitors goes from too big/too small or tearing the picture or full of dots on screen.
Did you read Dominique_71's comment in the thread, he shown hwinfo --monitor is a quicker way to grab them? While his crt monitor show many resolutions, on mine, it just gave the native one to use.
In our two case, at least, both methods confirm the values in the edid, making sure we get the values from the monitor edid.

Give hwinfo a try, or get them from nvidia the way i did.


http://pastebin.ca/3329594 Oh my God. "hwinfo --monitor" is not working. I do not know why. :( Or am I so stupid to happen or something strange with my hardware. Completely not see my monitor.
Xrandr info http://pastebin.ca/3329624 if it needs
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Tue Jan 12, 2016 6:53 pm    Post subject: Reply with quote

Siarhei,

Lets go back to basics and test, when that works, we will build an xorg.conf to suit you if needed.

As root, do the following ...
Make an xorg.conf that contains only
Code:
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    #BusID          "PCI:1:0:0"
    #Option         "DPI" "96 x 96"
EndSection
provided you have only a single graphics card, the commented options are not needed.
Rename your existing xorg.conf as we will want bits of it later.

In rename xorg.conf.d so its not used.

If xdm or your window manager is in the default runlevel, remove it. We want to use startx.
That's us back to default settings for Xorg.

Code:
emerge -1 twm xterm xclock
That installs some nice simple test programs, which --depclean will remove.

Reboot, because I want to be sure there is no junk lying around.
Log in as your normal not root user

If you have a ~/.xinitrc rename it because we want Xorg to use system defaults except for the nvidia driver.

Run startx as your normal user.

You should see three xterminal windows and an analogue clock. This is Tabbed Window Manager. It only uses the left mouse button.
As long as you have an image, we are more interested in
a) does it fit the screen.
b) the content of Xorg.0.log

This is Xorg with all the automatic defaults. If it does the right thing, you can add back pieces of the setup we removed.
Start with the keyboard and mouse, so you at least get your input settings back.

From your logs, Xorg is doing the right thing but its being changed later. As krinn says, you have some settings you don't know about.
We can track them down by adding the renamed things back.

-- edit --

Your Xrandr info in interesting
Code:
Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 16384 x 16384
DVI-I-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      75.03 +  70.07    60.00
   1680x1050     60.00*
The preferred (native) resolution is second in the list.
On the automatic setup, I would expect your display to start at 1024x768 if the Xrandr list is the same as the EDID data.
The preferred resolution should be listed first.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Tue Jan 12, 2016 7:39 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

Lets go back to basics and test, when that works, we will build an xorg.conf to suit you if needed.

As root, do the following ...
Make an xorg.conf that contains only
Code:
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    #BusID          "PCI:1:0:0"
    #Option         "DPI" "96 x 96"
EndSection
provided you have only a single graphics card, the commented options are not needed.
Rename your existing xorg.conf as we will want bits of it later.

In rename xorg.conf.d so its not used.

If xdm or your window manager is in the default runlevel, remove it. We want to use startx.
That's us back to default settings for Xorg.

Code:
emerge -1 twm xterm xclock
That installs some nice simple test programs, which --depclean will remove.

Reboot, because I want to be sure there is no junk lying around.
Log in as your normal not root user

If you have a ~/.xinitrc rename it because we want Xorg to use system defaults except for the nvidia driver.

Run startx as your normal user.

You should see three xterminal windows and an analogue clock. This is Tabbed Window Manager. It only uses the left mouse button.
As long as you have an image, we are more interested in
a) does it fit the screen.
b) the content of Xorg.0.log

This is Xorg with all the automatic defaults. If it does the right thing, you can add back pieces of the setup we removed.
Start with the keyboard and mouse, so you at least get your input settings back.

From your logs, Xorg is doing the right thing but its being changed later. As krinn says, you have some settings you don't know about.
We can track them down by adding the renamed things back.

-- edit --

Your Xrandr info in interesting
Code:
Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 16384 x 16384
DVI-I-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      75.03 +  70.07    60.00
   1680x1050     60.00*
The preferred (native) resolution is second in the list.
On the automatic setup, I would expect your display to start at 1024x768 if the Xrandr list is the same as the EDID data.
The preferred resolution should be listed first.

All this makes tomorrow and that Minsk time too late :D . Xrandr mode (1680x1050 60.00) I created myself because it was not initially after installing a new video card. It was only available mode 1024x768 75.03 + 70.07 60.00. That damn adapter vga-dvi
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Wed Jan 13, 2016 6:14 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

Lets go back to basics and test, when that works, we will build an xorg.conf to suit you if needed.

As root, do the following ...
Make an xorg.conf that contains only
Code:
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    #BusID          "PCI:1:0:0"
    #Option         "DPI" "96 x 96"
EndSection
provided you have only a single graphics card, the commented options are not needed.
Rename your existing xorg.conf as we will want bits of it later.

In rename xorg.conf.d so its not used.

If xdm or your window manager is in the default runlevel, remove it. We want to use startx.
That's us back to default settings for Xorg.

Code:
emerge -1 twm xterm xclock
That installs some nice simple test programs, which --depclean will remove.

Reboot, because I want to be sure there is no junk lying around.
Log in as your normal not root user

If you have a ~/.xinitrc rename it because we want Xorg to use system defaults except for the nvidia driver.

Run startx as your normal user.

You should see three xterminal windows and an analogue clock. This is Tabbed Window Manager. It only uses the left mouse button.
As long as you have an image, we are more interested in
a) does it fit the screen.
b) the content of Xorg.0.log

This is Xorg with all the automatic defaults. If it does the right thing, you can add back pieces of the setup we removed.
Start with the keyboard and mouse, so you at least get your input settings back.

From your logs, Xorg is doing the right thing but its being changed later. As krinn says, you have some settings you don't know about.
We can track them down by adding the renamed things back.

-- edit --

Your Xrandr info in interesting
Code:
Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 16384 x 16384
DVI-I-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      75.03 +  70.07    60.00
   1680x1050     60.00*
The preferred (native) resolution is second in the list.
On the automatic setup, I would expect your display to start at 1024x768 if the Xrandr list is the same as the EDID data.
The preferred resolution should be listed first.


NeddySeagoon,

I did everything like you recommended. Result is nothing
xorg.0.log: http://pastebin.ca/3331063
This is xorg.conf generated by nvidia (nvidia-xconfig):
http://codepad.org/FvH4Yyoq
Xterm runs with a resolution of 1024x768
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Wed Jan 13, 2016 7:49 pm    Post subject: Reply with quote

Siarhei,

Good. That's progress. Its not clear if the log you posted wan using my xorg.conf or the nvidia generated one. It doesn't matter.
This is the important line from the log.
[ 56.316] (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768.

Either your monitor does not provide EDID data for 1680 x 1050 or if it does, its not first in the list, so its not used automatically.

The next step is to generate a modeline that suits your display.
Code:
Recommended Resolution 1680 x 1050
Horizontal Refresh Rate 30 ~ 82KHz
Vertical Refresh Rate  56 ~ 76Hz


your modeline:
ModeLine       "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync

Looks about right, I have checked it later in this post.

Now to tell the nvidia driver that you really know better than the automatic set up because if you just provide the modeline and call it up in the Screen section of xorg.conf, the nvidia driver will ignore it.

The following is based on /usr/share/doc/nvidia-drivers-358.16-r1/README.bz2. nVidia keep changing how the works, so check its the same for your version. You need Appendix B. X Config Options. Its a big file too.

Its the part around
Code:
     Note that, rather than globally disable all uses of the EDID, you can
    individually disable each particular use of the EDID; e.g.,
   
        Option "UseEDIDFreqs" "FALSE"
        Option "UseEDIDDpi" "FALSE"
        Option "ModeValidation" "NoEdidModes"
thats of most interest.
Reading this version of the README suggests that you no longer need to set special options for the driver to use your modeline. That's new to me.

Checking your modeline then ... ModeLine "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
The pixel clock is 146.25MHz. Thats a pixel duration of 6.8376068 ns.
With a total of 2240 pixels on a line, that takes 15.3162393162 us or 65290.1786 lines every second. That suits your monitor, whic needs between 30,000 and 80,000 lines per second.
The next part is written in terms of lines of 15.3162393162 us each, each fram is drawn in 16.6793846153846ms, which is a frame rate of 59.9542502951594 Hz
That's pretty good for 60Hz.

Long story short. Add your modeline back in and change your SubSection "Display"
to read
Code:
    SubSection     "Display"
        Depth       24
        # Modes      "nvidia-auto-select"
        Modes      "1680x1050_60.00"
    EndSubSection

so your modeline should be used.
Is it?
Post the Xorg.0.log.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Wed Jan 13, 2016 8:35 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

Good. That's progress. Its not clear if the log you posted wan using my xorg.conf or the nvidia generated one. It doesn't matter.
This is the important line from the log.
[ 56.316] (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768.

Either your monitor does not provide EDID data for 1680 x 1050 or if it does, its not first in the list, so its not used automatically.

The next step is to generate a modeline that suits your display.
Code:
Recommended Resolution 1680 x 1050
Horizontal Refresh Rate 30 ~ 82KHz
Vertical Refresh Rate  56 ~ 76Hz


your modeline:
ModeLine       "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync

Looks about right, I have checked it later in this post.

Now to tell the nvidia driver that you really know better than the automatic set up because if you just provide the modeline and call it up in the Screen section of xorg.conf, the nvidia driver will ignore it.

The following is based on /usr/share/doc/nvidia-drivers-358.16-r1/README.bz2. nVidia keep changing how the works, so check its the same for your version. You need Appendix B. X Config Options. Its a big file too.

Its the part around
Code:
     Note that, rather than globally disable all uses of the EDID, you can
    individually disable each particular use of the EDID; e.g.,
   
        Option "UseEDIDFreqs" "FALSE"
        Option "UseEDIDDpi" "FALSE"
        Option "ModeValidation" "NoEdidModes"
thats of most interest.
Reading this version of the README suggests that you no longer need to set special options for the driver to use your modeline. That's new to me.

Checking your modeline then ... ModeLine "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
The pixel clock is 146.25MHz. Thats a pixel duration of 6.8376068 ns.
With a total of 2240 pixels on a line, that takes 15.3162393162 us or 65290.1786 lines every second. That suits your monitor, whic needs between 30,000 and 80,000 lines per second.
The next part is written in terms of lines of 15.3162393162 us each, each fram is drawn in 16.6793846153846ms, which is a frame rate of 59.9542502951594 Hz
That's pretty good for 60Hz.

Long story short. Add your modeline back in and change your SubSection "Display"
to read
Code:
    SubSection     "Display"
        Depth       24
        # Modes      "nvidia-auto-select"
        Modes      "1680x1050_60.00"
    EndSubSection

so your modeline should be used.
Is it?
Post the Xorg.0.log.

My Xorg.0.log http://codepad.org/tE1TUbCc
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Wed Jan 13, 2016 8:48 pm    Post subject: Reply with quote

Siarhei,

Code:
[  1216.687] (WW) NVIDIA(0): No valid modes for "CRT-0:1680x1050_60.00"; removing.
[  1216.687] (WW) NVIDIA(0):
[  1216.687] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
[  1216.687] (WW) NVIDIA(0):     "nvidia-auto-select".
[  1216.687] (WW) NVIDIA(0):
[  1216.688] (II) NVIDIA(0): Validated MetaModes:
[  1216.688] (II) NVIDIA(0):     "CRT-0:nvidia-auto-select"
[  1216.688] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[  1216.695] (--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X


This suggests that your modeline is not valid but somehow, X got to set Virtual screen size determined to be 1680 x 1050.

The Virtual screen size is the size that Xorg draws in the pixel buffer. The display resolution need not be the same.
This feature is called a Viewport.

If you have a Virtual screen size of 1680 x 1050 and a display of say 1024x768 the 1024x768 display can be moved around the Virtual screen (1680 x 1050) so you see a piece of the Virtual screen an if it was a larger picture being viewed through a smaller frame. As the mouse approaches the edge of the visible image, the image moves.

All I can say from the log is that Xorg is drawing a 1680 x 1050 image. I cannot tell if it all fits on the screen.
I suspect it may not as your modeline is not being used.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Thu Jan 14, 2016 6:16 am    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

Code:
[  1216.687] (WW) NVIDIA(0): No valid modes for "CRT-0:1680x1050_60.00"; removing.
[  1216.687] (WW) NVIDIA(0):
[  1216.687] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
[  1216.687] (WW) NVIDIA(0):     "nvidia-auto-select".
[  1216.687] (WW) NVIDIA(0):
[  1216.688] (II) NVIDIA(0): Validated MetaModes:
[  1216.688] (II) NVIDIA(0):     "CRT-0:nvidia-auto-select"
[  1216.688] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[  1216.695] (--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X


This suggests that your modeline is not valid but somehow, X got to set Virtual screen size determined to be 1680 x 1050.

The Virtual screen size is the size that Xorg draws in the pixel buffer. The display resolution need not be the same.
This feature is called a Viewport.

If you have a Virtual screen size of 1680 x 1050 and a display of say 1024x768 the 1024x768 display can be moved around the Virtual screen (1680 x 1050) so you see a piece of the Virtual screen an if it was a larger picture being viewed through a smaller frame. As the mouse approaches the edge of the visible image, the image moves.

All I can say from the log is that Xorg is drawing a 1680 x 1050 image. I cannot tell if it all fits on the screen.
I suspect it may not as your modeline is not being used.


On the forum http://ubuntuforums.org/archive/index.php/t-1477507.html, I found the following solution:
Code:
"For the sake of anyone finding this post through Google, here's the fix.

0. Not have deleted the Windows 7 installation that the machine shipped with (not too many times do I find myself saying anything like that, but there ya go)
1. Using softMCCS (http://www.entechtaiwan.com/lib/softmccs.shtm), save the EDID from Windows 7 as edid.bin (it is IMPORTANT that you save this as a .bin file, .raw did not work for me). Save this to a thumb drive.
2. Boot Ubuntu to the recovery console, and save the edid.bin file in /etc/X11 (or wherever, but I found this to be convenient)
3. Add the following to the "Device" section of /etc/X11/xorg.conf:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etct/X11/edid.bin"
4. Reboot. You're all set."
In the evening, try to make it. Though this is not Gentoo-way but in my case the result is needed :D
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Thu Jan 14, 2016 4:41 pm    Post subject: Reply with quote

NeddySeagoon,

I took advantage of edid pull out of the operating system Windows 10x64. The problem was not sloved. Xorg.0.log: http://codepad.org/drnPrNNH, SoftMCCS Report http://codepad.org/U4sbFmBp

Maybe it's time to buy a more modern monitor :D
But the monitor so good becaus my eyes is absolutely not tired of it
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42569
Location: 56N 3W

PostPosted: Thu Jan 14, 2016 9:02 pm    Post subject: Reply with quote

Siarhei,

I'm not sure if the nVidia driver honours the
Code:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etct/X11/edid.bin"

They are driver specific.

Also, nVidia thinks that your display is CRT-0 ... from the log.
Code:
[    51.926] (--) NVIDIA(0):     CRT-0 (boot)
[    51.926] (--) NVIDIA(0):     DFP-0
[    51.926] (--) NVIDIA(0):     DFP-1
[    51.926] (--) NVIDIA(0):     DFP-2
[    51.926] (--) NVIDIA(0):     DFP-3
[    51.926] (--) NVIDIA(0):     DFP-4
[    51.958] (--) NVIDIA(0): Ancor Communications Inc ASUS VW221 (CRT-0): connected
[    51.958] (--) NVIDIA(0): Ancor Communications Inc ASUS VW221 (CRT-0): 400.0 MHz maximum pixel clock
[    51.958] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-0: disconnected
[    51.974] (--) NVIDIA(0): DFP-0: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-1: disconnected
[    51.974] (--) NVIDIA(0): DFP-1: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-2: disconnected
[    51.974] (--) NVIDIA(0): DFP-2: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-3: disconnected
[    51.974] (--) NVIDIA(0): DFP-3: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-3: 330.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-4: disconnected
[    51.974] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[    51.974] (--) NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
so using
Code:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etct/X11/edid.bin"
needs to be changed.
Anything connected to a VGA cable is detected as CRT-, even if its not.

I guess you use a VGA cable?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Siarhei
n00b
n00b


Joined: 10 Jan 2016
Posts: 22
Location: Minsk

PostPosted: Fri Jan 15, 2016 5:17 am    Post subject: Reply with quote

NeddySeagoon wrote:
Siarhei,

I'm not sure if the nVidia driver honours the
Code:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etct/X11/edid.bin"

They are driver specific.

Also, nVidia thinks that your display is CRT-0 ... from the log.
Code:
[    51.926] (--) NVIDIA(0):     CRT-0 (boot)
[    51.926] (--) NVIDIA(0):     DFP-0
[    51.926] (--) NVIDIA(0):     DFP-1
[    51.926] (--) NVIDIA(0):     DFP-2
[    51.926] (--) NVIDIA(0):     DFP-3
[    51.926] (--) NVIDIA(0):     DFP-4
[    51.958] (--) NVIDIA(0): Ancor Communications Inc ASUS VW221 (CRT-0): connected
[    51.958] (--) NVIDIA(0): Ancor Communications Inc ASUS VW221 (CRT-0): 400.0 MHz maximum pixel clock
[    51.958] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-0: disconnected
[    51.974] (--) NVIDIA(0): DFP-0: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-1: disconnected
[    51.974] (--) NVIDIA(0): DFP-1: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-2: disconnected
[    51.974] (--) NVIDIA(0): DFP-2: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-3: disconnected
[    51.974] (--) NVIDIA(0): DFP-3: Internal TMDS
[    51.974] (--) NVIDIA(0): DFP-3: 330.0 MHz maximum pixel clock
[    51.974] (--) NVIDIA(0):
[    51.974] (--) NVIDIA(0): DFP-4: disconnected
[    51.974] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[    51.974] (--) NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
so using
Code:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etct/X11/edid.bin"
needs to be changed.
Anything connected to a VGA cable is detected as CRT-, even if its not.

I guess you use a VGA cable?


Yes of corse. My graphics card has not VGA http://www.gigabyte.com/products/product-page.aspx?pid=4663#sp, and my monitor has only VGA. In my xorg.conf I used CRT-0
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum