Re: Re Regression: Playing QT files from mplayer stopped workingin 5.1
I have mplayer in 4.8-STABLE and 5.1-RC1. What specifically would you like? On 9 Jun, Alexander Leidinger wrote: > On Mon, 9 Jun 2003 14:33:11 +0200 > [EMAIL PROTECTED] (Ted Lindgreen) wrote: > >> I've tested it as cleanly as possible (make update, apply patch, >> make world/kernel, and portupgrade -f multimedia/mplayer). >> Is works fine and I haven't found any complications. >> I think it's save to commit. > > Someone should still look into mplayer, I think there's something wrong > with it. > > Bye, > Alexander. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i386-undermydesk-freebsd?
What does "i386-undermydesk-freebsd" refer to? What is it used for? Is there an "i386-inthedrawer-freebsd", or "i386-intheXbox-freebsd"? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 06/05/2003 breaks nvidia driver
Thanks for the suggestion about recompiling the nvidia driver, but I do after each kernel compile and install, so that isn't the answer, though not a bad idea. Recompiles of both the Linux-nvidia-port and the standalone-nvidia driver failed, so I am in the process, now, of backing out of everything that was updated. Are there any suggestions for better diagnosing of the problem? On 5 Jun, Scott Long wrote: > [EMAIL PROTECTED] wrote: >> I am not on my 5.1-BETA2 system right now, so I don't have any useful >> details, but after CVSuping /usr/src early 05/06/2003 (after midnight), then >> build world and recompiling and installing "my" kernel, the nvidia driver >> "checks out" when X is loaded with a failure to initialize the driver. >> >> The system in question has run 5.1-BETA1 and earlier 5.1-BETA2 code before >> without any nvidia driver problem. >> >> In the meantime, any suggestions on how to provide useful information, other >> than just the XFree86.0.log file, would be helpful. I have used both of the >> "native" nvidia driver and the ports-linux version (once), but tend to stay >> with the "native" version (1.0-3203). > > There was yet another ABI change recently that affected the nvidia > driver. The only thing to do is just recompile that driver. > > Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup 06/05/2003 breaks nvidia driver
If you started X (by itself) and the screen flickered on and off, then I would suspect that it is being told to use a video mode that your card, or more likely - monitor, won't support. If that is true, then you could be in danger of damaging your monitor. 1) Got all available documentation available (online and from supplied manuals) on my flat-panel monitor and video card with respect to video modes, including horizontal and vertical frequencies 2) Manually modified a previously existing (FBSD-4.8) XF86Config file to include the proper frequencies and raw modelines (without all of the frequency information) for the identified video modes from the documentation 3) Downloaded the FreeBSD nvidia driver from nvidia.com 4) Compiled and installed the nvidia driver 5) Included nvidia enable in /boot/loader.conf 6) Started X by itself to make sure that it was stable with the default mode that I had chosen in the XF86Config file (ie; the basic/default X window was steady) 7) Started X + Gnome and used xvidtune to fine tune the modelines and choose which to use 8) Found some reference to two settable sysctl variables (hw.nvidiaAGP..) and "enabled" them, though they don't appear to be necessary for normal operation 9) Found some reference (nvidia MANual page?) about three AGP "modes" definable in the XF86Config file (chooses between OS AGP support versus onboard AGP support), though they don't seem to be necessary 10) Recompile nvidia driver after every 5.1 kernel recompile Worked with 5.1-BETA1, and 5.1-BETA2 (up until the last source update, May 28th or so). Works with 5.1-RC1. I did not try 5.0. On 6 Jun, Matt wrote: > > none said: >> After having installed 5.1-RC1, the nvidia driver, and named, are >> back in full operation. Yeah! > > Can I just ask you a question abuot this? What are the steps you went > through to get this driver to work? > > I tried this on 5.0-CURRENT a while back and the below happened: > > I have a nvidia geforce 4 MX 220. I tried installing > /usr/ports/x11/nvidia-driver which compiled fine. I changed the XF86Config > to use driver "nvidia", kldload'd the module which loaded fine and > detected my video card. However when I started X the screen flickered on > and off several times and then the pc rebooted without any panic or > anything. > > I tried adding agp options etc and same thing happened. > > What have you done to get it to work? I'm on 5.1-RELEASE now but have not > tried it again yet. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup 06/05/2003 breaks nvidia driver
I am not on my 5.1-BETA2 system right now, so I don't have any useful details, but after CVSuping /usr/src early 05/06/2003 (after midnight), then build world and recompiling and installing "my" kernel, the nvidia driver "checks out" when X is loaded with a failure to initialize the driver. The system in question has run 5.1-BETA1 and earlier 5.1-BETA2 code before without any nvidia driver problem. In the meantime, any suggestions on how to provide useful information, other than just the XFree86.0.log file, would be helpful. I have used both of the "native" nvidia driver and the ports-linux version (once), but tend to stay with the "native" version (1.0-3203). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.1-BETA2 Syslog/Named problems
5.1-BETA2 (05/24) install (cvsup 05/28 updated) is experiencing syslog/named problems not encountered under 5.1-BETA1. Named is running as it was in 5.1-BETA1 and BETA2 before 05/28 cvsup. An NSSWITCH.CONF file was added to see if that would make any difference, but it did not. Snippet from boot messages: Starting syslogd. May 29 00:33:40 syslogd: bind: Can't assign requested address syslogd: child pid 140 exited with return code 1 Starting named. opensocket_f: bind([0.0.0.0].0): Can't assign requested address ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.1-BETA2 pkg_info wierdness
Instead of simple text lines, pkg_info is returning what looks like "escaped words" after clean install of 5.1-BETA2: pkg_info|more Hermes-1.3.2Fast\ pixel\ formats\ conversion\ libraryMesa-3.4.2_2 A\ graphics\ library\ similar\ to\ SGI\'s\ OpenGLORBit-0.5.17 High-performance\ CORBA\ ORB\ with\ support\ for\ the\ C\ l ORBit2-2.6.1_1 High-performance\ CORBA\ ORB\ with\ support\ for\ the\ C\ l XFree86-FontServer-4.3.0_1 XFree86-4\ font\ serverXFree86-NestServer-4.3.0_1 XFree86-4\ nested\ X\ serverXFree86-PrintServer-4.3.0 XFree86-4\ print\ serverXFree86-Server-4.3.0_8 XFree86-4\ X\ server\ and\ related\ programsXFree86-VirtualFramebufferServer-4.3.0_1 XFree86-4\ virtual\ framebuffer\ serverXFree86-clients-4.3.0_2 XFree86-4\ client\ programs\ and\ related\ filesXFree86-documents-4.3.0 XFree86-4\ documentationXFree86-font100dpi-4.3.0 XFree86-4\ bitmap\ 100\ dpi\ fontsXFree86-font75dpi-4.3.0 XFree86-4\ bitmap\ 75\ dpi\ fontsXFree86-fontCyrillic-4.3.0 XFree86-4\ Cyrillic\ fontsXFree86-fontDefaultBitmaps-4.3.0 XFree86-4\ default\ bitmap\ fontsXFree86-fontEncodings-4.3.0 XFree86-4\ font\ encoding\ filesXFree86-fontScalable-4.3.0 XFree86-4\ scalable\ fontsXFree86-libraries-4.3.0_4 XFree86-4\ libraries\ and\ headersXFree86-manuals-4.3.0 XFree86-4\ man\ pagesXft-2.1.2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
