ATI oss color space compressed in the dark shades of gray
With the arrival von linux 3.13 to [core] I switched from catalyst to the open source drivers, as they finally provide a sufficient performance. My only problem now is that the colorspace is compressed for gray values below 16 (that means every shade of gray having values of 0 to 16 look just black). That's only the case for my HDMI-output connected to my TV, which worked without problems with the catalyst drivers. Also, only the dark grays are compressed, the near-white grays show up correct.
In the wiki I found a xrandr-command "--set "Broadcast RGB" "Full"", which can be used with chips from Intel. Is there something similar for the open source ati drivers?
That's just outputting the options "load detection", "dither", "audio", "underscan vborder", "underscan hborder", "underscan" and "coherent" for both my monitor and TV - are these really all? Here's the full output:
$ xrandr -q --verbose
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
DisplayPort-0 connected 2560x1440+0+0 (0x59) normal (normal left inverted right x axis y axis) 597mm x 336mm
Identifier: 0x55
Timestamp: 2366135
Subpixel: horizontal rgb
Gamma: 1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC: 0
CRTCs: 0 1 2 3 4 5
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
EDID:
00ffffffffffff0010ac57a04c543930
34140104b53c22783a8e05ad4f33b026
0d5054a54b008100b300d100714fa940
818001010101565e00a0a0a029503020
350055502100001a000000ff00473630
365430434f3039544c0a000000fc0044
454c4c2055323731310a2020000000fd
0031561d711e000a202020202020012d
02031df1509005040302071601061112
1513141f20230d7f07830f0000023a80
1871382d40582c250055502100001e01
1d8018711c1620582c25005550210000
9e011d007251d01e206e285500555021
00001e8c0ad08a20e02d10103e960055
50210000180000000000000000000000
0000000000000000000000000000004b
dither: off
supported: off, on
audio: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
coherent: 1
range: (0, 1)
2560x1440 (0x59) 241.5MHz +HSync -VSync *current +preferred
h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 88.8KHz
v: height 1440 start 1443 end 1448 total 1481 clock 60.0Hz
1920x1200 (0x5a) 193.2MHz -HSync +VSync
h: width 1920 start 2056 end 2256 total 2592 skew 0 clock 74.6KHz
v: height 1200 start 1203 end 1209 total 1245 clock 59.9Hz
1920x1080 (0x5b) 148.5MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
v: height 1080 start 1082 end 1087 total 1125 clock 60.0Hz
1920x1080 (0x5c) 148.5MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz
1920x1080 (0x5d) 148.5MHz +HSync +VSync
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.2KHz
v: height 1080 start 1084 end 1089 total 1125 clock 50.0Hz
1920x1080 (0x5e) 148.4MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.4KHz
v: height 1080 start 1084 end 1089 total 1125 clock 59.9Hz
1920x1080i (0x5f) 74.2MHz +HSync +VSync Interlace
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.8KHz
v: height 1080 start 1084 end 1094 total 1125 clock 60.1Hz
1920x1080i (0x60) 74.2MHz +HSync +VSync Interlace
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.1KHz
v: height 1080 start 1084 end 1094 total 1125 clock 50.0Hz
1920x1080 (0x61) 74.2MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
1920x1080i (0x62) 74.2MHz +HSync +VSync Interlace
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.7KHz
v: height 1080 start 1084 end 1094 total 1125 clock 60.0Hz
1920x1080 (0x63) 74.2MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
1600x1200 (0x64) 162.0MHz +HSync +VSync
h: width 1600 start 1664 end 1856 total 2160 skew 0 clock 75.0KHz
v: height 1200 start 1201 end 1204 total 1250 clock 60.0Hz
1680x1050 (0x65) 146.2MHz -HSync +VSync
h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.3KHz
v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz
1280x1024 (0x66) 135.0MHz +HSync +VSync
h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 80.0KHz
v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz
1280x1024 (0x67) 108.0MHz +HSync +VSync
h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 64.0KHz
v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz
1280x800 (0x68) 83.5MHz +HSync -VSync
h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.7KHz
v: height 800 start 803 end 809 total 831 clock 59.8Hz
1152x864 (0x69) 108.0MHz +HSync +VSync
h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.5KHz
v: height 864 start 865 end 868 total 900 clock 75.0Hz
1280x720 (0x6a) 74.2MHz +HSync +VSync
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
v: height 720 start 725 end 730 total 750 clock 60.0Hz
1280x720 (0x6b) 74.2MHz +HSync +VSync
h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.5KHz
v: height 720 start 725 end 730 total 750 clock 50.0Hz
1280x720 (0x6c) 74.2MHz +HSync +VSync
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
v: height 720 start 725 end 730 total 750 clock 59.9Hz
1440x576i (0x6d) 27.0MHz -HSync -VSync Interlace
h: width 1440 start 1464 end 1590 total 1728 skew 0 clock 15.6KHz
v: height 576 start 580 end 586 total 625 clock 50.1Hz
1024x768 (0x6e) 78.8MHz +HSync +VSync
h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.1KHz
v: height 768 start 769 end 772 total 800 clock 75.1Hz
1024x768 (0x6f) 65.0MHz -HSync -VSync
h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
v: height 768 start 771 end 777 total 806 clock 60.0Hz
1440x480i (0x70) 27.0MHz -HSync -VSync Interlace
h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.8KHz
v: height 480 start 488 end 494 total 525 clock 60.1Hz
1440x480i (0x71) 27.0MHz -HSync -VSync Interlace
h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.7KHz
v: height 480 start 488 end 494 total 525 clock 60.1Hz
800x600 (0x72) 49.5MHz +HSync +VSync
h: width 800 start 816 end 896 total 1056 skew 0 clock 46.9KHz
v: height 600 start 601 end 604 total 625 clock 75.0Hz
800x600 (0x73) 40.0MHz +HSync +VSync
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
v: height 600 start 601 end 605 total 628 clock 60.3Hz
720x576 (0x74) 27.0MHz -HSync -VSync
h: width 720 start 732 end 796 total 864 skew 0 clock 31.2KHz
v: height 576 start 581 end 586 total 625 clock 50.0Hz
720x480 (0x75) 27.0MHz -HSync -VSync
h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
v: height 480 start 489 end 495 total 525 clock 60.0Hz
720x480 (0x76) 27.0MHz -HSync -VSync
h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
v: height 480 start 489 end 495 total 525 clock 59.9Hz
640x480 (0x77) 31.5MHz -HSync -VSync
h: width 640 start 656 end 720 total 840 skew 0 clock 37.5KHz
v: height 480 start 481 end 484 total 500 clock 75.0Hz
640x480 (0x78) 25.2MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
v: height 480 start 490 end 492 total 525 clock 60.0Hz
640x480 (0x79) 25.2MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
v: height 480 start 490 end 492 total 525 clock 59.9Hz
720x400 (0x7a) 28.3MHz -HSync +VSync
h: width 720 start 738 end 846 total 900 skew 0 clock 31.5KHz
v: height 400 start 412 end 414 total 449 clock 70.1Hz
HDMI-0 connected (normal left inverted right x axis y axis)
Identifier: 0x56
Timestamp: 2366135
Subpixel: horizontal rgb
Clones:
CRTCs: 0 1 2 3 4 5
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
EDID:
00ffffffffffff0034a9a6a001010101
00140103800000780adaffa3584aa229
17494b00000001010101010101010101
010101010101023a80d072382d40102c
4580ba882100001e023a801871382d40
582c4500ba882100001e000000fc0050
616e61736f6e69632d54560a000000fd
00173d0f440f000a20202020202001d1
02032672509f90140520130412031102
16071506012309070168030c001000b8
260fe3051f01011d80d0721c1620102c
2580ba882100009e011d8018711c1620
582c2500ba882100009e011d00bc52d0
1e20b8285540ba882100001e011d0072
51d01e206e285500ba882100001e0000
000000000000000000000000000000c1
dither: off
supported: off, on
audio: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
coherent: 1
range: (0, 1)
1920x1080 (0x5d) 148.5MHz +HSync +VSync +preferred
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.2KHz
v: height 1080 start 1084 end 1089 total 1125 clock 50.0Hz
1920x1080 (0x5c) 148.5MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz
1920x1080 (0x5e) 148.4MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.4KHz
v: height 1080 start 1084 end 1089 total 1125 clock 59.9Hz
1920x1080i (0x5f) 74.2MHz +HSync +VSync Interlace
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.8KHz
v: height 1080 start 1084 end 1094 total 1125 clock 60.1Hz
1920x1080i (0x60) 74.2MHz +HSync +VSync Interlace
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.1KHz
v: height 1080 start 1084 end 1094 total 1125 clock 50.0Hz
1920x1080 (0x61) 74.2MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
1920x1080i (0x62) 74.2MHz +HSync +VSync Interlace
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.7KHz
v: height 1080 start 1084 end 1094 total 1125 clock 60.0Hz
1920x1080 (0x63) 74.2MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
1280x720 (0x6a) 74.2MHz +HSync +VSync
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
v: height 720 start 725 end 730 total 750 clock 60.0Hz
1280x720 (0x6b) 74.2MHz +HSync +VSync
h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.5KHz
v: height 720 start 725 end 730 total 750 clock 50.0Hz
1280x720 (0x6c) 74.2MHz +HSync +VSync
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
v: height 720 start 725 end 730 total 750 clock 59.9Hz
1440x576i (0x6d) 27.0MHz -HSync -VSync Interlace
h: width 1440 start 1464 end 1590 total 1728 skew 0 clock 15.6KHz
v: height 576 start 580 end 586 total 625 clock 50.1Hz
1440x480i (0x70) 27.0MHz -HSync -VSync Interlace
h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.8KHz
v: height 480 start 488 end 494 total 525 clock 60.1Hz
1440x480i (0x71) 27.0MHz -HSync -VSync Interlace
h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.7KHz
v: height 480 start 488 end 494 total 525 clock 60.1Hz
720x576 (0x74) 27.0MHz -HSync -VSync
h: width 720 start 732 end 796 total 864 skew 0 clock 31.2KHz
v: height 576 start 581 end 586 total 625 clock 50.0Hz
720x480 (0x75) 27.0MHz -HSync -VSync
h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
v: height 480 start 489 end 495 total 525 clock 60.0Hz
720x480 (0x76) 27.0MHz -HSync -VSync
h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
v: height 480 start 489 end 495 total 525 clock 59.9Hz
640x480 (0x78) 25.2MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
v: height 480 start 490 end 492 total 525 clock 60.0Hz
640x480 (0x79) 25.2MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
v: height 480 start 490 end 492 total 525 clock 59.9Hz
DVI-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x57
Timestamp: 2366135
Subpixel: horizontal rgb
Clones:
CRTCs: 0 1 2 3 4 5
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
load detection: 1
range: (0, 1)
dither: off
supported: off, on
audio: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
coherent: 1
range: (0, 1)
Just to emphasize this further: color space compression is not a problem on my monitor, but only on the TV. Setable options don't differ as you can see in the output above. Also, Xorg.0.log shows that the TV on HDMI-0 supports the RGB 4:4:4 encoding (just like the monitor does). Here's the full Xorg.0.log:
[ 2358.417]
X.Org X Server 1.15.0
Release Date: 2013-12-27
[ 2358.417] X Protocol Version 11, Revision 0
[ 2358.417] Build Operating System: Linux 3.12.5-1-ARCH x86_64
[ 2358.417] Current Operating System: Linux arch 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64
[ 2358.417] Kernel command line: root=PARTUUID=97f3bf97-014d-4333-8092-e190efc8bd3f rootfstype=ext4 ro add_efi_memmap initrd=\EFI\arch\initramfs-arch.img
[ 2358.417] Build Date: 09 January 2014 08:47:24AM
[ 2358.417]
[ 2358.417] Current version of pixman: 0.32.4
[ 2358.417] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2358.417] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2358.417] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 3 16:25:06 2014
[ 2358.417] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2358.417] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2358.417] (==) No Layout section. Using the first Screen section.
[ 2358.417] (==) No screen section available. Using defaults.
[ 2358.417] (**) |-->Screen "Default Screen Section" (0)
[ 2358.417] (**) | |-->Monitor "<default monitor>"
[ 2358.417] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2358.417] (==) Automatically adding devices
[ 2358.417] (==) Automatically enabling devices
[ 2358.417] (==) Automatically adding GPU devices
[ 2358.417] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2358.417] Entry deleted from font path.
[ 2358.417] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2358.417] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2358.417] Entry deleted from font path.
[ 2358.417] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2358.417] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 2358.417] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2358.417] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2358.417] (II) Loader magic: 0x804c80
[ 2358.417] (II) Module ABI versions:
[ 2358.417] X.Org ANSI C Emulation: 0.4
[ 2358.417] X.Org Video Driver: 15.0
[ 2358.417] X.Org XInput driver : 20.0
[ 2358.417] X.Org Server Extension : 8.0
[ 2358.417] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2358.418] (--) PCI:*(0:1:0:0) 1002:683f:1787:200b rev 0, Mem @ 0xe0000000/268435456, 0xf7e00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[ 2358.418] (II) Open ACPI successful (/var/run/acpid.socket)
[ 2358.418] Initializing built-in extension Generic Event Extension
[ 2358.418] Initializing built-in extension SHAPE
[ 2358.418] Initializing built-in extension MIT-SHM
[ 2358.418] Initializing built-in extension XInputExtension
[ 2358.418] Initializing built-in extension XTEST
[ 2358.418] Initializing built-in extension BIG-REQUESTS
[ 2358.418] Initializing built-in extension SYNC
[ 2358.418] Initializing built-in extension XKEYBOARD
[ 2358.418] Initializing built-in extension XC-MISC
[ 2358.418] Initializing built-in extension SECURITY
[ 2358.418] Initializing built-in extension XINERAMA
[ 2358.418] Initializing built-in extension XFIXES
[ 2358.418] Initializing built-in extension RENDER
[ 2358.418] Initializing built-in extension RANDR
[ 2358.418] Initializing built-in extension COMPOSITE
[ 2358.418] Initializing built-in extension DAMAGE
[ 2358.418] Initializing built-in extension MIT-SCREEN-SAVER
[ 2358.418] Initializing built-in extension DOUBLE-BUFFER
[ 2358.418] Initializing built-in extension RECORD
[ 2358.418] Initializing built-in extension DPMS
[ 2358.418] Initializing built-in extension Present
[ 2358.418] Initializing built-in extension DRI3
[ 2358.418] Initializing built-in extension X-Resource
[ 2358.418] Initializing built-in extension XVideo
[ 2358.418] Initializing built-in extension XVideo-MotionCompensation
[ 2358.418] Initializing built-in extension XFree86-VidModeExtension
[ 2358.418] Initializing built-in extension XFree86-DGA
[ 2358.418] Initializing built-in extension XFree86-DRI
[ 2358.419] Initializing built-in extension DRI2
[ 2358.419] (II) "glx" will be loaded by default.
[ 2358.419] (II) LoadModule: "dri2"
[ 2358.419] (II) Module "dri2" already built-in
[ 2358.419] (II) LoadModule: "glamoregl"
[ 2358.419] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 2358.420] (II) Module glamoregl: vendor="X.Org Foundation"
[ 2358.420] compiled for 1.15.0, module version = 0.6.0
[ 2358.420] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2358.420] (II) LoadModule: "glx"
[ 2358.420] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2358.420] (II) Module glx: vendor="X.Org Foundation"
[ 2358.420] compiled for 1.15.0, module version = 1.0.0
[ 2358.420] ABI class: X.Org Server Extension, version 8.0
[ 2358.420] (==) AIGLX enabled
[ 2358.420] Loading extension GLX
[ 2358.420] (==) Matched ati as autoconfigured driver 0
[ 2358.420] (==) Matched ati as autoconfigured driver 1
[ 2358.420] (==) Matched modesetting as autoconfigured driver 2
[ 2358.420] (==) Matched fbdev as autoconfigured driver 3
[ 2358.420] (==) Matched vesa as autoconfigured driver 4
[ 2358.420] (==) Assigned the driver to the xf86ConfigLayout
[ 2358.420] (II) LoadModule: "ati"
[ 2358.420] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 2358.420] (II) Module ati: vendor="X.Org Foundation"
[ 2358.420] compiled for 1.15.0, module version = 7.3.0
[ 2358.420] Module class: X.Org Video Driver
[ 2358.420] ABI class: X.Org Video Driver, version 15.0
[ 2358.420] (II) LoadModule: "radeon"
[ 2358.420] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 2358.420] (II) Module radeon: vendor="X.Org Foundation"
[ 2358.420] compiled for 1.15.0, module version = 7.3.0
[ 2358.420] Module class: X.Org Video Driver
[ 2358.420] ABI class: X.Org Video Driver, version 15.0
[ 2358.420] (II) LoadModule: "modesetting"
[ 2358.420] (WW) Warning, couldn't open module modesetting
[ 2358.420] (II) UnloadModule: "modesetting"
[ 2358.420] (II) Unloading modesetting
[ 2358.420] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2358.420] (II) LoadModule: "fbdev"
[ 2358.420] (WW) Warning, couldn't open module fbdev
[ 2358.420] (II) UnloadModule: "fbdev"
[ 2358.420] (II) Unloading fbdev
[ 2358.420] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2358.420] (II) LoadModule: "vesa"
[ 2358.420] (WW) Warning, couldn't open module vesa
[ 2358.420] (II) UnloadModule: "vesa"
[ 2358.420] (II) Unloading vesa
[ 2358.420] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 2358.420] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
ATI Mobility Radeon HD 4670, ATI FirePro M5750,
ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
SUMO, SUMO, SUMO2, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
ATI Radeon 4100, ATI Mobility Radeon HD 4200,
ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
AMD Radeon HD 6300 Series Graphics,
AMD Radeon HD 6200 Series Graphics, PALM, PALM, PALM, CYPRESS,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
AMD Firestream 9350, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
ATI Mobility Radeon HD 5800 Series,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
ATI Mobility Radeon Graphics, CEDAR,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
BARTS, BARTS, Mobility Radeon HD 6000 Series,
Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, HAINAN, HAINAN, HAINAN,
HAINAN, HAINAN, HAINAN, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE,
BONAIRE, BONAIRE, BONAIRE, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, KABINI, KABINI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
HAWAII, HAWAII, HAWAII, HAWAII
[ 2358.423] (++) using VT number 7
[ 2358.423] (II) [KMS] Kernel modesetting enabled.
[ 2358.423] (II) RADEON(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2358.423] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 2358.423] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 2358.423] (==) RADEON(0): Default visual is TrueColor
[ 2358.423] (==) RADEON(0): RGB weight 888
[ 2358.423] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 2358.423] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x683f)
[ 2358.423] (II) Loading sub module "dri2"
[ 2358.423] (II) LoadModule: "dri2"
[ 2358.423] (II) Module "dri2" already built-in
[ 2358.423] (II) Loading sub module "glamoregl"
[ 2358.423] (II) LoadModule: "glamoregl"
[ 2358.423] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 2358.423] (II) Module glamoregl: vendor="X.Org Foundation"
[ 2358.423] compiled for 1.15.0, module version = 0.6.0
[ 2358.423] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2358.423] (II) glamor: OpenGL accelerated X.org driver based.
[ 2358.452] (II) glamor: EGL version 1.4 (DRI2):
[ 2358.462] (II) RADEON(0): glamor detected, initialising EGL layer.
[ 2358.462] (II) RADEON(0): KMS Color Tiling: enabled
[ 2358.462] (II) RADEON(0): KMS Color Tiling 2D: enabled
[ 2358.462] (II) RADEON(0): KMS Pageflipping: enabled
[ 2358.462] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[ 2358.509] (II) RADEON(0): Output DisplayPort-0 has no monitor section
[ 2358.572] (II) RADEON(0): Output HDMI-0 has no monitor section
[ 2358.593] (II) RADEON(0): Output DVI-0 has no monitor section
[ 2358.644] (II) RADEON(0): EDID for output DisplayPort-0
[ 2358.644] (II) RADEON(0): Manufacturer: DEL Model: a057 Serial#: 809063500
[ 2358.644] (II) RADEON(0): Year: 2010 Week: 52
[ 2358.644] (II) RADEON(0): EDID Version: 1.4
[ 2358.644] (II) RADEON(0): Digital Display Input
[ 2358.644] (II) RADEON(0): 10 bits per channel
[ 2358.644] (II) RADEON(0): Digital interface is DisplayPort
[ 2358.644] (II) RADEON(0): Max Image Size [cm]: horiz.: 60 vert.: 34
[ 2358.644] (II) RADEON(0): Gamma: 2.20
[ 2358.644] (II) RADEON(0): DPMS capabilities: Off
[ 2358.644] (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
[ 2358.644] (II) RADEON(0): First detailed timing is preferred mode
[ 2358.644] (II) RADEON(0): Preferred mode is native pixel format and refresh rate
[ 2358.644] (II) RADEON(0): redX: 0.678 redY: 0.309 greenX: 0.202 greenY: 0.689
[ 2358.644] (II) RADEON(0): blueX: 0.148 blueY: 0.051 whiteX: 0.313 whiteY: 0.329
[ 2358.644] (II) RADEON(0): Supported established timings:
[ 2358.644] (II) RADEON(0): 720x400@70Hz
[ 2358.644] (II) RADEON(0): 640x480@60Hz
[ 2358.644] (II) RADEON(0): 640x480@75Hz
[ 2358.644] (II) RADEON(0): 800x600@60Hz
[ 2358.644] (II) RADEON(0): 800x600@75Hz
[ 2358.644] (II) RADEON(0): 1024x768@60Hz
[ 2358.644] (II) RADEON(0): 1024x768@75Hz
[ 2358.644] (II) RADEON(0): 1280x1024@75Hz
[ 2358.644] (II) RADEON(0): Manufacturer's mask: 0
[ 2358.644] (II) RADEON(0): Supported standard timings:
[ 2358.644] (II) RADEON(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 2358.644] (II) RADEON(0): #1: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 2358.644] (II) RADEON(0): #2: hsize: 1920 vsize 1200 refresh: 60 vid: 209
[ 2358.644] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 2358.644] (II) RADEON(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 2358.644] (II) RADEON(0): #5: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 2358.644] (II) RADEON(0): Supported detailed timing:
[ 2358.644] (II) RADEON(0): clock: 241.5 MHz Image Size: 597 x 336 mm
[ 2358.644] (II) RADEON(0): h_active: 2560 h_sync: 2608 h_sync_end 2640 h_blank_end 2720 h_border: 0
[ 2358.644] (II) RADEON(0): v_active: 1440 v_sync: 1443 v_sync_end 1448 v_blanking: 1481 v_border: 0
[ 2358.644] (II) RADEON(0): Serial No: G606T0CO09TL
[ 2358.644] (II) RADEON(0): Monitor name: DELL U2711
[ 2358.644] (II) RADEON(0): Ranges: V min: 49 V max: 86 Hz, H min: 29 H max: 113 kHz, PixClock max 305 MHz
[ 2358.644] (II) RADEON(0): Supported detailed timing:
[ 2358.644] (II) RADEON(0): clock: 148.5 MHz Image Size: 597 x 336 mm
[ 2358.644] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 2358.644] (II) RADEON(0): v_active: 1080 v_sync: 1082 v_sync_end 1087 v_blanking: 1125 v_border: 0
[ 2358.644] (II) RADEON(0): Supported detailed timing:
[ 2358.644] (II) RADEON(0): clock: 74.2 MHz Image Size: 597 x 336 mm
[ 2358.644] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 2358.644] (II) RADEON(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 2358.644] (II) RADEON(0): Supported detailed timing:
[ 2358.644] (II) RADEON(0): clock: 74.2 MHz Image Size: 597 x 336 mm
[ 2358.644] (II) RADEON(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 2358.644] (II) RADEON(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 2358.644] (II) RADEON(0): Supported detailed timing:
[ 2358.644] (II) RADEON(0): clock: 27.0 MHz Image Size: 597 x 336 mm
[ 2358.644] (II) RADEON(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
[ 2358.644] (II) RADEON(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
[ 2358.644] (II) RADEON(0): Number of EDID sections to follow: 1
[ 2358.644] (II) RADEON(0): EDID (in hex):
[ 2358.644] (II) RADEON(0): 00ffffffffffff0010ac57a04c543930
[ 2358.644] (II) RADEON(0): 34140104b53c22783a8e05ad4f33b026
[ 2358.644] (II) RADEON(0): 0d5054a54b008100b300d100714fa940
[ 2358.644] (II) RADEON(0): 818001010101565e00a0a0a029503020
[ 2358.644] (II) RADEON(0): 350055502100001a000000ff00473630
[ 2358.644] (II) RADEON(0): 365430434f3039544c0a000000fc0044
[ 2358.644] (II) RADEON(0): 454c4c2055323731310a2020000000fd
[ 2358.644] (II) RADEON(0): 0031561d711e000a202020202020012d
[ 2358.644] (II) RADEON(0): 02031df1509005040302071601061112
[ 2358.644] (II) RADEON(0): 1513141f20230d7f07830f0000023a80
[ 2358.644] (II) RADEON(0): 1871382d40582c250055502100001e01
[ 2358.644] (II) RADEON(0): 1d8018711c1620582c25005550210000
[ 2358.644] (II) RADEON(0): 9e011d007251d01e206e285500555021
[ 2358.644] (II) RADEON(0): 00001e8c0ad08a20e02d10103e960055
[ 2358.644] (II) RADEON(0): 50210000180000000000000000000000
[ 2358.644] (II) RADEON(0): 0000000000000000000000000000004b
[ 2358.644] (II) RADEON(0): Printing probed modes for output DisplayPort-0
[ 2358.644] (II) RADEON(0): Modeline "2560x1440"x60.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
[ 2358.644] (II) RADEON(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync (67.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080i"x59.9 74.18 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1440x576i"x50.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1440x480i"x60.0 27.03 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.8 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "1440x480i"x59.9 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 2358.644] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 2358.706] (II) RADEON(0): EDID for output HDMI-0
[ 2358.706] (II) RADEON(0): Manufacturer: MEI Model: a0a6 Serial#: 16843009
[ 2358.706] (II) RADEON(0): Year: 2010 Week: 0
[ 2358.706] (II) RADEON(0): EDID Version: 1.3
[ 2358.706] (II) RADEON(0): Digital Display Input
[ 2358.706] (II) RADEON(0): Indeterminate output size
[ 2358.706] (II) RADEON(0): Gamma: 2.20
[ 2358.706] (II) RADEON(0): No DPMS capabilities specified
[ 2358.706] (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 2358.706] (II) RADEON(0): First detailed timing is preferred mode
[ 2358.706] (II) RADEON(0): redX: 0.640 redY: 0.345 greenX: 0.291 greenY: 0.635
[ 2358.706] (II) RADEON(0): blueX: 0.163 blueY: 0.093 whiteX: 0.288 whiteY: 0.296
[ 2358.706] (II) RADEON(0): Manufacturer's mask: 0
[ 2358.706] (II) RADEON(0): Supported detailed timing:
[ 2358.706] (II) RADEON(0): clock: 148.5 MHz Image Size: 698 x 392 mm
[ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 2358.706] (II) RADEON(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 2358.706] (II) RADEON(0): Supported detailed timing:
[ 2358.706] (II) RADEON(0): clock: 148.5 MHz Image Size: 698 x 392 mm
[ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 2358.706] (II) RADEON(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 2358.706] (II) RADEON(0): Monitor name: Panasonic-TV
[ 2358.706] (II) RADEON(0): Ranges: V min: 23 V max: 61 Hz, H min: 15 H max: 68 kHz, PixClock max 155 MHz
[ 2358.706] (II) RADEON(0): Supported detailed timing:
[ 2358.706] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
[ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 2358.706] (II) RADEON(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 2358.706] (II) RADEON(0): Supported detailed timing:
[ 2358.706] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
[ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 2358.706] (II) RADEON(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 2358.706] (II) RADEON(0): Supported detailed timing:
[ 2358.706] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
[ 2358.706] (II) RADEON(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
[ 2358.706] (II) RADEON(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 2358.706] (II) RADEON(0): Supported detailed timing:
[ 2358.707] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
[ 2358.707] (II) RADEON(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 2358.707] (II) RADEON(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 2358.707] (II) RADEON(0): Number of EDID sections to follow: 1
[ 2358.707] (II) RADEON(0): EDID (in hex):
[ 2358.707] (II) RADEON(0): 00ffffffffffff0034a9a6a001010101
[ 2358.707] (II) RADEON(0): 00140103800000780adaffa3584aa229
[ 2358.707] (II) RADEON(0): 17494b00000001010101010101010101
[ 2358.707] (II) RADEON(0): 010101010101023a80d072382d40102c
[ 2358.707] (II) RADEON(0): 4580ba882100001e023a801871382d40
[ 2358.707] (II) RADEON(0): 582c4500ba882100001e000000fc0050
[ 2358.707] (II) RADEON(0): 616e61736f6e69632d54560a000000fd
[ 2358.707] (II) RADEON(0): 00173d0f440f000a20202020202001d1
[ 2358.707] (II) RADEON(0): 02032672509f90140520130412031102
[ 2358.707] (II) RADEON(0): 16071506012309070168030c001000b8
[ 2358.707] (II) RADEON(0): 260fe3051f01011d80d0721c1620102c
[ 2358.707] (II) RADEON(0): 2580ba882100009e011d8018711c1620
[ 2358.707] (II) RADEON(0): 582c2500ba882100009e011d00bc52d0
[ 2358.707] (II) RADEON(0): 1e20b8285540ba882100001e011d0072
[ 2358.707] (II) RADEON(0): 51d01e206e285500ba882100001e0000
[ 2358.707] (II) RADEON(0): 000000000000000000000000000000c1
[ 2358.707] (II) RADEON(0): Printing probed modes for output HDMI-0
[ 2358.707] (II) RADEON(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080i"x59.9 74.18 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1440x576i"x50.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1440x480i"x60.0 27.03 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.8 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "1440x480i"x59.9 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 2358.707] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 2358.726] (II) RADEON(0): EDID for output DVI-0
[ 2358.726] (II) RADEON(0): Output DisplayPort-0 connected
[ 2358.726] (II) RADEON(0): Output HDMI-0 connected
[ 2358.726] (II) RADEON(0): Output DVI-0 disconnected
[ 2358.726] (II) RADEON(0): Using exact sizes for initial modes
[ 2358.726] (II) RADEON(0): Output DisplayPort-0 using initial mode 1920x1080
[ 2358.726] (II) RADEON(0): Output HDMI-0 using initial mode 1920x1080
[ 2358.726] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 2358.726] (II) RADEON(0): mem size init: gart size :3fbde000 vram size: s:40000000 visible:3f1b0000
[ 2358.726] (==) RADEON(0): DPI set to (96, 96)
[ 2358.726] (II) Loading sub module "fb"
[ 2358.726] (II) LoadModule: "fb"
[ 2358.726] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2358.727] (II) Module fb: vendor="X.Org Foundation"
[ 2358.727] compiled for 1.15.0, module version = 1.0.0
[ 2358.727] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2358.727] (II) Loading sub module "ramdac"
[ 2358.727] (II) LoadModule: "ramdac"
[ 2358.727] (II) Module "ramdac" already built-in
[ 2358.727] (--) Depth 24 pixmap format is 32 bpp
[ 2358.727] (II) RADEON(0): [DRI2] Setup complete
[ 2358.727] (II) RADEON(0): [DRI2] DRI driver: radeonsi
[ 2358.727] (II) RADEON(0): [DRI2] VDPAU driver: radeonsi
[ 2358.727] (II) RADEON(0): Front buffer size: 8160K
[ 2358.727] (II) RADEON(0): VRAM usage limit set to 923097K
[ 2358.727] (==) RADEON(0): Backing store enabled
[ 2358.727] (II) RADEON(0): Direct rendering enabled
[ 2358.792] (II) RADEON(0): Use GLAMOR acceleration.
[ 2358.792] (II) RADEON(0): Acceleration enabled
[ 2358.792] (==) RADEON(0): DPMS enabled
[ 2358.792] (==) RADEON(0): Silken mouse enabled
[ 2358.792] (II) RADEON(0): Set up textured video (glamor)
[ 2358.792] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured Video.
[ 2358.792] (II) RADEON(0): [XvMC] Extension initialized.
[ 2358.792] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 2358.792] (--) RandR disabled
[ 2358.796] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 2358.796] (II) AIGLX: enabled GLX_ARB_create_context
[ 2358.796] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 2358.796] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 2358.796] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 2358.796] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 2358.796] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 2358.796] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 2358.796] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 2358.797] (II) AIGLX: Loaded and initialized radeonsi
[ 2358.797] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 2358.833] (II) RADEON(0): Setting screen physical size to 508 x 285
[ 2358.860] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 2358.860] (**) Power Button: Applying InputClass "system-keyboard"
[ 2358.860] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2358.860] (**) Power Button: Applying InputClass "keyboard"
[ 2358.860] (II) LoadModule: "evdev"
[ 2358.860] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2358.860] (II) Module evdev: vendor="X.Org Foundation"
[ 2358.860] compiled for 1.15.0, module version = 2.8.2
[ 2358.860] Module class: X.Org XInput Driver
[ 2358.860] ABI class: X.Org XInput driver, version 20.0
[ 2358.860] (II) Using input driver 'evdev' for 'Power Button'
[ 2358.860] (**) Power Button: always reports core events
[ 2358.860] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 2358.860] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2358.860] (--) evdev: Power Button: Found keys
[ 2358.860] (II) evdev: Power Button: Configuring as keyboard
[ 2358.860] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 2358.860] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2358.860] (**) Option "xkb_rules" "evdev"
[ 2358.860] (**) Option "xkb_model" "pc104"
[ 2358.860] (**) Option "xkb_layout" "de"
[ 2358.860] (**) Option "xkb_variant" "nodeadkeys"
[ 2358.875] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 2358.875] (**) Power Button: Applying InputClass "system-keyboard"
[ 2358.875] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2358.875] (**) Power Button: Applying InputClass "keyboard"
[ 2358.875] (II) Using input driver 'evdev' for 'Power Button'
[ 2358.875] (**) Power Button: always reports core events
[ 2358.875] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 2358.875] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2358.875] (--) evdev: Power Button: Found keys
[ 2358.875] (II) evdev: Power Button: Configuring as keyboard
[ 2358.875] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 2358.875] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 2358.875] (**) Option "xkb_rules" "evdev"
[ 2358.875] (**) Option "xkb_model" "pc104"
[ 2358.875] (**) Option "xkb_layout" "de"
[ 2358.875] (**) Option "xkb_variant" "nodeadkeys"
[ 2358.875] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 2358.875] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event27)
[ 2358.875] (II) No input driver specified, ignoring this device.
[ 2358.875] (II) This device may have been added with another device file.
[ 2358.875] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event26)
[ 2358.875] (II) No input driver specified, ignoring this device.
[ 2358.875] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event25)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event24)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event23)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=11 (/dev/input/event22)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event18)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event17)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event16)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event15)
[ 2358.876] (II) No input driver specified, ignoring this device.
[ 2358.876] (II) This device may have been added with another device file.
[ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event14)
[ 2358.877] (II) No input driver specified, ignoring this device.
[ 2358.877] (II) This device may have been added with another device file.
[ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event13)
[ 2358.877] (II) No input driver specified, ignoring this device.
[ 2358.877] (II) This device may have been added with another device file.
[ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event12)
[ 2358.877] (II) No input driver specified, ignoring this device.
[ 2358.877] (II) This device may have been added with another device file.
[ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[ 2358.877] (II) No input driver specified, ignoring this device.
[ 2358.877] (II) This device may have been added with another device file.
[ 2358.877] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event19)
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "system-keyboard"
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "keyboard"
[ 2358.877] (II) Using input driver 'evdev' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 2358.877] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event19"
[ 2358.877] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Vendor 0x45e Product 0x745
[ 2358.877] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found keys
[ 2358.877] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
[ 2358.877] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2.1/4-1.2.1.2/4-1.2.1.2:1.0/input/input19/event19"
[ 2358.877] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 8)
[ 2358.877] (**) Option "xkb_rules" "evdev"
[ 2358.877] (**) Option "xkb_model" "pc104"
[ 2358.877] (**) Option "xkb_layout" "de"
[ 2358.877] (**) Option "xkb_variant" "nodeadkeys"
[ 2358.877] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event20)
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "system-keyboard"
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev pointer catchall"
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
[ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "keyboard"
[ 2358.877] (II) Using input driver 'evdev' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 2358.878] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 2358.878] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event20"
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Vendor 0x45e Product 0x745
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found 9 mouse buttons
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found scroll wheel(s)
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found relative axes
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found x and y relative axes
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found absolute axes
[ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Forcing absolute x/y axes to exist.
[ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found keys
[ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as mouse
[ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
[ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Adding scrollwheel support
[ 2358.878] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: YAxisMapping: buttons 4 and 5
[ 2358.878] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2358.878] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2.1/4-1.2.1.2/4-1.2.1.2:1.1/input/input20/event20"
[ 2358.878] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 9)
[ 2358.878] (**) Option "xkb_rules" "evdev"
[ 2358.878] (**) Option "xkb_model" "pc104"
[
Similar Messages
-
Can you run the darker shade UI on iOS7 running v28
Hi,
Can you run the darker shade UI on iOS7 running v28 instead of the lighter shade UI?
Thanks.The UI and certain features/functions in v28 has changed as compared to the previous versions. But you can customize the v28 UI color/fonts/text etc to something of your choice. Then replace the default UI with your own in App builder
http://www.adobe.com/devnet/digitalpublishingsuite/articles/using-dps-store-configurator.h tml -
How do I prevent the Darker Shade Box (color shift) around Vector Objects when Printing
Sorry in advance for the novelette. I am absolutely mystified and frustrated and would love some help! I've been working on this problem for about 30 hours over the last 4 days to figure out what the heck is happening and cannot find an answer through various forms of research.
Basically, when I print a JPEG, I am getting this area (a box) of darker shaded coloring around my heart and love text. I've tested it a million different ways and am at a loss as to what the problem is ... is it an application problem, a color profile problem between my applications and printer, an improper way that I saved my file, etc.
Here is a photo I took of the image printed out (so it is slightly skewed from camera distortion):
The details:
(1) I create graphic art and sell it online. I save all of my printable art as JPEG files because of my customer base (diy hobbyists that print on their home printers without much knowledge base nor graphic design software).
(2) I use both Adobe Illustrator (AI) and Photoshop Elements 11 (PSE11) to design and save my artwork.
(3) I insert JPEG images into Microsoft Word 2003 documents to "test print" since most of my customers use home printers to print. Since most people have this basic software, it is a good gauge of the kind of print out they might get using the same or similar software.
(4) My PSE11 color profile setting is the default sRGB. I have test printed many times and I get the truest colors with this color profile.
(5) My AI color settings are normally also an sRGB color mode, but on occasion, I use a CMYK color mode if I am creating a larger document that I know the customer will need to take to a professional printer to print out.
(6) I do my home printing (for proofs) on an Epson Stylus Photo 1400 (which has the 6 color ink cartridges).
(7) Until this printing problem occurred on this test print out, I always used the "photo enhance" option when I designate settings for my printer via the Microsoft Word documents.
IMPORTANT: This is when I have the color shift?? or color rendering issues?? and it is the only time. If I use the regular ICM/ICC color profile of sRGB, the printing issue doesn't occur. Instead, I have a solid color background instead of this one with the strips of lighter color on the top and bottom. However, I can't control how the customer prints, so I need to feel confident that whatever color profile setting they use, they will not run into this problem. I even test printed the documents over at FedEx and the darker box/color shift did not occur.
(8) The document in question only has 3 sets of objects: the heart, the solid colored rectangle colored background and the text. All 3 objects are vectors, they are at 100% opacity and there are no "special effects" applied.
(9) The image was entirely created in AI this time and exported as a maximum quality JPEG file, although you will see below that I tried many ways to create and save the file so that I didn't have the color band borders on top/bottom.
(10) I regularly use AI for part of my art, then I drag it to my PSE11 open document and it becomes a Vector Object (it cannot by copying/pasting into a PSE11 document). I also regularly export AI images as PNG files, then insert them into an open PSE11 document. This printing issue has not occurred until recently. Here is an example of a very complex AI image I created, then inserted into PSE11 just to add the background (the Teddy Bear and books are AI vector objects) that were exported as PNG files then inserted into PSE11 to integrate with the background image - I test printed with Photo Enhance and had no printing issues:
So, from the research I have done, it looks like it is a color rendering or color space issue with conflicting color profiles in the same document. I checked my color profile settings and both sRGB and CMYK were set to embed ICC color profiles.
I tried changing AI settings to Preserve Numbers (ignore linked profiles) for CMYK, but that didn't work.
I also checked and made sure that not only the document setup showed the sRGB color profile, but that all the objects within the document also were converted to sRGB as well for consistency. That didn't work.
I tried converting the document to CMYK along with the vector objects. That didn't work.
I tried saving the heart image as a PNG file alone, the "love" text as a PNG file alone, both the heart and text together as a PNG files alone. Once saved as PNG files, I inserted them into an open empty PSE11 document - as I normally do. I then added the background color I wanted. That didn't work - the print still showed the color changes.
I tried dragging each vector object separately and even as a group and got the same color change issue when printing.
I tried "expanding" and "outlining" the text before exporting as JPEG, before exporting as a PNG and before dragging as a vector object into PSE11. Expanding the text did not help the situation.
I tried exporting as Adobe PDF, then opening in PSE11, then resaving as JPEG. That didn't work.
I tried flattening transparency (even though there is no transparency in the AI file). That didn't work.
I tried rasterizing the image. That didn't work.
Thinking that the file might be corrupt, I started from scratch and redesigned the same heart and love text. Unfortunately, I had the same problem as before. At this point, my AI started becoming buggy and would not open new files. It happened repeatedly and I decided it was best to uninstall and reinstall AI (and maybe that would fix the problem).
I created just the heart in AI, then inserted it into an open PSE11 document (both after exporting as PNG and also by dragging as Vector Object from AI). It seemed to work. I could both drag the vector into PSE11 from AI and export from AI as a PNG, then insert into open PSE11 document with a background color - and it printed a solid background.
So, I thought that reinstalling and setting back to defaults worked. But, then I added the love text around the heart and tried exporting as JPEG files and the same problem continued to recur. Whether I dragged as a Vector object into PSE11 (the heart object and love text separately and also another time with the vector objects dragged as a group) or saved them as PNG files and inserted into PSE11 - I got the different shades of color on what should be a solid background. I even tried saving the PSE11 as a PSD file first, then resaving as JPEG and I tried saving as PNG and printing and this didn't help solve the problem.
I really think it is some color conflict issue but I can't figure it out. I am definitely not very knowledgeable about color profiles and how to sync all my devices, however, as I mentioned, this was not an issue until recently (and I think??? I recall changing the CMYK setting from Preserve Numbers to embed color profile a month or so ago - however, it should have been solved when AI went back to its defaults upon reinstall).
The reason I believe it is a color rendering/color space issue is because I could see the color output when I saved the JPEG with CMYK color profile versus sRGB color profile and the sRGB colors were much richer, not surprisingly. The top and bottom colors matched the sRGB printout and the middle darker box section matched the CMYK printout.
I am sure it is something fundamental or simple and I am completely overlooking it. I wish it were just a transparency issue, because people know how to fix or do workarounds for it. But, there are no vector objects with any transparency ...
If I missed some detail, I apologize. Any help would be a dream come true at this point! lol
Thank you!Okay, I got motivated to try again. From doing a bit more research on troubleshooting AI printing problems, the Adobe article talks about print drivers. It was advised to uninstall and reinstall the print driver if the printing issue persists. So, I did. Unfortunately, I still had the same result after reinstalling and trying a test print! Ugh.
So, as Jacob said upfront, I seem to have an overactive print driver that is trying too hard (and it is a non-postscript printer which I realize is part of the problem).
There are so many variables in my situation as to how I create art and save/export art. I sometimes work solely in AI, sometimes solely in PSE and sometimes I use both programs to create. Consequently, I will:
(1) export directly from AI as JPEG if I am not adding PSE11 artwork.
(2) export directly from AI as PNG if I plan on inserting that image into PSE11 to add to artwork I have created in PSE11.
(3) drag vector objects as a Smart Objects directly from AI to PSE11 to add to artwork I am creating in PSE11 if I know I will playing with the vector object and resizing in PSE11.
So, I did a test print using scenario 2, where I inserted the heart and love text PNG (AI created vector object) into an old PSE11 document. This old document already had a vector object from AI with a solid background and I knew it printed correctly. So, after inserting this new PNG from AI into this old document, it printed correctly using the photo enhance mode.
However, I haven't had a chance to actually create new art in the older AI files (that I know print properly), resave as something else and try another test print (either by exporting as JPEG and printing in Word or by exporting as PNG file and inserting into PSE11 document, then saving as JPEG and printing in Word).
After testing the different possibilities of ICM settings within my printer, I found that the JPEG images printed out with the truest colors and best quality if I simply selected "no color management" from the printer. Shocker, huh? lol
MY SOLUTION: So, what I think I will simply do is add an instruction sheet with the printables I sell, explaining that the color profile setting should never be handled by the printer so make sure to turn off color management by printer (and if they feel they must use the printer for color management, make sure the setting is sRGB since I embed that color profile in my JPEG's).
Edited to add: Since my issue was never about how I could print a successful image (I knew I could simply change the color profile settings), but rather about how to make sure that customers would get consistent and high quality print outputs of my digital images, this seems like the best approach.
I don't think I will every really know exactly why I am now getting color shifts in the "photo enhance" mode when I did not have this problem a couple months ago - applying the same methods of creating artwork. I was concerned that I was saving/exporting using incorrect or mismatched color settings or something of that nature. However, since I went through the process of making my color spaces the same for everything, and I still have issue, clearly that is not the culprit. The only thing I can do to solve the problem and it is a straightforward solution anyway -> is to educate the buyer on how to print successfully (don't use photo enhance! ha ha).
Thanks again to everyone who chimed in and offered advice! -
Disable automatic color space compression on CinemaDNG files
When I import my CinemaDNG files from the BMPCC into Premiere, it looks like premiere is still applying a rec709-type LUT to the image by default, as opposed to showing the log images it captures in. Is there a way to disable this? I have several LUTs built specifically for BMCC/BMPCC footage in its log format, and the auto-correction Premiere slaps on there messes up those LUTs. I really want to get away from Davinci Resolve and go with a full Adobe workflow but unless there's a workaround for this I'm still limited to round-tripping to Resolve in order to use the LUTs.
Premiere isn't applying any LUT, it's just doing a kind of poopy job interpreting the RAW and there are only rudimentary controls to tweak it.
The way Premiere handles raw DNGs right now is very disappointing. For whatever reason Adobe chose not to use Adobe Camera RAW to handle DNGs in Premiere and instead went with an "ACR Lite," those three rinky dink sliders in the source settings menu. I think this could be because ACR is a heavy duty piece of kit that makes After Effects attractive...if you incorporate ACR into Premiere, you're stealing a big chunk of functionality from AE. Or, maybe ACR will be implemented in a future update and these controls are just a holdover.
So what happens when you go from ACR to those three little sliders? Top image is a ML 5dmk3 frame rendered out from Photoshop, with ACR settings straight down the middle. The bottom image is the same frame except from Premiere, with no effects applied, except a slight downward exposure adjustment, without which the shirt was completely blown out.
I think there is a ways to go before there is a truly workable workflow for RAW inside of Premiere with as much image control as AE has.
Moving from raw to a workable colorspace is a lot like developing a film print, it's not a process you can throw away or automate, there is a certain care and thoughtfulness that should go into it, and really only Adobe Camera RAW controls are equipped for this kind of work.
Until then I think the best workflow is to import your footage into AE, and "develop" your footage with ACR individually before exporting to a near-lossless codec like ProRes. -
The availability of color space in RAW, TIFF and JPEG files
This is useful if your new to DSLR photography.
This is Nikon response on my question in the discussion: View photo metadata
I'm assuming that you know that Adobe RGB shows about 50% and sRGB 35% of CIELAB color space.
In a DSLR camera like the Nikon D800 you can select a color space (Adobe RGB or sRGB) in the shooting menu.
In Adobe Lightroom 4.3 the RAW metadata shows no color space info. Therefore I asked why not?
In the (Dutch) Nikon D800 manual on page 84 (about RAW) and 274 (about color space) and Nikon FAQ website there is no descripton about the color space availability/behavior in RAW, JPEG and TIFF files.
In the book "Mastering the Nikon D800 by Darrel Young" on page 125 - 126 is written: "If you shoot in RAW format a lot, you may want to consider using Adobe RGB....."
All experts on this forum answered: color space does not apply/affect the RAW data file or RAW files have no color space.
The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are always physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available. So the forum experts gave the correct answer!
Of course you can convert afterwards a JPEG or TIFF file with sRGB color space to Adobe RGB but you don't get more colors.
When you install the Microsoft Camera Codec Pack or FastPictureViewer Codec Pack they only show color space metadata for JPEG and TIFF files and nothing for RAW because color space "doesn't exist". I thought the codec packs removed the color space metadata for my RAW files.
Adobe Lightroom also can not show color space for RAW files because that "doesn't exist".Van-Paul wrote:
The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available.
I still think this is an evasive answer that doesn't really pinpoint the exact chain of events that take place. They are:
1. The raw file contains the naked data captured by the sensor. This is just a very dark grayscale image.
2. In the raw converter it is encoded into a working color space to process the information. In Lightroom this is known as "Melissa RGB", or linear gamma Prophoto. It is also demosaiced to bring back the color information.
3. From Lightroom it can be exported to one of the familiar color spaces like sRGB or Adobe RGB. This is, in principle at least, a normal profile conversion.
These three steps are what the camera does to produce a jpeg. So the basic steps are the same, the camera is just doing it automatically (and usually butchering the image in the process...).
This Darrell Young is, I'm sure, an excellent photographer, but in this he is seriously confused and just propagating a common myth. Anyway, thanks for bringing up this discussion, hope you didn't object too much to the tone of the answers... Our only concern here was to get this right and with no room for misunderstanding. -
What color space as base in a brand guide?
What color space forms the base of a color brand guide? How do you start in terms of color spesifications? When I look at most guides it seems that Pantone is always the base, then CMYK, then RGB and Hex? Is RGB and Hex always gonna be a dithered version of the CMYK values or is it best practise to hand pick each one to make them look as close to the CMYK as possible? Is Pantone always mentioned first in the list because that's where the designer started?
Also, is best practise to mimmick the CMYK and Pantone colors so that the RGB and hex values look like them? Seems to me that most brand guides / visual manuals are made firstly for print, then they add the screen based color spaces.
In the enclosed example I also observe that the complete values are not always listed, in many cases the Y and K is missing in the CMYK values, does that mean it doesn't contain any black, or is it simply meaning zero? It rarerly occurs with the other color spaces.For web, email and screen in general it should always be sRGB. Then you can be fairly certain that it will display correctly (more or less) in any scenario. sRGB wil also work for print (inkjet), it's just that many colors that can be printed are out of sRGB gamut, so it's a restriction that doesn't need to be there. sRGB is a small color space that can't reproduce very saturated colors - they're just clipped. So it's better to start with a larger space like Adobe RGB or even ProPhoto.
For editing purposes you want a large color space simply to have headroom and not hit the wall at every move. The final destination may well be a smaller space, like a printer profile. The software then converts to that destination profile as it goes to the printer. You can soft proof to the printer profile to get an impression of how the final result will look.
You can print directly from InDesign, but the typical InDesign workflow is to export a finished PDF. That is where you specify a final destination profile for the whole document, whether a certain CMYK profile for offset press, or an RGB profile for screen. So you have your master InDesign file, and output PDFs for each destination. The InDesign file can contain placed RGB images in any color space, while text and graphic elements are CMYK. Then everything is converted in one go at export.
You should always go through the PDF Export dialog carefully. Use the presets, but don't automatically accept defaults. For specific purposes, ask here or in the InDesign forum, where they deal with this all the time.
For screen, under "Output" use convert to destination, sRGB, include profile. Under "Compression", things aren't as obvious as they used to be (downsample to 96 or 100 ppi), because of the new retina displays that can benefit from a higher resolution. I hold my judgement on this one. -
MPB 17" and what Adobe RGB color space coverage I might expect from it
Hello,
I am photographer and currently PC user. However, I plan to dive to the Mac’s world.
Before I become a Mac user, I have few questions.
Now I think about MacBook Pro 17”, i7 2.66MHz, 8GB RAM, 500 GB 7200rpm HDD and antiglare screen.
I plan to use additional monitor for photo editing.
I did search on google about *NVIDIA GeForce GT 330M* and *Adobe RGB color space* it covers, however, it gave me no results related to Mac. The only information about this card and Adobe colors I found is that Sony Vaio use this graphic card and in some forums, one say it covers 98% and in other 100% of Adobe color space which made me wonder what type of screen Vaio have.
- is MacBook Pro 17” good for photo editing?
- what % of AdobeRGB color space I might expect from it on my external screen or what % of sRGB colors space it delivers?
- Is it possible to calibrate Mac’s native screen and external one, use both at the time and have different profiles on each?
- Tell me anything that would stop me thinking about MBP for photo editing?
Thank you for your time reading this and hope to find the answers here.You should consider posting your questions in the Pro Application section for Aperture. You will bump into more photographers there than you will here. But I will make an attempt at answers:
whats about Adobe color space?
No, the MBP screen will not encompass the Adobe Color Space. In fact, few desktop monitors are capable of this.
does the native MBP screen display full color range the video card is able to produce...
There really is no limit to the color extremes, which define a color space, as established by a graphics card. So your question is not a well formed question. An old ATI Rage card with 8-bit output would reveal the same color gamut as would the NVIDIA GeForce GT 330M connected to the same display. The gamut is determined by the attached display, not the graphics card.
...or connecting external monitor to it’s mini display port would bring much wider color range to my eyes?
Yes, certainly the potential for that exists. Notebook screens are usually a compromise and can't be expected to compete with a high-end desktop display in many categories, including color gamut. But whether it would bring a "much wider color range to" your eyes is hard to say. It depends on what type of external display is in use. -
Document's transparency blend space? Destination color space?
I need some hand-holding please.
I just exported to pdf, and got this message, and would be happy to fix it if I had a clue what to do:
The document's transparency blend space doesn't match the destination color space specified in the Export Adobe PDF settings.
To avoid color appearance changes in the PDF, click cancel and change either the document's transparency blend space, or the destination color space.
Can you please translate that into English and tell me what to do?OK, I've reproduced the problem, and here's what I'd do.
You've placed RGB images over CMYK vector paterns made in Illustrator, which in some ways makes things more complex than if the imges and backgrounds were all in a single color space, but it looks as if only the backgrounds are going to be affected by any flattening that will be taking place in the conversion, so if there is any color shifting due to the flattening and choice of space, and I don't see any, it will be isolated to the background texture and probably not noticeable.
Since you have two destinations, you need two differnt PDFs. The sample is very interesting, but I suspect the print run will be small -- limited to family members -- so the first thing to do is ask the printer what PDF export settings he wants you to use. If you're going to have this printed somewhere like Kinkos or Staples, they probably can't answer that question, and I'd stick with the High Quality Print preset, and be sure the compatibility is set to Acrobat 5 or higher so the transparency isn't flattened. Print one page as a sample before committing to the entire job to check the color (and don't expect miracles from the average copy shop running a color copier -- they usually just aren't set up to handle color management and matching).
For the screen version, set the blend space to RGB and choose the Smallest File Size preset. you shouldn't get the warning (but you could ignore it even if you did). If the file is still too big, set the compressin settings to downsample color and grayscale to 75 ppi and lineart to 600 and see if that helps before you try reducing the quality in the compression. The prints off a desktop printer won't be quite as good as they will be at 100ppi, but probably acceptable on most inexpensive paper stocks that peopl seem to use, and hopefully they are going to get the better printed version, anyway.
Peter -
Images Change Colors between monitors while the UI stays the same
Hey! Im having an issue where photoshop changes the colors when I move the window between my monitors, seen here: http://sta.sh/04y5s60vf3j This isnt due to the monitors themselves being different, it actually changes after a few seconds of moving it inbetween the monitors. The left one has been callibrated with a spyder 3 elite which I no longer have access to. I applied the file with windows color management instead of the spyder utility. The second one is new, and it is not callibrated by anything, but instead was done by hand with the built in brightness/contrast/custom RGB settings. Both of them are very close to eachother, enough so for my tastes. but when photoshop changes what the image looks like, it's causing problems. Interestingly enough, when I disable callibration for the monitor on the left, the image does not change colors between monitors, but instead always appears as it does on the right. but then they don't match up and the whole screen looked washed out because it's uncallibrated, so that doesnt do me any good. Another interesting thing to point out, is when this image is saved as a .JPG, and viewed with firefox the image appears exactly like the monitor on the LEFT (which is my main monitor) despite the left monitor being the one that is force changed. does anyone have any suggestions? It also appears that windows photoviewer is behaving the same way, though firefox does not. Meaning when I open an image in all 3 on the left monitor, they look the same, but when opened on the right monitor, windows photo viewer and photoshop both display the image as brighter and redder than firefox does. This is frustrating, because it seems photoshop is changing the image with my callibration on my left monitor to match what it looks like on the web, which it does. but it doesn't do this for the right monitor, or when the left is uncallibrated. Another issue I can see with this is even if the UI is the same shade of gray, the images are different between the monitors because of this change. Does anyone have any suggestions?
- BDAlright! So I reread through all this, poked at some things on the internet, and I'm going to attempt to summarize what would be a good solution for all this (And it seems, it still won't be perfect, but to get myself into the best environment I can for not messing with images for an hour trying to make them look nice before I post them to the web. I painted something yesterday on the cintiq, popped it over to my laptop screen and it just looked washed out and terrible.)
1. Get a X-rite EODIS3 i1 Display Pro, Callibrate laptop and cintiq. I do have the money to drop on something like this, especially if it's a time saver.
Things I'm not sure about:
a. There was a ton of complaints about the software not working when I checked reviews, but also a ton that said everything was great. most of them were mac users though.
b. I'm not sure if problems would still be posed, even while calibrated, by me having a wide gamut monitor.
c. I'm a terrible excuse for a human being and I think the colors showing up brighter on the wide gamut screen is pretty (I should just make my images this bright on a normal screen and there won't be any issues. >.>)
2. Set Firefox to color manage (easy enough)
3. Change my photoshop working space to sRGB (since they'll have been calibrated at this point)
3. Accept the fact that most of the people who look at my work will be doing so on a monitor that is almost certainly uncalibrated, and I can't control what they will see on my screen, but I CAN control if the colors are -actually- what I want them to be on any properly calibrated device. which is probably the best way to go anyways.
4. Make paintings, have fun.
Now, you two have been going on about all sorts of interesting things in here, and it seems that calibration issue run much much deeper than I ever thought. Do either of you have recommendations for how I should tweak this list of things to do or other things I can/ should do? I'm not currently a working professional, but if I have anything to say about it, I will be within a few years (I'm going to school for illustration and studying concept design on my own time) so it'd be useful for me to get into good habits now.
- Brendavid -
Error "Expected end of color space" when opening converted OTF - PDF.
Hi experts,
I need help. I'm converting from otf to pdf and it works fine. However when i tried putting a bitmap 256 color to the smartform and generate pdf with CONVERT_OTF FM the pdf result in an error "Expected end of color space" when opening the document and it goes blank.
Can anyone tell why ?
Thanks,
FelixHi Peter,
I can open it with another acrobat version. However, the image is not displayed. Do you know why?
Thanks -
I'm a couple of days into a trial of Fireworks and I got it
only for two reasons: First to be able to create navigation bars
with popup menus on some of the menu options and second, to more
easily create photo galleries for my web site. (I'm quite
comfortable with PhotoShop and creating web-optimized images.)
Anyway, I've run into a couple of things that have got me
stumped...
If I use FW CS3 to optimize a JPG image for the web (either
from directly within FW or via the Create Web Photo Album command
from within Dreamweaver CS3) the resulting images no longer have a
color space embedded. And I can't find out how to embed one. The
original JPG images were created in PS CS3 and had the sRBG color
space embedded and the colors displayed as expected in a web
browser. The resulting "optimized" images no
longer have a color space embedded and the colors appear quite off.
This might be acceptable with some vector graphics or logos but
it's not acceptable with photgraphs, especially for a photography
web site.
(It's quite well-known, at least in photography circles that
for proper display of the colors, images designed for the web
should be in sRGB with that space embedded, as that is what web
browsers are optimized for. Anything else, including not embedding
a color space results in colors that are "off".)
A related issue is that when using the Create Web Photo Album
from within DW CS3 the resulting files all have a new suffix of
"_jpg" added to the name. Meaning that my
original "name.jpg" gets named
"name_jpg.jpg". I really don't like that, and
can't find how to turn it off.
(I went to a large bookstore to buy a FW book today but they
didn't have any. And the only one they even listed on their
computer is due to be published at the end of February!)
Any help would be greatly appreciated. Thanks.
Eldor - Montrealquote:
Originally posted by:
Newsgroup User
EldorG wrote:
> As I said, PEBCAK error. But that still leaves me
with the file name 'problem'
> I mentioned... that my images get named from
'name.jpg' to 'name_jpg.jpg'.
> This happens when I use the 'Create Web Photo Album'
from Dreamweaver CS3
> (which in turn calls FW to do the work). Should I
post that in the DW forum,
> or is it a FW thing? Thanks very much! Eldor
Don't name them in FW. Allow them to be exported with the
names they
already have.
Linda Rathgeber [PVII] *Adobe Community Expert-Fireworks*
http://www.projectseven.com
Fireworks Newsgroup:
news://forums.projectseven.com/fireworks/
CSS Newsgroup: news://forums.projectseven.com/css/
http://www.adobe.com/communities/experts/
Linda, I'm
not naming the images in FW. As a matter of fact, I never
even see a FW dialog. If I optimize an image directly from within
FW, there is no problem. But doing so from Dreamweaver (through the
Create Web Photo Album command which seems to call FW to automate
the work) causes the images to be reduntantly renamed. And I don't
see an option anywhere to change this.
As I said, I'm not sure if this is something I should be
asking in the FW forum or the DW forum. But since this option
doesn't even exist in DW until FW is installed and FW is called
from DW to do this, I really don't know where to ask.
How does that FW automation work? Is there a script file or
something somewhere that I might find and modify?
That option in DW not only optimizes a bunch of images, it
creates thumbnails as well, and writes all the stuff into HTML code
to produce a table of the images. So I can't just go to FW and
manually optimize an image.
Regards...
Eldor -
Camera Raw vs Lightroom Color Spaces
I photographed RAW image of a Gregtag color target with my Nikon D300 and opened it in camera raw in the ProPhoto Color space and adjusted the develop sliders so that the tone squares on the bottom row matched the ProPhoto values, (e.g approx 238,189,144,103,66,37) and ran the Robert Fors calibration script.
So far so good. I have read that all one needs to do is use the same settings in Lightroom. But when I opened the exact same RAW file in Lightroom and use the exact same develop and calibration settings that I used in ACR, it gives different values for the tone squares. And in fact the values are almost exactly the values for Adobe RGB (e.g. approx 242,200,159,121,84,53). And when I open that file in Photoshop from Lightroom using the ProPhoto color space option the value stay at the same Adobe RGB levels within the ProPhoto color space.
What am I missing/doing wrong?the values in lightroom are not based on prophotoRGB, but on a prophotoRGB-derived space with the same primaries but with a sRGB tone curve. Since adobeRGB has almost the same tonecurve as sRGB, your values came out close. Bottomline is that the values do not correspond to the ppRGB values in ACR.
-
I posted the following message to another thread, but at the recommendation of a member I am starting a new thread here. For a couple of answers see the thread below.
http://forums.adobe.com/message/3298911#3298911
I will provide much more information hoping an Adobe support person will chime in. This is extremely odd.
System: HP, AMD, Windows 7 64-Bit, Nvidia 9100, all updates to Windows, latest Nvidia 9100 driver
Display: Samsung 226CW, Windows settings 32-bit color, correct resolution,
Calibration: Done with ColorMunki, D65 target, done after monitor has been on for more than 30 minutes
Personal: (I am adding this information with some hesitation, please excuse it if it sounds like I'm bragging; I am not). I have multiple posts on my blog, have made many presentations on color managed workflow and am very comfortable with the settings in Photoshop and Lightroom. Please take this only as a baseline information, I am not bragging. In fact, I am begging for information!
Problem:
Any, I mean ANY, original JPEG image in sRGB space coming out of the camera with no adjustments, any PSD file in sRGB space, any TIFF file in sRGB space look significantly paler in Lightroom and in Photoshop CS5 than they look in other Windows based image viewers like FastStone or XnView. This should not need these applications to be color space aware, but the situation is the same with or without their color managment turned on or off. I have done the following:
1. Totally uninstalled Lightroom 3 and reinstalled it
2. Recreated a brand new Lightroom catalog/library and reimported all the images, converting all the RAW files to DNG (just in case!)
3. Recalibrated the display
When I view a file, any file and I will use for the sake of simplicity a JPEG file in sRGB color space, in Lightroom it looks pale. Since the file is in sRGB color space, I have verified this, the rendering in Lightroom should be the same as rendering in anything else. But it is not. I took my monitor and connected it to this system with the same odd behavior of rendering in Lightroom being much paler than outside. It appears as if I am viewing an image in Adobe RGB in a windows viewer that is not color managed.
I further tried the following:
1. I copied various versions of one file, all in sRGB color space. One PSD and two JPEG files from the folders of the above system and copied them to my system, Intel, Windows 7 64-bit, display calibrated and profiled with ColorMunki to the same standards as the problem system above.
2. Imported them to Lightroom on my system
3. The rendering in Lightroom is identical to rendering outside Lightroom for all the files and all are same as the rendering in FastStone on the problem system. Outside rendering was done using FastStone as on the problem system.
My deduction is that something on the problem system outlined in the opening of the message is interfering with the Adobe rendering engine and I have no idea what it could be. I WILL GREATLY APPRECIATE if an Adobe engineer could chime in and steer me in the right direction. I am willing to try other things but I have run out of ideas despite the fact that I have reduced much of the problem to the lowest common denominator of sRGB and JPEG against a PSD in sRGB.
Waiting anxiously of your help.
CemalAlso, I know enough to calibrate a monitor when it is connected to a new computer. That said, even without calibration the behavior should have changed to display all the images in question the same but perhaps with somewhat off colors. Am I right? I am not arguing the point, I am rhetorically raising the question. If the 226CW is wide gamut and 244T is not, when I connect 244T on the same computer the wide gamut issue should be eliminated, should it not? I am not talking at this point about the "correct" color, but the same color in or out of Lightroom.
Unfortunately when you connect another monitor to a computer and don't calibrate or manually change it, Windows will not change the monitor profile. Macs will autodetect and change the profile but this innovation has not reached windows yet. The behavior you observe is caused by managed apps using the monitor profile and unmanaged apps not. If the monitor profile is not changed, the behavior doesn't change.
BTW, for a "cheap" software to be color space aware it does not need a quantum leap in technology I believe. It simply needs to know how to read the ICC profile and the LUT, is that correct?
It's extremely simple to program color management into apps. Standard API libraries have been available in Windows for over a decade. The reason why this hasn't happened is related to the fact that Microsoft hasn't made IE color managed and the software makers do not want to confuse folks when images look different in their program vs IE. Considering that this still is the biggest issue people wrongly complain about in every color managed application (just check Photoshop fora) that is maybe not that strange. -
Color space conversion due to transparency ...
Hi there!
Let's assume we have a document that contains two RGB images, one of them is set to 70 % transparency. When printing to PDF, the 70 % transparent RGB image is converted to CMYK, the other one retains its RGB color space ...
I seem to understand that this is due to the current transparency color space setting. I could change that to RGB.
But I wonder: Is there no way to keep the color space here, no matter if it is CMYK or RGB the images are coming with?
Thanks,
KlausKlaus,
To learn what happens with flattening and color, you should refer to this excellent document, "Transparency in Adobe Applications: A Print Production Guide."
http://www.adobe.com/designcenter/creativesuite/articles/cs3ip_printprodtrans.pdf
Here's are relevant section (page 24):
Printing transparency: step-by-step
When printing a page containing live transparency from InDesign CS3 and the Transparency Blend Space is set to Document CMYK, the following steps will take place (steps 3 and 6 may perform color conversions):
1 Transparency is detected on a spread by the Flattener.
2 The Flattener refers to the Transparency Blend Space setting to determine the appropriate color space in which to blend transparent objects. In this example, Document CMYK was selected. The Document CMYK color space is determined by the active color settings (Edit > Color Settings).
3 Any image that is tagged with a color space that differs from the selected blend space is converted to Document CMYK.
4 The Flattener flattens the transparency.
5 The flattened data is passed to the print engine.
6 The print engine compares the color information in the flattened data with the Printer Profile color space set in the Print dialog box. If the color settings dont match, the print engine converts the colors to the color space indicated by the Printer Profile.
7 The color-managed job is printed. -
Color Space Question... using Lagarith Lossless Codec.
Hi all,
I use the Lagarith Lossless Codec for all my source editing files importing into Premiere Pro and for exporting to my encoder I use.
My question is this. I found that most of my sources are in YUV color space, so when I prep them for editing using VirtualDub, etc... I export them to Lagarith Lossless Codec in the YUY2 color space setting. The size difference between using RGB and YUY2 is enough to make me want to just use YUY2. So when editing those prepped files in YUY2 in Premiere Pro and them exporting the in the same YUY2 color space configuration, does it degrade in quality at all? I heard somewhere that Premiere Pro ONLY edits in RGB color space. So am I really messing up here or is it safe to do what I am doing?
Thanks in advance!Premiere Pro will keep the color space of the original media. And many of the effects can now also operate in YUV space (They are marked by the YUV icon.) However, any effects you use that are not marked with that icon will force an RGB conversion.
Maybe you are looking for
-
Hello, is it possible to connect my alienware laptop on an iMac and use just the screen of the iMac?
Does anyone know?
-
Hi, Do you know if the extensions of Oracle SQL - DML error logging - model clause - pivot clause are supported by ANSI SQL (or other RDBMS) ? Thanks for your help
-
How to judge inspection lot is LTCA status?
Hi all, How to judge inspection lot is LTCA status? Can we see it in QALS table? But which field is for this status? Many thanks!
-
Lost my ipod touch and is there any way i can get all my info deleted from it?
lost my ipod is there any way i can track it down or delete the info thats in it please reply
-
AT&T MicroCell not working after iOS 5 Update
I live is a "Fringe" area with poor reception from my carrier, AT&T; one bar. We installed an AT&T MicroCell and reception in and around my home was much better; five bars and the carrier indicator on the iPhone shows AT&T MicroCell. Since installing