RE: No "Beep" from PC Speaker

2005-05-24 Thread Eric van der Paardt


-Original Message-
> called "twinke-beeps," (GPL, all rights reserved) which proves that
Sarge is
> still a contender in state-of-the-art multimedia:
> 
> beep -f 1000 -n -f 1000  -n -f 1500  -n -f 1500 -n -f 1700 -n -f 1700
-n -r 
> 2 -f 1500 -n -f 1350 -n -f 1350 -n -f 1300 -n -f 1300 -n -f 1150 -n -f
1150 
> -n -f 1000

I don't know anything about beep, but that looks a little out of 
tune to me ;)

Try the frequencies 
1000/1000/1498/1498/1682/1682/1498
1335/1335/1260/1260/1122/1122/1000

Now that's the true spirit of GPL!



Re: No "Beep" from PC Speaker

2005-05-23 Thread David Jardine
On Mon, May 23, 2005 at 01:55:09PM -0400, Marty wrote:

[...]

> After solving my own beep problems I wrote the following command
> called "twinke-beeps," (GPL, all rights reserved) which proves that Sarge is
> still a contender in state-of-the-art multimedia:
> 
> beep -f 1000 -n -f 1000  -n -f 1500  -n -f 1500 -n -f 1700 -n -f 1700 -n -r 
> 2 -f 1500 -n -f 1350 -n -f 1350 -n -f 1300 -n -f 1300 -n -f 1150 -n -f 1150 
> -n -f 1000

I don't know anything about beep, but that looks a little out of 
tune to me ;)

Try the frequencies 
1000/1000/1498/1498/1682/1682/1498
1335/1335/1260/1260/1122/1122/1000

-- 
David Jardine

"Running Debian GNU/Linux and
loving every minute of it."  -L. von Sacher-M.(1835-1895)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No "Beep" from PC Speaker

2005-05-23 Thread Marty

Kenneth Jacker wrote:

  martyb> Did you try to "beep" as root?

I grabbed the 'beep' package, installed it, and it worked!

So, I can now add the invocation of /usr/bin/beep to the 'xalarm' cmmd line.

I still wonder why "$ echo ^G" doesn't work in "terminal" windows ... 
something missing in /etc/terminfo/*?



Thanks, Marty, since you basically solved my problem!

  -Kenneth




No problem. After solving my own beep problems I wrote the following command
called "twinke-beeps," (GPL, all rights reserved) which proves that Sarge is
still a contender in state-of-the-art multimedia:

beep -f 1000 -n -f 1000  -n -f 1500  -n -f 1500 -n -f 1700 -n -f 1700 -n -r 2 
-f 1500 -n -f 1350 -n -f 1350 -n -f 1300 -n -f 1300 -n -f 1150 -n -f 1150 -n -f 
1000


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: No "Beep" from PC Speaker

2005-05-23 Thread Marty

Colin wrote:

Marty wrote:


Did you try to "beep" as root?  (I use the program /usr/bin/beep for
this test.  The reason I ask is because I think once I had to be root to
run "beep."  I forget what the problem was, probably a permissions issue.)


Man!  Now that's being a bit paranoid!  You need to be root to make a beep?




From /var/lib/dpkg/info/beep.templates:

Template: beep/suid_option
Type: select
Choices: suid root for all, suid root with only group audio executable, not 
suid at all
[...]

Default: suid root with only group audio executable
Description: How to handle suid root for beep program?
 beep must be run as root since it needs to access the speaker hardware.
 There are several posibilities to make the program usable:  Either only
 for root (no suid bit at all), executable only by users of the group
 audio, or usable for all.
 .
 Because each program that is suid root is security risk this is not done
 by default.  However, the program is quite small (~150 lines of code) and
 is fairly easy to verify the safety of the code yourself, if you don't
 trust my judgement.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: No "Beep" from PC Speaker

2005-05-23 Thread Colin
Marty wrote:

> Did you try to "beep" as root?  (I use the program /usr/bin/beep for
> this test.  The reason I ask is because I think once I had to be root to
> run "beep."  I forget what the problem was, probably a permissions issue.)

Man!  Now that's being a bit paranoid!  You need to be root to make a beep?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No "Beep" from PC Speaker

2005-05-23 Thread Kenneth Jacker
  martyb> Did you try to "beep" as root?

I grabbed the 'beep' package, installed it, and it worked!

So, I can now add the invocation of /usr/bin/beep to the 'xalarm' cmmd line.

I still wonder why "$ echo ^G" doesn't work in "terminal" windows ... 
something missing in /etc/terminfo/*?


Thanks, Marty, since you basically solved my problem!

  -Kenneth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No "Beep" from PC Speaker

2005-05-22 Thread Marty

Kenneth Jacker wrote:

  martyb> Possibly because PC Speaker support (INPUT_PCSPKR) is not
  martyb> enabled in your kernel or the corresponding module is not
  martyb> loaded.

Thanks for the suggestion!

I installed the 'pcspkr' module using 'modconf', but still hear nothing.

Other ideas?

Thanks,

  -Kenneth



Did you try to "beep" as root?  (I use the program /usr/bin/beep for
this test.  The reason I ask is because I think once I had to be root to
run "beep."  I forget what the problem was, probably a permissions issue.)

Failing that, the next question is "is your speaker connected?"  If it
is you should hear one or more beeps from the BIOS, while booting.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: No "Beep" from PC Speaker

2005-05-22 Thread Kenneth Jacker
  martyb> Possibly because PC Speaker support (INPUT_PCSPKR) is not
  martyb> enabled in your kernel or the corresponding module is not
  martyb> loaded.

Thanks for the suggestion!

I installed the 'pcspkr' module using 'modconf', but still hear nothing.

Other ideas?

Thanks,

  -Kenneth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: No "Beep" from PC Speaker

2005-05-22 Thread Gerhard Gaussling
Am Sonntag 22 Mai 2005 19:49 schrieb Marty:
>  (Why the kernel
> configuration routines consider the PC speaker an "input device" is a
> separate mystery, unless it contributed to your not finding this
> option and consequently not running this driver.)
Good question. It took me also some times to figure that out.

regards

Gerhard



Re: No "Beep" from PC Speaker

2005-05-22 Thread Marty

Kenneth Jacker wrote:

[sarge; 2.6.8-2-686; KDE; SBL!]

I can't get my PC speaker to "beep" in a "console" or "Konsole"
session ... I guess there are worse problems!  ;-)

Anyway, this,

$ echo -v-g

produces no sound.  Neither does 'xalarm' with the "-alarmaudio beep" option.

I've enabled it via 'alsamixer', checked 'xset' and various KDE "sound
options", but still hear nothing.

Most likely I've turned it off somewhere else, but just don't know where ...

Anyone have any ideas?

Thanks,



Possibly because PC Speaker support (INPUT_PCSPKR) is not enabled in
your kernel or the corresponding module is not loaded.  (Why the kernel
configuration routines consider the PC speaker an "input device" is a
separate mystery, unless it contributed to your not finding this option
and consequently not running this driver.)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




No "Beep" from PC Speaker

2005-05-22 Thread Kenneth Jacker
[sarge; 2.6.8-2-686; KDE; SBL!]

I can't get my PC speaker to "beep" in a "console" or "Konsole"
session ... I guess there are worse problems!  ;-)

Anyway, this,

$ echo -v-g

produces no sound.  Neither does 'xalarm' with the "-alarmaudio beep" option.

I've enabled it via 'alsamixer', checked 'xset' and various KDE "sound
options", but still hear nothing.

Most likely I've turned it off somewhere else, but just don't know where ...

Anyone have any ideas?

Thanks,

-- 
Prof Kenneth H Jacker   [EMAIL PROTECTED]
Computer Science Dept   www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]