Xorg 7.4 screwed up my colors

Hi everyone,
I've problems with colors in the new Xorg. The screen looks like it had just 8 colors instead of 24-bit palette. I've no clue what causes this, everything worked fine before the upgrade.
Here's my xorg.conf if this is of any use
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
# PS/2 Mouse not detected
# Serial Mouse not detected
InputDevice "USB Mouse" "CorePointer"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
#RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
Load "synaptics"
Load "bitstream"
Load "IA"
Load "xtsol"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us, pl"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "synaptics"
Option "Device" "/dev/psaux"
Option "SendCoreEvents" "true"
Option "Protocol" "auto-dev"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
Option "HorizScrollDelta" "0"
EndSection
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "sis"
VendorName "All"
BoardName "All"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "sis"
VendorName "Videocard vendor"
BoardName "SiS 660/661FX/M661FX/M661MX/741/741GX/M741/760/M760"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x800"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x800"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "LCD Panel 1280x800"
HorizSync 31.5 - 90.0
VertRefresh 60.0 - 60.0
Option "dpms"
EndSection
Section "DRI"
Mode 0666
EndSection
Thanks in advance,
Przemek

Well, here's the output for warnings
(WW) The directory "/usr/share/fonts/PEX" does not exist.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
(WW) The directory "/usr/share/fonts/ttf/western" does not exist.
(WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
(WW) The directory "/usr/share/fonts/truetype" does not exist.
(WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
(WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
(WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
(WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
(WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) Warning, couldn't open module type1
(WW) Warning, couldn't open module record
(WW) Warning, couldn't open module bitstream
(WW) Warning, couldn't open module ia
(WW) Warning, couldn't open module xtsol
(WW) Falling back to old probe method for sis
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:0:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:1:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:1) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:5) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:6) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:7) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:1) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:2) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:4:0) found
(WW) SIS(0): Could not find/read video BIOS
(WW) SynPS/2 Synaptics TouchPad can't grab event device, errno=16
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) SynPS/2 Synaptics TouchPad can't grab event device, errno=16
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) SynPS/2 Synaptics TouchPad can't grab event device, errno=16
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) SynPS/2 Synaptics TouchPad can't grab event device, errno=16
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) SynPS/2 Synaptics TouchPad can't grab event device, errno=16
and for errors
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "record" (module does not exist, 0)
(EE) Failed to load module "bitstream" (module does not exist, 0)
(EE) Failed to load module "ia" (module does not exist, 0)
(EE) Failed to load module "xtsol" (module does not exist, 0)
It seems that some modules don't load. Besides, I've no clue what's the issue with the old probe method for sis.
Seems like here's the same problem
http://forum.ubuntu-fr.org/viewtopic.php?id=262473
Last edited by CoolGenie (2008-12-05 19:11:33)

Similar Messages

[Solved] Xorg 1.5 screwed up my NVIDIA

Hi,
Today I did a pacman -Syu and I got the newest NVIDIA driver installed and the newest Xorg. Everything broke. Well not exactly everything. But my settings are all screwed up. For a start my screen refuses to load at the normal resolution (1680x1050). I got a default 1024x860 (or whatever it is). Also my colour depth is 16. And regardless of any changes I make in NVIDIA settings manager the changes never stick. Also my compiz-fusion is totally screwed up. When it starts up my screen goes completely white. I have to blindly alt+F2 and run kwin to be able to do anything.
Also my fonts are really small.
Here is my xorg.conf:
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
# RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
# FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
# Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
# Load "type1"
Load "freetype"
# Load "record"
# Load "synaptics"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "sv-latin1"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 32
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
#Section "DRI"
# Mode 0666
#EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
This is what my Xorg.0.log says:
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH i686
Current Operating System: Linux myhost 2.6.27-ARCH #1 SMP PREEMPT Fri Nov 28 10:56:24 UTC 2008 i686
Build Date: 09 November 2008 07:16:27PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 1 21:55:19 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Xorg Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "PS/2 Mouse"
(**) Option "AutoAddDevices" "False"
(**) Not automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/PEX" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
(WW) The directory "/usr/share/fonts/ttf/western" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
Entry deleted from font path.
(==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
(**) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/misc,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/100dpi,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81d66e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0@1:0:0) nVidia Corporation GeForce 8800 GT rev 162, Mem @ 0xfa000000/0, 0xe0000000/0, 0xf8000000/0, I/O @ 0x0000ac00/0, BIOS @ 0x????????/131072
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 177.82 Tue Nov 4 14:03:48 PST 2008
(II) Loading extension GLX
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) NVIDIA dlloader X Driver 177.82 Tue Nov 4 13:42:45 PST 2008
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 16, (--) framebuffer bpp 16
(==) NVIDIA(0): RGB weight 565
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 8800 GT (G92) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 62.92.12.00.05
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8800 GT at PCI:1:0:0:
(--) NVIDIA(0): Samsung SyncMaster (DFP-1)
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1024x768"
(II) NVIDIA(0): "800x600"
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(--) NVIDIA(0): DPI set to (55, 65); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "1024x768"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms" "true"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "sv-latin1"
(**) Keyboard0: XkbLayout: "sv-latin1"
(WW) Option "XkbVariant" requires an string value
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "Protocol" "auto"
(**) Option "Device" "/dev/psaux"
(II) PS/2 Mouse: Setting mouse protocol to "ExplorerPS/2"
(**) PS/2 Mouse: Device: "/dev/psaux"
(**) PS/2 Mouse: Protocol: "auto"
(**) Option "SendCoreEvents" "true"
(**) Option "CorePointer"
(**) PS/2 Mouse: always reports core events
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "true"
(**) Option "Emulate3Timeout" "70"
(**) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 70
(**) Option "ZAxisMapping" "4 5"
(**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5
(**) PS/2 Mouse: Buttons: 9
(**) PS/2 Mouse: Sensitivity: 1
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (PS/2 Mouse)
(II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE)
(II) PS/2 Mouse: Setting mouse protocol to "ExplorerPS/2"
(II) PS/2 Mouse: ps2EnableDataReporting: succeeded
(II) config/hal: Adding input device ImExPS/2 Logitech Explorer Mouse
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Macintosh mouse button emulation
(EE) config/hal: NewInputDeviceRequest failed
(II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select@1680x1050+0+0"
Any help would be much appreciated!
BFC
Last edited by BlueFightingCat (2008-12-02 16:41:01)

fLuXx wrote:Ok, so i tried, but it didn't work. All works but the fonts - they're messed up pretty bad. I can't even read what I'm typing right now. Here are some screenshots (just so you know - it gets even worse than that):
http://img254.imageshack.us/my.php?image=fluki1qu4.png
http://img254.imageshack.us/my.php?image=fluki2ax1.png
hmmm, I have exactly the same problem and I also use the nvidia-96xx.
I noticed that I only get the scrambled text for the lines beyond 20 lines...so if I rescale the height of my window to 20 lines I never get scrambled text and and when I change the height of the window larger then 20 lines, only the 20+ lines get scrambled.
Last edited by Bob Day (2008-12-02 18:05:24)

Xorg 1.5rc6 screws up urxvt in xmonad

I have the testing repository enabled and i have an nVidia card so i upgraded my xorg-server, but when I restarted X and opened up an instance of urxvt it came out all funny, it isn't tiled and it doesn't get focus, but i can type in it. Does anyone have an idea
i tried recompiling xmonad and urxvt but that didn't work.
Last edited by Vintendo (2008-09-03 15:28:43)

Set urxvt borderless through your WM. Certainly openbox can do it. Here's some discussion I had about this topic on the openbox mailing list:
http://comments.gmane.org/gmane.comp.wi … enbox/3947

IWeb 08 screws my photos color profile

Anyone has this problem with the new iWeb 08?
I installed the new version, ran it without any problems, did some rearranging of my site, created a new page etc.. And then published the whole site all over again.
But now, all my images are tagged with the sRGB profile instead of the profile that was in the images.. now all my images have become very saturated and dark. The thumbnails are fine, but when you click in to see the photos in slideshow or not, the images are loaded and it looks horrible.
I've went into my iDisk to check the images and found that all my photos are tagged with the sRGB profile instead of my normal AdobeRGB profile or Nikon sRGB profile or no profile...
ARGH!!!!

iWEB 08 is a fully color confused application, whilst iPhoto is only partly color confused.
The following applies when dragging images from iPhoto library, with the "Optimize Images on Import" option on. According to the manual, this option only changes the size, but I would not be surprised if it changes something else also. Then after, exporting from iWEB to files on the hard drive.
Having spent 8 hours analyzing the problem, I am beginning to understand what is happening but certainly not WHY???
iWEB appear to convert the images 2 times (when importing and when exporting I wonder), both times incorrectly, and to top it off, it exports images without a color profile BUT with the EXIF data of the original, which at this point is incorrect. HOWEVER, it appears that thumbnails are only converted incorrectly once, adding to the confusion.
Before going into some remedies let me answer the question: What color space etc. is "correct" for the WEB?
There are three rules to publishing photos on the WEB (files for download is a different story):
a) Image, including thumbnails should be in sRGB color space (Otherwise it will NOT display correctly on MicroSoft systems, where browsers happily ignores color profiles and sRGB is ASSUMED for all images)
b) There should be an sRGB color profile in the image file, including thumbnails (Otherwise it will NOT display correctly on MacOS, where browsers assume AppleRGB, but will happily adjust to any color profile)
c) Discard unnecessary information in the file to reduce size, such as EXIF information, thumbnails etc (optional rule)
Having said that, you may ask yourself, who do that? Well to tell the truth, not many. A quick check on Apples website reveals that there is a mix of color "strategies". For instance, the pictures demonstrating the cool features of iLife08, appear to be in sRGB but without color profile. Thus, they will be displayed correctly on a MicroSoft system but not on a Mac.
Well, back to iWEB - To try to fix the color problem, do one or both of the following:
1) Keep calling Apple Cupertino until they fix the problem (really, I am not joking, I am tired)
2) Convert images after they have been exported. This seems to work also, almost. However, converting a pictures color space is not exactly reversible, thus result is not perfect. Use for instance Photoshop CS1 or later (make sure color settings is such that there are no conversions when you open files and use the colorimetric conversion option in advanced settings) and:
a) Open picture
b) Assign AppleRGB profile
c) Convert to sRGB
d) Assign the original profile (usually sRGB or AdobeRGB or the cameras RGB)
e) Convert to sRGB
f) Save (with option: include color profile)
File is now about 2 times the original
g) Open graphics converter
h) Choose convert...
i) Choose file(s), hold Cmd-key and choose remove resources (which does not remove the color profile)
File is now ok for publishing on the WEB
TIP, if it seems like a daunting task to manually convert all of the exported images (and do not forget the thumbnails), make an Action-script in Photoshop, then use the Batch feature with sub-folders etc .... . Also the graphics converter operation can be applied to include subfolders. I did this, and it works ok, but be sure to only convert YOUR images, not the other files in the structure. I also applied the same conversion to the thumbnails to simpify things and it turned out not to bad. (Can somebody make an AppleScript maybe?)
And finally, how about iPhoto? Well, iPhoto will always export images in the color space and profile it happens to be imported with, unless you edit the image in some external editor. If you are WEB publishing "lucky", the image will come out in sRGB color space and with an sRGB color profile. And yes, I have also tried various iPhoto-WEB export plug-ins, and they also all do it wrong.
If you read all of this, you are a patient person. Thanks for the attention.
Tomas Jonsson, Genicore Embedded Systems AB

[Solvedish] Can color depth be changed in X with no xorg.conf file?

I have a laptop that's working perfectly with no xorg.conf file except for the color depth is at 16 and I want it at 24. Can color depth be changed in X with no xorg.conf file? (I already tried the amazing three line xorg.conf file to no avail.)
Last edited by skottish (2008-03-09 03:15:11)

Won't work on a running X session, and has the same effect as the aforementioned xorg.conf file if run before starting X.
I may just have to make a new xorg.conf file. The last one decided it hated some upgrade I made and started wreaking havoc all over my system. Crashes and lockups and flickers galore!
--EDIT--
It turns out that the xf86-video-intel driver was my problem all along. I reverted to the i810 driver and my xorg file works again (it has more than three lines).
Last edited by skottish (2008-03-09 03:16:45)

Photoshop screws up colors in my jpgs

So, I've been working in Illustrator and then rasterizing my file in Photoshop so I can save as a jpg, and for 2 drafts it went off fine, but of course the last and final draft it screws up the colors in the jpg completely, it looks fine when viewed in Ps but when I go to send it out and it's a hot mess... what is happening?

maybe you deselected the ICC Profile checkbox when saving the last jpg.
Edit: no wait, scratch that, make sure that the image is in sRGB before you save it. Best way to do this is to save it using File->Save for Web & Devices (unless you are working with 20mb+ files)

A different take on the "Save For Web" color shift issue...

Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
Nothing new here.
Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
Anyone got a decent solution for this?

Sorry, I think I'm being unclear. This has nothing to do with individual monitor profiles. In Proof Setup, "Monitor RGB" amounts to turning off ALL color management, and simply letting the monitor do what it will. It is what the vast majority of web browsers do (even if the operating system provides color management, the browsers don't take advantage of it), so that is what you need to consider for images that will be viewed on a web browser. If you convert your image to sRGB, select Monitor RGB in Proof Set up, and turn on Proof Colors, you will see the image as it would appear on a web browser (after you save it as a jpg or use "Save For Web/Devices" to save it as a jpg).   Since almost everyone is running different uncalibrated monitors, there will be lots of variation in how it will look to them, so precise control of the color is unimportant.
That said, I would expect the color on a calibrated monitor (such as the one I use when editing) to be reasonably close to the colors I am seeing while editing in PS. To the extent a monitor deviates from "calibrated", those colors will vary, but a good monitor should show good colors.   Unfortunately, this is NOT the case, as my previous post shows. The colors produced by the steps above are oversaturated and significantly shifted in hue. There is, to my mind, anyway, no reason for this. Adobe clearly knows what the mapping is between the colors as it displays them in PS and the un-controlled "Monitor RGB" -- that is, it is the color map they are using during normal editing display. If they were to reverse-apply that map prior to saving it as a jpg, then the image would appear on a browser on that same (presumably calibrated) monitor very similar to what you set up when editing. Anyone else viewing the image on a web browser with a calibrated monitor would also see good colors. To the extent other viewers' monitors are out of calibration, their colors will suck, but there's nothing you can do about that.
I guess in some sense I AM "asking for a Color-Mamangement-solution for a "non-Color-Management-situation", but specifically I'm asking for PS Color Management to do the best it can for non-Color-Managed situations that we all face every day.
Does that make more sense?

Looking for a better solution to the "Save for web" color shift issue

Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
Nothing new here.
Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
Anyone know of such a beast? I would gladly pay for a plug-in that really works and fixes the problem.
And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
Anyone got a decent solution for this?

Chris
I spent all day Googling and doing side by side comparisons of my old and new systems.
My display is a Dell U2410. It has several presets, including sRGB and Adobe RGB. I've been using sRGB.
On my OLD system, (Win XP, PsCS2, DwCS4) there seems to be no distinction between color managed and non color managed apps, even on this wide gamut display. I could capture (digital camera) in Adobe RGB, open and edit in PsCS2, save as .psd, convert to CMYK for print, or convert to sRGB for SFW. All images looked identical and they printed and displayed perfectly. I thought this was normal, and seemed logical. This also seems to be the source of my incorrect assumptions. I was trying to get my new machine to behave like my old one.
So I get this new machine (Windows 7, PsCS5, DwCS5) and now (still in sRGB display mode) all color managed apps appear de-saturated. Non color managed apps are OK. If I switch the display to Adobe RGB, color managed apps are OK, but non color managed apps are way too saturated. From my investigation, I believe this is normal behavior on a wide gamut display. I've tried changing the Control Panel > Display > Screen Resolution > Advanced settings > Color Management options, but to no avail. Either I'm missing something, or Windows 7 is doing color management differently.
It seems my only option now is to use Adobe RGB display setting for Ps, etc. and switch to sRGB for Dw and non color managed apps. Or, have 2 separate files for print and web. I've Googled 'til my eyes are numb and still not sure I'm getting this. Any enlightenment would be greatly appreciated.
Finally, I don't see an edit function here, so I can't remove my previous incorrect reply. Moderator, please feel free to do so.
Thanks

Firefox 29 screw up - Please consider USERS How to fix this???

I often get fed up with firefox, the only reason I stay with it is because of the 3rd party plugins, but this is a step too far.
I am so seriously pissed off with Mozilla Firefox, not just because of the new design but the complete lack of respect for your users.
I got a message saying that there was an important security update, it did NOT NOT NOT warn me that it intended to install a completely redesigned application.
Have you guys heard of change control management?
I am in the middle of working and I spend 15 hours a day online, now i have to figure out this AWFUL user interface.
I guess this is what you get when you have a bunch of amateurs developing software.
So what was it, did not one person in Mozilla figure NOT out that you need to tell users that an upgrade includes a serious change in UI or worse still did you know and think FFF..orget them we will just do it and tell them it is a security update.
Rather than creating this terrible user interface you should have focused on the biggest problem with Firefox MEMORY and CPU usage with the ability of users to figure out which tab is using memory or CPU,
If I had wanted a Google Chrome clone I would have installed Google Chrome, but I hate the Chrome interface. Do you not know that Google are the worst company in the world at designing a UI, their email is rubbish, the new adwords Keyword Planner should be used in schools and colleges as a "how NOT to design software"
What pisses me off is that you have the arrogance to think that you can just bulldoze over your userbase. If I were local I would come to your office ask which bright spark was in charge of this and punch them in the face.
I have seen others ask how to roll back and again in your ignorance you make pathetic excuses and lock the question, as you did with the guy here:
https://support.mozilla.org/en-US/questions/997424
well if you do that with me I will raise this on every blog related to Firefox. I wonder if there is any interest in creating a fork in the development?
I do not want to have to install an old version, I have a lot invested in my Firefox user interface which has been completely screwed up by this update. In addition to this I can't move the address bar and put it next to the menu and I can't move the tabs below the menus and toolbars.
You have also screwed up my colorful tabs which I need because of sight issues.
THIS IS MY DESKTOP do not DICTATE how I layout my screen!!
To call you complete F'ing Morons would not be enough!
Now if I roll back I am going to be facing nagware and security risks.
In future can you PLEASE respect your users by doing the following:
1. Do NOT install UI changes without informing the user and giving them a choice
2. ALWAYS include a feature to stick with the old UI
3. Allow users to stick with the old UI and still get REAL security updates.
I am so angry with you right now!

The attitude of the developers - not to mention the forum moderators beggars belief! How do we users get the Firefox we want - rather than what arrogent developers deem?
Moses and Tyler are flat out rude! You're not helping people. Telling us to use Chrome if we don't like your new Firefox? FF29 IS Chrome!
You're on the down, Firefox. Listen to the users or your market share is gone.

IWeb 09 color output messed up

Hi,
I have an iWeb site set up so that an iFrame photo gallery from another site is embedded inside my iweb page. Everything worked beautifully in iweb08. I have set up the embedded gallery so that the background colors are the same as the iweb page (333333) and it blends perfectly. Seems simple enough. web standard colors are web standard colors.
I have just updated my sites to iWeb09 and everything looks great *within iWeb*. iWeb connects to the internet and the preview loads the embedded website and it looks identical to my iWeb08 site. BUT when I publish this site and view it (firefox/safari - windows and mac) the iweb-created site background suddenly appears much lighter (about 555555) than the embedded iframe gallery (333333).
I notice that in the new iweb09 css file, colors are no longer displayed as HTML, but instead the RGB "equivalents". This seems to be the only difference between my old iweb08 css and the new iweb09 css. So I simply replaced the new with the old...Same color problems. *What am I missing?* *What could be corrupting the color output in iWeb 09??* This is really annoying and for now I should probably just revert to iweb08 on my external backup drive. I guess I'll also pick apart all of iweb09's output files to try to find the problem html or css.
Why Apple? Why?????

OK, so I read that support note several times from Apple and figured out how to use it as a workaround. In my case, I needed a background that was the same color as parts of the foreground elements for a seamless blend (a nav bar on the left, done with HTML snippit). It was driving me absolutely nuts trying to get a simple accurate RGB value generated from iWeb. RGB... hmmmmmm. Mucked with my snapshot color HMMMMMM....
Ok, so RGB color spaces are commonly embedded in images, etc. I thought, well, what if iWeb is using that at the time of the assignment of a color to a object (like my stretchable square) and pre-screwing-up the color in the definition of the square? To work around, I would have to do the gamma hokie pokie so my RGB color space was something that iWeb would be happy with... generate the square of color, then set the color space back. In theory, this should give me a proper value for the square's color on output (matches what everyone sees in the &^#% browser). Badda boom, badda bing, it worked:
Steps:
1) set your monitor color space to sRGB IEC61966 in the System Prefs under Display, Color tab
2) generate your evil iWeb color square of death using the Color Picker and the magnifying glass to select the onscreen color you want to match.
3) set your monitor back to the *normal* setting (Apple Cinema Display for example)
When you want to use that color, copy that square and paste it. It will carry the proper RGB around with it (or at least it is working for me right now...)
Now, if anyone else uses this approach with a color different than Navy blue, please indicate and also indicate of the grey dog ear was on your problem color when this all started.

Xorg config wireless keyboard

Anybody configaration so that my box will recognise a wireless key board.
Also is there a default xorg.config I screwed up the name for xorg.config and now it lets me pick a reselution 1680x1050 ??

To install my wireless keyboard all I had to do was plug in the usb thingy (it had the normal thingies but using them didn't work)
You can create a new xorg.conf using xorgconfig

Why when I open my raw files into lightroom, colors are different from my camera's preview?

Ciao,
I have a problem... maybe this can be a stupid question but anyway.. I would like to know the reason why when I open a raw image in lightroom, for a second I see the right colors/tone/contrast that i see when i look at the same images on my camera and soon after the word "Loading" I see the raw files with different colors.
Why this happens???
Before "Loading" and --> after
Thank you so much

Hey Giuseppe
I have a similar problem but the cause may be different from yours. I shoot a Canon 6D and as far as I know no one with the 5D MKIII has my issue, but maybe you could look into it.
Canon's Adobe Camera Raw in Photoshop CC, as well as Lightroom CC, is automatically down converting my CR2 RAW files from 14 bit color depth to 8 bit color depth. This is screwing up my colors, contrast, gradients, etc quite a bit when trying to process RAW files in Photoshop CC and Lightroom CC.
You can read my thread here:
Banding due to automatic downconverting of RAW files to 8 bit
You might want to check and see if your RAW files are actually being processed in 16 bit color depth. There is a possibility that they are being down converted automatically for some reason.
The bit depth in Lightroom for RAW files is supposed to be 16 bit but when opening my files it just converts it down.
Try downloading Canon's Digital Photo Professional 4
Canon U.S.A. : Consumer & Home Office : EOS 5D Mark III
Use that software to process a RAW photo and convert to a 16 bit TIFF. I know this software truly gives you a 16 bit depth image. Then compare the result side to side with what you're seeing in Lightroom.
If you are having this issue, I have not yet found a way to process RAW CR2 files in ACR or Lightroom and maintain 16 bit depth.
If you are batch processing to JPEGs it probably doesn't matter, but my issue is that it is down converting BEFORE exporting and thus any edits I do become much more destructive on my 8 bit image than they would if I was editing a 16 bit image. I have to be able to keep things in 16 bit up until the point they go to the printer.
Sorry, this may not help you at all, it looks like there could just be a difference in White Balance, but I figured I'd throw my two cents out there and maybe you could see if this is actually what is happening for you, and hopefully eventually Adobe could potentially fix this bug.

When I change my TIFFs to jpegs, the color and tone are changing as well [was: Need help please!]

When I change my TIFFs to jpegs, the color and tone are changing as well, any ideas as to what the problem could be?

You are screwing up the colors by not using color management or at least not keeping an eye what color space/ profiel your source files use anbd what happens when Safe for Web converts them. As a start, perhaps refer to this, then work your way through the Internet wide and far to learn about color management:
Common Photoshop Issues
Mylenium

How do I shut off Color Management

Hi everyone,
I am using Indesign cs3. My book printer needs Color Management shut off. Also I am having problems
making a Postscript file that I then need to run through Distiller. In the Postscript settings I can't save it to file.
Thank you
Jan

Rebekkah Angel wrote:
Edit>>>color settings>>>
and I can turn color management off in InDesign -
Am I mistaken?
This doesn't really turn off color management. It preserves all incoming numbers and interprets them as if they are in the current working space instead of reading any embedded profiles.
I suppose one could do that to satisfy the ridiuclous printer specification, but you'd be extremely foolish to do so. The printer's RIP has no idea what color settings you've used nor what your missing and mismatched profile policies might have been. It sees only the numbers you have in the PDF. Problems sometimes arise when ICC profiles are embedded in the PDF and the printer uses a differnt output space, resulting in color conversions in the RIP. First, the printer can no longer point to your file and say "these are the numbers you provided and that's what we printed" when they screw up the color, and second, 100% K can be converted to rich black which would be a nightmare, if not a complete disaster, under many circumstances.
What should be specified is that no profiles be embedded (and in fact that's what happens with PDF/X-1a compliant files, as well as with most of the other presets) so that all colors are presumed to be in the correct color space. This is not a problem if the correct color space is known and used as the desination during export. Badly presented specs, such as those at Lightning Source, and failure to provide adequate profile information to properly use color mangement is the problem, not the use of color management itself.

Color discrepancy with imported PSD between Motion and FCP

I've got a Motion project with an imported PSD file as a background element (the PSD was created in Photoshop CS2 for Windows, running under Parallels).
The PSD file consists of two overlapping curved shapes, one blue, one green (part of our corporate look). The colors (RGB) match our official guidelines.
I imported the Motion project to FCP and placed it on the timeline, on V1. In FCP, I then used a color generator to create a small blue rectangle which would serve as a border for a slightly smaller thumbnail image that would get overlaid later on. The rectangle is on V2. I used the exact same RGB values for it as I did in Photoshop for the curved shape.
Trouble is, the blue color in the shape that got imported into FCP inside the Motion project doesn't match the generated color.
See this screenshot, in FCP:
http://elamaton.no-ip.com/~jarkko/colordiscrepancymotion.png
Three blues: leftmost, the color generator resized to a small rectangle; on the center, the shape that I created in Photoshop and imported into a Motion project, dropped into FCP; rightmost, an instance of Photoshop CS2 running in a virtual WinXP in Parallels Desktop. You'll notice that the blues of the generator and Photoshop match, but the middle shape that travelled the CS2->Motion->FCP route is a different shade.
Narrowing it down further, I decided to import the PSD file directly into FCP (just to see if it'd match - it needs to go through Motion for the final product). Here's a screengrab of Canvas this time:
http://elamaton.no-ip.com/~jarkko/colordiscrepancy_motion2.png
Again, from left to right: the generated rectangle, the directly imported PSD, the PSD in the imported Motion project. The first two match, but something in Motion or the Photoshop->Motion route screws up the colors of the blue-green shape (as well as the Työterveyslaitos logo on the top left, also a PSD, in the same Motion project). The blue shade is also incorrect in the Motion canvas, pre-import to FCP.
What's going on here, and how can I fix things?
The project settings are PAL DV in both FCP and Motion. No rendering has been done, I'm importing the .motn into FCP as-is.
Any help is greatly appreciated, deadlines loom...

First, double-check that your PSD is in RGB, but I suspect it it or it wouldn't even work in FCP. I suspect a gamma issue moving between the apps:
http://docs.info.apple.com/article.html?artnum=93794
You might try setting the colorspace in FCP to RGB or adding a gamma filter in Motion to adjust.
Mark

Xorg 7.4 screwed up my colors

Similar Messages

Maybe you are looking for