PDA

View Full Version : Ati Radeon 9600 + fglrx = BlackScreen of Death


MAXA_BG
March 3rd, 2008, 01:38 PM
Hi everyone!
This is my first post in the forum so I hope I get some help :)
I installed Ubuntu 7.10 last week (clean install...this is my first go at Linux and you could say that I'm a newbie) and since then I have been trying to enable the Desktop Effects.
If I install the Property Drivers I get a black screen before the login screen.
I have reconfigured xorg.conf maybe 10 times or more.
I have read topics that are similiar with my problem none seemd to help.
Googled like crazy still no result.
So if some one with the samo config had the problem please share how you fixed it.
lspci (onlu the video controlers:
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary)

Xorg.conf:
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "ATI Technologies Inc RV350 AP [Radeon 9600]"
Driver "ati"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "F720P"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc RV350 AP [Radeon 9600]"
Monitor "F720P"
DefaultDepth 24
SubSection "Display"
Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
EndSection
And please dont link me to google. You have to belive me I have tried a ton of guids and nothing helped.
Also I think its strange with the live CD of Sabayon I ahve the 3D Effects with XGL acc but Sabayon uses KDE could that solve it?

felker2
March 3rd, 2008, 03:22 PM
Are you sure you're using Ubuntu 7.10 and not Ubuntu 8.04 Alpha? Because I recognize the no-screen-output as a Ubuntu 8.04 Alpha problem, for which the bug-fix has been committed today.
For me, Ubuntu 7.10 with the prop.driver worked normally on my ATI X1250.

Ubuntu version check:

sander@fujitsu:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
sander@fujitsu:~$



Furthermore, your xorg.conf says "Driver "ati"", where I would expect 'fglrx'. Strange.

MAXA_BG
March 3rd, 2008, 05:05 PM
Its ati because when its fglrx I can't get to the logon screen.
maxa@MAXA-desktop:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

MAXA_BG
March 4th, 2008, 04:47 AM
A friend gave me an idea. I can boot Sabayon and look at the xorg.conf file and see what the differance is. But I'll have to wait for a while 'cause my DVD-RW broke :lolflag:

Distro Jockey
March 4th, 2008, 05:44 AM
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon 9600]
01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 9600] (Secondary)

I'm running the same card using the default Xorg drivers (i.e. ati) rather than fglrx and I have fully functional Desktop Effects (even Water Effect).

My xorg.conf is identical to yours in the relevant places as you can see below.

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "ATI Technologies Inc RV350 AR [Radeon 9600]"
Driver "ati"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "Philips 170S"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc RV350 AR [Radeon 9600]"
Monitor "Philips 170S"
DefaultDepth 24
SubSection "Display"
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
EndSection

When you go to
System > Preferences > Appearance > Visual Effects
what does it say / what can you do?

MAXA_BG
March 4th, 2008, 12:55 PM
Hmm thats strange. Now I am able to enable the effects but they are reaaaaaaly slow. And I can only see a whute sreen. Only way to fix it is to restart the PC and the effects are off :popcorn:
maxa@MAXA-desktop:~$ glxinfo | grep "direct rendering"
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
maxa@MAXA-desktop:~$

That would be the problem?
Now how to fix it....

Arilou
March 4th, 2008, 01:42 PM
Hmm thats strange. Now I am able to enable the effects but they are reaaaaaaly slow. And I can only see a whute sreen. Only way to fix it is to restart the PC and the effects are off :popcorn:
maxa@MAXA-desktop:~$ glxinfo | grep "direct rendering"
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
maxa@MAXA-desktop:~$

That would be the problem?
Now how to fix it....

Hi, I'm not very good at this, but I've been having the same troubles with a Radeon 9550, while I can't exactly solve your problem I can provide you with some links that have helped me a lot.

This link shows how to install ATI.com drivers, I recommend you erase all previous ones before trying this one, it runs Advanced Desktop Effects if you activate xserver-xgl, but x-server bugs (at least for me) some 3D options for gaming.
http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#Method_1:_Install_ the_Driver_the_Ubuntu_Way

If you're not a gamer then:
https://help.ubuntu.com/community/BinaryDriverHowto/ATI#head-117effcb5f0fbe8e10f40881bff1dbf7824a77b0
and then adding xserver-xgl
http://ubuntuforums.org/showthread.php?t=569654
should do it for you as it installs Ubuntu's radeon drivers (instead of ATI ones) and xserver-xgl seems to be fully compatible with those.

I hope this helps you even if it's only a bit. ^_^

MAXA_BG
March 4th, 2008, 05:19 PM
Nope i have tried these guids didn't help. Has any one had the wight cube problem? And how did they solve it?

MAXA_BG
March 5th, 2008, 05:24 AM
Update:Maneged to install the prop drivers but now I cant get rid of MESA
maxa@MAXA-desktop:~$ fglrxinfo -display :0
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (2.1 Mesa 7.0.1)

maxa@MAXA-desktop:~$

EDIT: I'm doing a fresh install tonight...I gues I have done a lot of bullshi* trying to get the effects going...I'm going to follow this Guide:
http://ubuntuforums.org/showthread.php?t=569654
The guide for Feisty - Gutsy helped me get the driver going but as you can expect I did some bullshi* and can't get it again.
I hope a fresh install will solve it.
EDIT:Effects working with prop drivers and fresh install