Bug 27478

Created attachment 34695 [details]
XorgLog.txt

Created attachment 34696 [details]
CurrentDmesg.txt

Created attachment 34697 [details]
BootDmesg.txt

Bugzilla won't let me attach the photos but here's a link:  http://launchpadlibrarian.net/42068556/gammaPhotos.tar.gz

"""
I am the one who started the original post. To clarify the bug, I have added camera photos using identical manual settings of the screens from Lucid (radeon) and karmic (flgrx). Note that all images are of the same bootchart file. The images are as follows:
2149: Lucid with default settings (1.0)
2150: Lucid with xgamma set to .6
2151: Karmic with default settings (1.0)
2152: karmic with xgamma set to .6

Notice the loss of shading and detail in the Lucid shots easily seen on the init and collector rows. Although the bug may seem trivial it does affect the usability of Lucid a good deal. Please consider this a serious bug.
For additional information I use a desktop pc with an xfx radeon hd 4770 and additional info can be seen in the bootchart photos.
"""

I have attached a photo of 2 monitors, from 2 separate computers with the same HTML color chart, side-by-side. On the left is a Windows computer, and the right is the Ubuntu 10.04 Beta1 computer that is afflicted with this bug.

The colors on the Ubuntu page that shouldn't be white, but are displaying as such are:
Gainsboro
Lavender
LavenderBlush
LemonChiffon
LightCyan
LightGoldenRodYellow
LightGray

Notice that Lime and LimeGreen appear to be almost identical on the right, and very different on the left.

http://launchpadlibrarian.net/42412653/IMG_0016.jpg

This is an issue with the TV DAC BG/ADJ values.  Can you attach a copy of the problematic video bioses and in the case of the RV100 and R420, the output of "radeontool regmatch TV_DAC_CNTL"?

This patch:
http://marc.info/?l=dri-devel&m=127052658905865&w=2
fixes the issues with R4xx cards.  For the RV100 and other older cards, I'll need to see the vbios and value of tv_dac_cntl as requested.  For r6xx, I this patch should fix the issue:
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=6a8a2d702b33c6ed5c789f21b4e89fdf221f01ca

I have an older video card (lspci says)
ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

Here is the output of radeontool regmatch TV_DAC_CNTL:
TV_DAC_CNTL (088c)	0x07480043 (122159171)
MC: 0x00	0x00000000
MC: 0x01	0x00000000
MC: 0x02	0x00000000
MC: 0x03	0x00000000
MC: 0x04	0x00000000
MC: 0x05	0x00000000
MC: 0x06	0x00000000
MC: 0x07	0x00000000
MC: 0x08	0x00000000
MC: 0x09	0x00000000
MC: 0x0a	0x00000000
MC: 0x0b	0x00000000
MC: 0x0c	0x00000000
MC: 0x0d	0x00000000
MC: 0x0e	0x00000000
MC: 0x0f	0x00000000
MC: 0x10	0x00000000
MC: 0x11	0x00000000
MC: 0x12	0x00000000
MC: 0x13	0x00000000
MC: 0x14	0x00000000
MC: 0x15	0x00000000
MC: 0x16	0x00000000
MC: 0x17	0x00000000
MC: 0x18	0x00000000
MC: 0x19	0x00000000
MC: 0x1a	0x00000000
MC: 0x1b	0x00000000
MC: 0x1c	0x00000000
MC: 0x1d	0x00000000
MC: 0x1e	0x00000000
MC: 0x1f	0x00000000
MC: 0x20	0x00000000
MC: 0x21	0x00000000
MC: 0x22	0x00000000
MC: 0x23	0x00000000
MC: 0x24	0x00000000
MC: 0x25	0x00000000
MC: 0x26	0x00000000
MC: 0x27	0x00000000
MC: 0x28	0x00000000
MC: 0x29	0x00000000
MC: 0x2a	0x00000000
MC: 0x2b	0x00000000
MC: 0x2c	0x00000000
MC: 0x2d	0x00000000
MC: 0x2e	0x00000000

You also said you wanted to see the vbios, but I can figure out how to get that information. Is that something I need to look at during boot time, or is that something I can get any time?

Please let me know if I can do anything else to help. I am by no means an expert, but I can test stuff out if I'm given good enough instruction.

(In reply to comment #8)
> I have an older video card (lspci says)
> ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]
> 
> Here is the output of radeontool regmatch TV_DAC_CNTL:
> TV_DAC_CNTL (088c)    0x07480043 (122159171)

that looks correct.  Does:
radeontool regset TV_DAC_CNTL 0x07280043
help?

> 
> You also said you wanted to see the vbios, but I can figure out how to get that
> information. Is that something I need to look at during boot time, or is that
> something I can get any time?
> 

Any time.

> Please let me know if I can do anything else to help. I am by no means an
> expert, but I can test stuff out if I'm given good enough instruction.

You'll need the pci bus id from lspci, e.g.,
01:05.0 VGA compatible controller: ATI Technologies Inc RS690
^^^^^^^
It will have some leading zeros in sysfs.

cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom

>that looks correct.  Does:
>radeontool regset TV_DAC_CNTL 0x07280043
>help?

Nope, has no effect. - unless I need to restart X in order for it to take effect. (I did not restart X)

>You'll need the pci bus id from lspci, e.g.,
>01:05.0 VGA compatible controller: ATI Technologies Inc RS690
>^^^^^^^
>It will have some leading zeros in sysfs.
>
>cd /sys/bus/pci/devices/<pci bus id>
>echo 1 > rom
>cat rom > /tmp/vbios.rom
>echo 0 > rom

Ok, I feel inept here. I preformed the above as root, and I'm not sure what I should be posting as a result. do you want the contents of /sys/bus/pci/devices/0000:01:00.0/rom ? 

I displayed /tmp/vbios.rom, and it appeared to be a binary file. As a shot-in-the-dark, I'll add /tmp/vbios.rom as an attachment in just a moment here.

Created attachment 34714 [details]
vbios of rv100

(In reply to comment #10)
> >that looks correct.  Does:
> >radeontool regset TV_DAC_CNTL 0x07280043
> >help?
> 
> Nope, has no effect. - unless I need to restart X in order for it to take
> effect. (I did not restart X)
> 

No need to restart X.  what port are you using for your problematic monitor?  VGA?  DVI?

> >You'll need the pci bus id from lspci, e.g.,
> >01:05.0 VGA compatible controller: ATI Technologies Inc RS690
> >^^^^^^^
> >It will have some leading zeros in sysfs.
> >
> >cd /sys/bus/pci/devices/<pci bus id>
> >echo 1 > rom
> >cat rom > /tmp/vbios.rom
> >echo 0 > rom
> 
> Ok, I feel inept here. I preformed the above as root, and I'm not sure what I
> should be posting as a result. do you want the contents of
> /sys/bus/pci/devices/0000:01:00.0/rom ? 

yes.  It's a binary file.

for the rv100, what connectors does your card actually have?  Also, can you attach your xorg log and dmesg output?  Perhaps it's the primary dac that's causing problems.  Can you get the output of:
radeontool regmatch DAC_MACRO_CNTL

Created attachment 34715 [details]
rv100_xorg_dmesg_vbios.tgz

My video card has a single connector that looks to be a dual link DVI M1-DA. This image matches the pins on my adapter: http://en.wikipedia.org/wiki/File:M1-DA.svg
I am using a cable that goes from that dual link above, to 2x VGA. I'm only using VGA #1 on this computer. 

The output of radeontool regmatch DAC_MACRO_CNTL:
DAC_MACRO_CNTL (0d04)	0x00000000 (0)
(all the repetitive zeros that follow are excluded)

I am attaching an archive of
dmesg.txt
Xorg.0.log
vbios.rom

I not going to be able to respond here for a few hours, hope that is enough information for a while.

(In reply to comment #14)
> Created an attachment (id=34715) [details]
> rv100_xorg_dmesg_vbios.tgz
> 
> My video card has a single connector that looks to be a dual link DVI M1-DA.
> This image matches the pins on my adapter:
> http://en.wikipedia.org/wiki/File:M1-DA.svg
> I am using a cable that goes from that dual link above, to 2x VGA. I'm only
> using VGA #1 on this computer. 

perfect.  thanks!

> 
> The output of radeontool regmatch DAC_MACRO_CNTL:
> DAC_MACRO_CNTL (0d04)    0x00000000 (0)
> (all the repetitive zeros that follow are excluded)

Does:
radeontool regset DAC_MACRO_CNTL 0x00000808
fix the issue?

Ok, I lied, I'm still responding.

radeontool regset DAC_MACRO_CNTL 0x00000808
fixed my problem!  It might look a little on the blue side, but that also could be just because I was so used to looking at it all washed out for so long that my eyes are playing tricks on me.  HTML colors appear to be looking right, and html lightgray is no longer displaying as white.

Created attachment 34718 [details] [review]
dac adj fix for legacy chips

This patch should fix your rv100 (an other r1xx-r3xx cards with similar problems) issues.

I am using:

01:00.0 VGA compatible controller: ATI Technologies Inc RV620 LE [Radeon HD 3450]

and am still having these problems.

The patch mentioned above for R6xxx cards appears already to have been applied to the kernel that is shipping with Ubuntu Lucid.

I just tried to copy the video bios, but I get:

carl@houllier:/sys/bus/pci/devices/0000:01:00.0$ sudo echo 1 > rom
bash: rom: Permission denied

Let me know if there's any other information I can provide.

(In reply to comment #18)
> I am using:
> 
> 01:00.0 VGA compatible controller: ATI Technologies Inc RV620 LE [Radeon HD
> 3450]
> 
> and am still having these problems.
> 
> The patch mentioned above for R6xxx cards appears already to have been applied
> to the kernel that is shipping with Ubuntu Lucid.
> 

Ok.

> I just tried to copy the video bios, but I get:
> 
> carl@houllier:/sys/bus/pci/devices/0000:01:00.0$ sudo echo 1 > rom
> bash: rom: Permission denied
> 
> Let me know if there's any other information I can provide.

You need to be root.

Created attachment 34734 [details]
ROM from RV620 card

> You need to be root.

Gah! Sorry. I thought sudo would be sufficient.

ROM attached.

I've verified that these two patches were already included in the kernel 2.6.32-17.26 this was reported against:  
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=6a8a2d702b33c6ed5c789f21b4e89fdf221f01ca
http://marc.info/?l=dri-devel&m=127052658905865&w=2

This patch was not present in that kernel, though:
https://bugs.freedesktop.org/attachment.cgi?id=34718

Thanks, I'll forward this bug to our kernel team for further handling.

i have too that problem, motherboard Asus A2M-VM with X1250 ATI embedded . when i used VGA is too brigth, contrast is false. with Compiz i see small line when i move the cube.

For the RV620/RV635 (HD3650/3450) can you attach the output of:
avivotool regmatch 0x7ef4
avivotool regmatch 0x7ff4
For the rs690 (X1250):
avivotool regmatch 0x7854
avivotool regmatch 0x7a54

(In reply to comment #24)
> For the RV620/RV635 (HD3650/3450) can you attach the output of:
> avivotool regmatch 0x7ef4

0x7ef4	0x00202002 (2105346)

> avivotool regmatch 0x7ff4

0x7ff4	0x00202502 (2106626)

(In reply to comment #25)
> (In reply to comment #24)
> > For the RV620/RV635 (HD3650/3450) can you attach the output of:

With (working) fglrx driver:

avivotool regmatch 0x7ef4
0x7ef4    0x00202002 (2105346)
avivotool regmatch 0x7ff4
0x7ff4    0x00202502 (2106626)

With (non-working) radeon driver:

avivotool regmatch 0x7ef4
0x7ef4	0x00202002 (2105346)
avivotool regmatch 0x7ff4
0x7ff4	0x00200102 (2097410)

This looks to be a bug in the kms atom parser as the ums parser gets this right.  I'll see if I can sort it out.

Created attachment 34850 [details] [review]
atom parser fixes

This patch fixes the remaining issues.

(In reply to comment #28)
> Created an attachment (id=34850) [details]
> atom parser fixes
> 
> This patch fixes the remaining issues.

This patch fixes my problems.  Many many thanks Alex!

(In reply to comment #28)
> Created an attachment (id=34850) [details]
> atom parser fixes
> 
> This patch fixes the remaining issues.

Hi, i might be dumb when applying this patch, so could you help me please. 
I have Radeon HD3650 and Samsung LCD monitor connected via DVI->VGA connector, with gamma issue in 10.04.

This is what i did:

bajic@bajic-ubuntu:/lib/modules/2.6.32-19-generic/kernel/drivers/gpu/drm/radeon$

bajic@bajic-ubuntu:/lib/modules/2.6.32-19-generic/kernel/drivers/gpu/drm/radeon$ sudo su

root@bajic-ubuntu:/lib/modules/2.6.32-19-generic/kernel/drivers/gpu/drm/radeon$ sudo patch -p1 < 0001-drm-radeon-kms-more-atom-parser-fixes.patch 

(assuming that i've allready copied patch to this folder. Is this the right folder btw .. ??? )

This is the result i get:

root@bajic-ubuntu:/lib/modules/2.6.32-19-generic/kernel/drivers/gpu/drm/radeon# sudo patch -p1 < 0001-drm-radeon-kms-more-atom-parser-fixes.patch 
patching file drivers/gpu/drm/radeon/atom.c
Hunk #1 FAILED at 905.
Hunk #2 FAILED at 919.
2 out of 2 hunks FAILED -- saving rejects to file drivers/gpu/drm/radeon/atom.c.rej


Thank you.

*** Bug 26926 has been marked as a duplicate of this bug. ***

(In reply to comment #28)
i own a radeon HD3450 and a syncmaster 940 nw monitor using VGA connectors and have the same problem using Karmic Koala.

i installed the Os using the safe graphic mode becouse in normal mode the display was corrupted and installation couldn't go on.

after updating the fully installed OS i activated ATI proprietary drivers to enable visual effects on desktop but the display have always been too bright. 

i am trying to apply the patch but i truly don't know how to . . . 

btw in the drivers/gpu/drm/radeon folder i can find only a file named radeon.ko is this normal?

You need to install the kernel source or try a ppa with a newer or patched kernel.

I confirm that the patch in comment #17 fixes the gamma problem on my RV100:
https://bugzilla.redhat.com/show_bug.cgi?id=583845

(In reply to comment #33)
.... ok, alex thanks a lot for your answer, even if i don't kow how to perform the actions that you suggested. i will give it a try tomorrow and post my results here asap.

A.

(In reply to comment #35)
Well i think i am managing it to get kernel 2.6.33.3 on my pc, let's see if i get it working..

(In reply to comment #36)
running new kernel now, but still no enhancements. now i see i have a lot of entries in the hardware drivers tool and the proprietary ati drivers won't install anymore ?!?! is it normal?

(In reply to comment #37)
> (In reply to comment #36)
> running new kernel now, but still no enhancements. now i see i have a lot of
> entries in the hardware drivers tool and the proprietary ati drivers won't
> install anymore ?!?! is it normal?

Are you saying you are still seeing the problem?  Did you apply the patch in comment 28?  The proprietary driver only works with a certain set of kernels.

(In reply to comment #38)
yeah still experiencing the trouble and atm i am installing all the updates found after reboot. in a few mins i will try applying the patch, not sure about result couse this is the first patch i apply in my life, any hint would be appreciated.
BTW i am following a how to apply patches found on LinuxHQ and adapting those procedures to my case.
wish me good luck ^_^

Created attachment 35322 [details]
patching results

tried to patch but i get an error at line 28 or 29

(In reply to comment #40)
an insane idea runs through my head:
i opened atom.c and found the two sections of the code where the changes should go, what happens if i manually apply the patch modifying the file? i think that lines with a minus sign should be erased and lines with a plus should be inserted, is it right? is it dangerous? (of course it is è_é )

TY

if you are using a git tree:
git am <patch>
if not, you can manually apply with:
patch -p1 -i <patch>
Alternatively, you can apply by hand. the '-' lines are removed and the '+' lines are added.

(In reply to comment #42)
thanks alex, manually added the differences between the files.
i found that the atom.c was already patched except for the ", tmp;" of the first difference in both the chunks of code, anyway nothing happened and the colours on my display are still very bright.
moreover with the new kernel there is no way to activate any driver for the videocard and everithing moves really slow.

any other hint for me? willing to try anything.

at worst i will wait for lucid lynx final release and update to it, might get things better isn't it?

(In reply to comment #43)
just installed lucid lynx from a USB pendrive everything goes wonderfully but colours are still bright, do i have to apply the patch in LL?

(In reply to comment #44)
checked out but atom.c still is not there, by searching the whole filesystem there is no sign of this file so patch cannot be applied.

You need to install the kernel source package.  I don't know whether LL has this patch or not.

(In reply to comment #46)
tried to sudo apt-get install kernel-sources but i get an error, translated from italian it says: 
"The package kernel-source doens't have available versions, but it is named by another package. This could mean that the package is missing, obsolete or it is only available inside another source."

(In reply to comment #46)
installed kernel source from package manager, still having bright colors and missing atom.c ....

(In reply to comment #48)
don't know if this is relevant:
- even as root i can't obtain the rom of my video card with instruction posted before.
- Atom.c does not appear anywhere in my system.
- i did any previous step using proprietary drivers but even now that i uninstalled them there is nothing different.
- radeontool instruction give always "mapping ctrl region" response.
- avivotool regmatch 0x7ef4 and avivotool regmatch 0x7ff4 give segmentation fault error.

looks like i got many strange things going on here !?!?

(In reply to comment #49)
> (In reply to comment #48)
> don't know if this is relevant:
> - even as root i can't obtain the rom of my video card with instruction posted
> before.

replace <pci bus id> with the bus id of your video card (look it up with lspci).


> - Atom.c does not appear anywhere in my system.

You apparently don't have the kernel source installed then.  Also it's atom.c (note the case).

> - i did any previous step using proprietary drivers but even now that i
> uninstalled them there is nothing different.
> - radeontool instruction give always "mapping ctrl region" response.
> - avivotool regmatch 0x7ef4 and avivotool regmatch 0x7ff4 give segmentation
> fault error.

You need to run avivotool as root.  radeontool isn't useful for your card.

Created attachment 35360 [details]
my vcard rom

(In reply to comment #50)
here is the rom finally! thanks for the help, hope this is useful.

maybe this is not the right place to ask for it, but how can i install the kernel sources then? i did it from the package manager but apparently it didn't work.

and here is what happens with avivotool:

kbkang@kbuntu:~$ sudo -s
[sudo] password for kbkang: 
root@kbuntu:~# avivotool regmatch 0x7ef4
mapping fb region
Segmentation fault
root@kbuntu:~# avivotool regmatch 0x7ff4
mapping fb region
Segmentation fault
root@kbuntu:~#

(In reply to comment #51)
well my pc got stuck and i dont know if it's becouse of something i did while trying to compile and install the new kernel, i reached the step where i had to make modules_install, and all was going just perfect. then i moved the bzimage in the boot directory and waited till this morning to edit the grub config file but as i woke up and turned on the pc: surprise! i will post as soon as i get my pc back to life!
thanks alex for all your patience!
thanks to everyone that posted here!
see you soon!

(In reply to comment #52)
well i'm back, don't know why but bios was upset with my usb keyboard, now i moved it to an external hub and everything's fine again.
as of now i'm running this kernel: 2.6.32.11+drm33.2, and i applyed the patch to the atom.c file before compiling and installing the sources. but now the driver is set to the opensource ATI radeon instead of the fglrx, trying to install the wich fails always and resulting in no change in colours but no acceleration at all. i'm running out of hope...

(In reply to comment #53)
back again. as i had no news since my last post maybe i was misunderstood. the problem is not solved and i still have very bright colours. is there anything else i can do? i will try once more reinstalling ubuntu, the kernel and the patch, but i doubt it will work... i'll give some feedback in a few days.

Thanks!

Just curious.. How come this fix was not commited yet to the repository, and the bug closed? My understanding is that many users have confirmed that the fix is correct and does fix the problem, or am I missing something?

[for me i can't confirm, i didn't test the patch but many others have]

(In reply to comment #55)
I don't know, i keep retrying but the problem is still there...

(In reply to comment #55)
> Just curious.. How come this fix was not commited yet to the repository, and
> the bug closed? My understanding is that many users have confirmed that the fix
> is correct and does fix the problem, or am I missing something?

The patches have been committed to the kernel.

Maybe this bug old/obsolete, but I recently got new Radeon HD 4350, and can confirm this bug. Display is too bright with gamma = 1, lowering gamma do not solve problem because window decorations become dark, red becomes tomato, buttons on forms in browser or other apps are white (using gtk theme 'Mist'). How I can fix this?

(In reply to comment #58)
> Maybe this bug old/obsolete, but I recently got new Radeon HD 4350, and can
> confirm this bug. Display is too bright with gamma = 1, lowering gamma do not
> solve problem because window decorations become dark, red becomes tomato,
> buttons on forms in browser or other apps are white (using gtk theme 'Mist').
> How I can fix this?

Make sure you have a new enough kernel with the patches mentioned in this bug 2.6.34 or newer should be ok.

(In reply to comment #58)
> Maybe this bug old/obsolete, but I recently got new Radeon HD 4350, and can
> confirm this bug. Display is too bright with gamma = 1, lowering gamma do not
> solve problem because window decorations become dark, red becomes tomato,
> buttons on forms in browser or other apps are white (using gtk theme 'Mist').
> How I can fix this?

Make sure you have a new enough kernel with the patches mentioned in this bug.  2.6.34 or newer should be ok.

(In reply to comment #60)
> Make sure you have a new enough kernel with the patches mentioned in this bug. 
> 2.6.34 or newer should be ok.

Yes, I have installed latest stable kernel 2.6.34. I use VGA adapter and UMS (KMS strangely freezes my X server with kernel panic when I shutdown/reboot my box. I will fix this later if possible).

(In reply to comment #61)

> Yes, I have installed latest stable kernel 2.6.34. I use VGA adapter and UMS
> (KMS strangely freezes my X server with kernel panic when I shutdown/reboot my
> box. I will fix this later if possible).

I fixed issue with KMS, but bug still visible, even with KMS.

(In reply to comment #62)
> (In reply to comment #61)
> 
> > Yes, I have installed latest stable kernel 2.6.34. I use VGA adapter and UMS
> > (KMS strangely freezes my X server with kernel panic when I shutdown/reboot my
> > box. I will fix this later if possible).
> 
> I fixed issue with KMS, but bug still visible, even with KMS.

Please attach a copy of your vbios as per the instructions in comment 9.  And attach the output of the following commands:
avivotool regmatch 0x7ef4
avivotool regmatch 0x7ff4

You can get avivotool here (part of the radeontool package):
http://cgit.freedesktop.org/~airlied/radeontool/

All commands must be run as root.

(In reply to comment #63)
> 
> Please attach a copy of your vbios as per the instructions in comment 9.  And
> attach the output of the following commands:
> avivotool regmatch 0x7ef4
> avivotool regmatch 0x7ff4
> 
> You can get avivotool here (part of the radeontool package):
> http://cgit.freedesktop.org/~airlied/radeontool/
> 
> All commands must be run as root.

Output of avivotool:
# avivotool regmatch 0x7ef4
0x7ef4	0x00221f00 (2236160)
# avivotool regmatch 0x7ff4
0x7ff4	0x00221f02 (2236162)

Created attachment 36589 [details]
vbios from Radeon HD 4350

rom vbios from Radeon HD 4350

Created attachment 36687 [details]
ROM of RV530

I have the same isuue with 06:00.0 VGA compatible controller: ATI Technologies Inc RV530 [Radeon X1600] on kernel 2.6.34

(In reply to comment #66)
> Created an attachment (id=36687) [details]
> ROM of RV530
> 
> I have the same isuue with 06:00.0 VGA compatible controller: ATI Technologies
> Inc RV530 [Radeon X1600] on kernel 2.6.34

I'm using same model now and it works fine.
lspci:
02:00.0 VGA compatible controller: ATI Technologies Inc RV530 [Radeon X1600]

> Please attach a copy of your vbios as per the instructions in comment 9.  And
> attach the output of the following commands:
> avivotool regmatch 0x7ef4
> avivotool regmatch 0x7ff4
> 
> You can get avivotool here (part of the radeontool package):
> http://cgit.freedesktop.org/~airlied/radeontool/
> 
> All commands must be run as root.

>Output of avivotool:
># avivotool regmatch 0x7ef4
>0x7ef4    0x00221f00 (2236160)
># avivotool regmatch 0x7ff4
>0x7ff4    0x00221f02 (2236162)

>vbios from Radeon HD 4350

Please answer anything :| Yes or no.
I can't use new adapter because it hurts my eyes.

Hmm… Looks like i have a hardware bug :( BIOS logo on POST is green, but should be red. Sorry.

(In reply to comment #68)
> >Output of avivotool:
> ># avivotool regmatch 0x7ef4
> >0x7ef4    0x00221f00 (2236160)
> ># avivotool regmatch 0x7ff4
> >0x7ff4    0x00221f02 (2236162)

> Please answer anything :| Yes or no.
> I can't use new adapter because it hurts my eyes.

The values there look fine.  Does:
avivotool regset 0x7ff4 0x00222002
help?  or
avivotool regset 0x7ff4 0x00202002

(In reply to comment #70)
> (In reply to comment #68)
> > >Output of avivotool:
> > ># avivotool regmatch 0x7ef4
> > >0x7ef4    0x00221f00 (2236160)
> > ># avivotool regmatch 0x7ff4
> > >0x7ff4    0x00221f02 (2236162)
> 
> > Please answer anything :| Yes or no.
> > I can't use new adapter because it hurts my eyes.
> 
> The values there look fine.  Does:
> avivotool regset 0x7ff4 0x00222002
> help?  or
> avivotool regset 0x7ff4 0x00202002

No. This don't help.
I can compare the colors with my old video card and I'm sure - the problem appears when I boot with new Radeon HD adapter.

(In reply to comment #71)
> 
> No. This don't help.
> I can compare the colors with my old video card and I'm sure - the problem
> appears when I boot with new Radeon HD adapter.

Same behavior when I booted Ubuntu 10.04 livecd. On HD 4350 screen brighter comparing with old X1600.

This is fixed in kms.