[gutsy][beta] Cannot get accelerated video, radeon 9200

I guess the proprietary fglrx driver has not been completely removed. See https://help.ubuntu.com/community/RadeonDriver#head-229f59879c2a2b6c6635d1e189706d97f836b879

Thanks for the quick update.

Yesterday night's adept update, which updated the xorg ati driver, had no effect on the problem.

Double-checked as per the instructions, fglrx package was removed ; but just to be sure, I did the following : aptitude remove --purge on the flgrx driver, then aptitude remove on libgl1-mesa-dri|glx.

This installed the -swx11 packages, confirmed by glxinfo reporting client and vendor string to "Brian Paul".

Redid an aptitude install libgl1-mesa-glx libgl1-mesa-dri, dpkg-reconfigure -phigh xserver-xorg and ctrl-alt-BS. Same as before, undefined symbol in r200_dri.so.

If it helps, ls -l /usr/lib/dri :
(...list up to Matrox driver)
-rw-r--r-- 1 root root 2384680 2007-08-17 00:44 r128_dri.so
-rw-r--r-- 1 root root 2485384 2007-08-17 00:44 r200_dri.so
-rw-r--r-- 1 root root 2388968 2007-08-17 00:44 r300_dri.so
-rw-r--r-- 1 root root 2436008 2007-08-17 00:44 radeon_dri.so
(list from S3 driver...)

Please let me know of any additional info I could provide.

Why do you have the swx packages installed?

Try apt-get install --reinstall <package> for all the packages you mention above. I am not sure you need all of these though, for instance libglit

Try "dpkg -S libGL" to see if you have an alien GL library somewhere.

The swx packages were only installed temporarily (to satisfy dependecies) while the mesa ones had been removed (from aptitude) just to be sure everything was cleaned up.

Apt-get reinstall on libgl1-mesa-glx libgl1-mesa-dri hasn't solved the problem.

To be on the safe side, I tried apt-get removing libgl1-mesa-dri, which also took X, KDE and xfce4 down, then reinstalling kubuntu-desktop letting apt-get handle the details... problem is still there.

I've downloaded the beta CD and booted off it to confirm that I *do* have DRI when running the liveCD.

I also have triple-checked that I don't have any fglrx-related package in the way. Everything reports uninstalled from apt-get, and confirmed by comparing dpkg -L and actual filesystem that no binary was left behind.

dpkg -S libGL output (after complete takedown and reinstall of X and mesa-dri) :

libgl1-mesa-glx: /usr/lib/libGL.so.1
ia32-libs: /usr/lib32/libGLU.so.1.3.070001
libglu1-mesa: /usr/lib/libGLU.so.1.3.070001
ia32-libs: /usr/lib32/libGL.so.1
ia32-libs: /usr/lib32/libGLU.so.1
libgl1-mesa-glx: /usr/lib/libGL.so.1.2
googleearth: /usr/lib/googleearth/libGLU.so.1
ia32-libs: /usr/lib32/libGL.so.1.2
xserver-xorg-core: /usr/lib/xorg/modules/extensions/libGLcore.so
libglu1-mesa: /usr/lib/libGLU.so.1

Right now backing up prior to a complete reinstall from liveCD...

This seems to be a 32bit vs 64bit issue. Was the live CD a 64-bit version?

The liveCD is indeed 64-bit (AMD64-Desktop version), as is the installed system (first installed 64-bit Edgy, net-updated to Feisty then Gutsy).

I know embarrassingly little about 64bit systems: Is the ia32-libs package needed?

It is required to run 32-bit apps on 64-bits systems. VMWare for
instance, or the Macromedia Flash plugin. It does provide the
lib32/dri/* drivers which I guess would be needed by a 32-bit version
of Xorg / libGL.

Since I'm running a 64-bit system, libGL complains that
/usr/lib32/r200_dri.so is 32-bit (per my first message), as expected.
The 64-bit /usr/lib/dri/r200_dri.so is provided by libgl1-mesa-dri
(64-bit pkg).

Now if I understand correctly the debug info above, libGL complains
about r200_dri.so while attempting to load it. The only "libGL" that I
could find is libGL.so.1 which is provided either by xorg-driver-fglrx
(removed and purged) *or* libgl1-mesa-glx (reinstalled several times).
Looks like they're not in sync but I can't see how that happens.

Anyway, I'll be away from that machine for a couple of weeks, and
everything is backed up. I still have tomorrow to look into this,
otherwise I'll probably just do a CD reinstall when I get back. Gutsy
will be final by then.

Try:
 dpkg -l '*fglrx*'
and
 locate fglrx
to see if there is still some evil proprietary bits around.

You're right, it looks like a mismatch between files that usually are provided by libgl1-mesa-glx and libgl1-mesa-dri.

On 10/3/07, Tormod Volden <email address hidden> wrote:
> Try:
> dpkg -l '*fglrx*'

un xfree86-driver-fglrx
rc xorg-driver-fglrx 7.1.0-8.37.6+2.6.22.4-12.4 Video
driver for ATI graphics accelerators

> and
> locate fglrx
> to see if there is still some evil proprietary bits around.

Ah, we might be on to something here. Aside from archives, packages
and other out-of-the-way stuff, found these :

/etc/X11/Xsession.d/70fglrx_32bit_dri
/etc/X11/Xsession.d/70fglrx_32bit_dri/fglrx.xsession
/etc/X11/Xsession.d/10fglrx
/etc/X11/Xsession.d/10fglrx.dpkg-old
/etc/X11/fglrx.xsession
/etc/acpi/events/fglrx-lid-aticonfig
/etc/acpi/events/fglrx-ac-aticonfig
/etc/acpi/fglrx-powermode.sh
/etc/default/fglrx
/etc/ati/fglrxprofiles.csv
/etc/ati/fglrxrc
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx/libfglrx_ip.a.GCC4
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx/firegl_public.o
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx/fglrx.mod.o

looks like something was *not* cleaned up correctly ; and considering
the kernel version above, this looks like the feisty fglrx wasn't
zapped when upgrading to gutsy. Still weird since nothing should be
calling them, but they're here.
(...)
Removing them manually didn't help. I'm still getting the same error in glxinfo.

Use "apt-get remove --purge <package>" to also remove the configuration files.

> Use "apt-get remove --purge <package>" to also remove the configuration
> files.

Did that every time. As far as these old fglrx (2.6.20-related) were
concerned, I had to remove them by hand since apt saw the packages as
"not installed" in the first place. I used --purge on every removal
mentioned previously.

Let's just drop it for now. As I mentioned previously, I'll be away
for a while, and I don't mind reinstalling fresh (actually should
clean up some cruft anyway...) when I get back.

Thanks for your time, efforts and help.