View Full Version : 1.0-6113 for FreeBSD thread
Note that vm.old_msync is not an environment variable, but a sysctl OID; you will need to set it manually using sysctl vm.old_msync=1 or make an appropriate entry in /etc/sysctl.conf.
Ok, i got it. Writing into sysctl.conf, appears the right value. But the system still crashes, even on my OTHER machine (Cel 300, Riva TNT2 Vanta, Intel 440 LX motherboard, so not a VIA bug). I run bzflag 2 times, after starting 3rd and quitting the screen freezes and 5-10 seconds a reboot occurs. (even old_msyn set to 1)
The VM OID is a partial workaround, please check if the behavior improves with the patches mentioned in the README.
Harvey Pooka
08-23-04, 06:48 PM
Anyone noticing a brief black screen every so often? Rarely, the screen will go black as if resetting itself then return to normal over a two to three second period.
I don't mean to sound like a brown-nose, but I have to say that the driver works perfectly for me - and it's because of your continued FreeBSD support that I'll be *sure* to buy an nvidia card when I upgade my current card...
Cheers,
Jamie
I updated my kernel and world as of 2004/08/14 00:00 UTC and installed, then built the driver, but it locks my machine up solid when starting.
I have a Fx 5200 Go in an Inspiron 8600.
The 4365 drivers work fine.. I am going to try twiddling with AGP settings next..
I have the same problem with quite the same hardware: a DELL Precision M60 with Quadro FX Go700. FreeBSD is current (less than 24 hours old). Also tried fiddling around but no solution. Perhaps an incompatility of the current driver with the laptop design (chipset...). I'm also looking forward to a solution to this problem.
@dulli: are you setup to catch the panic and submit a stack trace to freebsd-gfx-bugs@nvidia.com?
@zander: I could do so tomorrow at the university (where I have a serial null-modem cable). Or is something like http://www.unixguide.net/freebsd/faq/18.13.shtml enough? Could you please tell me (via PM) what I need to send to freebsd-gfx-bugs and how to obtain it, since I've never debugged drivers before. If necessary I can recompile the kernel, use a serial null-modem cable or whatever is needed.
@dulli: a simple stack trace from kdb/ddb, captured via null-modem serial connection, along with appropriately detailed information about your hardware and software configuration would already help a lot.
@zander: I could do so tomorrow at the university (where I have a serial null-modem cable). Or is something like http://www.unixguide.net/freebsd/faq/18.13.shtml enough? Could you please tell me (via PM) what I need to send to freebsd-gfx-bugs and how to obtain it, since I've never debugged drivers before. If necessary I can recompile the kernel, use a serial null-modem cable or whatever is needed.
If you're using a recent -current you will need to compile with KDB as well as DDB to get access to the debugger to get more info (unless you want to copy the stack trace by hand - not fun)
You can also debug via firewire (very neat :))
Just read about debugging over Firewire. That's really cool, accessing a dead OS' core. I will try it this weekend.
lanjoe9
08-27-04, 09:47 PM
I've tried to use this driver in FreeBSD 5.3b1 but xorgconfig never detects the nvidia driver (yet the nvidia_drv.o file is there), and the only devices created are nvidia0 and nvidiactl.
I think it has to do with this:
The /dev/nvidia device files will be
created (unless the system is using devfs) (Found in the README )
So what should I do if the system is running devfs?
Has anyone got it working with FreeBSD 5.3b1?
Hi
Since I installed the new nVidia drivers problems started to appear. I followed the faq and patched the files but no use. My computer simply freezed and reseted.
What can I say it's very frustrating for Freebsd, those things shouldn't happen, right?
Anyway I returned to the previous driver and I hope everything will be ok, I got 200 more frames in glxgears using the old drivers 43.65
I wonder what are your experiences with this new driver
Regards
dehling
08-31-04, 12:42 PM
This driver locks up my system completely, even with AGP disabled. Just like recent versions of the NV opensource driver. Older versions of both drivers worked prefectly :-(
Intel 440BX motherboard
Pentium 2 350Mhz
Diamond viper v770 (TNT 2, 32MB)
Eike.
UNIX4ALL
09-01-04, 03:31 PM
This driver locks up my system completely, even with AGP disabled. Just like recent versions of the NV opensource driver. Older versions of both drivers worked prefectly :-(
Same here, this drivers freezes all my computer randomly (only when Im on X, moving icons, browsing, with gnome-terminal ...) I Tested with FreeBSD AGP, Nvidia AGP and without AGP with SMP enabled, now Im recompiling the kernel without SMP and test.
FreeBSD 5.3-BETA2 (cvsupped of today)
Intel Pentium 4 3,06Ghz HT
Asus P4G8X Deluxe (Intel E7205 Chipset)
Asus V9520 TD 256MB (Only works with this driver version, the older driver canīt initialize the card)
CPUTYPE=i686
CFLAGS & CXXFLAGS = -O -pipe.
I Hope Nvidia will fix these problems soon, a lot of crashes arenīt good for my partitions and it is very frustating.
hishnik
09-03-04, 10:17 AM
Anybody have any luck with AGP on an ASUS k8v deluxe mobo (Athlon 64, but running it 32-bit mode)?? It appears according to the README file, nvidia's internal AGP support doesn't support the via 8385 AGP controller, which is what this mobo has.
I tried recompiling the kernel module the correct way to use FreeBSD's AGP, but then when I try to start X that way, the machine hangs requiring a hard reset.
Kinda frustrating if you ask me.
I think I would have such problem
The same situation.
UNIX4ALL
09-05-04, 09:24 AM
Well, after several days of usage with an UP kernel (not SMP enabled) Its rock solid, nothing nasty, all works without hangs but the problems arise when I build a SMP kernel.
SMP + NVIDIA = Hangs on X.
UP + NVIDIA = Rock Solid.
Well, there are any information, progress or anything about this issue ?
@UNIX4ALL: are you using FreeBSD's AGPGART driver or the builtin NvAGP driver? In the former case, does the SMP problem reproduce with NvAGP? Also, does the behavior change if you build the kernel without optimizations (i.e. with the default flags)?
UNIX4ALL
09-05-04, 12:26 PM
@UNIX4ALL: are you using FreeBSD's AGPGART driver or the builtin NvAGP driver? In the former case, does the SMP problem reproduce with NvAGP? Also, does the behavior change if you build the kernel without optimizations (i.e. with the default flags)?
I use booth, and hang with NvAGP too, moving away make.conf (for defaults optimizations) make the same situation :(.
Post #39 have information about my hardware and software versions.
UNIX4ALL
09-06-04, 08:57 AM
I have discover the fix to this problem:
Patching sys/kern/uipc_socket.c to version 1.212 and recompiling kernel with SMP enabled and debug.mpsafenet=1 debug.mpsafevm=1 works great ! The hangs are related to the problems on poll()/select() application wedge with debug.mpsafenet=1, because the fix isnīt MFC'ed we have this problems, a temporary workaround is patching by hand, however on the next few days the patch will appear on RELENG_5.
The patch is here:
patch (http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c.diff?r1=1.208.2.1&r2=1.212&f=u)
hishnik
09-06-04, 12:22 PM
Anybody have any luck with AGP on an ASUS k8v deluxe mobo (Athlon 64, but running it 32-bit mode)?? It appears according to the README file, nvidia's internal AGP support doesn't support the via 8385 AGP controller, which is what this mobo has.
I tried recompiling the kernel module the correct way to use FreeBSD's AGP, but then when I try to start X that way, the machine hangs requiring a hard reset.
Kinda frustrating if you ask me.
The Same Thing.
I can't use this driver - it's really bad thing i'm think.
Is there any ideas?
There is nothing unusual in log. It ends with
(II) NVIDIA(0): Setting mode "1280x1024"
That's all.
Please help US. :drooling:
hishnik
09-16-04, 02:13 PM
---
@hishnik: you'll need to provide more information about your hardware/sofware configuration. Without it, we can only guess: have you tried disabling ACPI?
Oberonald
09-27-04, 02:49 PM
Just a short question....
Is there a way (for a newby so please dont make it too complex) to get FreeBSD 5.2.1. to work on a AMD64 with a NVIDIA Geforce FX-5500 card? I've been busy for day's, surfing the Internet, trying to figure things out only to reach the conclusion that it's probably "impossible". There simply are no NVIDIA drivers to be used on a AMD64 FreeBSD machine.
Am I correct? Or is there there still hope ;-))
Heya!
Of course can you use FreeBSD 5.2.1 with your NVidia card on amd64. The only drawback is, that the available drivers (i tested vesa and nv from X.org 6.8) are *not* hardware-accelerated, which means you wouldn't be able to play p.e. quake3 with an acceptable framerate. My suggestion is to wait for FreeBSD 5.3, which will "hit stores" on about 10th October 2004. I think when 5.3's out, NVidia will released amd64 drivers soon.
(If you think you can do it, try cvsupping the RELENG_5 branch which will allow you to use a Beta version of 5.3. These betas are already in a nearly-stable state imho; use it if you want to have a look at 5.3)
regards,
kpanic
muythaibxr
10-05-04, 02:49 PM
Hey zander, I have a similar config to hishnik.
Here is what happens:
I can set it to use NvAgp, or no AGP, and either way the sysctls and the xorg.log file both don't have anything about AGP getting enabled, other than the fact that the NvAgp option was set to use nvidia's internal agp support. Other than the fact that AGP isn't getting enabled, Everything works fine. Just a little slower than I'd expect for a couple of games (significantly slower than windows, but still accelerated).
When I try to use FreeBSD's AGP, and set all the options to match, I can see in the log (upon reboot) that AGP was enabled in the xorg.log, but the machine hangs hard... I can't even ssh to the machine to reboot it. I tried using FreeBSD's AGP with acpi and apic disabled, and with just acpi, and with just apic, and no matter what the result is the same.
I've just been running without AGP for the time being, but I think that the driver just doesn't have support for my AGP chipset yet.
I have a GeForce FX 5900, Athlon 64 3200+ (running in FreeBSD/i386, 32-bit), 1GB of Corsair RAM, asus k8v deluxe mobo. This uses the Via k8t800 chipset I believe (I might have that wrong, but it's the via chipset that's meant for socket 754 athlon 64's).
Anyway, any idea if the driver will support this chipset on its next release?
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.