On Fri, 01 Aug 2003, D.J. Bolderman wrote:

> On do, 31 jul 2003, Michael Gruetzner wrote:
> 
> > Hello,
> 
> > did you compile a new kernel? If yes, then you need to reemerge 
> > alsa-driver after 'make modules_install'. To start alsa you can switch 
> > between the different states with '/etc/init.d/alsasound zap'.
> 
> Yes, I did compile a new kernel, but I also re-emerged alsa-driver
> after that.
> 
> The alsasound zap command seems to work, but I don't get any sound yet
> :(
> 
> Any more suggestions ?
> 
> Thanks,
> Dick

Hi, first, off the top of my head, is the linux symlink in /usr/src
pointing to the right kernel (the one you are using): alsa uses this
symlink to determine where it should install its modules.

I had a problem just like yours a while ago. Here's my debug
procedure for alsa (it's kind of a works for me solution, but worth a
try, it's not designed to actually solve anything, but to acquire
enough onformation to pinpoint the problem) :

1) If you are using any kind of xdm disable them (they tend to call
for the modules, hence load them and do not resort to the alsasound
script).
2) Remove the startup script (alsasound) from the boot runlevel.
3) reboot the machine.
4) run alsasound by hand :

   4.1) Does it complain that the modules are already loaded ? 

If so, another app needs sound and insmods the
modules before you lauched the script, and possibly before the script
is run when in the runlevel. Check that, and ask the app to be
launched after the script

   4.2) If script runs flawlessly, start X and xmms. If any sound
        server is enabled, disable it (we are tryong to have as few
        interfering sound app as possible), and restart X. Do not
        forget to check in the alsamixer if the channels are
        unmuted. Run xmms, load the alsa plugin. Does xmms output
        sound ? If not, make sure that the snd-pcm-oss and
        snd-mixer-oss modules are present, and try the oss plugin,
        does it work ? (make sure that you did NOT compile any oss
        support inside the kernel !!). 

5) If the above did not work, try insmoding the modules by hand, and
playing sound from xmms.

6) Try the esd or arts plugins from gnome or kde.

You should now have enough information to pinpoint the problem. If
not, could you send any unexpected output you got.

One last thing, it can help to launch xmms from a console in order to
get the debug messages.

HTH, good luck,

Jonathan

> > D.J. Bolderman wrote:
> > >Guys,
> 
> > >For some reason, alsa sound stopped working. Xmms produces no sound
> > >output. Xawtv and mpg123 are working fine. Last night I was fiddling
> > >around with Mythtv, but I can't remember to have changed anything
> > >which could affect alsa. 
> 
> > >I re-emerged alsa-driver and alsa-xmms, but to no avail...
> 
> > >Restarting alsasound seems to give some problems:
> 
> > >bash-2.05b# /etc/init.d/alsasound restart
> > > * ALSA driver is already running.
> > >bash-2.05b# /etc/init.d/alsasound stop   
> > >  * ERROR:  "alsasound" has not yet been started.
> > >bash-2.05b# /etc/init.d/alsasound start
> > >   * ALSA driver is already running.
> 
> 
> > >lsmod shows:
> 
> > >Module                  Size  Used by    Not tainted
> > >snd-pcm-oss            39652   0  (autoclean)
> > >snd-mixer-oss          13752   0  (autoclean) [snd-pcm-oss]
> > >i2c-dev                 4772   0  (unused)
> > >tuner                  10144   1  (autoclean)
> > >tvaudio                12892   0  (autoclean) (unused)
> > >msp3400                17036   1  (autoclean)
> > >bttv                   69888   1 
> > >i2c-algo-bit            8360   1  [bttv]
> > >radeon                104392   2 
> > >agpgart                14772   3  (autoclean)
> > >i2c-proc                7472   0 
> > >i2c-core               16232   0  [i2c-dev tuner tvaudio msp3400 bttv
> > >i2c-algo-bit i2c-proc]
> > >snd-cs46xx             72252   1 
> > >snd-rawmidi            15712   0  [snd-cs46xx]
> > >snd-seq-device          4420   0  [snd-rawmidi]
> > >snd-ac97-codec         42232   0  [snd-cs46xx]
> > >snd-pcm                68512   0  [snd-pcm-oss snd-cs46xx]
> > >snd-page-alloc          7060   0  [snd-cs46xx snd-pcm]
> > >snd-timer              16900   0  [snd-pcm]
> > >snd                    34756   1  [snd-pcm-oss snd-mixer-oss
> > >snd-cs46xx snd-rawmidi snd-seq-device snd-ac97-codec snd-pcm
> > >snd-timer]
> > >soundcore               4580   6  [bttv snd]
> 
> > >Relevant cat /proc/pci:
> 
> > > Bus  0, device   9, function  0:
> > >     Multimedia audio controller: Cirrus Logic CS 4614/22/24
> > >     [CrystalClear SoundFusion Audio Accelerator] (rev 1).
> > >     IRQ 5.
> > >     Master Capable.  Latency=32.  Min Gnt=4.Max Lat=24.
> > >     Non-prefetchable 32 bit memory at 0xef101000 [0xef101fff].
> > >     Non-prefetchable 32 bit memory at 0xef000000 [0xef0fffff].
> 
> > >What could be the problem here ?
> 
> --
> [EMAIL PROTECTED] mailing list
> 
> 

-- 
You now have Asian Flu.

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to