Hello!
Last week there must have been an update which killed my USB3/Thunderbolt port. How can I fix this or do I need to wait for another update?
Cheers,
Dejan
With ZERO information on anything regarding your system, you’re unlikely to receive any help.
At least post your system info: Run inxi -Fxxc0z | eos-sendlog in your terminal and post back the link provided.
1 Like
1 Like
There have been a kernel update that might help 
.
If not maybe try to find some info in the logs mentioned here
1 Like
journalctl -k -b -0 | eos-sendlog
Forgot to mention that the kernel update was from last friday and is now at 6.17.8 maybe it will help ?
I am updating my machine every single day. Unfortunately, it did not help yet. We will see, if an update will bring news.
If you’re running the main kernel, have you tried the LTS and visa versa? It’s not really a solution, but it may be a workaround until the main updates.
Thanks for the tip. I will try running the LTS.
But: How will I find out about the main kernel working again?
Keep an eye out for updates and try it again.
It may not be the kernel at all but if it is, that’s really all you can do.
This is a bit confusing I read this from your system specs
Kernel: 6.17.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
So if you update every day what happened to the 6.17.8 kernel ?
1 Like
Perhaps the version did not reach Germany that fast? I have tried pacman right now again and there was no new kernel available.
Maybe try eos-rankmirrors and try the update again , I think something is wrong here.
OK, ranked, rebooted, there it is. Still no USB3/Thunderbolt. 
What is the output of:
systemctl status bolt.service
You are using KDE Plasma. I am not sure if you need this package: plasma-thunderbolt
Also, open a terminal and have the following command running while trying to use your Thunderbolt port and see if you get something to hint at an error:
sudo dmesg -w
"authmode: enabled, force-power: unset"
Is the force-power: unset the reason why I don’t have power over USB-C? This was my measure right now…
I will test dmesg when I get to my eGPU at home.
I think that is because nothing is using that port so the thunderbolt controller is not forced to remain powered on by the operating system.
Also, when you plug in your eGPU, run the status command and check again.
eos-rankmirrors is not the right tool when trying to find mirrors for kernel updates.
But these are:
reflector or reflector-simple
rate-mirrors
rami
2 Likes
I have run in terminal: sudo dmesg -w y > textfile
The file is 100 kb, so I guess that I should make it available somewhere instead of posting it here.
I can’t upload it within this message. 
So, what would everyone suggest as upload destination?
EDIT:
How about this? https://filebin.net/ztnp70aiql9sjruv
After restarting my computer on Linux - months since I have tried it -, the eGPU is being recognized and charging seems to work. I will try a restart in Linux and report back.