You are not logged in.

#1 2005-12-22 19:34:47

Komodo
Member
From: Oxford, UK
Registered: 2005-11-03
Posts: 674

Random ATI cop-out

I decided to install OpenOffice 2 to give it a whirl, and it kept not running upon installation; I tried reinstalling it a few times, but to no avail.

When I next booted up, I'd lost direct rendering with my ATI card! Why on earth would that have happened?

The only other things that I'd done before the reboot were cleaning out /var/cache/pacman/pkg and /tmp.

I'd be extremely grateful for ANY help with this, as I'm dying to get back to modelling with Blender and playing Enemy Territory, lol :'(

When I run ET, it gives me this:

ET 2.60 linux-i386 Mar 10 2005
----- FS_Startup -----
Current search path:
/home/.etwolf/etmain
/opt/enemy-territory/etmain/pak2.pk3 (22 files)
/opt/enemy-territory/etmain/pak1.pk3 (10 files)
/opt/enemy-territory/etmain/pak0.pk3 (3725 files)
/opt/enemy-territory/etmain/mp_bin.pk3 (6 files)
/opt/enemy-territory/etmain

----------------------
3763 files in pk3 files
execing default.cfg
couldn't exec language.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok

------- Input Initialization -------
Joystick is not active.
------------------------------------
Bypassing CD checks
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
...loading libGL.so.1: Initializing OpenGL display
...setting mode 4: 800 600
Using XFree86-VidModeExtension Version 2.2
Xlib:  extension "XFree86-DGA" missing on display ":0.0".
Failed to detect XF86DGA Mouse
XFree86-VidModeExtension Activated at 800x600
Using 8/8/8 Color bits, 24 depth, 0 stencil display.
GL_RENDERER: Mesa GLX Indirect


***********************************************************
 You are using software Mesa (no hardware acceleration)!   
 Driver DLL used: libGL.so.1
 If this is intentional, add
       "+set r_allowSoftwareGL 1"
 to the command line when starting the game.
***********************************************************
...WARNING: could not set the given mode (4)
Initializing OpenGL display
...setting mode 3: 640 480
Using XFree86-VidModeExtension Version 2.2
XFree86-VidModeExtension Activated at 640x480
Received signal 11, exiting...

I hope that's of some help :S


.oO Komodo Dave Oo.

Offline

#2 2005-12-22 19:47:57

postlogic
Member
Registered: 2005-02-24
Posts: 410
Website

Re: Random ATI cop-out

Looks like you are running Mesa, and not the DRI. First, run fglrxinfo and make sure it is running Mesa (although I can see it is), then run lsmod and check that the fglrx module is running.

You didnt do ANYTHING? Not upgrade the kernel or similar? You could also try pacman -Sy ati-drivers again in any case. If you installed some package with mesa as the dependency, it will overwrite your libGL and similar. Atleast it used to.

Offline

#3 2005-12-22 20:49:48

Komodo
Member
From: Oxford, UK
Registered: 2005-11-03
Posts: 674

Re: Random ATI cop-out

well, I reinstalled my ati-drivers (I use the script from the ATI site) and everything's ok again now... I really can't see why there would have been a problem though... if anyone has any idea, I'd like to know, for future reference :?


.oO Komodo Dave Oo.

Offline

Board footer

Powered by FluxBB