You are not logged in.
Hi,
wondering if anyone has inbstalled the catalyst 9.1, which is in extra now. Wondering if thjis solved the "blackscreen" problem.
fr
Offline
I have X1600Pro AGP, catalyst 9.1 and:
I had "blackscreens" when I put "TexturedVideoSync" "on" in xorg.conf
Also when I had "@kdm hal (...)" in rc.conf I had randomly blacksceens, change it to "hal @kdm (...)" solve problem for me.
My xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "aticonfig-Screen[0]-0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "AIGLX" "On"
EndSection
Section "Files"
#RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dbe"
Load "dri"
#Load "record"
Load "extmod"
Load "xtrap"
Load "glx"
Load "GLcore"
Load "freetype"
#Load "drm"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "pl"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
Option "XaaNoOffscreenPixmaps" "true"
Option "UseFastTLS" "2"
Option "TexturedVideo" "On"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
BusID "PCI:1: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
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "On"
EndSection
With this everything works fine.
PS. sorry for my "english"
Offline
If you look in the AMD/ATI thread, you'll see that a few people had problems with 9.1. Your mileage may vary, but I would recommend not upgrading.
[ lamy + pilot ] [ arch64 | wmii ] [ ati + amd ]
Offline
@above: Upgrade, just don't 'pacman -Sc', so you can go back if necessary...
Offline
I'm wondering why there's no x64_86 package of catalyst 9.1?
Offline
Because if you notice 32bit packages get out sooner as more people use it and more devs are allocated to maintain packages I guess, x86_64 is less used I believe so less devs are allocated (sounds logic). Just give it some time.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Because if you notice 32bit packages get out sooner as more people use it and more devs are allocated to maintain packages I guess, x86_64 is less used I believe so less devs are allocated (sounds logic). Just give it some time.
And because devs running 64-bit can compile both 64 and 32-bit, but 32-bit devs can't (easily) compile for 64-bit.
Offline
I'm wondering why there's no x64_86 package of catalyst 9.1?
See http://bbs.archlinux.org/viewtopic.php? … 18#p491818
In summary, AndyRTR reports that "9-1 is broken on x86_64", but Mikko777 found a workaround.
I'm not using it myself yet - waiting anxiously for an official release.
Offline
It more or less worked fine for my on x86_64. I just had to copy one file to another location and it was easy street. You can easily update the PKGBUILD and update that way.
Peter
Offline
Hm. You mean get a hold of the i686 PKGBUILD and tweak that for x86_64?
...How would I do this from an x86_64 platform?
Last edited by aaaantoine (2009-02-05 20:51:39)
Offline
I just took the x86_64 PKGBUILD for 8.12 and changed the version number to 9.1. I updated the md5sums, and viola!
Peter
Offline