Re: [arch-general] alsa, hdmi, and the invisible magic output
On Fri, Dec 3, 2010 at 7:21 PM, Damjan Georgievski wrote:
> > Also, when trying to open a file with alsaplayer, if vlc or banshee are
> > already playing something, that error pops out:
> >
> > ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> > snd_pcm_open: Device or resource busy (plug:dmix)
> > [...]
> > NOTE: THIS IS THE NULL PLUGIN. YOU WILL NOT HEAR SOUND!!
> >
> > I don't understand.
> > As far as I remember, I was always able to play a game while watching a
> > video and/or playing music.
> > What happends?
>
> lsof /dev/snd/*
>
> this command will tell you what program has the sound card open.
>
> --
> damjan
>
while using vlc and/or banshee, lsof returns:
COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 6704 faust memCHR 116,4 4477 /dev/snd/pcmC0D0p
pulseaudi 6704 faust 21u CHR 116,7 0t0 4480 /dev/snd/controlC0
pulseaudi 6704 faust 22u CHR 116,4 0t0 4477 /dev/snd/pcmC0D0p
pulseaudi 6704 faust 23u CHR 116,7 0t0 4480 /dev/snd/controlC0
pulseaudi 6704 faust 30u CHR 116,7 0t0 4480 /dev/snd/controlC0
mixer_app 6821 faust 22u CHR 116,7 0t0 4480 /dev/snd/controlC0
and once I started playing a video with opera (shutting down vlc/banshee),
lsof gives:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 6704 faust 23u CHR 116,7 0t0 4480 /dev/snd/controlC0
pulseaudi 6704 faust 30u CHR 116,7 0t0 4480 /dev/snd/controlC0
mixer_app 6821 faust 22u CHR 116,7 0t0 4480 /dev/snd/controlC0
operaplug 29834 faust memCHR 116,4 4477 /dev/snd/pcmC0D0p
operaplug 29834 faust 10r CHR 116,2 0t0 3694 /dev/snd/timer
operaplug 29834 faust 11u CHR 116,4 0t0 4477 /dev/snd/pcmC0D0p
operaplug 29834 faust 12u CHR 116,7 0t0 4480 /dev/snd/controlC0
Even if I pkill pulseaudio, after restarting vlc, it comes back.
I'm also a bit surprised by the logs I found on messages:
Dec 3 19:16:01 alpha crond[2005]: FILE /var/spool/cron/root USER root PID
29120 job sys-hourly
Dec 3 19:30:01 alpha crond[2005]: FILE /var/spool/cron/faust USER faust PID
29258 /usr/local/bin/switch_wall
Dec 3 19:38:47 alpha pulseaudio[6704]: module-x11-publish.c: PulseAudio
information vanished from X11!
*Dec 3 18:39:31 alpha rtkit-daemon[2346]: Successfully made thread 29933 of
process 29933 ((unreachable)/usr/bin/pulseaudio) owned by '42' high priority
at nice level -11.
Dec 3 18:39:31 alpha rtkit-daemon[2346]: Supervising 1 threads of 1
processes of 1 users.
Dec 3 18:40:39 alpha rtkit-daemon[2346]: Successfully made thread 31100 of
process 29933 ((unreachable)/usr/bin/pulseaudio) owned by '42' RT at
priority 5.
Dec 3 18:40:39 alpha rtkit-daemon[2346]: Supervising 2 threads of 1
processes of 1 users.
Dec 3 18:40:39 alpha rtkit-daemon[2346]: Successfully made thread 31101 of
process 29933 ((unreachable)/usr/bin/pulseaudio) owned by '42' RT at
priority 5.
Dec 3 18:40:39 alpha rtkit-daemon[2346]: Supervising 3 threads of 1
processes of 1 users.
*Dec 3 19:40:40 alpha pulseaudio[29933]: alsa-util.c: snd_pcm_avail_delay()
returned strange values: delay 0 is less than avail 16.
Dec 3 19:40:40 alpha pulseaudio[29933]: alsa-util.c: Most likely this is a
bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA
developers.
Dec 3 19:40:40 alpha pulseaudio[29933]: alsa-util.c: snd_pcm_dump():
Dec 3 19:40:40 alpha pulseaudio[29933]: alsa-util.c: Soft volume PCM
Dec 3 19:40:40 alpha pulseaudio[29933]: alsa-util.c: Control: PCM Playback
Volume
rtkit-daemon is logging one hour in the past, compared to other processes.
what's that?
whatever...
I read to the pulseaudio wiki page, and tried to "finish" installing it (as
I already may have start, if gnome's already lauching it... I just don't
remember why/how/when I'ld have done that...)
I installed
- pulseaudio-alsa (why would I've installed pulseaudio without
pulseaudio-alsa?!)
- lib32-alsa-plugins (web browser sound does not work without it)
- lib32-pulse
and some gnome modules (gnome-media-?-pulse, can't find them back in the
history, but I had to uninstall their equivalents without pulse)
then, I rmmod and blacklisted snd_pcm_oss, modified libao.conf to use
pulseaudio
/etc/asound.conf has been replaced (understand: move it, or the related
package won't install), ...
nothing special, just following the wiki page.
And now, I can play quakelive/watch a flash video while listening to music,
using vlc or banshee.
Everything's back to normal. Except pulse is correctly installed.
And, last but not least: TV and motherboard output the same thing, so I can
choose to plug my jack to the TV or to the computer (while before, only vlc
outputed on the TV).
So, thanks for your help!
And sorry for my english...
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
"Nobody wants to say how this works.
Maybe nobody k
Re: [arch-general] alsa, hdmi, and the invisible magic output
> Also, when trying to open a file with alsaplayer, if vlc or banshee are > already playing something, that error pops out: > > ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave > snd_pcm_open: Device or resource busy (plug:dmix) > [...] > NOTE: THIS IS THE NULL PLUGIN. YOU WILL NOT HEAR SOUND!! > > I don't understand. > As far as I remember, I was always able to play a game while watching a > video and/or playing music. > What happends? lsof /dev/snd/* this command will tell you what program has the sound card open. -- damjan
Re: [arch-general] alsa, hdmi, and the invisible magic output
On Fri, Dec 3, 2010 at 10:31 AM, Philipp Überbacher
wrote:
> Excerpts from Samuel Martín Moro's message of 2010-12-03 01:45:14 +0100:
> > I added this .asoundrc:
> >
> > pcm.!default {
> > type hw
> > card 0
> > }
> >
> > ctl.!default {
> > type hw
> > card 0
> > }
> >
> > It fixed at least a problem: I've no more warning about
> snd_pcm_dmix_open.
> > But, still no sound while banshee's operating...
>
> I don't know the .asoundrc syntax but as far as I can tell you should
> tell your programs to use a dmix device instead of hw:something. dmix
> means software mixing while hw:something means the program uses the
> device exclusively.
>
> If that doesn't work you could try PA.
>
> Good luck.
>
>
I have now the following:
pcm.card0 {
type plug
slave.pcm "dmix"
hint {
show on
description "My dmix output"
}
}
ctl.mixer0 {
type hw
card 0
}
I also tried replacing slave.pcm "dmix" of card0 by "dmixer", defining the
following:
pcm.dmixer {
type dmix
ipc_key 2048
slave {
pcm "hw:0,1"
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
bindings {
0 0
1 1
}
}
None of them fixed the problem.
And I'm still not sure I'm calling the good output (the second test uses
hw0,1, the first one does not specify it)
But there's nothing coming out of my TV anymore.
Also, when trying to open a file with alsaplayer, if vlc or banshee are
already playing something, that error pops out:
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
snd_pcm_open: Device or resource busy (plug:dmix)
[...]
NOTE: THIS IS THE NULL PLUGIN. YOU WILL NOT HEAR SOUND!!
I don't understand.
As far as I remember, I was always able to play a game while watching a
video and/or playing music.
What happends?
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
Excerpts from Samuel Martín Moro's message of 2010-12-03 01:45:14 +0100:
> I added this .asoundrc:
>
> pcm.!default {
> type hw
> card 0
> }
>
> ctl.!default {
> type hw
> card 0
> }
>
> It fixed at least a problem: I've no more warning about snd_pcm_dmix_open.
> But, still no sound while banshee's operating...
I don't know the .asoundrc syntax but as far as I can tell you should
tell your programs to use a dmix device instead of hw:something. dmix
means software mixing while hw:something means the program uses the
device exclusively.
If that doesn't work you could try PA.
Good luck.
Re: [arch-general] alsa, hdmi, and the invisible magic output
I just noticed:
I've two pluseaudio items in the startup applications list (from gnome)
first one doing 'start-pulseaudio-x11'
and the other one: 'start-pulseaudio-kde'
What's that? Might it be related?
On Fri, Dec 3, 2010 at 9:12 AM, Samuel Martín Moro wrote:
>
> fa...@alpha : cat /proc/asound/modules
> 0 snd_hda_intel
> fa...@alpha : cat /etc/modprobe.d/*.conf
> blacklist kyrofb
> blacklist sisfb
> blacklist tdfxfb
> blacklist tridentfb
> blacklist savagefb
> blacklist s3fb
> blacklist viafb
> blacklist vmlfb
> blacklist cyber2000fb
> blacklist neofb
> blacklist rivafb
> blacklist uvesafb
> blacklist radeonfb
> blacklist atyfb
> blacklist aty128fb
> blacklist cirrusfb
> blacklist pm2fb
> blacklist vt8623fb
> blacklist sstfb
> blacklist nvidiafb
> blacklist kyrofb
> blacklist sisfb
> blacklist tdfxfb
> blacklist tridentfb
> blacklist savagefb
> blacklist s3fb
> blacklist viafb
> blacklist vmlfb
> blacklist cyber2000fb
> blacklist neofb
> blacklist rivafb
> blacklist uvesafb
> blacklist radeonfb
> blacklist atyfb
> blacklist aty128fb
> blacklist cirrusfb
> blacklist pm2fb
> blacklist vt8623fb
> blacklist sstfb
> blacklist nvidiafb
> blacklist nouveau
> alias snd-card-0 snd-hda-intel
> alias sound-slot-0 snd-hda-intel
> install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
> ohci_hcd $CMDLINE_OPTS
> install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
> uhci_hcd $CMDLINE_OPTS
> fa...@alpha :
>
> Behold, the invisible sound device!
>
> So? Am I fucked?
> Or may one of my modprobe be the cause?
>
>
>
> On Fri, Dec 3, 2010 at 4:11 AM, Andy Reindl wrote:
>
>> cat /proc/asound/modules
>
>
>
>
> --
> Samuel Martín Moro
> {EPITECH.} tek5
> CamTrace S.A.S
> (+033) 1 41 38 37 60
> 1 Allée de la Venelle
> 92150 Suresnes
> FRANCE
>
> "Nobody wants to say how this works.
> Maybe nobody knows ..."
> Xorg.conf(5)
>
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
fa...@alpha : cat /proc/asound/modules
0 snd_hda_intel
fa...@alpha : cat /etc/modprobe.d/*.conf
blacklist kyrofb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist savagefb
blacklist s3fb
blacklist viafb
blacklist vmlfb
blacklist cyber2000fb
blacklist neofb
blacklist rivafb
blacklist uvesafb
blacklist radeonfb
blacklist atyfb
blacklist aty128fb
blacklist cirrusfb
blacklist pm2fb
blacklist vt8623fb
blacklist sstfb
blacklist nvidiafb
blacklist kyrofb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist savagefb
blacklist s3fb
blacklist viafb
blacklist vmlfb
blacklist cyber2000fb
blacklist neofb
blacklist rivafb
blacklist uvesafb
blacklist radeonfb
blacklist atyfb
blacklist aty128fb
blacklist cirrusfb
blacklist pm2fb
blacklist vt8623fb
blacklist sstfb
blacklist nvidiafb
blacklist nouveau
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
ohci_hcd $CMDLINE_OPTS
install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
uhci_hcd $CMDLINE_OPTS
fa...@alpha :
Behold, the invisible sound device!
So? Am I fucked?
Or may one of my modprobe be the cause?
On Fri, Dec 3, 2010 at 4:11 AM, Andy Reindl wrote:
> cat /proc/asound/modules
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
What does "cat /proc/asound/modules" give you? If it lists two different
modules, maybe the driver you don't want is loading before the good one,
causing alsa to pick the bad one as the primary. In which case you might
just be able to fix that by placing the following in
/etc/modprobe.d/modprobe.conf: "options module_name_here index=-2" which
should make the bad module load after the good one. That happened on my
system, and this fix worked perfectly for me.
--
Andy
On Thu, Dec 2, 2010 at 5:45 PM, Samuel Martín Moro wrote:
> I added this .asoundrc:
>
> pcm.!default {
> type hw
> card 0
> }
>
> ctl.!default {
> type hw
> card 0
> }
>
> It fixed at least a problem: I've no more warning about snd_pcm_dmix_open.
> But, still no sound while banshee's operating...
>
>
> On Fri, Dec 3, 2010 at 1:22 AM, Samuel Martín Moro >wrote:
>
> > I've seen that.
> > But I did not seen anything about using a specific output of the card.
> > as I only have one detected device, how can I set HDMI as default output?
> > (or: how can I see my graphic card as a audio device too?)
> > Is it that 'bindings' keyword, that's not explained on the wiki?
> >
> > 2010/12/3 Cédric Girard
> >
> > On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro >> >wrote:
> >>
> >> >
> >> > What can I do?
> >> > Setting HDMI as default (only) output? How to do so?
> >> > Wait for a patch? Is it a kernel-related bug? Or with nvidia driver?
> >> > Would that even fix the banshee/browser troubles accessing device?
> >> >
> >> >
> >> You can control Alsa routing with the asoundrc [1] config file.
> >>
> >> [1] http://alsa.opensrc.org/.asoundrc
> >>
> >> --
> >> Cédric Girard
> >>
> >
> >
> >
> > --
> > Samuel Martín Moro
> > {EPITECH.} tek5
> > CamTrace S.A.S
> > (+033) 1 41 38 37 60
> > 1 Allée de la Venelle
> > 92150 Suresnes
> > FRANCE
> >
> > "Nobody wants to say how this works.
> > Maybe nobody knows ..."
> > Xorg.conf(5)
> >
>
>
>
> --
> Samuel Martín Moro
> {EPITECH.} tek5
> CamTrace S.A.S
> (+033) 1 41 38 37 60
> 1 Allée de la Venelle
> 92150 Suresnes
> FRANCE
>
> "Nobody wants to say how this works.
> Maybe nobody knows ..."
> Xorg.conf(5)
>
Re: [arch-general] alsa, hdmi, and the invisible magic output
I added this .asoundrc:
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
It fixed at least a problem: I've no more warning about snd_pcm_dmix_open.
But, still no sound while banshee's operating...
On Fri, Dec 3, 2010 at 1:22 AM, Samuel Martín Moro wrote:
> I've seen that.
> But I did not seen anything about using a specific output of the card.
> as I only have one detected device, how can I set HDMI as default output?
> (or: how can I see my graphic card as a audio device too?)
> Is it that 'bindings' keyword, that's not explained on the wiki?
>
> 2010/12/3 Cédric Girard
>
> On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro > >wrote:
>>
>> >
>> > What can I do?
>> > Setting HDMI as default (only) output? How to do so?
>> > Wait for a patch? Is it a kernel-related bug? Or with nvidia driver?
>> > Would that even fix the banshee/browser troubles accessing device?
>> >
>> >
>> You can control Alsa routing with the asoundrc [1] config file.
>>
>> [1] http://alsa.opensrc.org/.asoundrc
>>
>> --
>> Cédric Girard
>>
>
>
>
> --
> Samuel Martín Moro
> {EPITECH.} tek5
> CamTrace S.A.S
> (+033) 1 41 38 37 60
> 1 Allée de la Venelle
> 92150 Suresnes
> FRANCE
>
> "Nobody wants to say how this works.
> Maybe nobody knows ..."
> Xorg.conf(5)
>
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
I've seen that.
But I did not seen anything about using a specific output of the card.
as I only have one detected device, how can I set HDMI as default output?
(or: how can I see my graphic card as a audio device too?)
Is it that 'bindings' keyword, that's not explained on the wiki?
2010/12/3 Cédric Girard
> On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro >wrote:
>
> >
> > What can I do?
> > Setting HDMI as default (only) output? How to do so?
> > Wait for a patch? Is it a kernel-related bug? Or with nvidia driver?
> > Would that even fix the banshee/browser troubles accessing device?
> >
> >
> You can control Alsa routing with the asoundrc [1] config file.
>
> [1] http://alsa.opensrc.org/.asoundrc
>
> --
> Cédric Girard
>
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro wrote: > > What can I do? > Setting HDMI as default (only) output? How to do so? > Wait for a patch? Is it a kernel-related bug? Or with nvidia driver? > Would that even fix the banshee/browser troubles accessing device? > > You can control Alsa routing with the asoundrc [1] config file. [1] http://alsa.opensrc.org/.asoundrc -- Cédric Girard
[arch-general] alsa, hdmi, and the invisible magic output
Good evening everyone, I'm using arch since a while now. Everything was working just fine, until a few weeks (months?) ago. Since, I had a few problems I can't understand : The first symptom was the day I lost sound on my regular audio output (moterhboard intel HDA). I finally noticed sound was actually send to my TV through my G92 9800GT. I had a long period during while I was always switching my speakers wire from my tower to the screen, and back to the computer. The main problem beeing that, after putting the screen in sleep mode, I wasn't able to get the sound back without restarting X. Since, the problem changed, somewhat. Now, vlc sends its sound in both my motherboard and my graphic card outputs. While banshee's still only using the motherboard one. The most recent symptom is that, when I'm already playing some music with banshee, I can't have sound on any web browser (opera, firefox & chromium tested so far). I first though it was flash-related. But since I can't have sound while playing quakelive too (and AFAIK, QLive doesn't uses flash), I'm a bit confused... What could be happening? The only way I can get sound working back in the web browser is to shut down banshee and restart the browser. And I won't be able to make banshee work again before closing the browser, and then starting banshee. The following error is continuously reported when executing chrome from terminal, while using banshee: ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave I searched for some details on google. It seems the first thing I may do is to specify which audio device use by default. So, I tried to find where my HDMI output is... fa...@alpha : aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 fa...@alpha : lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller fa...@alpha /proc/asound : l -R /proc/asound/ /proc/asound/: total 0 dr-xr-xr-x 5 root root 0 Dec 2 23:45 card0 -r--r--r-- 1 root root 0 Dec 2 23:45 cards -r--r--r-- 1 root root 0 Dec 2 23:45 devices -r--r--r-- 1 root root 0 Dec 2 23:45 hwdep lrwxrwxrwx 1 root root 5 Dec 2 23:45 Intel -> card0 -r--r--r-- 1 root root 0 Dec 2 23:45 modules dr-xr-xr-x 2 root root 0 Dec 2 23:45 oss -r--r--r-- 1 root root 0 Dec 2 23:45 pcm dr-xr-xr-x 2 root root 0 Dec 2 23:45 seq -r--r--r-- 1 root root 0 Dec 2 23:45 timers -r--r--r-- 1 root root 0 Dec 2 23:45 version /proc/asound/card0: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 codec#0 -r--r--r-- 1 root root 0 Dec 2 23:45 id -rw-r--r-- 1 root root 0 Dec 2 23:45 oss_mixer dr-xr-xr-x 5 root root 0 Dec 2 23:45 pcm0c dr-xr-xr-x 3 root root 0 Dec 2 23:45 pcm0p dr-xr-xr-x 3 root root 0 Dec 2 23:45 pcm1p /proc/asound/card0/pcm0c: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 oss dr-xr-xr-x 2 root root 0 Dec 2 23:45 sub0 dr-xr-xr-x 2 root root 0 Dec 2 23:45 sub1 dr-xr-xr-x 2 root root 0 Dec 2 23:45 sub2 /proc/asound/card0/pcm0c/sub0: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 hw_params -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 prealloc -r--r--r-- 1 root root 0 Dec 2 23:45 prealloc_max -r--r--r-- 1 root root 0 Dec 2 23:45 status -r--r--r-- 1 root root 0 Dec 2 23:45 sw_params /proc/asound/card0/pcm0c/sub1: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 hw_params -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 prealloc -r--r--r-- 1 root root 0 Dec 2 23:45 prealloc_max -r--r--r-- 1 root root 0 Dec 2 23:45 status -r--r--r-- 1 root root 0 Dec 2 23:45 sw_params /proc/asound/card0/pcm0c/sub2: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 hw_params -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 prealloc -r--r--r-- 1 root root 0 Dec 2 23:45 prealloc_max -r--r--r-- 1 root root 0 Dec 2 23:45 status -r--r--r-- 1 root root 0 Dec 2 23:45 sw_params /proc/asound/card0/pcm0p: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 oss dr-xr-xr-x 2 root root 0 Dec 2 23:45 sub0 /proc/asound/card0/pcm0p/sub0: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 hw_params -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 prealloc -r--r--r-- 1 root root 0 Dec 2 23:45 prealloc_max -r--r--r-- 1 root root 0 Dec 2 23:45 status -r--r--r-- 1 root root 0 Dec 2 23:45 sw_params /proc/asound/card0/pcm1p: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 oss dr-xr-xr-x 2 root root 0 Dec 2 23:45 sub0 /proc/asound/card0/pcm1p/sub0: total 0 -r--r--r-- 1 root root 0 Dec 2 23:45 hw_params -r--r--r-- 1 root root 0 Dec 2 23:45 info -rw-r--r-- 1 root root 0 Dec 2 23:45 prealloc -r--r--r-- 1 root root 0 Dec 2 23:45 prealloc_max -r--r--r-- 1 root r
