Re: new pccard beep code "not quite right"
[EMAIL PROTECTED] wrote: >> While I'm sure the new beeps for pccard insert/remove are quite charming >> on some laptops, they are a bit broken on mine... >> >> The new beeps are nothing more than a barely audible click or two... But >> the real problem is that if the speaker wants to beep afterwards, my ears >> are assaulted by not one but a nearly endless stream of beeps. They >> continue for different lengths depending on when they begin... They seem >> to stop when a card is identified though -- but it only requires another >> beep to set it off again, and they continue until a card is either ejected >> or another is identified (they don't stop if I break to ddb). >> >> Any debugging info needed will be happily provided! This is my fault. I fixed this problem in sys/pccard/pccard_beep.c rev.1.5. Please update your kernel. Cheers MIHIRA Yoshiro To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new pccard beep code "not quite right"
While I'm sure the new beeps for pccard insert/remove are quite charming on some laptops, they are a bit broken on mine... The new beeps are nothing more than a barely audible click or two... But the real problem is that if the speaker wants to beep afterwards, my ears are assaulted by not one but a nearly endless stream of beeps. They continue for different lengths depending on when they begin... They seem to stop when a card is identified though -- but it only requires another beep to set it off again, and they continue until a card is either ejected or another is identified (they don't stop if I break to ddb). Any debugging info needed will be happily provided! -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message