Thunderbolt does not appear to work with Gentoo

[simplycorbett]

I'm using ~amd64 keyworded gentoo-kernel-bin with Stable KDE. DMESG can correctly see the thunderbolt drives.

However, they don't seem to work.

For example, if I plug in a NVME drive its seen in dmesg/kernel, but not shown in fdisk -l.

On Fedora, everything works. In addition, Fedora asks me on KDE if I want to authorize the thunderbolt device. This does not happen on Gentoo/KDE.

I have the thunderbolt use flag enabled, as well.

My thunderbolt monitor (sometimes) works. It's hit or miss on Gentoo. Works perfectly on Fedora every time.

In system settings on KDE, under thunderbolt, it says the subsystem is not running on Gentoo. However, it works on Fedora.

I'd really prefer to stick with Gentoo. Is there some way to fix this?

[alamahant]

Install and enable plz

Code: Select all

sys-apps/bolt

[simplycorbett]

Thanks, but the same issue - KDE continues to say the thunderbolt subsystem is disabled, and none of my thunderbolt devices are accessible/working.

[simplycorbett]

After looking at the ebuild, it looks like the package only works with openrc? I am on systemd.

But google says it should also work with systemd.

The service boltd does not exist.

[alamahant]

I see

Code: Select all

cat /usr/lib/udev/rules.d/90-bolt.rules 
# bolt udev rules
#
# SPDX-License-Identifier: GPL-2.0-or-later
#
# Copyright © 2017 Red Hat, Inc
#
# Authors:
#       Christian J. Kellner <ckellner@redhat.com>
#

ACTION=="remove", GOTO="bolt_end"

# start bolt service if we have a thunderbolt device connected
SUBSYSTEM=="thunderbolt", TAG+="systemd", ENV{SYSTEMD_WANTS}+="bolt.service"

LABEL="bolt_end"

and

Code: Select all

cat /etc/init.d/boltd 
#!/sbin/openrc-run
# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2

name="Thunderbolt Security Daemon"
description="Userspace system daemon to enable security levels for Thunderbolt 3"
command="/usr/libexec/boltd"
command_background="true"
pidfile="/var/run/boltd.pid"

depend() {
	need dbus
	before display-manager
}

Please check if bolt.service exists and enable/start it.
If not just invoke /usr/libexec/boltd.
Also try :

Code: Select all

boltctl list
boltctl enroll <device uuid>

[simplycorbett]

Code: Select all

boltctl list
boltctl: error: could not create client: Error calling StartServiceByName for org.freedesktop.bolt: Unit bolt.service not found.

Manually running /usr/libexec/boltd does work!

However, thunderbolt monitor still has no display signal.

But yes, nvme drives and everything else works now!

[alamahant]

Try this?

Code: Select all

[Unit]
Description=Thunderbolt Security Daemon
After=network.target dbus.service
Wants=dbus.service
Before=display-manager.service

[Service]
Type=simple
ExecStart=/usr/libexec/boltd
PIDFile=/var/run/boltd.pid

[Install]
WantedBy=multi-user.target

Maybe name it /etc/systemd/sytem/bolt.service
and enable it.
Dont forget to do a

Code: Select all

systemctl daemon-reload

As for the monitor try dis/reconnecting it.I hope the before=display-manager will get this sorted.
Also, by the way , do you have this installed?

Code: Select all

eix thunderbolt
* kde-plasma/plasma-thunderbolt
     Available versions:  (6) 6.4.5^t ~6.5.3^t
       {debug test}
     Homepage:            https://invent.kde.org/plasma/plasma-thunderbolt
     Description:         Plasma integration for controlling Thunderbolt devices

?

[simplycorbett]

I will try adding it to the service and getting back to you in a couple hours.

Yes, I have that package installed. As long as I am running boltd manually as a root user (using screen) thunderbolt works on KDE's thunderbolt menu and I can authorize devices.

The monitor does not work, however. Even with reconnecting. The sound works on it, but no display signal.

Since it works on Fedora, I think this may be a Nvidia driver issue with Gentoo. I have no idea how to troubleshoot such a problem, though.

[simplycorbett]

Figured I'd update!

With bolt running as a systemd service the monitor does work! The laptop has to be booted with the monitor plugged in already and then it just works.

If the monitor is plugged in after it's booted into a desktop environment, it doesn't work.

Thank you so much for all the help!