** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Benjamin Drung (bdrung)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools i
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2078573
Title:
I can no longer boot from my Thunderbolt disk
Status in initramfs-too
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
Thanks for checking. I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded. So initramfs needs a hook to
include bolt.
--
You received this bug notification because you are a member of Ubuntu
It doesn't work with adding thunderbolt to /etc/initramfs-tools/modules
(and update-initramfs after the add).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2078573
Thanks for confirming it. You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.
I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
*
It works with thunderbolt.host_reset=0 in the kernel command line.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2078573
Title:
I can no longer boot from
Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:
- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset(
8 matches
Mail list logo
