FYI,
I've read quite a few negative comments about the latest nvidia drivers,
but I must say I have had the opposite experience.
On my labrat box, I'm running a newly installed latest gentoop 2004
2.6.2 system with ~x86 everything and glibc with nptl activated, so the
5336 level nvidia drivers we
On Fri, 6 Feb 2004, Collins Richey wrote:
> FYI,
>
> I've read quite a few negative comments about the latest nvidia drivers,
> but I must say I have had the opposite experience.
Well the latest drivers actually make games like NWN run faster than ever.
A great improvement from the old drivers
Collins Richey wrote:
FYI,
I've read quite a few negative comments about the latest nvidia drivers,
but I must say I have had the opposite experience.
On my labrat box, I'm running a newly installed latest gentoop 2004
2.6.2 system with ~x86 everything and glibc with nptl activated, so the
5336 l
On Fri, 6 Feb 2004, Arne Vogel wrote:
> So I would recommend saving all your work (and closing the mail
> application, especially if it is configured
> to fetch e-mails every x minutes) before starting a 3D game. The nvidia
> driver 5336 or kernel 2.6 *may* freeze the PC.
BTW do you have ACPI e
Hi,
On Friday 06 February 2004 15:58, Arne Vogel wrote:
> The first problem was that KDE would refuse to start, complaining about
> a missing symbol
> _nv22 in /usr/lib/libGLcore.so.1 (which pointed to the new version
> of that NVIDIA library).
> GNOME would work fine. I could resolve this b
On Friday 06 February 2004 09:56 am, Grendel wrote:
> On Fri, 6 Feb 2004, Collins Richey wrote:
> > FYI,
> >
> > I've read quite a few negative comments about the latest nvidia
> > drivers, but I must say I have had the opposite experience.
>
> Well the latest drivers actually make games like NWN r
On Fri, 6 Feb 2004 16:37:01 -0500
Ernie Schroder <[EMAIL PROTECTED]> wrote:
> I have the same board and graphics card but I can't get the 5336
>
> nvidia drivers to load upI have nvidia-agp and agpgart loaded but
> "modprobe nvidia" returns:
>
> I do have: /lib/modules/2.6.1-gentoo/
On Friday 06 February 2004 05:03 pm, Ian Truelsen wrote:
> On Fri, 6 Feb 2004 16:37:01 -0500
>
> Ernie Schroder <[EMAIL PROTECTED]> wrote:
> > I have the same board and graphics card but I can't get the 5336
> >
> > nvidia drivers to load upI have nvidia-agp and agpgart loaded but
> > "modprobe
Hemmann, Volker Armin wrote:
Hi,
On Friday 06 February 2004 15:58, Arne Vogel wrote:
The first problem was that KDE would refuse to start, complaining about
a missing symbol
_nv22 in /usr/lib/libGLcore.so.1 (which pointed to the new version
of that NVIDIA library).
GNOME would work fine.
On Friday 06 February 2004 23:30, Arne Vogel wrote:
> Hemmann, Volker Armin wrote:
> >Hi,
> >
> >On Friday 06 February 2004 15:58, Arne Vogel wrote:
> >>The first problem was that KDE would refuse to start, complaining about
> >>a missing symbol
> >>_nv22 in /usr/lib/libGLcore.so.1 (which point
On Fri, 6 Feb 2004 17:26:04 -0500
Ernie Schroder <[EMAIL PROTECTED]> wrote:
> > As far as I have been able to figure out, if you use 2.6.1 then you
> > have to use the 1.0.5336 and not the 1.0.5336-r1 version of
> > nvidia-kernel. Try downgrading and it should work.
>
>
> Thanks Ian. That did it
Ian Truelsen wrote:
Glad to hear it. As far as sensors is concerned, from what I have been
able to find out, it will not work with the 2.6 kernel at the moment. I
think that this is because the sensor modules in the 2.6 kernel have
switched over to sysfs, but the sensor program has not made the swi
On Friday 06 February 2004 09:56 am, Grendel wrote:
> On Fri, 6 Feb 2004, Collins Richey wrote:
> > FYI,
> >
> > I've read quite a few negative comments about the latest nvidia
> > drivers, but I must say I have had the opposite experience.
>
> Well the latest drivers actually make games like NWN r
Hi,
On Saturday 07 February 2004 18:16, Ernie Schroder wrote:
> I also have the a7nx8 and a ti4200 I am seeing about a 10% decrease
> in framerate with glxgears, and am having lockups. The lockups occur
> more frequently with a GL screensaver running, but do occasionally
> happen with a rap
On Saturday 07 February 2004 01:15 pm, Hemmann, Volker Armin wrote:
> Hi,
>
> On Saturday 07 February 2004 18:16, Ernie Schroder wrote:
> > I also have the a7nx8 and a ti4200 I am seeing about a 10%
> > decrease in framerate with glxgears, and am having lockups. The
> > lockups occur more frequ
On Sat, 7 Feb 2004, Ernie Schroder wrote:
> I also have the a7nx8 and a ti4200 I am seeing about a 10% decrease
> in framerate with glxgears, and am having lockups. The lockups occur
> more frequently with a GL screensaver running, but do occasionally
> happen with a rapid mouse movement
Ernie Schroder <[EMAIL PROTECTED]> writes:
> I also have the a7nx8 and a ti4200 I am seeing about a 10% decrease
> in framerate with glxgears, and am having lockups. The lockups occur
> more frequently with a GL screensaver running, but do occasionally
> happen with a rapid mouse movement
On Saturday 07 February 2004 06:12 pm, Grendel wrote:
> On Sat, 7 Feb 2004, Ernie Schroder wrote:
> > I also have the a7nx8 and a ti4200 I am seeing about a 10%
> > decrease in framerate with glxgears, and am having lockups. The
> > lockups occur more frequently with a GL screensaver running, b
On Sunday 08 February 2004 03:22 am, Matthew Kennedy wrote:
> Ernie Schroder <[EMAIL PROTECTED]> writes:
> > I also have the a7nx8 and a ti4200 I am seeing about a 10%
> > decrease in framerate with glxgears, and am having lockups. The
> > lockups occur more frequently with a GL screensaver run
I installed the 5336 nvidia (not ebuild) package under 2.4.22-gentoo-r5
kernel without problems. (But i think that after doing this my 2.6
module disappeared (not sure))
On Sun, 8 Feb 2004 09:56:32 -0500
Ernie Schroder <[EMAIL PROTECTED]> wrote:
> On Sunday 08 February 2004 03:22 am, Matthew Kenn
On Sun, 8 Feb 2004, Jakub Krajcovic wrote:
> I installed the 5336 nvidia (not ebuild) package under 2.4.22-gentoo-r5
> kernel without problems. (But i think that after doing this my 2.6
> module disappeared (not sure))
Yes, the NVIDIA's installer, searched and if it finds a nvidia.o for
another
On Sat, 2004-02-07 at 10:16, Ernie Schroder wrote:
> I also have the a7nx8 and a ti4200 I am seeing about a 10% decrease
> in framerate with glxgears, and am having lockups. The lockups occur
> more frequently with a GL screensaver running, but do occasionally
> happen with a rapid mouse
On Sun, 8 Feb 2004, Ernie Schroder wrote:
> The box seems more stable since passing acpi=off to the kernel. I had
> used the 2.4.x syntax (noacpi) which doesn't seem to work with 2.6
> kernels.
You will probably note and increase in frame rate after disabling acpi for
kernel 2.6.
> My
On Sun, 8 Feb 2004, Ernie Schroder wrote:
> Hmmm, I hadn't thought to check the AGP status. I found that forcing
> NvAGP with:
>
> Option "NvAGP" "1"
>
> results in:
>
> $ cat /proc/driver/nvidia/agp/status
> Status: Disabled
>
> and glxgears framerate of about 5200 f/sec
Hmm.
On Fri, 06 Feb 2004 15:58:21 +0100
Arne Vogel <[EMAIL PROTECTED]> wrote:
> I'm using 2.6.1 since a couple of days as default kernel after I
> managed to solve the
> remaining upgrade-related issues (2.4.x to 2.6.x was definitely the
> most work-intensive
> transition I have experienced), and I i
On Sun, 8 Feb 2004, Ernie Schroder wrote:
> Hmmm, I hadn't thought to check the AGP status. I found that forcing
> NvAGP with:
>
> Option "NvAGP" "1"
>
> results in:
>
> $ cat /proc/driver/nvidia/agp/status
> Status: Disabled
Well I did some benchmakrs and found that glxgears is
On Sunday 08 February 2004 08:38 pm, Grendel wrote:
> On Sun, 8 Feb 2004, Ernie Schroder wrote:
> > Hmmm, I hadn't thought to check the AGP status. I found that
> > forcing NvAGP with:
> >
> > Option "NvAGP" "1"
> >
> > results in:
> >
> > $ cat /proc/driver/nvidia/agp/status
> > Status:
Hi,
On Monday 09 February 2004 04:20, Ernie Schroder wrote:
> Checking things out, I find that agpgart and nvidia-agp (both built as
> modules) are loaded at boot and trying to rmmod them fails saying
> they are in use. Does this happen due to frame buffer?
> CONFIG_FB_VESA=y
somebody should put
On Sunday 08 February 2004 11:03 pm, Hemmann, Volker Armin wrote:
> Hi,
>
> On Monday 09 February 2004 04:20, Ernie Schroder wrote:
> > Checking things out, I find that agpgart and nvidia-agp (both
> > built as modules) are loaded at boot and trying to rmmod them
> > fails saying they are in use. D
On Sun, 8 Feb 2004, Ernie Schroder wrote:
> > glxgears is giving me 3446 fps on all agp settings.
I forgot to mention that I wa running in 24bpp, 1024*768
>
> Checking things out, I find that agpgart and nvidia-agp (both built as
> modules) are loaded at boot and trying to rmmod them fails say
On Monday 09 Feb 2004 04:03, Hemmann, Volker Armin wrote:
> somebody should put a message into the ebuild that FB and NVIDA is a
> NONO. This will never work.
Of course it works, as long as you use the VESA framebuffer. It's the
Riva framebuffer that causes problems with Nvidia.
> And it has be
On Monday 09 February 2004 05:49, Ernie Schroder wrote:
> On Sunday 08 February 2004 11:03 pm, Hemmann, Volker Armin wrote:
> > Hi,
> >
> > On Monday 09 February 2004 04:20, Ernie Schroder wrote:
> > > Checking things out, I find that agpgart and nvidia-agp (both
> > > built as modules) are loaded
I don't know what's the problem with using framebuffer??? I think that
the framebuffer is a great idea. Why bother with X all the time, when
sometimes you don;t even need to start it, and you can do all you need
in the console, even _graphically_ browse the net (yes, links it is).
An one more thin
> > Frame buffer works just fine. That's not the problem.The caveat is if
> > using an Nvidia card, you need to compile in the vesa framebuffer
> > driver, NOT the nvidia FB support.
Yup. rivafb + nvidia = bad
> You do not need FB. Never. And if you want to use nvidia or ati-binary
> drivers, F
On Mon, 9 Feb 2004, The awesome and feared Jakub Krajcovic commented thusly,
> I don't know what's the problem with using framebuffer??? I think that
> the framebuffer is a great idea. Why bother with X all the time, when
> sometimes you don;t even need to start it, and you can do all you need
> i
>From the outputs mplayer gives after compilation, the only usable X
output is X11, that doesn't support fullscreen. Trust me on this one
_none_ of the X outputs even come close to VESA performance (in this
specific issue)
On Tue, 10 Feb 2004 06:25:07 +0600 (LKT)
Grendel <[EMAIL PROTECTED]> wrote:
On Tue, 10 Feb 2004, The awesome and feared Jakub Krajcovic commented thusly,
> >From the outputs mplayer gives after compilation, the only usable X
> output is X11, that doesn't support fullscreen. Trust me on this one
> _none_ of the X outputs even come close to VESA performance (in this
> speci
37 matches
Mail list logo
