debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <2107477@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package initramfs-tools - 0.147ubuntu1.1

---------------
initramfs-tools (0.147ubuntu1.1) plucky; urgency=medium

  * Fix missing panel modules in initramfs (LP: #2107477)
    - Fix include pattern for panel drivers if MODULES=dep
    - Include all bridge, panel and backlight drivers if MODULES=most

 -- Tobias Heider <tobias.heider@xxxxxxxxxxxxx>  Wed, 25 Jun 2025
14:50:25 +0200

** Changed in: initramfs-tools (Ubuntu Plucky)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to dracut in Ubuntu.
https://bugs.launchpad.net/bugs/2107477

Title:
  [SRU] Display broken in initramfs on ARM64 laptops

Status in dracut package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in dracut source package in Plucky:
  New
Status in initramfs-tools source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

  On affected hardware, the display only works after the initramfs.
  This means there is no visible input field if disk encryption was selected in the installer.
  The same of course applies for any other output during the initramfs.

  [ Test Plan ]

  To reproduce the issue, install an affected machine with disk encryption or add break= to the kernel command line to get an interactive initramfs shell.
  With the bug present the screen stays dark. It might still be possible to enter
  the passphrase blindly or exit the debug shell. After modules are loaded from the root file system the screen should start working.

  With the patch applied there should be visible output for the password
  or shell prompt in the initramfs.

  [ Where problems could occur ]

  The fix should only include additional modules, we should make sure
  not to accidentally drop any functionality in the process.

  [ Other Info ]

  Since dracut and initramfs-tools behave similar enough the same test
  plan should apply to both. Both are already fixed in questing and
  there is positive test feedback from users in discourse
  https://discourse.ubuntu.com/t/faq-ubuntu-25-04-on-snapdragon-x-
  elite/61016/18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2107477/+subscriptions