My computer is connected to my piano through a
usb-midi cable. If I use my
piano while the computer starts up, whether /dev/dsp
is renamed to /dev/dsp1, or it
simply disappears! I'm using a Debian Etch weekly
build from 13 January 2006. If I
do an `lsmod', all snd-* modules are loaded as usual.
What is happening? I did not
post this on bugs.debian.org as I do not know in which
package the bug is. Thanks
in advance for answering me.


_____________________
Eduard

 ________________________________________
__________
Do You Yahoo!?
En finir avec le spam? Yahoo! Courriel vous offre la meilleure protection po
ssible contre les messages non nollicités
http://mail.yahoo.ca Yahoo! Courriel


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.or
g

[ Post a follow-up to this message ]

Package: udev
Severity: normal

On Sun, Jan 21, 2007 at 06:02:10PM -0500, Dumitrescu, Eduard wrote:
>     My computer is connected to my piano through a usb-midi cable. If
> I use my piano while the computer starts up, whether /dev/dsp is
> renamed to /dev/dsp1,

Is that a problem? If so, how? Software that uses your MIDI-interface
should just work with dsp1, too.

> or it simply disappears!

That, of course, *is* a problem.

> I'm using a Debian Etch weekly build from 13
> January 2006. If I do an `lsmod', all snd-* modules are loaded as
> usual.

It would be helpful if you could provide more information, such as:

* what type of MIDI-interface you have (the output of 'lsusb' would be
good)
* what kernel you're running
* what architecture you're running this on.

> What is happening? I did not post this on bugs.debian.org as I
> do not know in which package the bug is.

My guess is that it's either the kernel or udev which is doing something
wrong here. I'm filing this as a bug on udev for the time being; I'm
sure Marco will properly reassign this bug once you've provided the
extra information.

Also note that there is a package "generic" which was specifically
created for cases like these, where you're not sure which package is
responsible for the bug. You may want to file a bug against generic next
time.

(Please wait with providing feedback until you know the bug number, and
then send it to <number>@bugs.debian.org).

--
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.or
g

[ Post a follow-up to this message ]

#include <hallo.h>
* Wouter Verhelst [Fri, Jan 26 2007, 02:15:35PM]:
> Package: udev
> Severity: normal
>
> On Sun, Jan 21, 2007 at 06:02:10PM -0500, Dumitrescu, Eduard wrote: 
>
> Is that a problem? If so, how? Software that uses your MIDI-interface
> should just work with dsp1, too.

Looks like the same design problem I complained in the past with having
/dev/cdrw1+ while /dev/cdrw is missing. And I still think that this idea
of linking ONLY /dev/functionality0 to /dev/functionality is stupid if
the enumeration is not created based on the list of capable devices but
just by getting the numbers from the set of related devices (any CD
reader, or any alsa-device, etc.).

/dev/foo should better be linked to /dev/fooN (N==lowest possible number).

Eduard.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.or
g

[ Post a follow-up to this message ]

On Jan 31, Eduard Bloch <edi@gmx.de> wrote:

> /dev/foo should better be linked to /dev/fooN (N==lowest possible number).
I agree in the general case (e.g. /dev/video), but not when there is an
established practice of using /dev/device in the place of /dev/device0
(e.g. /dev/dsp).
Backward compatibility sucks.

-- 
ciao,
Marco

[ Post a follow-up to this message ]