On Sat, Nov 09, 2002 at 08:40:21AM -0500, Hiten Pandya wrote the words in effect of:
On Fri, Nov 08, 2002 at 07:21:32PM -0800, Brooks Davis wrote the words in effect of:
On Fri, Nov 08, 2002 at 10:09:10PM -0500, Hiten Pandya wrote:
P.S. hw.pci should moved somewhere global, but donno how
Hello,
I've just seen the release of FreeBSD-NVIDIA driver for
FreeBSD-4.7
Will this driver work with -CURRENT ?¿
PS: http://www.nvidia.com/view.asp?IO=freebsd_1.0-3203
--
JFRH.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Nov 08, 2002 at 02:11:08PM +0100, Juan Francisco Rodriguez Hervella wrote:
Hello,
I've just seen the release of FreeBSD-NVIDIA driver for
FreeBSD-4.7
Will this driver work with -CURRENT ?¿
PS: http://www.nvidia.com/view.asp?IO=freebsd_1.0-3203
The README file found at the
On Fri, 2002-11-08 at 23:52, Erik Trulsson wrote:
The README file found at the above URL claims that:
quote
FreeBSD -STABLE versions older than 4.7 and FreeBSD -CURRENT are
not supported.
end quote
So I guess the answer is no.
It is of course possible that it might work anyway even if
Erik Trulsson wrote:
On Fri, Nov 08, 2002 at 02:11:08PM +0100, Juan Francisco Rodriguez Hervella wrote:
Hello,
I've just seen the release of FreeBSD-NVIDIA driver for
FreeBSD-4.7
Will this driver work with -CURRENT ?¿
PS: http://www.nvidia.com/view.asp?IO=freebsd_1.0-3203
The
Hmm, not for me (yet?). Part of dmesg:
VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc03bb322 (122)
VESA: NVidia
VESA: NVidia Riva TNT A0
agp0: VIA 82C597 (Apollo VP3) host to PCI bridge mem 0xe000-0xe3ff at
device 0.0 on pci0
agp0: allocating GATT for aperture of
[ sorry for not getting the in-reply-to correct, i'm no longer
subscribed to current@ ]
the nvidia supplied drivers appear to work fine except for libGL* which
are compiled on an older system and thus give:
/usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol
__sF
any way to
On Fri, Nov 08, 2002 at 05:30:19PM +0100, Martin Faxer wrote:
[ sorry for not getting the in-reply-to correct, i'm no longer
subscribed to current@ ]
the nvidia supplied drivers appear to work fine except for libGL* which
are compiled on an older system and thus give:
On Fri, Nov 08, 2002 at 05:43:20PM +0100, Martin Faxer wrote:
On Fri, Nov 08, 2002 at 05:30:19PM +0100, Martin Faxer wrote:
i apologize for not reading current@ a bit more :)
i found the __sF thread now :)
another apology, since this is my 3rd mail in a very short period of
time! however, i
Does your kernel module load correctly? I get complaints about an
unsupported memory range [see my previous post for more details]. I'm
building a kernel with 'option PCI_ALLOW_UNSUPPORTED_IO_RANGE' now to
see if that helps.
And about __sF, could an LD_PRELOAD with a __sF 'stub' be a workaround?
On Fri, 8 Nov 2002, Juan Francisco Rodriguez Hervella wrote:
I've seen that... so, the only possibility we've got is to cry loudly at
NVIDIA people and ask them to make a driver for -CURRENT
(I shouldn't install -CURRENT on my home computer :(
I run -CURRENT on my systems (which is where
Recompile your kernel with
options PCI_ALLOW_UNSUPPORTED_IO_RANGE
On Fri, 8 Nov 2002, Willem van Engen wrote:
Hmm, not for me (yet?). Part of dmesg:
VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc03bb322 (122)
VESA: NVidia
VESA: NVidia Riva TNT A0
agp0: VIA 82C597
Martin Faxer wrote:
the nvidia supplied drivers appear to work fine except for libGL* which
are compiled on an older system and thus give:
/usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol
__sF
any way to get around this?
Yes. Run a newer version of -current. Warner
Matthew N. Dodd wrote:
Recompile your kernel with
options PCI_ALLOW_UNSUPPORTED_IO_RANGE
Given the number of times that this comes up, can we change that to
PCI_ALLOW_ACTUALLY_SUPPORTED_IO_RANGE_WHICH_IS_NON_DEFAULT_TO_BE_ANNOYING
?
Thanks.
-- Terry
To Unsubscribe: send mail to [EMAIL
On Fri, 8 Nov 2002, Terry Lambert wrote:
Matthew N. Dodd wrote:
Recompile your kernel with
options PCI_ALLOW_UNSUPPORTED_IO_RANGE
Given the number of times that this comes up, can we change that to
PCI_ALLOW_ACTUALLY_SUPPORTED_IO_RANGE_WHICH_IS_NON_DEFAULT_TO_BE_ANNOYING
?
I think the
On Fri, Nov 08, 2002 at 05:45:00PM -0500, Matthew N. Dodd wrote the words in effect of:
On Fri, 8 Nov 2002, Terry Lambert wrote:
Matthew N. Dodd wrote:
Recompile your kernel with
options PCI_ALLOW_UNSUPPORTED_IO_RANGE
Given the number of times that this comes up, can we change that
On Fri, Nov 08, 2002 at 10:09:10PM -0500, Hiten Pandya wrote:
P.S. hw.pci should moved somewhere global, but donno how this can be
done or even if it is possible to do.
I think you just need a SYSCTL_DECL(_hw_pci) in scope.
-- Brooks
--
Any statement of the form X is the one, true Y is
17 matches
Mail list logo
