[NCLUG] Beep, Beep, Beep - How do I make it beep properly?

John Gilmore jgilmore at glycou.com
Sun Oct 9 02:10:47 MDT 2005


OK, so nobody else cares - I'll reply to myself...

I'm thinking that this may be a hardware problem...

I commented out the section of code in the 'pcspkr' kernel module that 
actually did the fiddleing around with the ports, and it changed the 
behavior.

Previously, it would beep only if the pcspkr module was loaded. Afterwards, it 
wouldn't beep at all, even with the modified pcspkr module loaded. So 
obviously the fiddling around with the ports IS what's producing the beep 
that I hear, and not some software layer redirecting a kernel event.

I had thought that some other driver was deliberately intercepting events of 
type EV_SND SND_BELL and processing them only if something else was 
registered to handle them -- kinda a "if you want beeps, we'll give you 
beeps, but we'll still allow you to not have any" but that theory is shot.

I'd like to check the object code and see if the outb_p calls are translated 
into assembler or calls to something else. It's possible, if they are 
translated into calls to something else, that that something else is doing 
something I don't want it to with them - though I can't imagine why that 
would be...   

Does anybody know the enough about gdb to make it disassemble object code? Or 
perhaps know enough about the kernels outb_p call to know what it is or does?

It also seems kinda stupid to reroute the pcspeaker to the sound card in 
hardware. Why on earth would anyboddy do something like that? And if they 
did, then why bother to include a speaker at all?

I think I've pursued this as far as I can without knowing the exact make and 
model of my Motherboard.

But if I could fix this by scratching out a couple of traces on the MB, I 
would.


On Friday 07 October 2005 16:34, John Gilmore wrote:
> Blah, Blah, Blah, Blah Blah....



More information about the NCLUG mailing list