Here is my question HB. Because I am using Ubuntu the only command I can find to determine temp is: cat /sys/class/thermal/thermal_zone0/temp. If you run this same command on your PI3 does it return the same temp as does your taskbar temp widget?
It does.
HB
Great!! Thanks for the effort. I have tied a LED to two GPIO pins and light it if this command produces a temperature greater than 42 and extinguish the LED when <= 42. The script also sends email. It will be really interesting to see the temps when I crunch with a PI3.
because this Thread is a little bit full of Information I lost the overview by the Problem with the Certificates for "Jessie" & Co. So far my PI would make over 28 Updates and I'm afraid that I could lost after the Updates the connectivity to the Project Servers. Is there are in the meantime a "quick and dirty" Solution for this Problem?
If you put the ca-certificates package "on hold" before an update you should be fine afterwards. The "hold" will prohibit any updates for this package until you explicitly "unhold" the package again. See: https://einsteinathome.org/node/198396
when I do what you mentioned I get the following Errors:
aptitude hold ca-certificates
[ ERR] Reading package lists
E: Malformed Description-md5 line; includes invalid character '7e58â–’49050f6ae75e912ec63afce4601'
E: Malformed Description-md5 line; includes invalid character 'a3c52cf750f216359a9386f6778k1379'
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_jessie_main_binary-armhf_Packages
E: The package lists or status file could not be parsed or opened.
I didn't notice that there is such an extensive literature on this. Thanks!
Quote:
After you've done those three steps, make sure to do the following to keep from losing the good certs in future upgrades
sudo apt-mark hold ca-certificates
Will do, thanks!
Quote:
Where did you get the wisdom file from? I hadn't seen that anyone had calculated a new one.
To get started quickly I did something very naive. I just copied the wisdom file that works on the Pi2 hoping that it might make a difference. I should check whether it really does make a difference.
Quote:
Also, what are the temps you're seeing and are you running at the full 1.2Ghz? I'm surprised to only see that small of an increase.
Initially, I was running without heatsinks and without a case. Temperatures (vcgencmd measure_temp) were consistently around 71°C and tasks finished in 42,000 s. Now that I installed heatsinks (still no case) nothing much changed. Temperature readings give results between 71°C and 75°C and tasks still need 42,000 s. vcgencmd measure_clock arm shows that the pi is running at full speed (1.2 GHz).
There is no ca-bundle.crt on Linux, it usually is a symlink to the system ca store. I tested this and it didn't work. Additionally it is not wise to download such a crucial part of security from untrusted sources. That's why I removed the link Ubik supplied in his response.
The Problem that DmmdL has is different. It seems the apt-get cache is corrupted and needs to be cleaned. I had the same problem some time ago. Look at the first answer here. That helped in my case.
vcgencmd measure_temp initially gave 74 C when running four Einstein, with a Heatsink freshly fitted,
giving 78.8 C now when running three Seti and one Einstein a little later.
vcgencmd measure_temp gave the frequency as frequency(45)=1170122000 initially, now gives consistently frequency(45)=1200000000
vcgencmd measure_temp initially gave 74 C when running four Einstein, with a Heatsink freshly fitted,
giving 78.8 C now when running three Seti and one Einstein a little later.
vcgencmd measure_temp gave the frequency as frequency(45)=1170122000 initially, now gives consistently frequency(45)=1200000000
Need a case and a fan i think.
Claggy
I am curious as to how these PI temps compare to ambient room temperature.
I have a pi3 running e@h also, and I have read this ENTIRE thread to get my head around this wisdom file! From what I can tell, the existing iteration will only lead to a speed up on the pi 2. My pi3 seems to finish units in about 33000 seconds which seems like pretty fast compared to the pi2 with wisdom.
Is there a wisdom file for the pi3 yet and will it make any difference anyway? Is the NEON any better on the pi3?
Just for info, I only run 2 tasks in parallel on it at the mo, because temps are at 75C even then and so I'm waiting on a heat sink delivery before I let it run 4.
RE: RE: Here is my
)
Great!! Thanks for the effort. I have tied a LED to two GPIO pins and light it if this command produces a temperature greater than 42 and extinguish the LED when <= 42. The script also sends email. It will be really interesting to see the temps when I crunch with a PI3.
Hi Folks, because this
)
Hi Folks,
because this Thread is a little bit full of Information I lost the overview by the Problem with the Certificates for "Jessie" & Co. So far my PI would make over 28 Updates and I'm afraid that I could lost after the Updates the connectivity to the Project Servers. Is there are in the meantime a "quick and dirty" Solution for this Problem?
BR
Greetings from the North
If you put the
)
If you put the ca-certificates package "on hold" before an update you should be fine afterwards. The "hold" will prohibit any updates for this package until you explicitly "unhold" the package again. See: https://einsteinathome.org/node/198396
Hi CB, when I do what you
)
Hi CB,
when I do what you mentioned I get the following Errors:
aptitude hold ca-certificates
[ ERR] Reading package lists
E: Malformed Description-md5 line; includes invalid character '7e58â–’49050f6ae75e912ec63afce4601'
E: Malformed Description-md5 line; includes invalid character 'a3c52cf750f216359a9386f6778k1379'
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_jessie_main_binary-armhf_Packages
E: The package lists or status file could not be parsed or opened.
Perhaps I doing something wrong?
BR
Greetings from the North
RE: I discovered this issue
)
I didn't notice that there is such an extensive literature on this. Thanks!
Will do, thanks!
To get started quickly I did something very naive. I just copied the wisdom file that works on the Pi2 hoping that it might make a difference. I should check whether it really does make a difference.
Initially, I was running without heatsinks and without a case. Temperatures (vcgencmd measure_temp) were consistently around 71°C and tasks finished in 42,000 s. Now that I installed heatsinks (still no case) nothing much changed. Temperature readings give results between 71°C and 75°C and tasks still need 42,000 s. vcgencmd measure_clock arm shows that the pi is running at full speed (1.2 GHz).
There is no ca-bundle.crt on
)
There is no ca-bundle.crt on Linux, it usually is a symlink to the system ca store. I tested this and it didn't work. Additionally it is not wise to download such a crucial part of security from untrusted sources. That's why I removed the link Ubik supplied in his response.
The Problem that DmmdL has is different. It seems the apt-get cache is corrupted and needs to be cleaned. I had the same problem some time ago. Look at the first answer here. That helped in my case.
My Pi 3 is up and running
)
My Pi 3 is up and running here and at Seti Beta:
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=78373
https://einsteinathome.org/host/12213079
vcgencmd measure_temp initially gave 74 C when running four Einstein, with a Heatsink freshly fitted,
giving 78.8 C now when running three Seti and one Einstein a little later.
vcgencmd measure_temp gave the frequency as frequency(45)=1170122000 initially, now gives consistently frequency(45)=1200000000
Need a case and a fan i think.
Claggy
vcgencmd measure_clock arm
)
vcgencmd measure_clock arm gives the freq, not what i posted above, one minute too late to edit.
Claggy
RE: My Pi 3 is up and
)
I am curious as to how these PI temps compare to ambient room temperature.
I have a pi3 running e@h
)
I have a pi3 running e@h also, and I have read this ENTIRE thread to get my head around this wisdom file! From what I can tell, the existing iteration will only lead to a speed up on the pi 2. My pi3 seems to finish units in about 33000 seconds which seems like pretty fast compared to the pi2 with wisdom.
Is there a wisdom file for the pi3 yet and will it make any difference anyway? Is the NEON any better on the pi3?
Just for info, I only run 2 tasks in parallel on it at the mo, because temps are at 75C even then and so I'm waiting on a heat sink delivery before I let it run 4.