Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x11-drivers/displaylink-driver-6.0.0 is systemd only #9

Open
Arniiiii opened this issue Jul 13, 2024 · 4 comments
Open

x11-drivers/displaylink-driver-6.0.0 is systemd only #9

Arniiiii opened this issue Jul 13, 2024 · 4 comments

Comments

@Arniiiii
Copy link

I have openrc, and the https://wiki.archlinux.org/title/DisplayLink mentions the service.

The service is seems to be installed for me at /usr/lib/systemd/system-sleep/displaylink.sh

@SuperTux88
Copy link
Owner

I have all my systems with systemd, and I have no way to test anything with openrc. So all the ebuilds in this overlay come without official openrc support. If it's easy to support, I try to add openrc (but can't test it), so some ebuilds have openrc support, but there are no guarantees for openrc. And this ebuild was already a mess to create just for systemd alone.

The arch wiki also only mentions systemd, and I don't even know if the upstream installer-script even supports openrc. The service itself is in /opt/displaylink/DisplayLinkManager (see /usr/lib/systemd/system/displaylink-driver.service). The script in /usr/lib/systemd/system-sleep/displaylink.sh is to suspend the DisplayLinkManager when you suspend your system and resume it again after that. But I have no idea how to do all that with openrc.

So I won't be able to add openrc support to this ebuild myself. But if you want to create a Pull-request, I'll merge it and try to keep it intact for future updates (however without guarantees, as I can't test it).

@Arniiiii
Copy link
Author

/usr/lib/systemd/system/displaylink-driver.service doesn't exist for me. Can you send here the file here, please?

Honestly, I don't how to write openrc scripts, but there's a doc about how to write them, so the systemd-specific script maybe can be rewritten in a spare time

@Arniiiii
Copy link
Author

Arniiiii commented Jul 14, 2024

I'm just trying to make an USB - HDMI adapter to work

@SuperTux88
Copy link
Owner

The displaylink-driver.service looks like this:

[Unit]
Description=DisplayLink Driver Service
After=display-manager.service
Conflicts[email protected]

[Service]
ExecStartPre=/sbin/modprobe evdi
ExecStart=/opt/displaylink/DisplayLinkManager
Restart=always
WorkingDirectory=/opt/displaylink
RestartSec=5

As said, I won't add openrc support to this ebuild myself, but if you want to, you can provide a PR. But you can probably also just create the files required for openrc on your PC without the ebuild, so that's maybe easier?

There is a reason why I use systemd on all my systems, because most things already provide systemd support, and for the things that don't it's very easy to write your own systemd unit files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants