The BOINC project has a screensaver that runs on Windows. I installed BOINC in a virtual machine running Windows XP (32 bit) and copied boinc.scr from the C:\Windows directory onto my 64 bit F13 system. When I run the screensaver I get an error. Any feedback is appreciated. I can run glxgears without any problem.
$ wine boinc.scr
Wine cannot find the ncurses library (libncurses.so.5).
err:winediag:X11DRV_WineGL_InitOpenglInfo The Mesa OpenGL driver is using software rendering, most likely your OpenGL drivers haven't been installed correctly
fixme:win:EnumDisplayDevicesW ((null),0,0x3328f0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x3328e8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x3328e8,0x00000000), stub!
$
When I ran wine it caused the following packages to be installed.
wine-core-1.1.38-1.fc13.x86_64 Wine core package
wine-fonts-1.1.38-1.fc13.noarch Wine font files
I then installed the following packages with "yum install wine(x86-32)".
wine i686 1.3.21-1.fc13 updates 33 k
alsa-lib i686 1.0.23-1.fc13 fedora 367 k
cairo i686 1.8.10-1.fc13 fedora 320 k
cdparanoia-libs i686 10.2-9.fc13 fedora 46 k
cyrus-sasl-lib i686 2.1.23-11.fc13 fedora 135 k
db4 i686 4.8.30-1.fc13 updates 614 k
dbus-libs i686 1:1.2.24-2.fc13 updates 129 k
expat i686 2.0.1-10.fc13 fedora 78 k
flac i686 1.2.1-6.fc12 fedora 239 k
fontconfig i686 2.8.0-1.fc13 fedora 186 k
freetype i686 2.3.11-7.fc13 updates 362 k
gamin i686 0.1.10-7.fc13 fedora 120 k
glib2 i686 2.24.1-1.fc13 fedora 1.2 M
glibc i686 2.12.2-1 updates 4.3 M
gnutls i686 2.8.6-2.fc13 updates 353 k
gstreamer i686 0.10.30-1.fc13 updates 802 k
gstreamer-plugins-base i686 0.10.30-1.fc13 updates 971 k
keyutils-libs i686 1.2-6.fc12 fedora 18 k
krb5-libs i686 1.7.1-19.fc13 updates 658 k
lcms-libs i686 1.19-1.fc13 fedora 101 k
libICE i686 1.0.6-2.fc13 fedora 52 k
libSM i686 1.1.0-7.fc12 fedora 25 k
libX11 i686 1.3.1-3.fc13 fedora 585 k
libXau i686 1.0.5-1.fc12 fedora 21 k
libXcursor i686 1.1.10-4.fc13 fedora 33 k
libXdamage i686 1.1.2-2.fc13 fedora 16 k
libXext i686 1.1.2-2.fc13 updates 33 k
libXfixes i686 4.0.4-2.fc13 fedora 19 k
libXft i686 2.1.14-1.fc13 fedora 48 k
libXi i686 1.3.2-1.fc13 updates 32 k
libXrender i686 0.9.5-1.fc13 fedora 26 k
libXtst i686 1.0.99.2-3.fc12 fedora 21 k
libXv i686 1.0.5-1.fc13 fedora 20 k
libXxf86vm i686 1.1.0-1.fc13 fedora 18 k
libasyncns i686 0.8-1.fc13 fedora 24 k
libcom_err i686 1.41.10-7.fc13 updates 34 k
libdrm i686 2.4.21-2.fc13 updates 68 k
liberation-narrow-fonts noarch 1.06.0.20100721-1.fc13 updates 197 k
libexif i686 0.6.19-1.fc13 updates 290 k
libgcc i686 4.4.5-2.fc13 updates 106 k
libgcrypt i686 1.4.5-4.fc13 fedora 228 k
libgpg-error i686 1.7-1.fc13 fedora 59 k
libgphoto2 i686 2.4.8-1.fc13 fedora 1.0 M
libgudev1 i686 153-5.fc13 updates 58 k
libjpeg i686 6b-46.fc12 fedora 126 k
libogg i686 2:1.2.0-1.fc13 fedora 22 k
libpng i686 2:1.2.44-1.fc13 updates 183 k
libselinux i686 2.0.94-2.fc13 updates 106 k
libsndfile i686 1.0.20-5.fc13 fedora 161 k
libstdc++ i686 4.4.5-2.fc13 updates 293 k
libtasn1 i686 2.4-2.fc13 fedora 239 k
libthai i686 0.1.14-2.fc13 fedora 185 k
libtheora i686 1:1.1.1-1.fc13 fedora 131 k
libtool-ltdl i686 2.2.6-20.fc13 fedora 44 k
libudev i686 153-5.fc13 updates 73 k
libusb i686 0.1.12-23.fc13 updates 27 k
libuuid i686 2.17.2-10.fc13 updates 62 k
libvisual i686 0.4.0-9.fc12 fedora 127 k
libvorbis i686 1:1.3.1-1.fc13 fedora 189 k
libxcb i686 1.5-1.fc13 fedora 103 k
libxml2 i686 2.7.7-2.fc13 updates 797 k
mesa-dri-drivers i686 7.8.2-1.fc13 updates 10 M
mesa-libGL i686 7.8.2-1.fc13 updates 154 k
mesa-libGLU i686 7.8.2-1.fc13 updates 188 k
nss-mdns i686 0.10-8.fc12 fedora 22 k
nss-softokn-freebl i686 3.12.9-5.fc13 updates 118 k
openal-soft i686 1.12.854-1.fc13 fedora 113 k
openldap i686 2.4.21-11.fc13 updates 238 k
openssl i686 1.0.0d-1.fc13 updates 1.4 M
orc i686 0.4.10-1.fc13 updates 145 k
pango i686 1.28.0-1.fc13 fedora 349 k
pixman i686 0.18.0-1.fc13 fedora 154 k
pulseaudio-libs i686 0.9.21-7.fc13 updates 420 k
tcp_wrappers-libs i686 7.6-59.fc13 updates 62 k
wine-capi i686 1.3.21-1.fc13 updates 37 k
wine-cms i686 1.3.21-1.fc13 updates 51 k
wine-core i686 1.3.21-1.fc13 updates 14 M
wine-courier-fonts noarch 1.3.21-1.fc13 updates 46 k
wine-desktop noarch 1.3.21-1.fc13 updates 123 k
wine-ldap i686 1.3.21-1.fc13 updates 93 k
wine-marlett-fonts noarch 1.3.21-1.fc13 updates 45 k
wine-ms-sans-serif-fonts noarch 1.3.21-1.fc13 updates 56 k
wine-openal i686 1.3.21-1.fc13 updates 43 k
wine-pulseaudio i686 1.3.21-1.fc13 updates 54 k
wine-small-fonts noarch 1.3.21-1.fc13 updates 48 k
wine-symbol-fonts noarch 1.3.21-1.fc13 updates 59 k
wine-system-fonts noarch 1.3.21-1.fc13 updates 52 k
wine-tahoma-fonts noarch 1.3.21-1.fc13 updates 106 k
wine-twain i686 1.3.21-1.fc13 updates 59 k
wine-wow i686 1.3.21-1.fc13 updates 218 k
zlib i686 1.2.3-23.fc12 fedora 69 k
Updating for dependencies:
wine-common noarch 1.3.21-1.fc13 updates 101 k
wine-core x86_64 1.3.21-1.fc13 updates 14 M
wine-fonts noarch 1.3.21-1.fc13 updates 33 k
OpenGL drivers haven't been installed correctly
-
patrick.melo
- Newbie
- Posts: 2
- Joined: Thu Jun 07, 2012 7:17 pm
-
Martin Gregorie
OpenGL drivers haven't been installed correctly
On Thu, 2012-06-07 at 19:31 -0500, patrick.melo wrote:
Windows because that's about the only way it can get as much CPU time as
it needs without interfering with your other work.
The native Linux version does a rather better job: it runs 24/7 as a
'niced' background task and so can sop up every bit of unused CPU that
is available without having any detectable effect of your own work. It
can even run more than one project simultaneously without interfering
with what you are doing. I ran SETI@home and MalariaControl together on
a fairly small box (866MHz P3, 512MB RAM) without any problems: every
few weeks I'd peek to see if it was still running: it always was.
However, there is one caveat: if you're doing it just to use up idle
cycles its fine on an older box with fixed CPU speeds because the power
consumption and CPU speeds don't change with the system workload.
However, on a modern variable speed box BOINC will spin the CPUs up to
max speed and burn through a lot of power that you wouldn't be paying
for if you weren't running it. I recently replaced the P3 with a dual
core Athlon system which was well-behaved and ramped up and down nicely
during Linux install and configuration. That is, until I fired up BOINC.
That's when all fans spun up to max speed and the machine sat there
howling and blasting hot air out its vents. I stood the noise for a day
and then dumped BOINC.
Martin
I think you'll find that BOINC is designed to be a screensaver underThe BOINC project has a screensaver that runs on Windows. I installed
BOINC in a virtual machine running Windows XP (32 bit) and copied
boinc.scr from the C:\Windows directory onto my 64 bit F13 system.
When I run the screensaver I get an error. Any feedback is
appreciated. I can run glxgears without any problem.
Windows because that's about the only way it can get as much CPU time as
it needs without interfering with your other work.
The native Linux version does a rather better job: it runs 24/7 as a
'niced' background task and so can sop up every bit of unused CPU that
is available without having any detectable effect of your own work. It
can even run more than one project simultaneously without interfering
with what you are doing. I ran SETI@home and MalariaControl together on
a fairly small box (866MHz P3, 512MB RAM) without any problems: every
few weeks I'd peek to see if it was still running: it always was.
However, there is one caveat: if you're doing it just to use up idle
cycles its fine on an older box with fixed CPU speeds because the power
consumption and CPU speeds don't change with the system workload.
However, on a modern variable speed box BOINC will spin the CPUs up to
max speed and burn through a lot of power that you wouldn't be paying
for if you weren't running it. I recently replaced the P3 with a dual
core Athlon system which was well-behaved and ramped up and down nicely
during Linux install and configuration. That is, until I fired up BOINC.
That's when all fans spun up to max speed and the machine sat there
howling and blasting hot air out its vents. I stood the noise for a day
and then dumped BOINC.
Martin
-
patrick.melo
- Newbie
- Posts: 2
- Joined: Thu Jun 07, 2012 7:17 pm
Thanks for your feedback Martin.
I'm running boinc-client and boinc-manager on a collection F17 machines and have them attached to rosetta@home. Everything seem to be running pretty well.
I wanted something I could use for "show and tell" from this F13 machine and it doesn't necessarily need to run as a screensaver. The graphical display just goes a long way to getting people to understand what the program is doing.
Patrick
I'm running boinc-client and boinc-manager on a collection F17 machines and have them attached to rosetta@home. Everything seem to be running pretty well.
I wanted something I could use for "show and tell" from this F13 machine and it doesn't necessarily need to run as a screensaver. The graphical display just goes a long way to getting people to understand what the program is doing.
Patrick
-
Martin Gregorie
OpenGL drivers haven't been installed correctly
On Fri, 2012-06-08 at 11:31 -0500, patrick.melo wrote:
show anything useful for that.
Possibly a better question to ask this list is "Is it possible to run a
Windows screen saver under Wine?".
IIRC Windows screen savers will only run in a specialised environment
because of the way Windows can suspend and re-activate them, but I don't
know anything about the screensaver environment or whether Wine supports
it.
Martin
Apologies for trying to teach you to suck eggs!Thanks for your feedback Martin.
I see what you're after and I suppose the boinc-client display doesn'tI wanted something I could use for "show and tell" from this F13
machine and it doesn't necessarily need to run as a screensaver. The
graphical display just goes a long way to getting people to understand
what the program is doing.
show anything useful for that.
Possibly a better question to ask this list is "Is it possible to run a
Windows screen saver under Wine?".
IIRC Windows screen savers will only run in a specialised environment
because of the way Windows can suspend and re-activate them, but I don't
know anything about the screensaver environment or whether Wine supports
it.
Martin
