Re: Throttling RPi4 CPU to Avoid Overheating
Op zaterdag 27 juli 2024 23:11:05 CEST schreef MPJ Grégoire: > Hello, > > I have a RaspberryPi 4, running Debian Stable. From time to time, the > system overheats under load and shuts down. Is there software I could > run or a setting I could configure that would throttle back the CPU to > keep the temperature under (say) 85°C? > > Thanks very much for supporting Raspberry Pi computers. > > Sincerely, You could bye a housing with ventilator and a small device to turn the ventilator on when the the temperature reaches a certain value. There is a small Python script that reads regularly the temperature and turns the ventilator on till it reaches a configurable lower temperature. -- fr.gr. Freek de Kruijf
Re: What's wrong with this entry in a cron job?
Op zaterdag 30 maart 2024 12:37:35 CET schreef Leigh Brown: > Hello, > > On 2024-03-30 10:52, Freek de Kruijf wrote: > > I have the following line in a cron job: > > > > 1 1 * * * rm -v /srv/db/webhoneypot-$(date --date=yesterday > > +%Y-%m-%d).json > > > > I get in the journal: > > > > Mar 30 01:01:01 rpi4rasphon CRON[1254]: (root) CMD (rm -v > > /srv/db/webhoneypot- > > $(date --date=yesterday +) > > > > and in the e-mail > > > > /bin/sh: 1: Syntax error: end of file unexpected (expecting ")") > > man 5 crontab says: > [..] > The ``sixth'' field (the rest of the line) specifies the command > to be > run. The entire command portion of the line, up to a > newline or % > character, will be executed by /bin/sh or by the shell specified > in the > SHELL variable of the cronfile. Percent-signs (%) in the > command, un‐ > less escaped with backslash (\), will be changed into newline > charac‐ > ters, and all data after the first % will be sent to the > command as > standard input. > > Regards, > > Leigh. Thanks. Would never have imaged this is the case. -- vr.gr. Freek de Kruijf
What's wrong with this entry in a cron job?
I have the following line in a cron job: 1 1 * * * rm -v /srv/db/webhoneypot-$(date --date=yesterday +%Y-%m-%d).json I get in the journal: Mar 30 01:01:01 rpi4rasphon CRON[1254]: (root) CMD (rm -v /srv/db/webhoneypot- $(date --date=yesterday +) and in the e-mail /bin/sh: 1: Syntax error: end of file unexpected (expecting ")") -- fr.gr. Freek de Kruijf
Re: Pi2 does not boot with debian-10.3.0-armhf-netinst.iso on SDCard
Op vrijdag 24 april 2020 01:37:42 CEST schreef Yves Caniou: > Hi, > > I've been trying to install debian using debian-10.3.0-armhf-netinst.iso > for a Pi2. The image is burned on the SDCard with a dd. The leds of the > Pi2 show access to the SDCard, but nothing shows up on screen and minicom. > Same hardware/SDCard/ElectricSupply/method used with Raspbian and Ubuntu > images are working. > It seems there is a problem with the image itself. > > Cheers. > > .Y Hi Yves, Burning an iso image on a SD card with dd gives a SD card with an iso filesystem on that card. The RPi2 however requires a SD card with a small partition with a FAT16 file system as a primary boot partition and another partition with a linux type file system for the main system. -- fr.gr. Freek de Kruijf
Problem with wpa_supplicant in Buster on a Raspberry Pi 4B
After analyzing an unreliable WiFi connection I did test the wpa_supplicant utility on that connection. So I used the command "wpa_supplicant -c -iwlan0 -d" to see what was wrong. It appeared that the SSID of the AP I want to connect to was entered in the blacklist, later removed, retried again, etc. At a certain moment it succeeded, but a little while later the status was again DISACCOCIATED. Anybody experiencing the same? Is there a workaround? -- fr.gr. Freek de Kruijf
Re: Error message on update of debian jessie on banana pi M64
Op zaterdag 21 juli 2018 03:00:00 CEST schreef Gene Heskett: > On Friday 20 July 2018 17:55:23 Freek de Kruijf wrote: > > Op vrijdag 20 juli 2018 10:36:53 CEST schreef Paul Wise: > > > On Thu, Jul 19, 2018 at 8:14 PM, Freek de Kruijf wrote: > > > I suggest upgrading your system to Debian stretch. > > I've done that, and its much less stable than a jessie install, needing a > powerdown reboot about hourly. Not only that, but logging into a console > to do almost anything I could just do on jessie is now blocked because > the console login is now prevented from running anything that needs x. > This makes maintenance or code development a major pain in the a$$. > I went from the Raspberry Pi 3B to the Banana Pi M64 only because it has 2GB memory instead of 1 GB. I run a number of standard services on it of which email or rather virus scanning became a problem. The system runs headless with only ssh, no X, for maintenance. So I do not have the problems you reported. -- fr.gr. Freek de Kruijf
Re: Error message on update of debian jessie on banana pi M64
Op vrijdag 20 juli 2018 10:36:53 CEST schreef Paul Wise: > On Thu, Jul 19, 2018 at 8:14 PM, Freek de Kruijf wrote: > > W: Failed to fetch > > http://security.debian.org/dists/jessie/updates/InRelease Unable to find > > expected entry 'main/binary-arm64/Packages' in Release file (Wrong > > sources.list entry or malformed file) > > The Debian LTS team does not support arm64 for jessie: > > https://wiki.debian.org/LTS > > I suggest upgrading your system to Debian stretch. > > If you don't want to upgrade and don't need security support: > > http://archive.debian.org/debian/ Appears to be quite easy. Found the method by searching the internet. Thanks for the suggestion. -- vr.gr. Freek de Kruijf
Error message on update of debian jessie on banana pi M64
I got the following error message on "apt update" on a debian jessie system on a Banana Pi M64: W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file) Indeed main/binary-arm64 is missing there. Others like main/binary-armhf or main/binary-armel are available. Should I enter a bug report? -- fr.gr. Freek de Kruijf
