1. Forum
  2. FidoNet
  3. RBERRYPI

  • Re: Monitor blank after Fedora boot

    From Theo@3:770/3 to Marco Moock on Wed Jan 10 11:59:36 2024
    Marco Moock <mm+usenet-es@dorfdsl.de> wrote:
    Hello!

    I am currently trying to install Fedora on Pi4.

    I copied the aarch raw image to the card and booted from it.
    The boot starts and the monitor shows the kernel messages.

    After that, the screen stays empty. Keyboard works, network too (I
    can't login because no user is yet available).

    How can I make the screen output work here?

    Is it perhaps displaying on the second HDMI port?

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Wed Jan 10 12:39:36 2024
    Hello!

    I am currently trying to install Fedora on Pi4.

    I copied the aarch raw image to the card and booted from it.
    The boot starts and the monitor shows the kernel messages.

    After that, the screen stays empty. Keyboard works, network too (I
    can't login because no user is yet available).

    How can I make the screen output work here?

    --
    kind regards
    Marco

    Spam und Werbung bitte an ichwillgesperrtwerden@nirvana.admins.ws

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Wed Jan 10 14:18:14 2024
    Am 10.01.2024 um 11:59:36 Uhr schrieb Theo:

    Is it perhaps displaying on the second HDMI port?

    Not connected at boot and doesn't show something when I connect it.

    I also can't connect both because I only have one HDMI to DVI cable and
    only one Mini HDMI to HDMI adapter.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Wed Jan 10 14:20:34 2024
    Am 10.01.2024 um 14:18:15 Uhr schrieb Marco Moock:

    Not connected at boot and doesn't show something when I connect it.

    I now tried booting with monitor on HDMI0 (not connected before), but
    the same situation occurs.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Andy Burns@3:770/3 to Marco Moock on Wed Jan 10 14:06:22 2024
    Marco Moock wrote:

    schrieb Theo:

    Is it perhaps displaying on the second HDMI port?

    Not connected at boot and doesn't show something when I connect it.

    Not on an rPi just a PC, but I was recently having similar issues with Fedora37, which if not connected to the displayport monitor at boot
    time, wouldn't output to the monitor after switching KVM from laptop to
    the PC ...

    Upgrading to Fedora40 /seems/ to have fixed the issue (only been done a
    couple of days, so not absolutely certain).

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Marco Moock on Wed Jan 10 14:46:46 2024
    Marco Moock <mm+usenet-es@dorfdsl.de> wrote:
    Am 10.01.2024 um 14:06:22 Uhr schrieb Andy Burns:

    Marco Moock wrote:

    schrieb Theo:

    Is it perhaps displaying on the second HDMI port?

    Not connected at boot and doesn't show something when I connect it.


    Not on an rPi just a PC, but I was recently having similar issues
    with Fedora37, which if not connected to the displayport monitor at
    boot time, wouldn't output to the monitor after switching KVM from
    laptop to the PC ...

    Does the Pi support Displayport?

    No it doesn't, it's HDMI only.

    Some DP outputs can switch into HDMI mode and drive HDMI monitors via a
    passive converter, but I'm not sure DP inputs can accept HDMI.

    Is there a workaround?

    You'd need an active HDMI to DP converter.

    But the fact it's working during boot suggests it's not a monitor incompatibility, since it can clearly drive the monitor to begin with.

    One thought might be that the desktop is driving the monitor to some
    resolution it's not happy with - perhaps worth trying is to configure the output with some safe resolution like 640x480 and see if it accepts it.

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Wed Jan 10 15:29:54 2024
    Am 10.01.2024 um 14:06:22 Uhr schrieb Andy Burns:

    Marco Moock wrote:

    schrieb Theo:

    Is it perhaps displaying on the second HDMI port?

    Not connected at boot and doesn't show something when I connect it.


    Not on an rPi just a PC, but I was recently having similar issues
    with Fedora37, which if not connected to the displayport monitor at
    boot time, wouldn't output to the monitor after switching KVM from
    laptop to the PC ...

    Does the Pi support Displayport?
    Is there a workaround?

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Andy Burns@3:770/3 to Marco Moock on Wed Jan 10 15:47:54 2024
    Marco Moock wrote:

    schrieb Andy Burns:

    I was recently having similar issues with Fedora37, which if not
    connected to the displayport monitor at boot time, wouldn't output
    to the monitor after switching KVM from laptop to the PC ...

    Does the Pi support Displayport?

    Not directly, but adapters are cheap, e.g. <https://amazon.co.uk/DPsource-to-HDMIsink/dp/B09CYYF5NN?th=1>

    Is there a workaround?

    What version of Fedora is on the rPi?

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Andy Burns on Wed Jan 10 17:23:54 2024
    Andy Burns <usenet@andyburns.uk> wrote:

    Marco Moock wrote:

    schrieb Andy Burns:

    I was recently having similar issues with Fedora37, which if not
    connected to the displayport monitor at boot time, wouldn't output
    to the monitor after switching KVM from laptop to the PC ...

    Does the Pi support Displayport?

    Not directly, but adapters are cheap, e.g. <https://amazon.co.uk/DPsource-to-HDMIsink/dp/B09CYYF5NN?th=1>

    That's the wrong way round, you need something like: https://www.amazon.co.uk/Cable-Matters-DisplayPort-Adapter-Resolution/dp/B07SRW29PG/

    Your link is also only a passive adapter, so only works if the source DP already supports HDMI protocol (aka DP++).

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Andy Burns@3:770/3 to Theo on Wed Jan 10 18:00:16 2024
    Theo wrote:

    Andy Burns wrote:

    <https://amazon.co.uk/DPsource-to-HDMIsink/dp/B09CYYF5NN?th=1>

    That's the wrong way round,

    Turns out I actually searched for "DP source to HDMI sink" instead of
    "HDMI source to DP sink" ... I was a little surprised they were as cheap
    and easy as to find as that.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Wed Jan 10 20:03:30 2024
    Am 10.01.2024 um 15:47:54 Uhr schrieb Andy Burns:

    Marco Moock wrote:

    schrieb Andy Burns:

    I was recently having similar issues with Fedora37, which if not
    connected to the displayport monitor at boot time, wouldn't output
    to the monitor after switching KVM from laptop to the PC ...

    Does the Pi support Displayport?

    Not directly, but adapters are cheap, e.g. <https://amazon.co.uk/DPsource-to-HDMIsink/dp/B09CYYF5NN?th=1>

    Is there a workaround?

    What version of Fedora is on the rPi?

    Fedora-Server-39-1.5.aarch64.raw.xz is the image I used.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Thu Jan 11 09:17:18 2024
    Am 10.01.2024 um 20:03:30 Uhr schrieb Marco Moock:

    Am 10.01.2024 um 15:47:54 Uhr schrieb Andy Burns:

    Marco Moock wrote:

    schrieb Andy Burns:

    I was recently having similar issues with Fedora37, which if not
    connected to the displayport monitor at boot time, wouldn't
    output to the monitor after switching KVM from laptop to the PC
    ...

    Does the Pi support Displayport?

    Not directly, but adapters are cheap, e.g. <https://amazon.co.uk/DPsource-to-HDMIsink/dp/B09CYYF5NN?th=1>

    Is there a workaround?

    What version of Fedora is on the rPi?

    Fedora-Server-39-1.5.aarch64.raw.xz is the image I used.

    I now tried Debian, same problem. Boot log is shown, after that screen
    blank.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Marco Moock on Thu Jan 11 09:31:26 2024
    Marco Moock <mm+usenet-es@dorfdsl.de> wrote:
    I now tried Debian, same problem. Boot log is shown, after that screen
    blank.

    That suggests the problem is that the monitor claims it can do such-and-such resolution, and then isn't happy when the Pi does it. Do you have a menu button on the monitor you can press and does it tell you the resolution, or does it say 'no signal' or 'out of range' or something?

    I'd guess the solution is to configure the desktop environment to use a different resolution, but it will depend on the DE as to how you configure
    that from the command line without using the DE's settings UI (which you
    can't see).

    You could also try xrandr after setting a $DISPLAY variable, something like:

    $ export DISPLAY=:0
    $ xrandr --mode 640x480

    which should temporarily set the resolution to 640x480. Then you can get
    into the settings UI.

    Note this is for X11 - I'm not sure what the equivalent is for Wayland.

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Andy Burns@3:770/3 to Theo on Thu Jan 11 10:15:22 2024
    Theo wrote:

    You could also try xrandr after setting a $DISPLAY variable
    Note this is for X11 - I'm not sure what the equivalent is for Wayland.

    You need a "helper" such as gnome-randr.py or gnome-randr-rust these are
    not part of Fedora

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Thu Jan 11 14:07:28 2024
    Am 11.01.2024 um 09:31:26 Uhr schrieb Theo:

    That suggests the problem is that the monitor claims it can do
    such-and-such resolution, and then isn't happy when the Pi does it.
    Do you have a menu button on the monitor you can press and does it
    tell you the resolution, or does it say 'no signal' or 'out of range'
    or something?

    I have now testet another monitor, in Debian all is fine.
    With Fedora, the problem still exists.

    The monitor shows "no signal".

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Thu Jan 11 19:52:46 2024
    Am 11.01.2024 um 14:07:29 Uhr schrieb Marco Moock:

    Am 11.01.2024 um 09:31:26 Uhr schrieb Theo:

    That suggests the problem is that the monitor claims it can do such-and-such resolution, and then isn't happy when the Pi does it.
    Do you have a menu button on the monitor you can press and does it
    tell you the resolution, or does it say 'no signal' or 'out of
    range' or something?

    I have now testet another monitor, in Debian all is fine.
    With Fedora, the problem still exists.

    The monitor shows "no signal".

    Can that issue come from the DVI to HDMI cable?

    I don't have any HDMI compatible monitor at all, I only have some that
    have VGA/DVI and I have a simple adapter cable.
    Maybe the output after the boot isn't acceptable for the DVI monitor?

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Marco Moock on Thu Jan 11 20:50:14 2024
    Marco Moock <mm+usenet-es@dorfdsl.de> wrote:
    Am 11.01.2024 um 14:07:29 Uhr schrieb Marco Moock:

    Am 11.01.2024 um 09:31:26 Uhr schrieb Theo:

    That suggests the problem is that the monitor claims it can do such-and-such resolution, and then isn't happy when the Pi does it.
    Do you have a menu button on the monitor you can press and does it
    tell you the resolution, or does it say 'no signal' or 'out of
    range' or something?

    I have now testet another monitor, in Debian all is fine.
    With Fedora, the problem still exists.

    The monitor shows "no signal".

    Can that issue come from the DVI to HDMI cable?

    I don't have any HDMI compatible monitor at all, I only have some that
    have VGA/DVI and I have a simple adapter cable.
    Maybe the output after the boot isn't acceptable for the DVI monitor?

    Single link DVI only goes up to 1080p. Maybe the monitor is declaring
    itself to support some higher resolution, and then balking when the Pi sends it? Or maybe the Pi is sending HDMI instead of DVI and the monitor can't handle that? The Pi can't do dual-link DVI but maybe the monitor is telling
    it to do a dual-link-only resolution?

    There are some settings in config.txt and cmdline.txt that would be worth playing with: https://www.raspberrypi.com/documentation/computers/config_txt.html#video-options
    https://www.raspberrypi.com/documentation/computers/configuration.html#hdmi-configuration

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Marco Moock@3:770/3 to All on Fri Jan 12 08:29:30 2024
    Am 11.01.2024 um 20:50:14 Uhr schrieb Theo:

    Single link DVI only goes up to 1080p. Maybe the monitor is declaring
    itself to support some higher resolution, and then balking when the
    Pi sends it? Or maybe the Pi is sending HDMI instead of DVI and the
    monitor can't handle that? The Pi can't do dual-link DVI but maybe
    the monitor is telling it to do a dual-link-only resolution?

    Monitor is ASUS VW22AT, 1680*1050.

    There are some settings in config.txt and cmdline.txt that would be
    worth playing with: https://www.raspberrypi.com/documentation/computers/config_txt.html#video-options
    https://www.raspberrypi.com/documentation/computers/configuration.html#hdmi-configuration

    Does that affected the booted OS?

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)