Re: i386 wine on amd64 - DRI a lost cause?
On 2010-07-03 19:30:36, Jonathan Chen wrote: > I'm got (unjailed) wine/i386 on amd64, and it plays DirectX 9 games > with no problems; eg EVE-Online. I'm using the nvidia-drivers, which > have to be installed on the 32-bit base, as well as the 64-bit driver > on the /usr/local Have noticed that everybody that has said it works is using the nvidia drivers (whilst I'm using the open ATI drivers)... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
On Fri, Jul 02, 2010 at 09:04:43AM +0200, David Naylor wrote: > On Friday 02 July 2010 01:35:05 xorquew...@googlemail.com wrote: > > On 2010-07-01 22:16:26, David Naylor wrote: > > > Have you tried the packages from http://people.freebsd.org/~ivoras/wine/ > > > > > > They worked for me with nvidia and intel. > > > > Thanks, but as I mentioned in the hackers@ thread (and possibly this one), > > it's actually DRI that's the problem. I can't even run 32-bit glxinfo > > reliably in the chroot. libGL often receives EFAULT when doing various > > ioctls on /dev/dri/card0 and sometimes crashes outright. > > That is interesting as I am able to play Warcraft 3 on an intel laptop. I > don't think it is using software rendering. Wine runs without crashing and > does require libGL to launch the game. > > I have also played Command and Conquer 3 on nvidia (but the proprietry nvidia > driver does not use dri). I'm got (unjailed) wine/i386 on amd64, and it plays DirectX 9 games with no problems; eg EVE-Online. I'm using the nvidia-drivers, which have to be installed on the 32-bit base, as well as the 64-bit driver on the /usr/local -- Jonathan Chen | To do is to be -- Nietzsche | To be is to do -- Sartre | Scooby do be do -- Scooby ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
On Friday 02 July 2010 01:35:05 xorquew...@googlemail.com wrote: > On 2010-07-01 22:16:26, David Naylor wrote: > > Have you tried the packages from http://people.freebsd.org/~ivoras/wine/ > > > > They worked for me with nvidia and intel. > > Thanks, but as I mentioned in the hackers@ thread (and possibly this one), > it's actually DRI that's the problem. I can't even run 32-bit glxinfo > reliably in the chroot. libGL often receives EFAULT when doing various > ioctls on /dev/dri/card0 and sometimes crashes outright. That is interesting as I am able to play Warcraft 3 on an intel laptop. I don't think it is using software rendering. Wine runs without crashing and does require libGL to launch the game. I have also played Command and Conquer 3 on nvidia (but the proprietry nvidia driver does not use dri). Good luck signature.asc Description: This is a digitally signed message part.
Re: i386 wine on amd64 - DRI a lost cause?
On 2010-07-01 22:16:26, David Naylor wrote: > > Have you tried the packages from http://people.freebsd.org/~ivoras/wine/ > > They worked for me with nvidia and intel. Thanks, but as I mentioned in the hackers@ thread (and possibly this one), it's actually DRI that's the problem. I can't even run 32-bit glxinfo reliably in the chroot. libGL often receives EFAULT when doing various ioctls on /dev/dri/card0 and sometimes crashes outright. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
On Thursday 01 July 2010 14:00:06 xorquew...@googlemail.com wrote: > On 2010-07-01 15:28:00, Mikle Krutov wrote: > > Sorry for late-answer, but why are you running wine in jail? > > May be that's the source of the problem. > > For me, it was just installed into /usr/local/ as some other > > > > program, some 32bit libs were in lib32, and so on. > > As mentioned, I've tried it in a jail, a plain chroot and also completely > unchrooted and unjailed. > > Wine itself works fine but DRI doesn't. > > I recently wrote to freebsd-hackers@ and the response wasn't exactly > positive. Seems 32-bit DRI is basically expected to fail when talking > to a 64-bit kernel. Wine's not the one at fault here. Have you tried the packages from http://people.freebsd.org/~ivoras/wine/ They worked for me with nvidia and intel. Regards, David signature.asc Description: This is a digitally signed message part.
Re: i386 wine on amd64 - DRI a lost cause?
On 2010-07-01 23:37:37, Mikle Krutov wrote: > Well, then i do not get why i was albe to play > some 3d games on wine with fbsd 8.0 amd64 > about when 8.0 was released. > Also > http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d I don't either. I've tried every possible combination including the contents of that wiki page. I've spoken to people who should know and I get generally disinterested replies along the lines of "it probably doesn't work". It's extremely frustrating. Thanks for the responses, anyway. I've pretty much given up at this point. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
Well, then i do not get why i was albe to play some 3d games on wine with fbsd 8.0 amd64 about when 8.0 was released. Also http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d 2010/7/1, xorquew...@googlemail.com : > On 2010-07-01 15:28:00, Mikle Krutov wrote: >> Sorry for late-answer, but why are you running wine in jail? >> May be that's the source of the problem. >> For me, it was just installed into /usr/local/ as some other >> program, some 32bit libs were in lib32, and so on. > > As mentioned, I've tried it in a jail, a plain chroot and also completely > unchrooted and unjailed. > > Wine itself works fine but DRI doesn't. > > I recently wrote to freebsd-hackers@ and the response wasn't exactly > positive. Seems 32-bit DRI is basically expected to fail when talking > to a 64-bit kernel. Wine's not the one at fault here. > > Regards, > xw > -- with best regards, Krutov Mikle ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
Sorry for late-answer, but why are you running wine in jail? May be that's the source of the problem. For me, it was just installed into /usr/local/ as some other program, some 32bit libs were in lib32, and so on. 2010/6/25, xorquew...@googlemail.com : > On 2010-06-24 18:57:35, Mikle Krutov wrote: >> 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. > > Yes, I have those. Here's a list of all ports installed in the i386 > jail (they were built in the jail itself so are definitely 32 bit): > > bash-4.0.35 The GNU Project's Bourne Again SHell > damageproto-1.1.0_2 Damage extension headers > dri-7.4.4,2 OpenGL hardware acceleration drivers for the DRI > dri2proto-2.1 DRI2 prototype headers > expat-2.0.1_1 XML 1.0 parser written in C > fixesproto-4.0 Fixes extension headers > fontconfig-2.8.0,1 An XML-based font configuration API for X Windows > freetype2-2.3.11A free and portable TrueType font rendering engine > gettext-0.17_1 GNU gettext package > inputproto-1.5.0Input extension headers > jpeg-8_1IJG's jpeg compression utilities > kbproto-1.0.3 KB extension headers > lcms-1.19_1,1 Light Color Management System -- a color management > library > libGL-7.4.4 OpenGL library that renders using GLX or DRI > libGLU-7.4.4OpenGL utility library > libICE-1.0.4_1,1Inter Client Exchange library for X11 > libSM-1.1.0_1,1 Session Management library for X11 > libX11-1.2.1_1,1X11 library > libXau-1.0.4Authentication Protocol library for X11 > libXdamage-1.1.1X Damage extension library > libXdmcp-1.0.2_1X Display Manager Control Protocol library > libXext-1.0.5,1 X11 Extension library > libXfixes-4.0.3_1 X Fixes extension library > libXi-1.2.1,1 X Input extension library > libXmu-1.0.4,1 X Miscellaneous Utilities libraries > libXpm-3.5.7X Pixmap library > libXrender-0.9.4_1 X Render extension library > libXt-1.0.5_1 X Toolkit library > libXxf86vm-1.0.2X Vidmode Extension > libdrm-2.4.12 Userspace interface to kernel Direct Rendering Module > servi > libglut-7.4.4 OpenGL utility toolkit > libiconv-1.13.1_1 A character set conversion library > libpthread-stubs-0.3_3 This library provides weak aliases for pthread > functions > libxcb-1.5 The X protocol C-language Binding (XCB) library > libxml2-2.7.6_1 XML parser library for GNOME > mesa-demos-7.4.4OpenGL demos distributed with Mesa > pkg-config-0.23_1 A utility to retrieve information about installed > libraries > png-1.2.43 Library for manipulating PNG images > renderproto-0.9.3 RenderProto protocol headers > wine-1.1.40,1 Microsoft Windows compatibility layer for Unix-like > systems > xextproto-7.0.5 XExt extension headers > xf86vidmodeproto-2.2.2 XFree86-VidModeExtension extension headers > xproto-7.0.15 X11 protocol headers > > This is sort of worrying then: Why am I seeing segfaults? I'd expect to see > executable format errors if there were 64 bit binaries being used somewhere > rather than straight crashes. > > Regards, > xw > -- with best regards, Krutov Mikle ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
On 2010-07-01 15:28:00, Mikle Krutov wrote: > Sorry for late-answer, but why are you running wine in jail? > May be that's the source of the problem. > For me, it was just installed into /usr/local/ as some other > program, some 32bit libs were in lib32, and so on. As mentioned, I've tried it in a jail, a plain chroot and also completely unchrooted and unjailed. Wine itself works fine but DRI doesn't. I recently wrote to freebsd-hackers@ and the response wasn't exactly positive. Seems 32-bit DRI is basically expected to fail when talking to a 64-bit kernel. Wine's not the one at fault here. Regards, xw ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
On 2010-06-24 18:57:35, Mikle Krutov wrote: > 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. Yes, I have those. Here's a list of all ports installed in the i386 jail (they were built in the jail itself so are definitely 32 bit): bash-4.0.35 The GNU Project's Bourne Again SHell damageproto-1.1.0_2 Damage extension headers dri-7.4.4,2 OpenGL hardware acceleration drivers for the DRI dri2proto-2.1 DRI2 prototype headers expat-2.0.1_1 XML 1.0 parser written in C fixesproto-4.0 Fixes extension headers fontconfig-2.8.0,1 An XML-based font configuration API for X Windows freetype2-2.3.11A free and portable TrueType font rendering engine gettext-0.17_1 GNU gettext package inputproto-1.5.0Input extension headers jpeg-8_1IJG's jpeg compression utilities kbproto-1.0.3 KB extension headers lcms-1.19_1,1 Light Color Management System -- a color management library libGL-7.4.4 OpenGL library that renders using GLX or DRI libGLU-7.4.4OpenGL utility library libICE-1.0.4_1,1Inter Client Exchange library for X11 libSM-1.1.0_1,1 Session Management library for X11 libX11-1.2.1_1,1X11 library libXau-1.0.4Authentication Protocol library for X11 libXdamage-1.1.1X Damage extension library libXdmcp-1.0.2_1X Display Manager Control Protocol library libXext-1.0.5,1 X11 Extension library libXfixes-4.0.3_1 X Fixes extension library libXi-1.2.1,1 X Input extension library libXmu-1.0.4,1 X Miscellaneous Utilities libraries libXpm-3.5.7X Pixmap library libXrender-0.9.4_1 X Render extension library libXt-1.0.5_1 X Toolkit library libXxf86vm-1.0.2X Vidmode Extension libdrm-2.4.12 Userspace interface to kernel Direct Rendering Module servi libglut-7.4.4 OpenGL utility toolkit libiconv-1.13.1_1 A character set conversion library libpthread-stubs-0.3_3 This library provides weak aliases for pthread functions libxcb-1.5 The X protocol C-language Binding (XCB) library libxml2-2.7.6_1 XML parser library for GNOME mesa-demos-7.4.4OpenGL demos distributed with Mesa pkg-config-0.23_1 A utility to retrieve information about installed libraries png-1.2.43 Library for manipulating PNG images renderproto-0.9.3 RenderProto protocol headers wine-1.1.40,1 Microsoft Windows compatibility layer for Unix-like systems xextproto-7.0.5 XExt extension headers xf86vidmodeproto-2.2.2 XFree86-VidModeExtension extension headers xproto-7.0.15 X11 protocol headers This is sort of worrying then: Why am I seeing segfaults? I'd expect to see executable format errors if there were 64 bit binaries being used somewhere rather than straight crashes. Regards, xw ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 wine on amd64 - DRI a lost cause?
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, xorquew...@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-unsubscr...@freebsd.org" > -- with best regards, Krutov Mikle ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
i386 wine on amd64 - DRI a lost cause?
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-unsubscr...@freebsd.org"
