Re: fglrx 8.29.6 and Xorg 7.1.1 :: ABI major version mismatch
When I do a dist-upgrade there are a lot of xserver-xorg updates; and fglrx-kernel-src is also to be updated, but fglrx-driver is not updated - in fact it is marked for removal. fglrx-driver depends on xserver-xorg ( 1:7.0.99), so I'm wary to update at the moment; hopefully fglrx-driver will be updated soon. On Thu, Sep 21, 2006 at 03:10:14PM -0700, Max A. wrote: fglrx 8.29.6 claims to support Xorg 7.1 http://www2.ati.com/drivers/linux/linux_8.29.6.html But I cannot get it work because of the following error: (II) LoadModule: fglrx (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so (II) Module fglrx: vendor=FireGL - ATI Technologies Inc. compiled for 6.8.99.8, module version = 8.29.6 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (EE) module ABI major version (0) doesn't match the server's version (1) (II) UnloadModule: fglrx (II) Unloading /usr/lib/xorg/modules/drivers/fglrx_drv.so (EE) Failed to load module fglrx (module requirement mismatch, 0) Does anybody know how to fix that? -- Jesper Nyholm Jensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Wolfenstein: E-T on debian amd64 with ATI X800 Pro gfx?
Hi, I would like to run Wolfenstein: Enemy Territory on my amd64 system, as I had it running on my 32-bit debian before I upgraded to amd64. Is it at all possible? Some words about my setup: o HW: - AMD64 3200+, - ATI X800 Pro gfx card. o SW: - OS: debian amd64 unstable/sid, - Linux kernel: 2.6.15.7, - X: Xorg 7.0, - gfx driver: proprietary ATI binary driver v. 8.27.10 (kernel module compiled and loaded), - a 32-bit debian sid chroot, - Wolfenstein: E-T v. 2.60. chroot: is working. I installed mplayer and some codecs and was able to view a .wmv-file. Also, I installed firefox and a flash plugin and was able to view flash in firefox. 3D-acceleration: is working on amd64. I tried running 'ppracer' (on amd64, i.e. not in chroot) with and without the driver loaded - it runs fast with and slow without. I also tried installing and running 'ppracer' in my chroot, but it was slow, so it seems 3D-acceleration is not working for my chroot. Wolfenstein: Enemy Territory: is not working, neither in amd64 nor in the 32-bit chroot. Here is the output when run in chroot: == ET output begin = W: Failed to change to directory '/pack/fglrx/ati': No such file or directory W: Falling back to directory '/' I: [sid386 chroot] Running command: et ET 2.60 linux-i386 Mar 10 2005 - FS_Startup - Current search path: /home/nyholm/.etwolf/etmain /usr/local/games/enemy-territory/etmain/pak2.pk3 (22 files) /usr/local/games/enemy-territory/etmain/pak1.pk3 (10 files) /usr/local/games/enemy-territory/etmain/pak0.pk3 (3725 files) /usr/local/games/enemy-territory/etmain/mp_bin.pk3 (6 files) /usr/local/games/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 XF86DGA Mouse (Version 2.0) initialized 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 XF86DGA Mouse (Version 2.0) initialized XFree86-VidModeExtension Activated at 640x480 Received signal 11, exiting... == ET output end = Except for the first 3 lines the output is exactly the same in amd64. Any ideas? -- Jesper Nyholm Jensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wolfenstein: E-T on debian amd64 with ATI X800 Pro gfx?
On Sat, Aug 12, 2006 at 10:33:15AM +0100, Jo Shields wrote: Jo Shields wrote: Jesper Nyholm Jensen wrote: Hi, I would like to run Wolfenstein: Enemy Territory on my amd64 system, as I had it running on my 32-bit debian before I upgraded to amd64. Is it at all possible? Some words about my setup: o HW: - AMD64 3200+, - ATI X800 Pro gfx card. o SW: - OS: debian amd64 unstable/sid, - Linux kernel: 2.6.15.7, - X: Xorg 7.0, - gfx driver: proprietary ATI binary driver v. 8.27.10 (kernel module compiled and loaded), - a 32-bit debian sid chroot, - Wolfenstein: E-T v. 2.60. chroot: is working. I installed mplayer and some codecs and was able to view a .wmv-file. Also, I installed firefox and a flash plugin and was able to view flash in firefox. 3D-acceleration: is working on amd64. I tried running 'ppracer' (on amd64, i.e. not in chroot) with and without the driver loaded - it runs fast with and slow without. I also tried installing and running 'ppracer' in my chroot, but it was slow, so it seems 3D-acceleration is not working for my chroot. Wolfenstein: Enemy Territory: is not working, neither in amd64 nor in the 32-bit chroot. Here is the output when run in chroot: == ET output begin = W: Failed to change to directory '/pack/fglrx/ati': No such file or directory W: Falling back to directory '/' I: [sid386 chroot] Running command: et ET 2.60 linux-i386 Mar 10 2005 - FS_Startup - Current search path: /home/nyholm/.etwolf/etmain /usr/local/games/enemy-territory/etmain/pak2.pk3 (22 files) /usr/local/games/enemy-territory/etmain/pak1.pk3 (10 files) /usr/local/games/enemy-territory/etmain/pak0.pk3 (3725 files) /usr/local/games/enemy-territory/etmain/mp_bin.pk3 (6 files) /usr/local/games/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 XF86DGA Mouse (Version 2.0) initialized 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 XF86DGA Mouse (Version 2.0) initialized XFree86-VidModeExtension Activated at 640x480 Received signal 11, exiting... == ET output end = Except for the first 3 lines the output is exactly the same in amd64. Any ideas? 1) You need the ATI driver installed inside the chroot as well as outside it (as it provides replacement libGL files) 2) What does ls -l /usr/lib/libGL.so.1 say? 3) what does glxinfo | grep vendor say? Oh, and do 2 3 outside the chroot - I personally would avoid using a chroot unless absolutely neccessary, and I know that for games, a chroot isn't absolutely neccessary No chroot for ET you say; how would one go about that? 1) I was thinking I might have to, but hoping I wouldn't, because how do I build the ATI driver kernel module? I mean, what kernel source do I use; the source from amd64 or do I need to install a kernel source package for the chroot? 2) Outside chroot: $ ls -l /usr/lib/libGL.so.1 lrwxrwxrwx 1 root root 12 Aug 10 18:47 /usr/lib/libGL.so.1 - libGL.so.1.2 3) Outside chroot: $ glxinfo |grep vendor server glx vendor string: SGI client glx vendor string: ATI OpenGL vendor string: ATI Technologies Inc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wolfenstein: E-T on debian amd64 with ATI X800 Pro gfx?
On Sat, Aug 12, 2006 at 12:01:01PM +0100, Jo Shields wrote:
Jesper Nyholm Jensen wrote:
On Sat, Aug 12, 2006 at 10:33:15AM +0100, Jo Shields wrote:
Jo Shields wrote:
Jesper Nyholm Jensen wrote:
Hi,
I would like to run Wolfenstein: Enemy Territory on my amd64 system,
as I had it running on my 32-bit debian before I upgraded to amd64.
Is it at all possible?
Some words about my setup:
o HW: - AMD64 3200+,
- ATI X800 Pro gfx card.
o SW:
- OS: debian amd64 unstable/sid,
- Linux kernel: 2.6.15.7,
- X: Xorg 7.0,
- gfx driver: proprietary ATI binary driver v. 8.27.10 (kernel
module compiled and loaded),
- a 32-bit debian sid chroot,
- Wolfenstein: E-T v. 2.60.
chroot:
is working. I installed mplayer and some codecs and was able to
view a .wmv-file.
Also, I installed firefox and a flash plugin and was able to view
flash in firefox.
3D-acceleration:
is working on amd64. I tried running 'ppracer' (on amd64, i.e. not
in chroot) with and without
the driver loaded - it runs fast with and slow without. I also tried
installing and running 'ppracer' in my chroot, but it was slow, so it
seems 3D-acceleration is not working for my chroot.
Wolfenstein: Enemy Territory:
is not working, neither in amd64 nor in the 32-bit chroot. Here is the
output when run in chroot:
== ET output begin
= W: Failed to change to directory
'/pack/fglrx/ati': No such file or
directory
W: Falling back to directory '/'
I: [sid386 chroot] Running command: et
ET 2.60 linux-i386 Mar 10 2005
- FS_Startup -
Current search path:
/home/nyholm/.etwolf/etmain
/usr/local/games/enemy-territory/etmain/pak2.pk3 (22 files)
/usr/local/games/enemy-territory/etmain/pak1.pk3 (10 files)
/usr/local/games/enemy-territory/etmain/pak0.pk3 (3725 files)
/usr/local/games/enemy-territory/etmain/mp_bin.pk3 (6 files)
/usr/local/games/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
XF86DGA Mouse (Version 2.0) initialized
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
XF86DGA Mouse (Version 2.0) initialized
XFree86-VidModeExtension Activated at 640x480
Received signal 11, exiting...
== ET output end =
Except for the first 3 lines the output is exactly the same in amd64.
Any ideas?
1) You need the ATI driver installed inside the chroot as well as
outside it (as it provides replacement libGL files)
2) What does ls -l /usr/lib/libGL.so.1 say?
3) what does glxinfo | grep vendor say?
Oh, and do 2 3 outside the chroot - I personally would avoid using
a chroot unless absolutely neccessary, and I know that for games, a
chroot isn't absolutely neccessary
No chroot for ET you say; how would one go about that?
Um... just run the ET installer?
Tried that; installer runs with no problems, but running 'et' gives same result
as in the chroot.
1)
I was thinking I might have to, but hoping I wouldn't, because
how do I build the ATI driver kernel module? I mean, what kernel
source do I use; the source from amd64 or do I need to install a
kernel source package for the chroot?
You will need to build a dummy package which will satisfy the
dependancy, using equivs
Oh, I will have to look into that.
2)
Outside chroot:
$ ls -l /usr/lib/libGL.so.1
lrwxrwxrwx 1 root root 12 Aug 10 18:47 /usr/lib/libGL.so.1 -
libGL.so.1.2
Thinking about it, more relevant outside a chroot is
/emul/ia32-linux/usr/lib/libGL.so* - but generally, I'm pretty sure
libGL.so.1.2 is from Mesa, indicating a wider library problem - where
precisely did you get your fglrx-driver package from?
$ find / -name libGL.so\* -exec ls -al '{}' \;
-rw-r--r-- 1 root root 447560 May 29 04:56
/var/sid-386-chroot/usr/lib/libGL.so.1.2
lrwxrwxrwx 1 root root 12
Re: Wolfenstein: E-T on debian amd64 with ATI X800 Pro gfx?
On Sat, Aug 12, 2006 at 02:14:06PM +0200, Jesper Nyholm Jensen wrote: On Sat, Aug 12, 2006 at 12:45:52PM +0100, Jo Shields wrote: Jesper Nyholm Jensen wrote: On Sat, Aug 12, 2006 at 12:01:01PM +0100, Jo Shields wrote: Jesper Nyholm Jensen wrote: On Sat, Aug 12, 2006 at 10:33:15AM +0100, Jo Shields wrote: Jo Shields wrote: Jesper Nyholm Jensen wrote: Hi, I would like to run Wolfenstein: Enemy Territory on my amd64 system, as I had it running on my 32-bit debian before I upgraded to amd64. Is it at all possible? Some words about my setup: o HW: - AMD64 3200+, - ATI X800 Pro gfx card. o SW: - OS: debian amd64 unstable/sid, - Linux kernel: 2.6.15.7, - X: Xorg 7.0, - gfx driver: proprietary ATI binary driver v. 8.27.10 (kernel module compiled and loaded), - a 32-bit debian sid chroot, - Wolfenstein: E-T v. 2.60. chroot: is working. I installed mplayer and some codecs and was able to view a .wmv-file. Also, I installed firefox and a flash plugin and was able to view flash in firefox. 3D-acceleration: is working on amd64. I tried running 'ppracer' (on amd64, i.e. not in chroot) with and without the driver loaded - it runs fast with and slow without. I also tried installing and running 'ppracer' in my chroot, but it was slow, so it seems 3D-acceleration is not working for my chroot. Wolfenstein: Enemy Territory: is not working, neither in amd64 nor in the 32-bit chroot. Here is the output when run in chroot: == ET output begin = W: Failed to change to directory '/pack/fglrx/ati': No such file or directory W: Falling back to directory '/' I: [sid386 chroot] Running command: et ET 2.60 linux-i386 Mar 10 2005 - FS_Startup - Current search path: /home/nyholm/.etwolf/etmain /usr/local/games/enemy-territory/etmain/pak2.pk3 (22 files) /usr/local/games/enemy-territory/etmain/pak1.pk3 (10 files) /usr/local/games/enemy-territory/etmain/pak0.pk3 (3725 files) /usr/local/games/enemy-territory/etmain/mp_bin.pk3 (6 files) /usr/local/games/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 XF86DGA Mouse (Version 2.0) initialized 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 XF86DGA Mouse (Version 2.0) initialized XFree86-VidModeExtension Activated at 640x480 Received signal 11, exiting... == ET output end = Except for the first 3 lines the output is exactly the same in amd64. Any ideas? 1) You need the ATI driver installed inside the chroot as well as outside it (as it provides replacement libGL files) 2) What does ls -l /usr/lib/libGL.so.1 say? 3) what does glxinfo | grep vendor say? Oh, and do 2 3 outside the chroot - I personally would avoid using a chroot unless absolutely neccessary, and I know that for games, a chroot isn't absolutely neccessary No chroot for ET you say; how would one go about that? Um... just run the ET installer? Tried that; installer runs with no problems, but running 'et' gives same result as in the chroot. 1) I was thinking I might have to, but hoping I wouldn't, because how do I build the ATI driver kernel module? I mean, what kernel source do I use; the source from amd64 or do I need to install a kernel source package for the chroot? You will need to build a dummy package which will satisfy the dependancy, using equivs Oh, I will have to look into that. 2) Outside chroot: $ ls -l /usr/lib/libGL.so.1 lrwxrwxrwx 1 root root 12 Aug 10 18:47 /usr/lib/libGL.so.1 - libGL.so.1.2
