Ok if I close this bug, given that it seems to be problematic HW?
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064370
Titl
vc4.force_hotplug=0x01 helped also in my case
btw, I tried also portable LCD monitor Wimaxit (cannot find anything specific
about model) and it has the same issue when force hotplug is not used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064370
Title:
fwiw I hit this too on Rpi4. I did not use noble before so I cannot
compare like Andre, it worked fine with jammy and focal. My monitor is
Asus PB278Q. I will test the hotplug and see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Well, I cannot explain why but my problematic monitor decided to work well even
without forcing hotplug, so now I cannot test the new kernels because I can't
see the problem anymore.
I'll revisit this if it starts misbehaving again.
--
You received this bug notification because you are a membe
@Dave so I tested this in 4 other monitors and they all worked as
expected without the need for forcing hotplug.
@Juerg you could say it's a regression because it worked on that
specific monitor and now it does not work anymore, but it is now
understood what happend and the reason for that (there
> So that means that with different monitors I could potentially not
need this vc4.force_hotplug option, right?
That is certainly my suspicion; it doesn't much surprise me that an LCD
controller isn't *quite* obeying the HDMI spec (or perhaps that it
expects to be part of something else which hand
** Tags added: kern-10811
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064370
Title:
Blank screen after boot in raspberry pi 4
To manage notifications about this bug go to:
https://bugs.launchpad
Thank you for the explanation.
So that means that with different monitors I could potentially not need
this vc4.force_hotplug option, right? I will (as time permits) try
plugging this device in all my other monitors to compare, let's see how
it goes (this monitor specifically is a laptop LCD using
> If I switch to the KMS overlay, the message is exactly the same, so it
means the EDID is accessible from the monitor in either case.
Not quite the case I'm afraid. The output you're quoting there is from
the pi's bootloader running on the GPU. So, what you've established
there is that the GPU (w
Ok, adding vc4.force_hotplug=0x01 to the kernel command line _does_ fix
the issue, the screen flickers for a second but comes back with normal
image and stays on.
Also, now I seem to be able to decode edid many times in a row without
it disappearing (appearing empty).
I'm not running the test of
This is the complete boot log, just in case something in it is useful
(taken from the serial console including the firmware initialization
part):
https://pastebin.canonical.com/p/2HMBbBdcFp/
This is the config file used in that boot (which btw is the stock file
from image, unchanged):
https://pa
Found one more bug report that may be related:
https://github.com/raspberrypi/linux/issues/5195
** Bug watch added: github.com/raspberrypi/linux/issues #5195
https://github.com/raspberrypi/linux/issues/5195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok, running some tests.
First thing is that with fKMS overlay, right on boot (even before the
kernel started) I can see these messages on the serial console:
RPi: BOOTLOADER release VERSION:0b7b6f28 DATE: 2024/04/17 TIME: 13:51:36
BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1713358296 ser
You are correct it was introduced for noble as, without the KMS driver,
there's no audio output over HDMI on the server image under the Pi 5
(LP: #2038924). KMS is also the only supported stack on the Pi 5
upstream, and rather than trying to support different stacks on
different models I opted to m
** Package changed: software-properties (Ubuntu) => linux-raspi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064370
Title:
Blank screen after boot in raspberry pi 4
To manage notificatio
I just found a usb flash key with my last installation (from a daily
image) from a few days ago, and it does not have a line for that
dtoverlay at all (neither fkms nor kms).
This line seems to have appeared on the official release.
--
You received this bug notification because you are a member
17 matches
Mail list logo
