Results 1 to 3 of 3

Thread: Raspberry pi 4 won't boot withnout hdmi connected

  1. #1

    Question Raspberry pi 4 won't boot withnout hdmi connected

    I recently installed tumbleweed on my raspberry pi 4, everything is working fine except booting.
    When i try to boot withnout hdmi connected, it doesn't do anything.

    I tried adding the following to /boot/config.txt:
    Code:
    hdmi_force_hotplug=1
    hdmi_group=1
    hdmi_mode=16
    but it didn't make any difference.

    But when i tried adding the same to /boot/efi/extraconfig.txt, a rainbow screen pops up while booting, but still doesn't boot up withnout hdmi connected.

    What can i do to fix this?
    Thanks

  2. #2
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,307

    Default Re: Raspberry pi 4 won't boot withnout hdmi connected

    From https://forums.raspberrypi.com/viewt...p?f=28&t=58151

    Even when the Pi boots successfully, you might not necessarily get a video signal that your monitor recognizes immediately
    The Raspbian OS is designed to output a HDMI signal, but if it doesn't detect a HDMI device connected to the Pi, it will default to generating a composite signal on the RCA port (or 4-pins 3.5mm A/V jack on later models). Depending on the monitor you are using, you may have to switch it on before you boot the Pi, and ensure that HDMI input is selected.

    Booting to NOOBS works a bit differently: it will always output an HDMI signal, even if you have nothing connected to the HDMI port, unless you press one of the numerical keys, 3 (PAL) or 4 (NTSC), to switch to a composite video output mode.
    Depending on your PI version, this might be it.

  3. #3

    Default Re: Raspberry pi 4 won't boot withnout hdmi connected

    Quote Originally Posted by brunomcl View Post
    From https://forums.raspberrypi.com/viewt...p?f=28&t=58151



    Depending on your PI version, this might be it.
    This is for rasbian OS though, i use tumbleweed so its probably different.

    Also, I am sure it isn't booting since i have an ssh service that runs on startup. The only thing that might be preventing the startup service to start is the login screen, but i am not sure about that.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •