Re: flash for 9-beta3
Hi Folks, Sorry if this is unrelated but in 9.0-BETA3 about:plugins in chromium and firefox both show both flash and acrobat plugins, but I see these NSPlugin Wrapper errors in the console when I start the browser from the command line. *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection After some google searching it seems it has to do with a compile/runtime time change in the linux syscall interface. I experimented with the changing the linux osrelease sysctl but it hasn't fixed the issue for me. ~ Ali On Mon, Oct 10, 2011 at 8:00 PM, Nenhum_de_Nos math...@eternamente.info wrote: On Mon, October 10, 2011 18:38, Phil Oleson wrote: On 10/10/11 15:30, Nenhum_de_Nos wrote: On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote: On Sat, October 8, 2011 20:03, Doug Barton wrote: On 10/08/2011 14:53, Warren Block wrote: nspluginwrapper needs to be run as the end user. The pkg-message tells them to do that. ops, haven't seen it though. all the ports cleaned by the clean part of the command got on my way :( I did, no good though. FF still says no plugins. is it FF 7 compatible ? matheus I ran into this recently. Though I have not figured out a more correct fix.. add this to your .bashrc: export MOZ_PLUGIN_PATH=/usr/local/lib/browser_plugins/symlinks/gecko19:/usr/local/lib/npapi/symlinks/firefox or.. .cshrc setenv MOZ_PLUGIN_PATH /usr/local/lib/browser_plugins/symlinks/gecko19:/usr/local/lib/npapi/symlinks/firefox and flash will work with the newer firefox. -Phil. thanks Phil, but no good to me :/ Both dirs don't exist, and I tried exporting to browser_plugins dir also ... thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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 ___ 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: x11/nvidia-driver / Compilation has failed
Hmm it seemed to be reading from a random other source tree because I had deleted /usr/src, but /usr/src-8 and /usr/src-9 where present. When I moved src-9 to src the build worked perfectly. I think that took care of the linux issue as well. Sorry for the spam. All these flags you mentioned will come in handy from now on so I can use those to avoid this issue. Thanks, ~ Ali On Wed, Oct 5, 2011 at 5:47 PM, Scot Hetzel swhet...@gmail.com wrote: On Wed, Oct 5, 2011 at 4:43 PM, Ali Mashtizadeh mashtiza...@gmail.com wrote: On Wed, Oct 5, 2011 at 2:27 PM, Scot Hetzel swhet...@gmail.com wrote: On Wed, Oct 5, 2011 at 3:52 PM, Ali Mashtizadeh mashtiza...@gmail.com wrote: Is there any reason I should still be hitting this bug when building on 9-STABLE? With Linux compatibility disabled I can build the driver, but the kernel refuses to load it saying it's incompatible with my kernel version. Was your kernel built from the same version of /usr/src, or have you updated the source (/usr/src) since you last rebuilt the kernel. If you updated the source, then you need to rebuild the kernel from those updated sources (should also build/installworld). Yes, I did that just before. I'll try buildkernel and installkernel again but I know havn't updated the tree. Could there be an issue since I built it from the directory /usr/src-9? Do you also have a /usr/src directory? If you do, then the port is using the wrong kernel source. You'll need to set SRC_BASE to /usr/src-9 when building the port. cd /usr/ports/x11/nvida-driver make deinstall ; make clean ; make install -DSRC_BASE=/usr/src-9 Then you should be able to load the kernel module. Scot -- Ali Mashtizadeh علی مشتی زاده ___ 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: x11/nvidia-driver / Compilation has failed
I did that. In fact I decided to remove all ports and rebuild all my ports based on a snapshot from portsnap that is one day old at this point. ~ Ali On Wed, Oct 5, 2011 at 2:05 PM, Garrett Cooper yaneg...@gmail.com wrote: On Wed, Oct 5, 2011 at 1:52 PM, Ali Mashtizadeh mashtiza...@gmail.com wrote: Is there any reason I should still be hitting this bug when building on 9-STABLE? With Linux compatibility disabled I can build the driver, but the kernel refuses to load it saying it's incompatible with my kernel version. You probably need to rebuild the port..? -Garrett -- Ali Mashtizadeh علی مشتی زاده ___ 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: x11/nvidia-driver / Compilation has failed
Is there any reason I should still be hitting this bug when building on 9-STABLE? With Linux compatibility disabled I can build the driver, but the kernel refuses to load it saying it's incompatible with my kernel version. ~ Ali 2011/8/31 Alexey Dokuchaev da...@freebsd.org: On Mon, Aug 29, 2011 at 02:59:48PM +0200, Olivier Smedts wrote: 2011/8/29 ken k...@tydfam.jp: Could I test your patch for nvidia-driver, too? I cannot find your patch in this mail. I took the patch in : http://lists.freebsd.org/pipermail/freebsd-current/2011-August/026515.html And it worked for me. Should be fixed in the port itself now (also updated to 280.13). ./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 ___ 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: x11/nvidia-driver / Compilation has failed
I ran buildworld and installworld again, but the module still won't load. Also, if I enable linux compatibility the original bug from this email chain is still present. On Wed, Oct 5, 2011 at 2:27 PM, Scot Hetzel swhet...@gmail.com wrote: On Wed, Oct 5, 2011 at 3:52 PM, Ali Mashtizadeh mashtiza...@gmail.com wrote: Is there any reason I should still be hitting this bug when building on 9-STABLE? With Linux compatibility disabled I can build the driver, but the kernel refuses to load it saying it's incompatible with my kernel version. Was your kernel built from the same version of /usr/src, or have you updated the source (/usr/src) since you last rebuilt the kernel. If you updated the source, then you need to rebuild the kernel from those updated sources (should also build/installworld). Scot -- Ali Mashtizadeh ___ 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: Heavy I/O blocks FreeBSD box for several seconds
Maybe someone can setup something like reviewboard [1] for developers to use. This may also help folks who want to keep abreast of the current work in a particular subsystem or get involved into the development process more. At my company we use reviews and it seems to help the catch some bugs and help new engineers ramp up faster. [1] http://www.reviewboard.org/ ~ Ali On Mon, Jul 11, 2011 at 2:48 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi, On Mon, Jul 11, 2011 at 5:14 PM, Andriy Gapon a...@freebsd.org wrote: on 11/07/2011 23:33 Arnaud Lacombe said the following: For the record, I would like to see enforced public review for _every_ patch *before* it is checked in, as a strong rule. gcc system is particularly interesting. But it is not likely to happen in FreeBSD where FreeBSD committers are clearly more free than other at checking-in un-publicly-reviewed stuff (especially _bad_ stuff). This would of course apply even to long-time committers, no matter how it hurt their ego (which I definitively do not care about). Have you just volunteered to review all of the patches that I would like to commit? And are you prepared to take responsibility for quality of your reviews? I am sure that other developers will gladly accept your offer too. _No-one_ can do all the reviews, especially not me (on a purely technical level). ACK must come from subsystem maintainers. Having public review would allow the community review, which is now just not possible today. As about patches from the maintainer, they might be committed without his approval, but still sent for review. If a maintainer goes outside his area, he has to get approval from the other subsystem maintainer. - Arnaud ___ 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 ___ 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
