On 3/20/07, David Baron <[EMAIL PROTECTED]> wrote:
Is there any conflicts here? Keep getting failure to open existing /dev/kqemu
(regardless of permissions) with an rt-patched (Ingo) kernel.
I would assume that most out of tree modules won't work with -rt, and
even some in-tree stuff - for exam
Debian.org
linuxquestions.org
phlak.org
knopper.de
Sycamorex wrote:
>Hi guys
>what are your favourite linux websites
>(and linux audio websites)?
>can you post them
>
>thank you
>
>marcin
>
>
>
>
> > Saw something interestic in my logchecks:
> > kernel: Generic RTD Driver v1.07
> >
> > If I take this one off, the "real" one will modprobe :-)
> > Question is, who is loading genrtc BEFORE /etc/modules gets
> > referenced?
> > Actually, I tried commenting it there and ... the error message
> >
On Mon, 2006-02-06 at 16:47 +0200, David Baron wrote:
> Saw something interestic in my logchecks:
> kernel: Generic RTD Driver v1.07
>
> If I take this one off, the "real" one will modprobe :-)
> Question is, who is loading genrtc BEFORE /etc/modules gets
> referenced?
> Actually, I tried comment
On Sat, 2006-02-04 at 21:55 +0200, David Baron wrote:
> This has been in my /etc/modules from the start. For a while now, (most
> recent?) 2.6 kernels, this will not load "device not found". Since it did not
> seem to effect anything, I just let it be. (Note I have both a rtc.ko and
> rtcgen.ko
On Wednesday 01 February 2006 01:39,
[EMAIL PROTECTED] wrote:
> > Made a kernel with alsa sound support compiled in! I also compiled in
> > the
> > "generic" devices. Result: NO UNDEFINED. My three (a set ncards = 3)
> > became
> > dummy, virmidi and the ensonic. The ensonic did not play, however,
On Tue, 2006-01-31 at 20:09 +0200, David Baron wrote:
>
> Made a kernel with alsa sound support compiled in! I also compiled in
> the
> "generic" devices. Result: NO UNDEFINED. My three (a set ncards = 3)
> became
> dummy, virmidi and the ensonic. The ensonic did not play, however, but
> the
>
On Thursday 26 January 2006 23:03, [EMAIL PROTECTED]
wrote:
> > >Newer kernels boot with many undefines. They seem to correspond to stuff
> > > in the sound core modules. Do I now need to explicitely load these or
> > > soundcore.ko on boot up (i.e. placing them in /etc/modules--somewhere
> > > al
On Thu, 2006-01-26 at 21:55 +0200, David Baron wrote:
> >Also a problem in 2.6.14. I am not using udev or devfs but have explicitely
> >created /dev nodes (old fashioned way and far far too many entries, but ...
> >always worked before).
>
> >Newer kernels boot with many undefines. They seem to
On Thu, 2006-01-26 at 21:55 +0200, David Baron wrote:
> >Also a problem in 2.6.14. I am not using udev or devfs but have explicitely
> >created /dev nodes (old fashioned way and far far too many entries, but ...
> >always worked before).
>
> >Newer kernels boot with many undefines. They seem to
On Thu, 2006-01-26 at 21:30 +0200, David Baron wrote:
> Also a problem in 2.6.14. I am not using udev or devfs but have explicitely
> created /dev nodes (old fashioned way and far far too many entries, but ...
> always worked before).
>
> Newer kernels boot with many undefines. They seem to corr
On Wed, Dec 22, 2004 at 06:31:33PM +0200, David Baron wrote:
modprobe.conf -- where did it go? If it is not there, how did everything get
To bed, I hope. ;-)
/etc/modprobe.conf doesn't exist anymore. Debian uses the directory
/etc/modprobe.d/, where you can put your module configuration files.
Sha
On Wednesday 22 December 2004 17:13, Florian Schmidt wrote:
> On Wed, 22 Dec 2004 16:43:56 +0200
>
> David Baron <[EMAIL PROTECTED]> wrote:
> > On Wednesday 22 December 2004 16:11, Florian Schmidt wrote:
> > > possible solution:
> > >
> > > modprobe snd_seq_midi
> >
> > This indeed go MIDI going! T
On Wed, 22 Dec 2004 16:43:56 +0200
David Baron <[EMAIL PROTECTED]> wrote:
> On Wednesday 22 December 2004 16:11, Florian Schmidt wrote:
> > possible solution:
> >
> > modprobe snd_seq_midi
>
> This indeed go MIDI going! Thanks.
>
> Question now is: What is happening on bootup (since I never need
On Wednesday 22 December 2004 16:11, Florian Schmidt wrote:
> possible solution:
>
> modprobe snd_seq_midi
This indeed go MIDI going! Thanks.
Question now is: What is happening on bootup (since I never needed to
explicitely modprobe this before?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Wed, 22 Dec 2004 16:07:29 +0200
David Baron <[EMAIL PROTECTED]> wrote:
> > Please show us the output of
> >
> > amidi -l
> #amidi -l
> DeviceName
> hw:0,0ES1371
> hw:1,0,0 UM-1 MIDI 1
> hw:2,0MPU-401 UART MIDI
ok
>
> > aconnect -io
> # UART MIDI
> [EMAIL PROTECTED]:~$ aconnect -
On Wednesday 22 December 2004 14:36, Florian Schmidt wrote:
> On Wed, 22 Dec 2004 14:19:55 +0200
>
> David Baron <[EMAIL PROTECTED]> wrote:
> > Anyone having problems here. My devices no longer show up. Audio works
> > fine.
> >
> > Note that
> > 1. /proc/asound/cards shows ALL devices
> > 2. cat /
On Wed, 22 Dec 2004 14:19:55 +0200
David Baron <[EMAIL PROTECTED]> wrote:
> Anyone having problems here. My devices no longer show up. Audio works fine.
>
> Note that
> 1. /proc/asound/cards shows ALL devices
> 2. cat /dev/midi# show events from the keyboard. The keyboard is through a
> USB
>
On Thursday 02 December 2004 19:07,
[EMAIL PROTECTED] wrote:
> hi, I'm new here. i don't know if it is ot, but i risk...
> Does anybody know how to make finale 2000/2003 work with wine?
> I tried, it works, shows all the buttons ok, but the notes are still
> symbols.
I believe the problem is that
Olivier,
> > But about color scale squares, just imagine how compact it can get : 8
> > tracks with 4 levels each, that's 32 little square on a gtk drawing
> > area. I believe white to black would be very efficient, and rolling over
> > a level or adjusting it, the status bar would get you some
Ryan,
> It's not *impossible* I bet someone with a lot of patience could set
> some reasonable loop points. The mellotron is a neat sounding
> instrument, I'd be really excited to have digital copies of the original
> tape loops. But each of these key presses is about a minute long and
> the mell
Stefan,
> that sounds almost like blenders "slide buttons" .>
> they basically like that (if it doesn't get mangled):
>
> /\
> |< 0.800 >|
> \/
>
> you can:
> a: click on the edges to change the value step by step (ctrl+click for
> larger steps)
> b: click and move y
> [EMAIL PROTECTED] wrote:
> > How 'bout those little number like they use in high endish graphics programs?
> > ...Where you have a row of numbers that it looks like they pulled out of a slot
> > machine and you can either click on them and enter a new number, use the up and
> > down arrows on
> On Sun, 2004-07-18 at 20:12, R Parker wrote:
> > > R Parker wrote:
> > > colorful approach :
> > > A little square which is white for 0, black for 1,
> > > and taking a scale of
> > > gray colors for intermediate values. You'd ajust it
> > > the same way as a
> > > knob, pressing the mouse but
Juha Erkkila hat gesagt: // Juha Erkkila wrote:
> about a month ago i upgraded my system from Debian Potato to Woody,
> looking forward to see all the interesting sound applications people
> have been writing, and which ones of those have been packaged for
> Debian. overall, i've been fairly happ
Eric Dantan Rzewnicki hat gesagt: // Eric Dantan Rzewnicki wrote:
> I'm not very familiar with the protocol for asking debian package
> maintainers to change things. What would it take to have the
> Soundtracker, Ecasound and Timidity debian packages converted to alsa
> 0.9.x?
I think, but I may
Juha Erkkila wrote:
>
> i admit i could look a little deeper into muse, but so far i've
> preferred ALSA 0.5, because Soundtracker, Ecasound and Timidity in
> Woody are compiled for 0.5, and i'm quite probably going to use these
> apps a lot (i know that at least Ecasound can be compiled for ALSA
27 matches
Mail list logo
