Posts by VLouis

    That way, I won't have to power down the RPi and risk a recurrence of "No Signal" when I power it back up.

    When I had the same issue the solution was to save the display data using the command "getedid create" (SSH).

    1. For the "No Signal":

    Do you have any reason to don't try to save the EDID (display) data from TV? Did you tried to search some info about that command? Maybe to learn something?

    When it's working (on the TV you see what should to be see), go to SSH and run that command...

    Or don't try it... and wait for... something...

    for now I think I'm going to try to track down what is tweaking CEC periodically, which has the effect of turning my tv back on

    2. Turning the TV back on:

    You could have some "unwanted" reboots (RPi power issue?) and it's activated in the CEC settings to wake up the display at the LE boot. (Settitings - System - Input - Peripherals - CEC - "Devices to power on during startup")

    I think Sony did way more with their hdmi control system than they needed to.

    It's a standard communication between the video source (RPI) and display (TV) using dedicated wires in the cable (HDMI). Till now I seen two issues, the cable - defective, wrong contact, poor quality, or the display in stand-by don't offer the display data (EDID info) - like my LG TV. You can try 2 simple things, try with another cable, and try to switch on the TV first then the RPi, to be sure the display data it's available.

    Hi, usually the HDMI is "turned on" only if at the boot is detected a compatibile display (HDMI cable issue, display in stand-by when the LE booting...). Between LE v9 and v11 was major changes, probably the newer version is more "stricter" to get the display information (EDID data). When I had the same issue the solution was to save the display data using the command "getedid create" (SSH).

    I've done this three times with same results. Maybe there is enough info here to chase down this gremlin.

    The NTFS (a proprietary journaling file system developed by Microsoft) support under linux is limited. These errors appears because the linux not able to fix the errors what can be after "unsafe" remove (or power fail, or else). Try the same with EXT4 or EXFAT formatted drives, and you wont get that errors (another story). Maybe the NTFS support will be improved... but for a linux OS, a linux file system (EXT4) is the best and safe choise.

    Looks like the RPi5 is very sensitive to the power source.

    Delivering a maximum of 5.1V, 5A, it supports USB PD (Power Delivery), so Raspberry Pi 5
    can communicate with it and select the most appropriate power profile. This enables
    Raspberry Pi 5 to increase the USB current limit automatically from the default 600mA to
    1.6A, in order to provide extra power for devices connected to the four Type A USB ports.

    (https://datasheets.raspberrypi.com/power-supply/2…oduct-brief.pdf)

    The RPi4 have a maximum USB port output of 1.2A without to request a "genuine" power source.

    So... could be a possibility that the RPi5 to don't "recognize" the power source as a "genuine Raspberry 27W" power source (and limit the power delivery on USB)?

    I did try connecting the tuners to a hub, but not a powered one. I'm reluctant to spend more money on one in order to test this, although I may be able to put my hands on one.

    Try to get one powered hub at least for testing, no need to be USB3, one old could be good too. Just to check it what's happen if the tuners doesn't draw the power from RPi. I'm not saying that the problem can't be something else, but if with one or two (exactly the same) tuner it's working well, should be useful to exclude the power issue.

    I agree with "chewitt". Messing up the system with media files not a smart choise. I always prefere a small but fast SD-card for the LE and something else (NAS, external HDD/SSD, "big" USB-stick) for media files (or anything else). Less headache in the case of system (LE) upgrade, reinstall...

    Currently, I have the computer set up to start with LE first. But if I ever want to switch to Win11, I have to press the ESC key at startup and switch to the BIOS menu to start Windows.

    If you use the LE from removable device (SD-card, USB-stick), why you don't set the LE as first boot and the W11 as second. When you want W11, just remove the LE, and the bios will boot from next available option. And instead to enter in the bios to (temporarly) change the boot order, theoreticaly exist "boot menu key" (I think is the "F9" for HP) to enter to boot select menu. I'm using this for W11 - Xubuntu "dual boot" (installed on different SSD's), my PC is booting directly to W11, if I sometimes want to boot the linux, I hit few times the "F11" key (MSI MB) when starting the bios, and I select the "Xubuntu" to boot.

    Another thing is how do you want to use that PC, if mostly with W11, and only sometimes do you want LE (Kodi), maybe is more simple to install the Kodi under Windows.