I have tried this, sadly the outcome was the same. Used a 4gb card which I found in my drawer.renice123 wrote: I would start looking for a malfunction with a .....(etc)
uSDHC/XC card size is a bit of a "red herring" apart from 16Gb being, perhaps, a minimum size and some care to be taken (eg. established compatible card reader/writer) for sizes >32Gb. (Virtually all of my P4B cards are various brands of 32Gb size). I'm more suspicious of the two power supplies you've tried - more details needed. For reference and FWIW some measurements of the loading characteristics of the, mainly "official", supplies that I've had access** to (and in one case, associated connecting cable) can be found here:LucaArctos wrote: ↑Sun Dec 01, 2019 8:06 pmI have tried this, sadly the outcome was the same. Used a 4gb card which I found in my drawer.renice123 wrote: I would start looking for a malfunction with a .....(etc)
Rounding up the SD cards used to: Samsung 4gb, Generic (SDHC) 32gb and a SanDisk 128gb.
Thank you a lot for your reply however!
Use Etcher. So much easier than using DD and less prone to making mistakes.renice123 wrote: ↑Mon Dec 02, 2019 7:56 amIt is better to use a 16 GB memory card - you can install full Raspbian on it using the dd utility. I noticed that almost all errors can be divided into several categories.
1. Errors when writing to the OS memory card. But it’s easier to write with the dd command and this will give a stable result! (For some reason, dd do not like, although it is dd that allows you to immediately avoid errors). To this we can add that after the possibility of writing to EEPROM, users feverishly began to overwrite the internal memory (why? In my experience, damage to any firmware is very rare, but an attempt to overwrite the firmware often leads to total problems).
Really? First I have heard about it. And I work here!renice123 wrote: ↑Mon Dec 02, 2019 7:56 am2. Raspberries of the fourth version, apparently, has weak springs in the card reader. On some computers, this leads to unstable operation with the memory card and, of course, causes a freeze.
Some people recommend immediately “lay” thin paper or a dielectric on top of a memory card.
Use the official power supply, voltage sag should not be a problem. It's also very cheap.renice123 wrote: ↑Mon Dec 02, 2019 7:56 am3. The power supply, which at the time of loading sags (voltage decreases), which also causes problems. This can be seen by stopping the glow of the red LED.
Yes, the rpi-update command loads the system a lot.
Do you always have a red LED on? Have you tried to measure the voltage on the power supply? (attention! The death of Raspberry is often caused by measuring the voltage on the GPIO, sometimes the voltmeter probes cause a short circuit and Raspberry dies instantly! It is necessary to measure the voltage of the power supply on the power supply itself - for example, through an adapter)
More often than not? Rubbish. Buster is very stable. I've had one weird issue to do with the ethernet driver since I started using it, from before the Pi4 was released.renice123 wrote: ↑Mon Dec 02, 2019 7:56 am4. More often than not, Raspberry freezes due to Raspbian software errors. This is due to both the instability of the new OS and user actions.
For example, rpi-update is a very “long command" in itself. But it is for some reason that they are beginning to use it on problematic (possibly) computers. Chromium and sometimes network programs using NFS cause deadlocks
There is a very specific combination of resolution, cable and monitor that has caused wifi issues. There is also an as yet not yet fully diagnosed issue with some EDID's some some older devices - I suspect this is bad EDID's built in to the monitors - seen this as least once.
Tru Dat.renice123 wrote: ↑Mon Dec 02, 2019 7:56 am6. Errors of memory cards. Memory cards are written at different speeds, most often this is the low speed of small fragments (4 K). Fake memory cards (especially large ones) or just bad memory cards are even more common.
A fake memory card when trying to write to it can cause the computer to freeze or work extremely slowly, which will also be perceived as a freeze.
renice123 wrote: ↑Mon Dec 02, 2019 7:56 amBased on these errors, we can do the following.
Recording using an dd image to a memory card from 8 to 16 GB (32 GB or higher can be a problem - fakes, for example). Well, if everyone likes Etcher so much, then there is no problem =)
Then configure the system. During the setup of the system, Raspberry works fine, there are no freezes? This is a good symptom!
After this, you can do the following
Log in and try to run some programs. No need to do the potentially problematic rpi-update command! See if freezes occur. Is the red LED blinking? If everything is normal, then the problem of subsequent freezes should most likely be looked for in the memory card.
If freezes occur on a clean system, then you will have to look for a problem for a long time, starting with the fact that the memory card may not fit snugly on the contacts in the card reader and ending with another hardware malfunction
FWIW, these are the card (brands, size ...) I've used with various Pi's since 2012: https://www.cpmspectrepi.uk/raspberry_p ... cards.html
Try this https://www.raspberrypi.org/forums/view ... p?t=249112
Try flashing directly from the .zip archive. Some unzip utilities have trouble with the zip64 format used with Raspbian images. Etcher will extract the image while writing, saving both space and time.
So your card should be okay, that's good.
Not sure I fully understood that. The SSH connection froze as well?
Anything outside of the Raspbian repositories is a crapshoot. It may be fine, but no one associated with Raspbian development has tested it.
Too bad, they are very handy for troubleshooting (you can monitor the shell output and login without a network connection). I use inexpensive CP2102 USB-TTL adapters that can be found on eBay for less than $2 (a bit more if you want fast shipping). There are also Raspberry Pi Console cables available from most Pi resellers.
Code: Select all
watchdog-device= /dev/watchdog watchdog-timeout = 15 temperature-sensor = /sys/class/thermal/thermal_zone0/temp max-temperature = 60 realtime= yes priority = 1