Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, Oct 17, 2010 at 6:16 PM, Doug Barton do...@freebsd.org wrote: On 10/17/2010 4:49 PM, Rob Farmer wrote: I am running 256.53 on amd64 current (r213747). I don't use anything linux (the module isn't loaded) and built the driver with all options off except ACPI_PM. My custom kernel does not have device agp. Hmm. I had all the options off except linux. I'll try with your combination and see if that improves things. I've given up on linux emulation support since 256.3x as it was the factor that was causing lockups on my two machines. Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, 17 Oct 2010, Garrett Cooper wrote: On Sun, Oct 17, 2010 at 6:16 PM, Doug Barton do...@freebsd.org wrote: On 10/17/2010 4:49 PM, Rob Farmer wrote: I am running 256.53 on amd64 current (r213747). I don't use anything linux (the module isn't loaded) and built the driver with all options off except ACPI_PM. My custom kernel does not have device agp. Hmm. I had all the options off except linux. I'll try with your combination and see if that improves things. I've given up on linux emulation support since 256.3x as it was the factor that was causing lockups on my two machines. Thanks. I tried again without linux support, no change, it still froze up. I suppose I can try again tomorrow without any of the options selected. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On Mon, Oct 18, 2010 at 8:54 AM, Doug Barton do...@freebsd.org wrote: On Sun, 17 Oct 2010, Garrett Cooper wrote: On Sun, Oct 17, 2010 at 6:16 PM, Doug Barton do...@freebsd.org wrote: On 10/17/2010 4:49 PM, Rob Farmer wrote: I am running 256.53 on amd64 current (r213747). I don't use anything linux (the module isn't loaded) and built the driver with all options off except ACPI_PM. My custom kernel does not have device agp. Hmm. I had all the options off except linux. I'll try with your combination and see if that improves things. I've given up on linux emulation support since 256.3x as it was the factor that was causing lockups on my two machines. Thanks. I tried again without linux support, no change, it still froze up. I suppose I can try again tomorrow without any of the options selected. Doug For what it's worth, the newest nvidia driver in ports (256.53) reliably freezes both my 8-STABLE and 9-CURRENT machine dead within minutes (amd64 , KDE4 both with and without compositing, Geforce GT240 cards. The mouse stops moving, no keyboard input does anything, it doesn't answer on the network.) I haven't had time to look at it, so I'm using the nv driver for now. -- Daniel Nebdal ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Is nvidia-driver 256.53 expected to work on -current?
Y'all will probably recall that I had a lot of problems with the nvidia-driver, and video generally (esp. flash) on i386 -current. Well I haven't had any problems recently because I haven't been using FreeBSD. :) But I have things I need to catch up on, so here's what I did: 1. Bought a new hard drive, and installed a snapshot of amd64 -current (this was actually done a while ago). 2. Yesterday I started configuring stuff, updated my source and ports trees, rebuilt the world, customized the kernel, etc. 3. With a newly up to date system I built the latest version of the nvidia-driver port, and started using it. My experience with it has been exactly the same as older versions of the port on previous versions of i386 -current. Sometimes it runs fine for a while, but when I exit the window manager (openbox) the system hangs and I never get back to the command prompt. (I'm using startx to try and minimize the number of variables.) Sometimes it will work fine for an hour, maybe two, then the whole thing just hangs. All the stuff is displayed on the screen, but the mouse won't move, I can't zap X, or even switch to the console. I have to power off. This is particularly frustrating because I haven't even loaded flash (or for that matter firefox) yet. Windows and linux (ubuntu, with the nvidia driver) work great on this same hardware, so I'm pretty thoroughly convinced that the problem is with freebsd/current somewhere. In addition to the -current partition I also installed amd64 8.1-RELEASE so I'll give that a go next, but I wanted to ask here first if anyone else was having problems on -current. Doug -- Breadth of IT experience, and| Nothin' ever doesn't change, depth of knowledge in the DNS. | but nothin' changes much. Yours for the right price. :) | -- OK Go http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
Doug Barton wrote: Y'all will probably recall that I had a lot of problems with the nvidia-driver, and video generally (esp. flash) on i386 -current. Well I haven't had any problems recently because I haven't been using FreeBSD. :) But I have things I need to catch up on, so here's what I did: 1. Bought a new hard drive, and installed a snapshot of amd64 -current (this was actually done a while ago). 2. Yesterday I started configuring stuff, updated my source and ports trees, rebuilt the world, customized the kernel, etc. 3. With a newly up to date system I built the latest version of the nvidia-driver port, and started using it. My experience with it has been exactly the same as older versions of the port on previous versions of i386 -current. Sometimes it runs fine for a while, but whe n I exit the window manager (openbox) the system hangs and I never get back to the command prompt. (I'm using startx to try and minimize the number of variables.) Sometimes it will work fine for an hour, maybe two, then the whole thing just hangs. All the stuff is displayed on the screen, but the mouse won't move, I can't zap X, or even switch to the console. I have to power off. This is particularly frustrating because I haven't even loaded flash (or for that matter firefox) yet. Windows and linux (ubuntu, with the nvidia driver) work great on this same hardware, so I'm pretty thoroughly convinced that the problem is with freebsd/current somewhere. In addition to the -current partition I also installed amd64 8.1-RELEASE so I'll give that a go next, but I wanted to ask here first if anyone else was having problems on -current. Doug I am currently running the Nvidia 195 driver on amd64 9 - current from the ports tree. It works without problems. When I tried to compile the 256 driver, it would not compile and said that it was not meant to work with 9 - current. Hope this helps. Ralph Ellis ralphell...@netscape.ca ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun Oct 17 10, Ralph Ellis wrote: Doug Barton wrote: Y'all will probably recall that I had a lot of problems with the nvidia-driver, and video generally (esp. flash) on i386 -current. Well I haven't had any problems recently because I haven't been using FreeBSD. :) But I have things I need to catch up on, so here's what I did: 1. Bought a new hard drive, and installed a snapshot of amd64 -current (this was actually done a while ago). 2. Yesterday I started configuring stuff, updated my source and ports trees, rebuilt the world, customized the kernel, etc. 3. With a newly up to date system I built the latest version of the nvidia-driver port, and started using it. My experience with it has been exactly the same as older versions of the port on previous versions of i386 -current. Sometimes it runs fine for a while, but whe n I exit the window manager (openbox) the system hangs and I never get back to the command prompt. (I'm using startx to try and minimize the number of variables.) Sometimes it will work fine for an hour, maybe two, then the whole thing just hangs. All the stuff is displayed on the screen, but the mouse won't move, I can't zap X, or even switch to the console. I have to power off. This is particularly frustrating because I haven't even loaded flash (or for that matter firefox) yet. Windows and linux (ubuntu, with the nvidia driver) work great on this same hardware, so I'm pretty thoroughly convinced that the problem is with freebsd/current somewhere. In addition to the -current partition I also installed amd64 8.1-RELEASE so I'll give that a go next, but I wanted to ask here first if anyone else was having problems on -current. Doug I am currently running the Nvidia 195 driver on amd64 9 - current from the ports tree. It works without problems. When I tried to compile the 256 driver, it would not compile and said that it was not meant to work with 9 - current. i'm running 256.52 on HEAD (amd64) without any issues. the 260.X drivers all freze my computer when i exit X. it's quite easy to work around the isse that the nvidia drivers fail to compile on HEAD. simply change the line #if __FreeBSD_version = 90 in src/nv-freebsd.h to #if __FreeBSD_version = 100. cheers. alex Hope this helps. Ralph Ellis ralphell...@netscape.ca -- a13x ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, Oct 17, 2010 at 15:55, Doug Barton do...@freebsd.org wrote: Windows and linux (ubuntu, with the nvidia driver) work great on this same hardware, so I'm pretty thoroughly convinced that the problem is with freebsd/current somewhere. In addition to the -current partition I also installed amd64 8.1-RELEASE so I'll give that a go next, but I wanted to ask here first if anyone else was having problems on -current. I am running 256.53 on amd64 current (r213747). I don't use anything linux (the module isn't loaded) and built the driver with all options off except ACPI_PM. My custom kernel does not have device agp. I use XFCE 4, don't really run anything graphically intense, and shutdown at night. I haven't had any problems, but IIRC from your past threads, the issues sort of build over time so I simply may not be aggravating the problem enough. The system is a HP Pavillion dv6405us laptop with a GeForce Go 6150. This is a pretty crappy card, even in Windows (the whole system was $500 3 years ago - it was one of those computers that supposedly was Vista Ready but could barely boot it), so I doubt I am gaining much over vesa though. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, Oct 17, 2010 at 16:18, Ralph Ellis ralphell...@netscape.ca wrote: I am currently running the Nvidia 195 driver on amd64 9 - current from the ports tree. It works without problems. When I tried to compile the 256 driver, it would not compile and said that it was not meant to work with 9 - current. Some necessary support was removed recently, but it has be re-added. See r213739. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On 18/10/2010 10:18, Ralph Ellis wrote: Doug Barton wrote: Y'all will probably recall that I had a lot of problems with the nvidia-driver, and video generally (esp. flash) on i386 -current. Well I haven't had any problems recently because I haven't been using FreeBSD. :) But I have things I need to catch up on, so here's what I did: 1. Bought a new hard drive, and installed a snapshot of amd64 -current (this was actually done a while ago). 2. Yesterday I started configuring stuff, updated my source and ports trees, rebuilt the world, customized the kernel, etc. 3. With a newly up to date system I built the latest version of the nvidia-driver port, and started using it. My experience with it has been exactly the same as older versions of the port on previous versions of i386 -current. Sometimes it runs fine for a while, but whe n I exit the window manager (openbox) the system hangs and I never get back to the command prompt. (I'm using startx to try and minimize the number of variables.) Sometimes it will work fine for an hour, maybe two, then the whole thing just hangs. All the stuff is displayed on the screen, but the mouse won't move, I can't zap X, or even switch to the console. I have to power off. This is particularly frustrating because I haven't even loaded flash (or for that matter firefox) yet. Windows and linux (ubuntu, with the nvidia driver) work great on this same hardware, so I'm pretty thoroughly convinced that the problem is with freebsd/current somewhere. In addition to the -current partition I also installed amd64 8.1-RELEASE so I'll give that a go next, but I wanted to ask here first if anyone else was having problems on -current. Doug I am currently running the Nvidia 195 driver on amd64 9 - current from the ports tree. It works without problems. When I tried to compile the 256 driver, it would not compile and said that it was not meant to work with 9 - current. Hope this helps. Ralph Ellis ralphell...@netscape.ca I have not had any trouble with the new Nvidia drivers at all - but I'm running i386, so it might be an amd64 issue. No compilation issues at all, no problems running, switching to VT etc. (and yes, I had the same problems as Doug a while ago) Kernel and world are not from today, but fairly recent though: FreeBSD 9.0-CURRENT #48 r213491M: Thu Oct 7 See: (--) PCI:*(0:1:0:0) 10de:06e4:1458:349c nVidia Corporation G98 [GeForce 8400 GS] rev 161, Mem @ 0xf200/16777216, 0xe000/268435456, 0xf000/33554432, I/O @ 0x2100/128, BIOS @ 0x/65536 (II) extmod will be loaded by default. (II) dbe will be loaded by default. (II) glx will be loaded. This was enabled by default and also specified in the config file. (II) record will be loaded by default. (II) dri will be loaded by default. (II) dri2 will be loaded by default. (II) LoadModule: glx (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=NVIDIA Corporation compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Server Extension (II) NVIDIA GLX Module 256.53 Fri Aug 27 20:49:59 PDT 2010 (II) Loading extension GLX (II) LoadModule: extmod (II) Loading /usr/local/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/local/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: record (II) Loading /usr/local/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: dri (II) Loading /usr/local/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading /usr/local/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: nvidia (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so (II) Module nvidia: vendor=NVIDIA Corporation compiled
Re: Is nvidia-driver 256.53 expected to work on -current?
On 10/17/2010 4:49 PM, Rob Farmer wrote: I am running 256.53 on amd64 current (r213747). I don't use anything linux (the module isn't loaded) and built the driver with all options off except ACPI_PM. My custom kernel does not have device agp. Hmm. I had all the options off except linux. I'll try with your combination and see if that improves things. Thanks, Doug -- Breadth of IT experience, and| Nothin' ever doesn't change, depth of knowledge in the DNS. | but nothin' changes much. Yours for the right price. :) | -- OK Go http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, Oct 17, 2010 at 11:32:00PM +, Alexander Best wrote: i'm running 256.52 on HEAD (amd64) without any issues. the 260.X drivers all freze my computer when i exit X. it's quite easy to work around the isse that the nvidia drivers fail to compile on HEAD. simply change the line #if __FreeBSD_version = 90 in src/nv-freebsd.h to #if __FreeBSD_version = 100. Or install from ports, which also patch the driver to support -CURRENT. ./danfe ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
