Not Registered Login | Register

New AMD drivers are out

New AMD drivers are out13. September 2007, 00:08

the new AMD graphics drivers with the promised speed improvements are out.

you can grab them here.

In order to build proper Ubuntu packages from them do the following:

$ sudo apt-get install module-assistant
$ ./ --buildpkg Ubuntu/gutsy
$ sudo dpkg -i fglrx-kernel-source_8.41.7-1_i386.deb xorg-driver-fglrx_8.41.7-1_i386.deb
$ sudo module-assistant 

Attention you dont need the module-assistant step since fglrx 8.443

now select the fglrx-kernel module in module-assistant and then build/ install it. Now you have cleanly installed the fglrx driver, which removable/ upgradable through synaptic.

Remember that the kernel module will conflict with the module in linux-restricted-modules. In order to clean this up add fglrx to /etc/default/linux-restricted-modules-common. so it reads


then reboot and run

$ sudo depmod

thanks to Matteo for this hint.

Anonymous 13. September 2007, 09:00

So you will either have to remove the latter entirely or delete the
fglrx module manually. (quite hacky)

You can disable Ubuntu's shipped fglrx driver by adding it to /etc/default/linux-restricted-modules-common

like so


(and then run "sudo /etc/init.d/linux-restricted-modules-common start" or reboot)

Matteo Zandi

MadMan2k 13. September 2007, 10:23

the problem is not that fglrx will be loaded at boot, but that modprobe will try to load the module from volatile/fglrx.ko (the version from restricted modules) instead of misc/fglrx.ko (the new version) as long as the restricted-modules package is installed. I have not yet found a way to change the priority of this...

Anonymous 13. September 2007, 12:48

I have not yet found a way to change the priority of this...

if you disable it by editing /etc/default/linux-restricted-modules-common, you won't have any fglrx.ko in volatile dir (after reboot)

if you still have problems "sudo depmod -ae" might help


Anonymous 13. September 2007, 17:52

What about amd 64 bit archtecture?? I follow step by step the guide but 1 did not succeed. My ati video card is no more working when X is started.

MadMan2k 13. September 2007, 19:38

though I did not try it on a 64bit machine the guide basically should work if the installer spits out 64bit packages.

In order to get back to a working system, you have to change the Driver line in your /etc/X11/xorg.conf from fglrx to ati. Now you can graphically undo the steps in order to revert to the fgrx driver from the repository.

Anonymous 14. September 2007, 09:00

$ ./ --buildpkg Ubuntu/gutsy
should read:
$ bash ./ --buildpkg Ubuntu/gutsy
or am i mistaken?

MadMan2k 14. September 2007, 10:24

if you don't explicitly call the script with a program, bash will try to guess it using the sha-bang(#!/bin/sh), which evaluates on ubuntu to dash.

Anonymous 04. October 2007, 18:36

hello, I tried following the steps posted above, but it gives me an error
"unsupported architecture"
Fresh Gutsy beta install :(

Anonymous 08. October 2007, 21:51

Following the unofficial ATI drivers guide on you should install other packages to solve dependencies:

sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5 linux-headers-generic

Anonymous 08. January 2008, 01:07

/usr/share/modass/packages/fglrx-kernel-source: 1: debian/rules: not found

This is the error that I get when I try to build the package with the module-assistant. Any suggestions?