| View previous topic :: View next topic |
| Author |
Message |
energy
n00b
Joined: 07 Dec 2004
Posts: 25
Location: Oulu, Finland
|
 Posted: Wed Feb 23, 2005 1:03 pm Post subject: |
 |
|
Whoa, new drivers have really improved! 
energy@chevron ~ $ glxgears
15340 frames in 5.0 seconds = 3068.000 FPS
15725 frames in 5.0 seconds = 3145.000 FPS
15755 frames in 5.0 seconds = 3151.000 FPS
15716 frames in 5.0 seconds = 3143.200 FPS
With old drivers I got only about ~1825 FPS at max.
Even CS is now playable under Cedega 
Almost forgot, my hardware:
Asus A7N8X
512MB DDR
Athlon XP 2200+
ATI Radeon 9800SE |
|
| Back to top |
|
 |
Arainach
l33t
Joined: 08 Jul 2004
Posts: 609
|
| Posted: Wed Feb 23, 2005 2:52 pm Post subject: |
|
|
Since upgrading to these drivers (Only major System change I can think of) I've been getting random hard locks (Ctrl-Alt-Backspace doesn't work, nor does Ctrl-Alt-Del - I have to hard restart). Anyone else getting these? Since that's the only real change I notice from 8.8.25, I may just downgrade back.
_________________
Gentoo: Stage3 w/ NPTL & udev, gcc 3.4.4 full rebuild
Kernel: 2.6.15-gentoo-r1 w/ 1G-Lowmem Patch
System: Athlon XP 2.2Ghz/1GB Corsair Value/160GB, 250GB WD IDE/128MB GeForce 6800/Sony 17" Trinitron G200 @ 1280x1024x75Hz |
|
| Back to top |
|
|
Gentii
Guru
Joined: 01 Feb 2004
Posts: 306
|
| Posted: Wed Feb 23, 2005 3:06 pm Post subject: |
|
|
| Twist wrote: | Folks, please, for your own sake, do not use glxgears as a benchmark. It has been well established that glxgears is useless in this capacity other than to indicate hardware acceleration is working (e.g., 125fps versus something more than 300).
You will get substantially better indication out of quake3-demo or unreal tournament if you are looking for a reproducible benchmark source.
-Twist |
Hmm, I'm having killing pulsation when I read ati related threads. WHEN THE FUCK WILL THESE RETARDS UNDERSTAND ? |
|
| Back to top |
|
|
RayDude
Advocate
Joined: 29 May 2004
Posts: 2066
Location: San Jose, CA
|
| Posted: Thu Feb 24, 2005 11:29 pm Post subject: |
|
|
I think I get a hard lockup every few days if I don't reboot. It could be because of these drivers. I hadn't put 2 and 2 together until I read your post. Thanks.
| Arainach wrote: | | Since upgrading to these drivers (Only major System change I can think of) I've been getting random hard locks (Ctrl-Alt-Backspace doesn't work, nor does Ctrl-Alt-Del - I have to hard restart). Anyone else getting these? Since that's the only real change I notice from 8.8.25, I may just downgrade back. |
_________________
Some day there will only be free software. |
|
| Back to top |
|
|
Arainach
l33t
Joined: 08 Jul 2004
Posts: 609
|
| Posted: Fri Feb 25, 2005 12:48 am Post subject: |
|
|
Exact Same Scenario with me. Linux has been rock solid for years, but now it hard locks every few days. I think that I'll downgrade right now.
_________________
Gentoo: Stage3 w/ NPTL & udev, gcc 3.4.4 full rebuild
Kernel: 2.6.15-gentoo-r1 w/ 1G-Lowmem Patch
System: Athlon XP 2.2Ghz/1GB Corsair Value/160GB, 250GB WD IDE/128MB GeForce 6800/Sony 17" Trinitron G200 @ 1280x1024x75Hz |
|
| Back to top |
|
|
den_RDC
Apprentice
Joined: 25 Aug 2002
Posts: 166
Location: beercountry, Belgium;)
|
| Posted: Fri Feb 25, 2005 12:45 pm Post subject: |
|
|
anyone got bighead display mode working with this driver?
_________________
Fan of the "Survivor Warriors of the Evil Empire of Bloody Destruction and Bloody Darkness" |
|
| Back to top |
|
|
kanandkumar
n00b
Joined: 03 Jan 2004
Posts: 11
|
| Posted: Tue Mar 01, 2005 5:42 am Post subject: |
|
|
Looks like many people here got their DRI working with ATI radeon! I am trying to get my DRI working. I have an AMD 64 laptop (Asus Z80K) with ATI radeon 9700 running gentoo 2004.3 native AMD64 build. I installed the ATI driver version 8.10.19 from the RPM. The ATI drivers showed some exception about "pci_get_class() not found for the stock kernel, so I am using vanilla kernel 2.6.10. The installation went fine but I don't have 3D acceleration. I checked the Xorg log and this is what I see:
--------------------
(II) fglrx(0): [drm] register handle = 0xf89f0000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOSPC"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xffffff000002f000 at 0x2a961
29000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
---------------------
Any ideas ? Did i miss some option in the kernel config ?
Thanks.
Anand |
|
| Back to top |
|
|
soundspeed
n00b
Joined: 04 Dec 2004
Posts: 43
Location: This is my world
|
| Posted: Fri Mar 04, 2005 1:16 am Post subject: |
|
|
[quote] | Code: | --------------------
(II) fglrx(0): [drm] register handle = 0xf89f0000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOSPC"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xffffff000002f000 at 0x2a961
29000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
--------------------- [/quote] |
I'm the same problem!
Help us, please!
_________________
Underground World |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Mar 04, 2005 10:26 am Post subject: |
|
|
That looks like an AMD64 specific problem, try posting in the AMD64 forum.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Q-collective
Advocate
Joined: 22 Mar 2004
Posts: 2071
|
| Posted: Tue Mar 08, 2005 9:43 pm Post subject: |
|
|
| An increase from 2000 to 3000 in glxgears (and if you don't run the glxgears wheels in the top window, even 5500!!) is a nice improvement |
|
| Back to top |
|
|
Arainach
l33t
Joined: 08 Jul 2004
Posts: 609
|
| Posted: Tue Mar 08, 2005 11:26 pm Post subject: |
|
|
Well, while it does absolutely NOTHING for me in Doom3, in other games (UT2004, RTCW, et. al) gameplay is much smoother and all-around nicer. So apparently these drivers did something right. Not to mention that the random hard locks I experienced apparently have something to do with my jumps among various "experimental" kernels (nitro and love), not the ATI drivers specifically. So I'm running on 8.10.19 now and I'm quite happy.
_________________
Gentoo: Stage3 w/ NPTL & udev, gcc 3.4.4 full rebuild
Kernel: 2.6.15-gentoo-r1 w/ 1G-Lowmem Patch
System: Athlon XP 2.2Ghz/1GB Corsair Value/160GB, 250GB WD IDE/128MB GeForce 6800/Sony 17" Trinitron G200 @ 1280x1024x75Hz |
|
| Back to top |
|
|
swilly
n00b
Joined: 05 Nov 2003
Posts: 20
|
| Posted: Thu Mar 10, 2005 5:38 pm Post subject: subject |
|
|
message
Last edited by swilly on Sun Jul 21, 2013 9:20 pm; edited 1 time in total |
|
| Back to top |
|
|
bushwakko
Guru
Joined: 25 Mar 2003
Posts: 495
|
|
| Back to top |
|
|
swilly
n00b
Joined: 05 Nov 2003
Posts: 20
|
| Posted: Fri Mar 11, 2005 3:04 am Post subject: subject |
|
|
message
Last edited by swilly on Sun Jul 21, 2013 9:19 pm; edited 1 time in total |
|
| Back to top |
|
|
violentgreen
Tux's lil' helper
Joined: 24 Sep 2003
Posts: 98
Location: Lexington, KY
|
| Posted: Fri Mar 18, 2005 12:52 pm Post subject: |
|
|
[quote="soundspeed"] | Quote: | | Code: | --------------------
(II) fglrx(0): [drm] register handle = 0xf89f0000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOSPC"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xffffff000002f000 at 0x2a961
29000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
--------------------- [/quote] |
I'm the same problem!
Help us, please! |
I solved this by setting the UseInternalAGPGART (or soemthing similar to that) to no. |
|
| Back to top |
|
|
violentgreen
Tux's lil' helper
Joined: 24 Sep 2003
Posts: 98
Location: Lexington, KY
|
| Posted: Fri Mar 18, 2005 12:54 pm Post subject: |
|
|
| I am still having the problem with my glxgears. I followed the above instructions and it removed the errors. Now when I run fgl_glxgears, I get a white box that spins for about half a second and then stops. No errors are shown. |
|
| Back to top |
|
|
Arainach
l33t
Joined: 08 Jul 2004
Posts: 609
|
| Posted: Fri Mar 18, 2005 4:50 pm Post subject: |
|
|
Try running opengl-update ati again.
_________________
Gentoo: Stage3 w/ NPTL & udev, gcc 3.4.4 full rebuild
Kernel: 2.6.15-gentoo-r1 w/ 1G-Lowmem Patch
System: Athlon XP 2.2Ghz/1GB Corsair Value/160GB, 250GB WD IDE/128MB GeForce 6800/Sony 17" Trinitron G200 @ 1280x1024x75Hz |
|
| Back to top |
|
|
mdshort
Apprentice
Joined: 06 Dec 2004
Posts: 157
|
| Posted: Fri Mar 18, 2005 9:48 pm Post subject: |
|
|
| Lokheed wrote: | Looks like they fixed my old problem:
A blank screen or X failing to load and returning to the console no longer occurs under X.Org 6.8 when using the config file generated by fglrxconfig |
Yea, you can get back into the console now, but you can't startx again :\
_________________
"With every rise, there is a fall." |
|
| Back to top |
|
|
violentgreen
Tux's lil' helper
Joined: 24 Sep 2003
Posts: 98
Location: Lexington, KY
|
| Posted: Fri Mar 18, 2005 10:16 pm Post subject: |
|
|
| Arainach wrote: | | Try running opengl-update ati again. |
I did that but I don't think that that is the problem.
fglrxinfo returns
| Code: |
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 Generic
OpenGL version string: 1.3.4769 (X4.3.0-8.8.25)
|
|
|
| Back to top |
|
|
ruomad
Tux's lil' helper
Joined: 17 Apr 2003
Posts: 93
|
| Posted: Sun Mar 20, 2005 7:21 am Post subject: |
|
|
i had to patch (a bit at random I admit) the drivers to have them work with kernel-2.6.11+
if not the kernel module is not built (you don't notice it at first because emerge carries on) and you get no DRI
(my hardware ati mobility 9700 + pentium M)
here are my ebuild and the patches
| Code: | # Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/media-video/ati-drivers/ati-drivers-8.10.19.ebuild,v 1.1 2005/02/16 22:21:44 lu_zero Exp $
IUSE=""
inherit eutils rpm multilib linux-info linux-mod
DESCRIPTION="Ati precompiled drivers for r350, r300, r250 and r200 chipsets"
HOMEPAGE="http://www.ati.com"
SRC_URI="x86? ( http://www2.ati.com/drivers/linux/fglrx_6_8_0-${PV}-1.i386.rpm ) "
# amd64? ( http://www2.ati.com/drivers/linux/fglrx64_6_8_0-${PV}-1.x86_64.rpm )"
LICENSE="ATI"
KEYWORDS="-* ~x86 ~amd64"
RDEPEND=">=x11-base/xorg-x11-6.8.0
>=x11-base/opengl-update-2.1_pre1"
DEPEND=">=virtual/linux-sources-2.4
${RDEPEND}"
PROVIDE="virtual/opengl"
ATIBIN="${D}/opt/ati/bin"
RESTRICT="nostrip multilib-pkg-force"
pkg_setup(){
#check kernel and sets up KV_OBJ
linux-mod_pkg_setup
# Set up X11 implementation
X11_IMPLEM_P="$(best_version virtual/x11)"
X11_IMPLEM="${X11_IMPLEM_P%-[0-9]*}"
X11_IMPLEM="${X11_IMPLEM##*\/}"
einfo "X11 implementation is ${X11_IMPLEM}."
}
src_unpack() {
local OLDBIN="/usr/X11R6/bin"
cd ${WORKDIR}
rpm_src_unpack
cd ${WORKDIR}/lib/modules/fglrx/build_mod
#epatch ${FILESDIR}/fglrx-3.9.0-allocation.patch
if kernel_is 2 6
then
#epatch ${FILESDIR}/fglrx-2.6-pagetable.patch
#epatch ${FILESDIR}/fglrx-2.6.10-pci_get_class.patch
#epatch ${FILESDIR}/8.08-kernel-2.6.10.patch
epatch ${FILESDIR}/8.8.25-kernel-2.6.11+.patch
epatch ${FILESDIR}/small-fglrx-2.6.11-rc1.patch
fi
epatch ${FILESDIR}/8.8.25-via-amd64.patch
rm -rf ${WORKDIR}/usr/X11R6/bin/fgl_glxgears
}
src_compile() {
einfo "Building the DRM module..."
cd ${WORKDIR}/lib/modules/fglrx/build_mod
if kernel_is 2 6
then
set_arch_to_kernel
addwrite "/usr/src/${FK}"
cp 2.6.x/Makefile .
export _POSIX2_VERSION="199209"
if use_m ;
then
make -C ${KV_DIR} M="`pwd`" modules || \
ewarn "DRM module not built"
else
make -C ${KV_DIR} SUBDIRS="`pwd`" modules || \
ewarn "DRM module not built"
fi
set_arch_to_portage
else
export _POSIX2_VERSION="199209"
# That is the dirty way to avoid the id -u check
sed -e 's:`id -u`:0:' \
-e "s:\`uname -r\`:${KV_FULL}:" \
-i make.sh
chmod +x make.sh
./make.sh || die "DRM module not built"
fi
}
pkg_preinst() {
# Clean the dinamic libGL stuff's home to ensure
# we don't have stale libs floating around ...
if [ -d "${ROOT}/usr/lib/opengl/ati" ]
then
rm -rf ${ROOT}/usr/lib/opengl/ati/*
fi
}
src_install() {
local ATI_ROOT="/usr/lib/opengl/ati"
cd ${WORKDIR}
# DRM module
insinto /lib/modules/${KV_FULL}/video
# set_kvobj
doins ${WORKDIR}/lib/modules/fglrx/build_mod/fglrx.${KV_OBJ}
local native_dir
use x86 && native_dir="lib"
use amd64 && native_dir="lib64"
# Install the libs
# MULTILIB-CLEANUP: Fix this when FEATURES=multilib-pkg is in portage
local MLTEST=$(type dyn_unpack)
if [ "${MLTEST/set_abi}" = "${MLTEST}" ] && has_multilib_profile; then
local OABI=${ABI}
for ABI in $(get_install_abis); do
src_install-libs
done
ABI=${OABI}
unset OABI
elif has_multilib_profile; then
src_install-libs
elif use amd64; then
src_install-libs lib $(get_multilibdir)
src_install-libs lib64 $(get_libdir)
else
src_install-libs
fi &> /dev/null
#apps
insinto /etc/env.d
doins ${FILESDIR}/09ati
exeinto /opt/ati/bin
doexe usr/X11R6/bin/*
#ati custom stuff
cp -a ${WORKDIR}/usr/include ${D}/usr/include
}
src_install-libs() {
local pkglibdir=lib
local inslibdir=$(get_libdir)
if [ ${#} -eq 2 ]; then
pkglibdir=${1}
inslibdir=${2}
elif has_multilib_profile && [ "${ABI}" == "amd64" ]; then
pkglibdir=lib64
fi
einfo "${pkglibdir} -> ${inslibdir}"
local ATI_ROOT="/usr/${inslibdir}/opengl/ati"
# The GLX libraries
exeinto ${ATI_ROOT}/lib
doexe ${WORKDIR}/usr/X11R6/${pkglibdir}/libGL.so.1.2
dosym libGL.so.1.2 ${ATI_ROOT}/lib/libGL.so.1
dosym libGL.so.1.2 ${ATI_ROOT}/lib/libGL.so
# Don't do this... see bug #47598
#dosym libGL.so.1.2 ${ATI_ROOT}/lib/libMesaGL.so
# same as the xorg implementation
dosym ../${X11_IMPLEM}/extensions ${ATI_ROOT}/extensions
#Workaround
sed -e "s:libdir=.*:libdir=${ATI_ROOT}/lib:" \
/usr/${inslibdir}/opengl/${X11_IMPLEM}/lib/libGL.la \
> $D/${ATI_ROOT}/lib/libGL.la
dosym ../${X11_IMPLEM}/include ${ATI_ROOT}/include
# X and DRI driver
if has_version ">=x11-base/xorg-x11-6.8.0-r4"
then
local X11_DIR="/usr/"
else
local X11_DIR="/usr/X11R6/"
fi
local X11_LIB_DIR="${X11_DIR}${inslibdir}"
exeinto ${X11_LIB_DIR}/modules/drivers
doexe ${WORKDIR}/usr/X11R6/${pkglibdir}/modules/drivers/fglrx_drv.o
exeinto ${X11_LIB_DIR}/modules/dri
doexe ${WORKDIR}/usr/X11R6/${pkglibdir}/modules/dri/fglrx_dri.so
exeinto ${X11_LIB_DIR}/modules/linux
doexe ${WORKDIR}/usr/X11R6/${pkglibdir}/modules/linux/libfglrxdrm.a
cp -a ${WORKDIR}/usr/X11R6/${pkglibdir}/libfglrx_gamma.* \
${D}/${X11_LIB_DIR}
#Not the best place
insinto ${X11_DIR}/include/X11/extensions
doins ${WORKDIR}/usr/X11R6/include/X11/extensions/fglrx_gamma.h
exeinto ${X11_LIB_DIR}/modules/dri
doexe ${WORKDIR}/usr/X11R6/${pkglibdir}/modules/dri/fglrx_dri.so
}
pkg_postinst() {
# Ebuild shouldn't do this automatically, just tell the user to do it,
# otherwise it messes up livecd/gamecd stuff ... (drobbins, 1 May 2003)
# if [ "${ROOT}" = "/" ]
# then
# /usr/sbin/opengl-update ati
# fi
echo
einfo "To switch to ATI OpenGL, run \"opengl-update ati\""
einfo "To change your XF86Config you can use the bundled \"fglrxconfig\""
echo
ewarn "***"
ewarn "If you are experiencing problems with memory allocation try to add"
ewarn "this line to in your X11 configuration file:"
ewarn " Option \"KernelModuleParm\" \"agplock=0\" "
ewarn "That should solve the hangups you could have with Neverwinter Nights"
ewarn "***"
# DRM module
update-modules
}
|
patches :
8.8.25-kernel-2.6.11.patch
| Code: | diff -urN build_mod/agpgart_be.c build_mod2/agpgart_be.c
--- build_mod/agpgart_be.c 2005-01-17 23:34:04.000000000 +0000
+++ build_mod2/agpgart_be.c 2005-01-17 23:36:12.000000000 +0000
@@ -116,7 +116,14 @@
#include <linux/pagemap.h>
#include <linux/miscdevice.h>
#include <linux/pm.h>
+#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,9)
+#define pci_find_class pci_get_class
+
+
+
+
+#endif
#if (LINUX_VERSION_CODE >= 0x020400)
#define FGL_PM_PRESENT
#else
diff -urN build_mod/firegl_public.c build_mod2/firegl_public.c
--- build_mod/firegl_public.c 2005-01-17 23:34:04.000000000 +0000
+++ build_mod2/firegl_public.c 2005-01-17 23:36:02.000000000 +0000
@@ -2590,13 +2590,13 @@
#endif /* __ia64__ */
vma->vm_flags |= VM_IO; /* not in core dump */
}
- if (remap_page_range(FGL_VMA_API_PASS
+ if (remap_pfn_range(FGL_VMA_API_PASS
vma->vm_start,
- __ke_vm_offset(vma),
+ vma->vm_pgoff,
vma->vm_end - vma->vm_start,
vma->vm_page_prot))
{
- __KE_DEBUG("remap_page_range failed\n");
+ __KE_DEBUG("remap_pfn_range failed\n");
return -EAGAIN;
}
vma->vm_flags |= VM_SHM | VM_RESERVED; /* Don't swap */
@@ -2655,15 +2655,15 @@
#else
// else
{
- if (__ke_vm_offset(vma) >= __pa(high_memory))
+ if (vma->vm_pgoff >= __pa(high_memory))
vma->vm_flags |= VM_IO; /* not in core dump */
- if (remap_page_range(FGL_VMA_API_PASS
+ if (remap_pfn_range(FGL_VMA_API_PASS
vma->vm_start,
- __ke_vm_offset(vma),
+ vma->vm_pgoff,
vma->vm_end - vma->vm_start,
vma->vm_page_prot))
{
- __KE_DEBUG("remap_page_range failed\n");
+ __KE_DEBUG("remap_pfn_range failed\n");
return -EAGAIN;
}
#ifdef __x86_64__
@@ -2692,15 +2692,15 @@
// else
#else
{
- if (__ke_vm_offset(vma) >= __pa(high_memory))
+ if (vma->vm_pgoff >= __pa(high_memory))
vma->vm_flags |= VM_IO; /* not in core dump */
- if (remap_page_range(FGL_VMA_API_PASS
+ if (remap_pfn_range(FGL_VMA_API_PASS
vma->vm_start,
- __ke_vm_offset(vma),
+ vma->vm_pgoff,
vma->vm_end - vma->vm_start,
vma->vm_page_prot))
{
- __KE_DEBUG("remap_page_range failed\n");
+ __KE_DEBUG("remap_pfn_range failed\n");
return -EAGAIN;
}
#ifdef __x86_64__ |
small-fglrxsmall-fglrx-2.6.11-rc1.patch
| Code: |
--- firegl_public.c-orig 2005-01-22 13:06:54.979098000 +0200
+++ firegl_public.c 2005-01-22 22:14:03.395750408 +0200
@@ -2800,5 +2800,36 @@ int ATI_API_CALL __ke_vm_map(struct file
#if LINUX_VERSION_CODE >= 0x020400
+#if LINUX_VERSION_CODE >= 0x02060b
+
+typedef struct {
+ void (*free_memory)(struct agp_memory *);
+ struct agp_memory * (*allocate_memory)(size_t, u32);
+ int (*bind_memory)(struct agp_memory *, off_t);
+ int (*unbind_memory)(struct agp_memory *);
+ void (*enable)(u32);
+ int (*acquire)(void);
+ void (*release)(void);
+ int (*copy_info)(struct agp_kern_info *);
+} drm_agp_t;
+
+static const drm_agp_t drm_agp = {
+ &agp_free_memory,
+ &agp_allocate_memory,
+ &agp_bind_memory,
+ &agp_unbind_memory,
+ &agp_enable,
+ &agp_backend_acquire,
+ &agp_backend_release,
+ &agp_copy_info
+};
+#undef DRM_AGP_MODULE_GET
+#undef DRM_AGP_MODULE_PUT
+
+#define DRM_AGP_MODULE_GET &drm_agp
+#define DRM_AGP_MODULE_PUT
+
+#endif
+
static const drm_agp_t *drm_agp_module_stub = NULL;
#define AGP_FUNCTIONS 8 |
|
|
| Back to top |
|
|
truth_bk
n00b
Joined: 15 Oct 2004
Posts: 13
|
| Posted: Wed Mar 23, 2005 1:19 am Post subject: Doom3 and ati-drivers |
|
|
unlike most people.... hehehe, I've had no problem getting doom3 up and running, and apparently everything is running well... I have direct rendering on, and the opengl provided by ati seems to be working well.... Tux Racer also runs very smoothly, and while I'm still emerging ut2004, I've been doing my tests with doom3....
here's the problem.... it runs, I can play, the "movement" seems smooth.... but I get some "snow" to call it somehow on certain areas.... lets say some pixels, enough to make it very disturbing, are just the "wrong" color, whiteish... Like I said, similar to the snow you'd see when u can't quite fine-tune your tv...
Anyone had anything similar to this happen to them!? Any suggestions?
PS- Did anyone understand what I meant!?!?!?! hahahahahaha!!! |
|
| Back to top |
|
|
Jowilly
Guru
Joined: 22 Jun 2002
Posts: 319
|
| Posted: Wed Mar 23, 2005 11:49 pm Post subject: Re: Doom3 and ati-drivers |
|
|
| truth_bk wrote: | unlike most people.... hehehe, I've had no problem getting doom3 up and running, and apparently everything is running well... I have direct rendering on, and the opengl provided by ati seems to be working well.... Tux Racer also runs very smoothly, and while I'm still emerging ut2004, I've been doing my tests with doom3....
here's the problem.... it runs, I can play, the "movement" seems smooth.... but I get some "snow" to call it somehow on certain areas.... lets say some pixels, enough to make it very disturbing, are just the "wrong" color, whiteish... Like I said, similar to the snow you'd see when u can't quite fine-tune your tv...
Anyone had anything similar to this happen to them!? Any suggestions?
PS- Did anyone understand what I meant!?!?!?! hahahahahaha!!! |
I have the same problem (white snow) with doom3 (but other 3d games are fine).
I believe this is caused by the card (ati 9800XT here) overheating. When I start from a cold boot and run the game, everything is fine for about 1 minute and then the white snow appears. If I start the game when the system is hot, the white snow appears as soon as I start it. |
|
| Back to top |
|
|
forceflow2
Guru
Joined: 16 Apr 2003
Posts: 464
Location: South Carolina
|
| Posted: Thu Mar 24, 2005 12:28 am Post subject: |
|
|
| ruomad wrote: | i had to patch (a bit at random I admit) the drivers to have them work with kernel-2.6.11+
if not the kernel module is not built (you don't notice it at first because emerge carries on) and you get no DRI
(my hardware ati mobility 9700 + pentium M)
|
Tried your ebuild and patches (which failed btw, had to go in manually and patch it, but no big deal) and still end up with the same error I had before when trying this already. I'm able to build the module, but modprobing leads to | Code: |
fglrx: Unknown symbol inter_module_get
|
Which I believe is a problem due to the DRM changes with the 2.6.1X series of the kernel:(
_________________
That rank under my username doesn't mean I know everything, it just means I ask a lot of questions. |
|
| Back to top |
|
|
Twist
Guru
Joined: 03 Jan 2003
Posts: 414
Location: San Diego
|
| Posted: Thu Mar 24, 2005 12:53 am Post subject: |
|
|
| Quote: | | here's the problem.... it runs, I can play, the "movement" seems smooth.... but I get some "snow" to call it somehow on certain areas.... |
This is very characteristic of failure of either the GPU or memory due to overheating/overclocking. If you see the "snow" in the same general areas of the screen across frames, that's most often memory. If it appears to be almost anywhere and/or you see other abberant effects - untextured surfaces, or polygons that have one vertex wildly off the screen, etc, then that's probably GPU.
-Twist |
|
| Back to top |
|
|
ruomad
Tux's lil' helper
Joined: 17 Apr 2003
Posts: 93
|
| Posted: Thu Mar 24, 2005 5:15 am Post subject: |
|
|
what kernel are you running ?
I just posted a problem with 2.6.12_rc1, but some rc for 2.6.11 may have been concerned as well, about inter_module_get (long deprecated) being removed in kernel (see lkml)
in that case you will have to patch the kernel (i don't know any workaround unti ati fixes it...) |
|
| Back to top |
|
|
|
Kernel & Hardware
