** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1837209
Title:
Splash screen fails to display on recent pi core18 images
Status in snapd:
In
The bug is in progress but it is unclear who is working on it. Can the
party responsible please self-assign and update the status of the issue.
Is there something to be done in the snappy project for this issue to be fixed?
Is this just waiting on a kernel snaps? Are those in stable channel now?
** Changed in: snappy
Status: New => In Progress
** Changed in: linux-raspi2 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
@p-pisati: Dave just confirmed that our latest edge-based images now
have the Ubuntu splash logo back, thanks a lot! Could we get this
version promoted to stable anytime soon?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2
Ok, tested and uploaded, let me know if you test images are fixed now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1837209
Title:
Splash screen fails to display on recent pi
Fixed kernel snaps are building as we speak, and will be uploaded to the
store -edge and -beta immediately after.
I'll build another test image first thing tomorrow morning, and then we
can promote it to -stable.
--
You received this bug notification because you are a member of Kernel
Packages,
When would it be possible to get this change released as part of the pi-
kernel snap? I still need to poke Adam, but I suppose we wouldn't want
to release our .3 core images without this fix. Will we have to delay
the core image releases for .3, or maybe can these changes go into pi-
kernel
Thanks Paolo - I can confirm the pre-cooked image displays the boot logo
nicely (couldn't test the snap itself, but I suspect that's due to me
lacking the correction snap incantations rather than anything wrong with
it - snap complained about replacing a signed kernel with an unasserted
one).
--
** Tags added: id-5c5030ac2528bd3e8b135fc0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1837209
Title:
Splash screen fails to display on recent pi core18 images
Status in
Test kernel snap available here:
https://people.canonical.com/~ppisati/lp1837209/pi-
kernel_4.15.0-1041.44_armhf.snap
and precooked image here:
https://people.canonical.com/~ppisati/lp1837209/ubuntu-
core-18-pi_lp1837209fix.img.xz
--
You received this bug notification because you are a member
@p-pisati: as mentioned earlier, with pi-kernel rev 21 the splash
support worked with dtoverlay line present, which does not anymore -
meaning it's a regression. It's also quite a visible regression, since
that's the first thing Ubuntu Core pi users see when they boot the
device. This might be a
mir-kiosk is currently the only supported way to get grahical (mostly
kiosk) applications up and running on ubuntu core, some of our digital-
signage customers use it so currently the overlay is a requirement
(until the mir team solves it with a pi specific mir backend or the vc4
driver changes in
@p-pisati: that assumes the overlay isn't required by anyone; as ogra
notes above, the overlay is required for mir-kiosk to work. I don't know
how important mir-kiosk is, but it seems it might be fairly relevant to
core [1]. Either way, it seems less risky to me to add modules to initrd
(which
If you remove the dtoverlay line (just tested it) and it works fine
during boot (before root is mounted), it means initrd has all necessary
modules to make it work, so it's not like initrd is missing something.
--
You received this bug notification because you are a member of Kernel
Packages,
Indeed - I'd rather not remove overlays without being certain we don't
need them. For now though, let's just get the splash screen working
again (as it's a little un-nerving for new users to be presented with a
straight black screen during boot and have no indication anything's
working other than
Last working image / kernel version? First broken image / kernel
version? So we can compare the two.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1837209
Title:
Splash screen
the overlay is needed for mir-kiosk to allow it to work at all
(unaccelerated though)
to have mir-kiosk fully accelerated one needs to use -kms-v3d instead
but this in turn disables all video decoding in the vc4 core. i
originally picked -fkms-v3d for the gadget since it is the least evil
(makes
Tested Oliver's suggestion and indeed it does work if the overlay is
removed but I assume that the overlay is there for a reason.
Furthermore, extracting the psplash binary from the psplash initrd and
running it after boot has concluded (at which point /dev/fb0 exists)
works successfully which
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1837209
Title:
Splash screen fails to display on
19 matches
Mail list logo
