hello,
Any chance someone can support nforce2's chipset agp? Not all of us own
nvidia graphics cards :-(
I don't know how hard it is to get this working on freebsd.
here's some code:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=utf-8&threadm=20030524205432.GA17179%40suse.de.lucky.linux.
Samy Al Bahra wrote:
> Daniel Eischen Wrote:
> > No, I don't think Terry is jumping to conclusion. Read
> > the archives of this problem. The Nvidia drivers and OpenGL
> > for FreeBSD won't work with -current and any threading
> > library other than libc_r.
>
> I didn't deal with any users havin
Daniel Eischen Wrote:
> No, I don't think Terry is jumping to conclusion. Read
> the archives of this problem. The Nvidia drivers and OpenGL
> for FreeBSD won't work with -current and any threading
> library other than libc_r.
I didn't deal with any users having kernel crashes from this %gs
resto
Samy Al Bahra wrote:
> I think Terry is jumping to conclusions on what Evan's problem could be.
> I have this seen this cause application to crash at exit (if using
> OpenGL) but never a crash in kernel-space from the nVidia drivers.
1) It works with libc_r, but not with libthr and not
On 13 Jun 2003, Samy Al Bahra wrote:
> Hey,
>
> > I believe the fix is as simple as saving and restoring %gs in
> > the nVidia driver, and/or not letting the nVidia use %gs at
> > all (segment registers generally belong to the OS, in any case,
> > and stealing a CPU register of any kind for exclu
On 13 Jun 2003 05:11:34 +, Samy Al Bahra <[EMAIL PROTECTED]> wrote:
Hey,
I believe the fix is as simple as saving and restoring %gs in
the nVidia driver, and/or not letting the nVidia use %gs at
all (segment registers generally belong to the OS, in any case,
and stealing a CPU register of any
Hey,
> I believe the fix is as simple as saving and restoring %gs in
> the nVidia driver, and/or not letting the nVidia use %gs at
> all (segment registers generally belong to the OS, in any case,
> and stealing a CPU register of any kind for exclusive use of a
> driver is a pig trick).
Please ta
Evan Dower wrote:
> >NVIDIA is handling everything to do with the driver. Expect a new
> >release "shortly" *cough*.
>
> I was afraid that might be the case :-(
The only thing you care about is entry and exit through driver
entry points... and maybe interrupts. It would be easy enough
to wrapper
Evan Dower wrote:
> I am highly interested in getting nvidia-driver to work well for FBSD, and
> in particular my own computer. I do not have the expertise to hack on either
> it or the kernel (yet), but I am eager to provide debugging information.
> nvidia-driver frequently crashes my machine, so
I was afraid that might be the case :-(
From: Munish Chopra <[EMAIL PROTECTED]>
On 2003-06-12 11:51 +, Evan Dower wrote:
> I am highly interested in getting nvidia-driver to work well for FBSD,
and
> in particular my own computer. I do not have the expertise to hack on
> either it or the ke
On 2003-06-12 11:51 +, Evan Dower wrote:
> I am highly interested in getting nvidia-driver to work well for FBSD, and
> in particular my own computer. I do not have the expertise to hack on
> either it or the kernel (yet), but I am eager to provide debugging
> information. nvidia-driver freq
I am highly interested in getting nvidia-driver to work well for FBSD, and
in particular my own computer. I do not have the expertise to hack on either
it or the kernel (yet), but I am eager to provide debugging information.
nvidia-driver frequently crashes my machine, so I expect that my input
12 matches
Mail list logo
