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?
Not connected at boot and doesn't show something when I connect it.
schrieb Theo:
Is it perhaps displaying on the second HDMI port?
Not connected at boot and doesn't show something when I connect it.
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?
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 ...
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?
Is there a workaround?
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>
Andy Burns wrote:
<https://amazon.co.uk/DPsource-to-HDMIsink/dp/B09CYYF5NN?th=1>
That's the wrong way round,
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?
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.
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.
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?
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".
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
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 14 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 231:05:05 |
| Calls: | 55 |
| Calls today: | 1 |
| Files: | 50,127 |
| D/L today: |
29 files (3,538K bytes) |
| Messages: | 275,355 |