Date: Thu, 24 Jun 2010 18:57:35 +0400 From: Mikle Krutov <nekoexmachina@gmail.com> To: xorquewasp@googlemail.com Cc: freebsd-questions@freebsd.org Subject: Re: i386 wine on amd64 - DRI a lost cause? Message-ID: <AANLkTineUZt_BsceUMwM1XoAQ9MA5CVeyC7CUOj4Ve00@mail.gmail.com> In-Reply-To: <20100624121141.GA40498@logik.internal.network> References: <20100624121141.GA40498@logik.internal.network>
next in thread | previous in thread | raw e-mail | index | archive | help
You need 32bit libGL and all mesa stuff to have dri with i386 apps on amd64 system. Also i've used http://msnp.ru/file/wine-fbsd64.zip port, not the by-hand-way while using amd64. Worked for me on both radeon and nvidia card. 2010/6/24, xorquewasp@googlemail.com <xorquewasp@googlemail.com>: > I have a full i386 tree installed at /jail/wine (ignore the 'jail' in > the name, I'll run it as a plain chroot if necessary) created with 'make > buildworld TARGET=i386'. > > I've built and installed wine into the jail/chroot and it works fine. > The problem: I can't get any kind of DRI to work in the jail/chroot. DRI > is working fine on the host system. Any program that attempts to use DRI > in the chroot/jail immediately segfaults. > > I built and installed a 32 bit version of graphics/dri into the > jail/chroot as glxinfo reported that direct rendering was disabled due > to missing files. I then made /dev/dri visible in the jail/chroot. > > Can an i386 version of DRI not talk to an amd64 kernel? Is there some > other way I should be doing this? > > I'm using a radeon card that uses r300_dri.so, if that's at all > significant. > > Regards, xw > > PS: Please CC as I'm not subscribed. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- with best regards, Krutov Mikle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTineUZt_BsceUMwM1XoAQ9MA5CVeyC7CUOj4Ve00>