Re: New NVidia drivers on -current
On Monday 18 November 2002 07.29, Mikhail Teterin wrote: Has anyone tried them yet? After removing the #error triggered by __FreeBSD_version being over 50, I got the thing nvidia.ko to build, but: 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers 00:56:12 aldan kernel: Preloaded elf module /boot/kernel/nvidia.ko at 0xc06470b0. 00:56:12 aldan kernel: VESA: NVidia 00:56:12 aldan kernel: VESA: NVidia Corporation NV15 Reference Board Chip Rev A0 00:56:14 aldan kernel: nvidia0: GeForce2 GTS mem 0xf000-0xf7ff,0xe900-0xe9ff irq 11 at device 0.0 on pci1 00:56:14 aldan kernel: pcib1: device nvidia0 requested decoded memory range 0xe900-0xe9ff 00:56:14 aldan kernel: pcib1: device nvidia0 requested unsupported memory range 0x0-0xe9ff (decoding 0xe900-0xe9ff, 0xf000-0xf7ff) 00:56:14 aldan kernel: nvidia0: Unable to allocate NVIDIA memory resource. 00:56:14 aldan kernel: device_probe_and_attach: nvidia0 attach returned 6 Any clues, or is, indeed, a major porting effort required to get it to work on -current? Thanks! -mi Hi, I suggest you read the following post to this list: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1510354+0+/usr/local/www/db/text/2002/freebsd-current/20021110.freebsd-current It talks about the (now deprecated) kernel config option PCI_ALLOW_UNSUPPORTED_IO_RANGE. This was moved to be a loader tunable instead. If you enable this at boot time you should be able to use nvidias driver without any problems on -CURRENT. I haven't had time to try this myself yet so I cannot promise you that it will work. You can find the setting if you try sysctl -a|grep pci, hw.pci.allow_unsupported_io_range should be set to one. Note that this cannot be set during runtime! Hope this helps. //David Holm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New NVidia drivers on -current
On Monday 18 November 2002 09.03, David Holm wrote: Hi, I suggest you read the following post to this list: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1510354+0+/usr/local/www/db/tex t/2002/freebsd-current/20021110.freebsd-current It talks about the (now deprecated) kernel config option PCI_ALLOW_UNSUPPORTED_IO_RANGE. This was moved to be a loader tunable instead. If you enable this at boot time you should be able to use nvidias driver without any problems on -CURRENT. I haven't had time to try this myself yet so I cannot promise you that it will work. You can find the setting if you try sysctl -a|grep pci, hw.pci.allow_unsupported_io_range should be set to one. Note that this cannot be set during runtime! Hope this helps. //David Holm Note that the patch has already been applied so no need to patch your kernel! BTW, why hasn't anyone set the mailing list to automatically set the reply-to address to [EMAIL PROTECTED]? //David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New NVidia drivers on -current
On 2002-11-17 23:53 +, Kris Kennaway wrote: [...] Try putting this in your loader.conf: hw.pci.allow_unsupported_io_range=1 This allowed the device to probe for me, but the system locks up when I try and start X. Do you by any chance either have an SiS chipset or a regular TNT (or both)? -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New NVidia drivers on -current
David Holm wrote: Note that the patch has already been applied so no need to patch your kernel! BTW, why hasn't anyone set the mailing list to automatically set the reply-to address to [EMAIL PROTECTED]? Because the poster may not be a list subscriber, and the most important person to reply to is the poster. It's up to the poster's MUA to know that the poster is a subscriber to the list, and set the Reply-To: on the basis of that knowledge. This could be done on the server, but there are two reasons not to do it in the mailing list manager: 1) It's computationally expensive, and all processing that could be done on either the server or the client, should be done on the client, to ensure that the deployment scales. 2) There is a draft RFC which is under consideration by the IETF, and is likely to become an issued RFC, which requires that certain headers not be altered by mailing list managers; specifically, all non hop-to-hop headers should not be modified by the mailing list manager, and Reply-To: is an end-to-end header, not a hop-to-hop header. Sof if it isn't in violation of an RFC for the mailing list software to set the Reply-To: now, it likely will be, in the near future. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New NVidia drivers on -current
At 9:11 AM +0100 2002/11/18, David Holm wrote: BTW, why hasn't anyone set the mailing list to automatically set the reply-to address to [EMAIL PROTECTED]? http://www.unicom.com/pw/reply-to-harmful.html. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
New NVidia drivers on -current
Has anyone tried them yet? After removing the #error triggered by __FreeBSD_version being over 50, I got the thing nvidia.ko to build, but: 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers 00:56:12 aldan kernel: Preloaded elf module /boot/kernel/nvidia.ko at 0xc06470b0. 00:56:12 aldan kernel: VESA: NVidia 00:56:12 aldan kernel: VESA: NVidia Corporation NV15 Reference Board Chip Rev A0 00:56:14 aldan kernel: nvidia0: GeForce2 GTS mem 0xf000-0xf7ff,0xe900-0xe9ff irq 11 at device 0.0 on pci1 00:56:14 aldan kernel: pcib1: device nvidia0 requested decoded memory range 0xe900-0xe9ff 00:56:14 aldan kernel: pcib1: device nvidia0 requested unsupported memory range 0x0-0xe9ff (decoding 0xe900-0xe9ff, 0xf000-0xf7ff) 00:56:14 aldan kernel: nvidia0: Unable to allocate NVIDIA memory resource. 00:56:14 aldan kernel: device_probe_and_attach: nvidia0 attach returned 6 Any clues, or is, indeed, a major porting effort required to get it to work on -current? Thanks! -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New NVidia drivers on -current
On 2002-11-18 01:29 +, Mikhail Teterin wrote: Has anyone tried them yet? After removing the #error triggered by __FreeBSD_version being over 50, I got the thing nvidia.ko to build, but: 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers 00:56:12 aldan kernel: Preloaded elf module /boot/kernel/nvidia.ko at 0xc06470b0. 00:56:12 aldan kernel: VESA: NVidia 00:56:12 aldan kernel: VESA: NVidia Corporation NV15 Reference Board Chip Rev A0 00:56:14 aldan kernel: nvidia0: GeForce2 GTS mem 0xf000-0xf7ff,0xe900-0xe9ff irq 11 at device 0.0 on pci1 00:56:14 aldan kernel: pcib1: device nvidia0 requested decoded memory range 0xe900-0xe9ff 00:56:14 aldan kernel: pcib1: device nvidia0 requested unsupported memory range 0x0-0xe9ff (decoding 0xe900-0xe9ff, 0xf000-0xf7ff) 00:56:14 aldan kernel: nvidia0: Unable to allocate NVIDIA memory resource. 00:56:14 aldan kernel: device_probe_and_attach: nvidia0 attach returned 6 Any clues, or is, indeed, a major porting effort required to get it to work on -current? Thanks! -mi http://www.thirteenandtwo.org/nvidia/faq.html The box is currently down, since somone decided to upgrade it to -CURRENT and messed up, but Marc Fonvieille was nice enough to put it up here until tomorrow or so: http://people.freebsd.org/~blackend/nvidia/faq.html (missing style sheet, but oh well). Basically it works fine on -CURRENT, what you are seeing could be because you have something interfering (anything from ACPI to some old ISA device), but most likely you are missing SYSVSHM or don't have sufficiently new X binaries (you need 4.2.1 -Servers, -clients and -libraries). If none of the above works, mdodd@ can most likely give you a better answer. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New NVidia drivers on -current
On Mon, Nov 18, 2002 at 01:29:12AM -0500, Mikhail Teterin wrote: Has anyone tried them yet? After removing the #error triggered by __FreeBSD_version being over 50, I got the thing nvidia.ko to build, but: 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers 00:56:12 aldan kernel: Preloaded elf module /boot/kernel/nvidia.ko at 0xc06470b0. 00:56:12 aldan kernel: VESA: NVidia 00:56:12 aldan kernel: VESA: NVidia Corporation NV15 Reference Board Chip Rev A0 00:56:14 aldan kernel: nvidia0: GeForce2 GTS mem 0xf000-0xf7ff,0xe900-0xe9ff irq 11 at device 0.0 on pci1 00:56:14 aldan kernel: pcib1: device nvidia0 requested decoded memory range 0xe900-0xe9ff 00:56:14 aldan kernel: pcib1: device nvidia0 requested unsupported memory range 0x0-0xe9ff (decoding 0xe900-0xe9ff, 0xf000-0xf7ff) 00:56:14 aldan kernel: nvidia0: Unable to allocate NVIDIA memory resource. 00:56:14 aldan kernel: device_probe_and_attach: nvidia0 attach returned 6 Any clues, or is, indeed, a major porting effort required to get it to work on -current? Thanks! Try putting this in your loader.conf: hw.pci.allow_unsupported_io_range=1 This allowed the device to probe for me, but the system locks up when I try and start X. Kris msg46846/pgp0.pgp Description: PGP signature
