Package: realtime-lsm
Version: 0.8.7-2
Severity: wishlist

I would report this bug against realtime-lsm-source, however, as
reported in #389043, documentation for that package is included in
realtime-lsm, so I report this bug here.

When the user is installing realtime-lsm, it is likely to use it
for musical purpouses. MIDI is functional only if the system
tick is set to 1000Hz, however default for new kernels is 250Hz.

I had to recompile the kernel twice: once to get the lsm module working,
then once again to switch from 250Hz to 1000Hz ticks, in order to get
MIDI working.

If realtime-lsm documentation would suggest to switch to 1000Hz, while
setting SECURITY_CAPABILITIES, this could avoid duplicate compiling
sessions :-).

So a possible enhancement for documentation could be:

just make sure that CONFIG_SECURITY_CAPABILITIES=m, thats the whole
point of it.

+If you plan to use the realtime-lsm modules with musical software, and
your musical equipment uses the MIDI interface, then you also need to
switch the system time clock from a resolution of 250Hz to 1000Hz.
Otherwise MIDI will not work properly. If you do not plan to use MIDI at
all, then this configuration change is not required. In order to switch
from 250Hz to 1000Hz you need to type:

        make menuconfig

from within the kernel source directory. Then navigate to
        Processor Type and Feature --> Timer Frequency
and set the proper value.

Build the new kernel with


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

realtime-lsm depends on no packages.

Versions of packages realtime-lsm recommends:
ii  module-assistant              0.10.8     tool to make module package creati
ii  realtime-lsm-source           0.8.7-2    Source for the realtime Linux secu

-- no debconf information


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

Reply via email to