first impressions with 8.9

[energyman]

It installs fine with 2.6.26.5. Start is ok. Restarting X from vt freezes the box (slight regression).
XV+composite got A LOT worse. From 'bad to bearable' to 'unbearable bad'. It is a pure flickerfest with the window it was above when starting showing up in every second frame.
vegastrike_cvs had a performance problem with big space stations. Frames got as low as 7 or 11 with fighter barracks. Performance increased a lot to 25FPS at the same point.
resizing windows is like always.
Desktop feels pretty smooth.

amdcccle spamms Xorg.0.log on startup and makes X crawl like a snail in a salt mine. Extremly slow for a couple of seconds (10 or 15). Then ok. Still - Xorg.0.log full of crap:
II) fglrx(0): EDID vendor "ACR", prod id 44404
(II) fglrx(0): Using hsync ranges from config file
(II) fglrx(0): Using vrefresh ranges from config file
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync
(II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (
(II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (
(II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (3
(II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (3
(II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (3
(II) fglrx(0): Modeline "640x480"x0.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (3
(II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (3
(II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync
(II) fglrx(0): Modeline "1024x768"x0.0 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsy
(II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsy
(II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsy
(II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (
(II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (
(II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (
(II) fglrx(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsyn
(II) fglrx(0): Modeline "1280x960"x59.9 101.25 1280 1360 1488 1696 960 963 967 996 -hsync +vs
(II) fglrx(0): Modeline "1152x864"x74.8 104.00 1152 1224 1344 1536 864 867 871 905 -hsync +vs
(II) fglrx(0): Modeline "1440x900"x59.9 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vs
(II) fglrx(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vs
(II) fglrx(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsyn
(II) fglrx(0): Modeline "1280x720"x59.9 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vs
(II) fglrx(0): Modeline "1360x765"x59.8 84.50 1360 1432 1568 1776 765 768 773 795 -hsync +vs

yeah fine. You tested it on startup. But no, that is not enough ....

[bridgman]

Still - Xorg.0.log full of crap:
II) fglrx(0): EDID vendor "ACR", prod id 44404
(II) fglrx(0): Using hsync ranges from config file
(II) fglrx(0): Using vrefresh ranges from config file
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync
(II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (
(II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (
(II) fglrx(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (3
(II) fglrx(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (3
(II) fglrx(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (3
(II) fglrx(0): Modeline "640x480"x0.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (3
(II) fglrx(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (3
(II) fglrx(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync
(II) fglrx(0): Modeline "1024x768"x0.0 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsy
(II) fglrx(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsy
(II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsy
(II) fglrx(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (
(II) fglrx(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (
(II) fglrx(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (
(II) fglrx(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsyn
(II) fglrx(0): Modeline "1280x960"x59.9 101.25 1280 1360 1488 1696 960 963 967 996 -hsync +vs
(II) fglrx(0): Modeline "1152x864"x74.8 104.00 1152 1224 1344 1536 864 867 871 905 -hsync +vs
(II) fglrx(0): Modeline "1440x900"x59.9 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vs
(II) fglrx(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vs
(II) fglrx(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsyn
(II) fglrx(0): Modeline "1280x720"x59.9 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vs
(II) fglrx(0): Modeline "1360x765"x59.8 84.50 1360 1432 1568 1776 765 768 773 795 -hsync +vs

yeah fine. You tested it on startup. But no, that is not enough ....

Sorry if this is a dumb question, but which part of the log is the "crap" you mentioned ?

[doubledr]

Sorry if this is a dumb question, but which part of the log is the "crap" you mentioned ?

I think he is saying those "fglrx(0): Modeline" lines

[maligor]

Sorry if this is a dumb question, but which part of the log is the "crap" you mentioned ?

grep 1680x1050\"x60 Xorg.0.log | wc -l
33

As in: It prints the full list 33 times in the log. And then there's the strange 0.0 refreshrates it seems to calculate from somewhere.

[bridgman]

Ahh, that makes sense. I know that the server seems to be making repeated RandR calls which result in redundant log messages, but 33 seems like a lot (I normally see 3-6 copies per boot with the open source drivers). Thanks !

[energyman]

what maligor said.

After boot I have two of this modeline instances in Xorg.0.l0g.
I start amdcccle, wait 10sec, amdcccle pops up, Xorg.0.log is filled with tha modelines stuff.

before amdcccle:
ls -lh /var/log/Xorg.0.log
-rw-r--r-- 1 root root 44K 18. Sep 20:27 /var/log/Xorg.0.log

after amdcccle:
ls -lh /var/log/Xorg.0.log
-rw-r--r-- 1 root root 105K 18. Sep 20:52 /var/log/Xorg.0.log

[chrisr]

Isn't this new libdri.so going to conflict with the libdri.so in the xorg-x11-server-Xorg package?

[abolabo]

first impression - wrong video picture (blinking screen) (http://lh4.ggpht.com/abolabo/SNY1abpg1eI/AAAAAAAAAIo/DDwqfCQwuSw/s800/Screenshot.jpg).

in xorg.log i found that

(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72

If experimenting with compiz X will die.

Ubuntu 8.04
RADEON HD 3470

[Dandel]

i did a few checks on the error and other details related to fglrx with my laptop, and however i found almost no log issues whatsoever.
dandel@dandel-laptop:/var/log$ grep \(WW\) Xorg.0.log | wc -l
88
dandel@dandel-laptop:/var/log$ grep \(WW\)\ AIGLX:\ 3D Xorg.0.log | wc -l
80
dandel@dandel-laptop:/var/log$ grep Modeline Xorg.0.log | wc -l
22
dandel@dandel-laptop:/var/log$ ls -lah Xorg.0.log
-rw-r--r-- 1 root root 45K 2008-09-22 12:50 Xorg.0.log
dandel@dandel-laptop:/var/log$ amdcccle
dandel@dandel-laptop:/var/log$ ls -lah Xorg.0.log
-rw-r--r-- 1 root root 45K 2008-09-22 12:50 Xorg.0.log
dandel@dandel-laptop:/var/log$




as for amdcccle i got no bloat from using that either, although i do have compiz disabled on this machine.
Toshiba Satellite P305D-S8828

as for a quick question, what is the system spec your using, energyman. ( it'll help the amd dev know more about what to test with )

[energyman]

AMD X2 6000+, AlieveNF5-esata2+, 4gb ram. Gecube HD3870. Gentoo.
KDE 4.1.66. X.Org version: 1.4.2.

xorg.conf:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "aticonfig-Screen[0]-0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
RgbPath "/usr/lib64/X11/rgb"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
Load "evdev"
EndSection

Section "InputDevice"

Identifier "Mouse0"
Driver "evdev"
Option "CorePointer"
Option "Name" "Logitech, Inc. MX610 Laser Cordless Mouse"
Option "evBits" "+1-2"
Option "keyBits" "~272-287"
Option "relBits" "~0-2 ~6 ~8"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
Option "XkbLayout" "de"
Option "Device" "/dev/input/event2"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"

# Option "EnablePageFlip" "on"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:4:0:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

[forum1793]

I'm having mixed results with 8.9 on 780g (hd3200). mplayer and xine seem to work. Mythtv is mixed. At first it worked OK. Then it got jumbled as it did with Catatlyst 8.6-8.8. Just tried it again and it is resizing screen automatically such that the text is too big and it cannot be read. Resolution currently at 1400 x 1050. I'll try others to see if problem also in those.

[forum1793]

Tried mythtv with other X screen configurations. Mythfrontend seems to change screen resolution back to 1280x768 and then pulls up fonts too big so only part of mythtv menu is seen. Every once in a while the checkerboard of doom still happens.