

I have the same problem....tho I found out that the problem is with the glx driver...I think....at least I can startx with xorg-X11 opengl implementation.Phlogiston. wrote:on my machine it does not work: I can compile the driver but when I start X, the screen stays black and nothing happens. After this I get an unknown error from X. I'm using nitro sources thats probably the reason why it does not work. Any hints?

This works beautifully on kernel 2.6.12-gentoo-rc9, but not all former functionality is restored: glx is broken. I had to disable the glx extensionbaeksu wrote:[note: I couldn't get the overlay from this thread to work, so I'm using the normal files one portage and just adding this patch into the ebuild. I'm assuming you know how to use a local portage overlay.]piwacet wrote:I'd like to try to use the above hack as well, what file is this so I can edit it?
Thanks.
edit: this is a file from the overlay I need to download, isn't it?
Easiest is to copy the nvidia-kernel directory from the normal portage overlay to a local one. Then save the above patch as a file, call it "inter_module_fix.patch", or whatever you like.
Copy the file to nvidia-kernel/files/1.0.6111/
Edit the nvidia-kernel-1.0.6111-r3.ebuild, and add "epatch ${FILESDIR}/${PV}/inter_module_fix.patch" to where all the other patches are handled (between lines 99-108 look fine)
Do an 'ebuild nvidia-kernel-1.0.6111-r3.ebuild digest'.
Emerge nvidia-kernel, and check that the new patch is applied.
Remember that you should have AGPGART disabled in your kernel.
The end.
Doesn't all 7x versions freeze when composite is enabled? That's kind of a stopper for me, as I don't play games (so I didn't know about the broken glx), and I only need the gfx drivers for better composite rendering.Princess Nell wrote:Interesting aside: the latest nvidia 1.0.7676 works, kindam a novelty since 1.0.6629, but it's severly broken: when I log out or try to switch VCs,
the machine hangs completely, and I can't even login remotely to shut X down.

PrakashP, I tried reversing the patch, but X still wouldn't start. Instead, I get:PrakashP wrote:OK, I managed to get 6111 drivers working an 2.6.12-git3 and later.
You have to revert this patch. (This won't hurt, as it only puts something back, which shouldn't affect the rest of the kernel.)
Unfortunately I don't have a clue how to fix the driver. Going from class_simple to class won't help, as the hooks are GPLed. Latest Nvidia drivers work, as they use some other method.
Code: Select all
(WW) ****INVALID MEM ALLOCATION**** b: 0xe8000000 e: 0xf0000000 correcting
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration
Well, whaddya know, now it suddenly started working...I swear I changed absolutely nothing, and now suddenly it works!PrakashP wrote:All I can say is, it works fine for me with 2.6.13. The only thing I had to manually adjust in the patch is a Makefile.
Perhaps your MTRR setup is messed up?

I've been using this patch from the thread and it's working quite fine fine with nitro-sources (2.6.12). For 2.6.13 (including ck-patches), you need to patch the kernel as described here.Phlogiston. wrote:did anyone try this with nitro or ck sources? Thx

Code: Select all
NVIDIA: failed to set MTRR 0xd0000000, 256M (write-combining)
(EE) NVIDIA(0): Failed to load GLX
Code: Select all
***** inter_module_fix.patch *****
==================================
PATCH COMMAND: patch -p0 -g0 --no-backup-if-mismatch < /usr/local/portage/media-video/nvidia-kernel/files/1.0.6111/inter_module_fix.patch
==================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/Makefile
|+++ b/drivers/base/Makefile
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file a/drivers/base/class_simple.c,
which does not exist! Applying it anyway.
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/class_simple.c
|+++ /dev/null
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 216
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/include/linux/device.h
|+++ b/include/linux/device.h
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
==================================
PATCH COMMAND: patch -p1 -g0 --no-backup-if-mismatch < /usr/local/portage/media-video/nvidia-kernel/files/1.0.6111/inter_module_fix.patch
==================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/Makefile
|+++ b/drivers/base/Makefile
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file drivers/base/class_simple.c,
which does not exist! Applying it anyway.
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/class_simple.c
|+++ /dev/null
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 216
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/include/linux/device.h
|+++ b/include/linux/device.h
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
==================================
PATCH COMMAND: patch -p2 -g0 --no-backup-if-mismatch < /usr/local/portage/media-video/nvidia-kernel/files/1.0.6111/inter_module_fix.patch
==================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/Makefile
|+++ b/drivers/base/Makefile
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file base/class_simple.c,
which does not exist! Applying it anyway.
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/class_simple.c
|+++ /dev/null
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 216
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/include/linux/device.h
|+++ b/include/linux/device.h
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
==================================
PATCH COMMAND: patch -p3 -g0 --no-backup-if-mismatch < /usr/local/portage/media-video/nvidia-kernel/files/1.0.6111/inter_module_fix.patch
==================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/Makefile
|+++ b/drivers/base/Makefile
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file class_simple.c,
which does not exist! Applying it anyway.
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/class_simple.c
|+++ /dev/null
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 216
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/include/linux/device.h
|+++ b/include/linux/device.h
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
==================================
PATCH COMMAND: patch -p4 -g0 --no-backup-if-mismatch < /usr/local/portage/media-video/nvidia-kernel/files/1.0.6111/inter_module_fix.patch
==================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/base/Makefile
|+++ b/drivers/base/Makefile
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 14 of patch
patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed.
/usr/portage/eclass/eutils.eclass: line 248: 23196 Done cat ${PATCH_TARGET}
23197 Abgebrochen | patch -p${count} ${popts} --dry-run -f
The patch itself won't apply cleanly, as it is in a different format. I actually can't/won't bother figure out how to change it, being still quite new to linux. Also, the first chunk won't work, as there are some changes to the file after the initial versions, so you better do it manually, changing the first and third chunks manually, and creating class_simple.c (second chunk) from the patch file yourself.tuxian wrote:Which patch is needed for gentoo-dev-sources-2.6.13?
Is used the patch from PrakashP's posting.

I have one MX4000 64MB which works with 6629 and I have another MX4000 128MB which doesn't. Obviously it depends on each card.moocha wrote:GF4MX440 working with 6629? Whoa. Never seen that before. My information came from the official NVIDIA forums - they stated that 6629 had a known bug that caused pre-NV20 cores not to work with 6629...voytas wrote:not true, i have NV17 card (GF4 MX 440) and it works with this driver...moocha wrote:Then why shouldn't I use 1.0.6629?
1.0.6629 has a known bug that prevents cards using cores older than NV20 from working under X at all (affected are, for example, GeForce4 MX440 series cards - i.e., mine). If your card ran fine under 1.0.6629 then by all means use that one. I don't know whether it compiles on recent kernels though, because I can't use it.
i had a TNT2PRO cards ant it didn't work with noting newer than 6111

Thx in advance!PrakashP wrote:OK, I managed to get 6111 drivers working an 2.6.12-git3 and later.
You have to revert this patch. (This won't hurt, as it only puts something back, which shouldn't affect the rest of the kernel.)
Unfortunately I don't have a clue how to fix the driver. Going from class_simple to class won't help, as the hooks are GPLed. Latest Nvidia drivers work, as they use some other method.


The patch have been applied successfully although now I have this error msg when trying to start X server:baeksu wrote:You can reverse with this patch. Just do 'patch -p1 -R --dry-run', then without dry-run if it works. Worked for me.
2.6.14 kernels don't need the patch, from what I've tried.
Code: Select all
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWUnlock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWUnlock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWSave from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWUnlock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWSave from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWLock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWLock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWUnlock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWLock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWUnlock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWSaveScreen from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWLock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWUnlock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Required symbol vgaHWLock from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Symbol vgaHWGetIndex from module /usr/lib/modules/drivers/nvidia_drv.o is unresolved!
Fatal server error:
Some required symbols were unresolved
Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.