Solo10G SFP+ (Thunderbolt 3 Edition): does not wake up, need to plug/unplug #37
Comments
|
I installed the latest driver from git and the problem remains. The thunderbolt network card is not detected, as shows ifconfig -a: Here is the dmesg: |
|
sudo insmod -f /lib/modules/5.16.0-6-amd64/aquantia/atlantic.ko |
|
Ok, I understand what is going on: as the system is protected with UEFI I cannot insert a module unless it is signed.
Any idea how to activate the network controller? |
|
ffries, you are listing your thunderbolt devices, not AQC PCI device. |
|
Thanks. Here us the output of lspci, no trace of AQC here. |
|
After unpluging/repluging, the Aquantia PCI device is visible: |
|
I modified my Thunderbolt setting. Now devices are not attached in pre-boot and only enabled with secure connection. The network card is seen by bolt utility but it is not listed in the PCI list. Now I only need to unplug/replug it once to make it available. Windoze (which I never use) does not have this issue. Any idea how to solve this? |
|
Is there a fix to this issue? I'm also seeing it with Ubuntu 22.04 LTS and the Sabrent th-s3ea adapter. After a long period of being online or after a reboot I need to unplug and replug in the adapter to get ip connectivity. |
|
The issue is still present besides BIOS firmware updates. Then the SPF+ led lights up and network connection is established. |
|
Unfortunately this issue is still present in latest Debian Bookworm. I suspect an hibernation problem: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear all,
First of all, thanks for the hard work.
My Solo10G SFP+ is connected to a Lenovo Thinkpad Thunderbolt 3 dock
When starting-up my GNU/Linux station, the Solo10G SFP+ is not detected.
I need to plug/unplug the Solo10G thunderbolt cable a number of times to force detection.
All hardware have the latest firmwares available.
Thunderbolt is configured in secure mode and all hardware is enables: dock and Solo10G SFP+.
Detection works under Windoze without problem (I am not a Win user).
Is there a workaround as on the long run it may hinder the thunderbolt cable?
The best would be a command that would force detection and/or waking-up.
I am using Debian testing stock kernel, please let me know if I need to reinstall your kernel module.
The reason is that I am booting in secure mode and I wonder whether installing a custom module is possible.
My kernel is:
Linux x280 5.16.0-6-amd64 #1 SMP PREEMPT Debian 5.16.18-1 (2022-03-29) x86_64 GNU/Linux
Kind regards,
Kellogs
The text was updated successfully, but these errors were encountered: