tag:old.nabble.com,2006:forum-6578Nabble - freebsd-emulation2009-12-22T15:47:30ZDevelopment of Emulators of other operating systemstag:old.nabble.com,2006:post-26896080Re: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)2009-12-22T15:47:30Z2009-12-22T15:47:30ZLeslie Jensen<br><div class='shrinkable-quote'><br>>
<br>> Sorry for my rush on the previous post. Here is a better script:
<br>> ----------------------------------------------------------
<br>> #!/bin/sh
<br>> #
<br>> # $FreeBSD: src/etc/rc.d/vbox,v 1.0 2009/12/22 20:20:06 mlobo Exp $
<br>> #
<br>>
<br>> # PROVIDE: vbox
<br>> # REQUIRE: LOGIN
<br>> # KEYWORD: nojail
<br>>
<br>> . /etc/rc.subr
<br>>
<br>> name="vbox"
<br>> start_cmd="${name}_start"
<br>> stop_cmd=":"
<br>>
<br>> vboxm_start()
<br>> {
<br>> /sbin/kldload vboxnetflt
<br>> /sbin/kldload vboxnetadp
<br>> }
<br>>
<br>> vbox_start()
<br>> {
<br>> if checkyesno vbox_enable; then
<br>> echo ' VirtualBox modules'
<br>> vboxm_start
<br>> fi
<br>> }
<br>>
<br>> load_rc_config $name
<br>> run_rc_command "$1"
<br>>
<br>> -------------------------------------------------------
<br>>
<br>> You have to place vbox_enable="YES" on /etc/rc.conf
</div><br>Thank you Mario.
<br><br>This works fine, module loaded and VirtualBox VM starts with no error :-)
<br><br>/Les
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26896080&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26896080&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26896052Re: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script) CORRECTION !2009-12-22T15:43:55Z2009-12-22T15:43:55ZMario Lobo-5<br>A small correction:
<br><br>take out the "-" lines and add the "+" line
<br><br>It should work now !
<br><br>----------------------------------------------------------
<br>#!/bin/sh
<br>#
<br># $FreeBSD: src/etc/rc.d/vbox,v 1.0 2009/12/22 20:20:06 mlobo Exp $
<br>#
<br><br># PROVIDE: vbox
<br>- # REQUIRE: LOGIN
<br>- # KEYWORD: nojail
<br>+ # BEFORE: LOGIN
<br><br>. /etc/rc.subr
<br><br>name="vbox"
<br>start_cmd="${name}_start"
<br>stop_cmd=":"
<br><br>vboxm_start()
<br>{
<br> /sbin/kldload vboxnetflt
<br> /sbin/kldload vboxnetadp
<br>}
<br><br>vbox_start()
<br>{
<br> if checkyesno vbox_enable; then
<br> echo ' VirtualBox modules'
<br> vboxm_start
<br> fi
<br>}
<br><br>load_rc_config $name
<br>run_rc_command "$1"
<br><br>-------------------------------------------------------
<br><br>Place vbox_enable="YES" on /etc/rc.conf
<br><br>--
<br>Mario Lobo
<br><a href="http://www.mallavoodoo.com.br" target="_top" rel="nofollow">http://www.mallavoodoo.com.br</a><br>FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE)
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26896052&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26896052&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895921Re: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)2009-12-22T15:25:19Z2009-12-22T15:25:19ZMario Lobo-5On Tuesday 22 December 2009 20:20:40 Leslie Jensen wrote:
<div class='shrinkable-quote'><br>> > This is a known problem for a while but I think it's almost microscopic.
<br>> >
<br>> >
<br>> > Just place the following script in /usr/local/etc/rc.d/vboxkos
<br>> >
<br>> > -----------------------------------
<br>> > #!/bin/sh
<br>> > echo ' VirtualBox'
<br>> > /sbin/kldload vboxnetflt
<br>> > /sbin/kldload vboxnetadp<- optional
<br>> > ------------------------------------
<br>> >
<br>> > and take vboxnetflt_load="YES" out of loader.conf.
<br>> > Load only vboxdrv.ko there !
<br>> >
<br>> > The modules will be loaded late enough and everything will work.
<br>>
<br>> I placed the vboxkos script as you described, set the same owner and
<br>> group and rights as the files already present. Unfortunately the
<br>> vboxnetflt module did not get loaded.
<br>>
<br>> /Les
<br>>
</div><br>Sorry for my rush on the previous post. Here is a better script:
<br>----------------------------------------------------------
<br>#!/bin/sh
<br>#
<br># $FreeBSD: src/etc/rc.d/vbox,v 1.0 2009/12/22 20:20:06 mlobo Exp $
<br>#
<br><br># PROVIDE: vbox
<br># REQUIRE: LOGIN
<br># KEYWORD: nojail
<br><br>. /etc/rc.subr
<br><br>name="vbox"
<br>start_cmd="${name}_start"
<br>stop_cmd=":"
<br><br>vboxm_start()
<br>{
<br> /sbin/kldload vboxnetflt
<br> /sbin/kldload vboxnetadp
<br>}
<br><br>vbox_start()
<br>{
<br> if checkyesno vbox_enable; then
<br> echo ' VirtualBox modules'
<br> vboxm_start
<br> fi
<br>}
<br><br>load_rc_config $name
<br>run_rc_command "$1"
<br><br>-------------------------------------------------------
<br><br>You have to place vbox_enable="YES" on /etc/rc.conf
<br>--
<br>Mario Lobo
<br><a href="http://www.mallavoodoo.com.br" target="_top" rel="nofollow">http://www.mallavoodoo.com.br</a><br>FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE)
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895921&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895921&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895862Re: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)2009-12-22T15:20:40Z2009-12-22T15:20:40ZLeslie Jensen<br><div class='shrinkable-quote'><br>> This is a known problem for a while but I think it's almost microscopic.
<br>>
<br>>
<br>> Just place the following script in /usr/local/etc/rc.d/vboxkos
<br>>
<br>> -----------------------------------
<br>> #!/bin/sh
<br>> echo ' VirtualBox'
<br>> /sbin/kldload vboxnetflt
<br>> /sbin/kldload vboxnetadp<- optional
<br>> ------------------------------------
<br>>
<br>> and take vboxnetflt_load="YES" out of loader.conf.
<br>> Load only vboxdrv.ko there !
<br>>
<br>> The modules will be loaded late enough and everything will work.
</div><br>I placed the vboxkos script as you described, set the same owner and
<br>group and rights as the files already present. Unfortunately the
<br>vboxnetflt module did not get loaded.
<br><br>/Les
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895862&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895862&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895681Re: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)2009-12-22T15:01:08Z2009-12-22T15:01:08ZMario Lobo-5On Tuesday 22 December 2009 19:48:27 Leslie Jensen wrote:
<div class='shrinkable-quote'><br>> On 2009-12-22 23:17, Paul Wootton wrote:
<br>> > I too get an error on starting a VM if I try to load the modules from
<br>> > /boot/loader.conf. For me, the loading of vboxnetflt does not seem to
<br>> > work correctly. I dont load vboxnetadp, so I cant comment on that.
<br>> >
<br>> > /boot/loader.conf
<br>> > zfs_load="YES"
<br>> > vboxdrv_load="YES"
<br>> > vboxnetflt_load="YES"
<br>> >
<br>> >
<br>> > If I try to start a VM that is using the "Bridged Ethernet" adapter, the
<br>> > error I get is
<br>> >
<br>> > "Failed to start the virtual machine Win Vista
<br>> >
<br>> > Failed to open/create the internal network 'HostInterfaceNetworking-re0'
<br>> > (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br>> >
<br>> > Failed to attach the network LUN
<br>> > (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br>> >
<br>> > Unknown eror creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br>> >
<br>> > Details
<br>> > Result Code: NS_ERROR_FAILURE (0x80004005)
<br>> > Component: Console
<br>> > Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}"
<br>> >
<br>> >
<br>> > I know the module got loaded.
<br>> > [paul@demophon /usr/home/paul]$ kldstat
<br>> > Id Refs Address Size Name
<br>> > 1 25 0xffffffff80100000 e7c540 kernel
<br>> > 2 1 0xffffffff80f7d000 18a788 zfs.ko
<br>> > 3 2 0xffffffff81108000 3778 opensolaris.ko
<br>> > 4 2 0xffffffff8110d000 41e88 vboxdrv.ko
<br>> > 5 1 0xffffffff8114f000 6960 vboxnetflt.ko
<br>> > 6 1 0xffffffff81223000 38fc linprocfs.ko
<br>> > 7 1 0xffffffff81227000 1bcc4 linux.ko
<br>> >
<br>> > If I then do a kldunload vboxnetflt followed by kldload vboxnetflt, I
<br>> > can now start and stop my VMs to my heart's content.
<br>> > Im using 9 CURRENT and I only started using /boot/loader.conf for the
<br>> > vbox modules about a month back. The vboxnetflt module has never worked
<br>> > correctly for me this way
<br>> >
<br>> > Paul
<br>>
<br>> Thanks for starting the new tread :-)
<br>>
<br>> This is exactly the same problem I'm having.
<br>>
<br>> I'm on 8.0-RELEASE
<br>>
<br>> /Les
<br>>
<br>> _______________________________________________
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895681&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br>> <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>> To unsubscribe, send any mail to
<br>> "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895681&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>>
</div><br>This is a known problem for a while but I think it's almost microscopic.
<br><br><br>Just place the following script in /usr/local/etc/rc.d/vboxkos
<br><br>-----------------------------------
<br>#!/bin/sh
<br>echo ' VirtualBox'
<br>/sbin/kldload vboxnetflt
<br>/sbin/kldload vboxnetadp <- optional
<br>------------------------------------
<br><br>and take vboxnetflt_load="YES" out of loader.conf.
<br>Load only vboxdrv.ko there !
<br><br>The modules will be loaded late enough and everything will work.
<br>--
<br>Mario Lobo
<br><a href="http://www.mallavoodoo.com.br" target="_top" rel="nofollow">http://www.mallavoodoo.com.br</a><br>FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE)
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895681&i=2" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895681&i=3" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895507Re: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)2009-12-22T14:48:27Z2009-12-22T14:48:27ZLeslie Jensen<br>On 2009-12-22 23:17, Paul Wootton wrote:
<br><div class='shrinkable-quote'><br>> I too get an error on starting a VM if I try to load the modules from
<br>> /boot/loader.conf. For me, the loading of vboxnetflt does not seem to
<br>> work correctly. I dont load vboxnetadp, so I cant comment on that.
<br>>
<br>> /boot/loader.conf
<br>> zfs_load="YES"
<br>> vboxdrv_load="YES"
<br>> vboxnetflt_load="YES"
<br>>
<br>>
<br>> If I try to start a VM that is using the "Bridged Ethernet" adapter, the
<br>> error I get is
<br>>
<br>> "Failed to start the virtual machine Win Vista
<br>>
<br>> Failed to open/create the internal network 'HostInterfaceNetworking-re0'
<br>> (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br>>
<br>> Failed to attach the network LUN
<br>> (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br>>
<br>> Unknown eror creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br>>
<br>> Details
<br>> Result Code: NS_ERROR_FAILURE (0x80004005)
<br>> Component: Console
<br>> Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}"
<br>>
<br>>
<br>> I know the module got loaded.
<br>> [paul@demophon /usr/home/paul]$ kldstat
<br>> Id Refs Address Size Name
<br>> 1 25 0xffffffff80100000 e7c540 kernel
<br>> 2 1 0xffffffff80f7d000 18a788 zfs.ko
<br>> 3 2 0xffffffff81108000 3778 opensolaris.ko
<br>> 4 2 0xffffffff8110d000 41e88 vboxdrv.ko
<br>> 5 1 0xffffffff8114f000 6960 vboxnetflt.ko
<br>> 6 1 0xffffffff81223000 38fc linprocfs.ko
<br>> 7 1 0xffffffff81227000 1bcc4 linux.ko
<br>>
<br>> If I then do a kldunload vboxnetflt followed by kldload vboxnetflt, I
<br>> can now start and stop my VMs to my heart's content.
<br>> Im using 9 CURRENT and I only started using /boot/loader.conf for the
<br>> vbox modules about a month back. The vboxnetflt module has never worked
<br>> correctly for me this way
<br>>
<br>> Paul
</div><br>Thanks for starting the new tread :-)
<br><br>This is exactly the same problem I'm having.
<br><br>I'm on 8.0-RELEASE
<br><br>/Les
<br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895507&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895507&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895479Re: Loading kernel modules for virtualbox via script2009-12-22T14:45:36Z2009-12-22T14:45:36ZLeslie Jensen<br>On 2009-12-22 23:18, Adam Vande More wrote:
<div class='shrinkable-quote'><br>>
<br>>
<br>> It started with the tread below
<br>>
<br>> <a href="http://forums.freebsd.org/showpost.php?p=45664&postcount=5" target="_top" rel="nofollow">http://forums.freebsd.org/showpost.php?p=45664&postcount=5</a><br>> <<a href="http://forums.freebsd.org/showpost.php?p=45664&postcount=5" target="_top" rel="nofollow">http://forums.freebsd.org/showpost.php?p=45664&postcount=5</a>>
<br>>
<br>> I asumed it was the accepted way to resolve this matter, therefore I
<br>> just asked for a way to automate it when the script in /etc/rc.d/
<br>> failed on 8.0.
<br>>
<br>> I'll start a new tread and describe what I've done.
<br>>
<br>> /Les
<br>>
<br>>
<br>> Yeah, that post is basically irrelevant to your described issue. Vbox
<br>> has changed a lot since then, #1 being it's in the ports tree now.
<br>> You've not actually related what the core issue is though.
<br>> vboxnetadp.ko is needed for host-only networking mode, most people don't
<br>> need this and quite useless for almost anything. Are you aware of this?
</div><br>No, I wasn't aware of this!
<br><br><br>>
<br>> You also stated " I load vboxnetflt.ko in /boot/loader.conf and load
<br>> vboxnetadp.ko manually after I've logged in."
<br>>
<br>> Do not do this. This why crontab didn't work for you.
<br><br>>
<br>>
<br>> --
<br>> Adam Vande More
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895479&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895479&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895199Re: Loading kernel modules for virtualbox via script2009-12-22T14:18:18Z2009-12-22T14:18:18ZGalactic_Dominator<div class='shrinkable-quote'>>
<br>>> It started with the tread below
<br>>
<br>> <a href="http://forums.freebsd.org/showpost.php?p=45664&postcount=5" target="_top" rel="nofollow">http://forums.freebsd.org/showpost.php?p=45664&postcount=5</a><br>>
<br>> I asumed it was the accepted way to resolve this matter, therefore I just
<br>> asked for a way to automate it when the script in /etc/rc.d/ failed on 8.0.
<br>>
<br>> I'll start a new tread and describe what I've done.
<br>>
<br>> /Les
<br>>
<br>>
</div>Yeah, that post is basically irrelevant to your described issue. Vbox has
<br>changed a lot since then, #1 being it's in the ports tree now. You've not
<br>actually related what the core issue is though. vboxnetadp.ko is needed for
<br>host-only networking mode, most people don't need this and quite useless for
<br>almost anything. Are you aware of this?
<br><br>You also stated " I load vboxnetflt.ko in /boot/loader.conf and load
<br>vboxnetadp.ko manually after I've logged in."
<br><br>Do not do this. This why crontab didn't work for you.
<br><br><br>--
<br>Adam Vande More
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895199&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895199&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895426VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script)2009-12-22T14:17:42Z2009-12-22T14:17:42ZPaul Wootton-2 Doug Barton wrote:
<div class='shrinkable-quote'><br>> Leslie Jensen wrote:
<br>>
<br>>> On 2009-12-22 21:22, Doug Barton wrote:
<br>>>
<br>>>> The appropriate way to do this is to add them to /boot/loader.conf,
<br>>>> like this:
<br>>>>
<br>>>> vboxdrv_load="yes"
<br>>>> vboxnetflt_load="yes"
<br>>>> vboxnetadp_load="yes"
<br>>> Thanks for your answer.
<br>>>
<br>>> I did test to load the modules as you suggest. They do load but
<br>>> virtualbox produces an error when starting a virtual machine.
<br>>>
<br>>
<br>> If what you're saying is that you tried loading the modules in
<br>> /boot/loader.conf and that produced an error, then you need to start a
<br>> NEW thread on this list and describe what you did, and what the
<br>> results are in detail. This method worked fine for me in 9-current, so
<br>> if it's not working for you then we need to find out why.
<br>>
<br>>
<br>>> I've tried to load vboxdrv and vboxnetflt via loader.conf and then load
<br>>> vboxnetadp manually before starting virtualbox. That also produces the
<br>>> error when starting a VM.
<br>>>
</div>I too get an error on starting a VM if I try to load the modules from
<br>/boot/loader.conf. For me, the loading of vboxnetflt does not seem to
<br>work correctly. I dont load vboxnetadp, so I cant comment on that.
<br><br>/boot/loader.conf
<br>zfs_load="YES"
<br>vboxdrv_load="YES"
<br>vboxnetflt_load="YES"
<br><br><br>If I try to start a VM that is using the "Bridged Ethernet" adapter, the
<br>error I get is
<br><br>"Failed to start the virtual machine Win Vista
<br><br>Failed to open/create the internal network 'HostInterfaceNetworking-re0'
<br>(VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br><br>Failed to attach the network LUN
<br>(VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br><br>Unknown eror creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND).
<br><br>Details
<br>Result Code: NS_ERROR_FAILURE (0x80004005)
<br>Component: Console
<br>Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}"
<br><br><br>I know the module got loaded.
<br>[paul@demophon /usr/home/paul]$ kldstat
<br>Id Refs Address Size Name
<br> 1 25 0xffffffff80100000 e7c540 kernel
<br> 2 1 0xffffffff80f7d000 18a788 zfs.ko
<br> 3 2 0xffffffff81108000 3778 opensolaris.ko
<br> 4 2 0xffffffff8110d000 41e88 vboxdrv.ko
<br> 5 1 0xffffffff8114f000 6960 vboxnetflt.ko
<br> 6 1 0xffffffff81223000 38fc linprocfs.ko
<br> 7 1 0xffffffff81227000 1bcc4 linux.ko
<br><br>If I then do a kldunload vboxnetflt followed by kldload vboxnetflt, I
<br>can now start and stop my VMs to my heart's content.
<br>Im using 9 CURRENT and I only started using /boot/loader.conf for the
<br>vbox modules about a month back. The vboxnetflt module has never worked
<br>correctly for me this way
<br><br>Paul
<br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895426&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895426&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26895032Re: Loading kernel modules for virtualbox via script2009-12-22T14:02:48Z2009-12-22T14:02:48ZLeslie Jensen<br>On 2009-12-22 22:32, Doug Barton wrote:
<div class='shrinkable-quote'><br>> Leslie Jensen wrote:
<br>>>
<br>>> On 2009-12-22 21:22, Doug Barton wrote:
<br>>>> The appropriate way to do this is to add them to /boot/loader.conf,
<br>>>> like this:
<br>>>>
<br>>>> vboxdrv_load="yes"
<br>>>> vboxnetflt_load="yes"
<br>>>> vboxnetadp_load="yes"
<br>>>>
<br>>>> You could also write a new-style rc.d script to do this fairly easily,
<br>>>> see
<br>>>> <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html" target="_top" rel="nofollow">http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html</a><br>>>>
<br>>>> for more information. There are also existing ports that use rc.d to
<br>>>> load kernel modules, although none of the names come to mind off hand.
<br>>>>
<br>>>>
<br>>>> Doug
<br>>>>
<br>>> Thanks for your answer.
<br>>>
<br>>> I did test to load the modules as you suggest. They do load but
<br>>> virtualbox produces an error when starting a virtual machine.
<br>>
<br>> If what you're saying is that you tried loading the modules in
<br>> /boot/loader.conf and that produced an error, then you need to start a
<br>> NEW thread on this list and describe what you did, and what the
<br>> results are in detail. This method worked fine for me in 9-current, so
<br>> if it's not working for you then we need to find out why.
<br>>
<br>>> I found information in the forums suggesting that one could load the
<br>>> modules via a script i /etc/rc.d/. But with 8.0 that did not work.
<br>>
<br>> Do you understand why it didn't work? Do you understand that my
<br>> suggestion is different than the one you received on the forum?
<br>>
<br>>> I've tried to load vboxdrv and vboxnetflt via loader.conf and then load
<br>>> vboxnetadp manually before starting virtualbox. That also produces the
<br>>> error when starting a VM.
<br>>
<br>> That sounds like a deeper issue to me that has nothing to do with HOW
<br>> you load them. Once again, you need to start a NEW thread to try and
<br>> diagnose the problem you're having.
<br>>
<br>>> For now I load the modules manually with a script that also starts
<br>>> virtualbox.
<br>>
<br>> If you have an actual solution that works then you should include that
<br>> information in the new thread you're going to create. :)
<br>>
<br>>
<br>> Doug
<br>>
</div>It started with the tread below
<br><a href="http://forums.freebsd.org/showpost.php?p=45664&postcount=5" target="_top" rel="nofollow">http://forums.freebsd.org/showpost.php?p=45664&postcount=5</a><br><br>I asumed it was the accepted way to resolve this matter, therefore I
<br>just asked for a way to automate it when the script in /etc/rc.d/ failed
<br>on 8.0.
<br><br>I'll start a new tread and describe what I've done.
<br><br>/Les
<br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895032&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26895032&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26894673Re: Loading kernel modules for virtualbox via script2009-12-22T13:32:49Z2009-12-22T13:32:49ZDoug BartonLeslie Jensen wrote:
<div class='shrinkable-quote'><br>>
<br>> On 2009-12-22 21:22, Doug Barton wrote:
<br>>> The appropriate way to do this is to add them to /boot/loader.conf,
<br>>> like this:
<br>>>
<br>>> vboxdrv_load="yes"
<br>>> vboxnetflt_load="yes"
<br>>> vboxnetadp_load="yes"
<br>>>
<br>>> You could also write a new-style rc.d script to do this fairly easily,
<br>>> see
<br>>> <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html" target="_top" rel="nofollow">http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html</a><br>>>
<br>>> for more information. There are also existing ports that use rc.d to
<br>>> load kernel modules, although none of the names come to mind off hand.
<br>>>
<br>>>
<br>>> Doug
<br>>>
<br>> Thanks for your answer.
<br>>
<br>> I did test to load the modules as you suggest. They do load but
<br>> virtualbox produces an error when starting a virtual machine.
</div><br>If what you're saying is that you tried loading the modules in
<br>/boot/loader.conf and that produced an error, then you need to start a
<br>NEW thread on this list and describe what you did, and what the
<br>results are in detail. This method worked fine for me in 9-current, so
<br>if it's not working for you then we need to find out why.
<br><br>> I found information in the forums suggesting that one could load the
<br>> modules via a script i /etc/rc.d/. But with 8.0 that did not work.
<br><br>Do you understand why it didn't work? Do you understand that my
<br>suggestion is different than the one you received on the forum?
<br><br>> I've tried to load vboxdrv and vboxnetflt via loader.conf and then load
<br>> vboxnetadp manually before starting virtualbox. That also produces the
<br>> error when starting a VM.
<br><br>That sounds like a deeper issue to me that has nothing to do with HOW
<br>you load them. Once again, you need to start a NEW thread to try and
<br>diagnose the problem you're having.
<br><br>> For now I load the modules manually with a script that also starts
<br>> virtualbox.
<br><br>If you have an actual solution that works then you should include that
<br>information in the new thread you're going to create. :)
<br><br><br>Doug
<br><br>--
<br><br> Improve the effectiveness of your Internet presence with
<br> a domain name makeover! <a href="http://SupersetSolutions.com/" target="_top" rel="nofollow">http://SupersetSolutions.com/</a><br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26894673&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26894673&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26894474Re: Loading kernel modules for virtualbox via script2009-12-22T13:18:05Z2009-12-22T13:18:05ZLeslie Jensen<br>On 2009-12-22 21:22, Doug Barton wrote:
<div class='shrinkable-quote'><br>> The appropriate way to do this is to add them to /boot/loader.conf,
<br>> like this:
<br>>
<br>> vboxdrv_load="yes"
<br>> vboxnetflt_load="yes"
<br>> vboxnetadp_load="yes"
<br>>
<br>> You could also write a new-style rc.d script to do this fairly easily,
<br>> see
<br>> <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html" target="_top" rel="nofollow">http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html</a><br>> for more information. There are also existing ports that use rc.d to
<br>> load kernel modules, although none of the names come to mind off hand.
<br>>
<br>>
<br>> Doug
<br>>
</div>Thanks for your answer.
<br><br>I did test to load the modules as you suggest. They do load but
<br>virtualbox produces an error when starting a virtual machine.
<br><br>I found information in the forums suggesting that one could load the
<br>modules via a script i /etc/rc.d/. But with 8.0 that did not work.
<br><br>I've tried to load vboxdrv and vboxnetflt via loader.conf and then load
<br>vboxnetadp manually before starting virtualbox. That also produces the
<br>error when starting a VM.
<br><br>So the vboxnetflt and vboxnetadp must be loaded in that order before one
<br>starts virtualbox.
<br><br>I was ok with the suggested script so when that didn't work I got stuck.
<br><br>For now I load the modules manually with a script that also starts
<br>virtualbox.
<br><br>/Les
<br><br><br><br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26894474&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26894474&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26894159Re: Loading kernel modules for virtualbox via script2009-12-22T12:29:34Z2009-12-22T12:29:34ZYuri PankovOn Tue, Dec 22, 2009 at 12:22:05PM -0800, Doug Barton wrote:
<div class='shrinkable-quote'><br>> The appropriate way to do this is to add them to /boot/loader.conf,
<br>> like this:
<br>>
<br>> vboxdrv_load="yes"
<br>> vboxnetflt_load="yes"
<br>> vboxnetadp_load="yes"
<br>>
<br>> You could also write a new-style rc.d script to do this fairly easily,
<br>> see
<br>> <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html" target="_top" rel="nofollow">http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html</a><br>> for more information. There are also existing ports that use rc.d to
<br>> load kernel modules, although none of the names come to mind off hand.
</div><br>And many base rc scripts in /etc/rc.d/, grep for load_kld, defined and
<br>described in /etc/rc.subr.
<br><br>>
<br>>
<br>> Doug
<br>>
<br>> --
<br>>
<br>> Improve the effectiveness of your Internet presence with
<br>> a domain name makeover! <a href="http://SupersetSolutions.com/" target="_top" rel="nofollow">http://SupersetSolutions.com/</a><br><br><br>Yuri
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26894159&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26894159&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26893774Re: Loading kernel modules for virtualbox via script2009-12-22T12:22:05Z2009-12-22T12:22:05ZDoug BartonThe appropriate way to do this is to add them to /boot/loader.conf,
<br>like this:
<br><br>vboxdrv_load="yes"
<br>vboxnetflt_load="yes"
<br>vboxnetadp_load="yes"
<br><br>You could also write a new-style rc.d script to do this fairly easily,
<br>see
<br><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html" target="_top" rel="nofollow">http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html</a><br>for more information. There are also existing ports that use rc.d to
<br>load kernel modules, although none of the names come to mind off hand.
<br><br><br>Doug
<br><br>--
<br><br> Improve the effectiveness of your Internet presence with
<br> a domain name makeover! <a href="http://SupersetSolutions.com/" target="_top" rel="nofollow">http://SupersetSolutions.com/</a><br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26893774&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26893774&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26888347Re: Wiki says: Bridged networking doesn't work with a wireless interface2009-12-22T05:27:03Z2009-12-22T05:27:03ZLeslie Jensen<br>On 2009-12-22 14:22, Christof Schulze wrote:
<div class='shrinkable-quote'><br>> Am Montag 21 Dezember 2009 23:41:42 schrieb Leslie Jensen:
<br>>> <a href="http://wiki.freebsd.org/VirtualBox" target="_top" rel="nofollow">http://wiki.freebsd.org/VirtualBox</a><br>>>
<br>>> says
<br>>>
<br>>> Bridged networking doesn't work with a wireless interface
<br>>>
<br>>>
<br>>> I'm in the process of testing the iwn driver on 8.0-RELEASE.
<br>>>
<br>>> On this machine Bridged networking works with a wireless interface.
<br>>>
<br>>> So I was just wondering if I was lucky or the wiki needs an update?
<br>>>
<br>>> /Leslie
<br>> Hello,
<br>>
<br>> in general the wiki is correct, but there might be some exceptions like in
<br>> your case. The Problem with bridging ethernet and wlan is that the layer 2
<br>> protocol is different which some drivers cannot handle correctly.
<br>>
<br>> Christof
<br>>
</div>Hi Christof
<br><br>I've seen that it's quite intermittent and unreliable, and I dropped the
<br>testing with wlan.
<br><br>/Leslie
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26888347&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26888347&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26888285Re: Wiki says: Bridged networking doesn't work with a wireless interface2009-12-22T05:22:16Z2009-12-22T05:22:16ZChristof SchulzeAm Montag 21 Dezember 2009 23:41:42 schrieb Leslie Jensen:
<div class='shrinkable-quote'><div class='shrinkable-quote'><br>> <a href="http://wiki.freebsd.org/VirtualBox" target="_top" rel="nofollow">http://wiki.freebsd.org/VirtualBox</a><br>>
<br>> says
<br>>
<br>> Bridged networking doesn't work with a wireless interface
<br>>
<br>>
<br>> I'm in the process of testing the iwn driver on 8.0-RELEASE.
<br>>
<br>> On this machine Bridged networking works with a wireless interface.
<br>>
<br>> So I was just wondering if I was lucky or the wiki needs an update?
<br>>
<br>> /Leslie
</div> Hello,
</div><br>in general the wiki is correct, but there might be some exceptions like in
<br>your case. The Problem with bridging ethernet and wlan is that the layer 2
<br>protocol is different which some drivers cannot handle correctly.
<br><br>Christof
<br><br>--
<br>() ascii ribbon campaign - against html e-mail
<br>/\ www.asciiribbon.org - against proprietary attachments
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (203 bytes) <a href="http://old.nabble.com/attachment/26888285/0/signature.asc" target="_top">Download Attachment</a></div>tag:old.nabble.com,2006:post-26887975Re: [WIP] wine/i386 on FreeBSD/amd64 (take 3)2009-12-22T04:56:27Z2009-12-22T04:56:27ZDavid Bruce NaylorOn Friday 18 December 2009 23:27:15 David Naylor wrote:
<div class='shrinkable-quote'><div class='shrinkable-quote'><br>> On Tuesday 08 December 2009 15:24:00 David Naylor wrote:
<br>> > Hi,
<br>> >
<br>> > I have developed a port that allows wine to be installed as a package
<br>> > under FreeBSD/amd64. This avoids having a i386 chroot environment (and
<br>> > is much easier to setup, once the package is built).
<br>>
<br>> I've changes the name of the port (should be obvious what it is for and not
<br>> conflict when wine/amd64 arrives). The port now also automagically
<br>> determines which third party shared libraries should be bundled with it.
<br>> (See below on how to handle nvidia-driver).
</div></div>I've fixed two soft dependencies (freetype and xrender). This should complete
<br>all the required libraries to be bundled. Anti-aliased fonts and transparency
<br>should be working. This allows MS Office 2007 to work as well as on i386.
<br><br>It appears a major bug crept in with the previous published patch. Therefore
<br>it was totally useless. It has been fixed in this one (the bin and lib
<br>directories were not set correctly).
<br><br>Also, this port should now work on i386 and one can soft link to the bin/*
<br>files.
<br><div class='shrinkable-quote'><div class='shrinkable-quote'><br>> > To get this working apply the attached patch and build the
<br>> > emulators/wine- amd64 port under FreeBSD/i386 then transfer that package
<br>> > to the amd64 host:
<br>> >
<br>> > (On FreeBSD/i386)
<br>> > # cd /usr/ports/emulators
<br>> > # patch < /tmp/wine-amd64.diff
<br>>
<br>> (patch name changed, fix arguments)
<br>> # patch -sp0 < /tmp/wine-fbsd64.diff
<br>>
<br>> > # cd wine-amd64
<br>> > # make package clean
<br>> >
<br>> > (On FreeBSD/amd64)
<br>> > # pkg_add wine-amd64-8-1.1.34,1.tbz
<br>>
<br>> (package name changed)
<br>> # pkg_add wine-amd64.8-1.1.34,1.tbz
<br>>
<br>> > I have such a package for FreeBSD-8 if anyone is willing to host it.
<br>>
<br>> I'll update the patch when wine-1.1.35 gets into my ports.
<br>>
<br>> > There are a few TODO items (port options not supported). Any
<br>> > comments/suggestions are welcome.
<br>>
<br>> 1) Install from package on FreeBSD/amd64 (any suggestions on how to do
<br>> that?)
<br>> 2) Which version of FreeBSD/amd64 supports FreeBSD/i386 well enough
<br>> to run wine?
<br>> 3) Any bugs reported?
</div></div>Fixed two bugs (the above mentioned soft dependencies). Please report any you
<br>may encounter.
<br><div class='shrinkable-quote'><div class='shrinkable-quote'><br>> > Word of warning: nvidia-driver breaks everything. Make sure it is not
<br>> > installed on both i386/amd64 systems. If one really wants wine with
<br>> > nvidia- driver support then install the beta on both i386 and amd64
<br>> > (very important it is the same version of the driver) and copy
<br>> > libGL.so.1, libGLcore.so.1 and libnvidia-tls.so.1 from i386 to
<br>> > $PREFIX/lib32 (on amd64).
<br>>
<br>> The above method still does work but now, if one installs nvidia-driver (of
<br>> the correct version) before building wine under FreeBSD/i386 then the
<br>> required libraries will be included (this makes the package unsuitable for
<br>> any system without the correct nvidia drivers installed).
</div>
</div>Regards,
<br>
<br>David
<br>
<br>> P.S. I've included the shar archive as some people have not been able to
<br>> apply the patch cleanly
<br><br /><tt>[wine-fbsd64.diff]</tt><br /><hr align="left" width="300" /><tt>diff -uNr /usr/ports/emulators/wine/Makefile wine/Makefile
<br>--- /usr/ports/emulators/wine/Makefile 2009-12-20 03:04:01.000000000 +0200
<br>+++ wine/Makefile 2009-12-20 17:02:22.000000000 +0200
<br>@@ -30,12 +30,10 @@
<br> --without-sane --without-xcursor
<br> CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
<br> LDFLAGS="-L${LOCALBASE}/lib"
<br>-USE_LDCONFIG= ${PREFIX}/lib ${PREFIX}/lib/wine
<br> MAKE_JOBS_SAFE= yes
<br> MAN1= widl.1 wine.1 winebuild.1 winedbg.1 winedump.1 winegcc.1 \
<br> winemaker.1 wineprefixcreate.1 wineserver.1 wmc.1 wrc.1
<br> MLINKS= winegcc.1 wineg++.1
<br>-ONLY_FOR_ARCHS= i386
<br> USE_BISON= build
<br> USE_BZIP2= yes
<br> USE_GMAKE= yes
<br>@@ -80,10 +78,33 @@
<br> CONFIGURE_ARGS+= --without-xslt
<br> .endif
<br>
<br>+# TODO: when does FreeBSD/i386 work properly under FreeBSD/amd64?
<br> .if ${OSVERSION} < 603000
<br> IGNORE= fails to properly work on versions of FreeBSD before 6.3
<br> .endif
<br>
<br>+.ifdef WINE_CROSS_BUILD
<br>+
<br>+CONFIGURE_ARGS+= --bindir=${PREFIX}/bin32 --libdir=${PREFIX}/lib32
<br>+CONFLICTS= wine-[0-9]*
<br>+ONLY_FOR_ARCHS= i386 amd64
<br>+USE_LDCONFIG32= ${PREFIX}/lib32 ${PREFIX}/lib32/wine
<br>+WINELIBDIR=${PREFIX}/lib32
<br>+
<br>+PLIST_REINPLACE+= winelib
<br>+PLIST_REINPLACE_WINELIB=s!lib/!lib32/!g
<br>+
<br>+ACTUAL-PACKAGE-DEPENDS=${DO_NADA}
<br>+
<br>+.else
<br>+
<br>+CONFLICTS= wine-fbsd64.*
<br>+ONLY_FOR_ARCHS= i386
<br>+USE_LDCONFIG= ${PREFIX}/lib ${PREFIX}/lib/wine
<br>+WINELIBDIR=${PREFIX}/lib
<br>+
<br>+.endif
<br>+
<br> post-patch:
<br> .if ${OSVERSION} < 700041
<br> ${REINPLACE_CMD} 's/-lpthread/-lthr/g' ${WRKSRC}/configure
<br>@@ -99,8 +120,8 @@
<br> ${MAN1PREFIX}/man/fr.UTF-8/man1/wineserver.1
<br> @-${RMDIR} -p ${MAN1PREFIX}/man/de.UTF-8/man1 \
<br> ${MAN1PREFIX}/man/fr.UTF-8/man1
<br>- ${MV} -f ${PREFIX}/lib/libwine.so.1.0 ${PREFIX}/lib/libwine.so.1
<br>- ${LN} -sf libwine.so.1 ${PREFIX}/lib/libwine.so
<br>+ ${MV} -f ${WINELIBDIR}/libwine.so.1.0 ${WINELIBDIR}/libwine.so.1
<br>+ ${LN} -sf libwine.so.1 ${WINELIBDIR}/libwine.so
<br> .if !defined(NOPORTDOCS)
<br> -@${MKDIR} ${DOCSDIR}
<br> .for i in README ANNOUNCE AUTHORS LICENSE
<br>@@ -109,6 +130,27 @@
<br> @${INSTALL_DATA} ${WRKSRC}/programs/winedbg/README ${DOCSDIR}/README.winedbg
<br> @${INSTALL_DATA} ${WRKSRC}/tools/winedump/README ${DOCSDIR}/README.winedump
<br> .endif
<br>+.ifdef WINE_CROSS_BUILD
<br>+ grep -v '[@%]' ${TMPPLIST} | sed "s!^!${PREFIX}/!g" | \
<br>+ xargs -n1 file -F' ' | grep ELF | cut -f1 -d' ' | \
<br>+ env LD_LIBRARY_PATH=${PREFIX}/lib32:${LD_LIBRARY_PATH} xargs ldd -f '%p\n' \
<br>+ | sort -u | grep -v '^\(/usr\)\?/lib' | grep -v "^${PREFIX}/lib32/libwine.so" \
<br>+ | grep -v "^${PREFIX}/lib32/wine" > ${WRKDIR}/winelibs.list
<br>+ for i in `cat ${WRKDIR}/winelibs.list` ; do \
<br>+ ${INSTALL_DATA} $${i} ${PREFIX}/lib32/ ; \
<br>+ echo lib32/`basename $${i}` >> ${TMPPLIST} ; \
<br>+ done
<br>+ for i in libfreetype.so.9 libXrender.so.1 ; do \
<br>+ ${INSTALL_DATA} ${LOCALBASE}/lib/$${i} ${PREFIX}/lib32/ ; \
<br>+ echo lib32/$${i} >> ${TMPPLIST} ; \
<br>+ done
<br>+ ${INSTALL_SCRIPT} ${FILESDIR}/binbounce ${PREFIX}/bin/wine
<br>+ for i in `grep ^bin ${TMPPLIST} | xargs -n1 basename` ; do \
<br>+ [ "$${i}" = "wine" ] || ${LN} -f ${PREFIX}/bin/wine ${PREFIX}/bin/$${i} ; \
<br>+ echo bin32/$${i} >> ${TMPPLIST} ; \
<br>+ done
<br>+ echo '@unexec rmdir %D/bin32 2>/dev/null || true' >> ${TMPPLIST}
<br>+.endif
<br> @${MKDIR} ${DESKTOPDIR}
<br> @${MV} ${DATADIR}/applications/wine.desktop ${DESKTOPDIR}/
<br> @${ECHO}
<br>diff -uNr /usr/ports/emulators/wine/files/binbounce wine/files/binbounce
<br>--- /usr/ports/emulators/wine/files/binbounce 1970-01-01 02:00:00.000000000 +0200
<br>+++ wine/files/binbounce 2009-12-20 18:29:51.000000000 +0200
<br>@@ -0,0 +1,27 @@
<br>+#!/bin/sh
<br>+
<br>+TARGET=$0
<br>+_count=0
<br>+while [ -L "$TARGET" ]
<br>+do
<br>+ TARGET=`ls -l "$TARGET" | sed -e 's/.* -> //'`
<br>+ _count=$(($_count + 1))
<br>+ if [ $_count -gt 100 ]
<br>+ then
<br>+ echo "$0: to many symbolic links" > /dev/stderr
<br>+ exit 1
<br>+ fi
<br>+done
<br>+
<br>+LOCALBASE=`dirname "$TARGET"`/..
<br>+BINNAME=`basename "$TARGET"`
<br>+
<br>+if [ `uname -p` = i386 ]
<br>+then
<br>+ export LD_LIBRARY_PATH="$LOCALBASE/lib32":"$LOCALBASE/lib32/wine":"$LD_LIBRARY_PATH"
<br>+else
<br>+ export LD_32_LIBRARY_PATH="$LOCALBASE/lib32":"$LOCALBASE/lib32/wine":"$LD_32_LIBRARY_PATH"
<br>+fi
<br>+export PATH="$LOCALBASE/bin32":"$PATH"
<br>+
<br>+exec "$LOCALBASE/bin32/$BINNAME" "$@"
<br>diff -uNr /usr/ports/emulators/wine-fbsd64/ChangeLog wine-fbsd64/ChangeLog
<br>--- /usr/ports/emulators/wine-fbsd64/ChangeLog 1970-01-01 02:00:00.000000000 +0200
<br>+++ wine-fbsd64/ChangeLog 2009-12-20 16:52:11.000000000 +0200
<br>@@ -0,0 +1,20 @@
<br>+2009/12/20:
<br>+ * Correctly set bin/lib directories
<br>+ * Support running on i386
<br>+ * Follow symbolic links to script
<br>+ * Allow spaces in path
<br>+ * Hard link the bin/* files (otherwise symbolic link following breaks)
<br>+
<br>+2009/12/19:
<br>+ * Include freetype (it is a soft dependancy)
<br>+ * Include libXrender (it is a soft dependancy)
<br>+
<br>+2009/12/18:
<br>+ * Rename to something with a little more sense (wine-amd64-[V] -> wine-fbsd64.[V])
<br>+ * Fix conflicts (wine conflicts with wine-fbsd64)
<br>+
<br>+2009/12/17:
<br>+ * Automatically determine libraries and binaries
<br>+
<br>+2009/12/08:
<br>+ * Initial implementation of WINE/i386 on FreeBSD/amd64
<br>diff -uNr /usr/ports/emulators/wine-fbsd64/Makefile wine-fbsd64/Makefile
<br>--- /usr/ports/emulators/wine-fbsd64/Makefile 1970-01-01 02:00:00.000000000 +0200
<br>+++ wine-fbsd64/Makefile 2009-12-18 19:44:47.000000000 +0200
<br>@@ -0,0 +1,12 @@
<br>+PORTNAME= wine
<br>+PKGNAMESUFFIX= -fbsd64.${OSVERSION:C/([0-9]).*/\1/}
<br>+
<br>+WINE_CROSS_BUILD=yes
<br>+
<br>+MASTERDIR= ${.CURDIR}/../wine
<br>+
<br>+#.if ${ARCH} == "amd64"
<br>+# TODO: install from package (how?)
<br>+#.endif
<br>+
<br>+.include "${MASTERDIR}/Makefile"
<br></tt><hr align="left" width="300" /><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (203 bytes) <a href="http://old.nabble.com/attachment/26887975/0/signature.asc" target="_top">Download Attachment</a></div>tag:old.nabble.com,2006:post-26886214Re: Building kernel modules for virtualbox independently2009-12-22T02:13:05Z2009-12-22T02:13:05ZVladimir Grebenschikov-2Hi
<br><br>Thanks, will be happy to test it.
<br><br><br>-----Original Message-----
<br>From: Bernhard Froehlich <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=0" target="_top" rel="nofollow">decke@...</a>>
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=1" target="_top" rel="nofollow">vova@...</a>
<br>Cc: freebsd-emulation <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=2" target="_top" rel="nofollow">freebsd-emulation@...</a>>, <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=3" target="_top" rel="nofollow">vbox@...</a>
<br>Subject: Re: Building kernel modules for virtualbox independently
<br>Date: Tue, 22 Dec 2009 10:25:24 +0100 (CET)
<br><br>On Tue, December 22, 2009 9:58 am, Vladimir Grebenschikov wrote:
<br>> Hi
<br>>
<br>> Probably it is better to move out build of kernel modules out of
<br>> virtualbox port ?
<br>>
<br>> After kernel upgrade all kmods should be rebuild, but rebuilding whole
<br>> virtualbox looks too heavy to do it on every kernel update.
<br><br>Our testing port is already split up and we will do a call for testers for
<br>the new virtualbox 3.1.2 port very soon.
<br><br><br>--
<br>Vladimir B. Grebenschikov
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=4" target="_top" rel="nofollow">vova@...</a>
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=5" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26886214&i=6" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26885975Re: Loading kernel modules for virtualbox via script2009-12-22T01:52:42Z2009-12-22T01:52:42ZLeslie Jensen<div class='shrinkable-quote'><br>>
<br>>
<br>> I have this in my crontab
<br>>
<br>> @reboot root /sbin/kldload
<br>> /boot/modules/vboxnetflt.ko
<br>>
<br>>
<br>>
<br>> --
<br>> Adam Vande More
</div><br>Thanks for the answer!
<br>The problem is that I understood that vboxnetflt.ko should be loaded
<br>before vboxnetadp.ko
<br><br>I load vboxnetflt.ko in /boot/loader.conf and load vboxnetadp.ko
<br>manually after I've logged in.
<br><br>I tried to load vboxnetadp.ko via crontab but Virtualbox came up with
<br>the error.
<br><br>If I unload both modules and load them again manually, vboxnetflt.ko
<br>first. Then it works!
<br><br>I can manage this, but I was looking for a way to do it automagically :-)
<br><br>I've seen that if vboxnetadp.ko is loaded first it loads vboxnetflt.ko
<br>as well.
<br><br>So what if the "dependency" was reversed? Then only vboxnetflt.ko had to
<br>be loaded and it could load vboxnetadp.ko.
<br><br>/Leslie
<br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885975&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885975&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26885719Re: Building kernel modules for virtualbox independently2009-12-22T01:25:24Z2009-12-22T01:25:24ZBernhard FroehlichOn Tue, December 22, 2009 9:58 am, Vladimir Grebenschikov wrote:
<br>> Hi
<br>>
<br>> Probably it is better to move out build of kernel modules out of
<br>> virtualbox port ?
<br>>
<br>> After kernel upgrade all kmods should be rebuild, but rebuilding whole
<br>> virtualbox looks too heavy to do it on every kernel update.
<br><br>Our testing port is already split up and we will do a call for testers for
<br>the new virtualbox 3.1.2 port very soon.
<br><br>--
<br>Bernhard Fröhlich
<br><a href="http://www.bluelife.at/" target="_top" rel="nofollow">http://www.bluelife.at/</a><br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885719&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885719&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26885453Building kernel modules for virtualbox independently2009-12-22T00:58:47Z2009-12-22T00:58:47ZVladimir Grebenschikov-2Hi
<br><br>Probably it is better to move out build of kernel modules out of
<br>virtualbox port ?
<br><br>After kernel upgrade all kmods should be rebuild, but rebuilding whole
<br>virtualbox looks too heavy to do it on every kernel update.
<br><br><br>--
<br>Vladimir B. Grebenschikov
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885453&i=0" target="_top" rel="nofollow">vova@...</a>
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885453&i=1" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26885453&i=2" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26881836Re: Loading kernel modules for virtualbox via script2009-12-21T15:37:52Z2009-12-21T15:37:52ZGalactic_DominatorOn Mon, Dec 21, 2009 at 4:37 PM, Leslie Jensen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881836&i=0" target="_top" rel="nofollow">leslie@...</a>> wrote:
<br><div class='shrinkable-quote'><br>>
<br>> Following the suggestion here:
<br>> <a href="http://forums.freebsd.org/showpost.php?p=45664&postcount=5" target="_top" rel="nofollow">http://forums.freebsd.org/showpost.php?p=45664&postcount=5</a><br>>
<br>> To load two kernel modules via a script in /etc/rc.d/
<br>>
<br>> Produces the following:
<br>>
<br>> WARNING: Ignoring old-style startup script /etc/rc.d/
<br>>
<br>> I found the answer here:
<br>>
<br>>
<br>> <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=2896643&group_id=151951&atid=782616" target="_top" rel="nofollow">http://sourceforge.net/tracker/index.php?func=detail&aid=2896643&group_id=151951&atid=782616</a><br>>
<br>> At the moment I load vboxnetflt via /boot/loader.conf and I then load
<br>> vboxnetadp manually before I start virtualbox.
<br>>
<br>> I would like a suggestion on how to load both modules automaticly!
<br>>
<br>> Thanks
<br>>
<br>> /Leslie
<br>>
<br>>
</div>I have this in my crontab
<br><br>@reboot root /sbin/kldload
<br>/boot/modules/vboxnetflt.ko
<br><br><br><br>--
<br>Adam Vande More
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881836&i=1" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881836&i=2" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26881495Wiki says: Bridged networking doesn't work with a wireless interface2009-12-21T14:41:42Z2009-12-21T14:41:42ZLeslie Jensen<br><a href="http://wiki.freebsd.org/VirtualBox" target="_top" rel="nofollow">http://wiki.freebsd.org/VirtualBox</a><br><br>says
<br><br>Bridged networking doesn't work with a wireless interface
<br><br><br>I'm in the process of testing the iwn driver on 8.0-RELEASE.
<br><br>On this machine Bridged networking works with a wireless interface.
<br><br>So I was just wondering if I was lucky or the wiki needs an update?
<br><br>/Leslie
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881495&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881495&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26881437Loading kernel modules for virtualbox via script2009-12-21T14:37:20Z2009-12-21T14:37:20ZLeslie Jensen<br>Following the suggestion here:
<br><a href="http://forums.freebsd.org/showpost.php?p=45664&postcount=5" target="_top" rel="nofollow">http://forums.freebsd.org/showpost.php?p=45664&postcount=5</a><br><br>To load two kernel modules via a script in /etc/rc.d/
<br><br>Produces the following:
<br><br>WARNING: Ignoring old-style startup script /etc/rc.d/
<br><br>I found the answer here:
<br><br><a href="http://sourceforge.net/tracker/index.php?func=detail&aid=2896643&group_id=151951&atid=782616" target="_top" rel="nofollow">http://sourceforge.net/tracker/index.php?func=detail&aid=2896643&group_id=151951&atid=782616</a><br><br>At the moment I load vboxnetflt via /boot/loader.conf and I then load
<br>vboxnetadp manually before I start virtualbox.
<br><br>I would like a suggestion on how to load both modules automaticly!
<br><br>Thanks
<br><br>/Leslie
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881437&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26881437&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26872522Current problem reports assigned to freebsd-emulation@FreeBSD.org2009-12-21T03:06:52Z2009-12-21T03:06:52ZFreeBSD bugmasterNote: to view an individual PR, use:
<br> <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=(number" target="_top" rel="nofollow">http://www.freebsd.org/cgi/query-pr.cgi?pr=(number</a>).
<br><br>The following is a listing of current problems submitted by FreeBSD users.
<br>These represent problem reports covering all versions including
<br>experimental development code and obsolete releases.
<br><br><br>S Tracker Resp. Description
<br>--------------------------------------------------------------------------------
<br>o kern/141439 emulation [linux] [patch] linux_exit_group kills group leader
<br>o kern/140156 emulation [linux] cdparanoia fails to read drive data
<br>o kern/139423 emulation [parallels] Networking does not work on amd64 guest on
<br>o kern/138944 emulation [parallels] [regression] Parallels no longer works in
<br>o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest
<br>o kern/138860 emulation [linux] linux_socketcall() causing buffer overflow
<br>f ports/137332 emulation add caution messages to some adobe products
<br>s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po
<br>o ports/136229 emulation [linux] emulators/linux_base-f10: certain linux apps l
<br>o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage
<br>o kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so.
<br>o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau
<br>o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n
<br>o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails
<br>o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand
<br>a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s
<br>o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU
<br>o kern/41543 emulation [patch] [request] easier wine/w23 support
<br>o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu
<br>o kern/29698 emulation [linux] [patch] linux ipcs doesn'work
<br>o kern/21463 emulation [linux] Linux compatability mode should not allow setu
<br>o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999
<br><br>22 problems total.
<br><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26872522&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26872522&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26870662FreeBSD ports that you maintain which are currently marked broken2009-12-20T23:28:17Z2009-12-20T23:28:17ZlinimonDear FreeBSD port maintainer:
<br><br>As part of an ongoing effort to reduce the number of problems in
<br>the FreeBSD ports system, we periodically notify users of ports
<br>that are marked as "broken" in their Makefiles. In many cases
<br>these ports are failing to compile on some subset of the FreeBSD
<br>build environments. The most common problem is that recent versions
<br>of -CURRENT include gcc4.2, which is much stricter than older versions.
<br>The next most common problem is that compiles succeed on the i386
<br>architecture (e.g. the common Intel PC), but fail on one or more
<br>of the other architectures due to assumptions about things such as
<br>size of various types, byte-alignment issues, and so forth.
<br><br>In occasional cases we see that the same port may have different
<br>errors in different build environments. The script that runs on the
<br>build cluster uses heuristics to try to 'guess' the error type to
<br>help you isolate problems, but it is only a rough guide.
<br><br>One more note: on occasion, there are transient build errors seen
<br>on the build farm. Unfortunately, there is not yet any way for this
<br>algorithm to tell the difference (humans are much, much better at
<br>this kind of thing.)
<br><br>The errors are listed below. In the case where the same problem
<br>exists on more than one build environment, the URL points to the
<br>latest errorlog for that type. (By 'build environment' here we
<br>mean 'combination of 6.x/7.x/-current with target architecture'.)
<br><br>(Note: the dates are included to help you to gauge whether or not
<br>the error still applies to the latest version. The program
<br>that generates this report is not yet able to determine this
<br>automatically.)
<br><br>portname: sysutils/linux-nero
<br>broken because: unfetchable
<br>build errors:
<br><a href="http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20091211210609/linux-nero-3.5.0.1.log" target="_top" rel="nofollow">http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20091211210609/linux-nero-3.5.0.1.log</a> (_Dec__7_01:52:47_UTC_2009)
<br>overview: <a href="http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=linux-nero" target="_top" rel="nofollow">http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=linux-nero</a><br><br><br>If these errors are ones that you are already aware of, please
<br>accept our apologies and ignore this message. On the other hand, if
<br>you no longer wish to maintain this port (or ports), please reply
<br>with a message stating that, and accept our thanks for your efforts
<br>in the past.
<br><br>Every effort has been made to make sure that these error reports
<br>really do correspond to a port that you maintain. However, due to
<br>the fact that this is an automated process, it may indeed generate
<br>false matches. If one of these errors fits that description,
<br>please forward this email to the author of this software, Mark
<br>Linimon <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26870662&i=0" target="_top" rel="nofollow">linimon@...</a>>, so that he can attempt to fix the
<br>problem in the future.
<br><br>Thanks for your efforts to help improve FreeBSD.
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26870662&i=1" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26870662&i=2" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26865794Re: ports/127018: Linuxulator incapable of using FreeBSD's LDAP environment2009-12-20T10:10:06Z2009-12-20T10:10:06ZMarcin Wisnicki-2The following reply was made to PR ports/127018; it has been noted by GNATS.
<br><br>From: =?ISO-8859-2?Q?Marcin_Wi=B6nicki?= <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26865794&i=0" target="_top" rel="nofollow">mwisnicki@...</a>>
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26865794&i=1" target="_top" rel="nofollow">bug-followup@...</a>, <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26865794&i=2" target="_top" rel="nofollow">ohartman@...</a>
<br>Cc:
<br>Subject: Re: ports/127018: Linuxulator incapable of using FreeBSD's LDAP
<br> environment
<br>Date: Sun, 20 Dec 2009 19:05:49 +0100
<br><br> Just noticed this via mail to emulation@ and since I used to have LDAP
<br> in the past I'd like to contribute some feedback.
<br>
<br> The underlying problem is that LDAP integration is done through
<br> nsswitch (part of libc) and nss_ldap.so module (from ports). Linux has
<br> the same mechanism however linux-compiled glibc will obviously fail to
<br> load freebsd-native nss_ldap.so.
<br> I assume that to get LDAP in linuxulator one will first need to
<br> install linux version of nss_ldap and it's dependencies and then
<br> configure nsswitch in /compat/linux/etc as he would on real linux
<br> system. At this time however there are no ports for those libs.
<br>
<br> I believe that it's also possible to solve this problem in more
<br> general way by writing some kind of nscd(8) proxy that would translate
<br> between protocol used in freebsd and what is expected by glibc.
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26865794&i=3" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26865794&i=4" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26863977Try to running Aladdin HASP SRM2009-12-20T06:12:58Z2009-12-20T06:12:58ZSergey-46Hello
<br><br>I have USB Aladdin HASP SRM key and try to use it on FreeBSD 8.0 but no luck now:(
<br>What I do wrong?
<br><br>Aladdin offers HASP SRM Run-time Installer Script (ftp://ftp.aladdin.com/pub/hasp/srm/Linux/HASP_SRM_LINUX_3.50_Run-time_Installer_script.tar.gz) for:
<br>- Linux SuSE ES 10 with Service Pack 1 (x86 and x86_64),
<br>- RedHat EL5 with Service Pack 1 (x86 and x86_64), and
<br>- Ubuntu Desktop 8.04 (x86 and x86_64).
<br><br>I install emulators/linux_base-gentoo-stage3 because I wish to use ktrace.
<br><br>Then I ran by hand as ordinary user:
<br> 1. aksusbd (support for HASP HL keys and low‐level access to HASP License Manager daemon)
<br>Now I see:
<br>ps ax | grep aks
<br>32631 2 S 0:00,00 2/aksusbd
<br>32632 2 S 0:00,00 2/aksusbd
<br>32633 2 S 0:00,00 2/aksusbd
<br>Resume: like of success
<br><br> 2. winehasp (access for HASP HL keys to Windows applications running in Wine)
<br>Now I see:
<br>ps ax | grep win
<br>32638 2 I 0:00,00 2/winehasp
<br>Resume: like of success
<br><br> 3. ktrace hasplmd -s (HASP License Manager daemon).
<br>Now I see:
<br>ps ax | grep hasp
<br>32638 2 I 0:00,00 2/winehasp
<br>Resume: hasplmd not running.
<br>One more test failed: netstat -an | grep 1947 found nothing instead of "Admin Control Center". :(
<br><br>ldd hasplmd
<br>hasplmd:
<br> libm.so.6 => /lib/libm.so.6 (0x28067000)
<br> libpthread.so.0 => /lib/libpthread.so.0 (0x2808e000)
<br> libdl.so.2 => /lib/libdl.so.2 (0x280a5000)
<br> libc.so.6 => /lib/libc.so.6 (0x280a9000)
<br> /lib/ld-linux.so.2 (0x28048000)
<br><br>linux_kdump > hasp.dump
<br><br> 32645 ktrace RET linux_brk 0
<br> 32645 ktrace CALL linux_olduname(0xbfbfed43,0xbfbfebfc,0xbfbfec10)
<br> 32645 ktrace NAMI "2/hasplmd"
<br> 32645 ktrace NAMI "/compat/linux/lib/ld-linux.so.2"
<br> 32645 hasplmd RET linux_olduname 0
<br> 32645 hasplmd CALL linux_brk(0)
<br> 32645 hasplmd RET linux_brk 135712768/0x816d000
<br> 32645 hasplmd CALL linux_newuname(0xbfbfe9f0)
<br> 32645 hasplmd RET linux_newuname 0
<br> 32645 hasplmd CALL linux_access(0x280601cb,0x4)
<br> 32645 hasplmd NAMI "/compat/linux/etc/ld.so.preload"
<br> 32645 hasplmd NAMI "/etc/ld.so.preload"
<br> 32645 hasplmd RET linux_access JUSTRETURN
<br> 32645 hasplmd CALL linux_open(0x280604b7,0,0)
<br> 32645 hasplmd NAMI "/compat/linux/etc/ld.so.cache"
<br> 32645 hasplmd NAMI "/compat/linux"
<br> 32645 hasplmd NAMI "/compat/linux/etc/ld.so.cache"
<br> 32645 hasplmd RET linux_open 3
<br> 32645 hasplmd CALL linux_fstat64(0x3,0xbfbfe30c,0x28062fd4)
<br> 32645 hasplmd UNKNOWN(8) 32645 hasplmd RET linux_fstat64 0
<br> 32645 hasplmd CALL linux_mmap2(0,0x2a86,0x1,0x2,0x3,0)
<br> 32645 hasplmd RET linux_mmap2 671498240/0x28064000
<br> 32645 hasplmd CALL close(0x3)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL linux_open(0x280660c1,0,0)
<br> 32645 hasplmd NAMI "/compat/linux/lib/libm.so.6"
<br> 32645 hasplmd NAMI "/compat/linux"
<br> 32645 hasplmd NAMI "/compat/linux/lib/libm.so.6"
<br> 32645 hasplmd RET linux_open 3
<br> 32645 hasplmd CALL read(0x3,0xbfbfe484,0x200)
<br> 32645 hasplmd GIO fd 3 read 512 bytes
<br> "\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0\0\^C\0\^C\0\^A\0\0\0p4\0\0004\0\0\0000\
<br> B\^B\0\0\0\0\0004\0 \0
<br> \0(\0\^_\0\^^\0\^F\0\0\0004\0\0\0004\0\0\0004\0\0\0@\^A\0\0@\^A\0\0\^E\
<br> \0\0\0\^D\0\0\0\^C\0\0\0\M-x\^]\^B\0\M-x\^]\^B\0\M-x\^]\^B\0\^S\0\0\0\
<br> \^S\0\0\0\^D\0\0\0\^A\0\0\0\^A\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\M-$<\^B\0\
<br> \M-$<\^B\0\^E\0\0\0\0\^P\0\0\^A\0\0\0\M-\>\^B\0\M-\N\^B\0\M-\N\^B\0`\
<br> \^A\0\0\M-$\^A\0\0\^F\0\0\0\0\^P\0\0\^B\0\0\0\M-p>\^B\0\M-pN\^B\0\M-pN\
<br> \^B\0\M-h\0\0\0\M-h\0\0\0\^F\0\0\0\^D\0\0\0\^D\0\0\0t\^A\0\0t\^A\0\0t\
<br> \^A\0\0 \0\0\0 \0\0\0\^D\0\0\0\^D\0\0\0P\M-etd\f\^^\^B\0\f\^^\^B\0\f\
<br> \^^\^B\0\^\\^D\0\0\^\\^D\0\0\^D\0\0\0\^D\0\0\0Q\M-etd\0\0\0\0\0\0\0\0\
<br> \0\0\0\0\0\0\0\0\0\0\0\0\^F\0\0\0\^D\0\0\0R\M-etd\M-\>\^B\0\M-\N\^B\0\
<br> \M-\N\^B\0$\^A\0\0$\^A\0\0\^D\0\0\0\^A\0\0\0\M^@\^U\^De\0\0\0\0\0\0\0\
<br> \0\0\0\0\0\0\0\0\0\0\0\0\0\0(\0\0\^D\0\0\0\^D\0\0\0\^P\0\0\0\^A\0\0\0G\
<br> NU\0\0\0\0\0\^B\0\0\0\^F\0\0\0 \0\0\0\M^L\^B\0\0\^O\0\0\0@\0\0\0\v\0\
<br> \0\0%\M^P \M-E \M^Dg\v\0\M-B\^P \^DiER\M^B\^P\M^@\240\0}\M^H\M-:\b\bI\
<br> \0\0\0\0\0\^[\^D\M^A\0\0\0\M^ZU\^PA P \M^@\M^T\M^B\M^P\^Q@\M-z2\0\M-Da\
<br> \^T\0\b\^F\M-F\M^P\M^Z\f\M^G\M-@ \M-(\0 \M^B\0\M^X\M^A\^DE\a\^E4a\^B\
<br> \0\0\M-)C\^X\M-H \b\^S\^X"
<br> 32645 hasplmd RET read 512/0x200
<br> 32645 hasplmd CALL linux_fstat64(0x3,0xbfbfe38c,0x28062fd4)
<br> 32645 hasplmd UNKNOWN(8) 32645 hasplmd RET linux_fstat64 0
<br> 32645 hasplmd CALL linux_mmap2(0,0x25080,0x5,0x802,0x3,0)
<br> 32645 hasplmd RET linux_mmap2 671510528/0x28067000
<br> 32645 hasplmd CALL linux_mmap2(0x2808b000,0x2000,0x3,0x812,0x3,0x23)
<br> 32645 hasplmd RET linux_mmap2 671657984/0x2808b000
<br> 32645 hasplmd CALL close(0x3)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL linux_open(0x2806594a,0,0x4f)
<br> 32645 hasplmd NAMI "/compat/linux/lib/libpthread.so.0"
<br> 32645 hasplmd NAMI "/compat/linux"
<br> 32645 hasplmd NAMI "/compat/linux/lib/libpthread.so.0"
<br> 32645 hasplmd RET linux_open 3
<br> 32645 hasplmd CALL read(0x3,0xbfbfe468,0x200)
<br> 32645 hasplmd GIO fd 3 read 512 bytes
<br> "\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0\0\^C\0\^C\0\^A\0\0\0\M^PG\0\0004\0\0\0\
<br> \M^XL\^A\0\0\0\0\0004\0 \0
<br> \0(\0$\0!\0\^F\0\0\0004\0\0\0004\0\0\0004\0\0\0@\^A\0\0@\^A\0\0\^E\0\0\
<br> \0\^D\0\0\0\^C\0\0\0\^T\M-y\0\0\^T\M-y\0\0\^T\M-y\0\0\^S\0\0\0\^S\0\0\
<br> \0\^D\0\0\0\^A\0\0\0\^A\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0d$\^A\0d$\^A\0\^E\
<br> \0\0\0\0\^P\0\0\^A\0\0\0\M-@-\^A\0\M-@=\^A\0\M-@=\^A\0|\^C\0\0 $\0\0\
<br> \^F\0\0\0\0\^P\0\0\^B\0\0\0\M-8.\^A\0\M-8>\^A\0\M-8>\^A\0\M-x\0\0\0\
<br> \M-x\0\0\0\^F\0\0\0\^D\0\0\0\^D\0\0\0t\^A\0\0t\^A\0\0t\^A\0\0 \0\0\0 \
<br> \0\0\0\^D\0\0\0\^D\0\0\0P\M-etd(\M-y\0\0(\M-y\0\0(\M-y\0\0l\^D\0\0l\^D\
<br> \0\0\^D\0\0\0\^D\0\0\0Q\M-etd\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
<br> \^F\0\0\0\^D\0\0\0R\M-etd\M-@-\^A\0\M-@=\^A\0\M-@=\^A\0@\^B\0\0@\^B\0\
<br> \0\^D\0\0\0\^A\0\0\0\M^@\^U\^De\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
<br> \0\0(\0\0\^D\0\0\0\^D\0\0\0\^P\0\0\0\^A\0\0\0GNU\0\0\0\0\0\^B\0\0\0\^F\
<br> \0\0\0 \0\0\0\M-2\^A\0\0M\0\0\0@\0\0\0\v\0\0\0\^Y!\^B\M^Q\^A
<br> \^P"@H \M-Y\^C\0I4\M^@\0\0@\0 \M^@\M^@\^QP`@@\^R\M^K\^B0D\0\0\^P\0\0\
<br> \^B\0\^A\r\0\M^D
<br> \M-p\^AX\M-0\r\240\M^@\b $\M^D\^PB\M-")m\bG\M^\V\^P\0\M^T \M^D$\b\0H(\
<br> \^A\M^R\^\\M-AB\240\M^P\^R\b\f \^B\^X`A\M-$"
<br> 32645 hasplmd RET read 512/0x200
<br> 32645 hasplmd CALL linux_fstat64(0x3,0xbfbfe370,0x28062fd4)
<br> 32645 hasplmd UNKNOWN(8) 32645 hasplmd RET linux_fstat64 0
<br> 32645 hasplmd CALL linux_mmap2(0,0x1000,0x3,0x22,0xffffffff,0)
<br> 32645 hasplmd RET linux_mmap2 671666176/0x2808d000
<br> 32645 hasplmd CALL linux_mmap2(0,0x161e0,0x5,0x802,0x3,0)
<br> 32645 hasplmd RET linux_mmap2 671670272/0x2808e000
<br> 32645 hasplmd CALL linux_mmap2(0x280a1000,0x2000,0x3,0x812,0x3,0x12)
<br> 32645 hasplmd RET linux_mmap2 671748096/0x280a1000
<br> 32645 hasplmd CALL linux_mmap2(0x280a3000,0x11e0,0x3,0x32,0xffffffff,0)
<br> 32645 hasplmd RET linux_mmap2 671756288/0x280a3000
<br> 32645 hasplmd CALL close(0x3)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL linux_open(0x28066605,0,0x1e)
<br> 32645 hasplmd NAMI "/compat/linux/lib/libdl.so.2"
<br> 32645 hasplmd NAMI "/compat/linux"
<br> 32645 hasplmd NAMI "/compat/linux/lib/libdl.so.2"
<br> 32645 hasplmd RET linux_open 3
<br> 32645 hasplmd CALL read(0x3,0xbfbfe44c,0x200)
<br> 32645 hasplmd GIO fd 3 read 512 bytes
<br> "\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0\0\^C\0\^C\0\^A\0\0\0p
<br> \0\0004\0\0\0,!\0\0\0\0\0\0004\0 \0 \0(\0\^\\0\^[\0\^F\0\0\0004\0\
<br> \0\0004\0\0\0004\0\0\0 \^A\0\0 \^A\0\0\^E\0\0\0\^D\0\0\0\^C\0\0\0#\^Z\
<br> \0\0#\^Z\0\0#\^Z\0\0\^S\0\0\0\^S\0\0\0\^D\0\0\0\^A\0\0\0\^A\0\0\0\0\0\
<br> \0\0\0\0\0\0\0\0\0\0\M-l\^[\0\0\M-l\^[\0\0\^E\0\0\0\0\^P\0\0\^A\0\0\0\
<br> \M-4\^^\0\0\M-4.\0\0\M-4.\0\0\M^X\^A\0\0\M-H\^A\0\0\^F\0\0\0\0\^P\0\0\
<br> \^B\0\0\0\M-P\^^\0\0\M-P.\0\0\M-P.\0\0\M-x\0\0\0\M-x\0\0\0\^F\0\0\0\^D\
<br> \0\0\0\^D\0\0\0T\^A\0\0T\^A\0\0T\^A\0\0 \0\0\0 \0\0\0\^D\0\0\0\^D\0\0\
<br> \0Q\M-etd\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^F\0\0\0\^D\0\0\0R\
<br> \M-etd\M-4\^^\0\0\M-4.\0\0\M-4.\0\0L\^A\0\0L\^A\0\0\^D\0\0\0\^A\0\0\0\
<br> \M^@\^U\^De\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0(\0\0\^D\0\0\0\^D\
<br> \0\0\0\^P\0\0\0\^A\0\0\0GNU\0\0\0\0\0\^B\0\0\0\^F\0\0\0 \0\0\0\^V\0\0\
<br> \0\^Y\0\0\0\^D\0\0\0\a\0\0\0\M^X\0\^Q\0\0B\0\0\M^B\0`\b\M^S(\b\M-^\^Y\
<br> \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^Z\0\0\0\0\0\0\0\^[\0\0\0\^\\0\0\0\0\0\
<br> \0\0\^^\0\0\0\0\0\0\0\0\0\0\0\^_\0\0\0!\0\0\0"\0\0\0\0\0\0\0\0\0\0\0#\
<br> \0\0\0%\0\0\0&\0\0\0\0\0\0\0(\0\0\0\M^Q!\M-|\M-x\M^U\M-3_\^Y\^E\M-h\a\
<br> \M-y\^F\^B\^D\M-y\a\^B\^D\M-y"
<br> 32645 hasplmd RET read 512/0x200
<br> 32645 hasplmd CALL linux_fstat64(0x3,0xbfbfe354,0x28062fd4)
<br> 32645 hasplmd UNKNOWN(8) 32645 hasplmd RET linux_fstat64 0
<br> 32645 hasplmd CALL linux_mmap2(0,0x307c,0x5,0x802,0x3,0)
<br> 32645 hasplmd RET linux_mmap2 671764480/0x280a5000
<br> 32645 hasplmd CALL linux_mmap2(0x280a7000,0x2000,0x3,0x812,0x3,0x1)
<br> 32645 hasplmd RET linux_mmap2 671772672/0x280a7000
<br> 32645 hasplmd CALL close(0x3)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL linux_open(0x2806682c,0,0x72)
<br> 32645 hasplmd NAMI "/compat/linux/lib/libc.so.6"
<br> 32645 hasplmd NAMI "/compat/linux"
<br> 32645 hasplmd NAMI "/compat/linux/lib/libc.so.6"
<br> 32645 hasplmd RET linux_open 3
<br> 32645 hasplmd CALL read(0x3,0xbfbfe430,0x200)
<br> 32645 hasplmd GIO fd 3 read 512 bytes
<br> "\^?ELF\^A\^A\^A\0\0\0\0\0\0\0\0\0\^C\0\^C\0\^A\0\0\0@a\^A\0004\0\0\0\
<br> \^T\M-V\^R\0\0\0\0\0004\0 \0\v\0(\0B\0A\0\^F\0\0\0004\0\0\0004\0\0\000\
<br> 4\0\0\0`\^A\0\0`\^A\0\0\^E\0\0\0\^D\0\0\0\^C\0\0\0\0n\^Q\0\0n\^Q\0\0n\
<br> \^Q\0\^S\0\0\0\^S\0\0\0\^D\0\0\0\^A\0\0\0\^A\0\0\0\0\0\0\0\0\0\0\0\0\0\
<br> \0\0\240\M^_\^R\0\240\M^_\^R\0\^E\0\0\0\0\^P\0\0\^A\0\0\0\M-\\M-!\^R\0\
<br> \M-\\M-!\^R\0\M-\\M-!\^R\0\240'\0\0\M-tS\0\0\^F\0\0\0\0\^P\0\0\^B\0\0\
<br> \0|\M-=\^R\0|\M-=\^R\0|\M-=\^R\0\M-x\0\0\0\M-x\0\0\0\^F\0\0\0\^D\0\0\0\
<br> \^D\0\0\0\M^T\^A\0\0\M^T\^A\0\0\M^T\^A\0\0 \0\0\0 \0\0\0\^D\0\0\0\^D\0\
<br> \0\0\a\0\0\0\M-\\M-!\^R\0\M-\\M-!\^R\0\M-\\M-!\^R\0\b\0\0\0@\0\0\0\^D\
<br> \0\0\0\^D\0\0\0P\M-etd\^Tn\^Q\0\^Tn\^Q\0\^Tn\^Q\0\M^\)\0\0\M^\)\0\0\^D\
<br> \0\0\0\^D\0\0\0Q\M-etd\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^F\0\0\
<br> \0\^D\0\0\0R\M-etd\M-\\M-!\^R\0\M-\\M-!\^R\0\M-\\M-!\^R\0$\^^\0\0$\^^\
<br> \0\0\^D\0\0\0\^A\0\0\0\M^@\^U\^De\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
<br> \0\0\0(\0\0\^D\0\0\0\^D\0\0\0\^P\0\0\0\^A\0\0\0GNU\0\0\0\0\0\^B\0\0\0\
<br> \^F\0\0\0 \0\0\0\M-s\^C\0\0
<br> \0\0\0\0\^B\0\0\^N\0\0\0\2400\^PD\0\0\^B\^A\M^L\^C\M-f\M^PAE\M^H\0\M^D\
<br> \0\b\0A\M^@\0@\M-@\M^@\0\f\^B\f\0\^A0\0\b@"\b\M-&\^D\M^HH6l\240\^V0\0&\
<br> \M^D\M^@\M^N\^D\bB$\^B\f\M-&\M-$"
<br> 32645 hasplmd RET read 512/0x200
<br> 32645 hasplmd CALL linux_fstat64(0x3,0xbfbfe338,0x28062fd4)
<br> 32645 hasplmd UNKNOWN(8) 32645 hasplmd RET linux_fstat64 0
<br> 32645 hasplmd CALL linux_mmap2(0,0x12f5d0,0x5,0x802,0x3,0)
<br> 32645 hasplmd RET linux_mmap2 671780864/0x280a9000
<br> 32645 hasplmd CALL linux_mmap2(0x281d3000,0x3000,0x3,0x812,0x3,0x12a)
<br> 32645 hasplmd RET linux_mmap2 673001472/0x281d3000
<br> 32645 hasplmd CALL linux_mmap2(0x281d6000,0x25d0,0x3,0x32,0xffffffff,0)
<br> 32645 hasplmd RET linux_mmap2 673013760/0x281d6000
<br> 32645 hasplmd CALL close(0x3)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL linux_mmap2(0,0x1000,0x3,0x22,0xffffffff,0)
<br> 32645 hasplmd RET linux_mmap2 673026048/0x281d9000
<br> 32645 hasplmd CALL linux_set_thread_area(0xbfbfe888)
<br> 32645 hasplmd RET linux_set_thread_area 0
<br> 32645 hasplmd CALL linux_mprotect(0x281d3000,0x2000,0x1)
<br> 32645 hasplmd RET linux_mprotect 0
<br> 32645 hasplmd CALL linux_mprotect(0x280a7000,0x1000,0x1)
<br> 32645 hasplmd RET linux_mprotect 0
<br> 32645 hasplmd CALL linux_mprotect(0x280a1000,0x1000,0x1)
<br> 32645 hasplmd RET linux_mprotect 0
<br> 32645 hasplmd CALL linux_mprotect(0x2808b000,0x1000,0x1)
<br> 32645 hasplmd RET linux_mprotect 0
<br> 32645 hasplmd CALL linux_mprotect(0x28062000,0x1000,0x1)
<br> 32645 hasplmd RET linux_mprotect 0
<br> 32645 hasplmd CALL munmap(0x28064000,0x2a86)
<br> 32645 hasplmd RET munmap 0
<br> 32645 hasplmd CALL linux_set_tid_address(0x281d9708)
<br> 32645 hasplmd RET linux_set_tid_address 32645/0x7f85
<br> 32645 hasplmd CALL linux_set_robust_list(0x281d9710,0xc)
<br> 32645 hasplmd RET linux_set_robust_list 0
<br> 32645 hasplmd CALL linux_rt_sigaction(0x20,0xbfbfe84c,0,0x8)
<br> 32645 hasplmd RET linux_rt_sigaction 0
<br> 32645 hasplmd CALL linux_rt_sigaction(0x21,0xbfbfe84c,0,0x8)
<br> 32645 hasplmd RET linux_rt_sigaction 0
<br> 32645 hasplmd CALL linux_rt_sigprocmask(0x1,0xbfbfeb08,0,0x8)
<br> 32645 hasplmd RET linux_rt_sigprocmask 0
<br> 32645 hasplmd CALL linux_getrlimit(0x3,0xbfbfeb90)
<br> 32645 hasplmd RET linux_getrlimit 0
<br> 32645 hasplmd CALL linux_newuname(0xbfbfe904)
<br> 32645 hasplmd RET linux_newuname 0
<br> 32645 hasplmd CALL linux_gettid
<br> 32645 hasplmd RET linux_gettid 32645/0x7f85
<br> 32645 hasplmd CALL linux_brk(0)
<br> 32645 hasplmd RET linux_brk 135712768/0x816d000
<br> 32645 hasplmd CALL linux_brk(0x818e000)
<br> 32645 hasplmd RET linux_brk 135712768/0x816d000
<br> 32645 hasplmd CALL linux_mmap2(0,0x100000,0x3,0x22,0xffffffff,0)
<br> 32645 hasplmd RET linux_mmap2 673030144/0x281da000
<br> 32645 hasplmd CALL linux_sys_futex(0x280a8070,0x1,0x7fffffff,0,0x8340bac,0xbfbfc300)
<br> 32645 hasplmd RET linux_sys_futex 0
<br> 32645 hasplmd CALL linux_getrlimit(0x7,0xbfbfea74)
<br> 32645 hasplmd RET linux_getrlimit 0
<br> 32645 hasplmd CALL close(0)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL close(0x1)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL close(0x2)
<br> 32645 hasplmd RET close 0
<br> 32645 hasplmd CALL close(0x3)
<br> 32645 hasplmd RET close -1 errno 9 Bad file descriptor
<br> 32645 hasplmd CALL close(0x4)
<br> 32645 hasplmd RET close -1 errno 9 Bad file descriptor
<br> 32645 hasplmd CALL close(0x5)
<br> 32645 hasplmd RET close -1 errno 9 Bad file descriptor
<br> 32645 hasplmd CALL close(0x6)
<br> 32645 hasplmd RET close -1 errno 9 Bad file descriptor
<br><br>Next contuiously call close() with argument from 0x7 to 0x2b55.
<br>And always RET close -1 errno 9 Bad file descriptor
<br><br> 32645 hasplmd CALL close(0x2b56)
<br> 32645 hasplmd RET close -1 errno 9 Bad file descriptor
<br> 32645 hasplmd CALL linux_open(0x815f2b2,0,0xffffffc8)
<br> 32645 hasplmd NAMI "/compat/linux/dev/null"
<br> 32645 hasplmd NAMI "/dev/null"
<br> 32645 hasplmd RET linux_open 0
<br> 32645 hasplmd CALL linux_open(0x815f2b2,0x1,0xffffffc8)
<br> 32645 hasplmd NAMI "/compat/linux/dev/null"
<br> 32645 hasplmd NAMI "/dev/null"
<br> 32645 hasplmd RET linux_open 1
<br> 32645 hasplmd CALL dup(0x1)
<br> 32645 hasplmd RET dup 2
<br> 32645 hasplmd CALL linux_clone(0x1200011,0,0,0,0x281d9708)
<br> 32645 hasplmd RET linux_clone 32646/0x7f86
<br> 32645 hasplmd CALL linux_exit_group(0)
<br><br>Bye. Serg
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26863977&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26863977&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26857146Re: ports/127018: Linuxulator incapable of using FreeBSD's LDAP environment2009-12-19T09:51:25Z2009-12-19T09:51:25ZPav LucistnikSynopsis: Linuxulator incapable of using FreeBSD's LDAP environment
<br><br>State-Changed-From-To: feedback->closed
<br>State-Changed-By: pav
<br>State-Changed-When: Sat Dec 19 17:50:20 UTC 2009
<br>State-Changed-Why:
<br>No activity for a year, feedback timeout, probably not ports related at all
<br><br><a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=127018" target="_top" rel="nofollow">http://www.freebsd.org/cgi/query-pr.cgi?pr=127018</a><br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26857146&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26857146&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26854691Re: [WIP] wine/i386 on FreeBSD/amd64 (take 2)2009-12-19T04:32:56Z2009-12-19T04:32:56ZDavid Bruce NaylorOn Saturday 19 December 2009 00:19:41 Brian Hechinger wrote:
<div class='shrinkable-quote'><div class='shrinkable-quote'><br>> On Fri, Dec 18, 2009 at 11:27:15PM +0200, David Naylor wrote:
<br>> > > (On FreeBSD/amd64)
<br>> > > # pkg_add wine-amd64-8-1.1.34,1.tbz
<br>> >
<br>> > (package name changed)
<br>> > # pkg_add wine-amd64.8-1.1.34,1.tbz
<br>>
<br>> Will this have everything we need in order to run it, even with nvidia
<br>> drivers? Since nvidia-driver doesn't have the latest BETA drivers in it, I
<br>> can't really use that to install the drivers on amd64.
</div></div>Yes it will. I've missed some soft dependencies but that will be fixed soon.
<br>If you grab the x86 version of the beta driver then all you need are:
<br>libGL.so.1
<br>libGLcore.so.1
<br>libnvidia-tls.so.1
<br><br>And copy them into /usr/local/lib32
<br><br>(To fix the soft dependencies copy across libXrender.so.1 and libfreetype.so.9
<br>from i386 to /usr/local/lib32)
<br><br>> > The above method still does work but now, if one installs nvidia-driver
<br>> > (of the correct version) before building wine under FreeBSD/i386 then the
<br>> > required libraries will be included (this makes the package unsuitable
<br>> > for any system without the correct nvidia drivers installed).
<br>>
<br>> Again, same thing. The drivers I'm going to need on amd64 are not the ones
<br>> that are going to be installed via nvidia-driver on i386, right?
<br><br>Yes, the kld will complain about a version mismatch and not work. See above.
<br><br>It will only grab the nvidia shared libraries if the nvidia driver is
<br>installed before the package is built.
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (203 bytes) <a href="http://old.nabble.com/attachment/26854691/0/signature.asc" target="_top">Download Attachment</a></div>tag:old.nabble.com,2006:post-26850477Re: [WIP] wine/i386 on FreeBSD/amd64 (take 2)2009-12-18T14:19:41Z2009-12-18T14:19:41Zwonko-2On Fri, Dec 18, 2009 at 11:27:15PM +0200, David Naylor wrote:
<br>> > (On FreeBSD/amd64)
<br>> > # pkg_add wine-amd64-8-1.1.34,1.tbz
<br>>
<br>> (package name changed)
<br>> # pkg_add wine-amd64.8-1.1.34,1.tbz
<br><br>Will this have everything we need in order to run it, even with nvidia drivers?
<br>Since nvidia-driver doesn't have the latest BETA drivers in it, I can't really
<br>use that to install the drivers on amd64.
<br><br>> The above method still does work but now, if one installs nvidia-driver (of
<br>> the correct version) before building wine under FreeBSD/i386 then the required
<br>> libraries will be included (this makes the package unsuitable for any system
<br>> without the correct nvidia drivers installed).
<br><br>Again, same thing. The drivers I'm going to need on amd64 are not the ones that
<br>are going to be installed via nvidia-driver on i386, right?
<br><br>-brian
<br>--
<br>"Coding in C is like sending a 3 year old to do groceries. You gotta
<br>tell them exactly what you want or you'll end up with a cupboard full of
<br>pop tarts and pancake mix." -- IRC User (<a href="http://www.bash.org/?841435" target="_top" rel="nofollow">http://www.bash.org/?841435</a>)
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26850477&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26850477&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26849951[WIP] wine/i386 on FreeBSD/amd64 (take 2)2009-12-18T13:27:15Z2009-12-18T13:27:15ZDavid Bruce NaylorOn Tuesday 08 December 2009 15:24:00 David Naylor wrote:
<br>> Hi,
<br>>
<br>> I have developed a port that allows wine to be installed as a package under
<br>> FreeBSD/amd64. This avoids having a i386 chroot environment (and is much
<br>> easier to setup, once the package is built).
<br><br>I've changes the name of the port (should be obvious what it is for and not
<br>conflict when wine/amd64 arrives). The port now also automagically determines
<br>which third party shared libraries should be bundled with it. (See below on
<br>how to handle nvidia-driver).
<br><br>> To get this working apply the attached patch and build the emulators/wine-
<br>> amd64 port under FreeBSD/i386 then transfer that package to the amd64 host:
<br>>
<br>> (On FreeBSD/i386)
<br>> # cd /usr/ports/emulators
<br>> # patch < /tmp/wine-amd64.diff
<br><br>(patch name changed, fix arguments)
<br># patch -sp0 < /tmp/wine-fbsd64.diff
<br><br>> # cd wine-amd64
<br>> # make package clean
<br>>
<br>> (On FreeBSD/amd64)
<br>> # pkg_add wine-amd64-8-1.1.34,1.tbz
<br><br>(package name changed)
<br># pkg_add wine-amd64.8-1.1.34,1.tbz
<br><br>> I have such a package for FreeBSD-8 if anyone is willing to host it.
<br><br>I'll update the patch when wine-1.1.35 gets into my ports.
<br><br>> There are a few TODO items (port options not supported). Any
<br>> comments/suggestions are welcome.
<br><br>1) Install from package on FreeBSD/amd64 (any suggestions on how to do that?)
<br>2) Which version of FreeBSD/amd64 supports FreeBSD/i386 well enough to run
<br>wine?
<br>3) Any bugs reported?
<br><br>> Word of warning: nvidia-driver breaks everything. Make sure it is not
<br>> installed on both i386/amd64 systems. If one really wants wine with
<br>> nvidia- driver support then install the beta on both i386 and amd64 (very
<br>> important it is the same version of the driver) and copy libGL.so.1,
<br>> libGLcore.so.1 and libnvidia-tls.so.1 from i386 to $PREFIX/lib32 (on
<br>> amd64).
<br><br>The above method still does work but now, if one installs nvidia-driver (of
<br>the correct version) before building wine under FreeBSD/i386 then the required
<br>libraries will be included (this makes the package unsuitable for any system
<br>without the correct nvidia drivers installed).
<br><br>Regards,
<br><br>David
<br><br>P.S. I've included the shar archive as some people have not been able to apply
<br>the patch cleanly
<br><br /><tt>[wine-fbsd64.diff]</tt><br /><hr align="left" width="300" /><tt>diff -uNr /usr/ports/emulators/wine/Makefile wine/Makefile
<br>--- /usr/ports/emulators/wine/Makefile 2009-12-08 08:27:51.000000000 +0200
<br>+++ wine/Makefile 2009-12-18 23:17:27.000000000 +0200
<br>@@ -30,12 +30,10 @@
<br> --without-sane --without-xcursor
<br> CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
<br> LDFLAGS="-L${LOCALBASE}/lib"
<br>-USE_LDCONFIG= ${PREFIX}/lib ${PREFIX}/lib/wine
<br> MAKE_JOBS_SAFE= yes
<br> MAN1= widl.1 wine.1 winebuild.1 winedbg.1 winedump.1 winegcc.1 \
<br> winemaker.1 wineprefixcreate.1 wineserver.1 wmc.1 wrc.1
<br> MLINKS= winegcc.1 wineg++.1
<br>-ONLY_FOR_ARCHS= i386
<br> USE_BISON= build
<br> USE_BZIP2= yes
<br> USE_GMAKE= yes
<br>@@ -80,10 +78,33 @@
<br> CONFIGURE_ARGS+= --without-xslt
<br> .endif
<br>
<br>+# TODO: when does FreeBSD/i386 work properly under FreeBSD/amd64?
<br> .if ${OSVERSION} < 603000
<br> IGNORE= fails to properly work on versions of FreeBSD before 6.3
<br> .endif
<br>
<br>+.ifdef WINE_CROSS_BUILD
<br>+
<br>+CONFIGURE_ENV+= MACHINE=i386 UNAME_m=i386 UNAME_p=i386
<br>+CONFLICTS= wine-[0-9]*
<br>+ONLY_FOR_ARCHS= i386 amd64
<br>+USE_LDCONFIG32= ${PREFIX}/lib32 ${PREFIX}/lib32/wine
<br>+WINELIBDIR=${PREFIX}/lib32
<br>+
<br>+PLIST_REINPLACE+= winelib
<br>+PLIST_REINPLACE_WINELIB=s!lib/!lib32/!g
<br>+
<br>+ACTUAL-PACKAGE-DEPENDS=${DO_NADA}
<br>+
<br>+.else
<br>+
<br>+CONFLICTS= wine-fbsd64.*
<br>+ONLY_FOR_ARCHS= i386
<br>+USE_LDCONFIG= ${PREFIX}/lib ${PREFIX}/lib/wine
<br>+WINELIBDIR=${PREFIX}/lib
<br>+
<br>+.endif
<br>+
<br> post-patch:
<br> .if ${OSVERSION} < 700041
<br> ${REINPLACE_CMD} 's/-lpthread/-lthr/g' ${WRKSRC}/configure
<br>@@ -99,8 +120,8 @@
<br> ${MAN1PREFIX}/man/fr.UTF-8/man1/wineserver.1
<br> @-${RMDIR} -p ${MAN1PREFIX}/man/de.UTF-8/man1 \
<br> ${MAN1PREFIX}/man/fr.UTF-8/man1
<br>- ${MV} -f ${PREFIX}/lib/libwine.so.1.0 ${PREFIX}/lib/libwine.so.1
<br>- ${LN} -sf libwine.so.1 ${PREFIX}/lib/libwine.so
<br>+ ${MV} -f ${WINELIBDIR}/libwine.so.1.0 ${WINELIBDIR}/libwine.so.1
<br>+ ${LN} -sf libwine.so.1 ${WINELIBDIR}/libwine.so
<br> .if !defined(NOPORTDOCS)
<br> -@${MKDIR} ${DOCSDIR}
<br> .for i in README ANNOUNCE AUTHORS LICENSE
<br>@@ -109,6 +130,23 @@
<br> @${INSTALL_DATA} ${WRKSRC}/programs/winedbg/README ${DOCSDIR}/README.winedbg
<br> @${INSTALL_DATA} ${WRKSRC}/tools/winedump/README ${DOCSDIR}/README.winedump
<br> .endif
<br>+.ifdef WINE_CROSS_BUILD
<br>+ grep -v '[@%]' ${TMPPLIST} | sed "s!^!${PREFIX}/!g" | \
<br>+ xargs -n1 file -F' ' | grep ELF | cut -f1 -d' ' | \
<br>+ env LD_LIBRARY_PATH=${PREFIX}/lib32:${LD_LIBRARY_PATH} xargs ldd -f '%p\n' \
<br>+ | sort -u | grep -v '^\(/usr\)\?/lib' | grep -v "^${PREFIX}/lib32/libwine.so" \
<br>+ | grep -v "^${PREFIX}/lib32/wine" > ${WRKDIR}/winelibs.list
<br>+ for i in `cat ${WRKDIR}/winelibs.list` ; do \
<br>+ ${INSTALL_DATA} $${i} ${PREFIX}/lib32/ ; \
<br>+ echo lib32/`basename $${i}` >> ${TMPPLIST} ; \
<br>+ done
<br>+ ${INSTALL_SCRIPT} ${FILESDIR}/binbounce ${PREFIX}/bin/wine
<br>+ for i in `grep ^bin ${TMPPLIST} | xargs -n1 basename` ; do \
<br>+ [ "$${i}" = "wine" ] || ${LN} -sf wine ${PREFIX}/bin/$${i} ; \
<br>+ echo bin32/$${i} >> ${TMPPLIST} ; \
<br>+ done
<br>+ echo '@unexec rmdir %D/bin32 2>/dev/null || true' >> ${TMPPLIST}
<br>+.endif
<br> @${MKDIR} ${DESKTOPDIR}
<br> @${MV} ${DATADIR}/applications/wine.desktop ${DESKTOPDIR}/
<br> @${ECHO}
<br>diff -uNr /usr/ports/emulators/wine/files/binbounce wine/files/binbounce
<br>--- /usr/ports/emulators/wine/files/binbounce 1970-01-01 02:00:00.000000000 +0200
<br>+++ wine/files/binbounce 2009-12-01 13:54:52.000000000 +0200
<br>@@ -0,0 +1,15 @@
<br>+#!/bin/sh
<br>+
<br>+LOCALBASE=`dirname $0`/..
<br>+BINNAME=`basename $0`
<br>+
<br>+while [ $# -gt 0 ]
<br>+do
<br>+ ARGS="$ARGS \"$1\""
<br>+ shift
<br>+done
<br>+
<br>+
<br>+export LD_32_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine
<br>+export PATH=$LOCALBASE/bin32:$PATH
<br>+eval exec $LOCALBASE/bin32/$BINNAME $ARGS
<br>diff -uNr /usr/ports/emulators/wine-fbsd64/ChangeLog wine-fbsd64/ChangeLog
<br>--- /usr/ports/emulators/wine-fbsd64/ChangeLog 1970-01-01 02:00:00.000000000 +0200
<br>+++ wine-fbsd64/ChangeLog 2009-12-18 23:16:58.000000000 +0200
<br>@@ -0,0 +1,9 @@
<br>+2009/12/18:
<br>+ * Rename to something with a little more sense (wine-amd64-[V] -> wine-fbsd64.[V])
<br>+ * Fix conflicts (wine conflicts with wine-fbsd64)
<br>+
<br>+2009/12/17:
<br>+ * Automatically determine libraries and binaries
<br>+
<br>+2009/12/08:
<br>+ * Initial implementation of WINE/i386 on FreeBSD/amd64
<br>diff -uNr /usr/ports/emulators/wine-fbsd64/Makefile wine-fbsd64/Makefile
<br>--- /usr/ports/emulators/wine-fbsd64/Makefile 1970-01-01 02:00:00.000000000 +0200
<br>+++ wine-fbsd64/Makefile 2009-12-18 19:44:47.000000000 +0200
<br>@@ -0,0 +1,12 @@
<br>+PORTNAME= wine
<br>+PKGNAMESUFFIX= -fbsd64.${OSVERSION:C/([0-9]).*/\1/}
<br>+
<br>+WINE_CROSS_BUILD=yes
<br>+
<br>+MASTERDIR= ${.CURDIR}/../wine
<br>+
<br>+#.if ${ARCH} == "amd64"
<br>+# TODO: install from package (how?)
<br>+#.endif
<br>+
<br>+.include "${MASTERDIR}/Makefile"
<br></tt><hr align="left" width="300" /><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (203 bytes) <a href="http://old.nabble.com/attachment/26849951/0/signature.asc" target="_top">Download Attachment</a></div>tag:old.nabble.com,2006:post-26833821Re: linux-f10-alsa-lib should be updated2009-12-17T11:45:29Z2009-12-17T11:45:29ZBoris SamorodovGrzegorz Blach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26833821&i=0" target="_top" rel="nofollow">magik@...</a>> writes:
<br><br>> On fedora servers, curretly is only alsa-lib-1.0.21-2.fc10.i386.rpm,
<br>> there is no more alsa-lib-1.0.21-1.fc10.i386.rpm, so port should be
<br>> updated.
<br><br>Fixed, thanks.
<br><br>--
<br>WBR, bsam
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26833821&i=1" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26833821&i=2" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>tag:old.nabble.com,2006:post-26829749VirtualBox: killing DMA2009-12-17T07:29:03Z2009-12-17T07:29:03ZDavid Bruce NaylorHi,
<br><br>I am having problems where network I/O on a FreeBSD guest within VirtualBox
<br>ends up killing the host. Here is my setup:
<br><br>Host: FreeBSD 8 RC2 /amd64
<br>Guest: FreeBSD-current (~week old) /i386
<br>VirtualBox: virtualbox-3.0.51.r22902_2 (bridged to my dc0)
<br><br>I've tried multiple configurations all resulting in the same problem. The
<br>most conservative configuration:
<br><br>Machine: VT disabled
<br>Host: hw.ata.ata_dma=0, hw.ata.atapi_dma=0 (safe mode didn't work)
<br>Guest: safe mode
<br>VirtualBox: VT and APIC disabled
<br><br>I can cause the problem by doing (in the guest):
<br><br># mount -t smbfs //server/tmp /mnt
<br># dd if=/mnt/big_file of=/tmp bs=1k
<br><br>The error messages on the host are:
<br>ad8: FAILED - load data
<br>ad8: setting up DMA failed
<br>g_vfs_done(): ad8s1d[WRITE(offset=65536, length=2048)]error = 5
<br>...
<br>(many g_vfs_done messages, with different partition, offset and length)
<br>...
<br>panic: initiate_write_inodeblock_ufs2: already started
<br><br>If I disable the network interface (from VirtualBox for the guest) then I
<br>cannot produce the above.
<br><br>Regards,
<br><br>David
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (203 bytes) <a href="http://old.nabble.com/attachment/26829749/0/signature.asc" target="_top">Download Attachment</a></div>tag:old.nabble.com,2006:post-26829094Re: Wine on FreeBSD/amd642009-12-17T06:47:39Z2009-12-17T06:47:39Zwonko-2On Wed, Dec 16, 2009 at 10:57:56PM +0000, Sam Fourman Jr. wrote:
<br>>
<br>> i could only get the alias to work if i changed by shell to bash so
<br>> now I use this in my ~/.bashrc
<br><br>I get the same exact error with bash. So I must be missing something else.
<br><br>-brian
<br>--
<br>"Coding in C is like sending a 3 year old to do groceries. You gotta
<br>tell them exactly what you want or you'll end up with a cupboard full of
<br>pop tarts and pancake mix." -- IRC User (<a href="http://www.bash.org/?841435" target="_top" rel="nofollow">http://www.bash.org/?841435</a>)
<br>_______________________________________________
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26829094&i=0" target="_top" rel="nofollow">freebsd-emulation@...</a> mailing list
<br><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" target="_top" rel="nofollow">http://lists.freebsd.org/mailman/listinfo/freebsd-emulation</a><br>To unsubscribe, send any mail to "<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26829094&i=1" target="_top" rel="nofollow">freebsd-emulation-unsubscribe@...</a>"
<br>