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: 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]
Re: Upgrade experience 5.1p10-5.2 Beta
On Sat, 29 Nov 2003, Justin Smith wrote: 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. When we ship 5.2, it will presumably ship with the debugging features disabled in the GENERIC kernel, but enabled in a second DEBUG kernel in the same way we shipped 5.1. However, it won't become the default in the branch version of the kernel configuration until 5-STABLE. If you run into any stability problems, you'll probably want to turn the debugging features back on again to help diagnose them. You might try turning INVARIANTS back on but leaving WITNESS off and see if that gives you enough performance to do what you need to do while still keeping around some debugging features to help in the event of any problem. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Senior Research Scientist, McAfee Research ___ [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
On Saturday 29 November 2003 20:04, Robert Watson wrote: When we ship 5.2, it will presumably ship with the debugging features disabled in the GENERIC kernel, but enabled in a second DEBUG kernel in the same way we shipped 5.1. Quick q on this one: I have several configs now to trace problems with acpi sleeping modes on this Inspiron laptop. On -stable I used to be able to boot /kernel.mychoice. Now everything is stored in /boot/kernel. Does: boot kernel.mychoice now search for: /boot/kernel.mychoice/kernel ? or: /boot/kernel/kernel.mychoice And, does how does makeoptions KERNEL=kernel.mychoice affect this, since sys/ conf/NOTES says: #makeoptionsKERNEL=foo #Build kernel foo and install /foo which seems to be the old way of doing things. -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #1: Sat Nov 29 00:15:33 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ SAREVOK_NOFW_DBG i386 === pgp0.pgp Description: signature
