| View previous topic :: View next topic |
| Author |
Message |
leej
Apprentice
Joined: 18 May 2002
Posts: 280
|
 Posted: Mon Jun 17, 2002 11:56 pm Post subject: NVidia performance between driver versions |
 |
|
After monitoring the NVidia & Linux newsgroups and the NVidia Linux Discussion Area it's become clear that some users are experiencing difficulties with the latest drivers (1.0-2960). From what I've read - most complaints appear to be coming from owners of VIA chipsets with an Athlon TB or Duron processor.
Most notably (and what I've experienced) - occasional lockups and the framerate is 700-1000fps slower (direct rendering/glx/etc all working correctly). Going back to 1.0-2880 completely eliminates the problem.
Anyway, I've noticed the 2880 glx ebuild has just been masked. Is there any way to keep these old NVidia (2880) drivers available in the Portage tree - just for those of us who require them to keep our 3d rendering fast & our systems stable? At least until NVidia release another set of drivers that will hopefully solve the problem. |
|
| Back to top |
|
 |
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Mon Jun 17, 2002 11:57 pm Post subject: |
|
|
Yeah, copy the ebuild file somewhere and edit your package.mask. Simple enough, just don't do an emerge rsync --clean.  |
|
| Back to top |
|
|
leej
Apprentice
Joined: 18 May 2002
Posts: 280
|
| Posted: Tue Jun 18, 2002 12:02 am Post subject: |
|
|
| delta407 wrote: | | Yeah, copy the ebuild file somewhere and edit your package.mask. Simple enough, just don't do an emerge rsync --clean. |
Is it as simple as that to preserve it? I've been meaning to go through the Developer HOWTO (to learn more about Ebuilds) for about six weeks but just seem to find excuses to be doing something else every time.  |
|
| Back to top |
|
|
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Tue Jun 18, 2002 12:09 am Post subject: |
|
|
Well, yeah, it is. Or you could change the permissions on it to 444, though I don't know if emerge rsync --clean will reset them. Anyway, to backup an ebuild, you should be able to just copy it away and copy it back as necessary, making sure it's unmasked before doing any emerge -u world or other such behavior that may "upgrade" you to the later version.
Heck, you could write an emerge rsync wrapper that copies back the old ebuild and changes package.mask from masking 2880 to masking 2960, solving two problems at once.  |
|
| Back to top |
|
|
leej
Apprentice
Joined: 18 May 2002
Posts: 280
|
| Posted: Tue Jun 18, 2002 12:15 am Post subject: |
|
|
Well thanks for the info! I'm going to back it up right now and definitely read that HOWTO tomorrow night.
...famous last words. |
|
| Back to top |
|
|
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Tue Jun 18, 2002 12:21 am Post subject: |
|
|
Yeah, I should probably read it too...
Oh, but it's so much fun to gather these kinds of things from staring at miles and miles of Python and dozens of ebuild files!
Oh well... RTFM.  |
|
| Back to top |
|
|
|
Kernel & Hardware
