Zero cpus is reported by one of my linux boxes.
It is running boinc 4.43 which is from BOINC (ie not an optimized version)
linux 2.2.20-compact from Debian.

This symptom showed up when I tried to get a upgraded client using apt-get. The upgrade didn't work and know the computer is running with no cpus. :)

In the client.xml file the number of CPUs is reported as zero.

The machine appears to be running just fine. It is attached to seti, einstein, and Predictor. All those projects appear to run fine too.

BoincView is the program that doesn't like 0. It divides something by number of cpus and reports a floating point error.

What could be causing this error?

---

CPU detection is a function in the boinc client. This function is not working on your system, so the boinc client detects no cpu.
It is not good. I am not shure if it will stay running in this configuration.
It could be that the new boinc client has a new function to detect cpu, which your system with this older kernel don't supports. But I will look into the source...
If you will get problems with your app, you can try to downgrade to a older boinc version.

---

CPU detection is a function in the boinc client. This function is not working on your system, so the boinc client detects no cpu.
It is not good. I am not shure if it will stay running in this configuration.
It could be that the new boinc client has a new function to detect cpu, which your system with this older kernel don't supports. But I will look into the source...
If you will get problems with your app, you can try to downgrade to a older boinc version.

"Upgraded" was not a good word to use.
The linux box has been using 4.43 boinc since I started boincing a few weeks ago. I tried to switch to a optimized version of 4.43.

When I tried to switch to the optimized version, a lot of things were upgraded on my linux box. The switch to the optimized version failed because I wasn't allowed to upgrade some of the unix stuff (I assume) was required for optimized boinc. I should have saved the info when the upgrade failed.

I believe I probably have a mix of old and new linux stuff on the computer. I believe my boinc will report zero cpus until I reinstall linux on the box.



On the bright side, the box has been boincing without errors for a week.
It doesn't seem to care that it has no cpus. :)

---

CPU detection is a function in the boinc client. This function is not working on your system, so the boinc client detects no cpu.
It is not good. I am not shure if it will stay running in this configuration.
It could be that the new boinc client has a new function to detect cpu, which your system with this older kernel don't supports. But I will look into the source...
If you will get problems with your app, you can try to downgrade to a older boinc version.

"Upgraded" was not a good word to use.
The linux box has been using 4.43 boinc since I started boincing a few weeks ago. I tried to switch to a optimized version of 4.43.

When I tried to switch to the optimized version, a lot of things were upgraded on my linux box. The switch to the optimized version failed because I wasn't allowed to upgrade some of the unix stuff (I assume) was required for optimized boinc. I should have saved the info when the upgrade failed.

I believe I probably have a mix of old and new linux stuff on the computer. I believe my boinc will report zero cpus until I reinstall linux on the box.



On the bright side, the box has been boincing without errors for a week.
It doesn't seem to care that it has no cpus. :)

I strongly belive the problem is kernel related. You should at least use a 2.4 kernel to get it working (including the needed kernel headers).

regards
Crunch3r

---

Join BOINC United now!

I strongly belive the problem is kernel related. You should at least use a 2.4 kernel to get it working (including the needed kernel headers).

regards
Crunch3r

[/quote]

I've upgraded linux to be debian 2.4.27-2-686 and I still only have zero cpus reported by boinc

---

CPU detection is a function in the boinc client. This function is not working on your system, so the boinc client detects no cpu.
It is not good. I am not shure if it will stay running in this configuration.
It could be that the new boinc client has a new function to detect cpu, which your system with this older kernel don't supports. But I will look into the source...
If you will get problems with your app, you can try to downgrade to a older boinc version.

"Upgraded" was not a good word to use.
The linux box has been using 4.43 boinc since I started boincing a few weeks ago. I tried to switch to a optimized version of 4.43.

When I tried to switch to the optimized version, a lot of things were upgraded on my linux box. The switch to the optimized version failed because I wasn't allowed to upgrade some of the unix stuff (I assume) was required for optimized boinc. I should have saved the info when the upgrade failed.

I believe I probably have a mix of old and new linux stuff on the computer. I believe my boinc will report zero cpus until I reinstall linux on the box.



On the bright side, the box has been boincing without errors for a week.
It doesn't seem to care that it has no cpus. :)

I strongly belive the problem is kernel related. You should at least use a 2.4 kernel to get it working (including the needed kernel headers).

regards
Crunch3r

I upgraded to the latest release of Debian. I'm not at home so I don't recall the exact numbers. BOINC still runs and crunches work units. My cpus is still zero though. What does boinc call to get the number of cpus?

---

CPU detection is a function in the boinc client. This function is not working on your system, so the boinc client detects no cpu.
It is not good. I am not shure if it will stay running in this configuration.
It could be that the new boinc client has a new function to detect cpu, which your system with this older kernel don't supports. But I will look into the source...
If you will get problems with your app, you can try to downgrade to a older boinc version.

"Upgraded" was not a good word to use.
The linux box has been using 4.43 boinc since I started boincing a few weeks ago. I tried to switch to a optimized version of 4.43.

When I tried to switch to the optimized version, a lot of things were upgraded on my linux box. The switch to the optimized version failed because I wasn't allowed to upgrade some of the unix stuff (I assume) was required for optimized boinc. I should have saved the info when the upgrade failed.

I believe I probably have a mix of old and new linux stuff on the computer. I believe my boinc will report zero cpus until I reinstall linux on the box.



On the bright side, the box has been boincing without errors for a week.
It doesn't seem to care that it has no cpus. :)

I strongly belive the problem is kernel related. You should at least use a 2.4 kernel to get it working (including the needed kernel headers).

regards
Crunch3r

I upgraded to the latest release of Debian. I'm not at home so I don't recall the exact numbers. BOINC still runs and crunches work units. My cpus is still zero though. What does boinc call to get the number of cpus?

Well i guess it´s your celeron wich seems to be the problem. I dont know why but it has got at least 100 hostids assigned to this machine (http://setiathome.berkeley.edu/show_host_detail.php?hostid=1445549) and the cpu type is reported corectly to the project as you can see yourself in your accout info.

I dont see anything wrong with the client.

---

Join BOINC United now!