I upgraded the OS on my Laptop to Ubuntu 64 bit. The laptop has an Nvidia Quadro NVs 135M video.

BAM! calls this machine a 32 bit Linux client. WRONG (it was 32 bit under a different host id)

The Nvidia Quadro is so small, it should not be considered as a GPU, only 128 MB of Memory and 8 CUDA cores, it is not ready to be a capable compute engine.

So how can I change this in BAM!!

This is host id 386699

Read the Bug Submit Guidelines!, check out #5 especially.

http://boincstats.com/en/bam/host/386699

Sorry that I did NOT include that in the original posting.

This is where I see Linux 32 bit and it should be Linux 64 bit.

Yes this machine has a coprocessor. It is a Nvidia NVS 135M, 8 cores, 256MB of RAM. Not enough cores, not enough RAM to be an effective machine. Apparently, only 128MB of the 256MB is allocated to general compute functions as the other 128MB is used as the video buffer. I see the 128MB reported in the BOINC Manager Event Log.

The Event Log does not give a clue on 32 bit vs 64 bit Linux, although the version of BOINC that I am using is compiled for 64 bit Linux.

The BOINC version is 7.0.28 (Development version)

Linux version is Ubuntu 12.04 Long Term Support (LTS)

So where do you get info on the host OS that tells you that the OS is 32 bit or 64 bit??

Can a host be globally declared to be off limits for GPU use as the GPU for whatever reason the user decides? Yes, I can say do not use GPU on a Project basis, but that leaves the GPU not available on other hosts. I can declare the Host off limits for GPU use in BOINC Manager (Suspend GPU Use) but that is not the same as DO NOT USE GPU.

So I am unsure what a solution might be and what workaround will be effective for this trivial GPU.

BAM! gets that information from acct_mgr_request.xml (Bug Submit Guidelines!#8, those rules are there for a reason)


Such a feature does not exist in the BOINC client by my knowledge, but maybe something can be done with cc_config.xml.

Read all about cc_config.xml here: http://boinc.berkeley.edu/wiki/Client_configuration

Just noticed you are using a development version of the client. Those are not supported by me and whether or not they work properly can't be guaranteed.