29 Oct
2007
29 Oct
'07
6:24 a.m.
Yesterday it worked - could read and play MIDI through my keyboard, or
fluidsynth, and play regular audio stuff.
Today, when I started up the system, KDE tells me:
Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (No such file or directory)
The sound server will continue, using the null output device.
I use ALSA and the system is usually set for Autodetect, but get the
same results if I select ALSA. I should have known that nothing really
works "out of the box" with Linux ;-) What the hey happened and how can
I fix it?
Running Debian testing. Did not update anything between the time it
worked and now.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
29 Oct
29 Oct
7:19 a.m.
New subject: Added E-Mu Midi1x1 adapter, now entire sound system doesn't work!
A few shutdowns/restarts later, it spontaneously started working again.
Stupid computers.
david wrote:
Yesterday it worked - could read and play MIDI through
my keyboard, or
fluidsynth, and play regular audio stuff.
Today, when I started up the system, KDE tells me:
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (No such file or directory)
The sound server will continue, using the null output device.
I use ALSA and the system is usually set for Autodetect, but get the
same results if I select ALSA. I should have known that nothing really
works "out of the box" with Linux ;-) What the hey happened and how can
I fix it?
Running Debian testing. Did not update anything between the time it
worked and now. 
9:54 a.m.
New subject: Added E-Mu Midi1x1 adapter, now entire sound system doesn't work!
david wrote:
Yesterday it worked - could read and play MIDI through
my keyboard, or
fluidsynth, and play regular audio stuff.
Today, when I started up the system, KDE tells me:
> device: default can't be opened for playback (No such file or directory)
The USB device is the default sound card because its driver was loaded
before the driver for your main sound card. The driver load order is
random and can change in successive boots.
Use the sound card configuration tool of your distribution to set a
fixed order that is used regardless of the driver load order.
HTH
Clemens
30 Oct
30 Oct
6:19 a.m.
New subject: Added E-Mu Midi1x1 adapter, now entire sound system doesn't work!
Clemens Ladisch wrote:
david wrote:
Hmmm ... the main soundcard is a device built-in to the motherboard, an
infamous Intel ICH4 PCI device. Wouldn't a PCI device be initialized and
driver installed before a USB device?
Yesterday it worked - could read and play MIDI
through my keyboard, or
fluidsynth, and play regular audio stuff.
Today, when I started up the system, KDE tells me:
> device: default can't be opened for playback (No such file or directory)
The USB device is the default sound card because its driver was loaded
before the driver for your main sound card. The driver load order is
random and can change in successive boots. Use the sound card configuration tool of your
distribution to set a
fixed order that is used regardless of the driver load order.
I use Debian Linux and haven't a clue on how to do that.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
6267
days inactive
6268
days old
linux-audio-user@lists.linuxaudio.org
3 comments
2 participants
participants (
participants (2)
)
-
Clemens Ladisch -
david
-
Clemens Ladisch
-
david