Announcement

Collapse
No announcement yet.

Nvidia driver messes up screen resolution for X11

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • vinnywright
    replied
    Originally posted by joneall View Post
    it was on deja vu (apparentely not mono, tho i don't see that in the list any more). I set it to liberation mono and everything is correct now. The font looks good and the cursor remains firmly attached to the last character typed (just after it).

    Many thanks to all who helped!


    vinny

    Leave a comment:


  • joneall
    replied
    Originally posted by vinnywright View Post
    make sure you are using a monospaced font .

    Konsole>settings>edit current profile>appearance tab>select font.

    VINNY
    It was on Deja vu (apparentely not mono, tho I don't see that in the list any more). I set it to Liberation mono and everything is correct now. The font looks good and the cursor remains firmly attached to the last character typed (just after it).

    Many thanks to all who helped!

    Leave a comment:


  • vinnywright
    replied
    make sure you are using a monospaced font .

    Konsole>settings>edit current profile>appearance tab>select font.

    VINNY

    Leave a comment:


  • joneall
    replied
    I had no xorg.conf.d under /etc/X11, so I created it and inserted the file as you suggested, oshunluvr.

    Should I uncheck "force fonts dpi 96"?

    In any case, my Konsole cursor is still 4 spaces to the right of the last character entered.

    Thanks again for your help. For me, this is a really thorny issue.

    Leave a comment:


  • stephen46710
    replied
    Thanks for the info oshunluvr.
    Last edited by stephen46710; Mar 26, 2017, 12:06 PM.

    Leave a comment:


  • oshunluvr
    replied
    Originally posted by joneall View Post
    I forgot to mention that the logon screen is back to normal. But the Konsole borders on unusable.

    Should I remove/purge and reinstall driver-375?

    Thanks for your input.
    Joneall, see the above post. I do not believe a reinstall is necessary or will help anything. BTW, the "dkms status" output is good. "installed" means the nvidia driver is present in the kernel so the installation went fine. Again, no need to re-install.

    Looking through your output above I see two problems:

    DisplaySize 160 90

    and

    Option "PreferredMode" "Mode 10"

    Unless your monitor is 6.2 inches (160mm) by 3.5 inches (90mm) that DisplaySize is way off.
    The second line above refers to the Modes. The two important ones are:

    Modeline "Mode 10" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
    Modeline "Mode 0" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync

    The numbers in bold are the important piece. Mode 10 is 1280x720 and Mode 0 is 1920x1200. Your system is claiming Mode 10 is preferred. Obviously, this is wrong.

    Either your monitor has incorrect EDID information or Xorg is reading it wrong. Could be a bad HDMI cable or just bad luck. If you have another cable, swap it and try the get-edid thing again. You could also try and install nvidia-378 which is the newest driver. Likely the answer will be to correct xorg. The best way to do this IMO is to create a file in /etc/X11/xorg.conf.d/ named "monitor.conf" and put this in it:

    Code:
    Section "Monitor"
    Identifier "HDMI-0"
    DisplaySize 520 290
    Option "DPMS" "true"
    [COLOR=#3E3E3E] Modeline "1920x1200" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync [/COLOR]
    EndSection
    In theory, this will fix it.
    The DisplaySize above is my 24" monitor. I couldn't find good measurements of yours online but you can measure it yourself or look for someone else's posted xorg.conf files. Xorg should - once it has the size and resolution correct - correctly set the DPI. If not, we can fix that too.

    Leave a comment:


  • oshunluvr
    replied
    Originally posted by stephen46710 View Post
    HI oshunluvr,

    this part of your post is what I meant. (The last bit of what I posted: !|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)").

    "An uppercase status or error letter indicates the package is likely to cause severe problems"
    I'm sorry Stephen I guess I didn't explain well enough. That message that you keep referring to above is NOT saying that he needs to re-install. On the contrary, it's saying it was installed and there are NO errors regarding the package installation.

    The bit you posted again that I have quote above is an INFORMATION string explaining how to read the last line of the output. The last line of the output is the ONLY line showing actual status information of the package that has been queried. Here is the query output from my system on my nvidia driver:
    Code:
    [FONT=monospace]
    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/ Name                                Version                Architecture           Description
    +++-===================================-======================-======================-============================================================================
    ii  nvidia-378                          378.13-0ubuntu0~gpu16. amd64                  NVIDIA binary driver - version 378.13
    [/FONT]
    The first three lines above EXPLAIN the meaning of the the first three LETTERS of the last line.

    The first "i" in the last line above means an install was DESIRED of the package. Thus the first info line is labeled "Desired="
    The second "i" in the last line above means the STATUS of the package is installed. Thus the second info line is labeled "Status="
    The third character in the last line above is blank. This means NO ERRORS. Thus the third info line is labeled "Err?=". Also note this last info line states "uppercase=bad". None of the first three characters in the first line are uppercase. Therefore nothing is "bad"

    If you are still unclear as to what I am trying to explain, please open a terminal and type "man dpkg-query" to read the full help file.
    Last edited by oshunluvr; Mar 26, 2017, 08:03 AM.

    Leave a comment:


  • joneall
    replied
    I forgot to mention that the logon screen is back to normal. But the Konsole borders on unusable.

    Should I remove/purge and reinstall driver-375?

    Thanks for your input.

    Leave a comment:


  • joneall
    replied
    Thanks for your help, everybody.

    Here is xrandr:

    $ xrandr
    Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 16384 x 16384
    VGA-0 disconnected (normal left inverted right x axis y axis)
    DVI-D-0 disconnected (normal left inverted right x axis y axis)
    HDMI-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 160mm x 90mm
    1920x1200 59.95*+
    1920x1080 60.00 59.94 50.00 60.05 60.00 50.04
    1680x1050 59.95
    1600x1200 60.00
    1440x900 59.89
    1280x1024 60.02
    1280x960 60.00
    1280x800 59.81
    1280x720 60.00 59.94 50.00
    1024x768 60.00
    800x600 60.32 56.25
    720x576 50.00
    720x480 59.94
    640x480 59.94
    DVI-D-1 disconnected (normal left inverted right x axis y ax

    The odd-ball alignment is what I see. Any display with columns, such as "ls -l", has the columns all skewed.

    Here is read-edid.

    1$ sudo get-edid |parse-edid
    This is read-edid version 3.0.2. Prepare for some fun.
    Attempting to use i2c interface
    No EDID on bus 0
    No EDID on bus 1
    No EDID on bus 2
    No EDID on bus 3
    No EDID on bus 4
    No EDID on bus 5
    No EDID on bus 6
    No EDID on bus 7
    No EDID on bus 9
    1 potential busses found: 8
    256-byte EDID successfully retrieved from i2c bus 8
    Looks like i2c was successful. Have a good day.
    Checksum Correct

    Section "Monitor"
    Identifier "SyncMaster"
    ModelName "SyncMaster"
    VendorName "SAM"
    # Monitor Manufactured week 31 of 2008
    # EDID version 1.3
    # Digital Display
    DisplaySize 160 90
    Gamma 2.60
    Option "DPMS" "true"
    Horizsync 27-81
    VertRefresh 50-60
    # Maximum pixel clock is 170MHz
    #Not giving standard mode: 1600x1200, 60Hz
    #Not giving standard mode: 1280x1024, 60Hz
    #Not giving standard mode: 1280x960, 60Hz
    #Not giving standard mode: 1280x800, 60Hz
    #Not giving standard mode: 1440x900, 60Hz
    #Not giving standard mode: 1680x1050, 60Hz

    #Extension block found. Parsing...
    Modeline "Mode 10" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
    Modeline "Mode 0" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync
    Modeline "Mode 1" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
    Modeline "Mode 4" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
    Modeline "Mode 5" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
    Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
    Modeline "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
    Modeline "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
    Modeline "Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
    Modeline "Mode 11" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
    Modeline "Mode 12" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace
    Modeline "Mode 13" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
    Option "PreferredMode" "Mode 10"
    EndSection

    I don't know what it is supposed to say, but it does find the screen type (Samsung Syncmaster) correctly. I wonder, tho, about that line

    DisplaySize 160 90

    What does that mean? And then

    1$ dkms status
    bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed
    nvidia-375, 375.39, 4.4.0-66-generic, x86_64: installed

    and

    1$ dpkg -l nvidia-375
    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/ Name Version Architecture Description
    +++-=======================-================-================-================================================== ==
    ii nvidia-375 375.39-0ubuntu0. amd64 NVIDIA binary driver - version 375.39

    No capital letters.

    Leave a comment:


  • joneall
    replied
    Originally posted by stephen46710 View Post
    Hi,

    you should be using the "nvidia-375" package according to the Nvidia drivers website!, (see supported products):

    http://www.geforce.com/drivers/results/114708

    If you can get into recovery mode (a network cable connection is required!), first go to "network" and then "root" and enter the following command:

    sudo apt-get remove nvidia-361 && sudo apt-get install nvidia-375

    Restart with Ctrl + Alt + Del, do not click on resume!.
    Are you telling me you cannot install the Nvidia driver under X11? But that is what I have always done, before now with the system graphical driver tool, yesterday by line commands.

    Leave a comment:


  • stephen46710
    replied
    HI oshunluvr,

    this part of your post is what I meant. (The last bit of what I posted: !|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)").

    "An uppercase status or error letter indicates the package is likely to cause severe problems"

    Maybe try the following terminal command?:

    sudo apt-get remove nvidia-375 && sudo apt-get install nvidia-375

    Another way is to go into recovery mode and activate network (network cable connection required) and then run "dpkg" and restart with Ctrl + Alt + Del (Don't click on resume!).

    Leave a comment:


  • oshunluvr
    replied
    Originally posted by stephen46710 View Post
    Also, on the following line:

    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

    it looks like it is saying you need to re-install the drivers? (I might be reading that wrong?).
    No, that output looks normal to me. It's the last line you have to read, the rest is just explanations of what you might see. At the beginning of the last line, "ii " means "install", "installed" and the third character is blank, meaning no errors. See "man dpkg-query" for a full description.

    Code:
    [FONT=monospace][COLOR=#000000]The first three columns of the output show the desired action, the package status, and errors, in that order.[/COLOR]
    
              Desired action:
                u = Unknown
                i = Install
                h = Hold
                r = Remove
                p = Purge
    
              Package status:
                n = Not-installed
                c = Config-files
                H = Half-installed
                U = Unpacked
                F = Half-configured
                W = Triggers-awaiting
                t = Triggers-pending
                i = Installed
    
              Error flags:
                <empty> = (none)
                R = Reinst-required
    
              An uppercase status or error letter indicates the package is likely to cause severe problems. Please refer to  [COLOR=#000000][B]dpkg[/B][/COLOR][COLOR=#000000](1)  for  information  about  the[/COLOR]
              above states and flags.
    [/FONT]
    Last edited by oshunluvr; Mar 25, 2017, 03:13 PM.

    Leave a comment:


  • stephen46710
    replied
    Also, on the following line:

    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

    it looks like it is saying you need to re-install the drivers? (I might be reading that wrong?).

    Leave a comment:


  • oshunluvr
    replied
    Originally posted by joneall View Post
    Thanks for your reply. However, I don't understand, because 375 is what I installed.

    $ dpkg -l nvidia-361
    dpkg-query: no packages found matching nvidia-361
    $ dpkg -l nvidia-375
    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/ Name Version Architecture Description
    +++-=======================-================-================-================================================== ==
    ii nvidia-375 375.39-0ubuntu0. amd64 NVIDIA binary driver - version 375.39

    Why is xorg.conf still talking about 361?
    Here's the contents of xorg.conf, if that is any help:

    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 361.42 (buildd@lgw01-18) Tue Apr 5 14:33:28 UTC 2016
    Your xorg.conf is being created by nvidia-settings, not the driver. Install nvidia-settings 375. You should also check the output of dkms status to be sure your driver is properly installed. Xorg errors and warnings are in /var/log/Xorg.0.log at every boot.

    Leave a comment:


  • oshunluvr
    replied
    xorg.conf isn't used by default anymore and putting settings there will work, until you upgrade your driver and then the file will be deleted. The "proper" way to pass settings to xorg is in /etc/X11/xorg.conf.d/ and then use various .conf files to represent the former sections, like "device.conf" for your device section, etc.

    Your log in screen isn't controlled by xorg, it's controlled by sddm. You could try editing /etc/init/sddm.conf and adding:

    ServerArguments=-nolisten tcp -geometry 1920x1200 -dpi 96

    Since you didn't post any log files, I would guess the issue is being caused by your monitor not being properly detected or EDID is missing or incorrect. This would explain most of what you're seeing. Try posting the output of xrandr and install the package "read-edid", then in the console type "sudo get-edid |parse-edid" and it will display what your monitor is showing to the system.

    Also, another way to get these things fixed is to use xrandr to correct mis-shapen video.

    As far as the cursor problem - likely being caused by the video issues so fix the resolution first.
    Last edited by oshunluvr; Mar 25, 2017, 02:20 PM.

    Leave a comment:

Working...
X