Including the DRM drivers similar to what initramfs-tools does solves
the issue for the VM EFI test case. Can you test if the initrd generated
by the following call will solve it for you?
sudo dracut --force --add-drivers "=drivers/gpu/drm/tiny vboxvideo
virtio-gpu"
--
You received this bug noti
** Attachment added: "initrd-570.86.16-using-update-initramfs.txt"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5866458/+files/initrd-570.86.16-using-update-initramfs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 2103533 ***
https://bugs.launchpad.net/bugs/2103533
OK, Plymouth crashing is a Plymouth problem. I've updated bug 2103533 to
not suggest it only happens with Nvidia.
** Summary changed:
- go backtrace during boot, can't boot
+ backtrace during boot, can't b
Here is an instance where I got to the text-based passphrase prompt, and
it crashed right afterwards.
** Attachment added: "crash boot.mp4"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5867404/+files/crash%20boot.mp4
--
You received this bug notification because
You can try to boot with "rd.break", but I assume that the crash happens
after the switch root.
What do you think about removing the DRM drivers from the initrd? That
means: Removing "drm" from the list of module dependencies in depends()
in /usr/lib/dracut/modules.d/45plymouth/module-setup.sh
--
The actual last screen
** Attachment added: "crash boot.jpg"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5867410/+files/crash%20boot.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
> I don't see any golang
Oh, you maybe right, I just didn't think hard enough and assumed golang.
> There's a second problem there, that you're getting the text-based prompt
> rather than the graphical
> splashscreen
Not always, but sometimes.
--
You received this bug notification because
That's bug 2103533, upstream
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/288
I don't see any golang
** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #288
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/288
--
You received this bug notification bec
There's a second problem there, that you're getting the text-based
prompt rather than the graphical splashscreen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot
For better clarity, this is the final screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications about this bug go to:
https:/
Before getting this video and screenshot, I tried several boots, all
with different results. One worked just fine, graphical passphrase
prompt. The other immediately crashed before I got to see the prompt
even, and the last one didn't even reach the graphical phase, only
showing the text-based pass
Let me try a slow-motion video :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications about this bug go to:
https://bugs.launch
> Do we have any idea bout what is crashing, or how to find out?
No, you're the only person to have reported it and I can't see any
screenshots :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Do we have any idea bout what is crashing, or how to find out?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications about this b
Maybe a kernel-based solution? Although when I tried that it was blocked
by Red Hat:
https://lists.freedesktop.org/archives/dri-
devel/2024-February/442066.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
As Alessandro alluded to in comment #24, Plymouth using a "framebuffer"
(or rather 'fbdev') is probably what's happening. Such raw framebuffers
could be overwritten by other processes without the exclusive rights
over the display that a full DRM driver gives you.
The thing is, using fbdev ("frameb
Yes I made a mistake there. Somehow I forgot I had led the effort to
shrink the initrd:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
> 2. drivers/gpu/drm/tiny/* and i915 are apparently missing from initrd.
They should never be missing.
Why should i915 be in initrd? My current initrd (pre-dracut) doesn't
have i915 nor amdgpu or any large DRM drivers. That's what we have
SimpleDRM for, no?
--
You received this bug notification
I can see separate unrelated issues here:
1. Some daemon written in Go is crashing during boot.
2. drivers/gpu/drm/tiny/* and i915 are apparently missing from initrd.
They should never be missing.
3. Nondeterminism, which may just be the crash in #1 being
unpredictable.
The fact that the Go cra
And when I say that it worked, I mean that I got a graphical luks
passphrase prompt, and no crash. When I say it did not work, I mean I
got no prompt at all and just the golang backtrace, and boot halted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Any way we can take a look at this stacktrace?
Why is golang even involved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notification
I'm very confused.
I ran dracut --force. Rebooted. It worked.
I then removed all my initrd files from /boot, and ran just "dracut".
Rebooted. It DID NOT work.
I then just rebooted again. I got the grub menu, bu I DID NOT select the
safe mode. Used the first menu entry as always. IT WORKED.
This
In case no DRM driver is available then plymouth can also drive a
framebuffer directly. That is what I believe might be happening, just
from reading this thread.
It's possible that the framebuffer backend is not as well tested, and
does not work reliably. Because normally most systems would use th
@ahasenack your diff includes this in the list for the "broken" initrd:
usr/lib/modules/6.14.0-11-generic/kernel/drivers/gpu/drm/i915/i915.ko.zst
which is the DRM driver for your Intel GPU.
Was that present originally? Is that why @bdrung suggested `--omit-
drivers amdgpu` for his AMD system?
-
Sorry, there is more to it. I just rebooted with the supposedly "broken"
initrd, and it worked. Could it be a race of some sort inside the
initrd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Here is a diff between my working[1] and broken[2] initrd:
--- /dev/fd/63 2025-03-25 06:30:09.440174979 -0300
+++ /dev/fd/62 2025-03-25 06:30:09.441174986 -0300
@@ -107,33 +107,10 @@
usr/lib/modules/6.14.0-11-generic/kernel/drivers/gpu/drm/display
usr/lib/modules/6.14.0-11-generic/kernel/driv
Yes simpledrm is meant to be built-in, but adding "drivers/gpu/drm/tiny"
also includes bochs.ko and cirrus-qemu.ko which will matter for some
VMs.
I don't suppose anyone is using a kernel build where
CONFIG_DRM_SIMPLEDRM=m when it should be CONFIG_DRM_SIMPLEDRM=y ?
Or maybe --add-drivers is doing
SimpleDRM is built into the kernel binary rather than as a module, so
there should be no extra modules needed.
The fact that `dracut --force --add-drivers "=drivers/gpu/drm/tiny
vboxvideo virtio-gpu"` makes it work on real hardware like intel or amd
I find quite odd.
> Then I checked that I only
You are supposed to be able to use Plymouth with just SimpleDRM, without
any real DRM drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To m
This command that you suggested worked for my intel lenovo x1:
sudo dracut --force --add-drivers "=drivers/gpu/drm/tiny vboxvideo
virtio-gpu"
Boot worked, and I had a graphical prompt for the luks passphrase.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is the command for my AMD laptop:
sudo dracut --force --add-drivers "=drivers/gpu/drm/tiny vboxvideo
virtio-gpu" --omit-drivers amdgpu
Then I checked that I only have the added DRM drivers:
sudo 3cpio -t /boot/initrd.img | grep drm
--
You received this bug notification because you are a m
Great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drac
Benjamin, I already opened days ago:
https://bugs.launchpad.net/bugs/2103533
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notification
For just diffing the content you could use "3cpio -t" or "3cpio -tv".
Marcos, please open a new bug report for tracking the issue with the
NVIDIA driver using "ubuntu-bug dracut".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Attachment added: "initrd-570.124.04-just-using-update-initramfs.txt"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5866459/+files/initrd-570.124.04-just-using-update-initramfs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "initrd-570.124.04-using-host-only.txt"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5866460/+files/initrd-570.124.04-using-host-only.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Attachment added: "initrd-570.124.04-with-drm-tiny.txt"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5866461/+files/initrd-570.124.04-with-drm-tiny.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I posted four files that I got using `lsinitrd` command. In my case, maybe the
problem is different from the one the original author reported.
Just the version using NVIDIA driver 570.86.16 the Plymouth worked. The other
three were made using the driver version available on graphics-drivers PPA a
About my second question, I found out `lsinitrd` command, but I don't
think it's great for producing diffs...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, c
If I'm using NVIDIA drivers, what would be the option to add the
drivers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications a
** Patch added: "initrd-content.diff"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2103798/+attachment/5866385/+files/initrd-content.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103
And how can I list the content of my initrd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103798
Title:
go backtrace during boot, can't boot
To manage notifications about this bug go to:
https://
Building the initrd with "sudo dracut --force --no-hostonly" made it
show the boot splash. So it looks like that we are missing something in
the initrd in the default mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Workaround: Before typing wait a bit for the backtrace and the password
prompt to reappear.
My current investigation: A plucky VM with BIOS works fine but a plucky
VM with EFI is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
44 matches
Mail list logo
