Gerhard den Hollander wrote:
* Basil Chupin <blchupin@tpg.com.au> (Tue, Sep 16, 2003 at 01:50:08AM +1000)
Im running k_athlon w/ nvidias 4496 and no problems
The trick is: 0) telinit 3 1) install K_athlon and k_sources 2) cd /usr/src/linux 3) make cloneconfig 4) edit include/linux/version.h and make sure it looks like this #define UTS_RELEASE "2.4.20-4GB-athlon" #define LINUX_VERSION_CODE 132116 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) 5) export IGNORE_CC_MISMATCH=true 6) sh NVIDIA-Linux-x86-1.0-4496-pkg2.run or 6) sh NVIDIA-Linux-x86-1.0-4496-pkg2.run --extract-only 6a)cd NVIDIA-Linux-x86-1.0-4496-pkg2 6b) make install 7) startx
the tricky bits are step 3) [as the kernel sources are not configed for athlon] and step 4) `(as the standard version.h calls a different UTS_RELEASE).
Everything that you mention above has been followed closely over and over again in the past few weeks with the same results- the driver doesn't perform.
What you say under point (4) re version.h does not need modification - at least on my system - because that is exactly what is shown in my file (ie without having to do any fiddling).
The only other thing is under (5): you use "=true" whereas SuSE's HOWTO states "=yes". I wonder if this would make a difference?
Nope. All that needs to happen is for IGNORE_CC_MISMATCH to have a value The line in the makefile states:
@if [ -z $(IGNORE_CC_MISMATCH) ]; then \
So either export IGNORE_CC_MISMATCH=suse_rules or export IGNORE_CC_MISMATCH=nvidia_sucks or export IGNORE_CC_MISMATCH=somethignVeryRude or .... will work.
I've gotten in the habit of setting Variables to true if they need to have ``any'' value. Suse seems to default to using yes.
The 64 mllion $ question here, of course, is: do you have 3D engaged in your setup? And if so, you have no troubles with using CTRL-ALT-F1 to F6 as well as CTRL-ALT-F1 and you don't get a flashing multi-coloured screen when reboting or shutting down?
Yes, 3D is enabled Ctrl-Alt-F works No flashing multicolored screen when rebooting
[Well, that is not entirely true. I have had the Ctrl-Alt-F giving me garbage problem with the 4496 driver once or twice, but that was with an earlier kernel.
It is true that after long and prolonged 3D usage without restarting the X-server then after a while (2 weeks, 3 weeks ?) the Nvidia kernel moduls gets a tad confused and Ctrl-Alt-F gives garbage ]
What video card are you using ?
I am using a GeForce4 MX 440 (64Mb DDR) Well, I just, yet and once again, tried to install the 4496 using the procedure you spelt out and with the same result: 4496 creates all those problems for me. So I went back to 4363. Just one more interesting piece of information re 496 and 4363. When I had the 4496 installed I tried the Gears test and the best fps I got was 2822. When I switched back to 4363 I now get 3206 fps. Cheers. -- Hire teenagers while they still know everything.