No hdmi signal on Pi4 using "hdmi1" after upgrading #1159
Comments
|
The connectors are numbered 0 & 1, where 0 is nearest the USB C power socket. |
richrboo
changed the title
|
Thanks. Sorry for the confusion, I saw that Raspbian uses hdmi1 and 2 in screen config. I have edited the report. |
|
I assume by upgrade you mean using rpi-update? Can you explain the exact configuration you have when it fails? |
|
When you first boot 2019-06-20 release, it has a gui checking for an update and then upgrades. After upgrading I then reboot and lose hdmi1. I assume it is doing apt-get update and upgrade behind the gui. I was only using one hdmi connection, hdmi1. This was plugged in to a TV. hdmi_enable_4k=1 is not enabled. |
|
A colleague tried his Pi4 and his hdmi sockets work. Using his working sdcard in my Pi, and hdmi1 doesn't work ruling out any sdcard issue. So possibly a hardware fault, but it did work with 2019-06-20 release, before the gui did the update. |
|
Does applying a little pressure (keep it light) to the hdmi plug when booting make it work? If so that would suggest a mechanical failure between PCB/hdmi socket/cable. |
|
Nope. There was no play at all, applying pressure made no difference. I've been back to the Pi shop and exchanged it, Tim helped and is holding my Pi to show an engineer. However now back in the office and I have the exact same issue with the exchanged one. |
|
It looks like there may be an issue with 4k30 on HDMI1 as I have replicated this. There are slight hardware differences between the two, and HDMI0 is the more capable port. Can you try adding to config.txt to force it to 1080p60 and reboot? At least that will confirm if you do have another dodgy board, or is it "only" software. |
|
I went back to the shop. They are seeing issues with dual monitor and using hdmi1 too. I have yet to try the above, but have a 3rd Pi4. This is no better. The shop think it isn't hardware issue, but very strange my colleague Pi4 works as expected on either hdmi. I'll use a single monitor on hdmi0 for now. The Pi store have two boards for investigation at least. Hopefully a software fix can be found. |
|
No point returning more Pi's - this is a software issue that seems to affect some setups and not others. |
|
Did you add |
|
I didn't have Using |
|
Can you test whether latest rpi-update firmware fixes your issue without adding |
|
I am not the original reporter but I have the same issue: single monitor connected on HDMI1 shows no picture. Result after rpi-update + cold boot: short flash of boot rainbow and raspberries and then dark again. |
|
dmesg shows several entires related to DRM, if that's related. |
|
@giddyhup I assume monitor works when connected to HDMI0? report? |
|
I can't use HDMI0, my adapter is too wide. HDMI1 worked when I booted the original buster image (slimmed desktop version). |
|
What does |
|
... |
|
Without monitor or when plugging in monitor when the Pi is already running With monitor after boot: Remark: it looks like the monitor goes blank at the stage where the greeter would appear. The rainbow pixel, the raspberries and the splash screen appear (albeit it is rather fast). |
|
I'm interested in results of booting with display already connected to HDMI1. |
|
I can't reproduce the stuck-at-boot situation reliably but I am SSHing all the time, I currently have neither keyboard nor mouse attached. |
|
recent dmesg entries: |
|
So "With monitor after boot:" means the monitor was plugged in before boot? |
|
Yes. Monitor was plugged in before boot. Monitor does not appear to support 4k. |
|
Latest syslog output: |
|
The vc4_crtc_atomic_flush backtrace is known and harmless. See: |
|
Okay your issue may be something new. OP was using 3840x2160@30 which needs more than 250MHz pixel clock (and also core_freq) and I was able to reproduce that. 1080p60 only requires 148.5MHz so I'd have thought 250MHz would be fine (and is in my setup). |
|
@Brian-Milnes Just to confirm, you have done an rpi-update to get the latest firmware, and you have the 4k monitor in HDMI port 0? |
|
Hi James |
|
@Brian-Milnes if you want to help test, download: Note: kodi won't use the dual displays, but it would be nice to identify why it hangs when second display is attached. There was a CEC related fix that could cause a hang on boot when using hdmi1 in latest firmware. |
|
It is August now. I'm just reporting the the same thing is happening to me when I applied the raspberries update right after the initial install on a new pi4 on August 22nd. It is clear is an upgrade software/config issue. I am connected to an OLED LG 4K TV which supports 30hz as well as 60hz. With the initial noobs software for the pi4 it works fine with the defaults picked--4K 30hz i believe. TV is plugged into HDMI 1 (as reported by raspberian) and the physical connector next to the power input. |
|
Official power supply. Same issues with an older Samsung TV when reboot upgrading the OS. Using |
|
This worked for mi config_hdmi_boost=4 |
|
Oct 23 2019. Same issue here. I tried LibreELEC-RPi4.arm-9.1.501.img (as OS-1) and 2019-09-26-raspbian-buster (as OS-2). One monitor via HDMI.
|
|
@htpbreewel If your issue is solely with audio, then that is NOT this issue. HDMI audio is routed independently of video. |
|
I'm using the latest version of Libreelec on a Raspberry Pi 4 and I am trying to use it with a 75" Samsung TV. My issue is that if I use all the same hardware and cables and boot it up with Raspbian installed, all works fine and it displays correctly on the TV, but if I swap out the SD card and boot up with Libreelec, I just get the no source error. I know the SD card is fine because if I plug it into a monitor Librelec is running. Libreelec doesn't seem to like the Samsung TV. Is it something to do with resolution and frequency? |
|
You can try to change to hfmi-failsefe in config.txt
See if that works.
send from mobile
Den tis 12 nov. 2019 05:28lloyd61 <[email protected]> skrev:
… I'm using the latest version of Libreelec on a Raspberry Pi 4 and I am
trying to use it with a 75" Samsung TV. My issue is that if I use all the
same hardware and cables and boot it up with Raspbian installed, all works
fine and it displays correctly on the TV, but if I swap out the SD card and
boot up with Libreelec, I just get the no source error. I know the SD card
is fine because if I plug it into a monitor Librelec is running. Libreelec
doesn't seem to like the Samsung TV. Is it something to do with resolution
and frequency?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1159?email_source=notifications&email_token=AIJOPLSE4KFW3VSVS43PFW3QTIWHHA5CNFSM4H3M5IP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDY7UNY#issuecomment-552729143>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJOPLUH2YA5CKQLMYJDSY3QTIWHHANCNFSM4H3M5IPQ>
.
|
|
With LibreElec only the HDMI port closest to the power jack works on
the Pi 4 (for the time being?). Not the second one.
Op 12-11-2019 om 10:44 schreef mullcom:
… You can try to change to hfmi-failsefe in config.txt
See if that works.
send from mobile
Den tis 12 nov. 2019 05:28lloyd61 ***@***.***> skrev:
> I'm using the latest version of Libreelec on a Raspberry Pi 4 and I am
> trying to use it with a 75" Samsung TV. My issue is that if I use
all the
> same hardware and cables and boot it up with Raspbian installed, all
works
> fine and it displays correctly on the TV, but if I swap out the SD
card and
> boot up with Libreelec, I just get the no source error. I know the
SD card
> is fine because if I plug it into a monitor Librelec is running.
Libreelec
> doesn't seem to like the Samsung TV. Is it something to do with
resolution
> and frequency?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
>
<#1159?email_source=notifications&email_token=AIJOPLSE4KFW3VSVS43PFW3QTIWHHA5CNFSM4H3M5IP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDY7UNY#issuecomment-552729143>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/AIJOPLUH2YA5CKQLMYJDSY3QTIWHHANCNFSM4H3M5IPQ>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1159?email_source=notifications&email_token=AMVWT5FYB5FVJ7LCU7RHG2TQTJ3JFA5CNFSM4H3M5IP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZUYQI#issuecomment-552815681>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMVWT5B6MH6NQY2SCTW37D3QTJ3JFANCNFSM4H3M5IPQ>.Web
Bug from
https://github.com/notifications/beacon/AMVWT5GFTRYIJB2AXGZBK5LQTJ3JFA5CNFSM4H3M5IP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZUYQI.gif
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage",
"potentialAction": { ***@***.***": "ViewAction", "target":
"#1159?email_source=notifications\u0026email_token=AMVWT5FYB5FVJ7LCU7RHG2TQTJ3JFA5CNFSM4H3M5IP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZUYQI#issuecomment-552815681","url":
"#1159?email_source=notifications\u0026email_token=AMVWT5FYB5FVJ7LCU7RHG2TQTJ3JFA5CNFSM4H3M5IP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZUYQI#issuecomment-552815681",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { ***@***.***": "Organization", "name": "GitHub", "url":
"https://github.com" } } ]
|
|
Thank you for the feedback and suggestions. After manipulating the config.txt file, I was able to get an image from the HDMI socket closest to the board corner, nothing from the inner socket. But that still wasn't the end of it, no matter what I did I could not get any sound. In the end I went back to my faithful Pi 3B+, imaged the same SD card, plugged it in and all worked straight away. |
|
@popcornmix I have had the same issue with two different Raspberry Pi 4 boards and two separate televisions (a Panasonic and a LG OLED65C9PLA 4K QLED TV). Nothing would work initially, I was getting No Signal on both TVs regardless of the hdmi_ configuration that I would put into the config.txt. I already have an RPi 3 B+ running but wanted to replace it with a 4K capable device. Note that all tests here are conducted using LibreElec 9.2.0 (Leia) that runs Kodi 18.5 as my home theatre solution.
I experimented some more and found that adding hdmi_enable_4kp60=1 to config.txt does allow it to be seen on the LG TV (still using start4.ef and fixup4.dat too). However there is speckling/interference on the screen. This only works on HDMI 1 though (not HDMI 0 surprisingly) - HDMI 0 only shows the Rainbow screen and LibreElec boot screen. HDMI 1 also shows the Kodi boot screen and then full interface, just with interference. Other notes for the LG screen:
EDIT: Missed it eariler in the documentation but config_hdmi_boost does nothing on an RPi 4 so that explains 3. The interference is too bad for an RPI 4 to be used with the LG (I have tried different HDMI cables too). Any other suggestions above what is above? I can ssh to it and run any diagnostics. @lloyd61 I feel your pain.... :) Maybe time to hack a Fire TV stick to get 4k if this can't be fixed :( |
Did you try setting hdmi_drive=2 in the config.txt |
|
Hi, I am having issues with displaying any HDMI output from my new RPI4 (4GB) on TV Panasonic Viera TX-l55DT50E. I am using os.: 2020-02-05-raspbian-buster-lite.img up-to-date including rpi-firmware. I tried almost every possible important configurations located in /boot/config.txt without success. Currently I have this configuration in /boot/config.txt: hdmi_force_mode=1 pi@raspberrypi:~ $ /opt/vc/bin/tvservice -m CEA https://www.raspberrypi.org/documentation/configuration/config-txt/video.md System pi@raspberrypi:~ $ cat /etc/rpi-issue pi@raspberrypi:~ $ vcgencmd version Can anyone please help with this issue ? |
|
@blacksocket Hi, I have the same problem, no output to Panasonic TV, were you able to find solution? |
|
Hi Misak, unfortunately I was not able to fix it yet.. ;-/ |
|
Hi @blacksocket, it was a pain, but I find out, that it was caused by HDMI cable (the one that is working for other devices normally). I've switched to more quality one and now I have hdmi output from RPI 4 to Panasonic TV. |
|
Great, I just changed the cable and indeed it works like a harm! |
|
I had various signal problems with supposedly 4K / 2160p cables, including with my YouView STB and Raspberry Pi.
These issues were resolved by using accredited cables:
[HDMI Premium certified cable]Known as Premium Certified cables, the packaging for each cable will display a QR code. Scanning this QR code will confirm that the cables perform to the required level.
Premium Certified HDMI Cable - Anti-Counterfeiting System:
This new development ensures that HDMI cables have been tested and certified to meet the requirements of Premium HDMI cable specification.
The anti-counterfeiting label shown on the packaging of a Premium HDMI Cable has encrypted data in the QR code which will allow you to quickly verify the authenticity of the cable by using your smart phone with the free-to-download HDMI Premium Cable App.
In purchasing this Premium HDMI cable, you can confidently and reliably enjoy viewing 4k UHD content without interference or signal/connectivity issues.
Brian Milnes
+44 7971 886 113
www.ind-tech.com<http://www.ind-tech.com/>
From: Tomas <[email protected]>
Sent: 17 April 2020 08:45
To: raspberrypi/firmware <[email protected]>
Cc: Brian Milnes <[email protected]>; Mention <[email protected]>
Subject: Re: [raspberrypi/firmware] No hdmi signal on Pi4 using "hdmi1" after upgrading (#1159)
Hi Misak, great! Whet exactly cable are you using now ? Can you share the parameters you used in your configuration in /boot/config.txt ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1159 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AG3IT5KJQY74SZ4BYLUPS73RNACH7ANCNFSM4H3M5IPQ>.
|
|
I have no signal on either HDMI port. The HDMI firmware on the Pi 4 seems to be a bit of a disaster. Pi 3 and 3B+ worked fine with the same SD card and cables. Have tried two Pi 4 devices so not hardware related. Have also tried different cables as well as all the settings above, except for changing min clock speed. |
|
@Squuiid I hope you weren't expecting anything to change as a result of your comment. If that was meant to be a bug report, try again. |
The HDMI HW on the Pi4 has changed considerable. It works for the vast majority of people, but we have had some reports of devices being recalcitrant to work. We have one device in for testing so far (1366x768 resolution is the main problem). |
|
@JamesH65 thank you for the quick response. Where can I file a proper and full bug report to better assist with getting this issue resolved? |
|
Just wanted to add that my first rpi4b 4GB behaves oddly. If i unplug everything, no SD just HDMI1 connected to microHDMI adapter, i do get to see Berry and it trying to boot. Will most likely be sending this berry back. Also, cannot install OS due to boot not working (no blinking green LED) when micro HDMI adapter connected. |
|
@jimi3 You need to check the output is set correctly - hope you haven't got a flaky unit! |
|
I am hopping it is the adapter cable, ordered a replacement and wrote to the Shop about it. |
|
Are you using a Pi supplied PSU too? (That's definitely worth doing...) |
|
yes, PSU is from Pi |
|
Asking if this is still an ongoing issue? I am screwing with this on my PI 4 with zero success. Port 0 will not work pre or post update. Port 1 works until rasberian update |
hdmi1 is lost after upgrading Pi4. Switching to hdmi0 gets the Pi4 booting again (the one nearest usb-c), but hdmi1 no longer works.
I can get hdmi1 working again, by reflashing SD card to 2019-06-20 release and avoid upgrading. So I'm assuming software issue, rather than a faulty Pi4.
The text was updated successfully, but these errors were encountered: