| View previous topic :: View next topic |
| Author |
Message |
hermes_jr
l33t
Joined: 26 Feb 2004
Posts: 701
Location: Moscow, Russia
|
 Posted: Tue Feb 01, 2005 6:34 pm Post subject: |
 |
|
Problem with nvidia here.
Kernel compiled with 8k stack size, realtime patches enabled.
nvidia-kernel do not even compile (with 2.6.10 nitros and same nvidia-kernel all was fine).
| Quote: |
$ emerge nvidia-kernel
....
/var/tmp/portage/nvidia-kernel-1.0.6629-r3/work/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c: In function `nv_agp_init':
/var/tmp/portage/nvidia-kernel-1.0.6629-r3/work/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:3025: error: too few arguments to function `agp_backend_acquire'
/var/tmp/portage/nvidia-kernel-1.0.6629-r3/work/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:3025: warning: assignment makes integer from pointer without a cast
/var/tmp/portage/nvidia-kernel-1.0.6629-r3/work/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c:3027: error: too few arguments to function `agp_backend_release'
make[3]: *** [/var/tmp/portage/nvidia-kernel-1.0.6629-r3/work/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.o] Error 1
make[2]: *** [_module_/var/tmp/portage/nvidia-kernel-1.0.6629-r3/work/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
!!! ERROR: media-video/nvidia-kernel-1.0.6629-r3 failed.
!!! Function linux-mod_src_compile, Line 417, Exitcode 2
!!! Unable to make IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/usr/src/linux clean module.
!!! If you need support, post the topmost build error, NOT this status message.
|
Nvidia/kernel ebuild and patches are from the first post.
This and this solutions didn't help.
Ideas? |
|
| Back to top |
|
 |
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 6:40 pm Post subject: |
|
|
| one Moment plz... |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 6:48 pm Post subject: |
|
|
EHM: this experimental includes bk trees from agp, drm and all.
So someone should keep this patch in safe place in case it should work, cuz the next mainline will most probably include this stuff as well... 
[EDIT]
its mostly about the two agp funcs which need an arg now
[/EDIT]
Try this:
| Code: |
diff -ruN nv-6629-jam/src/nv/nv-linux.h nv-6629-jam-2/src/nv/nv-linux.h
--- nv-6629-jam/src/nv/nv-linux.h 2005-01-24 23:16:46.000000000 +0100
+++ nv-6629-jam-2/src/nv/nv-linux.h 2005-01-26 00:25:10.000000000 +0100
@@ -930,6 +930,9 @@
/* lock for linux-specific alloc queue */
struct semaphore at_lock;
+
+ /* AGP bridge handle */
+ struct agp_bridge_data *agp_bridge;
} nv_linux_state_t;
diff -ruN nv-6629-jam/src/nv/nv.c nv-6629-jam-2/src/nv/nv.c
--- nv-6629-jam/src/nv/nv.c 2005-01-24 23:16:46.000000000 +0100
+++ nv-6629-jam-2/src/nv/nv.c 2005-01-26 00:47:14.000000000 +0100
@@ -3011,10 +3011,11 @@
return -1;
}
#elif defined(AGPGART)
- int error;
- if ((error = agp_backend_acquire()) != -EINVAL)
+ nv_linux_state_t *nvl = NV_GET_NVL_FROM_NV_STATE(nv);
+ nvl->agp_bridge = agp_backend_acquire(nvl->dev);
+ if (nvl->agp_bridge)
{
- if (!error) agp_backend_release();
+ agp_backend_release(nvl->agp_bridge);
nv_printf(NV_DBG_WARNINGS,
"NVRM: not using NVAGP, an AGPGART backend is loaded!\n");
return -1;
diff -ruN nv-6629-jam/src/nv/os-agp.c nv-6629-jam-2/src/nv/os-agp.c
--- nv-6629-jam/src/nv/os-agp.c 2005-01-24 23:16:46.000000000 +0100
+++ nv-6629-jam-2/src/nv/os-agp.c 2005-01-26 00:49:01.000000000 +0100
@@ -60,23 +60,23 @@
#endif
#if defined(KERNEL_2_6)
-#define NV_AGPGART_BACKEND_ACQUIRE(o) agp_backend_acquire()
-#define NV_AGPGART_BACKEND_ENABLE(o,mode) agp_enable(mode)
-#define NV_AGPGART_BACKEND_RELEASE(o) agp_backend_release()
-#define NV_AGPGART_COPY_INFO(o,p) agp_copy_info(p)
-#define NV_AGPGART_ALLOCATE_MEMORY(o,count,type) agp_allocate_memory(count,type)
-#define NV_AGPGART_FREE_MEMORY(o,p) agp_free_memory(p)
-#define NV_AGPGART_BIND_MEMORY(o,p,offset) agp_bind_memory(p,offset)
-#define NV_AGPGART_UNBIND_MEMORY(o,p) agp_unbind_memory(p)
+#define NV_AGPGART_BACKEND_ACQUIRE(nvl,o) ({ nvl->agp_bridge = agp_backend_acquire(nvl->dev); !nvl->agp_bridge; })
+#define NV_AGPGART_BACKEND_ENABLE(nvl,o,mode) agp_enable(nvl->agp_bridge,mode)
+#define NV_AGPGART_BACKEND_RELEASE(nvl,o) agp_backend_release(nvl->agp_bridge)
+#define NV_AGPGART_COPY_INFO(nvl,o,p) agp_copy_info(nvl->agp_bridge,p)
+#define NV_AGPGART_ALLOCATE_MEMORY(nvl,o,count,type) agp_allocate_memory(nvl->agp_bridge,count,type)
+#define NV_AGPGART_FREE_MEMORY(nvl,o,p) agp_free_memory(p)
+#define NV_AGPGART_BIND_MEMORY(nvl,o,p,offset) agp_bind_memory(p,offset)
+#define NV_AGPGART_UNBIND_MEMORY(nvl,o,p) agp_unbind_memory(p)
#elif defined(KERNEL_2_4)
-#define NV_AGPGART_BACKEND_ACQUIRE(o) ({ (o)->acquire(); 0; })
-#define NV_AGPGART_BACKEND_ENABLE(o,mode) (o)->enable(mode)
-#define NV_AGPGART_BACKEND_RELEASE(o) ((o)->release())
-#define NV_AGPGART_COPY_INFO(o,p) ({ (o)->copy_info(p); 0; })
-#define NV_AGPGART_ALLOCATE_MEMORY(o,count,type) (o)->allocate_memory(count,type)
-#define NV_AGPGART_FREE_MEMORY(o,p) (o)->free_memory(p)
-#define NV_AGPGART_BIND_MEMORY(o,p,offset) (o)->bind_memory(p,offset)
-#define NV_AGPGART_UNBIND_MEMORY(o,p) (o)->unbind_memory(p)
+#define NV_AGPGART_BACKEND_ACQUIRE(nvl,o) ({ (o)->acquire(); 0; })
+#define NV_AGPGART_BACKEND_ENABLE(nvl,o,mode) (o)->enable(mode)
+#define NV_AGPGART_BACKEND_RELEASE(nvl,o) ((o)->release())
+#define NV_AGPGART_COPY_INFO(nvl,o,p) ({ (o)->copy_info(p); 0; })
+#define NV_AGPGART_ALLOCATE_MEMORY(nvl,o,count,type) (o)->allocate_memory(count,type)
+#define NV_AGPGART_FREE_MEMORY(nvl,o,p) (o)->free_memory(p)
+#define NV_AGPGART_BIND_MEMORY(nvl,o,p,offset) (o)->bind_memory(p,offset)
+#define NV_AGPGART_UNBIND_MEMORY(nvl,o,p) (o)->unbind_memory(p)
#endif
#endif /* AGPGART */
@@ -96,6 +96,7 @@
U032 agp_fw;
void *bitmap;
U032 bitmap_size;
+ nv_linux_state_t *nvl = NV_GET_NVL_FROM_NV_STATE(nv);
memset( (void *) &gart, 0, sizeof(agp_gart));
@@ -110,7 +111,7 @@
* the memory controller.
*/
- if (NV_AGPGART_BACKEND_ACQUIRE(drm_agp_p))
+ if (NV_AGPGART_BACKEND_ACQUIRE(nvl,drm_agp_p))
{
nv_printf(NV_DBG_INFO, "NVRM: AGPGART: no backend available\n");
goto bailout;
@@ -128,7 +129,7 @@
agp_fw = 1;
agp_fw &= 0x00000001;
- if (NV_AGPGART_COPY_INFO(drm_agp_p, &agpinfo))
+ if (NV_AGPGART_COPY_INFO(nvl,drm_agp_p, &agpinfo))
{
nv_printf(NV_DBG_ERRORS,
"NVRM: AGPGART: kernel reports chipset as unsupported\n");
@@ -188,7 +189,7 @@
if (!(agp_rate & 0x00000004)) agpinfo.mode &= ~0x00000004;
if (!(agp_rate & 0x00000002)) agpinfo.mode &= ~0x00000002;
- NV_AGPGART_BACKEND_ENABLE(drm_agp_p, agpinfo.mode);
+ NV_AGPGART_BACKEND_ENABLE(nvl,drm_agp_p, agpinfo.mode);
*ap_phys_base = (void*) agpinfo.aper_base;
*ap_mapped_base = (void*) gart.aperture;
@@ -200,7 +201,7 @@
failed:
MTRR_DEL(gart); /* checks gart.mtrr */
- NV_AGPGART_BACKEND_RELEASE(drm_agp_p);
+ NV_AGPGART_BACKEND_RELEASE(nvl,drm_agp_p);
bailout:
#if defined(KERNEL_2_4)
inter_module_put("drm_agp");
@@ -219,6 +220,7 @@
return 1;
#else
void *bitmap;
+ nv_linux_state_t *nvl;
/* sanity check to make sure we should actually be here. */
if (!gart.ready)
@@ -234,7 +236,8 @@
NV_IOUNMAP(gart.aperture, RM_PAGE_SIZE);
}
- NV_AGPGART_BACKEND_RELEASE(drm_agp_p);
+ nvl = NV_GET_NVL_FROM_NV_STATE(nv);
+ NV_AGPGART_BACKEND_RELEASE(nvl,drm_agp_p);
#if defined(KERNEL_2_4)
inter_module_put("drm_agp");
#endif
@@ -268,6 +271,7 @@
agp_memory *ptr;
agp_priv_data *data;
RM_STATUS status;
+ nv_linux_state_t *nvl;
if (!gart.ready)
{
@@ -283,7 +287,8 @@
return RM_ERROR;
}
- ptr = NV_AGPGART_ALLOCATE_MEMORY(drm_agp_p, PageCount, AGP_NORMAL_MEMORY);
+ nvl = NV_GET_NVL_FROM_NV_STATE(nv);
+ ptr = NV_AGPGART_ALLOCATE_MEMORY(nvl,drm_agp_p, PageCount, AGP_NORMAL_MEMORY);
if (ptr == NULL)
{
*pAddress = (void*) 0;
@@ -291,7 +296,7 @@
return RM_ERR_NO_FREE_MEM;
}
- if (NV_AGPGART_BIND_MEMORY(drm_agp_p, ptr, *Offset))
+ if (NV_AGPGART_BIND_MEMORY(nvl,drm_agp_p, ptr, *Offset))
{
// this happens a lot when the aperture itself fills up..
// not a big deal, so don't alarm people with an error message
@@ -304,7 +309,7 @@
if (status != RM_OK)
{
nv_printf(NV_DBG_ERRORS, "NVRM: AGPGART: memory allocation failed\n");
- NV_AGPGART_UNBIND_MEMORY(drm_agp_p, ptr);
+ NV_AGPGART_UNBIND_MEMORY(nvl,drm_agp_p, ptr);
goto fail;
}
@@ -319,7 +324,7 @@
return RM_OK;
fail:
- NV_AGPGART_FREE_MEMORY(drm_agp_p, ptr);
+ NV_AGPGART_FREE_MEMORY(nvl,drm_agp_p, ptr);
*pAddress = (void*) 0;
return RM_ERROR;
@@ -359,7 +364,7 @@
{
nv_printf(NV_DBG_ERRORS, "NVRM: AGPGART: unable to remap %lu pages\n",
(unsigned long)agp_data->num_pages);
- NV_AGPGART_UNBIND_MEMORY(drm_agp_p, agp_data->ptr);
+ NV_AGPGART_UNBIND_MEMORY(nvl,drm_agp_p, agp_data->ptr);
goto fail;
}
@@ -458,8 +463,8 @@
{
size_t pages = ptr->page_count;
- NV_AGPGART_UNBIND_MEMORY(drm_agp_p, ptr);
- NV_AGPGART_FREE_MEMORY(drm_agp_p, ptr);
+ NV_AGPGART_UNBIND_MEMORY(nvl,drm_agp_p, ptr);
+ NV_AGPGART_FREE_MEMORY(nvl,drm_agp_p, ptr);
nv_printf(NV_DBG_INFO, "NVRM: AGPGART: freed %ld pages\n",
(unsigned long)pages);
|
|
|
| Back to top |
|
|
discomfitor
l33t
Joined: 21 Feb 2003
Posts: 927
Location: None
|
| Posted: Tue Feb 01, 2005 7:05 pm Post subject: |
|
|
anuron: Make sure NVAGP is set to 2 in your xorg.conf.
hermes_jr: If Tiger683's solution doesn't work, try toggling agpgart support in the kernel (I remember reading somewhere that it was possible to have build failures if it wasn't in a certain state, but that may or may not apply here).
Updated the first post to ensure that people can't possibly miss the NVAGP thing again.
Also, does anyone know where I can find the lirc patch? I've been looking for a while but just can't find it. If people want lirc, SOMEBODY is going to have to bite the bullet and just tell me where it is.
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort. |
|
| Back to top |
|
|
anuron
n00b
Joined: 01 Feb 2005
Posts: 4
|
| Posted: Tue Feb 01, 2005 7:12 pm Post subject: |
|
|
@Darckness
NVAGP is 2 i tried it both, with and without nvidia agp used.
It seems to be a known problem with the 6629 and the TNT2 chipset
cheers
anuron |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 7:28 pm Post subject: |
|
|
@Darckness:LIRC
Have to pull it off cvs, the one i was trying with was SOOOOOOOOOOO broken with this kernel... no chance at all.
T |
|
| Back to top |
|
|
hermes_jr
l33t
Joined: 26 Feb 2004
Posts: 701
Location: Moscow, Russia
|
| Posted: Tue Feb 01, 2005 7:59 pm Post subject: |
|
|
Tiger683: thanks, your patch works here.
Anyways, 2.6.11-rc2-nitro1 is the first nitro kernel which doesn't work well on my pc. The first thing is the problem with nvidia which is half-solved, so I can compile nvidia-kernel now but system hangs on X start.
The second prob is something with network filesystem mount; with 2.6.10-nitro4 network filesystems mounts in 1 sec, with 2.6.11 - about 20 sec, not good. So 2.6.11-rc2-nitro1 is the most unstable nitro for me atm.
Darckness, sorry  . |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 8:02 pm Post subject: |
|
|
Shit....
First of all, if you use the one with realtime preempt, then it'S been completely my work and responsibility,
second, I'm surprised cuz for me nfs as well as captive-ntfs were completely BROKEN.
What else abut instability?
please copy, i need it to get fixed as soon as possible...
T |
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Tue Feb 01, 2005 8:13 pm Post subject: |
|
|
| hermes_jr wrote: | Tiger683: thanks, your patch works here.
Anyways, 2.6.11-rc2-nitro1 is the first nitro kernel which doesn't work well on my pc. The first thing is the problem with nvidia which is half-solved, so I can compile nvidia-kernel now but system hangs on X start.
The second prob is something with network filesystem mount; with 2.6.10-nitro4 network filesystems mounts in 1 sec, with 2.6.11 - about 20 sec, not good. So 2.6.11-rc2-nitro1 is the most unstable nitro for me atm.
Darckness, sorry . |
Remember though, the 2.6.11-rc* kernels are considered beta and as such may have these kind of probs. Also, using the patches for the nvidia drivers from zander (found them on google) worked fine for me when i quick tested 2.6.11. Although, It seems as though 2.6.11-rc* is breaking stuff left and right........ Also, if you could give any more info I'd be happy to help as i experianced a prob similer to this with 2.6.10-dark5 (test build 1) and fixed it by a simple make mrproper and recompile of both the kernel and nvidia driver..... you can try that, it might work. Anyway, more info would be a huge help.
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 8:33 pm Post subject: |
|
|
He said in a pm it was not the experimental, but one thing i can tell:
2.6.11-rc2 is probably just the beginning of the probs....
ohohoh.... |
|
| Back to top |
|
|
hermes_jr
l33t
Joined: 26 Feb 2004
Posts: 701
Location: Moscow, Russia
|
| Posted: Tue Feb 01, 2005 8:33 pm Post subject: |
|
|
| predatorfreak wrote: | | Also, if you could give any more info I'd be happy to help as i experianced a prob similer to this with 2.6.10-dark5 (test build 1) and fixed it by a simple make mrproper and recompile of both the kernel and nvidia driver..... you can try that, it might work. Anyway, more info would be a huge help. |
1. Which info exactly?
2. I've done make mrproper and recompile about 10 times in last 3 hours, and I'm tired...
Atm, my nitro is compiled with "Voluntary Kernel Preemption (Desktop)" option and nfs mount prob is still present. Also X loads in a big amount of time. I have a black blinking screen for about 2 minutes and then X loads. And in this 2 mins system doesn't react even on num lock...
Absolutely nothing suspicious in xorg.log.
Almost nothing bad in dmesg:
| Quote: |
....
eth0: link up, 10Mbps, half-duplex, lpa 0x0000
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: reserved bits set in mode 0x1f00481b. Fixed.
agpgart: X tried to set rate=x3. Setting to AGP3 x4 mode.
agpgart: X passes broken AGP2 flags (1f004813) in AGP3 mode. Fixed.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: reserved bits set in mode 0x1f00481b. Fixed.
agpgart: X tried to set rate=x3. Setting to AGP3 x4 mode.
agpgart: X passes broken AGP2 flags (1f004813) in AGP3 mode. Fixed.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
NVRM: rm_init_adapter failed
NVRM: rm_init_adapter failed
NVRM: rm_init_adapter failed
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: reserved bits set in mode 0x1f00481b. Fixed.
agpgart: X tried to set rate=x3. Setting to AGP3 x4 mode.
agpgart: X passes broken AGP2 flags (1f004813) in AGP3 mode. Fixed.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
|
|
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 8:42 pm Post subject: |
|
|
| :confused: |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Feb 01, 2005 8:53 pm Post subject: |
|
|
so, it WAS the experimental, and as such i can say that it either is caused by the bk-tree changes of agp-gart or we just have another "FEATURE" of the upcoming versions of 2.6.x > 2.6.10
 |
|
| Back to top |
|
|
discomfitor
l33t
Joined: 21 Feb 2003
Posts: 927
Location: None
|
| Posted: Tue Feb 01, 2005 8:57 pm Post subject: |
|
|
Figured as much. I'm gonna need a new release of nvidia drivers. NOW!
You heard me nvidia.
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort. |
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Tue Feb 01, 2005 9:06 pm Post subject: |
|
|
What i ment was stuff such as dmesg output, X logs, etc.
Edit: fixed a typo
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
Mon
n00b
Joined: 17 Jul 2003
Posts: 34
Location: The Netherlands
|
| Posted: Tue Feb 01, 2005 11:45 pm Post subject: |
|
|
Ok so i was cheating a bit; i was Ubuntu in my previous post. But on my Gentoo install it also doesn't work:
http://www.pastebin.com/236495
Both my Ubuntu as Gentoo installation have the correct 'linux' symlinks to the nitro directories. |
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Tue Feb 01, 2005 11:57 pm Post subject: |
|
|
| Mon wrote: |
Ok so i was cheating a bit; i was Ubuntu in my previous post. But on my Gentoo install it also doesn't work:
http://www.pastebin.com/236495
Both my Ubuntu as Gentoo installation have the correct 'linux' symlinks to the nitro directories. |
It appears as though your using -r1 when -r3 is the only one known to work with 2.6.11-rc*. Please try ACCEPT_KEYWORDS="~x86" emerge nvidia-kernel.
~predatorfreak
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Wed Feb 02, 2005 12:02 am Post subject: |
|
|
thanks...
and if it doesn't work, try the patch I posted a few posts upstairs....
T |
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Wed Feb 02, 2005 12:06 am Post subject: |
|
|
Also on a side note, I'm going to generate some highload conditions to test 2.6.10-dark5 (test build 3) and likely release it in a day or two.
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Wed Feb 02, 2005 12:15 am Post subject: |
|
|
I'll probably be setting up a server in a few days, and while dark5 is getting really hardened, it'll probably be powering this baby...
hmm, i think we can expect realtime enabled staircase scheduler by tomorrow..... 
T
probably
EDIT: g'night, it's 3 am here.
Last edited by Tiger683 on Wed Feb 02, 2005 1:09 am; edited 1 time in total |
|
| Back to top |
|
|
nikopol
n00b
Joined: 27 Sep 2004
Posts: 7
Location: /home/Braga
|
| Posted: Wed Feb 02, 2005 12:35 am Post subject: |
|
|
| predatorfreak wrote: |
It appears as though your using -r1 when -r3 is the only one known to work with 2.6.11-rc*. Please try ACCEPT_KEYWORDS="~x86" emerge nvidia-kernel.
~predatorfreak |
-r3 is the answer. Compiles and runs fine.
ACCEPT_KEYWORDS="-x86" |
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Wed Feb 02, 2005 1:16 am Post subject: |
|
|
| nikopol wrote: | | predatorfreak wrote: |
It appears as though your using -r1 when -r3 is the only one known to work with 2.6.11-rc*. Please try ACCEPT_KEYWORDS="~x86" emerge nvidia-kernel.
~predatorfreak |
-r3 is the answer. Compiles and runs fine.
ACCEPT_KEYWORDS="-x86" |
Typo there, its ~ not - .
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
nikopol
n00b
Joined: 27 Sep 2004
Posts: 7
Location: /home/Braga
|
| Posted: Wed Feb 02, 2005 1:21 am Post subject: |
|
|
| Yes... need more caffeine. |
|
| Back to top |
|
|
The_Master
n00b
Joined: 23 Feb 2004
Posts: 14
|
| Posted: Wed Feb 02, 2005 2:43 am Post subject: |
|
|
This happened after running for about 2 days.
| Code: |
------------[ cut here ]------------
kernel BUG at arch/i386/mm/pageattr.c:136!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: fglrx
CPU: 0
EIP: 0060:[<c0112154>] Tainted: P VLI
EFLAGS: 00213082 (2.6.11-rc2-nitro1)
EIP is at __change_page_attr+0x12c/0x1a9
eax: 0000bd20 ebx: c16d4600 ecx: c100bd20 edx: c1000000
esi: c05e9f68 edi: 00000163 ebp: f6a30000 esp: f6917eb8
ds: 007b es: 007b ss: 0068
Process X (pid: 4942, threadinfo=f6916000 task=f772f020)
Stack: c16d4600 00000010 00000000 00000011 c011220f 00203246 00000163 c16d4400
f69e75a0 00000004 00001000 c0111e73 00000163 00000000 00000163 00000000
f8c67fbb f8c9dd60 00000000 f8c9dd60 00000000 f8c6de02 f8c70d4d f8c850f5
Call Trace:
[<c011220f>] change_page_attr+0x3e/0x95
[<c0111e73>] iounmap+0x7d/0x9a
[<f8c67fbb>] agp_generic_free_gatt_table+0x5b/0xc0 [fglrx]
[<f8c6de02>] agp_backend_cleanup+0xc/0x45 [fglrx]
[<f8c70d4d>] __ke_agp_uninit+0x1a/0x25 [fglrx]
[<f8c850f5>] _firegl_release_agp+0x15/0x140 [fglrx]
[<f8c72f35>] firegl_takedown+0x335/0xb90 [fglrx]
[<f8c7233f>] firegl_release+0x12f/0x190 [fglrx]
...
|
|
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Wed Feb 02, 2005 3:16 am Post subject: |
|
|
what version are you using (realtime/normal)? I believe tiger683 is working on a new realtime version which fixes up the agp probs. Other then that, I'd don't know, it looks to me like it might be a preempt bug (which is why i asked if you where using the realtime version as ALOT of preempt changes where made in this version).
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
