Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 this can be done or even if it is possible to do. I think you just need a SYSCTL_DECL(_hw_pci) in scope. Thanks! I added SYSCTL_DECL(_hw_pci), and then uncommented out the sysctl bits. Now it works fine. But I have a question, should I put SYSCTL_DECL(_hw_pci) in some sort of header file? Anyway, patch at: http://www.unixdaemons.com/~hiten/work/diffs/pci_pci.patch I have not attached it, because I just asked a question, and if I do have to put it in a header file, then it would just be worthless having a patch in this mail. Cheers. Hi there. As requested some people, the patch has been committed, and no behaviours have changed, except that PCI_ALLOW_UNSUPPORTED_IO_RANGE kernel configuration option has been nuked. A loader tunable, hw.pci.allow_unsupported_io_range is available. It is set to 0 by default, and a sysctl is provided to show the readonly value. The above patch was committed, with a few other changes, by Matthew (mdodd). Cheers. -- Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED]) http://www.unixdaemons.com/~hiten/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 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 NVIDIA don't support it but since a kernel module is involved and those are generally not portable between major releases it is not very likely it will work. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 NVIDIA don't support it but since a kernel module is involved and those are generally not portable between major releases it is not very likely it will work. Actually it says it isn't _supported_ not it doesn't work :) The KLD consists of two parts - one is binary only, and the other has source so you can recompile it under different releases and have it work. Given that the version Matthew Dodd hacked together that used the _linux_ version of this worked in both -current and -stable I would suggest it's probably likely that it will work :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 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 NVIDIA don't support it but since a kernel module is involved and those are generally not portable between major releases it is not very likely it will work. 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 :( -- JFRH. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 size 256M nvidia0: RIVA TNT mem 0xe600-0xe6ff,0xe400-0xe4ff irq 11 at device 0.0 on pci1 pcib1: device nvidia0 requested decoded memory range 0xe400-0xe4ff pcib1: device nvidia0 requested unsupported memory range 0x0-0xe5ff (decoding 0xe400-0xe5ff, xe600-0xe6ff) nvidia0: Unable to allocate NVIDIA memory resource. device_probe_and_attach: nvidia0 attach returned 6 I had to disable the #error in nv_freebsd.h when compiling of course. - Willem On Fri, 08 Nov 2002 14:11:08 +0100 Juan Francisco Rodriguez Hervella [EMAIL PROTECTED] 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 -- JFRH. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
[ 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 get around this? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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: /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol __sF any way to get around this? i apologize for not reading current@ a bit more :) i found the __sF thread now :) i guess a temporary 'fix' will be to recompile my libc with __sF once again. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 can inform you all that libGL works after having removed the static qualifier from __sF and recompiled libc! 13125 frames in 5.0 seconds = 2625.000 FPS 16237 frames in 5.0 seconds = 3247.400 FPS 16091 frames in 5.0 seconds = 3218.200 FPS this is on a -CURRENT from 31st oct :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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? - Willem On Fri, 8 Nov 2002 17:30:19 +0100 Martin Faxer [EMAIL PROTECTED] 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: /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol __sF any way to get around this? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 I did the initial kernel driver work for this driver.) If you're clever you can edit the 1 file preventing the driver from building on -CURRENT and it will all just work. You'll note that the package detects DEVFS, which isn't a -STABLE feature. The driver works just fine on -CURRENT but don't bother NVIDIA with bug reports if you're trying to use it there. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 (Apollo VP3) host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 agp0: allocating GATT for aperture of size 256M nvidia0: RIVA TNT mem 0xe600-0xe6ff,0xe400-0xe4ff irq 11 at device 0.0 on pci1 pcib1: device nvidia0 requested decoded memory range 0xe400-0xe4ff pcib1: device nvidia0 requested unsupported memory range 0x0-0xe5ff (decoding 0xe400-0xe5ff, xe600-0xe6ff) nvidia0: Unable to allocate NVIDIA memory resource. device_probe_and_attach: nvidia0 attach returned 6 I had to disable the #error in nv_freebsd.h when compiling of course. - Willem On Fri, 08 Nov 2002 14:11:08 +0100 Juan Francisco Rodriguez Hervella [EMAIL PROTECTED] 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 -- JFRH. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 Losh fixed this in the last day or so. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 plan is to make this option a loader tunable and make the conditional in the pci code bitchy and then fix the larger problem with IO ranges. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 to
PCI_ALLOW_ACTUALLY_SUPPORTED_IO_RANGE_WHICH_IS_NON_DEFAULT_TO_BE_ANNOYING
?
I think the plan is to make this option a loader tunable and make the
conditional in the pci code bitchy and then fix the larger problem with
IO ranges.
Hi there.
I have made a basic patch, which took me about 10 minutes to do so.
Basically, it removes the option PCI_ALLOW_UNSUPPORTED_IO_RANGE, and
replaces it with a loader tunable. This is no different from imp's
change to make PCI_ENABLE_IO_MODES a l-tunable. But this time, I do not
have a sysctl to show the _readonly_ value, this is because the hw.pci
node leaves in pci.c and I am unsure of how to tackle that. I have not
tested this patch, so consider it experimental.
Also. If this patch works, then we will have to remove the
PCI_ALLOW_UNSUPPORTED_I0_RANGE from ``options'' files and add entries
for hw.pci.enable_io_modes and this loader tunable to the loader(8)
manual page or some such.
Patch also available at:
http://www.unixdaemons.com/~hiten/work/diffs/pci_pci.patch
Cheers.
P.S. hw.pci should moved somewhere global, but donno how this can be
done or even if it is possible to do.
--
Hiten Pandya
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
--- /home/hiten/pci_pci.c Fri Nov 8 17:25:52 2002
+++ /sys/dev/pci/pci_pci.c Fri Nov 8 19:11:03 2002
@@ -38,6 +38,9 @@
#include sys/systm.h
#include sys/kernel.h
#include sys/bus.h
+#if 0
+#include sys/sysctl.h
+#endif
#include machine/resource.h
@@ -90,6 +93,18 @@
DRIVER_MODULE(pcib, pci, pcib_driver, pcib_devclass, 0, 0);
/*
+ * sysctl and tunable vars
+ */
+int pci_allow_unsupported_io_range = 1;
+TUNABLE_INT(hw.pci.allow_unsupported_io_range,
+ (int *)pci_allow_unsupported_io_range);
+#if 0
+SYSCTL_INT(_hw_pci, OID_AUTO, allow_unsupported_io_range, CTLFLAG_RD,
+ pci_allow_unsupported_io_range, 1,
+ Allows the PCI Bridge to pass through an unsupported memory range
+ assigned by the BIOS.);
+#endif
+/*
* Generic device interface
*/
static int
@@ -288,21 +303,23 @@
switch (type) {
case SYS_RES_IOPORT:
if (!pcib_is_isa_io(start)) {
-#ifndef PCI_ALLOW_UNSUPPORTED_IO_RANGE
- if (start sc-iobase)
- start = sc-iobase;
- if (end sc-iolimit)
- end = sc-iolimit;
- if (end start)
- start = 0;
-#else
- if (start sc-iobase)
- printf(start (%lx) sc-iobase (%x)\n, start, sc-iobase);
- if (end sc-iolimit)
- printf(end (%lx) sc-iolimit (%x)\n, end, sc-iolimit);
- if (end start)
- printf(end (%lx) start (%lx)\n, end, start);
-#endif
+ if (!pci_allow_unsupported_io_range) {
+ if (start sc-iobase)
+ start = sc-iobase;
+ if (end sc-iolimit)
+ end = sc-iolimit;
+ if (end start)
+ start = 0;
+ } else {
+ if (start sc-iobase)
+ printf(start (%lx) sc-iobase (%x)\n, start,
+ sc-iobase);
+ if (end sc-iolimit)
+ printf(end (%lx) sc-iolimit (%x)\n,
+ end, sc-iolimit);
+ if (end start)
+ printf(end (%lx) start (%lx)\n, end, start);
+ }
}
if (!pcib_is_isa_io(start)
((start sc-iobase) || (end sc-iolimit))) {
@@ -325,21 +342,23 @@
*/
case SYS_RES_MEMORY:
if (!pcib_is_isa_mem(start)) {
-#ifndef PCI_ALLOW_UNSUPPORTED_IO_RANGE
- if (start sc-membase end = sc-membase)
- start = sc-membase;
- if (end sc-memlimit)
- end = sc-memlimit;
- if (end start)
- start = 0;
-#else
- if (start sc-membase end sc-membase)
- printf(start (%lx) sc-membase (%x)\n, start, sc-membase);
- if (end sc-memlimit)
- printf(end (%lx) sc-memlimit (%x)\n, end, sc-memlimit);
- if (end start)
- printf(end (%lx) start (%lx)\n, end, start);
-#endif
+ if (!pci_allow_unsupported_io_range) {
+ if (start sc-membase end = sc-membase)
+ start = sc-membase;
+ if (end sc-memlimit)
+ end = sc-memlimit;
+ if (end start)
+ start = 0;
+ } else
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
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 FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg46408/pgp0.pgp Description: PGP signature
