If any of the RPi Foundation's engineers happen to stumble upon this, please tell me what I'm supposed to do because I'm out of ideas. I'm also getting progressively frustrated and disappointed at the Raspberry Pi 4.
I will try and describe the problem as accurately as possible.
I ordered a RPi 4/4GB on June 25th, a day after the announcement, along with an official 5.1V 3A USB C power supply and the official case . I received everything a week later and the board was D.O.A. (see previous post https://www.raspberrypi.org/forums/view ... 8&t=244811
). It's last behaviour was that both the red and the green lights were constantly on. Other than that the board was completely unresponsive and I had no choice but to return it to my supplier within 7 days (Nettop, the only one for Greece).
Due to shortage in supply for the 4GB variant I had to wait two more weeks to receive a new board, which happened on Friday, July 26th. I inserted my previously baked card for the first faulty board and it worked like a charm (The Pi 4 is a leap forward from my previous Pi 3B, but hot as hell, or close to it). I updated, installed apps, tested stuff, stress tested, the whole shebang, without any problems whatsoever, except for the realisation that this one needs cooling desperately. I turned it on, worked, and turned it off by properly shutting down and then also unplugging the power supply, maybe five times in total. And when I got confident enough, I prepared for "the desktop setup". You see, I've been working on a RPi 3B as my daily driver for the last couple of years, that boots from SD and runs from an SSD in a USB enclosure. What this means is that I always have an SD card inserted (no USB booting) and cmdline.txt directs to the SSD as the root, not the 2nd SD partition. So I started working towards setting things up the same way for the Pi 4. I prepared the partitions of the external SSD, rsynced everything from the SD card and changed cmdline.txt on the SD card to point to the SSD. I plugged in everything again, nothing different this time except for the extra SSD connected to the lower USB 3 port.
And then, when I pluggen in the power supply, this happened. Both the red and the green light flashed four times, with a short but noticeable fade out after each light-up, then a small (2 or 3 sec) pause, then the same exact pattern again, four flashes of both lights, each light up followed by a slight fade out, not a sharp turn-off. And the board did not boot of course. I think I unplugged it and plugged it in again only to be greeted with the same behaviour as the first board. No matter whether an SD card is inserted or not the red AND green lights are constantly on, no hdmi output (tried on both ports), no ethernet lights and no signs of life. The thing is once again dead in the water. I tried with two SD cards, that boot just fine on a Pi 2 by the way, to no avail. I reimaged one of them with Buster lite, just in case, yet nothing. There is no response from the board. No boot takes place.
Before anyone asks, yes I have tried the documented procedure of bootloader restoration. But the symptoms I face are not the ones described in the docs. I don't have four flashes without an SD card. I don't have inactive green light. The green light is ALWAYS ON! Needless to say that booting with an SD card containing the two recovery files did nothing to revive the board, nor gave the expected -as documented- behaviour of continuous flashing. Nothing changed.
I have only ever used the Pi 4 with the official power supply, so I reckon that is not the source of the problem.
The SSD is a Samsung 850 480GB that I retired from my white bearded Q6600, where it worked just fine for about two years. The enclosure is a NATEC USB 3 that worked just fine on two desktop PCs. Just a process of elimination for possible causes...
I really hoped the Pi4 would become my little but now capable everyday PC. What I face is a second return, scheduled for tomorrow, with the prospect of a third faulty board, that will happen at a random time and after the 7 day return period, possibly affecting me with return fees, not to mention the inconvenience of an unavailable system and my wasted time.
I read in the forum that all the boards are factory ckecked (no objections there) and that most of the reported problems are proven to be software issues in the end. However, I can in no way explain the behavior of these two board from a software point of view. They just won't boot and what's more frustrating is I don't understand why. Anyone cares to explain?
Oh, by the way, I''m at the point where my local reseller thinks I'm doing "something" to the boards because the only two reported as faulty are mine. I'm not a Pi virgin, so to speak, nor a Linux one, nor a computer noob. I am careful and I read the f****** manual. When I can't find the answers, I come to the forum.
So, what on earth is going on?
This is my Raspberry Pi. There are many like it but this one is mine.