It is a brand new cable.
that's not the point - did you try some of these troubleshooting actions from the url which I provided? eventually you may gather more insights of your problem following these attempts...
It is a brand new cable.
that's not the point - did you try some of these troubleshooting actions from the url which I provided? eventually you may gather more insights of your problem following these attempts...
Feb 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.
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 #
That line looks OK. So you've only removed the "quiet" at the end, added the video option, and now we have an error.
Well I mean it was never working so.......
I don't have this error in my RPi log. I guess the syntax is OK, but not the boot value.
Please write LE to microSD by using https://etcher.balena.io/. It does verification after writing.
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.
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.
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.
Here is my log file hooked up to my new TV with no config changes
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.
I booted with no sdcard. The netboot screen came up and said ESC for diagnostics. I hit ESC and the screen went blank.
I said boot with just hdmi and power connected. No keyboard. Otherwise you won't get the diagnostic display.
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?
If it was defective why would it work on other monitors?
Provide a log from a working display please.
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.
Provide a log from a working display please.
This is the log from when it worked on my Dell monitor.
Thanks. A quick comparison shows that you have an audio problem on Samsung TV, which doesn't exist on Dell:
Feb 16 18:10:58.707366 LibreELEC Boot[471]: ### Setting up sound card ###
Feb 16 18:10:58.707369 LibreELEC Boot[470]: ### Setting up sound card ###
Feb 16 18:10:58.739933 LibreELEC pulseaudio[378]: W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
Feb 16 18:10:58.741242 LibreELEC pulseaudio[378]: W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
Do you use an AVR for audio?
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?