Re: debian-user-digest Digest V2004 #1325
> From: Chris Metzler <cmetzler@speakeasy.net>
> To: debian-user@lists.debian.org
> Subject: Re: new install, sound not working (+2
> bonus problems)
>
> On Thu, 22 Apr 2004 21:26:56 -0700 (PDT)
> Phil Ramey <philramey@pacbell.net> wrote:
> >
> > 2) in first attempt to get sound working, i
> compiled a
> > new kernel, 2.6.5, with ALSA, but the wrong
> drivers
>
> sid + 2.6 kernel is pretty bold for a new user, to
> be blunt. I don't
> mean to dissuade you -- just that it's not
> surprising that this should
> be hard. Getting everything just so under the new
> 2.6 kernels has
> given a lot of people a lot of difficulty, as
> numerous threads in
> the archive here will show. I haven't tried it yet,
> mainly because
> I do audio work and the configuration of 2.6 kernels
> for optimum
> realtime performance is still being figured out.
>
> I've spent a lot of time messing with ALSA under the
> 2.4's,
> but none under 2.6 (when it got packaged with the
> kernel);
> I'm still not sure how it's different, but it
> apparently is,
> so I'm not sure I'll be any help. With that out of
> the way
> . . .
>
>
> > 3) incremented the "extra version" makefile option
>
> Just out of curiosity . . .I'm not sure what you
> mean by this.
> How are you compiling your kernels? Also, you may
> want to take
> a look at
>
>
http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en
>
> which provides a good explanation of the relatively
> painless
> way to do it in Debian, through use of the make-kpkg
> command.
>
Well, having compiled the 2.6.5 kernel several times,
if you just try to do it straight the system gives
errors because you're installing exactly the same
version, and it generates directories based on version
number (module directories). so if you edit the
"Makefile" in the source directory, there's an "extra
version" field, which you can edit to your heart's
content to keep your system free of kernel version
duplication conflicts.
>
> > and
> > re-compiled with the right drives and ALSA, no
> dice,
> > still didn't work. it detected the chip fine in
> boot,
> > but didn't work.
>
> When you did this, did you configure your kernel so
> that ALSA was
> compiled into the kernel itself, or as separate
> modules? What about
> soundcore? Did you only compile ALSA stuff, or did
> you also compile
> OSS stuff as well as ALSA? Are you sure about these
> answers? Can
> you show me the sound portions of the .config for
> this kernel? And,
> with this kernel booted, can you do an lsmod and
> show what modules
> you have loaded? Also, can you show me the messages
> from it
> "detecting the chip fine in boot"? And what do the
> ALSA portions
> of your /etc/modules.conf look like?
>
Both with OSS and with ALSA I compiled it directly
into the kernel, not as modules. as was Soundcore. I
always compiled either ALSA or OSS, never both, no
conflicts.
Kernel sound for the OSS try:
#
# Sound
#
CONFIG_SOUND=y
#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set
#
# Open Sound System
#
CONFIG_SOUND_PRIME=y
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
CONFIG_SOUND_ES1371=y
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_FORTE is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_AD1980 is not set
for the ALSA shot:
#
# Sound
#
CONFIG_SOUND=y
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
<snip down to the PCI devices>
CONFIG_SND_ENS1371=y
I am currently running a kernel with OSS built in
(doesn't work either), not ALSA, so.... should I go
back to the other kernel with ALSA support? I just
want it to work... (now I understand why people think
it's amazing the first time they see Knoppix boot and
Just Work)
>
> > gnome's volume control gave me crap
> > for not being able to open /dev/mixer so i
> addusered
> > my user into the audio group, which made it quiet
> > down.
>
> Yeah, that's a common pitfall.
>
>
> > Inexplicably, no sound application worked
> > except for Stones, the gnome stones clone. sound
> > started a few seconds into the game, and was
> > low-quality thoughout.
>
> What about other GNOME applications that make sound?
> If you go to
> GNOME's menus, going Desktop Preferences --> Sound,
> and turn on
> "sound events" for GNOME, do you hear sounds
> (assuming you have the
> gnome-audio package installed, which provides the
> .wav files for
> GNOME events)? If you try to play a wav file from
> the command line,
> using the "play" command, e.g.
>
> play /usr/share/sounds/login.wav
>
> what happens? If it doesn't work, what error
> message do you see?
> What if you do
>
> esdplay /usr/share/sounds/login.wav
>
> instead?
>
Neither of those commands are found on my system.
>
> > Tried alsaconf, it didn't
> > detect the chip. alsaconf also gave error:
> "cannot
> > find module SND" three times at run...
>
> OK, this smells to me like you don't actually have
> ALSA installed;
> an lsmod under this case would be handy, as noted
> above. I know
> that you built ALSA during your kernel compile
> because you say
> you did above; but that doesn't mean that ALSA got
> loaded properly
> at boot-time.
>
> One possibility which trips people up fairly often
> is when they
> compile modules for both ALSA and OSS, *and* have
> the discover
> package installed. discover is a hardware detection
> program that
> loads modules on the basis of what it finds. It
> runs before the
> ALSA scripts do during a normal boot process, and
> when it finds
> a soundcard, it *tries to load OSS drivers*. Then,
> the ALSA
> drivers can't load, because the OSS drivers are
> already in and
> taking care of the soundcard. I've heard tell that
> hotplug can
> do this to you too, but I don't have any personal
> experience with
> that. Anyway, lsmod, and an examination of the boot
> log, as
> requested above, should show if this is what's going
> on. The
> solution, if so, is to tell discover (or hotplug) to
> *not* load
> OSS drivers through configuration files.
>
I never have have both OSS and ALSA loaded at the same
time, so I do not believe it's a conflict between the
two, except perhaps in config files, because at boot,
in the OSS version kernel I compliled, it tries to
load ALSA and fails... it also has a long string of
failed module loads that i think were from the 2.4
kernel it was installed with...
lsmod output:
Module Size Used by
nvidia 2070568 12
binfmt_misc 8200 1
(everything else i need is compiled directly into the
kernel, not as modules)
Current (oss) boot log:
Apr 23 10:52:18 box kernel: es1371: version v0.32 time
19:05:02 Apr 22 2004
Apr 23 10:52:18 box kernel: PCI: Found IRQ 9 for
device 0000:00:0e.0
Apr 23 10:52:18 box kernel: PCI: Sharing IRQ 9 with
0000:00:10.2
Apr 23 10:52:18 box kernel: es1371: found chip, vendor
id 0x1274 device id 0x1371 revision 0x08
Apr 23 10:52:18 box kernel: es1371: found es1371 rev 8
at io 0xd800 irq 9 joystick 0x0
Apr 23 10:52:18 box kernel: ac97_codec: AC97 Audio
codec, id: (Unknown)
alsa boot log:
Apr 21 23:10:47 box kernel: Advanced Linux Sound
Architecture Driver Version 1.0.4rc2 (Tue Mar 30
08:19:30 2004 UTC).
Apr 21 23:10:47 box kernel: PCI: Found IRQ 9 for
device 0000:00:0e.0
Apr 21 23:10:47 box kernel: PCI: Sharing IRQ 9 with
0000:00:10.2
Apr 21 23:10:47 box kernel: ALSA device list:
Apr 21 23:10:47 box kernel: #0: Ensoniq AudioPCI
ENS1371 at 0xd800, irq 9
so I was led to believe it was detecting fine...
>
> > 4) recompiled again with proper driver and OSS,
> boot
> > detects the chip (integraded on the mobo,
> > don't'cha'know), and stones works better (music
> this
> > time), but nothing else is fixed. when i load any
> > multimedia program, it complains about not being
> able
> > to open /dev/dsp
>
> What's the complaint error message *specifically*?
>
right now? "osscommon: Unable to open /dev/dsp (in
use?)"
> A common problem that occurs in this instance, with
> you running
> GNOME, has to do with esd. GNOME uses a software
> daemon called
> esd, the "Enlightened Sound Daemon," to mix together
> multiple
> sound sources, so that you can hear multiple
> simultaneous sounds.
> Unfortunately, esd can grab onto /dev/dsp and not
> let any other
> software talk to it because it's busy. One solution
> to this is
> to dump esd. Another is to adjust esd to let go of
> /dev/dsp when
> it doesn't need it, which is done through its config
> file.
>
I've found references online to that config file being
in /etc/esd.conf, but it isn't there on my system.
I'm in a bit of a rush right now, i'll have more time
to tinker later, but I hope this will shed some light
on my problems...
thanks!
-Phil Ramey
Reply to: