Skip to content

Conversation

@Githubguy132010
Copy link
Owner

Description

This pull request fixes issue #115 by removing the commands in no-beep.service that overwrite the comprehensive modprobe configuration file.

Changes Made

  • Removed the following lines from no-beep.service:
    ExecStart=/bin/bash -c "echo 'blacklist pcspkr' > /etc/modprobe.d/nobeep.conf"
    ExecStart=/bin/bash -c "echo 'blacklist snd_pcsp' >> /etc/modprobe.d/nobeep.conf"
    

Rationale

The existing /etc/modprobe.d/nobeep.conf file already contains a more complete configuration including:

  • Additional blacklisted beep modules (hpilo, ipmi_si, hpwdt, toshiba_acpi)
  • Options for PC speaker modules in case they get loaded anyway
  • Dummy module installation to prevent the real modules from loading

By removing these lines from the service file, we ensure that the comprehensive configuration remains intact during runtime, providing better beep-silencing functionality.

Testing

  • Verified that the service file syntax is valid
  • Confirmed that the comprehensive modprobe configuration remains in place

Fixes #115

@Githubguy132010 Githubguy132010 merged commit 5381cfd into main Apr 8, 2025
2 checks passed
@Githubguy132010 Githubguy132010 deleted the fix-issue-115-service-config branch April 8, 2025 16:56
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

Successfully merging this pull request may close these issues.

Fix systemd service configuration overwriting comprehensive modprobe config

2 participants