I have 4 Raspberry Pi 4 & 5 connected through a switch to a LG 65CX without any problems.
yes it seems there are some switches that don't do pass through CEC. I did not know that was a thing but I guess it is. So I have ordered one that says it does CEC pass through. We will see. Before I looked into it, I was worried it was an LG thing but I don't think so. Glad to hear it works for you.
So it turns out there was a cord that was common in all my testing. The mini-hdmi connector. I tried another one of those that I have and it seems to be working now. I read that the small jumpers can have problems so I am going to get a new long hdmi to mini hdmi cord to replace both cables.
It seems everything is working even CEC. Though I did find out that LG does not let CEC communicate through a switch so that is a problem. But that is something I will have to figure out.
Thank you to all for all your help.
Try a different HDMI port on TV. Sometimes HDMI ports have different specs on the same device.
I have tried that but I will try it again, with the current settings.
So you want to listen to TV speakers. Go into TV settings, and search for HDMI audio settings. Maybe audio is disabled for HDMI. If you find something, enable it, and reboot RPi.
It is not disabled because I have used other audio via hdmi. My xbox works fine for instance.
so I don't know that means, except that it has to be a kodi setting, but If I do:
systemctl stop kodi
The boot splash comes back so it is can still connect to the TV
but when I start it again:
systemctl start kodi
boom, back to blank screen.
Can I try different resolution from the cmd line?
I mean I own one but it is not hooked up. I don't even think I have hooked up the optical cable from the TV to the RPi4. The only thing plugged into the RPi is power and the mini-hdmi to hdmi connector.
so I don't know that means, except that it has to be a kodi setting, but If I do:
systemctl stop kodi
The boot splash comes back so it is can still connect to the TV
but when I start it again:
systemctl start kodi
boom, back to blank screen.
Can I try different resolution from the cmd line?
Provide a log from a working display please.
This is the log from when it worked on my Dell monitor.
I said boot with just hdmi and power connected. No keyboard. Otherwise you won't get the diagnostic display.
When I do this the TV just says "No Signal" I don't get a boot or a splash screen or anything.
Yes, it has the same error (post #21) with the original cmdline.txt. I'm starting to think that your hardware is defective. Please try Raspberry Pi OS on another microSD to rule that out. HDMI seems to be OK.
I've changed your status to "member", so you can post faster now.
If it was defective why would it work on other monitors? It just happened to break when I moved to my new TV?
Can you just connect hdmi and power (no sdcard inserted) and check output on display.
You should see a diagnostic screen. Report the output of the "display:" line.
I booted with no sdcard. The netboot screen came up and said ESC for diagnostics. I hit ESC and the screen went blank.
On a side not, I am clearly not a spammer and hopefully considered a good, if new, member of the community. Can I have my "Time to post" reduced so that I can more quickly respond to the help that I am getting? If not I understand just wanted to ask.
Since I can only post very 40 min I am going to cram in as much as I can.
Here is my log file hooked up to my new TV with no config changes
Then I made this change:
LibreELEC:~ # cat /flash/cmdline.txt
boot=UUID=1507-5354 disk=UUID=077f401e-ddf6-42b9-95f9-dfb3c6c109f1 video=HDMI-A-1:1920x1080M@60D
LibreELEC:~ #
And this is the log for that boot.
I just did a fresh install I have not configured anything but the wifi and I am getting the same notification.
This is not an error and it is booting fine so I don't think it is the issue. I believe that is just a warning.
Well I mean it was never working so.......
CodeFeb 16 18:10:56.923038 LibreELEC kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:94:E2:98 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 boot=UUID=1507-5354 disk=UUID=077f401e-ddf6-42b9-95f9-dfb3c6c109f1 video=HDMI-A-1:1920x1080M@60D Feb 16 18:10:56.923082 LibreELEC kernel: Unknown kernel command line parameters "boot=UUID=1507-5354 disk=UUID=077f401e-ddf6-42b9-95f9-dfb3c6c109f1", will be passed to user space.Have a look at cmdline.txt again (especially the separator before "boot=...").
The content of this file has to be one line. Options are only separated by one space sign. No newline, tab etc.
I don't have any separator before boot in that file. Any extra space there would have to come from whatever concatenated that string before it.
Pixie:/flash # cat cmdline.txt
boot=UUID=1507-5354 disk=UUID=077f401e-ddf6-42b9-95f9-dfb3c6c109f1 video=HDMI-A-1:1920x1080M@60D
Pixie:/flash #
So since i cannot see anything when it posts the link does it post more than one boot cycle? Because i will have to boot it then turn it off then boot it on another monitor to be able to post the logs? If not is there a cmd line way to do it?
My old TV was a 4K TV. I have tried multiple cables all with the same results. I have a brand new cable for 8k. The cable works on multiple devices for this TV.
Okay so I have learned a few things.
I switched back to see if I could get OSMC running again. It is not working. So I don't know why it worked for a while. Does the working for a while indicate the video driver hardware is being overwhelmed or requiring to send too much signal, or it is not enough signal?
I learned that the config.txt and the cmdline.txt are pi configs not specific to LE.
so it seems that the pi is just unhappy and that is not necessarily LE so I was wrong in using that terminology.
I made the update you suggested, I also remove quite from the boot. So now when I turn it on I see the boot process. So it can show something. After it booted, it showed the kodi screen for about a sec then went black and had clicking from the audio.
At 4K?
I don't know at the default settings, it just booted right up. I don't really care if it is at 4k nothing I have is in 4k. So if I can disable that to make it work I will be happy.
Try without that switch.
I was trying it without the switch before I installed the switch for the other devices. So that does not seem to be the problem. My xbox ran through the switch for a few hours yesterday with no issues.
