Ugly Watermark Issue "AMD Unsupported hardware"

[n3Cre0]

I updated yesterday from the official Ubuntu ATI drivers to the just released 9.1 and I got this ugly watermark now saying "AMD Unsupported hardware" and I can't get rid of it! It's driving me nuts! I already tried to solve it by replacing /etc/ati/control and /etc/ati/signature with the new, correct versions (using --extract on the installer) but no go.

OS: Ubuntu Linux 8.10 x86
GPU: 01:00.0 VGA compatible controller: ATI Technologies Inc M26 [Radeon Mobility X700 XL (PCIE)]

I installed using these commands:

chmod +x ati-driver-installer-*.run
./ati-driver-installer-*-x86.x86_64.run --buildpkg Ubuntu/intrepid
dpkg -i fglrx-kernel-source_*.deb
dpkg -i fglrx-amdcccle_*.deb
dpkg -i fglrx-modaliases_*.deb
dpkg -i libamdxvba1_*.deb
dpkg -i xorg-driver-fglrx_*.deb
rm -R *fglrx*
rm *amd*

There are no other problems however. I just want to get rid of the watermark.
Any (other) suggestions?

[Kano]

You can use the control file from another driver which had no watermark.

[n3Cre0]

Thanks - that worked!

I extracted the 8.12 control file and use that one now.

[Kano]

Btw. you see the PCI ID only with

lspci -nn

not pure lspci.

[n3Cre0]

When I execute `lspci -nn | grep ATI` I get

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M26 [Radeon Mobility X700 XL (PCIE)] [1002:564f]

What is it needed?

[Kano]

1002:564f means:

Vendor 1002 = ATI

Product 564f

Interestingly that ID is inside the fglrx_drv.so which I parse to get the whitelist for my script. Why ATI does not allow that ID in the control file I absolutely have no idea. That signature/control check is just crap to annoy users without deeper knowledge.

[bridgman]

We're looking into this internally and should know more on Monday.

[n3Cre0]

All right! Thank you all

Great driver btw, no issues whatsoever.

[Kitof]

Same ugly watermark here with Sapphire 2600 HD XT AGP :

03:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV 630 XT AGP [Radeon HD 2600 XT AGP] [1002:9586]

[Kitof]

We're looking into this internally and should know more on Monday.

Any news ?