Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 08/22/2018 10:29, Alan Cox wrote: > On 08/22/2018 08:48, tech-lists wrote: >> On 22/08/2018 05:29, Manfred Antar wrote: On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: > Перенаправленное сообще

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 22/08/2018 16:29, Alan Cox wrote: All of kmem_alloc_attr(), kmem_alloc_contig(), and kmem_malloc() should have their first parameter, typically kernel_arena, but sometimes kmem_arena, removed in FreeBSD 12. There is still one more pending change to kmem_free() that has not hit HEAD yet. That

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

> On Aug 21, 2018, at 10:10 PM, Alan Cox wrote: > > On 08/21/2018 23:29, Manfred Antar wrote: >> >>> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: >>> >>> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: Перенаправленное сообщение Тема: nvidi

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 08/22/2018 08:48, tech-lists wrote: > On 22/08/2018 05:29, Manfred Antar wrote: >> >>> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev >>> wrote: >>> >>> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: Перенаправленное сообщение Тема: nvidia-driver buil

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 22/08/2018 05:29, Manfred Antar wrote: On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: Перенаправленное сообщение Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) Дата: Tue, 21 Aug 2018 16:41:

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 08/21/2018 23:29, Manfred Antar wrote: > >> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: >> >> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: >>> Перенаправленное сообщение >>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) >>> Дата: Tue, 2

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: > > On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: >> >> Перенаправленное сообщение >> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) >> Дата: Tue, 21 Aug 2018 16:41:42 +0700 >> От: Alex V. Pe

Re: nvidia-driver fails to load gui

Hi, On Wed, Dec 10, 2014 at 5:31 PM, Shawn Webb wrote: > On Wed, Dec 10, 2014 at 11:27 AM, Henry Hu wrote: > > > > > > > On Wed, Dec 10, 2014 at 11:25 AM, Shawn Webb wrote: > > > >> On Wed, Dec 10, 2014 at 11:22 AM, Henry Hu > wrote: > >> > >>> > >>> > >>> On Wed, Dec 10, 2014 at 11:17 AM, Sh

Re: nvidia-driver fails to load gui

On Wed, Dec 10, 2014 at 11:27 AM, Henry Hu wrote: > > > On Wed, Dec 10, 2014 at 11:25 AM, Shawn Webb wrote: > >> On Wed, Dec 10, 2014 at 11:22 AM, Henry Hu wrote: >> >>> >>> >>> On Wed, Dec 10, 2014 at 11:17 AM, Shawn Webb wrote: >>> On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu wrote:

Re: nvidia-driver fails to load gui

On Wed, Dec 10, 2014 at 11:25 AM, Shawn Webb wrote: > On Wed, Dec 10, 2014 at 11:22 AM, Henry Hu wrote: > >> >> >> On Wed, Dec 10, 2014 at 11:17 AM, Shawn Webb wrote: >> >>> On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu >>> wrote: >>> On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb w

Re: nvidia-driver fails to load gui

On Wed, Dec 10, 2014 at 11:22 AM, Henry Hu wrote: > > > On Wed, Dec 10, 2014 at 11:17 AM, Shawn Webb wrote: > >> On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu wrote: >> >>> >>> >>> On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb wrote: >>> Hey All, More new laptop woes. The good-ish n

Re: nvidia-driver fails to load gui

On Wed, Dec 10, 2014 at 11:17 AM, Shawn Webb wrote: > On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu wrote: > >> >> >> On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb wrote: >> >>> Hey All, >>> >>> More new laptop woes. The good-ish news is that the VESA driver works, >>> but >>> x11/nvidia-driver doe

Re: nvidia-driver fails to load gui

On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu wrote: > > > On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb wrote: > >> Hey All, >> >> More new laptop woes. The good-ish news is that the VESA driver works, but >> x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run `startx`, it >> appears that

Re: nvidia-driver fails to load gui

On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb wrote: > Hey All, > > More new laptop woes. The good-ish news is that the VESA driver works, but > x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run `startx`, it > appears that xorg switches to a new vty, but doesn't actually bring up the >

Followup re: nvidia-driver linux patch (was: recent commit causes lock up)

Just thought I'd give a heads up re: the nvidia_linux.c patch and the latest version of nvidia-driver. I upgraded to the new nvidia-driver-280.13 just now and had to remove the patch file. It broke the build with a "wrong number of arguments to fget" error. After removing the patch, the build pr

Re: nvidia-driver not work

On 17.08.2010 18:47 (UTC+1), Ivan Klymenko wrote: $ dmesg (cut) panic: mutex page lock not owned at /usr/src/sys/vm/vm_page.c:1759 cpuid = 0 Uptime: 3m35s Use the latest nvidia driver from the website (256.44) and not from the port. Here the test port... Sorry, I am afraid there is no atta

Re: nvidia-driver not work

[Solved] The problem, is a driver of the port "nvidia-driver", i used the test port (said me Ivan) В Tue, 17 Aug 2010 09:52:50 -0400 John Baldwin пишет: - Show quoted text - Here the test port... nvidia-driver.256.44.port.tar.bz2 5K Download I upload the file in this URL http://rapidshare.com/fil

Re: nvidia-driver not work

On 17.08.2010 16:11 (UTC+1), Ivan Klymenko wrote: В Tue, 17 Aug 2010 09:52:50 -0400 John Baldwin пишет: On Saturday, August 14, 2010 9:35:02 pm Álvaro Castillo wrote: $ dmesg (cut) panic: mutex page lock not owned at /usr/src/sys/vm/vm_page.c:1759 cpuid = 0 Uptime: 3m35s Use the latest nvi

Re: nvidia-driver not work

> >>> $ dmesg (cut) > >>> > >>> panic: mutex page lock not owned at /usr/src/sys/vm/vm_page.c:1759 > >>> cpuid = 0 > >>> Uptime: 3m35s > >> > >> Use the latest nvidia driver from the website (256.44) and not from > >> the port. > >> > > Here the test port... > > Sorry, I am afraid there is no atta

Re: nvidia-driver not work

В Tue, 17 Aug 2010 09:52:50 -0400 John Baldwin пишет: > On Saturday, August 14, 2010 9:35:02 pm Álvaro Castillo wrote: > > $ dmesg (cut) > > > > panic: mutex page lock not owned at /usr/src/sys/vm/vm_page.c:1759 > > cpuid = 0 > > Uptime: 3m35s > > Use the latest nvidia driver from the website (

Re: nvidia-driver not work

On Saturday, August 14, 2010 9:35:02 pm Álvaro Castillo wrote: > $ dmesg (cut) > > panic: mutex page lock not owned at /usr/src/sys/vm/vm_page.c:1759 > cpuid = 0 > Uptime: 3m35s Use the latest nvidia driver from the website (256.44) and not from the port. -- John Baldwin ___

Re: nvidia-driver not work

On Sun, 15 Aug 2010 02:35:02 +0100 __lvaro Castillo wrote: > I dont understand this -> Dump failed. Partition too small. -> My root > partition has got a 435GB only ocupated 17GB and swap 512MB > You have 4GB of memory and only 512MB of swap - too small to dump the contents of memory. Crash du

Re: nvidia-driver not work

В Sun, 15 Aug 2010 02:35:02 +0100 Álvaro Castillo пишет: > This is my kernel > > http://pastebin.com/1NpvzNp6 > try the following: Delete: AGP device from the kernel config rebuild new kernel and boot into single user mode, mount -u / mount -a and reinstall the NVIDIA driver port ... cd /usr/p

Re: nvidia-driver crashing kernel on head

On Saturday 17 July 2010 17:25:27 Christian Zander wrote: > On Sat, Jul 17, 2010 at 07:24:54AM -0700, David Naylor wrote: > (...) > > > > >>> These freezes and panics are due to the driver using a spin mutex > > > >>> instead of a > > > >>> regular mutex for the per-file descriptor event_mtx. If

Re: nvidia-driver crashing kernel on head

On Sunday 11 July 2010 22:14:44 Doug Barton wrote: > On 07/08/10 14:52, Rene Ladan wrote: > > On 08-07-2010 22:09, Doug Barton wrote: > >> On Thu, 8 Jul 2010, John Baldwin wrote: > >>> These freezes and panics are due to the driver using a spin mutex > >>> instead of a > >>> regular mutex for the p

Re: nvidia-driver crashing kernel on head

On 07/08/10 14:52, Rene Ladan wrote: > On 08-07-2010 22:09, Doug Barton wrote: >> On Thu, 8 Jul 2010, John Baldwin wrote: >> >>> These freezes and panics are due to the driver using a spin mutex >>> instead of a >>> regular mutex for the per-file descriptor event_mtx. If you patch the >>> driver >

Re: nvidia-driver crashing kernel on head

On Thursday, July 08, 2010 5:52:10 pm Rene Ladan wrote: > On 08-07-2010 22:09, Doug Barton wrote: > > On Thu, 8 Jul 2010, John Baldwin wrote: > > > >> These freezes and panics are due to the driver using a spin mutex > >> instead of a > >> regular mutex for the per-file descriptor event_mtx. If y

Re: nvidia-driver crashing kernel on head

On 08-07-2010 22:09, Doug Barton wrote: > On Thu, 8 Jul 2010, John Baldwin wrote: > >> These freezes and panics are due to the driver using a spin mutex >> instead of a >> regular mutex for the per-file descriptor event_mtx. If you patch the >> driver >> to change it to be a regular mutex I think

Re: nvidia-driver crashing kernel on head

On Thu, 8 Jul 2010, John Baldwin wrote: These freezes and panics are due to the driver using a spin mutex instead of a regular mutex for the per-file descriptor event_mtx. If you patch the driver to change it to be a regular mutex I think that should fix the problems. Can you give an example?

Re: nvidia-driver crashing kernel on head

On Friday, July 02, 2010 12:55:38 pm David Naylor wrote: > On Friday 02 July 2010 14:57:35 René Ladan wrote: > > 2010/7/2 Yuri Pankov : > > > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote: > > >> Hi, > > >> > > >> I'm not sure this has been reported before but I am experience crashe

Re: nvidia-driver crashing kernel on head

On Friday 02 July 2010 14:57:35 René Ladan wrote: > 2010/7/2 Yuri Pankov : > > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote: > >> Hi, > >> > >> I'm not sure this has been reported before but I am experience crashes > >> with nvidia-driver on -current (cvsup ~day ago). > >> > >> If

Re: nvidia-driver crashing kernel on head

On Fri, Jul 02, 2010 at 02:57:35PM +0200, René Ladan wrote: > 2010/7/2 Yuri Pankov : > > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote: > >> Hi, > >> > >> I'm not sure this has been reported before but I am experience crashes with > >> nvidia-driver on -current (cvsup ~day ago). > >>

Re: nvidia-driver crashing kernel on head

2010/7/2 Yuri Pankov : > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote: >> Hi, >> >> I'm not sure this has been reported before but I am experience crashes with >> nvidia-driver on -current (cvsup ~day ago). >> >> If I remove all the debugging options from the kernel config then it i

Re: nvidia-driver crashing kernel on head

On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote: > Hi, > > I'm not sure this has been reported before but I am experience crashes with > nvidia-driver on -current (cvsup ~day ago). > > If I remove all the debugging options from the kernel config then it is very > usable. > > H

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 14-06-2010 23:31, Christian Zander wrote: > On Mon, Jun 14, 2010 at 02:30:03PM -0700, Rene Ladan wrote: > (...) >>> I've asked the driver author if the calls to vm_page_wire() and >>> vm_page_unwire() can simply be removed but have not heard back yet. >>> >> >> Is there any n

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/14/10 19:14, Doug Barton wrote: Details, I'm running today's -current (r209174) and I've had it up for 4.5 hours already, which is 3 hours longer than I was able to run with anything > 195.22 for months. I've done full "normal" use which includes lots of terminals, tbird, firefox, flash, et

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Mon, Jun 14, 2010 at 2:31 PM, Christian Zander wrote: > On Mon, Jun 14, 2010 at 02:30:03PM -0700, Rene Ladan wrote: > (...) >> > I've asked the driver author if the calls to vm_page_wire() and >> > vm_page_unwire() can simply be removed but have not heard back yet. >> > >> >> >

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Mon, Jun 14, 2010 at 02:30:03PM -0700, Rene Ladan wrote: (...) > > I've asked the driver author if the calls to vm_page_wire() and > > vm_page_unwire() can simply be removed but have not heard back yet. > > > > Is there any news on this? I have updated to the latest current

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 14-06-2010 14:48, John Baldwin wrote: > On Sunday 13 June 2010 11:23:07 pm Doug Barton wrote: >> On 06/13/10 19:09, Alan Cox wrote: >>> On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: >>> On 06/01/10 08:26, John Baldwin wrote: > > I've asked the driver author if the calls

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/14/10 14:30, Rene Ladan wrote: On 14-06-2010 14:48, John Baldwin wrote: On Sunday 13 June 2010 11:23:07 pm Doug Barton wrote: On 06/13/10 19:09, Alan Cox wrote: On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: On 06/01/10 08:26, John Baldwin wrote: I've asked the driver author

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Mon, Jun 14, 2010 at 05:48:55AM -0700, John Baldwin wrote: (...) > > >>> > > >>> I've asked the driver author if the calls to vm_page_wire() and > > >>> vm_page_unwire() can simply be removed but have not heard back yet. > > >>> > > >> > > >> Is there any news on this? I have updated to the late

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sunday 13 June 2010 11:23:07 pm Doug Barton wrote: > On 06/13/10 19:09, Alan Cox wrote: > > On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: > > > >> On 06/01/10 08:26, John Baldwin wrote: > >> > >>> > >>> I've asked the driver author if the calls to vm_page_wire() and > >>> vm_page_unwire()

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/13/10 19:09, Alan Cox wrote: On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: On 06/01/10 08:26, John Baldwin wrote: I've asked the driver author if the calls to vm_page_wire() and vm_page_unwire() can simply be removed but have not heard back yet. Is there any news on this? I h

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: > On 06/01/10 08:26, John Baldwin wrote: > >> >> I've asked the driver author if the calls to vm_page_wire() and >> vm_page_unwire() can simply be removed but have not heard back yet. >> > > Is there any news on this? I have updated to the lates

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/01/10 08:26, John Baldwin wrote: I've asked the driver author if the calls to vm_page_wire() and vm_page_unwire() can simply be removed but have not heard back yet. Is there any news on this? I have updated to the latest current so I'm running the nv driver now, but I'd like to get the

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Saturday 29 May 2010 10:55:41 pm Craig Rodrigues wrote: > On Sun, May 30, 2010 at 02:48:13AM +0800, datastream datastream.freecity wrote: > > > http://www.nvnews.net/vbulletin/showthread.php?t=150719 > > NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. > > Hi, > > I

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sat, May 29, 2010 at 12:31 PM, Garrett Cooper wrote: > On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity > wrote: >> >> On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: >>> >>> On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, May 30, 2010 at 02:48:13AM +0800, datastream datastream.freecity wrote: > > http://www.nvnews.net/vbulletin/showthread.php?t=150719 > NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. Hi, I did the following: - updated r208649 - applied following patch to nvidia-

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity wrote: > > On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: >> >> On 05/26/10 09:51, Kostik Belousov wrote: >>> >>> I did a quick glance over the driver, try this: >>> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.pat

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >> >> I did a quick glance over the driver, try this: >> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch >> I did no

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 5/27/2010 12:12 PM, Kostik Belousov wrote: I think you have stale/wrong includes used by the build. I just checked that driver indeed builds with my patch. vm_page_lock() and vm_page_unlock() are the macros defined in vm/vm_page.h that are present since first Kip commit. As I reported earlie

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Thu, May 27, 2010 at 11:54:27AM -0700, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >I did a quick glance over the driver, try this: > >http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > >I did not even compiled the patched driver. > > cc -pipe -g -g -g -DNV_V

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. cc -pipe -g -g -g -DNV_VERSION_STRING=\"195.36.15\" -D__KERNEL__ -DNVRM -O -Werror -D_KERNEL -DK

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 5/26/2010 2:56 PM, Ryan Stone wrote: I'm by no means an expert in this area, but isn't removing the locking on free a bad thing? Looking at the code, it seems that vm_page_unwire() only requires the page to be locked if it is managed. As it was acquired by contigmalloc, the page should

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

> I'm by no means an expert in this area, but isn't removing the locking > on free a bad thing? Looking at the code, it seems that vm_page_unwire() only requires the page to be locked if it is managed. As it was acquired by contigmalloc, the page should be unmanaged so that should be ok. I am co

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Wed, May 26, 2010 at 12:41:51PM -0500, Alan Cox wrote: > Kostik Belousov wrote: > >On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: > > > >>Garrett Cooper wrote: > >> > >>> Just reporting the fact that nvidia-driver 195.22 is horribly > >>>broken between r206173 and r208486 (my

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Wed, May 26, 2010 at 10:41 AM, Alan Cox wrote: > Kostik Belousov wrote: >> >> On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: >> >>> >>> Garrett Cooper wrote: >>>   Just reporting the fact that nvidia-driver 195.22 is horribly broken between r206173 and r208486 (my mach

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 5/26/2010 9:51 AM, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. Kostik, Thanks for taking a look at this! I sent the following to Alexey recently in regard

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

Kostik Belousov wrote: On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: Garrett Cooper wrote: Just reporting the fact that nvidia-driver 195.22 is horribly broken between r206173 and r208486 (my machine consistency livelocks at X11 startup); the latest driver is still broken

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: > Garrett Cooper wrote: > >Just reporting the fact that nvidia-driver 195.22 is horribly > >broken between r206173 and r208486 (my machine consistency livelocks > >at X11 startup); the latest driver is still broken as well with the > >sa

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

Garrett Cooper wrote: Just reporting the fact that nvidia-driver 195.22 is horribly broken between r206173 and r208486 (my machine consistency livelocks at X11 startup); the latest driver is still broken as well with the same symptoms. I realize that's a huge revision difference, and I'll def

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/2010 12:00 AM, Garrett Cooper wrote: > Just reporting the fact that nvidia-driver 195.22 is horribly > broken between r206173 and r208486 (my machine consistency livelocks > at X11 startup); the latest driver is still broken as well with the > same symptoms. I realize that's a huge rev

Re: Nvidia driver

On Oct 09, "Justin Smith" wrote: > On Wed, 2003-10-08 at 19:53, Andre Guibert de Bruet wrote: > > On Wed, 8 Oct 2003, Justin Smith wrote: > > > If you hook up a serial console, are there any messages that get printed > > out? > > Unfortunately, I have no way of doing this on the machine that has

Re: Nvidia driver

On Wed, 2003-10-08 at 21:46, Daniel O'Connor wrote: > On Thursday 09 October 2003 01:41, Justin Smith wrote: > > > Ahh! > > > Here is a fragment of my loader.conf.. > > > nvidia_load="YES" > > > machdep.disable_mtrrs="1" > > > hw.nvidia.registry.ReqAGPRate="1" > > > > Although this fix alloes me to

Re: Nvidia driver

On Wed, 2003-10-08 at 19:53, Andre Guibert de Bruet wrote: > On Wed, 8 Oct 2003, Justin Smith wrote: > If you hook up a serial console, are there any messages that get printed > out? Unfortunately, I have no way of doing this on the machine that has the nvidia card. I think the "random" crashes

Re: Nvidia driver

On Thursday 09 October 2003 01:41, Justin Smith wrote: > > Ahh! > > Here is a fragment of my loader.conf.. > > nvidia_load="YES" > > machdep.disable_mtrrs="1" > > hw.nvidia.registry.ReqAGPRate="1" > > Although this fix alloes me to start up the nvidia driver, the machine > still reboots when I run

Re: Nvidia driver

On Wed, 8 Oct 2003, Justin Smith wrote: > > > Ahh! > > Here is a fragment of my loader.conf.. > > nvidia_load="YES" > > machdep.disable_mtrrs="1" > > hw.nvidia.registry.ReqAGPRate="1" > > Although this fix alloes me to start up the nvidia driver, the machine > still reboots when I run certain app

Re: Nvidia driver

On Oct 03, "Daniel O'Connor" wrote: > On Friday 03 October 2003 16:34, Mike Hunter wrote: > > How do you turn those down? /boot/loader.conf? I tried saying > > "hw.nvidia.card.rates="2x 1x" but that didn't seem to do anything (I have > > a feeling that putting that in /boot/loader.conf makes no

Re: Nvidia driver

On Friday 03 October 2003 16:34, Mike Hunter wrote: > How do you turn those down? /boot/loader.conf? I tried saying > "hw.nvidia.card.rates="2x 1x" but that didn't seem to do anything (I have > a feeling that putting that in /boot/loader.conf makes no sense...please > consider this a desperate cr

Re: Nvidia driver

On Oct 02, "Daniel O'Connor" wrote: > My wife's computer did this. In the end I turned down all the knobs I > could find (mostly AGP speed stuff). > > It still dies when trying OpenGL though. > hw.nvidia.agp.card.rates: 2x 1x > hw.nvidia.agp.card.fw: not supported > hw.nvidia.agp.card.sba: suppo

Re: Nvidia driver

On Oct 02, "Mworld" wrote: For the record, I tried that and it didn't work for me. > I have had the same problem before and fixed it with WITH_FREEBSD_AGP > > Regards, > Otto. > > - Original Message - > From: "Justin Smith" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday,

Re: Nvidia driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 02 October 2003 10:11 am, Ty Hoeffer wrote: > On Thursday 02 October 2003 00:23, Mike Hunter wrote: > > On Oct 01, "Justin Smith" wrote: > > > MY system: > > > FreeBSD jsmith.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Oct 1 > > > 13:55:0

Re: Nvidia driver

On Thursday 02 October 2003 00:23, Mike Hunter wrote: > On Oct 01, "Justin Smith" wrote: > > MY system: > > FreeBSD jsmith.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Oct 1 > > 13:55:06 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > > i386 > > > > > > Whenever I try to use the nivid

Re: Nvidia driver

I have had the same problem before and fixed it with WITH_FREEBSD_AGP Regards, Otto. - Original Message - From: "Justin Smith" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 02, 2003 10:46 AM Subject: Nvidia driver > MY system: > FreeBSD jsmith.org 5.1-CURRENT FreeB

Re: Nvidia driver

The regular nvidia driver that comes with X windows works fine. Just rename the driver in XF86Config from 'nvidia' to 'nv' and everything (except opengl) works. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: Nvidia driver

On Thursday 02 October 2003 13:53, Mike Hunter wrote: > > Whenever I try to use the nividia driver for X windows, my system > > reboots. Any suggestions? > > ME TOO! My wife's computer did this. In the end I turned down all the knobs I could find (mostly AGP speed stuff). It still dies when tryi

Re: Nvidia driver

On Oct 01, "Justin Smith" wrote: > MY system: > FreeBSD jsmith.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Oct 1 > 13:55:06 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > i386 > > > Whenever I try to use the nividia driver for X windows, my system > reboots. Any suggestions? ME

Re: Nvidia driver

In message <[EMAIL PROTECTED]>, Justin Smith wrote: >MY system: >FreeBSD jsmith.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Oct 1 >13:55:06 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC >i386 > > >Whenever I try to use the nividia driver for X windows, my system >reboots. Any sugges

Re: nvidia-driver still fails on -CURRENT

On Sat, 30 Aug 2003 17:56:43 +0200 "Julian St." <[EMAIL PROTECTED]> wrote: > Hello, > > some people reported strange behavior of nvidia-driver: after starting > X the screen flickers shortly and then displays gibberish in > text-mode. The system is still responsive, as one can login via serial >

Re: nvidia-driver not loading GLX.

Another folloup: I've just re-cvsup today and built world an everythin appears ok so far uname -a: FreeBSD nova 5.1-CURRENT FreeBSD 5.1-CURRENT #4: Mon Aug 4 13:08:34 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 ___ [EMAIL PROTECTED

Re: nvidia-driver not loading GLX.

Just a follow-up. This is what happens when I run on an generic kernel. nvidia0: mem 0xf000-0xf7ff,0xdf00-0xdfff irq 11 at device 0.0 on pci1 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x1

Re: NVidia driver stability?

On 2003-07-13 01:47 +, Evan Dower wrote: > That may have done it. Now that I recompiled nvidia-driver only > WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. > Since something seems to be screwy with my network driver (rtl8139) when > the kernel is compiled without opti

Re: NVidia driver stability?

That may have done it. Now that I recompiled nvidia-driver only WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. Since something seems to be screwy with my network driver (rtl8139) when the kernel is compiled without optimizations, I recompiled with them and so far all is

Re: NVidia driver stability?

On 2003-07-12 21:22 +, Will Saxon wrote: > Well I have to say that about 30min after I wrote in originally, I started having > problems. X locked up, but I could switch around to different vty's and also > ctrl-alt-bksp out of X. However, when I tried to restart X my machine locked up > enti

RE: NVidia driver stability?

know what to think. -Will > -Original Message- > From: Munish Chopra [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 12, 2003 5:57 PM > To: [EMAIL PROTECTED] > Subject: Re: NVidia driver stability? > > > On 2003-07-12 14:46 +, Evan Dower wrote: > >

Re: NVidia driver stability?

Evan Dower wrote: After following all the instructions at http://www.soulwax.net/nvidia/faq.shtml _very_ carefully and compiling nvidia-driver WITH_FREEBSD_AGP, WITH_NVIDIA_HACKS, and with FORCE_AGP_RATE, my system was dramatically slower and substantially _less_ stable. (I had to switch to an

Re: NVidia driver stability?

On 2003-07-12 14:46 +, Evan Dower wrote: > After following all the instructions at > http://www.soulwax.net/nvidia/faq.shtml _very_ carefully and compiling > nvidia-driver WITH_FREEBSD_AGP, WITH_NVIDIA_HACKS, and with FORCE_AGP_RATE, > my system was dramatically slower and substantially _les

RE: NVidia driver stability?

After following all the instructions at http://www.soulwax.net/nvidia/faq.shtml _very_ carefully and compiling nvidia-driver WITH_FREEBSD_AGP, WITH_NVIDIA_HACKS, and with FORCE_AGP_RATE, my system was dramatically slower and substantially _less_ stable. (I had to switch to another computer to w

RE: NVidia driver stability?

I just installed these drivers on my machine, which uses a Geforce4 Ti4200. I had 10 glxgears processes running in the background and was running glxinfo over and over, and while the glxgears processes were not really spinning very fast nothing crashed or anything like that. Machine is running

Re: nvidia-driver database?

On 2003-07-11 20:48 +, Evan Dower wrote: > We've been posting our success stories and problems for a few days now. Has > anybody tried to compile these sorts of things into some sort of database? > Maybe something keeping track of hardware, configuration details, and > performance (success o

Re: NVidia driver stability?

On Friday 11 July 2003 04:09 pm, Mike Porter wrote: > ON the old nvidia driver, I couldn't use GL without crashing, now, it works > fine. Granted I haven't done anything like repeatedly running glxinfo or > anything (is there a need/desire for this?) Just to clarify, repetedly running glxinfo see

Re: NVidia driver stability?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 10 July 2003 07:19 pm, Bruce Cran wrote: > On Thu, Jul 10, 2003 at 04:41:40PM -0700, Evan Dower wrote: > > The new nvidia-driver was unstable for me as well. So much so that I > > deinstalled it so I could get some actual work done. > > I

Re: NVidia driver stability?

> I've been seeing this *exact* same behaviour on a Riva TNT2 for some > time now. I find the new driver to be a /little/ more stable -- i.e. > it's only locked up once on me since I installed it on Monday, as > opposed to locking up three out of the four mornings for the previous > driver. > > I

Re: NVidia driver stability?

Thus spake Evan Dower ([EMAIL PROTECTED]) [10/07/03 19:41]: > The new nvidia-driver was unstable for me as well. So much so that I > deinstalled it so I could get some actual work done. I never was able o get > any specifics about it, as I don't have a serial console set up, and when > it crashe

Re: NVidia driver stability?

Kenneth Culver wrote: I don't know if this is relevant, but the NVidia drivers won't work with libkse or libthr, because it messes with the %gs segment register, which both threading libraries use. The only threading library it currently works with is libc_r. Actually from what I hear that's not

Re: NVidia driver stability?

> I don't know if this is relevant, but the NVidia drivers won't work with > libkse or libthr, because it messes with the %gs segment register, which > both threading libraries use. The only threading library it currently > works with is libc_r. Actually from what I hear that's not accurate. It on

Re: NVidia driver stability?

I don't know if this is relevant, but the NVidia drivers won't work with libkse or libthr, because it messes with the %gs segment register, which both threading libraries use. The only threading library it currently works with is libc_r. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net

Re: NVidia driver stability?

gt; Many thanks, > Evan Dower > Undergraduate, Computer Science > University of Washington > > >From: "Brian Kincaid" <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Re: NVidia driver stability? > >Date: 10 Jul 2003 15:45:41 -0700 > >MI

Re: NVidia driver stability?

t; To: [EMAIL PROTECTED] Subject: Re: NVidia driver stability? Date: 10 Jul 2003 15:45:41 -0700 MIME-Version: 1.0 Received: from mx2.freebsd.org ([216.136.204.119]) by mc3-f9.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 10 Jul 2003 15:46:07 -0700 Received: from hub.freebsd.org (hub.

  1   2   >