SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I know that this one has been discussed in various threads but I still cannot kill the PC speaker.
I am using Slackware 'Current' using a custom kernel with 'pcspkr' build as a module. UDEV (v116) is present so I should be able to prevent the 'pcspkr' module loading by putting an entry in the '/etc/modprobe.d/blacklist' file. I have also tried commenting the appropriate 'alias' line in '/etc/modprobe.d/isapnp' but still the module loads at boot.
I know I could rebuild the kernel again without the PC Speaker module, but I would like a solution which avoids this.
Yes, but see my opening message. It doesn't seem to work when I add the module to the 'blacklist'. Apparently this behaviour was noted by others with v111 of UDEV, but was supposed to be cured in version 116.
# grep -R pcspkr /etc/
/etc/rc.d/rc.modules: /sbin/modprobe pcspkr
/etc/rc.d/rc.local:modprobe -r pcspkr
/etc/rc.d/rc.modules-2.6.21.5-smp: /sbin/modprobe pcspkr
/etc/modprobe.d/isapnp:# alias pnp:dPNP0800 pcspkr
/etc/modprobe.d/blacklist:# also need to comment the pcspkr alias in /etc/modprobe.d/isapnp.
/etc/modprobe.d/blacklist:blacklist pcspkr
/etc/udev/rules.d/50-udev.rules:DRIVERS=="pcspkr", ENV{ID_CLASS}="spkr"
(No, usually I'm not logged in as root )
Apparently the pcspkr module gets loaded by rc.modules, so you'd need to comment it out there too.
Tell me if that helps; I've been trying to prevent pcspkr from loading too, and ended unloading it in rc.local (as you probably noticed ).
Putting the following code into '/etc/modprobe.d/blacklist' works:
Quote:
install pcspkr /bin/true
I still feel however that this line:
Quote:
DRIVERS=="pcspkr",ENV{ID_CLASS)="spkr"
in '/etc/udev/rules.d/60-persistent-input.rules' has something to do with it being loaded and difficult to blacklist. However, changing or creating udev rules are currently beyond my ability.
Have you tried editing /etc/inputrc ?
Uncomment the line:
set bell-style none
Worked for me.
No, I haven't tried that one, but I'm currently using 'install pcspkr /bin/true' added to the '/etc/modprobe.d/blacklist' file and this is working for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.