Public bug reported: I'm facing an issue with Thunderbolt in initrd on a Lenovo Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11.
Cross-checking the same dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: When starting the Laptop USB generic drivers are loaded and the Dock is recognized. The dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: thunderbolt 1-0:1.1: new retimer found, vendor ... thunderbolt 1-1: new device found, vendor ... thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock As soon as the Thunderbolt module is loaded the devices connected to the dock shut off: Monitors turn blank, Keyboard backlights and Mouse status indicator LEDs turn off. I assume the power supply to the laptop does still work, but do not know for sure. This causes that only Monitors or Keyboards connected to the Laptop directly via USB or HDMI will work for entering the passphrase, as well as the internal Monitor and Keyboard (-> which are connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The dock works flawlessly in UEFI, GRUB as well as the plymouth/LUKS environment as it is now acting as USB3.2 device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: As soon as the LUKS passphrase is entered correct and the system loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the initrd/LUKS passphrase/plymouth stage, but I found no documentation if there is such and how to change that policy. I also did not find any workaround to drop Thunderbolt for initrd and set USB generic drivers only. Here is some similar report that the issue exists since Kernel 5.4, but they did not have the same conclusion/mentioning of USB-generic drivers vs. Thunderbolt drivers: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215 Thanks for your help ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Affects: initrd-tools (Ubuntu) Importance: Undecided Status: New ** Affects: thunderbolt-tools (Ubuntu) Importance: Undecided Status: New ** Tags: cryptsetup initramfs initrd luks thunderbolt ** Package changed: network-manager (Ubuntu) => initrd-tools (Ubuntu) ** Also affects: thunderbolt-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm facing an issue with Thunderbolt in initrd on a Lenovo Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11. Cross-checking the same dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: When starting the Laptop USB generic drivers are loaded and the Dock is recognized. The dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. - As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase window, I recognized the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: + As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: - thunderbolt 1-0:1.1: new retimer found, vendor ... + thunderbolt 1-0:1.1: new retimer found, vendor ... - thunderbolt 1-1: new device found, vendor ... + thunderbolt 1-1: new device found, vendor ... - thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock + thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock As soon as the Thunderbolt module is loaded the devices on the dock shut off: Monitors turn blank, Keyboard backlights and Mouse status indicator LEDs turn off. I assume the power supply to the laptop does still work, but do not know for sure. This causes that only Monitors or Keyboards connected to the Laptop directly via USB or HDMI will work for entering the passphrase, as well as the internal Monitor and Keyboard (-> which are connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The dock works flawlessly in UEFI, GRUB as well as the plymouth/LUKS environment as it is now acting as USB3.2 device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: As soon as the LUKS passphrase is entered correct and the system kernel loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the plymouth stage, but I found no documentation if there is such and how to change that policy. I also did not find any workaround to drop Thunderbolt for plymouth and set USB generic drivers only. - Thanks for your help ** Description changed: I'm facing an issue with Thunderbolt in initrd on a Lenovo Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11. Cross-checking the same dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: When starting the Laptop USB generic drivers are loaded and the Dock is recognized. The dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: thunderbolt 1-0:1.1: new retimer found, vendor ... thunderbolt 1-1: new device found, vendor ... thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock - As soon as the Thunderbolt module is loaded the devices on the dock shut - off: Monitors turn blank, Keyboard backlights and Mouse status indicator - LEDs turn off. I assume the power supply to the laptop does still work, - but do not know for sure. + As soon as the Thunderbolt module is loaded the devices connected to the + dock shut off: Monitors turn blank, Keyboard backlights and Mouse status + indicator LEDs turn off. I assume the power supply to the laptop does + still work, but do not know for sure. This causes that only Monitors or Keyboards connected to the Laptop directly via USB or HDMI will work for entering the passphrase, as well as the internal Monitor and Keyboard (-> which are connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The dock works flawlessly in UEFI, GRUB as well as the plymouth/LUKS environment as it is now acting as USB3.2 device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: As soon as the LUKS passphrase is entered correct and the system kernel loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the plymouth stage, but I found no documentation if there is such and how to change that policy. I also did not find any workaround to drop Thunderbolt for plymouth and set USB generic drivers only. Thanks for your help ** Description changed: I'm facing an issue with Thunderbolt in initrd on a Lenovo Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11. Cross-checking the same dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: When starting the Laptop USB generic drivers are loaded and the Dock is recognized. The dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: thunderbolt 1-0:1.1: new retimer found, vendor ... thunderbolt 1-1: new device found, vendor ... thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock As soon as the Thunderbolt module is loaded the devices connected to the dock shut off: Monitors turn blank, Keyboard backlights and Mouse status indicator LEDs turn off. I assume the power supply to the laptop does still work, but do not know for sure. This causes that only Monitors or Keyboards connected to the Laptop directly via USB or HDMI will work for entering the passphrase, as well as the internal Monitor and Keyboard (-> which are connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The dock works flawlessly in UEFI, GRUB as well as the plymouth/LUKS environment as it is now acting as USB3.2 device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: - As soon as the LUKS passphrase is entered correct and the system kernel loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. - That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the plymouth stage, but I found no documentation if there is such and how to change that policy. + As soon as the LUKS passphrase is entered correct and the system loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. + That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the initrd/LUKS passphrase/plymouth stage, but I found no documentation if there is such and how to change that policy. - I also did not find any workaround to drop Thunderbolt for plymouth and + I also did not find any workaround to drop Thunderbolt for initrd and set USB generic drivers only. Thanks for your help ** Summary changed: - Issues with Thunderbolt in Plymouth: Devices blocked + Issues with Thunderbolt in initrd: Devices recgonzied but "blocked" ** Summary changed: - Issues with Thunderbolt in initrd: Devices recgonzied but "blocked" + Issues with Thunderbolt in initrd: Devices recognized but not working ** Description changed: I'm facing an issue with Thunderbolt in initrd on a Lenovo Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11. Cross-checking the same dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: When starting the Laptop USB generic drivers are loaded and the Dock is recognized. The dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: thunderbolt 1-0:1.1: new retimer found, vendor ... thunderbolt 1-1: new device found, vendor ... thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock As soon as the Thunderbolt module is loaded the devices connected to the dock shut off: Monitors turn blank, Keyboard backlights and Mouse status indicator LEDs turn off. I assume the power supply to the laptop does still work, but do not know for sure. This causes that only Monitors or Keyboards connected to the Laptop directly via USB or HDMI will work for entering the passphrase, as well as the internal Monitor and Keyboard (-> which are connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The dock works flawlessly in UEFI, GRUB as well as the plymouth/LUKS environment as it is now acting as USB3.2 device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: As soon as the LUKS passphrase is entered correct and the system loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the initrd/LUKS passphrase/plymouth stage, but I found no documentation if there is such and how to change that policy. I also did not find any workaround to drop Thunderbolt for initrd and set USB generic drivers only. + Here is some similar report that the issue exists since Kernel 5.4, but they did not have the same conclusion/mentioning of USB-generic drivers vs. Thunderbolt drivers: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215 + Thanks for your help -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/2097229 Title: Issues with Thunderbolt in initrd: Devices recognized but not working Status in cryptsetup package in Ubuntu: New Status in initrd-tools package in Ubuntu: New Status in thunderbolt-tools package in Ubuntu: New Bug description: I'm facing an issue with Thunderbolt in initrd on a Lenovo Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11. Cross-checking the same dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: When starting the Laptop USB generic drivers are loaded and the Dock is recognized. The dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. As soon as GRUB is attempting to start the selected system and initrd is loaded to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts: thunderbolt 1-0:1.1: new retimer found, vendor ... thunderbolt 1-1: new device found, vendor ... thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock As soon as the Thunderbolt module is loaded the devices connected to the dock shut off: Monitors turn blank, Keyboard backlights and Mouse status indicator LEDs turn off. I assume the power supply to the laptop does still work, but do not know for sure. This causes that only Monitors or Keyboards connected to the Laptop directly via USB or HDMI will work for entering the passphrase, as well as the internal Monitor and Keyboard (-> which are connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The dock works flawlessly in UEFI, GRUB as well as the plymouth/LUKS environment as it is now acting as USB3.2 device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: As soon as the LUKS passphrase is entered correct and the system loads, Thunderbolt modules are loaded fresh again and from that moment on work properly. That is why I was hoping for the best case of security policies blocking Thunderbolt inputs in the initrd/LUKS passphrase/plymouth stage, but I found no documentation if there is such and how to change that policy. I also did not find any workaround to drop Thunderbolt for initrd and set USB generic drivers only. Here is some similar report that the issue exists since Kernel 5.4, but they did not have the same conclusion/mentioning of USB-generic drivers vs. Thunderbolt drivers: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215 Thanks for your help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2097229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
