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

POE state does not persist across reboots #119

Open
thadrumr opened this issue Aug 1, 2024 · 2 comments
Open

POE state does not persist across reboots #119

thadrumr opened this issue Aug 1, 2024 · 2 comments

Comments

@thadrumr
Copy link

thadrumr commented Aug 1, 2024

As it stand POE settings on ports does not persist across reboots. I have tried to add a simple systemctl service but it doesn't seem to work on boot. I can call it with systemctl and it works. It would be nice if this could be saved and come back up in the same state across reboots.

@KanjiMonster
Copy link
Contributor

Hi,

Without knowing the details of your script my guess would be the service starts too early when the driver isn't loaded yet. Try delaying it, let it wait in a loop until the appropriate path appears (e.g. /sys/kernel/debug/serial0-0 for AS4610)

@thadrumr
Copy link
Author

thadrumr commented Aug 9, 2024

This is how my script is setup. This was at the suggestion of someone on the Slack channel. I have it waiting on the baseboxd.service. This worked a few versions back but stoped working. I have not changed the script or anything. It would be better if this would just persist without having to run a script.

[Unit]
Description=poectl
After=baseboxd.service

[Service]
Type=oneshot
ExecStart=/home/basebox/poe_setup_ports.sh
NotifyAccess=main

[Install]
WantedBy=multi.user.target

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