Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

AMD Graphics on Debian 7.4

75 views
Skip to first unread message

ray

unread,
Apr 11, 2014, 11:30:01 PM4/11/14
to
The netinstall did not recognize the HD 7770 card.

The AMD Catalyst notes page states the supported distros to be:
Red Hat Enterprise Linux Suite 6.3 and 6.4
SUSE Linux Enterprise 11 SP3
OpenSUSE 11.4 and 12.1
Ubuntu 12.04.2 and 13.04

So I looked for what needs to be done to get drivers working on Debian 7.4.

I downloaded the Catalyst installation per:
http://support.amd.com/en-us/kb-articles/Pages/Catalyst-Linux-Installer-Notes.aspx#

Then:
sudo sh ./amd-catalyst-13.12-linux-x86.x86_64.run --listpkg

which produces:

Debian Packages:
Debian/sid
Debian/unstable
Debian/etch
Debian/stable
Debian/lenny
Debian/testing
Debian/experimental

Well, I am running wheezy, Debian 7.4. So I tried:
sh ./amd-catalyst-13.12-linux-x86.x86_64.run --buildpkg Debian/experimental

which produced:
Generating package: Debian/experimental
Error: Distro Version entered incorrectly or not supported, use --listpkg to identify valid distro versions

I tried the same thing with Debian/wheezy, and got the same message.

Any idea how I may get the card to work in 7.4?

What may be the challenges of installing one of:
Debian/lenny
Debian/testing
Debian/experimental

then installing the Catalyst package, then upgrading to 7.4?

Ray

-------------------------

MB Big Bang-XPower II, CPU Intel i7-3930K CPU @ 3.20GHz x12,
GPU Sapphire 7770, RAM 32GB, 1 TB HDD, 4 ea 64 GB SSD, PSU 850W,
Windows 8, Debian 7.4 (wheezy) 64-bit, GNOME 3.4.2


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/520a9a82-aa4a-4da0...@googlegroups.com

Gary Dale

unread,
Apr 12, 2014, 12:00:02 AM4/12/14
to
If you read what you wrote, it says that the driver supports Debian/testing and Debian/stable. While these are the same and Debian/jessie and Debian/wheezy, it doesn't mean that the script recognizes them as that. Try using the same wording that the .run script uses for your version (which is not experimental BTW).

However, the install should recognize a 7770 card at least enough to install. At worst it would be a slow VESA mode. Then you have the choice of upgrading to the open source driver or the closed source one. I prefer the open source one - less hassle - but you may have a different need.



--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/5348B994...@torfree.net

Patrick Bartek

unread,
Apr 12, 2014, 12:00:02 AM4/12/14
to
On Fri, 11 Apr 2014, ray wrote:

> The netinstall did not recognize the HD 7770 card.
>
> [snip]
>
> Then:
> sudo sh ./amd-catalyst-13.12-linux-x86.x86_64.run --listpkg
>
> which produces:
>
> Debian Packages:
> Debian/sid
> Debian/unstable
> Debian/etch
> Debian/stable
> Debian/lenny
> Debian/testing
> Debian/experimental
>
> Well, I am running wheezy, Debian 7.4. So I tried:
> sh ./amd-catalyst-13.12-linux-x86.x86_64.run --buildpkg
> Debian/experimental
> [snip]
> Any idea how I may get the card to work in 7.4?

Have you tried the Debian/stable package? Wheezy is the current Stable.

B


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20140411205...@debian7.boseck208.net

Lisi Reisz

unread,
Apr 12, 2014, 5:20:02 AM4/12/14
to
On Saturday 12 April 2014 04:04:29 ray wrote:
> Well, I am running wheezy, Debian 7.4.  So I tried:
> sh ./amd-catalyst-13.12-linux-x86.x86_64.run --buildpkg
> Debian/experimental

This doesn't make sense. Wheezy is Stable, so surely:

sh ./amd-catalyst-13.12-linux-x86.x86_64.run --buildpkg Debian/stable

assuming that line to be otherwise correct.

> Error: Distro Version entered incorrectly or not supported, use
> --listpkg to identify valid distro versions

Yes, the error was that you needed "stable", certainly
not "experimental"!

Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201404121015.0...@gmail.com

ray

unread,
Apr 12, 2014, 11:00:01 AM4/12/14
to

> Yes, the error was that you needed "stable", certainly
> not "experimental"!
>

OK, I tried:
Generating package: Debian/stable
./packages/Debian/ati-packager.sh: 1: ./packages/Debian/ati-packager.sh: dpkg-architecture: not found
Error: unsupported architecture:

Just to confirm:
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.4 (wheezy)
Release: 7.4
Codename: wheezy

Yes, wheezy is stable; today. But at the time the driver package was built, what would have been 'stable'?

Ray


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20c85e5e-e13f-45e1...@googlegroups.com

Curt

unread,
Apr 12, 2014, 1:00:02 PM4/12/14
to
On 2014-04-12, ray <r...@aarden.us> wrote:
>
> Yes, wheezy is stable; today. But at the time the driver package was
> built, what would have been 'stable'?
>

I deduce squeeze.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/slrnlkirro...@einstein.electron.org

Reco

unread,
Apr 12, 2014, 1:00:02 PM4/12/14
to
Hi.

On Sat, 12 Apr 2014 07:38:14 -0700 (PDT)
ray <r...@aarden.us> wrote:

> ./packages/Debian/ati-packager.sh: 1: ./packages/Debian/ati-packager.sh: dpkg-architecture: not found

Install 'dpkg-dev' package to solve this.

Reco


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20140412205241.1be4...@gmail.com

Bruno Schneider

unread,
Apr 12, 2014, 2:00:02 PM4/12/14
to
On Sat, Apr 12, 2014 at 11:38 AM, ray wrote:
>
> Yes, wheezy is stable; today. But at the time the driver package was built, what would have been 'stable'?
>

Ray, why don't you install the fglrx driver from repositories?

I'm having my own problems with that driver, but since I use testing,
I'll post them in a different thread.

--
Bruno Schneider
http://www.dcc.ufla.br/~bruno/


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/CAP1wdQsKLBEiTvBuPS2xoJK-...@mail.gmail.com

Lisi Reisz

unread,
Apr 12, 2014, 6:00:01 PM4/12/14
to
On Saturday 12 April 2014 15:38:14 ray wrote:
> Yes, wheezy is stable; today.  But at the time the driver package
> was built, what would have been 'stable'?

Try testing. If the driver is an old driver, Wheezy may have been
Testing when the driver was released. Wheezy was released as Stable
on 4th May 2013.

Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201404122256.1...@gmail.com

Lisi Reisz

unread,
Apr 12, 2014, 6:30:02 PM4/12/14
to
On Saturday 12 April 2014 15:38:14 ray wrote:
> OK, I tried:
> Generating package: Debian/stable
> ./packages/Debian/ati-packager.sh: 1:
> ./packages/Debian/ati-packager.sh: dpkg-architecture: not found

> ****Error: unsupported architecture:****
(my stars)

I haven't been reading this properly. Sorry. :-( Are your distro,
your driver and your CPU all the same architecture? It is
complaining about the architecture, not the distro version.

Have you got multiarch installed?

It *was* complainung about the distro version:

Generating package: Debian/experimental
Error: Distro Version entered incorrectly or not supported,
use --listpkg to identify valid distro versions

Anyhow, it looks as though you do indeed need Wheezy - you have got
one step further down the line, it has accepted your distro version
and is now complaining about architecture. Try installing multiarch.

Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201404122318.2...@gmail.com

Lisi Reisz

unread,
Apr 12, 2014, 6:30:02 PM4/12/14
to
On Saturday 12 April 2014 23:18:26 Lisi Reisz wrote:
> On Saturday 12 April 2014 15:38:14 ray wrote:
> > OK, I tried:
> > Generating package: Debian/stable
> > ./packages/Debian/ati-packager.sh: 1:
> > ./packages/Debian/ati-packager.sh: dpkg-architecture: not found
> >
> > ****Error: unsupported architecture:****
>
> (my stars)
>
> I haven't been reading this properly. Sorry. :-( Are your distro,
> your driver and your CPU all the same architecture? It is
> complaining about the architecture, not the distro version.
>
> Have you got multiarch installed?
>
> It *was* complainung about the distro version:
complaining
>
> Generating package: Debian/experimental
> Error: Distro Version entered incorrectly or not supported,
> use --listpkg to identify valid distro versions
For Wheezy read stable:
> Anyhow, it looks as though you do indeed need Wheezy - you have got
> one step further down the line, it has accepted your distro version
> and is now complaining about architecture. Try installing
> multiarch.
>
> Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201404122323.2...@gmail.com

ray

unread,
Apr 12, 2014, 10:50:01 PM4/12/14
to
> > ****Error: unsupported architecture:****
>
> I haven't been reading this properly. Sorry. :-( Are your distro,
>
> your driver and your CPU all the same architecture?

Yes, from the dpkg --print-architecture --> amd64, the CPU is an Intel i7-3930K, and the Catalyst package is amd-catalyst-13.12-linux-x86.x86_64.run.


>It is complaining about the architecture, not the distro version.

> Have you got multiarch installed?

Not that I know of. So I did the following:

# dpkg --print-architecture
amd64

# dpkg --print-foreign-architectures
# dpkg --add-architecture i386
# dpkg --print-architecture
amd64

# dpkg --print-foreign-architectures
i386

apt-get update
Hit http://ftp.us.debian.org wheezy Release.gpg
...<snip>
Fetched 6,647 kB in 18s (357 kB/s)
Reading package lists... Done


Then:

# sh ./amd-catalyst-13.12-linux-x86.x86_64.run --buildpkg Debian/stable
Created directory fglrx-install.hrcfIz
Verifying archive integrity... All good.
Uncompressing AMD Catalyst(TM) Proprietary Driver-13.251.......
...
Generating package: Debian/stable
./packages/Debian/ati-packager.sh: 1: ./packages/Debian/ati-packager.sh: dpkg-architecture: not found
Error: unsupported architecture:
Removing temporary directory: fglrx-install.hrcfIz

I have looked but can't find what 'dpkg-architecture: not found' means, none the less, how to address it.

Ray


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/aef41e08-4c22-4b37...@googlegroups.com

Lisi Reisz

unread,
Apr 13, 2014, 6:20:01 AM4/13/14
to
Would it be worth just trying installing multiarch? With one of the
apt family. (I use aptitude). I agree that it is not obviously
needed, but it is apparently not there, and the problem now is
something to do with the architecture.

Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201404131116.1...@gmail.com

ray

unread,
Apr 13, 2014, 2:50:02 PM4/13/14
to
> Would it be worth just trying installing multiarch? With one of the
> apt family. (I use aptitude). I agree that it is not obviously

# apt-get install multiarch
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package multiarch

https://wiki.debian.org/Multiarch/Implementation says:
Using multiarch

"To enable the installation of multiarch binaries, apt and dpkg need configuration changes. For example, if you have an amd64 system that you want to install i386 libraries onto, do the following:

multiarch support is present from dpkg 1.16.2 (or 1.16.0 in Ubuntu) and apt 0.8.13.

run dpkg --add-architecture i386

run apt-get update to refresh the package cache with the newly added architecture"

This seems to only provide for dpkg multiarch awareness and not the implementation. From the above referenced webpage, it looks like the packages (Catalyst) must be built to use this.

Just for record, https://wiki.debian.org/Multiarch/Bootstrapping addresses how to assemble multiarch awareness but all the content was produced 3 years ago and appears to no longer be needed due to Debain maturation.
https://wiki.debian.org/ATIProprietary#wheezy
I updated to:

deb http://http.debian.net/debian/ wheezy main contrib non-free

Ran:aptitude update

with no errors,
and:
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') fglrx-driver

which ran without error except for the initial emission:
No candidate version found for fglrx-driver
No candidate version found for fglrx-driver
So I tried:
# apt-get install fglrx-modules-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package fglrx-modules-dkms


Similarly,
# apt-get install fglrx-driver
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package fglrx-driver is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'fglrx-driver' has no installation candidate

I did see a reference to i386 files on http://wiki.cchtml.com/index.php/Debian:
# sudo apt-get remove --purge xserver-xorg-video-radeon
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
hyphen-en-us libfs6 x11-apps x11-session-utils x11-xfs-utils xinit xorg
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
task-desktop* task-gnome-desktop* xserver-xorg-video-all*
xserver-xorg-video-ati* xserver-xorg-video-radeon*
0 upgraded, 0 newly installed, 5 to remove and 9 not upgraded.
After this operation, 1,998 kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 137565 files and directories currently installed.)
Removing task-gnome-desktop ...
Removing task-desktop ...
Removing xserver-xorg-video-all ...
Removing xserver-xorg-video-ati ...
Removing xserver-xorg-video-radeon ...
Purging configuration files for xserver-xorg-video-radeon ...
Processing triggers for man-db ...

And followed this up with:
sudo apt-get install fglrx-driver fglrx-control fglrx-glx fglrx-atieventsd fglrx-modules-dkms

which produced:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package fglrx-glx is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package fglrx-driver is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'fglrx-driver' has no installation candidate
E: Unable to locate package fglrx-control
E: Package 'fglrx-glx' has no installation candidate
E: Unable to locate package fglrx-atieventsd
E: Unable to locate package fglrx-modules-dkms

>From the same site, to get ia32 libraries:
sudo apt-get install fglrx-glx-ia32
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package fglrx-glx-ia32 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'fglrx-glx-ia32' has no installation candidate

It looks like there is a challenge with doing something with fglrx.

Am I missing something here?

I found an alternative at: https://wiki.debian.org/Installing_ATI_fglrx_legacy_with_latest_kernel

This is a year old but it addressing building the driver package. Is there any problem with this approach?

Thanks for all the input,
Ray







Ray


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/c654bac5-f549-4f22...@googlegroups.com

Ric Moore

unread,
Apr 13, 2014, 3:30:02 PM4/13/14
to
On 04/13/2014 02:27 PM, ray wrote:
> Am I missing something here? I found an alternative at:
> https://wiki.debian.org/Installing_ATI_fglrx_legacy_with_latest_kernel
> This is a year old but it addressing building the driver package. Is
> there any problem with this approach? Thanks for all the input, Ray Ray
Do you have Synaptic installed?? Use that to hunt down and install your
packages. If the wheezy version fails you then try the run package ...as
a last resort. Or, upgrade to jessie to legally get the latest and
greatest. That is what I did to get the newer versions of my nVidia
drivers and VLC. As a plus, you stay within the deb package scheme of
things. Just make darn sure you do the upgrade in text terminal mode,
with X stopped totally. Ric

--

My father, Victor Moore (Vic) used to say:

"There are two Great Sins in the world...

..the Sin of Ignorance, and the Sin of Stupidity.

Only the former may be overcome." R.I.P. Dad.

https://linuxcounter.net/cert/44256.png

X-oldie-warning: Toothless but still vicious



--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/534AE587...@gmail.com

ray

unread,
Apr 13, 2014, 8:30:02 PM4/13/14
to
> Do you have Synaptic installed?? Use that to hunt down and install your
> packages. If the wheezy version fails you then try the run package ...as
> a last resort. Or, upgrade to jessie to legally get the latest and
> greatest. That is what I did to get the newer versions of my nVidia
> drivers and VLC. As a plus, you stay within the deb package scheme of
> things. Just make darn sure you do the upgrade in text terminal mode,
> with X stopped totally.

I did not find the fglrx package in Synaptic. I did find some multiarch packages which I installed. But the initial error of not finding the architecture was persistent.

Ray


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/e0a29707-c069-4c60...@googlegroups.com

Marko Randjelovic

unread,
Apr 14, 2014, 2:20:02 AM4/14/14
to
On Sun, 13 Apr 2014 11:27:31 -0700 (PDT)
ray <r...@aarden.us> wrote:

> Am I missing something here?

Of course you are, in one of previous posts you got a solution but looks
like you missed it :)

--
http://markorandjelovic.hopto.org


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20140414080...@eunet.rs

Bruno Schneider

unread,
Apr 14, 2014, 9:50:03 AM4/14/14
to
On Sun, Apr 13, 2014 at 9:01 PM, ray wrote:
>
> I did not find the fglrx package in Synaptic. I did find some multiarch packages which I installed. But the initial error of not finding the architecture was persistent.
>

It is in the non-free section. Perhaps you have not include that
section in your sources.

It seems you were trying to install a 32bits module on a 64bits system.

--
Bruno Schneider
http://www.dcc.ufla.br/~bruno/


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/CAP1wdQtYrWMyoAd4e8v5rp5s...@mail.gmail.com

ray

unread,
Apr 14, 2014, 11:50:03 AM4/14/14
to
Marko,

> Of course you are, in one of previous posts you got a solution but looks
> like you missed it :)

Thank you for responding. I have overlooked it a couple times now; going back through, I don't see it. Please suggest what it was, I can't see what I am missing.

Ray


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/ac5e535b-c76d-4273...@googlegroups.com

Ric Moore

unread,
Apr 14, 2014, 7:00:02 PM4/14/14
to
On 04/13/2014 08:01 PM, ray wrote:
>> Do you have Synaptic installed?? Use that to hunt down and install your
>> packages. If the wheezy version fails you then try the run package ...as
>> a last resort. Or, upgrade to jessie to legally get the latest and
>> greatest. That is what I did to get the newer versions of my nVidia
>> drivers and VLC. As a plus, you stay within the deb package scheme of
>> things. Just make darn sure you do the upgrade in text terminal mode,
>> with X stopped totally.
> I did not find the fglrx package in Synaptic. I did find some multiarch packages which I installed. But the initial error of not finding the architecture was persistent.
Open synaptic again and type amd in the search bar. I'm seeing over a
dozen fglrx related packages. If you have a 64bit install you really
don't want a 32bit graphical system, especially if you use DKMS to
update your driver during kernel upgrades.


--

My father, Victor Moore (Vic) used to say:

"There are two Great Sins in the world...

..the Sin of Ignorance, and the Sin of Stupidity.

Only the former may be overcome." R.I.P. Dad.

https://linuxcounter.net/cert/44256.png

X-oldie-warning: Toothless but still vicious



--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/534C666E...@gmail.com

Lisi Reisz

unread,
Apr 14, 2014, 7:30:02 PM4/14/14
to
On Sunday 13 April 2014 19:27:31 ray wrote:
> > Would it be worth just trying installing multiarch? With one of
> > the apt family. (I use aptitude). I agree that it is not
> > obviously
>
> # apt-get install multiarch
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package multiarch

lisi@Tux-II:~$ aptitude search multiarch
p binutils-multiarch - Binary utilities that
support multi-arch targe
p binutils-multiarch:i386 - Binary utilities that
support multi-arch targe
p gdb-multiarch - The GNU Debugger (with
support for multiple ar
p gdb-multiarch:i386 - The GNU Debugger (with
support for multiple ar
v multiarch-binutils -
v multiarch-binutils:i386 -
i A multiarch-support - Transitional package to
ensure multiarch compa
p multiarch-support:i386 - Transitional package to
ensure multiarch compa
v pango1.0-multiarch-modver-1.6.0 -
v pango1.0-multiarch-modver-1.6.0:i386 -
lisi@Tux-II:~$

You have to find the exact package and install it by name, not just
plug a word in and panic!! As you see, I have multiarch-support
installed. If you _can't_ see that I have multiarch-support
installed, and I am assuming too much, then I suggest that you read
up a bit on how to manage package managers.

Lisi


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201404150019.0...@gmail.com

ray

unread,
Apr 14, 2014, 9:00:01 PM4/14/14
to
> You have to find the exact package and install it by name, not just
>
> plug a word in and panic!! As you see, I have multiarch-support
>
> installed. If you _can't_ see that I have multiarch-support
>
> installed, and I am assuming too much, then I suggest that you read
>
> up a bit on how to manage package managers.

Thank you for the follow-up. I apologize for being so terse. Researching multiarch turned up no single package or even a suggestion of multiple specific files. I did find:

dpkg --add-architecture i386

This seemed like a multiarch solution but in fact did not resolve the ATI installation problem. The only clue I got was through Synaptic.

I found multiarch content using Synaptic. There were several packages as you indicated. When all packages were selected, some were marked in red. So I backed out and found which were not compatible due to red marks. It was not obvious why they were not compatible; when reviewing the descriptions, some had the same description but responded differently to selection matching. Through trial and error, I found the maximum set of components that could be mutually selected.

Obviously I didn't know what I was doing; just because I got all green lights didn't tell me the selection was the solution. Most troubling was with the maximum count, those left out were i386. This just doesn't seem correct; why is the alternate architecture (i386) not selectable? It would seem that without the i386 components, it really wouldn't be a multiarch solution. Or did I miss something (again)? Is there a sequence that these need to be installed under?

Ray


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/7d3baf75-4cfe-451b...@googlegroups.com
0 new messages