1
I was just playing around with the bios beep and therefore I had to load the module pcspkr. But the beep would only work when I rebooted the system. The module is definitely loaded, but the speaker driver is not working until rebooting the system.
Here is what I did:
$ modprobe pcspkr
$ lsmod | grep pcspkr
pcspkr 12702 0
What is the reason for this behaviour?
regards
Update: Even suspending to RAM makes the bios beep work.
Quick n Dirty
Posted 2013-07-17T15:33:26.640
Reputation: 203
I guess that
pcspkrdepends on some other modules that were not loaded. – terdon – 2013-07-17T15:36:41.060I'd rather say, one or more other modules must be unloaded before the speaker beeps. Can you bring your system to the state where it doesn't beep and then provide the complete output of
lsmod? – ott-- – 2013-07-17T17:35:28.023@terdon:
modprobealways inserts dependent modules first. – user1686 – 2013-07-17T18:20:27.480@grawity yes, but I was imagining some strange situations with blacklisted modules. Not at all sure it is possible but if the blacklist has been read and a module banned and then one that requires the banned one is loaded, will the blacklisting be ignored? – terdon – 2013-07-17T18:26:20.103
no, i dont think so; btw: originally the pcspkr module was blacklisted on my system, but i removed it from the blacklist – Quick n Dirty – 2013-07-18T08:10:03.820