Horrifingly distorted colors on display.

Problems and successes with specific brands/models of computer video hardware
Post Reply
Message
Author
TheNH813
Posts: 62
Joined: Wed 13 Nov 2013, 19:27

Horrifingly distorted colors on display.

#1 Post by TheNH813 »

The colors on my FujiPlus 19in LCD look like 256 color when it is clearly set to 24bit ona DVI connection. I have no idea why, using the same NVidia self extracting installer on Ubuntu with the same kernel version works perfectly, It works fine on Puppy Linux if I use a VGA cable, but given the high resolution of 1280x1024, DVI-D is what I want to use. Can someone explain why this is happening and what I need to change, I tried different bit depths, but that only made it worse. It does look much sharper then VGA now, but this is not really acceptable. Can someone tell me what options I need to change to get this working, that 15 foot DVI-D cable wasn't cheap LOL.
Last edited by TheNH813 on Sat 04 Apr 2015, 05:01, edited 4 times in total.

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#2 Post by Ted Dog »

if those are print screens and not photos of screens then its xorgwizard related. looks by the horrible color to be vesa safe mode, ie drivers for hardware is not setup right so defaults to lowest common mode.
Did you reboot at least twice? it takes a few reboots to overrite liveCD type logic. Try needed kernel strings to disable / enable the drivers needed.
This is a legacy issue between distros ran as liveCDs and those used to full install.

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#3 Post by Ted Dog »

opps now your images disappeared while typing reply.. that is a serous bad driver problem. :lol: based on what you once shown and my spotty short term memory it still looked like wrong driver. It can only get worse with photos.

TheNH813
Posts: 62
Joined: Wed 13 Nov 2013, 19:27

#4 Post by TheNH813 »

LOL You've got it all wrong, I deleted the images because they looked perfect.

Those images I posted looked perfect, this is what I saw:
Image

Here's how it's supposed to look:
Image

I am not using VESA, I stated I installed the NVidia driver self extractor. The same driver works fine on other Linux OSes, just not Precise Puppy. Precise Puppy is Ubuntu 12.04 based, yet it doe snto work, when it does on 12.04 (LiveCD). I installed the drivers on a LiveCD of Ubuntu 12.04 and without rebooting, it worked perfectly, I just had to unload nouveau and start NVidia. I am using a hard install on Puppy, so changes are immediate and permanent. Rebooting once, and even not at all was perfectly fine for other drivers I compiled and installed, including capture card, WiFi and Ethernet. I know what I'm doing when it comes to this stuff, so this is really puzzling me. I finally got a upgrade graphics card that uses the same driver, and bought a fancy double shielded cable, plus I'v had this install for half a year now. It's set up perfectly except for this. :( I tried completely reinstalling the driver to no affect before thsi new post.

The bottom picture is a screenshot (perfect), top is bad one (taken with camera).

Puppy Linux is my only OS right now, I'v compiled lots of stuff custom. I have installed over 3.5G of software, and it takes DAYS to download the sources and packages. Having to change OSes is not an option at this point unless absolute necessity. In fact, I would rather use analog video aka VGA (which is noticably less sharp) then digital DVI if this is unfixable.

Sorry if the picture is a bit blurry, but the colors are not washed out.
That is really how I see it, I hope this gives you an idea of how horrible it is. The analog VGA connections looks just fine, but I want the HD DVI Digital connection. That is currently very color distorted, yellow is pink, blue is green, red is purple. The NVidia X Server settings application that comes with the drivers reports it is currently running in 24 bit mode. Yeah right. It absolutely sucks LOL.

Well, I'l be pulling the video cable and restarting so I can see again. This page is pink and flickers gold when scrolling. Man that is hard on one's eyes haha, It's like being color blind.

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#5 Post by Ted Dog »

since you did get it to work elsewhere use that install and grab the resulting x.config files. Something is not right in the setting on the puppylinux side. Not a bunch of DVI people around to help. Remove all the x config files in puppylinux ( all even bak files and 0.conf ) All xorgwizard needs to be dumped. There is a command string to force it off. you will need to start X without it. ( once you find correct launching code for X you can place it in /etc/rc/local.rc for next reboot. ) Given no option to seccond guess what X settings are the only one given will be used ( the one copied from a linux that works )
If its 64bit use fatdog64 I see that the settings for DVI are included as an option for the screen controller ( allows multiple different type interfaces to be used at best resolution ) and it does not need manufacturer secret blob of 50megs to do it. you can set up DVI , HDMI, laptop and VGA to run however you want. With my laptop I can run 3 different screens at natural pixel type of each. And its After a running X is already started.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#6 Post by bigpup »

What version of Precise are you using?
There are several versions and they have different Linux kernels.

What is the specific Nvidia graphics hardware?
What specific Nvidia driver package did you install?
Did you get it from Nvidia web site and compiled it for the specific Precise Puppy?
Did you only install one Nvidia driver package?
Did you run Xorgwizard to select the Nvidia driver to use it?

Post the contents of /etc/X11/xorg.conf

If the driver package was not a pet package specifically made for the version of Precise you have.
You usually need to look for one or do this:

Example:
A version of Wary Puppy.
how to get Nvidia driver compiled for your version of Puppy.

Make sure you have about 200mb free space in your save file first..

1 Download the NVidia Linux package for your card from Nvidia web site.
For his it was :
Nvidia-Linux-x86-93.43.20-pkg1.run

(you can usually find the devx and kernel source in the Precise repository along with the iso file)

2 Download the devx for your system.
His is Wary 5.10 so wary_devx.501.sfs.

3 Download the kernel sources for your system.
His was kernel sources 2.6.32.28.sfs

4 Enable both sfs files in the bootmanager, and reboot..

5 After rebooting, and making sure both sfs files are enabled..
Drop out of X to the command prompt and run the installer..
For his I typed:
/mnt/home/Nvidia-Linux-x86-93.43.20-pkg1.run
Let the installer do its thing, and watch for any errors..
(If you have the wrong driver, which I did the first time around, the installer scans your card, and will tell you which package you need...)
When it is finished, reboot...
After rebooting, run xorgwizard, and choose nvidia..
Ta-da...
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

TheNH813
Posts: 62
Joined: Wed 13 Nov 2013, 19:27

#7 Post by TheNH813 »

@bigpup

I'm using the version of Precise with kernel 3.2.48, the non PAE version.

I have found that both my old and new GPUs have the same problem. They are a Geforce 3 Ti 200 and a Geforce 210, one AGP, one PCI (not PCIE).

For testing purposes between my last two posts, I have removed the new card, and plugged both into the old one. I disabled the driver for and Geforce 210 for now, as the issue is same with both. If I find the setting for one, it will be same for both. It's some obscure option for the color in my opinion. I may be wrong. I think I may be missing the right color profile or something.

I do not need a devx or kernel source, this is a hard install from a custom Puppy DVD I made. The main SFS already came with those combined into it.

I have tried recompiling the drivers from NVidia's site many times. I always select NVidia in xorgwizard, and the display looks the same. I can try again if you want. Do I need custom compile options or something?

The proprietary drivers work fine, even both versions and cards at once as long as I use VGA. I'm having problems with the color being way messed up over DVI-D, It's not the cable, as it works on a Ubuntu LiveCD. Maybe I'l stick that HDD with XP on it in to grab some info from GPU-Z and use a monitor identification tool I have in my windows tools stuff.

This is the display: http://www.newegg.com/Product/Product.a ... 6824168005
I got it from someone used, it's obviously not too new. I replaced some capacitors and resistors on the backlight board a year ago, but I don't think it has anything else wrong with it. Besides it works elsewhere.

I can provide any further info if necessary.

Yes, you are right, I may know a decent amount about Puppy and nearly every part of the GUI, but when it comes to configs and the customs scripts it uses, I am lost. I know a lot about general Linux stuff, just not the specifics for this OS. I would definitely like to learn more about the internals.

@Ted Dog

It would be nice to copy the config, but xorg runs in configless mode on Ubuntu based OSes for my hardware. It basically guesses it each time X starts, so no luck there. Is there some way to see what it's doing maybe?

Also, to use OpenGL and CUDA a manufacturer binary is pretty necessary. Nouveau does not provide this well, and VESA absolutely not at all. I cannot use opensource drivers for my setup.

I usually tend to use OSS as much as possible, but I know from experiences with this hardware on other OSes that this is not possible for the GPU drivers.

@both
Well, I'l be back in the morning, it's almost 3AM now,

As requested, Xorg.conf. It refused to let me attach it.

Code: Select all

#Special base config file used in Puppy Linux.

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
#    Load        "freetype"

# This loads xtrap extension, used by xrandr
#    Load       "xtrap"

# This loads the GLX module (if present). xorg 7.4/5 need explicit disable to disable...
#    Disable    "glx" #LOADGLX

# This loads dri module (if present). 7.4 loads it by default, have to disable...
#    Load       "dri" #LOADDRI
#    Disable "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font paths to be set
# **********************************************************************

Section "Files"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

    FontPath   "/usr/share/X11/fonts/misc/"
    FontPath   "/usr/share/X11/fonts/Type1/"
    FontPath   "/usr/share/X11/fonts/TTF/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...

    Option "RandR" "on"

# With this, Xorg won't talk to HAL to add evdev devices and you'll be back
# with the old Xorg behavior (pre-7.4)...

    Option "AutoAddDevices" "false"

# For no-Hal, kirk also suggests this...

#    Option "AllowMouseOpenFail" "true"

# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...

    Option "DontZap" "false"

EndSection

#everything past here is auto-generated by Puppy's Xorg Wizard...

Section "ServerLayout"
	Identifier "Default Layout"
	Screen "Screen0" 0 0
	InputDevice "Keyboard0" "CoreKeyboard"
	InputDevice "Mouse0" "CorePointer"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option      "XkbRules" "xorg"
	Option      "XkbModel" "pc102"
	Option      "XkbLayout" "us" #xkeymap0
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Device" "/dev/input/mice"
	Option	    "Protocol" "IMPS/2" #mouse0protocol
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	Option      "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
	#HorizSync    31-80
	VertRefresh  59-75
	#UseModes     "Modes0" #monitor0usemodes
	Option      "PreferredMode" "1280x1024"
EndSection

Section "Modes"
	Identifier "Modes0"
	#modes0modeline0
EndSection

Section "Device"
	Identifier  "card0"
	Driver      "nvidia" #card0driver
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth 24
	#Option         "metamodes" "1280x1024_60 +0+0" #METAMODES_0
	Subsection "Display"
		Depth       24
		Modes       "1280x1024"
	EndSubsection
EndSection

#PuppyHardwareProfile=NVidiaFP_988D
Section "ServerLayout"
	Identifier "Default Layout"
	Screen "Screen0" 0 0
	InputDevice "Keyboard0" "CoreKeyboard"
	InputDevice "Mouse0" "CorePointer"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option      "XkbRules" "xorg"
	Option      "XkbModel" "pc102"
	Option      "XkbLayout" "us" #xkeymap0
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Device" "/dev/input/mice"
	Option	    "Protocol" "IMPS/2" #mouse0protocol
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	Option      "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
	#HorizSync    31-80
	VertRefresh  59-75
	#UseModes     "Modes0" #monitor0usemodes
	Option      "PreferredMode" "1280x1024"
EndSection

Section "Modes"
	Identifier "Modes0"
	#modes0modeline0
EndSection

Section "Device"
	Identifier  "card0"
	Driver      "nvidia" #card0driver
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth 24
	#Option         "metamodes" "1280x1024_60 +0+0" #METAMODES_0
	Subsection "Display"
		Depth       24
		Modes       "1280x1024"
	EndSubsection
EndSection

#PuppyHardwareProfile=NVidiaFP_988D

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#8 Post by Ted Dog »

configless mode lol that is marketing talk. puppylinux is also configless that is the problem. BUT the end result of configless .... is a conf file passed to X. That is what you can use and defeat the configless mode in puppylinux by turning it off and wiping all other config files from X.

Its there in other configless systems as well find it and reuse it. :wink:

do not believe all terms used are actually done like you think. sometimes its exactly opposite or non-explanatory ( what is a metro interface anyway ? ) we should be like.Microsoft and just coin new phrases for our widgets and do hickeys. Also what language is the surface ( Microsofts laptop with removal plastic fake keypad ) ad being sung in? Sounds totally made up!
Well at least in linux we do not yet just make up product names out of any noun in the dictionary. :roll:

sorry rant over...

TheNH813
Posts: 62
Joined: Wed 13 Nov 2013, 19:27

#9 Post by TheNH813 »

Yeah, that configless stuff is wierd, there is no xorg.conf on my Ubuntu.
It must be temporarily generating one in ram from another file.

You know what, I think you're right, I can still use another working config. I'l just find another OS this runs on right and copy it's config file. I have a couple blank partitions for OS testing anyway, and their empty. A dated version of Linux Mint I have is a prime candidate here, it runs the same kernel and xorg versions.

I totally agree with your point on the random marketing terms, its stupid.
Anyone with a little understanding begins to wonder what they were on at the time. LOL

Well, wish me luck, I'l try to find a xorg.conf from another OS.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#10 Post by bigpup »

One thing to try.

In the program Nvidia X server settings->X Server Display Configuration
There is a button to have the settings save to X configuration file.
This should make the settings change the Xorg.conf to what is selected in the Nvidia X server settings program.

Reboot after you use this.

Nvidia X server settings has X sever color correction section.

Maybe something here will help.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

#11 Post by L18L »

Perhaps a look into /var/log/Xorg.0.log might also help.

TheNH813
Posts: 62
Joined: Wed 13 Nov 2013, 19:27

#12 Post by TheNH813 »

bigpup wrote:One thing to try.

In the program Nvidia X server settings->X Server Display Configuration
There is a button to have the settings save to X configuration file.
This should make the settings change the Xorg.conf to what is selected in the Nvidia X server settings program.

Reboot after you use this.

Nvidia X server settings has X sever color correction section.

Maybe something here will help.
YES!!! Thanks for the suggestion. That fixed it. The xorg.conf file looks nearly identical, only the order of a few things is rearranged. Well, if anyone else has this problem, just use the NVidia xorg config utility. The order of the card, display and screen sections was reversed. All the values were the same, but they were set in a different order.

I have no idea why it worked, but I'm fine with that.
I'm gonna spend a little while figuring out why now.
There reason for me to believe that it sets some config elsewhere too.
The amount of RAM that X uses dropped by over 20M, which is signifigant.
Not sure exactly what that configuration utility does, but it worked.
Why did I never think to try it in the first place LOL.

@L18L
Perhaps a look into /var/log/Xorg.0.log might also help."
Hm.... I looked at it, but nothing unusual. It was a odd config problem.

@Everyone
I will consider this solved, because it's working great now.
I can finally get a sharper and smoother picture, it makes a big difference.
The problem is resolved with either card, and they both work.

Thanks for helping me troubleshoot,
-TheNH813

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#13 Post by bigpup »

Good to hear it is now working!!

The Nvidia X server Settings program is designed to tweak the Nvidia drivers settings, so seems logical it would know what it is doing for Nvidia manufactures drivers.
Nvidia wrote the code for the program. :shock:

I think Xorgwizard is using a one size fits all Nvidia profile that is not too specific to the Nvidia driver you may be using. It generally works Ok for any Nvidia driver.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

Post Reply