Bug#463435: Partially solved

2008-01-31 Thread Eugen Dedu 

Hi,

I reply to myself...  After looking in the code of pommed, I saw that it 
looked for uinput module.  After modprobe uinput, the beep works.


Two clarifications remain:

- Would it be possible to automatically load the uinput module?  I think 
to all the people who have the same problem.


- Can you write (in 10 minutes) a file about how beep works (in linux?)? 
 It seems that the card does no beep, it should be simulated in 
software, and uinput module is needed (are there other input modules?)


Thank you,
--
Eugen Dedu



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

Bug#463435: Partially solved

2008-01-31 Thread Julien BLACHE 
Eugen Dedu [EMAIL PROTECTED] wrote:

Hi,

 - Would it be possible to automatically load the uinput module?  I
 think to all the people who have the same problem.

I don't want to go there, it doesn't help when uinput isn't available
anyway. There should be a warning in the log when uinput is not
available, I'll doublecheck that.

 - Can you write (in 10 minutes) a file about how beep works (in
 linux?)? It seems that the card does no beep, it should be simulated
 in software, and uinput module is needed (are there other input
 modules?)

All you need to know is in pommed/beep.c. Basically you create an
input device in userspace which handles beep events and the kernel
happily passes them along, then all you have to do is ... well, *beep*
:)

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



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