Ati Radeon Xpress 200M + Edgy + FGLRX working how to

[d-E-a-D]

Ok, finally it's working! let's show how!
Running on HP Pavilion Dv5176.

Right now i'm out off time, but when i have some, i'll try to install ATI drivers from ATI site into version V 7.04
Right now just activate all options in the repositories, do a update in System -> Administration -> Update Manager, go to System -> Administration ->Restricted Drivers Manager and activate ATI driver.
NOTE: DESKTOP EFFECTS DOES NOT WORK !!!!! ATI DOES NOT SUPPORT COMPOSITE EXTENSION!!

1st of all sorry 4 my bad English.
2nd I have Sideport ONLY activated.
3rd !!!! EDGY 32bit Fresh Install !!!! Users said that it works on 64bit too!

Download ati-driver-installer-8.32.5-x86.x86_64 driver from ati.

Now, step by step:

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf_bkp

sudo gedit /etc/X11/xorg.conf

Add this to xorg.conf:

Section "Extensions"

    Option  "Composite" "Disable"

EndSection

!!!! GO TO THE FOLDER WERE YOU DOWNLOAD ATI DRIVER !!!!

sudo apt-get update
sudo apt-get install module-assistant build-essential
sudo apt-get install fakeroot dh-make debhelper debconf libstdc++5 linux-headers-$(uname -r)

sudo ln -sf bash /bin/sh
bash ati-driver-installer-8.32.5-x86.x86_64.run --buildpkg Ubuntu/edgy
sudo ln -sf dash /bin/sh

sudo dpkg -i xorg-driver-fglrx_8.32.5-1*.deb
sudo dpkg -i fglrx-kernel-source_8.32.5-1*.deb
sudo dpkg -i fglrx-control_8.32.5-1*.deb

sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a

sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv

sudo shutdown -r now

And that should work!

Now, let's get XGL and Beryl working:
Add this to your sources.list (/etc/apt/sources.list):

deb http://ubuntu.beryl-project.org/ edgy main

wget http://ubuntu.beryl-project.org/root@lupine.me.uk.gpg -O- | sudo apt-key add -
sudo apt-get update

sudo apt-get install xserver-xgl
sudo apt-get install beryl emerald-themes

sudo gedit /usr/local/bin/startxgl.sh

Add this to startxgl.sh:

#!/bin/sh
Xgl :1 -fullscreen -ac -accel xv:pbuffer -accel glx:pbuffer &
DISPLAY=:1
exec dbus-launch --exit-with-session gnome-session

sudo chmod a+x /usr/local/bin/startxgl.sh
sudo gedit /usr/share/xsessions/xgl.desktop

Add this to xgl.desktop:

[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Comment=Start an Xgl Session by d-E-a-D
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application

Logout with ctrl + alt + backspace

Change to session "Xgl" and login.
Run:

beryl-manager

If you want you can add it to System - Preferences - Sessions to your startup.

Off topic, if you have MY LAPTOP SERIES with broadcom Wireless adapter, just do this after a fresh install:

sudo aptitude install bcm43xx-fwcutter
sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh

And your broadcom will be working right away!

If you wan't to use a wireless manager, compwiz18 is tha man! just download his *.deb at here.

EDIT: I stop using XGL and Beryl just because i need to use 3d at full throttle... i'm waiting for AIGLX and COMPIZ under ATI.

TESTED ati-driver-installer-8.33.6-x86.x86_64 AND IT WORKS!!!! just follow this how to but with *8.33.6* instead *8.32.5*!!!!
Note: XGL NOT TESTED.

Cumps

[ramasdf123]

hope fully this work, i am going to give it a shot now and replay back

[kcallis]

Was that for the 64-bit version or the 32-bit version of Edgy? Because I no longer see 32-bit version at ati.amd.com... All of the mergers... How is one suppose to keep up?

[ramasdf123]

awesome it works on the 1st try so i'ill keep this updated if anything happens...

i would like to correct something though

sudo ln -sf bash /bin/sh
bash ati-driver-installer-8.32.5-x86.x86_64 --buildpkg Ubuntu/edgy
sudo ln -sf dash /bin/sh

I had to change it to

sudo ln -sf bash ~/Desktop
bash ati-driver-installer-8.32.5-x86.x86_64 --buildpkg Ubuntu/edgy
sudo ln -sf dash ~/Desktop

and when you download the ati-driver-installer-8.32.5-x86.x86_64 it is going to be *.run extention, you have to remove that to make it work

for now it works so if it does crash i will update

thank d-E-a-D

[KLineD]

Many many thanks to you d-e-a-d for this excellent guide. I was having a lot of troubles getting my ati card to work in edgy fresh install

[thx_1138]

Good starter guide for users just wanting to get this done with minimal searching, I basically went through all these steps and the only thing I would add to it would be is to make sure the xgl.desktop file has been enabled to executed. This can be done by simply navigating to the /usr/share/xsessions/ folder and right clicking on the xgl.desktop icon and selecting Properties. Once there head to the properties tab and click on the checkbox next to Execute. Xgl would not load up properly unless I had enabled this.

I used these pages in which point out the exact same steps on this post
http://wiki.cchtml.com/index.php/Ubu...allation_Guide
http://wiki.beryl-project.org/wiki/I...buntu/Edgy/XGL
http://lhansen.blogspot.com/2006/10/...untu-edgy.html

Enjoy the 3D desktop effects!

[d-E-a-D]

I've edited the post, it should be working now.

Now I'm trying to use compiz instead of beryl because its much stable, but i still getting problems, if anyone could make it working please report.

Cumps

[robin.w]

Thanks a lot and congratulation d_E_a_D!!!

You rock, you're king! Finally I can enjoy beryl as well!!!

All good

Robin

[paulobear]

Hi dEaD --

Your post was a breath of fresh air -- mostly.

The ATI driver now works for my HP DV8110us notebook -- an AMD64 Turion machine. Woohoo! I don't get a splash screen after I login -- all I see is the XWindows hashed screen and an 'x' mouse cursor. The Gnome desktop manager starts up just fine.

But when I try to run beryl-manager, it catches signal 11, and all is messed up at that point. There are no window widgets, (close, minimize, etc) and the desktop menu bar and the workspace bar is gone. I can log out and then log back in to a Gnome XGL session so all is not lost.

I did try to set up my graphics memory to use both sideport and uma (udma??) and added 128Mb of shared memory (also tried no shared memory). This resulted in the splash screen (after the login screen) to go pure white with an "arrow" mouse cursor. It changes to the normal Gnome round/busy mouse cursor for a moment and then changes back. There is some disk activity, and then it all just stops. The mouse is mobile, but my desktop never shows up.

I didn't start from a clean Edgy install. I had attempted to install fglrx/compiz some time earlier after I'd installed Edgy. So there may be something messed up there. I'll try to re-install some time this week.

All in all, I'm a very happy camper. The fact that fglrx is working is a great step for me!

PaulOBear

[compwiz18]

Originally Posted by paulobear Hi dEaD -- Your post was a breath of fresh air -- mostly. The ATI driver now works for my HP DV8110us notebook -- an AMD64 Turion machine. Woohoo! I don't get a splash screen after I login -- all I see is the XWindows hashed screen and an 'x' mouse cursor. The Gnome desktop manager starts up just fine. But when I try to run beryl-manager, it catches signal 11, and all is messed up at that point. There are no window widgets, (close, minimize, etc) and the desktop menu bar and the workspace bar is gone. I can log out and then log back in to a Gnome XGL session so all is not lost. I did try to set up my graphics memory to use both sideport and uma (udma??) and added 128Mb of shared memory (also tried no shared memory). This resulted in the splash screen (after the login screen) to go pure white with an "arrow" mouse cursor. It changes to the normal Gnome round/busy mouse cursor for a moment and then changes back. There is some disk activity, and then it all just stops. The mouse is mobile, but my desktop never shows up. I didn't start from a clean Edgy install. I had attempted to install fglrx/compiz some time earlier after I'd installed Edgy. So there may be something messed up there. I'll try to re-install some time this week. All in all, I'm a very happy camper. The fact that fglrx is working is a great step for me! PaulOBear

Are you running Ubuntu 64bit? If so then you have a bug that isn't the fault of this tutorial.