Hmm, so the 100k shipped that work fine means nothing? Where do you get the figures for non-working boards? And why do you think they leave the factory untested? (they don't)k-pi wrote: ↑Tue Jul 02, 2019 3:47 pmAs the title says, just received my RPi4B/4GB from The PiHut, & the HDMI output is dead, not a hint of anything from either socket, trying with my 2 brand new microHDMI cables, the only thing that appears to work is the new PSU!
This is a straight swap over of the mSDHC card from my RPi3B+ which I had set up Buster on 2 days ago!
What a disaster this board seems to be, lots of useless boards being shipped out, presumably untested!
This is after waiting for them to restock as well!
Because of all the problems being encountered since the launch of this model on these forums.Where do you get the figures for non-working boards? And why do you think they leave the factory untested? (they don't)
If you put this line in config.txt
Code: Select all
Are you able to SSH, ping? If you can gain access to the console via SSH I am sure it will be a lot easier to troubleshoot this one.k-pi wrote: ↑Tue Jul 02, 2019 7:29 pmAll the equipment is official Raspberry Pi, the PSU & mHDMI cables. Plus a fresh installation of Buster 2 days ago, which worked in my RPi3B+.
Rebooted with the cable in the other socket, & got the expected blank.
Rebooted, mHDMI cable back in HDMI0, & now I get 640x480, 4 raspberries, the logo, & then......nothing, again!
That looks like "EDID info. interpretation (confusion) issues" to me. AIUI different code is "controlling" the HDMI output in "console mode" cf. "desktop mode". The tvservice command (which now has some new options) is still the first source of info. There are some additional diagnostics that can "delve deeper" but I'm not the "main expert" in their interpretation. As I suggested in my previous post it may be useful to compare the behaviour of Buster with your display on your P3B+ with its behaviour on the P4B and, hopefully, separate "Buster only" issues from "Buster + P4B" issues. For example the "not underscanning" issue I have with some of my TV's appears to be mainly a "Buster" issue as the same issue occurs with a cloned uSDHC card on an old B2 Pi: http://www.cpmspectrepi.uk/raspberry_pi ... kTest.html ie. I resort to a VNC setup because using the HDMI2 input on the TV (+ a USB KM switch) still has an overscanned display.k-pi wrote: ↑Tue Jul 02, 2019 7:25 pmSo, tried again, with the 'safe mode' option, & whilst it seemed to be booting, continually moved the mouse, it first entered 640x480, then changed into 1280x768, (it doesn't do 1366x768in HDMI).
So, Ive got it to boot once, at least - lets hope this has sorted out whatever the problem was when it was first powered on - it's not nice spending money & getting duff results.
No, it's using 1024x768 on this 1366x768 monitor, & the desktop says the HDMI0 socket is HDMI-2. Trying to change it with the Screen Layout Editor, it just reverts back to 1024x768 from 1366x768 that I try to save.
I'm going to try my mHDMI cable in the other socket, & reboot.
I'll try that in the morning, getting late here, & my brain is/has got befuddled trying to get this thing working properly, thanks.
Problem here is that it worked fine on the RPi3B+, same Buster mSDHC card, same monitor.That looks like "EDID info. interpretation (confusion) issues" to me.
If nothing above seems to work, do this ^
This statement is complete nonsense on so many levels I don't even know here to start.