Before the "Enforced by 6.10" GPU preferences came along, there was just a general "Use Nvidia GPU if available" preference (which did work with 6.4, 6.5 and 6.6). It would seem the new one isn't backwards compatible. I'll email the BOINC devs on this.
I was just joking about the unceremoniousness (for a new word). It's always nice to see others having read whatever I have written and for them to forward that info to others. That way I can continue playing Tomb Raider Underworld, without distraction. :-)
Apropos, have you checked if LaptopVideo2Go may have updated drivers for your system?
Also, what kind of Dell system do you have? I ask, as it does say at the Nvidia latest drivers, that for some Dell systems you need to upgrade the BIOS first. Then the newer drivers work.
Before the "Enforced by 6.10" GPU preferences came along, there was just a general "Use Nvidia GPU if available" preference (which did work with 6.4, 6.5 and 6.6). It would seem the new one isn't backwards compatible. I'll email the BOINC devs on this.
Thanks! This would really assist in my situation. Maybe there is something that can be placed in the cc_config.xml. (wishful thinking ;-)
Quote:
I was just joking about the unceremoniousness (for a new word). It's always nice to see others having read whatever I have written and for them to forward that info to others. That way I can continue playing Tomb Raider Underworld, without distraction. :-)
I figured that you were joking. I always take the approach of read first and then ask. I know I tend to appreciate that more then "did you read this article or the FAQ first?". :-)
Quote:
Apropos, have you checked if LaptopVideo2Go may have updated drivers for your system?
Slow day. Will be doing that next... (as versus more Quake)
Quote:
Also, what kind of Dell system do you have? I ask, as it does say at the Nvidia latest drivers, that for some Dell systems you need to upgrade the BIOS first. Then the newer drivers work.
I have a Latitude E6400 (no letters after the name). Dell is so picky about driver install order that I've been holding off on the BIOS update but I'll now give it a go. There isn't a newer video driver listed on Dell's site for this laptop and Windows XP (although it's there for Vista).
Before the "Enforced by 6.10" GPU preferences came along, there was just a general "Use Nvidia GPU if available" preference (which did work with 6.4, 6.5 and 6.6). It would seem the new one isn't backwards compatible. I'll email the BOINC devs on this.
Jord, remember how we got into this.
The old "Use Nvidia GPU if available" preference only ever worked by inhibiting the server from sending work for the GPU: it never did (and couldn't, by design) prevent the client from requesting work - which led to the sort of conversation we're having now. The new "Enforced by 6.10" is supposed still to inhibit the server from sending GPU work, and in addition - but only when paired with a compatible v6.10.xx client - inhibit the requests as well. I don't see anything out of spec from ca77738's last log.
Quote:
I was just joking about the unceremoniousness (for a new word). It's always nice to see others having read whatever I have written and for them to forward that info to others. That way I can continue playing Tomb Raider Underworld, without distraction. :-)
Well, you did say 'Spread the word.' - so I did ;-)
The new "Enforced by 6.10" is supposed still to inhibit the server from sending GPU work, and in addition - but only when paired with a compatible v6.10.xx client - inhibit the requests as well.
Yes, but if it isn't working with non-6.10 clients, then what are they supposed to do? So, in my opinion it should be backward compatible with those that came before 6.10
If that needs a bug-fix on the server, that's OK. The user can't upgrade anyway. ;-)
Thanks! This would really assist in my situation. Maybe there is something that can be placed in the cc_config.xml. (wishful thinking ;-)
Anything put into the core client configuration file will need a client that knows something about it. So in your case... no. 6.6 is no longer updated.
If it's a bug, it needs to be fixed in the server code and the server needs to be updated to use the new code.
Quote:
I always take the approach of read first and then ask. I know I tend to appreciate that more then "did you read this article or the FAQ first?". :-)
How refreshing, yet how unuser-like. :-)
Usually it's "I am too busy to read big things, extra links, other stuff. I just need this fixed, pronto, or I will remove BOINC and leave you all". So thumbs up to you, Mike.
Quote:
I have a Latitude E6400 (no letters after the name).
(Damn, used a "usually" already, so now have to figure out another sentence start...)
Normally (Aha! ey?), I check the manufacturer's sites as well, but I find Dell so notoriously difficult to navigate that I won't do it this time. I've got a bad headache that aspirins can't get rid of, am sneezing and coughing and have some shivers. I really don't want to get ill, but apparently don't have a say in it. I'll believe you on your word. :-D
The new "Enforced by 6.10" is supposed still to inhibit the server from sending GPU work, and in addition - but only when paired with a compatible v6.10.xx client - inhibit the requests as well.
Yes, but if it isn't working with non-6.10 clients, then what are they supposed to do? So, in my opinion it should be backward compatible with those that came before 6.10
If that needs a bug-fix on the server, that's OK. The user can't upgrade anyway. ;-)
????
But in what respect is it 'not working'?
I see
12/24/2009 10:14:47 AM Einstein@Home Requesting new tasks for GPU
12/24/2009 10:14:52 AM Einstein@Home Message from server: No work sent
which is exactly what's supposed to happen with v6.6 - both the request, and the rejection.
You get that message as well because you aren't using a 6.10 client.
Einstein requires a 6.10 client for their ABP1. Anything lower and you're being laughed at and egged. ;-)
I guess I think the preference should do: If I unchecked it, the client shouldn't ask for work on the GPU. Since both 6.6 and 6.10 were capable of that, this preference should work for both clients, not 6.10 only.
The older "Use Graphics Processing Unit (GPU) if available" preference, if unchecked on 6.6 clients, would stop them asking for work on the project you unchecked it on. The newer preference seems to work for 6.10 and above clients only, not those that came before.
Or maybe it doesn't do it just on the Einstein project.
I always take the approach of read first and then ask.
How refreshing, yet how unuser-like. :-)
Did I mention that I work in the IT industry and really dislike spending lots of time creating manuals/documents that no one reads? I figure I should walk the talk... ;-)
Quote:
Quote:
I have a Latitude E6400 (no letters after the name).
Normally (Aha! ey?) Good one!, I check the manufacturer's sites as well, but I find Dell so notoriously difficult to navigate that I won't do it this time.
Dell's site isn't that bad - after you put in your support tag, convince it to memorize it, learn what drop downs you have to change for your OS, how long to wait and what to click to get things to go faster... :-(
I updated the BIOS and tried to upgrade the video drivers to 185.X and 195.X but the NVidia install said there wasn't compatible drivers for XP.
12/24/2009 10:14:43 AM Einstein@Home update requested by user
12/24/2009 10:14:47 AM Einstein@Home Sending scheduler request: Requested by user.
12/24/2009 10:14:47 AM Einstein@Home Requesting new tasks for GPU
12/24/2009 10:14:52 AM Einstein@Home Scheduler request completed: got 0 new tasks
12/24/2009 10:14:52 AM Einstein@Home Message from server: No work sent
Mike,
Even after zeroing the debts, notice that your client is only asking for GPU work. As Gundolf mentions, it is very strange that the client is not asking for CPU work. I don't understand why this is happening. If it were my machine, I'd check that there was a reasonable resource share for E@H (different 'venues' can have different resource shares for example and I believe you did play around with venues at one point. I'd also triple check every website preference setting for every venue just in case you've overlooked something. I'd also try a couple more manual updates, particularly after increasing the cache size a bit to see if a request for CPU work could be encouraged at some point. I'd sneak the 'extra days' setting as high as 2 or 3 days and put the other projects on NNT to prevent them getting extra work just to see if a E@H CPU request could be forced.
If a CPU request still is not forthcoming, there must be some setting somewhere that is preventing it.
Another technique you could try is to deliberately exclude the GPU by use of a suitable app_info.xml. I can't think of a reason why this should get you CPU tasks when the normal method wont but when you're desperate you tend to give anything a try :-). I've created one below if you wish to give it a try it. If you read through it you will see that it allows just S5R6 (CPU) tasks and also ABP1 CPU tasks. Just copy and paste the code below using a text editor like Notepad. Place the file in your E@H project folder and ensure there are copies of all listed programs placed there as well. You may already have some or all of these programs but if any are missing you can get them from here. You will find all the programs if you scroll down near the bottom of the page.
Once you have placed the app_info.xml file and made sure that all the program files (7 files) are also present just stop and restart BOINC and then BOINC should start asking for CPU work for E@H. To make sure AP is properly selected for E@H, look for 'using anonymous platform' in the BOINC Manager messages tab as BOINC starts up.
Before the "Enforced by 6.10"
)
Before the "Enforced by 6.10" GPU preferences came along, there was just a general "Use Nvidia GPU if available" preference (which did work with 6.4, 6.5 and 6.6). It would seem the new one isn't backwards compatible. I'll email the BOINC devs on this.
I was just joking about the unceremoniousness (for a new word). It's always nice to see others having read whatever I have written and for them to forward that info to others. That way I can continue playing Tomb Raider Underworld, without distraction. :-)
Apropos, have you checked if LaptopVideo2Go may have updated drivers for your system?
Also, what kind of Dell system do you have? I ask, as it does say at the Nvidia latest drivers, that for some Dell systems you need to upgrade the BIOS first. Then the newer drivers work.
RE: Before the "Enforced by
)
Thanks! This would really assist in my situation. Maybe there is something that can be placed in the cc_config.xml. (wishful thinking ;-)
I figured that you were joking. I always take the approach of read first and then ask. I know I tend to appreciate that more then "did you read this article or the FAQ first?". :-)
Slow day. Will be doing that next... (as versus more Quake)
I have a Latitude E6400 (no letters after the name). Dell is so picky about driver install order that I've been holding off on the BIOS update but I'll now give it a go. There isn't a newer video driver listed on Dell's site for this laptop and Windows XP (although it's there for Vista).
RE: Before the "Enforced by
)
Jord, remember how we got into this.
The old "Use Nvidia GPU if available" preference only ever worked by inhibiting the server from sending work for the GPU: it never did (and couldn't, by design) prevent the client from requesting work - which led to the sort of conversation we're having now. The new "Enforced by 6.10" is supposed still to inhibit the server from sending GPU work, and in addition - but only when paired with a compatible v6.10.xx client - inhibit the requests as well. I don't see anything out of spec from ca77738's last log.
Well, you did say 'Spread the word.' - so I did ;-)
RE: The new "Enforced by
)
Yes, but if it isn't working with non-6.10 clients, then what are they supposed to do? So, in my opinion it should be backward compatible with those that came before 6.10
If that needs a bug-fix on the server, that's OK. The user can't upgrade anyway. ;-)
RE: Thanks! This would
)
Anything put into the core client configuration file will need a client that knows something about it. So in your case... no. 6.6 is no longer updated.
If it's a bug, it needs to be fixed in the server code and the server needs to be updated to use the new code.
How refreshing, yet how unuser-like. :-)
Usually it's "I am too busy to read big things, extra links, other stuff. I just need this fixed, pronto, or I will remove BOINC and leave you all". So thumbs up to you, Mike.
(Damn, used a "usually" already, so now have to figure out another sentence start...)
Normally (Aha! ey?), I check the manufacturer's sites as well, but I find Dell so notoriously difficult to navigate that I won't do it this time. I've got a bad headache that aspirins can't get rid of, am sneezing and coughing and have some shivers. I really don't want to get ill, but apparently don't have a say in it. I'll believe you on your word. :-D
RE: RE: The new "Enforced
)
????
But in what respect is it 'not working'?
I see
which is exactly what's supposed to happen with v6.6 - both the request, and the rejection.
RE: But in what respect is
)
You get that message as well because you aren't using a 6.10 client.
Einstein requires a 6.10 client for their ABP1. Anything lower and you're being laughed at and egged. ;-)
I guess I think the preference should do: If I unchecked it, the client shouldn't ask for work on the GPU. Since both 6.6 and 6.10 were capable of that, this preference should work for both clients, not 6.10 only.
The older "Use Graphics Processing Unit (GPU) if available" preference, if unchecked on 6.6 clients, would stop them asking for work on the project you unchecked it on. The newer preference seems to work for 6.10 and above clients only, not those that came before.
Or maybe it doesn't do it just on the Einstein project.
RE: RE: I always take the
)
Did I mention that I work in the IT industry and really dislike spending lots of time creating manuals/documents that no one reads? I figure I should walk the talk... ;-)
Dell's site isn't that bad - after you put in your support tag, convince it to memorize it, learn what drop downs you have to change for your OS, how long to wait and what to click to get things to go faster... :-(
I updated the BIOS and tried to upgrade the video drivers to 185.X and 195.X but the NVidia install said there wasn't compatible drivers for XP.
Sounds like I'm SOL on the driver side...
I think the main question
)
I think the main question (concerning ca77738's problem:-) is: why doesn't the client ask for CPU work?
Host 986988 doesn't have any tasks downloaded and the debts are zeroed out...
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: 12/24/2009 10:14:43
)
Mike,
Even after zeroing the debts, notice that your client is only asking for GPU work. As Gundolf mentions, it is very strange that the client is not asking for CPU work. I don't understand why this is happening. If it were my machine, I'd check that there was a reasonable resource share for E@H (different 'venues' can have different resource shares for example and I believe you did play around with venues at one point. I'd also triple check every website preference setting for every venue just in case you've overlooked something. I'd also try a couple more manual updates, particularly after increasing the cache size a bit to see if a request for CPU work could be encouraged at some point. I'd sneak the 'extra days' setting as high as 2 or 3 days and put the other projects on NNT to prevent them getting extra work just to see if a E@H CPU request could be forced.
If a CPU request still is not forthcoming, there must be some setting somewhere that is preventing it.
Another technique you could try is to deliberately exclude the GPU by use of a suitable app_info.xml. I can't think of a reason why this should get you CPU tasks when the normal method wont but when you're desperate you tend to give anything a try :-). I've created one below if you wish to give it a try it. If you read through it you will see that it allows just S5R6 (CPU) tasks and also ABP1 CPU tasks. Just copy and paste the code below using a text editor like Notepad. Place the file in your E@H project folder and ensure there are copies of all listed programs placed there as well. You may already have some or all of these programs but if any are missing you can get them from here. You will find all the programs if you scroll down near the bottom of the page.
einstein_S5R6
einstein_S5R6_3.01_windows_intelx86.exe
einstein_S5R6_3.01_windows_intelx86_0.exe
einstein_S5R6_3.01_windows_intelx86_1.exe
einstein_S5R6_3.01_windows_intelx86_2.exe
einstein_S5R6_3.01_graphics_windows_intelx86.exe
einsteinbinary_ABP1
einsteinbinary_ABP1_3.12_graphics_windows_intelx86.exe
einsteinbinary_ABP1_3.12_windows_intelx86.exe
einstein_S5R6
301
6.3.0
einstein_S5R6_3.01_windows_intelx86.exe
einstein_S5R6_3.01_windows_intelx86_0.exe
einstein_S5R6_3.01_windows_intelx86_1.exe
einstein_S5R6_3.01_windows_intelx86_2.exe
einstein_S5R6_3.01_graphics_windows_intelx86.exe
graphics_app
einsteinbinary_ABP1
312
6.7.0
einsteinbinary_ABP1_3.12_windows_intelx86.exe
einsteinbinary_ABP1_3.12_graphics_windows_intelx86.exe
graphics_app
Once you have placed the app_info.xml file and made sure that all the program files (7 files) are also present just stop and restart BOINC and then BOINC should start asking for CPU work for E@H. To make sure AP is properly selected for E@H, look for 'using anonymous platform' in the BOINC Manager messages tab as BOINC starts up.
Cheers,
Gary.