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

Newegg Daily Deals

Reply
 
Thread Tools
Old 07-01-04, 08:50 PM   #61
zoot
Registered User
 
Join Date: Jul 2004
Posts: 3
Angry Re: 1.0-6106 for X86-32 thread

Quote:
Originally Posted by AndyI
Just as I think nVidia have sorted out the Linux drivers with regard to TV-Out (been dodgy since 4663), they then break 1024x768 for the TV-Out:

(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(WW) NVIDIA(0): Not using mode "1024x768" (not a valid TV mode)
(**) NVIDIA(0): Validated modes for display device TV-0:
(**) NVIDIA(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(**) NVIDIA(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) NVIDIA(0): Virtual screen size determined to be 800 x 600


This is on an unaltered XF86Cfg-4. The same file has been running since 4363!!
I got the same problem, WE WANT 1024X768 TVOUT!
zoot is offline   Reply With Quote
Old 07-01-04, 10:26 PM   #62
kauschovar
Registered User
 
Join Date: Jun 2004
Posts: 8
Default Re: 1.0-6106 for X86-32 thread

Thanks nVidia! I've been waiting for this day for a long time. The performance on my 6800 Ultra is phenominal. UT2004 is playable at max details at 1600x1200 -- not even a hiccup. I think I need to put in a new sound card though. The built-in card seems to be holding me back in games like America's Army. (Edit: actually, after playing online the performance isn't bad at all. Maybe even faster than on Windows. It just seemed a bit weak at the shooting range.)

I did notice one problem though. Sometimes the text in CGA mode is messed up. After messing with my xorg.conf, my prompt was dim and after starting kdm, all colored text would not be drawn period. Or it may have been all text with the intensity bit turned on. Anyways, it only happens in true CGA mode as far as I can tell (not konsole, xterm, etc), so it's hardly a problem. And I haven't noticed it since then either. It only occured while installing/configuring the driver.

Oh yeah, and nvidia-settings reports my core is at 71 degrees Celsius. At what temperature should I begin to worry?

Quote:
kauschovar $ glxgears
55061 frames in 5.0 seconds = 11012.200 FPS
67596 frames in 5.0 seconds = 13519.200 FPS
67618 frames in 5.0 seconds = 13523.600 FPS
67606 frames in 5.0 seconds = 13521.200 FPS
67600 frames in 5.0 seconds = 13520.000 FPS
67681 frames in 5.0 seconds = 13536.200 FPS
67851 frames in 5.0 seconds = 13570.200 FPS
67752 frames in 5.0 seconds = 13550.400 FPS
67763 frames in 5.0 seconds = 13552.600 FPS
67677 frames in 5.0 seconds = 13535.400 FPS
67749 frames in 5.0 seconds = 13549.800 FPS
blackbard: If you haven't got your's working yet, try 'emerge unmerge nvidia-kernel nvidia-glx' and then download and run the driver from nVidia's site: http://www.nvidia.com/object/linux_d..._1.0-6106.html. I got the same error messages and that's what fixed it for me.

Last edited by kauschovar; 07-01-04 at 11:12 PM.
kauschovar is offline   Reply With Quote
Old 07-01-04, 10:35 PM   #63
kauschovar
Registered User
 
Join Date: Jun 2004
Posts: 8
Default Re: 1.0-6106 for X86-32 thread

Wow. This has got to be a first. The Linux drivers came out before the Windows drivers: http://www.nvidia.com/object/winxp_2k_56.72. I guess the Windows drivers are still going through WHQL tetsting.
kauschovar is offline   Reply With Quote
Old 07-01-04, 11:21 PM   #64
sleepylight
Registered User
 
Join Date: Jul 2004
Posts: 14
Question Re: 1.0-6106 for X86-32 thread

Hey all!

It's great to see NVIDIA drivers with 4k stack support. I'm sure all the 2.6.X kernel users are all plenty happy!

I'm running the 2.6.7 kernel I just built tonight. I also have the 1.0-6106 driver package. When I run the installer it comes back with a fairly general message saying that it isn't happy with my source tree. I don't really know what it's looking for, but it seems unhappy none the less.

So, I checked the usual suspects. uname -r reports 2.6.7, and that's right. /usr/src/linux points to /usr/src/linux-2.6.7, so that's cool too. Finally, /lib/modules/2.6.7/build points to /usr/src/linux-2.6.7. Honestly, I don't see what's wrong with this picture. I tried running the installer in advanced mode and the dirs it wanted to find the source in and install it's modules all look just fine.

Without any other ideas I tried giving your makefile a shot. Well, that didn't pan out either. make returned the error message that the installer's been showing me along with the complaint that it can't figure out my kernel version. What's up?
sleepylight is offline   Reply With Quote
Old 07-02-04, 12:19 AM   #65
ghostwalker
Registered User
 
Join Date: Sep 2003
Location: Tacoma, WA
Posts: 76
Default Re: 1.0-6106 for X86-32 thread

I am running 2.6.7 with the ck4 patch, the schedule cfq. Man what a difference with 4K stacks and cfq IO it is awsome. The nvidia driver is a little on the large size, 4817716, lsmod. I only get 5300~ fps w/glxgears. Still for my use that is good. Gforce4 MX 440.

Walt
ghostwalker is offline   Reply With Quote
Old 07-02-04, 02:27 AM   #66
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-6106 for X86-32 thread

@qasr: please submit a detailed bug report to linux-bugs@nvidia.com (w/ nvidia-bug-report.log).
zander is offline   Reply With Quote
Old 07-02-04, 02:31 AM   #67
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-6106 for X86-32 thread

@kauschovar: the gauge on the thermal page graphically displays the current core (i.e. on-die, not heatsink) operating temperature with respect to the slowdown threshold temperature; 70C is quite cool, still.
zander is offline   Reply With Quote
Old 07-02-04, 02:32 AM   #68
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-6106 for X86-32 thread

@sleepylight: can you post the nvidia-installer.log file for this configuration?
zander is offline   Reply With Quote

Old 07-02-04, 03:05 AM   #69
kauschovar
Registered User
 
Join Date: Jun 2004
Posts: 8
Default Re: 1.0-6106 for X86-32 thread

Quote:
Originally Posted by zander
70C is quite cool, still.
That's good to hear. Thanks for the info.
kauschovar is offline   Reply With Quote
Old 07-02-04, 06:55 AM   #70
catimimi
Registered User
 
Join Date: Jan 2004
Posts: 52
Default Re: 1.0-6106 for X86-32 thread

Hi all,

It seems that one more thing is regressive in this excellent release.

I'm no longer able to force AGP4X with my via chipset.

I tried :
options nvidia NVreg_EnableVia4x = 1
in modprobe.conf, this works well with release 4620

I tried to force this value in os-registry.c and to recompile

I tried to force AGP4X as indicated in the doc, nothing happens.

Is this a bug ?

Thanks for reply.

Michel.
catimimi is offline   Reply With Quote
Old 07-02-04, 07:12 AM   #71
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 1.0-6106 for X86-32 thread

@catimimi: this is a known bug that will be resolved with the next driver release. Unfortunately, there is no workaround for this, at the moment.
zander is offline   Reply With Quote
Old 07-02-04, 07:43 AM   #72
mrblobby
Registered User
 
Join Date: Jan 2004
Location: New Zealand
Posts: 7
Default Re: 1.0-6106 for X86-32 thread

Hi there,

Just installed 6106 on my system (AthlonXP 2500+, FX5600, Mandrake 10.0 Official kernel 2.6.3-mdk)...installation ran nicely, tested a few apps and they ran fine, I ran ut2003 which runs noteably faster, but trying to exit ut2003 X gets upset and restarts..

The XFree logs in /var/log/... show no errors, but dmesg shows an error thus...

atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.

I previously ran nvidia 5336, and had no issues...is this something anyone else has seen?

Kind regards,

Chris Wilkinson, New Zealand.
mrblobby 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 07:47 PM.


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