First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 15722
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: x86-kernel@gentoo.org (DEPRECATED) <x86-kernel@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jay Pfeifer (RETIRED) <pfeifer@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
nvidia-kernel-1.0.4191-r1.ebuild sample updated ebuild text/plain Jay Pfeifer (RETIRED) 2003-02-15 07:53 0000 3.81 KB Details
nvidia-kernel-1.0.4191-r2.ebuild ebuild w/simple check for rmap on 2.4 kernels text/plain Jay Pfeifer (RETIRED) 2003-02-22 08:34 0000 3.91 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 15722 depends on: Show dependency tree
Bug 15722 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-02-14 20:31 0000
rmap15b has issues with nvidia-kernel 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



solution is here: 
http://members.optusnet.com.au/ckolivas/kernel/nvidia-rmap15b.patch

------- Comment #1 From Jay Pfeifer (RETIRED) 2003-02-14 21:42:47 0000 -------
want to clarify. i know that a rmap patch exists in the nvidia-kernel ebuild,
but it fails to 
help with highmem/rmap when used on lolo-sources 2.4.20r1_rc3 or higher. It
works fine on 
lolo-sources 2.4.20-r1_rc2 and earlier. the patch earlier does not help. 

------- Comment #2 From Jay Pfeifer (RETIRED) 2003-02-14 22:26:09 0000 -------
ok. the fix was right under our noses... we apply the patch from here: 
http://www.minion.de/files/NVIDIA_kernel-1.0-4191-2.5-tl.diff 
only to 2.5 kernels...  :-) 
 
it is also for the rmap issue on 2.4 - i'll get an update ebuild attached in a bit. 
 
patch works great so far... 
 
regards, 
 
_j_ 

------- Comment #3 From Jay Pfeifer (RETIRED) 2003-02-15 07:53:40 0000 -------
Created an attachment (id=8298) [details]
sample updated ebuild

maybe this should be assigned to azarah? it is a fix for the nvidia-kernel
ebuild... 
 
anyway, he is a sample updated ebuild that will patch 2.4 as well as 2.5 based
kernels. i also 
removed the seemingly outdated rmap patch we were using. 
 
regards, 
 
_j_ 

------- Comment #4 From Brandon Low (RETIRED) 2003-02-21 20:27:34 0000 -------
az, please take a look at this, I'm not sure what we should do about this since
only some kernels currently use rmap... thanks.

------- Comment #5 From Martin Schlemmer (RETIRED) 2003-02-22 06:37:51 0000 -------
The patch in protage is the updated on.  Now, we could apply it for 2.4
kernels,
only problem is .... will it work fine with non rmap kernel ?

------- Comment #6 From Jay Pfeifer (RETIRED) 2003-02-22 08:16:34 0000 -------
ok, how about this: 
 
we have to have the running kernel's sources in /usr/src/linux so... 
so, we already do the check for 2.4 vs 2.5, when it comes up as 2.4 
why don't we have the ebuild check for /usr/src/linux/mm/rmap.c 
if it exists... apply the patch(NVIDIA_kernel-1.0-4191-2.5-tl.diff), if not skip it. 
 
make sense? 
 
i'll write a sample ebuild and post in a bit. 
 
regards, 
 
_j_ 

------- Comment #7 From Jay Pfeifer (RETIRED) 2003-02-22 08:34:22 0000 -------
Created an attachment (id=8606) [details]
ebuild w/simple check for rmap on 2.4 kernels

basically reworked this minor change to the ebuild:

local RMAPSRC="/usr/src/linux/mm/rmap.c"

    cd ${S}
    if [ "${KV_major}" -eq 2 -a "${KV_minor}" -eq 4 ] && [ -r "${RMAPSRC}" ]
    then
	einfo "Detected rmap enabled kernel."
	EPATCH_SINGLE_MSG="Applying rmap patch for kernel 2.4..." \
	epatch ${FILESDIR}/${NV_PACKAGE}-2.5-tl.diff
    fi


_j_

------- Comment #8 From Jay Pfeifer (RETIRED) 2003-03-04 20:48:35 0000 -------
added updated ebuild to cvs. 

------- Comment #9 From Jay Pfeifer (RETIRED) 2003-03-07 23:05:02 0000 -------
closing as the nvidia-kernel/rmap15b issue seems to be resolved.

First Last Prev Next    No search results available      Search page      Enter new bug