[Pkg-fglrx-devel] Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Bertrand Marc]

Yes sorry I moved them a bit faster than I should have. And I plan to
upgrade the repository to get a nice release (other than unstable) so
it will change again... but the repository will stay here :
http://pkg-fglrx.alioth.debian.org/debian/

I don't know much about these diversions, I'll have a look tonight. I
just took the 9-8 package in unstable and changed the Xorg version to
do this backport, so there must be the same issue in unstable. Patrick
do you know about this ?

Bertrand

2009/8/20, Gary Dale <garydale at rogers.com>:
> Bertrand Marc wrote:
>> No sorry, I only have 32bits. But you can easily build amd64 backports
>> with the following :
>>
>> #install the build dependancies
>> sudo aptitude build-dep fglrx-driver
>>
>> #download the source of the backport
>> wget http://beberking.free.fr/fglrx/fglrx-driver_9-8-1+bpo1.diff.gz
>> wget http://beberking.free.fr/fglrx/fglrx-driver_9-8-1+bpo1.dsc
>> wget
>> http://ftp.de.debian.org/debian/pool/non-free/f/fglrx-driver/fglrx-driver_9-8.orig.tar.gz
>>
>>
>>
>> #Extract and build the package
>> dpkg-source -x fglrx-driver_9-8-1+bpo1.dsc
>> cd fglrx-driver-9-8/
>> dpkg-buildpackage -b
>>
>> That should do the trick!
>>
>> Bertrand
>>
> OK, the build seems to have worked. I'm left with these files:
>
> -rw-r--r-- 1 root root   139062 2009-08-19 22:23
> fglrx-atieventsd_9-8-1+bpo1_amd64.deb
> -rw-r--r-- 1 root root  7026142 2009-08-19 22:23
> fglrx-control_9-8-1+bpo1_amd64.deb
> -rw-r--r-- 1 root root 13784818 2009-08-19 22:23
> fglrx-driver_9-8-1+bpo1_amd64.deb
> -rw-r--r-- 1 root root   195036 2009-08-19 22:23
> fglrx-glx_9-8-1+bpo1_amd64.deb
> -rw-r--r-- 1 root root  7093634 2009-08-19 22:23
> fglrx-glx-ia32_9-8-1+bpo1_amd64.deb
> -rw-r--r-- 1 root root  1547372 2009-08-19 22:23
> fglrx-source_9-8-1+bpo1_amd64.deb
>
>
> I can dpkg -i the atieventsd but none of the others install - most
> complain "dpkg-divert: cannot open diversions: No such file or
> directory". Is there something else I need to do to get this to work?
>
>