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

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-15-05, 06:29 AM   #133
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-8174 for Linux x86 released

@catimimi: if you're not planning on using APM power management, you can build the kernel without CONFIG_PM; else you can compile it with CONFIG_PM_LEGACY or alternatively apply this patch: http://www.nvnews.net/vbulletin/show...06&postcount=1.
zander is offline   Reply With Quote
Old 12-15-05, 07:59 AM   #134
catimimi
Registered User
 
Join Date: Jan 2004
Posts: 52
Default Re: 1.0-8174 for Linux x86 released

Thanks Zander, it works with the patch. My kernel was already compiled with the legacy option and the nvidia module didn't compile.
Can I tell you, that it is a little difficult to compile the x86_64 module since the texts messages have no spaces, and the screen is not blanked so that new messages overwrites older ones. But when you know what are the questions, you manage to work around.

Thanks for these well working modules.

Michel

I run Geforce 7800 GTX
catimimi is offline   Reply With Quote
Old 12-15-05, 09:57 AM   #135
LuckyLoop
Registered User
 
Join Date: Dec 2005
Location: Toulouse France
Posts: 20
Question support nvs 285 pci-e

Hi,
Do you know when the nvs 285 were supported ?
I tested nvs 285 pci-e on a chipset ATI rs480, with kernel 2.4.30 and 2.6.14 with XFree86 4.5.0 and Xorg 6.8.2 and 6.9 , X was unstabled.
But on a chipset intel 915 no problem !
Thanks

Luc
LuckyLoop is offline   Reply With Quote
Old 12-15-05, 10:53 AM   #136
bigmack
Registered User
 
Join Date: Dec 2005
Posts: 1
Exclamation Re: 1.0-8174 for Linux x86 released

Ok, I have latest (8174) installed, and am running an FX-5200 video card. I am running on an old ABIT motherboard. I am running Fedord FC3 (kernel is 2.6.11-1.14) .

EVERYTHING IS FINE, until .... I start X and I am up and running for a few minutes, then the X system hangs. Mouse is still active, but it takes a hard reset to get control back on the system. CTRL+ALT+BS does nothing.

Any suggestions???
bigmack is offline   Reply With Quote
Old 12-15-05, 05:18 PM   #137
Darkvater
Registered User
 
Join Date: Feb 2005
Posts: 57
Default Re: 1.0-8174 for Linux x86 released

8174 definitely has regressed with respect to the console framebuffer corruption. While in previous generations the console was (VT1) unusable with tv-out plugged in, now also VT7 (X server) is unusable when I restart X after I disconnect the video-cable to get my normal desktop back. Corrupted as hell .

Relevant section(s) from xorg.conf in case I might've done something wrong but it worked until now:
Quote:
Option "RenderAccel" "On"
Option "AllowGLXWithComposite" "1"
Option "HWCursor" "1"
Option "TwinView"
Option "HorizSync" "TV-0: 30-50"
Option "VertRefresh" "TV-0: 60"
Option "TwinViewOrientation" "DFP-0 LeftOf TV-0"
Option "TVOutFormat" "COMPOSITE"
Option "TVOverScan" "0.9"
Option "MetaModes" "DFP-0: 1280x1024, TV-0: 800x600"
Composite insidie KDE 3.4 itself is disabled on my SUSE 9.3 box with my FX5600.
Quote:
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
Option "XFIXES" "Enable"
Option "DAMAGE" "Enable"
EndSection
Darkvater is offline   Reply With Quote
Old 12-16-05, 08:59 PM   #138
archangelis
Registered User
 
Join Date: Sep 2005
Posts: 2
Unhappy Re: 1.0-8174 for Linux x86 released

Kernel oops loading 8174 on Fedora Core 4. Tried 8174 both with and without ACPI patch, and with many different options. Same virtual address accessed (0xf4) each time.

Can someone point to a workaround or immediate patch? I am having great difficulty getting older Nvidia drivers to work with newer kernels and want to use 8174. But it doesn't work!

Kernel log follows.

Dec 15 21:57:04 xxxxxx kernel: NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-8174 Tue Nov 22 17:48:37 PST 2005
Dec 15 21:57:05 xxxxxx kernel: NVRM: not using NVAGP, an AGPGART backend is loaded!
Dec 15 21:57:05 xxxxxx kernel: Unable to handle kernel NULL pointer dereference at virtual address 000000f4
Dec 15 21:57:05 xxxxxx kernel: printing eip:
Dec 15 21:57:05 xxxxxx kernel: e14ba05a
Dec 15 21:57:05 xxxxxx kernel: *pde = 1a8c6067
Dec 15 21:57:05 xxxxxx kernel: Oops: 0000 [#1]
Dec 15 21:57:05 xxxxxx kernel: Modules linked in: nvidia(U) ipv6 parport_pc lp parport i2c_dev i2c_core pcmcia acpi_cpufreq ath_pci(U) ath_rate_sample(U) wlan(U) ath_hal(U) video button battery ac ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd snd_maestro3 snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd soundcore eepro100 e100 mii floppy dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod
Dec 15 21:57:05 xxxxxx kernel: CPU: 0
Dec 15 21:57:05 xxxxxx kernel: EIP: 0060:[<e14ba05a>] Tainted: PF VLI
Dec 15 21:57:05 xxxxxx kernel: EFLAGS: 00013293 (2.6.14-1.1653_FC4)
Dec 15 21:57:05 xxxxxx gdm[1898]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Dec 15 21:57:05 xxxxxx kernel: EIP is at _nv003913rm+0x7ca/0x198c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: eax: 00000000 ebx: d9081c00 ecx: da4fc800 edx: 00000000
Dec 15 21:57:05 xxxxxx kernel: esi: 00000000 edi: d99fbc3d ebp: d99fbc54 esp: d99fbabc
Dec 15 21:57:05 xxxxxx kernel: ds: 007b es: 007b ss: 0068
Dec 15 21:57:05 xxxxxx kernel: Process X (pid: 1973, threadinfo=d99fb000 task=d99f6ab0)
Dec 15 21:57:05 xxxxxx kernel: Stack: badc0ded 00000000 00000000 00000004 e145a506 ddbe2000 da4fc800 dae52800
Dec 15 21:57:05 xxxxxx kernel: e145a506 dae5281c 0000002e d99fbb04 0000000d 00000001 da4fc800 d97a9000
Dec 15 21:57:05 xxxxxx kernel: d97a9c00 ddbe2000 dae52800 d97a9800 e15b02dd 00000000 00000080 d90be000
Dec 15 21:57:05 xxxxxx kernel: Call Trace:
Dec 15 21:57:05 xxxxxx kernel: [<e145a506>] _nv002418rm+0x26/0x2c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e145a506>] _nv002418rm+0x26/0x2c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b02dd>] _nv005094rm+0x19/0x40 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146a91a>] _nv002304rm+0x1a/0x6c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15af863>] _nv004901rm+0x8f/0x9c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15afa9e>] _nv004942rm+0x6a/0x7c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e154b7ec>] _nv000389rm+0x24/0x28 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e154b7bf>] _nv000426rm+0x1f/0x28 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e154828e>] _nv000387rm+0x4e/0x58 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b1a59>] _nv004931rm+0x51/0x90 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b17f0>] _nv005111rm+0x74/0x80 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e145a506>] _nv002418rm+0x26/0x2c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e145a534>] _nv002412rm+0x28/0x30 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e14b804d>] _nv003914rm+0x33d/0x1228 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e145a380>] _nv002423rm+0x38/0x50 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146a840>] _nv001818rm+0xe4/0x150 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146ad1f>] _nv002215rm+0x63/0x84 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e14c420d>] _nv001371rm+0x5d/0x27c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e14c43ee>] _nv001371rm+0x23e/0x27c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e155d72e>] _nv005756rm+0xfe/0x10c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e154727a>] _nv006323rm+0x1a/0x20 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b11cc>] _nv005117rm+0x1c4/0x208 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b11bd>] _nv005117rm+0x1b5/0x208 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b0d78>] _nv004912rm+0x34/0x7c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e15b0dab>] _nv004912rm+0x67/0x7c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e144a3ef>] _nv005057rm+0x53/0x5c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e1459a2c>] _nv002443rm+0x58/0x100 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e154badf>] _nv000433rm+0xd3/0xec [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146be8e>] _nv001656rm+0x6e/0x104 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146be85>] _nv001656rm+0x65/0x104 [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146f473>] _nv001627rm+0x6b/0xac [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146c691>] _nv001662rm+0x139/0x41c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146c7b1>] _nv001662rm+0x259/0x41c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e146c7a1>] _nv001662rm+0x249/0x41c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e1694c49>] os_acquire_sema+0x60/0x6c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e1470b92>] rm_init_adapter+0x5e/0x8c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e1470b86>] rm_init_adapter+0x52/0x8c [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<e1691637>] nv_kern_open+0x1ca/0x24f [nvidia]
Dec 15 21:57:05 xxxxxx kernel: [<c0160b68>] chrdev_open+0x83/0x146
Dec 15 21:57:05 xxxxxx kernel: [<c0157a43>] __dentry_open+0xa4/0x1ad
Dec 15 21:57:06 xxxxxx kernel: [<c0157bbc>] filp_open+0x70/0x78
Dec 15 21:57:06 xxxxxx kernel: [<c0157ca0>] get_unused_fd+0xa9/0xcb
Dec 15 21:57:06 xxxxxx kernel: [<c013a440>] audit_getname+0x6b/0xd0
Dec 15 21:57:06 xxxxxx kernel: [<c0157d7b>] do_sys_open+0x31/0xad
Dec 15 21:57:06 xxxxxx kernel: [<c0102ea1>] syscall_call+0x7/0xb
Dec 15 21:57:06 xxxxxx kernel: Code: a4 83 c4 fc 83 c4 f8 53 8b 45 08 50 e8 0c 71 00 00 50 6a 18 8b 95 9c fe ff ff 52 8b 42 18 ff d0 89 c6 83 c4 20 83 c4 f8 6a 00 56 <8b> 86 f4 00 00 00 ff d0 8b 85 94 fe ff ff c1 e8 04 8a 44 28 ec
archangelis is offline   Reply With Quote
Old 12-17-05, 05:18 AM   #139
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-8174 for Linux x86 released

@archangelis: please provide more information to help us reproduce this problem (see http://www.nvnews.net/vbulletin/show....php?t=46678); minimally, please generate and attach an nvidia-bug-report.log file and reproduction steps.
zander is offline   Reply With Quote
Old 12-17-05, 09:57 AM   #140
koos
Registered User
 
Join Date: Aug 2005
Posts: 8
Default Still having no luck w/ 1920x1200 displays w/ 5200FX

The newest driver that works is 7174, newer report a max clock range of 135MHz (see both attached log files) The ML I use is:
Modeline "1920x1200" 154.128 1920 1968 2000 2080 1200 1203 1209 1235 -hsync -vsync
Is there any hope this will be fixed or is the 5200FX such a poor choice that 1280x1024 is all that it can (and thus the 7174 does impossible things)?
Attached Files
File Type: log Xorg.7174.log (29.9 KB, 192 views)
File Type: log Xorg.8174.log (30.4 KB, 197 views)
koos is offline   Reply With Quote

Old 12-17-05, 11:37 AM   #141
PrakashP
gentoo ~x86_64 user
 
PrakashP's Avatar
 
Join Date: Jul 2004
Location: Germania
Posts: 213
Default Re: 1.0-8174 for Linux x86 released

Something currently less important: Is there a known issue between compiling Nvidia glue layer with gcc 4.1? If one tries one gets missing symbols on linking/modprobing. (I could reproduce it.)

See here (page 9 and 10):

http://forums.gentoo.org/viewtopic.p...962930#2962930
PrakashP is offline   Reply With Quote
Old 12-17-05, 11:48 AM   #142
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-8174 for Linux x86 released

@PrakashP: it's possible that gcc 4.1 generates additional warning messages for Linux kernel header files relied upon by conftest.sh's compile tests that check for the presence of certain kernel interface functions.
zander is offline   Reply With Quote
Old 12-17-05, 01:58 PM   #143
hmazuji
Registered User
 
Join Date: Dec 2005
Posts: 15
Default Re: 1.0-8174 for Linux x86 released

Quote:
Originally Posted by netllama
Anyone experiencing problems with 1.0-8174 should please start a new with the following information:
0) nvidia-bug-report.log

no precompiled kernel interface was found to match your kernel... unable to connect ... the installer will need to compile a kernel interface for your kernel. performing cc test with cc=cc. gcc-version-check failed: ./usr/src/nv/conftest.sh: line 19: cc: command not found
could not compile gcc-version-check.c please be sure you have your distributions libc development package installed and that cc is a valid c compile name.
if you know what you are doing and you want to ignore the gcc version check...


1) a detailed description of the problem


no opengl with suse 10.0 x86_64


2) how the problem can be reproduced

spend $450 on a 7800gtx



This will ensure that your issue can receive the attention it needs, both from NVIDIA, and the other readers on this forum who may not be looking at this thread.

Thanks for your cooperation,
Lonni
read between the lines
hmazuji is offline   Reply With Quote
Old 12-17-05, 02:11 PM   #144
tux_gt
Registered User
 
Join Date: Nov 2004
Posts: 16
Default Re: 1.0-8174 for Linux x86 released

Quote:
Originally Posted by hmazuji
read between the lines
Did not followed the complete thread, but if you got this error message, you should at least install gcc, kernel-source and glibc-devel.
tux_gt 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 05:37 PM.


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