On Wed, 28 Mar 2001, Erik Steffl wrote:
> <sort-of-rant on which packages to get>
> this problem is more general, there are some 'groups' of packages that
> all provide same/similar functionality but it's not clear which ones
> work together, netscape packages are similar (or at least were when I
> was installing netscape).
> </sort-of-rant>
Agreed. These mesa and glide packages are very confusing. Netscape is
similar. I don't know if it could be resolved by better naming, or if
maybe there needs to be some documentation explaining the twisted logic
<g> behind these intricately related groups of packages.
Do others find that the current combination of naming and dependancies are
sufficient to make things clear?
> dpkg: mesag3-glide2: dependency problems, but removing anyway as you
> request:
> xbase-clients depends on libgl1; however:
> Package libgl1 is not installed.
> Package mesag3-glide2 which provides libgl1 is to be removed.
>
> I got these for all the packages (AFAIK, lot of them: xpp, libfltk1,
> xscreensaver-gl, vreng, xlockmore-gl, kdebase etc...)
How I dealt with this: first, I used apt-get. I acutally got rid of the
old packages first, and it uninstalled lots of packages that I didn't want
to get rid of, like libwine, wine, xbase-clients, xf86setup, and
xscreensaver-gl. That made me a little bit nervous, but when I
reinstalled them, it actually installed xlibmesa3 and xlibmesa-dev; that's
how I found those packages in the first place.
> how do I test it now? I got the following info from glxinfo:
The glx stuff looks good. Do you also see the OpenGL/Mesa stuff in
the glxinfo output? Like this?
OpenGL vendor string: VA Linux Systems, Inc.
OpenGL renderer string: Mesa DRI Voodoo3 20001101
OpenGL version string: 1.2 Mesa 3.4
OpenGL extensions:
GL_ARB_multitexture, GL_ARB_tranpose_matrix, GL_EXT_abgr,
GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array,
GL_EXT_histogram,
...
> btw what do the Xlib messages mean? why would it try to connect to
> :0.0 server???
I have no idea. I've been running exclusively on display 0, so I don't
know why it's trying to use display 0 when you're obviously wanting to use
display 2. Weird. Maybe someone else can help?
> > Also, make sure that your kernel supports AGP (CONFIG_AGP is m or y; and
>
> I have PCI video card - does this mean that PCI cards don't work?
Ooo...that never even crossed my mind. I just saw on some web page that
you need AGP support, so I included it; I don't know if works on a PCI
card. Again, it's outside of my experience. Maybe someone else knows?
You should probably try to find out the anwer to this from the XFree86
people.
> I noticed that already. that's quite annoying - is this a temporary
> limitation?
I don't know. I think it might actually be a limitation of the
hardware. That's jsut a guess though.
Sorry I couldn't be a little more helpful. My only knowledge comes from
my experience in getting mine to work. Obviously, our situations are a
little different.
--
David Steinberg -o) In a world without walls
Computer Engineering Undergrad, UBC / \ and fences, who needs
[EMAIL PROTECTED] _\_v Windows and Gates?
