View previous topic :: View next topic |
Author |
Message |
r0nster n00b
Joined: 31 May 2002 Posts: 13 Location: Searcy, AR
|
Posted: Sun Apr 27, 2003 9:32 pm Post subject: New Nvidia Drivers 1.0-4363 released. |
|
|
Supposedly fixes bugs left over from the previous 4.0-x versions. Hopefully an ebuild will pop up soon |
|
Back to top |
|
|
idl Retired Dev
Joined: 24 Dec 2002 Posts: 1728 Location: Nottingham, UK
|
Posted: Sun Apr 27, 2003 9:36 pm Post subject: |
|
|
cool, very speedy work by nvidia Perhaps it will fix my problems with phoenix. _________________ a.k.a port001
Found a bug? Please report it: Gentoo Bugzilla |
|
Back to top |
|
|
dice Guru
Joined: 21 Apr 2002 Posts: 577
|
Posted: Sun Apr 27, 2003 9:44 pm Post subject: |
|
|
Code: | * media-video/nvidia-glx
Latest version available: 1.0.4363
Latest version installed: 1.0.4349
Size of downloaded files: 4,099 kB
Homepage: http://www.nvidia.com/
Description: XFree86 GLX libraries for the NVIDIA's X driver
* media-video/nvidia-kernel
Latest version available: 1.0.4363
Latest version installed: 1.0.4349-r2
Size of downloaded files: 645 kB
Homepage: http://www.nvidia.com/
Description: Linux kernel module for the NVIDIA's X driver |
Runing emerge -uD world right now |
|
Back to top |
|
|
r0nster n00b
Joined: 31 May 2002 Posts: 13 Location: Searcy, AR
|
Posted: Sun Apr 27, 2003 9:44 pm Post subject: |
|
|
So far, the 1.0-4349 (or whatever they were) seemed to work for me rather well. Others seem to have astonishingly long startup times, display corruption, etc. So I guess I've been lucky because I have experienced nothing of the sort yet, knock on wood!
If anything, DVD playback has improved a small bit compared to the previous driver I was running (the 3.x series). FYI, I'm also running XFree 4.3.0 -r2. |
|
Back to top |
|
|
stevos22 Tux's lil' helper
Joined: 22 Feb 2003 Posts: 102
|
Posted: Mon Apr 28, 2003 2:06 am Post subject: |
|
|
Great stuff, Linux geeks welcome monthly driver updates from NVIDIA ;_0 |
|
Back to top |
|
|
yem n00b
Joined: 05 Nov 2002 Posts: 63 Location: Aotearoa
|
Posted: Mon Apr 28, 2003 9:09 am Post subject: |
|
|
It'd be nice if the nvidia-kernel module used the current kernel (as determined by uname -r) instead of whatever old bunger is lurking in /usr/src/linux. I'm thinking of filing this as a bug.
Linus Torvalds wrote: | I would suggest that people who compile new kernels should:
- not have a single symbolic link in sight (except the one that the
kernel build itself sets up, namely the "linux/include/asm" symlink
that is only used for the internal kernel compile itself)
And yes, this is what I do. My /usr/src/linux still has the old 2.2.13
header files, even though I haven't run a 2.2.13 kernel in a _loong_
time. But those headers were what glibc was compiled against, so those
headers are what matches the library object files.
And this is actually what has been the suggested environment for at
least the last five years. I don't know why the symlink business keeps
on living on, like a bad zombie. Pretty much every distribution still
has that broken symlink, and people still remember that the linux
sources should go into "/usr/src/linux" even though that hasn't been
true in a _loong_ time. |
Here's an updated ebuild for nvidia-kernel-0.1.4363 that does NOT depend upon the /usr/src/linux symlink: http://icculus.org/~yem/nvidia-kernel-1.0.4363.ebuild
Thoughts? |
|
Back to top |
|
|
RockHound Tux's lil' helper
Joined: 11 Nov 2002 Posts: 112 Location: Hamburg, Germany
|
Posted: Mon Apr 28, 2003 11:35 am Post subject: |
|
|
@yem: I think that you are right on track. Go ahead and file a bug report to nVidia ... i won't hurt. And you are always sure to get your current kernel compiled in.
Thanx for your headsup.
Greetz,
Martin |
|
Back to top |
|
|
delta407 Bodhisattva
Joined: 23 Apr 2002 Posts: 2876 Location: Chicago, IL
|
Posted: Mon Apr 28, 2003 5:51 pm Post subject: |
|
|
Gentoo, as a distribution, assumes that the running kernel is accessible in /usr/src/linux. I agree that `uname` is probably a better solution, but Gentoo expects that symlink to be accurate. _________________ I don't believe in witty sigs. |
|
Back to top |
|
|
maw Apprentice
Joined: 25 Aug 2002 Posts: 175 Location: Nottingham, UK
|
Posted: Mon Apr 28, 2003 7:14 pm Post subject: |
|
|
I'd suggest changing the distro then... that would be especially useful for people who run 2.5.x and 2.4.x... _________________ Your Gentoo woll sle me sodenly!
I may the beaute of it not sustene
(to misquote Chaucer) |
|
Back to top |
|
|
yem n00b
Joined: 05 Nov 2002 Posts: 63 Location: Aotearoa
|
Posted: Tue Apr 29, 2003 8:51 am Post subject: |
|
|
delta407 wrote: | Gentoo, as a distribution, assumes that the running kernel is accessible in /usr/src/linux. I agree that `uname` is probably a better solution, but Gentoo expects that symlink to be accurate. |
Hi delta. Can you be a little more specific? A quick grep of my portage tree shows 189 files containing "/usr/src/linux". If we discard all ebuilds except the highest version in each directory, it comes down to 64 files (including Changelogs and READMEs).
Is it worth changing these files?
I know /usr/src/linux is the traditional home, but since linux-2.4.20 I would call that deprecated. It would be nice to see it phased out, which could be accomplished by using a better method in ebuilds going forward.
Has this been hashed out on gentoo-dev yet? |
|
Back to top |
|
|
mb4guns Guru
Joined: 04 Dec 2002 Posts: 300 Location: Netherlands
|
Posted: Fri May 02, 2003 7:43 am Post subject: |
|
|
nvidia owns _________________ sys0: Athlon64, Corsair TWINX DDR400 (1024mb), GeForce FX5600 256mb, 2x SATA MAxtor 120gig, Plextor 708a, Zalman cooling, Zalman powered, gnomed
sys1: Dell inspiron 4100 PentiumIII-mobile@1000 512mb ATI Radeon mobility m6 30gig, gnomed |
|
Back to top |
|
|
minam n00b
Joined: 02 May 2003 Posts: 2 Location: Provo, UT
|
Posted: Sun May 04, 2003 2:14 am Post subject: How to emerge 4363? |
|
|
Okay--I'm a major newbie to Gentoo (though not to linux). I've searched and searched and can't find info on this question: how can I emerge the latest NVidia drivers (4363)? Posts I've read seem to imply that there is an ebuild for it floating around somewhere, but I can't find it, and the "online package database" only lists the 4349 driver.
I can't get X to start at all with the 4349... it freezes on start up. I've followed the advice of others with similar problems (posted to these forums), to no avail, and the only thing I haven't tried yet is using the latest driver. Help me, please!
Thanks,
Jamis |
|
Back to top |
|
|
floam Veteran
Joined: 27 Oct 2002 Posts: 1067 Location: Vancouver, WA USA
|
Posted: Sun May 04, 2003 2:53 am Post subject: |
|
|
minam..... its in portage, so just emerge nvidia-kernel after an emerge sync to get the latest stuff from portage (assming you're letting portage give you testing/unstable packages of course.) |
|
Back to top |
|
|
minam n00b
Joined: 02 May 2003 Posts: 2 Location: Provo, UT
|
Posted: Sun May 04, 2003 3:20 am Post subject: |
|
|
floam--thanks for the pointer. I didn't realize the 4363 drivers were considered testing/unstable. I'll do some reading in that direction and set up portage to look there. |
|
Back to top |
|
|
Safrax Guru
Joined: 23 Apr 2002 Posts: 422
|
Posted: Sun May 04, 2003 4:16 am Post subject: |
|
|
Nvidia mucks up yet another driver release. 2D is still as slow as the 41's and the other 43's. I've had enough random lockups due to these drivers to really make me mad. I wish I could use the 31xx series with a 2.5.68-mm* kernel. I would be a really happy person. |
|
Back to top |
|
|
puddpunk l33t
Joined: 20 Jul 2002 Posts: 681 Location: New Zealand
|
Posted: Sun May 04, 2003 5:40 am Post subject: |
|
|
NVIDIA didn't muck it up. They work fine here. Maybe you mucked up?
I don't mean to be dense, but just because something doesn't work for you, it doesn't mean that the cause is a big failure. |
|
Back to top |
|
|
Safrax Guru
Joined: 23 Apr 2002 Posts: 422
|
Posted: Sun May 04, 2003 8:47 am Post subject: |
|
|
If anything its Nvidia and the decision to drop XAA and implement their own. It doesn't work half as good as the 31's with the XAA drivers. Whenever there is something updating 2D wise, like a konsole scroll, the text tears like mad. With the 31's I never had this problem, everything was as smooth as silk. And as far as user error. Doubt it. I've encountered this problem on 3 machines at work as well as all my home systems. It's a nvidia driver problem. |
|
Back to top |
|
|
Cossins Veteran
Joined: 21 Mar 2003 Posts: 1136 Location: Copenhagen, Denmark
|
Posted: Sun May 04, 2003 12:31 pm Post subject: |
|
|
Well, it certainly doesn't occur to everyone - I've never had problems with the nvidia drivers all the way from tnt2 through geforce4.
If so many people have problems, why doesn't anyone sit down and look at the source code (it is open-source) to fix whatever problems you may have?
- Simon |
|
Back to top |
|
|
aerogems n00b
Joined: 19 Feb 2003 Posts: 30
|
Posted: Sun May 04, 2003 12:46 pm Post subject: |
|
|
puddpunk wrote: | NVIDIA didn't muck it up. They work fine here. Maybe you mucked up?
I don't mean to be dense, but just because something doesn't work for you, it doesn't mean that the cause is a big failure. |
All 4xxx series drivers are pure crap for me so far in my GF2 TI. The 2D performance is like using an unaccelerated XServer.... It's just painful, and it plays hell with the schedulers in the 2.5.68mm* sources.
I also emailed the guy who's been making the 2.5 patches, and he suggested commenting out all references to "devfs_unload" in nv.c for the 3123 drivers to make them work with 2.5.68mm2 and mm3. He said it should work without problems so long as you don't try and remove the module. I haven't had occation to test it myself yet, but I do so wish someone would update the 3123 drivers as well. They may lock up often, but at least while they were working I could use my system with little pain. And I'm in search of a nice Radeon 8500 now so that I'll have the option of XFree's native DRI drivers or ATIs. I've had it with my only choices being to not be able to upgrade my kernel past 2.5.68mm1, or use drivers that make it an absolute pain to use my system. Screw Nnidia. |
|
Back to top |
|
|
fragbert Tux's lil' helper
Joined: 18 Apr 2003 Posts: 75 Location: Dallas, TX
|
Posted: Sun May 04, 2003 7:14 pm Post subject: |
|
|
puddpunk wrote: | NVIDIA didn't muck it up. They work fine here. Maybe you mucked up?
I don't mean to be dense, but just because something doesn't work for you, it doesn't mean that the cause is a big failure. |
He's not the only one having constant lockup problems with the 4xxx series. I'm sure it's not beyond your "dense" mental capacity to understand that it is certainly possible for someone to have a problem, even with an identical configuration and similar hardware, that someone else does not have. I'm also stuck on the 3123 drivers, because anything more recent constantly hard-locks X. Right now I believe the lockup may be caused by the Linux AGPGART's interacting poorly with the nvidia kernel module... but there's really no telling. Certainly there's nothing in the logfiles to indicate what the problem is, and I'm not knowledgeable enough to gdb the frozen X process. I will post if I ever find a fix.
Regards,
Michael |
|
Back to top |
|
|
drexelslacker n00b
Joined: 01 May 2003 Posts: 7
|
Posted: Sun May 04, 2003 8:29 pm Post subject: Problems with AGP? |
|
|
The only problems I've experienced with nVidia drivers is when trying to use AGP. I have a GeForce3 and run the current gentoo stable set. If I turn on AGP, I'll get random lockups within 10 minutes of starting X. When I turn it off, it's rock solid stable. To all the people having big problems, have you tried not using AGP? For curiosity's sake, it would be interesting to see if that's what the general problem is.
DrexelSlacker |
|
Back to top |
|
|
puddpunk l33t
Joined: 20 Jul 2002 Posts: 681 Location: New Zealand
|
Posted: Mon May 05, 2003 12:37 am Post subject: |
|
|
Well, sorry to be a wet blanket on this nvidia flaming, but the 4xxx drivers work great for me. The 2D is fast and accurate, and the 3D is great. I think it was a good idea for NVIDIA to drop the XAA, as (IIRC) they found themselves very constrained by it, so they are writing their own. And of course, there are always the people who think that new code will work flawlessly on everybodies computer.
File a bug (on the nvidia forums, or whatever), be patient and stick with the 3xxx if it suits. It could be heaps worse, you could be trying to deal with ATI's drivers (trust me, you don't know how lucky you are with NVIDIA until you try and deal with ATI's drivers).
Oh, and by the way, I'm running a GeForce 2 MX on a Duron 1000 with kernel 2.5.68-mm1 and I experiance no problems.
EDIT: Typo |
|
Back to top |
|
|
BMan n00b
Joined: 03 Apr 2003 Posts: 28 Location: London, UK
|
Posted: Sun May 11, 2003 9:26 pm Post subject: |
|
|
Fragbert, I had the random x lockups with the 4xxx drivers and found the problem was with the "render accel" option.
Putting: Option "RenderAccel" "False" in XF86config fixed the problem for me and now it's totally stable.
Hope that helps! |
|
Back to top |
|
|
wrex n00b
Joined: 01 May 2003 Posts: 26 Location: San Jose, CA
|
Posted: Sun May 11, 2003 10:04 pm Post subject: |
|
|
BMan wrote: | Putting: Option "RenderAccel" "False" in XF86config fixed the problem for me and now it's totally stable. |
Hmm... /usr/doc/nvidia-glx-1.0.4364/README.gz says that the default for this RenderAccel is disabled. I've just tried explicitly putting in an explict "False", though, as you've suggested. I'll just have to wait and see if this makes things better.
I've been getting intermittent lockups as well with a PCI GeForce4 FX card (twinhead). I've tried among other things putting in an explicit 'Option "NvAGP" "0"' into my XF86Config, but I'm still getting lockups.
It was locking up pretty regularly (interestingly about 4 out of 5 times while xscreensaver was running pyro). I'll know within a day if RenderAcell False fixes it.
I'll leave xscreensaver running all night and report back tomorrow if setting RenderAccel fixed the problem for me as well. |
|
Back to top |
|
|
wrex n00b
Joined: 01 May 2003 Posts: 26 Location: San Jose, CA
|
Posted: Mon May 12, 2003 5:14 am Post subject: no joy |
|
|
Just got back from Mom's day dinner and X was locked up (once again with pyro on the screen).
I've just re-emerged/compiled gentoo-sources-2.4.20-r5, nvidia-kernel and nvidia-glx. I'm specifying noapic in grub, turned off AGP and RenderAccel in XF86Config. I'm running out of things to try.
If it was just locking up while the screensaver was running I could live with it, but periodically I get a lockup while actively using the system -- that's far more than annoying.
Sigh. |
|
Back to top |
|
|
|