Hi.
I have two question. I hope what someone helps me.
First:
I have NVidia fx5600 and installs drivers from
/usr/ports/x11/nvidia-driver
# cat /boot/loader.conf
hw.ata.ata_dma=0
nvidia_load="YES"
linux_load="YES" # Linux emulat
> All code interacting with FreeBSD data structures resides in the open
> part of the kernel module; a pointer to the newly allocated object is
> passed to rm_alloc_agp_pages as an opaque pointer, it is required later
> when the NVIDIA AGP GART driver needs to obtain the physical addresses
> of the
> It'd be interesting to learn if the code path you suspect really is the
> one taken in the case of this failure. Is this problem easily
> reproducible on your machine? If so, how and with what hard/software
> combination?
I think the stack is getting (somewhat) smashed so there's no real way to
On Thu, Nov 14, 2002 at 10:55:17AM -0500, Kenneth Culver wrote:
>
> I'm not positive, but looking at the code this is what happens.
>
> first an object is allocated, then it goes and finds some nvidia
> specific data structure contained in that object (from what I can
> tell), then it calls rm_all
> Are you sure that nv_free_vm_object() is free'ing a valid object?
>
I'm not positive, but looking at the code this is what happens.
first an object is allocated, then it goes and finds some nvidia specific
data structure contained in that object (from what I can tell), then it
calls rm_alloc_agp
On 14-Nov-2002 Kenneth Culver wrote:
>> several functions that call vm_object functions in FreeBSD's kernel that
>> eventually call atomic_clear_short(). For some reason those functions in
>> between aren't in the backtrace though, and without that I can (and
>> have) look through the code in the
> several functions that call vm_object functions in FreeBSD's kernel that
> eventually call atomic_clear_short(). For some reason those functions in
> between aren't in the backtrace though, and without that I can (and
> have) look through the code in the kernel to see how nv_alloc_pages can
> get
> Looks like it is indeed nvidia's fault. It called atomic_clear_short()
> with an invalid pointer in nv_alloc_pages(). You might be able to look
> at nv_alloc_pages() to try and figure out the bug.
nv_alloc_pages never actually calls atomic_clear_short(), but it does call
several functions that
On 14-Nov-2002 Kenneth Culver wrote:
> I'm posting this here because of a panic I'm getting using the FreeBSD
> nvidia driver; however, I'm not convinced that this panic is the fault of
> the driver, and I wanted to post the backtrace here (from a serial
> console, can't see anything on the pc con
I'm posting this here because of a panic I'm getting using the FreeBSD
nvidia driver; however, I'm not convinced that this panic is the fault of
the driver, and I wanted to post the backtrace here (from a serial
console, can't see anything on the pc console during this crash since X is
up) just in
On Sat, 3 Aug 2002, Erik Greenwald wrote:
> ugh, sounds like the lip-service I was getting. "I'll look into that" :/
No, they're working on it, and actually have GL running in the lab.
> I'm starting to ponder the legality and challenge involved in reverse
> engineering the card and building a d
On Sat, Aug 03, 2002 at 05:28:07PM -0400, Matthew N. Dodd wrote:
>
> Sorry, this has been the status for months now.
>
ugh, sounds like the lip-service I was getting. "I'll look into that" :/
I'm starting to ponder the legality and challenge involved in reverse
engineering the card and build
On Sat, 3 Aug 2002, Thierry Herbelot wrote:
> Le Saturday 03 August 2002 22:09, Matthew N. Dodd a écrit :
> > On Sat, 3 Aug 2002, Alp ATICI wrote:
> > > And what's the latest about the Nvidia drivers? It's mentioned that
> > > Nvidia has plans to produce the
Le Saturday 03 August 2002 22:09, Matthew N. Dodd a écrit :
> On Sat, 3 Aug 2002, Alp ATICI wrote:
> > And what's the latest about the Nvidia drivers? It's mentioned that
> > Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to
> > know what
On Sat, 3 Aug 2002, Alp ATICI wrote:
> And what's the latest about the Nvidia drivers? It's mentioned that
> Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to
> know what's going on in that issue too.
"Any day now."
--
| Matthew N. D
On 2002-08-03 12:14 +, Alp ATICI wrote:
[snip]
>
> And what's the latest about the Nvidia drivers? It's mentioned that
> Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to know
> what's going on in that issue too.
>
We know about as
th 5.x for some time?
And what's the latest about the Nvidia drivers? It's mentioned that
Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to know
what's going on in that issue too.
Thanks,
Alp
On Mon, 4 Feb 2002, John Baldwin wrote:
> The kernel is already so
Rufino wrote:
>
> Hi,
>
> Just thought I would mention my -STABLE NVidia drivers have been working for
> the past week, as far as 2D and XVideo goes. Available on CVS at
> http://sourceforge.net/projects/nv-bsd.
>
> David
>
> To Unsubscribe: send mail to [EMAIL
Vladimir Kushnir wrote:
> Well, since nobody seems to be interested (I can't for the life of mine
> understand why), thanks and a couple of (perhaps silly) questions.
I'm interested, I've just been busy thats all. I haven't had a chance to play
with the drivers yet.
Thanks David!
To Unsubscrib
On Saturday 17 November 2001 12:41 am, you wrote:
> Hi,
Hey,
> Well, since nobody seems to be interested (I can't for the life of mine
> understand why), thanks and a couple of (perhaps silly) questions.
>
>
> i) any plans on porting to -CURRENT? On GLX stuff? And does it work with
> DEVFS?
I
Hi,
Well, since nobody seems to be interested (I can't for the life of mine
understand why), thanks and a couple of (perhaps silly) questions.
On Thu, 15 Nov 2001, David Rufino wrote:
> Hi,
>
> Just thought I would mention my -STABLE NVidia drivers have been working for
> the
Hi,
Just thought I would mention my -STABLE NVidia drivers have been working for
the past week, as far as 2D and XVideo goes. Available on CVS at
http://sourceforge.net/projects/nv-bsd.
David
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the b
This day is something I've been looking forward to, nvidia hardware
acceleration for XFree86 4.x. The kernel module loads, but the
nvidia_drv.o bails out complaining about failed to allocate dma fb.. I
dont think that's your code causing it of course, but do you have any idea
what might?
> Hi,
>
Hi,
I've uploaded the nvidia driver code I've been working on to the CVS repository
at http://sourceforge.net/projects/nv-bsd, if anyone wants to take a look.
It is still work in progress, but has come a long way. In particular you
can see the dmesg output when X is started at:
http://cvs.sourc
> I would guess that if they have managed to abstract their NT source to the point
> where a simple wrapper can turn it into a linux kmod, then it is quite possible
> that it may be able to be ported to FreeBSD. The only other thing is whether
> their X Server could be ported in such a way (is it
ways
run XFree86 in linux emulation...if possible.
> > that's less than the
> > programmer time to make the NVidia drivers work is worth, and you can
> > actually be sure you'll have some kind of success, where the NVidia stuff
> > is really up in the air.
>
>
aybe. but honestly, do you
> really care enough to try?
'Maybe' is good enough for me.
> that's less than the
> programmer time to make the NVidia drivers work is worth, and you can
> actually be sure you'll have some kind of success, where the NVidia stuff
ks for a VooDoo3. that's less than the
programmer time to make the NVidia drivers work is worth, and you can
actually be sure you'll have some kind of success, where the NVidia stuff
is really up in the air.
-garrett
x
Peter Wemm wrote:
> They provide the OS interface glue to enable interfacing with the
> kernel. The driver then completely takes over the card management
> in kernel context - busmaster DMA, command fifo managenent, card
> memory management, the lot.
So, given a working FreeBSD-speci
actually you're not even getting kernel driver source for linux. What
you're getting is an ugly binary blob that looks like the guts of an NT
driver, plus enough source stuff to let the kernel hook to the binary
blob. It's not pretty. And, as you might expect, it's a little prone to
failure.
ron
Garrett Rooney wrote:
> On Sat, 29 Jul 2000, Nimrod Mesika wrote:
>
> > I thought the whole point of XFree4 new driver mechanism was that
> > it was OS-neutral. It should be possible to run the same binary
> > driver on all x86 platforms running XFree4 *without* recompiling.
> >
> > I don't know
On Sat, 29 Jul 2000, Nimrod Mesika wrote:
> I thought the whole point of XFree4 new driver mechanism was that
> it was OS-neutral. It should be possible to run the same binary
> driver on all x86 platforms running XFree4 *without* recompiling.
>
> I don't know how this driver interacts with the
On Sat, Jul 29, 2000 at 11:59:17PM +0800, Trent Nelson wrote:
> On a more technical note, given an accurate port of the kernel
> device driver (which would be trivial at best), is there any
> reason these Linux OpenGL drivers & associated libraries can't
> just be branded as 'Linux' object types a
Moving to hackers@, where most discussions regarding the NVIDIA drivers
seem to take place lately.
Chris BeHanna wrote:
> I don't remember if it was this list on which I saw this
> discussion, or if it was hackers. Anyway, I looked at xfree86.org
> today, and noticed
Thus spake Trent Nelson ([EMAIL PROTECTED]):
> What's porting going to involve? I can't see porting the kernel module
> being *too* difficult (I'd love to start on something after exams) - but
> I don't know how the Linux object files for the XFree86 interface are
> going to be dealt with
Brandon Fosdick wrote:
>
> Does anybody have the new nvidia drivers working yet? Aparently I'm not
> as smart as I thought. :)
From what I've been told - FreeBSD's kernel is unable to run Linux's
kernel modules. Hence, the source provided by nVIDIA for
Does anybody have the new nvidia drivers working yet? Aparently I'm not
as smart as I thought. :)
-Brandon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
37 matches
Mail list logo