Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 01-10-05, 08:33 AM   #49
brcha
Registered User
 
brcha's Avatar
 
Join Date: Jan 2005
Location: Belgrade, Serbia
Posts: 2
Send a message via ICQ to brcha Send a message via MSN to brcha Send a message via Yahoo to brcha
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Quote:
Originally Posted by nukem
Sigh this does not work either. When I start Doom3 the system just hangs and I have to hard reboot. After I applied your patch I looked through all my logs in /var/log and I didnt even see an entry for the time it crashed. Could someone PLEASE help me?
Try running doom like
doom &>logfile

and then try to wait for some time before rebooting.

Btw, did you try to press CTRL+ALT+F1 to enter the console mode when doom hangs? Or maybe even CTRL+ALT+BACKSPACE.
brcha is offline   Reply With Quote
Old 01-10-05, 07:00 PM   #50
nukem
Registered User
 
Join Date: Dec 2004
Posts: 226
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Quote:
Originally Posted by brcha
Try running doom like
doom &>logfile

and then try to wait for some time before rebooting.

Btw, did you try to press CTRL+ALT+F1 to enter the console mode when doom hangs? Or maybe even CTRL+ALT+BACKSPACE.
I tired doom3 &> logfile and no log file was created. I guess it wasnt written since the system crashed. I have tried CTRL+ALT+F1 CTL+ALT+BACKSPACE and I have started sshd to ssh into my computer and none of them worked. Ive looked in /var/log and have seen nothing. Tell me if there is a partical file you'd like to look at.

Thanks

nuke
nukem is offline   Reply With Quote
Old 01-11-05, 10:01 AM   #51
~Searcher~
crazy IT fish
 
Join Date: Jan 2005
Location: Ukraine
Posts: 2
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Someone knows howto build 6629 driver on 2.6.10-mm2

I've tried all patches above, but got tthe same result - unable to build module.

Trouble is discovered on the stage of building (gcc) the code - multi errors of compilations.

Will be grateful for any help.

TO ALL (especially to the nvidia guys)

PS: What about gathering all patches for any kind of nvidia drivers and any kernel version in one place?
May be there is such prodject?
May be nvidia will create it?
~Searcher~ is offline   Reply With Quote
Old 01-11-05, 04:52 PM   #52
vinx77
another user
 
Join Date: Jan 2005
Location: Groningen, the Netherlands
Posts: 11
Thumbs down Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

NVIDIA-Linux-x86-1.0-6629-pkg1.run is available (PKG1).

There are no compile-errors, so nVidia used your patch

Ijust upgraded my Fedora-kernel to 2.6.10-1.737_FC3 and I now get an boot-error "nvidia-kernel cannot be found" with a reference to 2.6.10. Has someone had this problem too?
vinx77 is offline   Reply With Quote
Old 01-11-05, 05:09 PM   #53
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

For clarification: the -pkg1 variant differs from its -pkg0 sibling only in that the former includes precompiled kernel interfaces, whereas the latter does not; 1.0-6629 does build against Linux 2.6.10, but may not work correctly unpatched.
zander is offline   Reply With Quote
Old 01-11-05, 06:25 PM   #54
Lithorus
Registered User
 
Lithorus's Avatar
 
Join Date: Sep 2004
Posts: 783
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Quote:
Originally Posted by vinx77
NVIDIA-Linux-x86-1.0-6629-pkg1.run is available (PKG1).

There are no compile-errors, so nVidia used your patch

Ijust upgraded my Fedora-kernel to 2.6.10-1.737_FC3 and I now get an boot-error "nvidia-kernel cannot be found" with a reference to 2.6.10. Has someone had this problem too?
New kernel means you probably have to reinstall the nvidia driver.
Lithorus is offline   Reply With Quote
Old 01-12-05, 04:56 PM   #55
marekjs
Registered User
 
Join Date: Nov 2004
Posts: 8
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Hi.
Fast question to brcha...
No problem to patch kernel 2.6.10 with your patch.Next I recompile my kernel.Successfull. Reboot. It runs. Next I install drivers 6111, because I've TNT2. Successfull. Startx. It runs. Next rebooting my Slack 10 again, and.... no screens found after startx. Strange.
What I do wrong?

marekjs

PS. No problem with 2.6.8.1+nvidia-6111 under Slack 10
marekjs is offline   Reply With Quote
Old 01-12-05, 06:37 PM   #56
heitkergm
Registered User
 
Join Date: Jan 2005
Posts: 1
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Folks - congrats go to Zander. I followed his instructions exactly on patching 6629 for use in 2.6.10 kernels (see the first post).

I can now boot 2.6.10 into init level 5, and get my accelerated nvidia driver. I'm pleased, to say the least.

FYI - AMD Opteron 64, Fedora Core 3 x86-64, kernel-2.6.10-1.737_FC3, nvidia Quadro NVS 280, Sun w1100z

Thanks, Matt
heitkergm is offline   Reply With Quote

Old 01-14-05, 05:09 AM   #57
Albert_V
Registered User
 
Albert_V's Avatar
 
Join Date: Jan 2005
Posts: 5
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

Hi. I have 2.6.10 and nvidia driver 1.0-6629 with a GeForce 6600 PCI-Express. More info in this thread.
Glxgears freezes computer with and without zanders patches. Is it my card that doesnt work or is it the combination between 2.6.10 and the nvidia driver?
Albert_V is offline   Reply With Quote
Old 01-21-05, 01:53 AM   #58
vherva
Registered User
 
Join Date: Aug 2003
Posts: 25
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

I just upgraded from 2.8.6.1-mm2 to 2.6.11-rc1-ck2 and NVIDIA-6111 to 6629.

I get the black screen on startx and this crash on logs:


Jan 20 22:24:35 host kernel: ------------[ cut here ]------------
Jan 20 22:24:35 host kernel: kernel BUG at arch/i386/mm/pageattr.c:136!
Jan 20 22:24:35 host kernel: invalid operand: 0000 [#1]
Jan 20 22:24:35 host kernel: PREEMPT
Jan 20 22:24:35 host kernel: Modules linked in: nvidia snd_pcm_oss snd_mixer_oss ppp_async crc_ccitt ppp_generic slhc 8250_pci 8250 serial
_core ide_cd cdrom w83781d i2c_sensor i2c_isa vmnet parport_pc parport vmmon microcode binfmt_misc nls_iso8859_1 nls_cp437 dm_mod i2c_i801 i2
c_core snd_intel8x0 snd_ac97_codec snd_ens1370 snd_rawmidi snd_seq_device snd_pcm snd_timer snd_page_alloc snd_ak4531_codec snd e100 mii
Jan 20 22:24:35 host kernel: CPU: 0
Jan 20 22:24:35 host kernel: EIP: 0060:[<c0113391>] Tainted: P VLI
Jan 20 22:24:35 host kernel: EFLAGS: 00213082 (2.6.11-rc1-ck1vh1)
Jan 20 22:24:35 host kernel: EIP is at __change_page_attr+0x151/0x160
Jan 20 22:24:35 host kernel: eax: 000022d7 ebx: 04270000 ecx: c1008b5c edx: 040001e3
Jan 20 22:24:35 host kernel: esi: c03dfc40 edi: 00000163 ebp: c1000000 esp: c5e51da8
Jan 20 22:24:35 host kernel: ds: 007b es: 007b ss: 0068
Jan 20 22:24:35 host kernel: Process X (pid: 8134, threadinfo=c5e50000 task=dda05ac0)
Jan 20 22:24:35 host kernel: Stack: c4270000 c10957c0 00000010 00000000 00000011 c01133fb 00203286 00000163
Jan 20 22:24:35 host kernel: c1000000 dd209bc0 c063f400 c5e51e1c c011302e 00203282 00021000 00010000
Jan 20 22:24:35 host kernel: e0c20000 e1171491 e0f86180 e0c20000 00010000 c063f400 e0f86173 dffaf400
Jan 20 22:24:35 host kernel: Call Trace:
Jan 20 22:24:35 host kernel: [<c01133fb>] change_page_attr+0x5b/0x70
Jan 20 22:24:35 host kernel: [<c011302e>] iounmap+0x7e/0xa0
Jan 20 22:24:35 host kernel: [<e1171491>] os_unmap_kernel_space+0x9/0xa [nvidia]
Jan 20 22:24:35 host kernel: [<e0f86180>] _nv001706rm+0x20/0x2c [nvidia]
Jan 20 22:24:35 host kernel: [<e0f86173>] _nv001706rm+0x13/0x2c [nvidia]
Jan 20 22:24:35 host kernel: [<e0f82731>] _nv002359rm+0xe9/0x184 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f79a7a>] _nv001955rm+0x36/0xe0 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f8b634>] _nv001297rm+0x9c/0xa8 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f8c98c>] rm_teardown_agp+0x48/0x50 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f79a7a>] _nv001955rm+0x36/0xe0 [nvidia]
Jan 20 22:24:35 host kernel: [<e116fb88>] nv_agp_teardown+0x52/0x88 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f885cb>] _nv001708rm+0x73/0xa0 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f7a4a6>] _nv001847rm+0x26/0x2c [nvidia]
Jan 20 22:24:35 host kernel: [<e0f88f7c>] _nv000650rm+0x58/0xcc [nvidia]
Jan 20 22:24:35 host kernel: [<e0f88fd7>] _nv000650rm+0xb3/0xcc [nvidia]
Jan 20 22:24:35 host kernel: [<e0f89671>] _nv001362rm+0x71/0xb0 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f8967e>] _nv001362rm+0x7e/0xb0 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f864be>] _nv001820rm+0x12/0x18 [nvidia]
Jan 20 22:24:35 host kernel: [<e0f8c0e7>] rm_disable_adapter+0x2f/0x8c [nvidia]
Jan 20 22:24:35 host kernel: [<e0f8c117>] rm_disable_adapter+0x5f/0x8c [nvidia]
Jan 20 22:24:35 host kernel: [<e0f8c10b>] rm_disable_adapter+0x53/0x8c [nvidia]
Jan 20 22:24:35 host kernel: [<e116d990>] nv_kern_close+0x15d/0x1ca [nvidia]
Jan 20 22:24:35 host kernel: [<c0152fc6>] __fput+0x106/0x120
Jan 20 22:24:35 host kernel: [<c015171f>] filp_close+0x4f/0x80
Jan 20 22:24:35 host kernel: [<c0102f71>] sysenter_past_esp+0x52/0x75
Jan 20 22:24:35 host kernel: Code: 89 f0 c1 e1 0c 09 e9 e8 4e fe ff ff 89 d9 e9 28 ff ff ff 8d b4 26 00 00 00 00 80 3e 00 78 0c 09 fb 89 1
e ff 49 04 e9 13 ff ff ff <0f> 0b 88 00 3c 39 30 c0 e9 06 ff ff ff 89 f6 55 89 d5 57 31 ff


(For full log, see http://iki.fi/v/tmp/nvidiacrash.log.)

-ck2 has some NVIDIA compability patch (http://ck.kolivas.org/patches/2.6/2....9_compat2.diff).

I also tried applying all the patches from http://www.minion.de/files/1.0-6629/ (which ones should I apply, all?) The result is the same.

Any ideas?

Con, if you are reading this: I really like -ck (I just got around to try it after using -mm and -ac for a long time). What's the difference between 11-rc1-ck2 and 10-ck5? Which one do you recommend?
vherva is offline   Reply With Quote
Old 01-21-05, 08:19 AM   #59
skye777
Registered User
 
Join Date: Jan 2005
Posts: 2
Unhappy Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

I just tried the patches you have suggested, and I'm suffering terribly here. No success installing 6629 or any other nVidia proprietary driver on my new MX4000plus 128 meg ddr agp card. Running SuSE 9.2 on an Athlon 2.7 ghz processor (i386 architecture). The kernel modules appear to install smoothly and normally using the patched installer, and finish with no error messages. On running: sax2 -m 0=nvidia, the nVidia splash appears, and remains on screen. The sax2 dialogue box which invites you to save or reject the configuration sax2 comes up , overlaid over the nVidia splash, in a trashy sort of mess, and sax2 dies there, with the tantalizing nVidia splash just stuck there, in the middle of the sax2 configuration process. I left that alone for about 90 minutes, but it never progressed or fixed itself. On reboot, it arrives at the same scrambled mess, and has required interveneing with a knoppix session to reset inittab to level 3.

Got any help or suggestions for me here? I'm on the verge of returning the damned graphics card in favor of ATI. Thanks!

Skye
skye777 is offline   Reply With Quote
Old 01-21-05, 08:55 AM   #60
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-6629 x86/x86-64 and Linux 2.6.10

@skye777: you're seeing a known problem with 1.0-6629 and your graphics card, please downgrade to 1.0-6111 or use the XFree86/Xorg "nv" driver until an updated driver has been made available.
zander is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 03:47 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.