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

Newegg Daily Deals

Reply
 
Thread Tools
Old 03-31-03, 04:32 PM   #37
zeograd
Registered User
 
Join Date: Mar 2003
Location: France
Posts: 1
Send a message via ICQ to zeograd
Default Twinmode issues fixed and installer feedback

Hi,
the latest 4349 installer didn't work at once on a woody/sarge, the kernel module wasn't loaded. --extract + a manual make install works flawlessly.
While improving 3D accel by around 15-20% on my machine (Athlon 1900+, GeForce2MX, AGP4, ...) it also fixed the crash problem I experimented after having upgraded to XFree 4.2.x
Good work, keep going
zeograd is offline   Reply With Quote
Old 03-31-03, 04:38 PM   #38
LordMorgul
Electrical Engineer
 
LordMorgul's Avatar
 
Join Date: Dec 2002
Location: San Luis Obispo, CA
Posts: 872
Default

Quote:
Originally posted by bwkaz
OK, cool. Let the record show that I want tarballs in the future.

Or at least an equivalent, like the ./NVIDIA-Linux-x86-1.0-4349.run --extract-only option that there is.

Thanks again.
I second the vote, I would like to see the option of tarballs packed in the installer forever, this allows for installation on a much wider number of highly 'tweaked' or modified linuxes that might not otherwise respond to the installer.
LordMorgul is offline   Reply With Quote
Old 03-31-03, 04:43 PM   #39
the_badger
Registered User
 
Join Date: Mar 2003
Posts: 2
Default Re: 1024 works but no native 1400

[quote]Originally posted by nosrema
[b]A Panel bloom, that is exactly what is does.

Any thoughts? Here are some files that might be of interest.

My laptop:
Dell Inspiron 8100
32MB Geforce2Go 1400x1050 XGA or SVGA screen I can't remember.

I'm having exactly the same problem on my Inspiron 8000 with the same display and graphics card. For now, I have to use the 1.0-3123 drivers as anything newer causes the problems described by nosrema. The funny thing is that I use the same XF86config files with the newer versions as with the old ones.
the_badger is offline   Reply With Quote
Old 03-31-03, 04:45 PM   #40
Soulburner
Registered User
 
Join Date: Mar 2003
Posts: 9
Default

Sorry to interject this question into this thread, but it's halfway on topic. I'm just curious if there are any plans to bring the FreeBSD drivers up to date with the other linux drivers?
Soulburner is offline   Reply With Quote
Old 03-31-03, 04:51 PM   #41
Andy Mecham
l33t master
 
Join Date: Jul 2002
Location: Santa Clara, CA
Posts: 1,163
Default

Quote:
I second the vote, I would like to see the option of tarballs packed in the installer forever, this allows for installation on a much wider number of highly 'tweaked' or modified linuxes that might not otherwise respond to the installer.
I think there's some misunderstandings about the installer. If the installer doesn't have a precompiled bit for your kernel, it will build one for you - it's the same thing as using the source tarball, except it's all in one nice, neat package. The installer should work on ANY installation or distribution, provided you have a shell, gzip, and a linker.

--andy
__________________
Andy Mecham
NVIDIA Corporation
Andy Mecham is offline   Reply With Quote
Old 03-31-03, 04:52 PM   #42
jobeus
Registered User
 
Join Date: Mar 2003
Posts: 15
Send a message via ICQ to jobeus
Default

There's been a lot of talk about the tarballs missing on here, and I'd just like to point out that they aren't really 'missing'...

ftp://download.nvidia.com/XFree86/Li....0-4349.tar.gz
ftp://download.nvidia.com/XFree86/Li....0-4349.tar.gz
jobeus is offline   Reply With Quote
Old 03-31-03, 05:07 PM   #43
bwkaz
Registered User
 
Join Date: Sep 2002
Posts: 2,262
Default

Quote:
Originally posted by Andy Mecham
it will build one for you
That's all I need to hear.

Quote:
Originally posted by jobeus
There's been a lot of talk about the tarballs missing on here, and I'd just like to point out that they aren't really 'missing'...
Well no, not for 4349. But the README is implying that they will not be provided for later versions, and I wanted to make sure (now, before the new versions got released) that they would be buildable. I would consider that to be the case now.
__________________
Registered Linux User #219692
bwkaz is offline   Reply With Quote
Old 03-31-03, 05:10 PM   #44
dagger
Registered User
 
Join Date: Mar 2003
Posts: 6
Default

Ive got small problem with new drivers

[root@veto NVIDIA_kernel-1.0-4349]# make
echo \#define NV_COMPILER \"`cc -v 2>&1 | tail -1`\" > nv_compiler.h
cc -c -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wpointer-arith -Wcast-qual -Wno-multichar -O -MD -D__KERNEL__ -DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_SOURCE -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=4349 -DNV_UNIX -DNV_LINUX -DNV_INT64_OK -DNVCPU_X86 -DREMAP_PAGE_RANGE_4 -I. -I/lib/modules/2.4.19/build/include -Wno-cast-qual nv.c
In file included from /lib/modules/2.4.19/build/include/linux/vmalloc.h:8,
from nv-linux.h:72,
from nv.c:14:
/lib/modules/2.4.19/build/include/linux/highmem.h: In function `bh_kmap':
/lib/modules/2.4.19/build/include/linux/highmem.h:21: warning: pointer of type `void *' used in arithmetic
nv.c: In function `nvos_proc_remove_all':
nv.c:624: dereferencing pointer to incomplete type
nv.c:625: dereferencing pointer to incomplete type
nv.c:626: dereferencing pointer to incomplete type
nv.c:627: warning: implicit declaration of function `remove_proc_entry'
nv.c:627: dereferencing pointer to incomplete type
nv.c:627: dereferencing pointer to incomplete type
make: *** [nv.o] Error 1
[root@veto NVIDIA_kernel-1.0-4349]#

What can I do?
dagger is offline   Reply With Quote

Old 03-31-03, 05:14 PM   #45
johnod
Registered User
 
Join Date: Mar 2003
Location: Conshohocken, PA USA
Posts: 4
Unhappy VERY slow start

I upgraded to the 4349 drivers. I see the same behavior as 4191 which is why I keep 3123 around. Sheesh :-)

Anyway, the problem is it takes 2 minutes before I see the NVidia logo and the system is totally unresponsive to network requests or anything! If I am remotely logged when those drivers fire up, I have a dead system for almost 2 minutes.

After 1:20 i see a flicker on my otherwise black screen. After just over 2 minutes I finally see the logo and I get my xdm login.

I thought the 3123 drivers were slow. They take 10 to 20 seconds before I see the logo.

My ATI-All-in-Blunder and my Voodoo3 take 3 seconds to get my xdm login.

WAAAAAAAAAA!
What do you need from me?
johnod is offline   Reply With Quote
Old 03-31-03, 05:17 PM   #46
ErroR|51
Registered User
 
Join Date: Mar 2003
Posts: 3
Default

Quote:
Originally posted by bwkaz
My distro will not work with anything other than source...
Would be the first time.... what distro would that be? I'm quite curious... lol.


Anyway... running Slackware 9 here and never experienced any problems whatsoever with the precedent drivers... going to install this new release asap tho.

Could anyone from the NVidia staff summarize the updates / implementations on this new version ?

Cheers,

ErroR|51

Last edited by ErroR|51; 03-31-03 at 05:21 PM.
ErroR|51 is offline   Reply With Quote
Old 03-31-03, 05:19 PM   #47
Andy Mecham
l33t master
 
Join Date: Jul 2002
Location: Santa Clara, CA
Posts: 1,163
Default

johnod:

There's a new setting that might help you. From the README:

Option "IgnoreDisplayDevices" "string"
This option tells the NVIDIA kernel module to completely
ignore the indicated classes of display devices when
checking what display devices are connected. You may
specify a comma-separated list containing any of "CRT",
"DFP", and "TV".

For example:

Option "IgnoreDisplayDevices" "DFP, TV"

will cause the NVIDIA driver to not attempt to detect
if any flatpanels or TVs are connected.

This option is not normally necessary; however, some video
BIOSes contain incorrect information about what display
devices may be connected, or what i2c port should be
used for detection. These errors can cause long delays
in starting X. If you are experiencing such delays, you
may be able to avoid this by telling the NVIDIA driver to
ignore display devices which you know are not connected.

NOTE: anything attached to a 15 pin VGA connector is
regarded by the driver as a CRT. "DFP" should only be
used to refer to flatpanels connected via a DVI port.

Can you try this?

--andy
__________________
Andy Mecham
NVIDIA Corporation
Andy Mecham is offline   Reply With Quote
Old 03-31-03, 05:32 PM   #48
bwkaz
Registered User
 
Join Date: Sep 2002
Posts: 2,262
Default

Quote:
Originally posted by ErroR|51
Would be the first time.... what distro would that be? I'm quite curious... lol.
Linux From Scratch, with no package management system installed. It also has an extremely patched kernel (an assortment of various patches I've found over the past few months), so I highly doubt that anyone has built a binary module that will work with the kernel.
__________________
Registered Linux User #219692
bwkaz 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


Similar Threads
Thread Thread Starter Forum Replies Last Post
Day of Defeat: Source and Half-Life 2: Deathmatch Updates Released News Archived News Items 0 06-11-12 09:50 PM
CUVILib v1.2 released News Archived News Items 0 05-17-12 07:40 AM
295.49 (long-lived branch release) for Linux x86/x86_64 released AaronP NVIDIA Linux 0 05-03-12 10:42 AM
SOF2 1.02 Patch Released! PsychoSy Gaming Central 5 10-17-02 05:08 AM
nvidia drivers in a motherboard with AGP 1.0 (motherboard MVP3+) knocker NVIDIA Linux 1 08-19-02 01:57 AM

All times are GMT -5. The time now is 01:43 AM.


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