<html>
<body>
<font face="Courier New, Courier">I'm sorry it took so long for me to
reply.<br><br>
Well, I had to so some small changes to those lines for the test to work:
normally, if the firls call to fglrxinfo is too soon and fails, and that
failure is not handled, the entire init script will be aborted and boic
will not start. So I changed the snippet to this:<br><br>
start()<br>
{<br>
<x-tab> </x-tab># added by
@@ rodrigo<br>
<x-tab> </x-tab>
testlogfile=/var/log/boinc-fglrx.log<br>
<x-tab> </x-tab>echo
"\nstart\n" > "$testlogfile"<br>
<x-tab> </x-tab>sleep
5<br>
<x-tab> </x-tab>
/usr/bin/fglrxinfo >> "$testlogfile" 2>&1 ||
true<br>
<x-tab> </x-tab>echo
"\n5sec passed\n" >> "$testlogfile"<br>
<x-tab> </x-tab>sleep
5<br>
<x-tab> </x-tab>
/usr/bin/fglrxinfo >> "$testlogfile" 2>&1 ||
true<br>
<x-tab> </x-tab>echo
"\n10sec passed\n" >> "$testlogfile"<br>
<x-tab> </x-tab>sleep
5<br>
<x-tab> </x-tab>
/usr/bin/fglrxinfo >> "$testlogfile" 2>&1 ||
true<br>
<x-tab> </x-tab>echo
"\n15sec passed\n" >> "$testlogfile"<br>
<x-tab> </x-tab>sleep
5<br>
<x-tab> </x-tab>
/usr/bin/fglrxinfo >> "$testlogfile" 2>&1 ||
true<br>
<x-tab> </x-tab>echo
"\n20sec passed\n" >> "$testlogfile"<br>
<x-tab> </x-tab>sleep
5<br>
<x-tab> </x-tab>
/usr/bin/fglrxinfo >> "$testlogfile" 2>&1 ||
true<br>
<x-tab> </x-tab>echo
"\n25sec passed\n" >> "$testlogfile"<br>
<x-tab> </x-tab>sleep
5<br>
<x-tab> </x-tab>
/usr/bin/fglrxinfo >> "$testlogfile" 2>&1 ||
true<br>
<x-tab> </x-tab>echo
"\n30sec passed\n" >> "$testlogfile"<br><br>
log_begin_msg "Starting $DESC: $NAME"<br><br>
...<br><br>
<br>
And the results, identical and consistent in every boot for the last week
(about a dozen or so) is, unfortunately:<br><br>
start<br><br>
Error: unable to open display (null)<br><br>
5sec passed<br><br>
Error: unable to open display (null)<br><br>
10sec passed<br><br>
Error: unable to open display (null)<br><br>
15sec passed<br><br>
Error: unable to open display (null)<br><br>
20sec passed<br><br>
Error: unable to open display (null)<br><br>
25sec passed<br><br>
Error: unable to open display (null)<br><br>
30sec passed<br><br>
<br>
The same script, when called in a terminal after my Desktop session
starts:<br><br>
start<br><br>
display: :0 screen: 0<br>
OpenGL vendor string: Advanced Micro Devices, Inc.<br>
OpenGL renderer string: AMD Radeon HD 7700 Series<br>
OpenGL version string: 4.2.12002 Compatibility Profile Context
9.002<br><br>
<br>
5sec passed<br><br>
display: :0 screen: 0<br>
OpenGL vendor string: Advanced Micro Devices, Inc.<br>
OpenGL renderer string: AMD Radeon HD 7700 Series<br>
OpenGL version string: 4.2.12002 Compatibility Profile Context
9.002<br><br>
<br>
10sec passed<br><br>
display: :0 screen: 0<br>
OpenGL vendor string: Advanced Micro Devices, Inc.<br>
OpenGL renderer string: AMD Radeon HD 7700 Series<br>
OpenGL version string: 4.2.12002 Compatibility Profile Context
9.002<br><br>
<br>
15sec passed<br><br>
display: :0 screen: 0<br>
OpenGL vendor string: Advanced Micro Devices, Inc.<br>
OpenGL renderer string: AMD Radeon HD 7700 Series<br>
OpenGL version string: 4.2.12002 Compatibility Profile Context
9.002<br><br>
<br>
20sec passed<br><br>
display: :0 screen: 0<br>
OpenGL vendor string: Advanced Micro Devices, Inc.<br>
OpenGL renderer string: AMD Radeon HD 7700 Series<br>
OpenGL version string: 4.2.12002 Compatibility Profile Context
9.002<br><br>
<br>
25sec passed<br><br>
display: :0 screen: 0<br>
OpenGL vendor string: Advanced Micro Devices, Inc.<br>
OpenGL renderer string: AMD Radeon HD 7700 Series<br>
OpenGL version string: 4.2.12002 Compatibility Profile Context
9.002<br><br>
<br>
30sec passed<br><br>
<br>
Given this results, and since my boot is faster than 30 secinds, I think
this is not a matter of timing: the script is unable to find a working
flgrx no matter how much it sleeps waiting. And my suspition is: fglrx is
only started with X, and boinc-client, being a sysV init is executed
before X.<br><br>
So boinc-client must be either moved from SysV to another initialization
"chain", for example Upstart, or gdm/lightdm/whatever starts
X.<br><br>
Or, another approach would be keep it there but to re-start it at certain
"checkpoints" if the environment allows more capabilities. So
no GPU for x-less servers (like now), but it could test for GPU again
after X session starts, and re-start client if it founds one.<br><br>
ML<br><br>
<br>
At 01:36 PM 3/10/2013, Christian Beer wrote:<br>
<blockquote type=cite class=cite cite="">I'm sorry I mixed up the bugs. I
meant 933354 GPU not found with ATI Hdxxxx series cards in my post. I did
some more research and think that we may debug this with some<br>
<br>
sleep 5<br>
fglrxinfo >> /home/user/boinc-fglrx.log<br>
sleep 5<br>
fglrxinfo >> /home/user/boinc-fglrx.log<br><br>
calls in /etc/init-d/boinc-client. In the end we need to know which
script needs to be started before boinc. I once read an article about
bootchart (
<a href="http://www.bootchart.org/">http://www.bootchart.org/</a>) which
may help us in finding the culprit on an affected system.<br>
<br>
What do you think about this?<br><br>
Regards<br>
Christian<br>
Am 10.03.2013 14:01, schrieb Christian Beer: <br>
<blockquote type=cite class=cite cite="">Hi,<br><br>
I think this bug (1140597) is really a timing issue at boot time. As this
seems to only affect ATI/AMD hardware I think that the drivers for these
cards either get loaded after boinc or they take too long to load so they
are not present when boinc tries to detect GPUs.<br><br>
My first try to see if this is correct would be to insert a time delay in
the boinc init script and see if this helps. If boinc can successfully
find the GPU after the delay we need to find the script that is loading
the driver and instruct the boinc init script to load after
this.<br><br>
If MestreLion would be so kind to try this out it would be great. You
just need to make some local changes to your init script and restart your
machine. If this is okay for you I will send you a line to add to your
init script.<br><br>
@Gianfranco: does the boinc Ubuntu package use the same init script as
the Debian package? I only have a working Debian installation.<br><br>
Regards<br>
Christian<br><br>
Am 10.03.2013 12:02, schrieb Gianfranco Costamagna: <br>
<blockquote type=cite class=cite cite=""><br>
Hi MestreLion, I think this is the right place to discuss to.<br><br>
Unfortunately you script has a bad behaviour for people that DON'T have
an usable GPU...<br><br>
I don't like to restart boinc to everybody just because the might suffer
from bug #1140597<br><br>
What do you think about?<br><br>
My opinion is that there should a way for giving the right order to init
scripts, but I don't know at the moment how to change the script right
now...<br><br>
Gianfranco<br><br>
<br>
</font><font face="Courier New, Courier" size=2><b>From: </b>MestreLion
<a href="mailto:launchpad@rodrigosilva.com">
<launchpad@rodrigosilva.com></a>; <br>
<b>To:
</b><a href="mailto:pkg-boinc-devel@lists.alioth.debian.org">
<pkg-boinc-devel@lists.alioth.debian.org></a>; <br>
<b>Subject: </b>[Bug 1140597] Re: "New version is available"
notification should be disabled <br>
<b>Sent: </b>Sun, Mar 10, 2013 12:05:22 AM <br>
</font><font face="Courier New, Courier"><br>
Whatever mailing list you guys use to continue this discussion, sign
me<br>
in! :)<br><br>
My C++ skills are a bit rusty, but I may be able to help, if not in<br>
programming, at least in discussing strategies, approaches and<br>
packaging.<br><br>
Also, I've created a script (wrapper for boincmgr) as a workaround
for<br>
some of the annoying boinc bugs: not detecting a GPU at boot and not
re-<br>
starting boinc client after shutting its tasks, so maybe it will be<br>
useful for you guys:
<a href="https://github.com/MestreLion/scripts/blob/master">
https://github.com/MestreLion/scripts/blob/master</a><br>
/boinc-manager<br><br>
-- <br>
You received this bug notification because you are a member of
Debian<br>
BOINC Maintainers, which is subscribed to boinc in Ubuntu.<br>
<a href="https://bugs.launchpad.net/bugs/1140597">
https://bugs.launchpad.net/bugs/1140597</a><br><br>
Title:<br>
"New version is available" notification should be
disabled<br><br>
To manage notifications about this bug go to:<br>
<a href="https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1140597/+subscriptions">
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1140597/+subscriptions</a>
<br>
<br>
-- <br>
pkg-boinc-devel mailing list<br>
pkg-boinc-devel@lists.alioth.debian.org<br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel">
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel</a>
<br><br>
</blockquote><br><br>
</blockquote></font></blockquote></body>
</html>