Re: HOWTO: module-assistant on amd64

[Knut Auvor Grythe <fglrx at auvor dot no>]

On Sun, Feb 20, 2005 at 10:52:19PM +0200, Alexandru Fomin wrote:
> I had the impression that if you don't want to have a chrooted Debian
>  i386 installed around, all you need to do to have an almost working
>  32bit environment is to install the ia32-libs package, and this should
>  be the debian-amd64 supported way.

Aha, that explains it. I had never seen that path before, nor heard of
the ia32-libs package ;-)

On a different note: The amount of libs there was pretty limited. I
tried to run some 32-bit programs, but they all missed some libs. Adding
the paths to the libs in my chroot directory to /etc/ld.so.conf helped a
bit, and I was able to run a 32-bit glxgears. To run doom3 I need to
chroot, but that is no surprise. I guess ia32-libs has pretty limited
use, but following the path conventions can't hurt anyway :-)

> If you have the extra disk space to spare and you install a boostraped
>  i386 environment, I think you can also install the fglrx-driver
>  package, directly from Flavio's site, inside the chrooted environment.
>  (PS: I never used deboostrap or cdeboostrap and I do not own yet an
>  amd64 system so I could be totally wrong here; please forgive me)

Good point. I already had an fglrx-driver packages installed in my
chroot (I just use my old 32-bit installation as my chroot), but forgot
that the version differed from my amd64 one. I upgraded my fglrx-driver
package in the chroot directory and everything seemed to work fine. This
has the added advantage of not messing up dpkg in the chroot too :-)

Of course, if the ia32 packages should happen to differ in version from
the amd64 ones, things will probably break. This is probably an unlikely
event (as the driver isn't updated *that* often), and the packages do
not know anything about each other anyway, so one would just have to
watch out manually. A mismatch would probably be even more unlikely if
rufus just mirrored the ia32 packages he used for making the amd64 ones,
so they were always in sync. That way chroot users could use the same
mirror both on the amd64 system and inside the chroot, preventing a
premature upgrade of the ia32 package. I think I'll suggest that to him.

Bottom line: Remove gotcha about the weird path, add gotcha about
keeping the fglrd-driver installation inside the chroot in sync with
what you have on your amd64 system.

> >  # Create the magic symlink so the driver finds the libs =)
> >  ln -s lib /usr/X11R6/lib64
>
> can you please try a different approach and let us know if it's working?
>
> [stuff about /etc/X11/Xsession.d/70fglrx-libgl_driver_path]

It didn't. It just falls back to Mesa Indirect :-|

-- 
Knut Auvor Grythe