Nvidia problem fixed in current?
1. Was the problem with the nvidia driver ever fixed? (I reported this more than a month ago --- the kernel nvidia driver only works with parameters set to lower the speed of the interface, and even then failed with some OpenGL programs like OpenUniverse). 2. Can one upgrade to 5.2 beta by cvsupping to current and rebuilding world and kernel? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Upgrade experience 5.1p10->5.2 Beta
First I tried making world and kernel from the cvsup'ed standard supfile. This went OK. Then I did installkernel and installworld (in that order) and the second step crashed with messages that shared libraries were missing. (It's as if it installed some files before installing the shared libraries they needed). I was able to reboot and manually copy over many of the shared libraries from /usr/obj/usr/src/lib to /usr/lib and this got rid of the complaints. Then, I tried running make installworld again, just to be sure everything got installed. This went for about 20 minutes and crashed with gencat command not found. Manually copying this over to /usr/bin (and manually copying all of the shared libraries again, because they would be missing after the crashed make installworld) didn't solve this problem. Odd, since the old system had a gencat command too. Finally, I just burned a CD with the 5.2 beta mini-install (using Slackware Linux...). I ran upgrade and everything seems OK. One problem: my Nvidia GEForce 2 MX card no longer works (of course, I reinstalled the nvidia kernel driver). It has the same problem it had more than a month ago when I was briefly tracking current: attempting to use it reboots the machine. I type 'xinit' and see the power-on self test screen for the motherboard appears. No error messages, etc. I vaguely recall that I solved this the last time by setting parameters in the bootloader that showed the AGP interface down. After doing that, I could run X windows but any OpenGL (OpenUniverse, Celestia) rebooted the machine. Questions: 1. Will the AGP performance be brought up to the level of 5.1p10 before 5.2 is released (so I don't have to slow the AGP interface and can do OpenGL)? 2. Why does the system fail in such an non-robust and uninformative fashion? Why no error messages? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Nvidia problem fixed in current?
Harald Schmalzbauer wrote: On Wednesday 26 November 2003 18:40, Justin Smith wrote: 1. Was the problem with the nvidia driver ever fixed? (I reported this more than a month ago --- the kernel nvidia driver only works with parameters set to lower the speed of the interface, and even then failed with some OpenGL programs like OpenUniverse). The kernel nvidia driver worked fine in 5.1. It only STOPPED working when I upgraded to 5.2 beta (and rebuilt and reinstalled the kernel driver). This is a problem of 5.2 vs 5.1 something changed that stopped it from working. Perhaps some libraries in 5.2 are no longer compatible with the nvidia kernel driver (since it is, fundamentally, a binary program --- one cannot recompile the core of it). Perhaps it's a problem with AGP in 5.2. Slowing down AGP (to 1x) allows the nvidia driver to work but it still reboots the machine whenever I try to do anything that involves OpenGL... Also, it's odd the the thing fails in such a strange manner (rebooting the machine without any error messages). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Upgrade experience 5.1p10->5.2 Beta (cont)
I should add something to what I said before about the nvidia driver problems: Running SIMPLE OpenGL programs (like mesa-demos) works. I've notices that Celestia and OpenUniverse download huge textures to the graphics card. Perhaps it is just the VOLUME of data going through the AGP port that crashes everything. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrade experience 5.1p10->5.2 Beta
Are you running with GENERIC from 5.2-BETA? If so, you may wish to recompile your kernel with WITNESS and INVARIANTS turned off and see if that helps. These debugging features are critical during the development process, but also seriously impact performance and might make the difference you're seeing. This worked like a charm! Everything, including opengl-intensive applications seem to work perfectly. It's amazing only problem was in the debugging code! Thank you. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrade experience 5.1p10->5.2 Beta (update)
This also fixed the scratchiness of the sound (sound had a kind of buzz to it, as though it was being played on a kazoo..) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PCMCIA CDROM drives
Does the generic kernel have drivers for these. I got such a cdrom drive for my Portege 3500 tablet PC and it appeared to be able to boot the 5.2 beta mini-install CD. I wasn't ready to proceed with a complete install, so I shut it off at this point. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Gcc 3.2.2 vs gcc 3.2.3
My system: FreeBSD jsmith.org 5.1-RELEASE-p3 FreeBSD 5.1-RELEASE-p3 #0: Sat Sep 20 14:37:32 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386 I'm running a P4 2.4 Ghz processor with 512meg of ram. I've had the problem of getting signal 11 and signal 4 when I make buildworld and buildkernel. I tested my system with memtest86 (for several hours) and it says everything is OK. Finally I upgraded gcc to 3.2.3 and this seems to have corrected the problems. I hypothesize that gcc 3.2.2 generates invalid machine code under some circumstances. Unfortunately, when I make installworld, it overwrites gcc 3.2.3 with gcc 3.2.2 so I have to reinstall the newer version by hand in order to be able to build the system the next time. I gather that 'current' is somewhat unstable now (although it probably uses a newer version of gcc). Is there a way I can modify my source so make world builds and installs gcc 3.2.3? It can't be as simple as replacing the compiler source in /usr/src with that of gcc 3.2.3 (or is it?). Any suggestions? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Nvidia driver
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? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Nvidia driver
> 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 apps (openuniverse, for instance) and at random times otherwise. Since I need this, I'll have to retreat to stable for a while... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 are actually the result of running screen savers that use OpenGL. The random crashes always happen when I leave the machine alone for a while. When I come back to it, it has rebooted. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 start up the nvidia driver, the machine > > still reboots when I run certain apps (openuniverse, for instance) and > > at random times otherwise. Since I need this, I'll have to retreat to > > stable for a while... > > Ahh, sounds exactly like the status of my wife's machine.. > > Openuniverse sounds.. opengl'ish.. > I would suggest putting back the original X OGL libs so you don't accidentally > blow your feet off :) Openuinivers does use OpenGL, but I can run the Cube game which also uses it. I didn't do much with cube, though --- I just started it up. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
