Announcement

**oshunluvr** · Nov 03, 2015, 01:29 PM

What does your log say? The usual culprit here is a bad EDID. You can either make an xorg.conf or set the desired resolution using xrandr.

**vsreeser** · Nov 03, 2015, 02:30 PM

Originally posted by oshunluvr View Post

What does your log say? The usual culprit here is a bad EDID. You can either make an xorg.conf or set the desired resolution using xrandr.

Not sure where the xorg.conf file is supposed to be.

I tried setting res using xrandr and got a bunch of errors.

Code:

xrandr --newmode VGA1 1680x1050_60.00  147.14  [URL="tel:1680 1784 1968 2256"]1680 1784 1968 2256[/URL]  [URL="tel:1050 1051 1054 1087"]1050 1051 1054 1087[/URL]
xrandr: Failed to get size of gamma for output default
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  19
  Current serial number in output stream:  19

Tried get-edid

Code:

get-edid                                          
This is read-edid version 3.0.1. Prepare for some fun.                               
Attempting to use i2c interface                                                        
No EDID on bus 1                                                                        
1 potential busses found: 0                                                               
Bus 0 doesn't really have an EDID...                                                       
Couldn't find an accessible EDID on this computer.

The monitor is connected using DVI to DVI cable. is an Envision G2219w1. Searching on how to fix edid or make a fake one. as this is probably the culprit

Wondering how much hair I will lose before this works right

**oshunluvr** · Nov 03, 2015, 03:08 PM

I've never heard of anyone creating a fake edid or needing to.

First off, your newmode command is malformed. Try xrandr --newmode "1680x1050_60.00" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 noted the added quotes and the removal of the VGA1 reference.

More worrisome is the lack of port detection, as xrandr is listing only "default." Maybe that's normal if you have only one port. Besides, if it's connected as DVI to DVI it wouldn't likely be "VGA1." Likely it would be something like "DVI-I-0" or similar. Most likely, your system is not using the correct driver - but you have to read your log file to tell which one is loaded. Try cat /var/log/Xorg.0.log |grep river and look to see which video driver is loaded.

I don't understand you connecting kernel updates to the apt-get dist-upgrade command. If a kernel update isn't there, dist-upgrade won't install one. If a kernel upgrade is there, then it's usually a security update and you should be installing it. Your server should be able to withstand a reboot unattended or it's not much of a server. Are you installing the nvidia driver from nvidia instead of the one supplied by Kubuntu? If so, you're kinda on your own as almost no one does that anymore nor is there any reason to IMO. dkms does an outstanding job of adding the nvidia blob to the kernel automatically.

**vsreeser** · Nov 03, 2015, 05:35 PM

Originally posted by oshunluvr View Post

I've never heard of anyone creating a fake edid or needing to.

First off, your newmode command is malformed. Try xrandr --newmode "1680x1050_60.00" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 noted the added quotes and the removal of the VGA1 reference.

This results in

Code:

xrandr --newmode "1680x1050_60.00" 147.14 1680 1784 1968 2256 1050 1051 1054 1087
xrandr: Failed to get size of gamma for output default

Originally posted by oshunluvr View Post

More worrisome is the lack of port detection, as xrandr is listing only "default." Maybe that's normal if you have only one port. Besides, if it's connected as DVI to DVI it wouldn't likely be "VGA1." Likely it would be something like "DVI-I-0" or similar. Most likely, your system is not using the correct driver - but you have to read your log file to tell which one is loaded. Try

Originally posted by oshunluvr View Post

cat /var/log/Xorg.0.log |grep river and look to see which video driver is loaded.

This is what I see:

cat /var/log/Xorg.0.log |grep river
[ 26.741] X.Org Video Driver: 15.0
[ 26.741] X.Org XInput driver : 20.0
[ 28.707] (==) Matched nvidia as autoconfigured driver 0
[ 28.707] (==) Matched nouveau as autoconfigured driver 1
[ 28.707] (==) Matched modesetting as autoconfigured driver 2
[ 28.707] (==) Matched fbdev as autoconfigured driver 3
[ 28.707] (==) Matched vesa as autoconfigured driver 4
[ 28.707] (==) Assigned the driver to the xf86ConfigLayout
[ 28.708] Module class: X.Org Video Driver
[ 28.716] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 28.731] Module class: X.Org Video Driver
[ 28.731] ABI class: X.Org Video Driver, version 15.0
[ 28.731] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 28.731] Module class: X.Org Video Driver
[ 28.731] ABI class: X.Org Video Driver, version 15.0
[ 28.732] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 28.732] Module class: X.Org Video Driver
[ 28.732] ABI class: X.Org Video Driver, version 15.0
[ 28.732] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 28.732] Module class: X.Org Video Driver
[ 28.732] ABI class: X.Org Video Driver, version 15.0
[ 28.732] (II) NVIDIA dlloader X Driver 340.93 Wed Aug 19 16:01:53 PDT 2015
[ 28.732] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 28.732] (II) NOUVEAU driver Date: Thu Nov 7 14:56:48 2013 +1000
[ 28.732] (II) NOUVEAU driver for NVIDIA chipset families :
[ 28.732] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 28.732] (II) FBDEV: driver for framebuffer: fbdev
[ 28.732] (II) VESA: driver for VESA chipsets: vesa
[ 28.739] ABI class: X.Org Video Driver, version 15.0
[ 28.739] ABI class: X.Org Video Driver, version 15.0
[ 28.740] ABI class: X.Org Video Driver, version 15.0
[ 28.740] ABI class: X.Org Video Driver, version 15.0
[ 28.924] ABI class: X.Org Video Driver, version 15.0
[ 29.419] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[ 29.532] Module class: X.Org XInput Driver
[ 29.532] ABI class: X.Org XInput driver, version 20.0

I see nouveau and nvidia in there. I have tried both drivers. Also tried reseating the card and cable, same result as before. The monitor is about 7 years old (received as father's day 208 present from wife to replace dual 19inch crts). Has no other problems except this one. Is it possible that it can no longer report its capabilities to the computer? Or is it more likely that the card is not receiving the info. Card is from 2012, so not old.

Originally posted by oshunluvr View Post

I don't understand you connecting kernel updates to the apt-get dist-upgrade command. If a kernel update isn't there, dist-upgrade won't install one. If a kernel upgrade is there, then it's usually a security update and you should be installing it. Your server should be able to withstand a reboot unattended or it's not much of a server. Are you installing the nvidia driver from nvidia instead of the one supplied by Kubuntu? If so, you're kinda on your own as almost no one does that anymore nor is there any reason to IMO. dkms does an outstanding job of adding the nvidia blob to the kernel automatically.

Installed dis-upgrade, no change. Tried in kernel 3.19 and 4.2.5 - same result

Installed nvidia driver thusly

sudo add-apt-repository ppa:graphics-drivers/ppasudo apt-get update && sudo apt-get install nvidia-340

I used 340 because it was the newest listed for the 8400GS on nvidia's site. Used the same ppa and commands to install the 355 driver on my other machine. It works fine. I really think this has something to do with the OS not knowing what the monitor can do. Just not sure how to remedy that

**oshunluvr** · Nov 04, 2015, 07:11 AM

After you did the --addmode did you check to see if xrandr accepted it? The gamma error relates to the missing edid, the xrandr stuff might still work.

It looks to me the problem is driver related. Not 340 vs. 355 but because you're getting four video drivers loading. To compare, here's my output from the log file:

Code:

stuart@office:~$ cat /var/log/Xorg.0.log |grep river[   454.683]    X.Org Video Driver: 19.0
[   454.683]    X.Org XInput driver : 21.0
[   454.690]    Module class: X.Org Video Driver
[   454.690] (II) NVIDIA dlloader X Driver  355.11  Wed Aug 26 15:38:55 PDT 2015
[   454.690] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   455.483] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[   455.699] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   455.726]    Module class: X.Org XInput Driver
[   455.726]    ABI class: X.Org XInput driver, version 21.0
[   455.726] (II) Using input driver 'evdev' for 'Power Button'
[   455.727] (II) Using input driver 'evdev' for 'Power Button'
[   455.728] (II) No input driver specified, ignoring this device.
[   455.729] (II) No input driver specified, ignoring this device.
[   455.729] (II) No input driver specified, ignoring this device.
[   455.729] (II) No input driver specified, ignoring this device.
[   455.729] (II) No input driver specified, ignoring this device.
[   455.730] (II) No input driver specified, ignoring this device.
[   455.730] (II) No input driver specified, ignoring this device.
[   455.730] (II) No input driver specified, ignoring this device.
[   455.731] (II) No input driver specified, ignoring this device.
[   455.731] (II) No input driver specified, ignoring this device.
[   455.731] (II) Using input driver 'evdev' for 'HP HP Wireless Keyboard Kit'
[   455.732] (II) Using input driver 'evdev' for 'HP HP Wireless Keyboard Kit'
[   455.734] (II) No input driver specified, ignoring this device.
[   455.734] (II) Using input driver 'evdev' for 'MOSART Semi. 2.4G Keyboard Mouse'
[   455.735] (II) Using input driver 'evdev' for 'MOSART Semi. 2.4G Keyboard Mouse'
[   455.736] (II) No input driver specified, ignoring this device.

I still have nouveau, fbdev, and vesa installed but they're not loading. Another oddity: mine shows Xorg Video Driver: 19.0 and yours shows 15.0 - weird.

Try this, create this file: /etc/X11/Xsession.d/65nvidia and put this in it:

Code:

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600GS"
EndSection

Then reboot and run the cat /Xorg... thing again.

**oshunluvr** · Nov 04, 2015, 08:35 AM

You should also have one or two files in /etc/modprobe.d with nvidia in the title - to blacklist nouveau.

**vsreeser** · Nov 04, 2015, 12:57 PM

Originally posted by oshunluvr View Post

You should also have one or two files in /etc/modprobe.d with nvidia in the title - to blacklist nouveau.

Oddly enough, I don't. Maybe I need to make them. Any tips, or howto links?

Creating /etc/X11/Xsession.d/65nvidia with the following had no effect

Code:

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8400GS"
EndSection

**vsreeser** · Nov 04, 2015, 01:31 PM

Followed instructions on http://askubuntu.com/questions/45122...-nvidia-driver
install failed. used sudo apt-get install nvidia-340. It installed ok, but still stuck. although now stuck at 1280x1024

cat /var/log/Xorg.0.log |grep river looks the same.

**oshunluvr** · Nov 04, 2015, 02:24 PM

Try creating the file /etc/modprobe.d/blacklist-nouveau.conf and put this in it:

blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

I have two files in mine that contain these lines: nvidia-graphics-drivers.conf and nvidia-355_hybrid.conf.

It would help a lot if you were more specific. Troubleshooting in the blind is nearly impossible.

What failed to install and why?
By "stuck at 1280x1024" you mean only that resolution is available?

Please run dkms status and post that too.

**vsreeser** · Nov 04, 2015, 02:41 PM

..

**vsreeser** · Nov 04, 2015, 02:51 PM

Originally posted by oshunluvr View Post

Try creating the file /etc/modprobe.d/blacklist-nouveau.conf and put this in it:

blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

I have two files in mine that contain these lines: nvidia-graphics-drivers.conf and nvidia-355_hybrid.conf.

It would help a lot if you were more specific. Troubleshooting in the blind is nearly impossible.

What failed to install and why?
By "stuck at 1280x1024" you mean only that resolution is available?

Please run dkms status and post that too.

1280x1024 is the highest res available. 640 800 and 1024 are also there. Just nothing higher

I have the follwing in /etc/modprobe.d

cat modeprobe
total 60
-rw-r--r-- 1 root root 2507 Feb 13 2013 alsa-base.conf
-rw-r--r-- 1 root root 325 Apr 10 2014 blacklist-ath_pci.conf
-rw-r--r-- 1 root root 1603 Apr 10 2014 blacklist.conf
-rw-r--r-- 1 root root 210 Apr 10 2014 blacklist-firewire.conf
-rw-r--r-- 1 root root 677 Apr 10 2014 blacklist-framebuffer.conf
-rw-r--r-- 1 root root 156 Feb 13 2013 blacklist-modem.conf
-rw-r--r-- 1 root root 126 Nov 4 14:00 blacklist-nouveau.conf
lrwxrwxrwx 1 root root 41 Oct 15 15:54 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r-- 1 root root 583 Apr 10 2014 blacklist-rare-network.conf
-rw-r--r-- 1 root root 1077 Apr 10 2014 blacklist-watchdog.conf
-rw-r--r-- 1 root root 127 Sep 30 10:55 dkms.conf
-rw-r--r-- 1 root root 456 Apr 14 2014 fbdev-blacklist.conf
-rw-r--r-- 1 root root 347 Apr 10 2014 iwlwifi.conf
-rw-r--r-- 1 root root 104 Apr 10 2014 mlx4.conf
-rw-r--r-- 1 root root 26 Nov 4 14:04 nouveau-kms.conf
lrwxrwxrwx 1 root root 49 Nov 4 14:15 nvidia-graphics-drivers.conf -> /etc/alternatives/x86_64-linux-gnu_nvidia_modconf

Contents of /etc/modprobe.d/blacklist-nouveau.conf

cat blacklist-nouveau.conf
blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

Contents of /etc/modprobe.d/blacklist-nvidia-graphics-drivers.conf

cat nvidia-graphics-drivers.conf
# This file was installed by nvidia-340
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

dkms status

dkms status
bbswitch, 0.7: added
nvidia-340, 340.93: added

**oshunluvr** · Nov 04, 2015, 03:32 PM

dkms status

dkms status
bbswitch, 0.7: added
nvidia-340, 340.93: added

Here's your problem. You are missing kernel headers so the nvidia driver isn't fully installed. Also, you don't need bbswitch unless you have an on-board Intel video along with your nvidia card. You can remove that if you want. For some reason, it is auto-installed with the nvidia drivers automatically. Open a terminal and enter this:

sudo apt-get install linux-headers-$(uname -r)

After the package installs, you should see a bunch of dkms activity and dksm status should report

Code:

[COLOR=#333333][FONT=monospace]nvidia-340, 340.93: installed[/FONT][/COLOR]

You'll need to reboot afterward.

**vsreeser** · Nov 05, 2015, 01:19 PM

sudo apt-get install linux-headers-$(uname -r) said nothing new installed. After reboot, the problem still exists
Do you think a fresh download and install of the newest (or any) stable kernel would help? Thinking back, this did start after updating to 4.2.5 I may have done something wrong there. kernel 3.19 is still on the system and it has the same problem now. Prior to update, I was using 1680x1050 res.

If needed, I can copy all data off to external 1Tb usb drive (soooo slow, but useful), and start over. Just a home server, so not critical.

Update: found missing esata card. Still slow backup, but not as bad

**oshunluvr** · Nov 05, 2015, 01:24 PM

Hmmm, your drivers should install automatically if you have the headers installed. Try:

sudo dkms autoinstall

report results...

Announcement

Stuck at 1024x768

Stuck at 1024x768

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment