[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/05/2010 10:23 PM, Rick Sewill wrote:
> On 07/05/2010 09:26 PM, Dave Stevens wrote:
>> Quoting JD <[email protected]>:
> 
>>> Can you post output of lspci?
>>
>> sure, here:
>>
>> 00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a2)
>> 00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a3)
>> 00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a3)
>> 00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
>> 00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)
>> 00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
>> 00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
>> 00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
>> 00:05.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
>> 00:06.0 PCI bridge: nVidia Corporation MCP55 PCI bridge (rev a2)
>> 00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
>> 00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
>> 00:0a.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
>> 00:0b.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
>> 00:0c.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
>> 00:0d.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
>> 00:0e.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
>> 00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a3)
>> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8  
>> [Athlon64/Opteron] HyperTransport Technology Configuration
>> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8  
>> [Athlon64/Opteron] Address Map
>> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8  
>> [Athlon64/Opteron] DRAM Controller
>> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8  
>> [Athlon64/Opteron] Miscellaneous Control
>> 01:06.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI]
>> 05:00.0 PCI bridge: NEC Corporation uPD720400 PCI Express - PCI/PCI-X  
>> Bridge (rev 07)
>> 05:00.1 PCI bridge: NEC Corporation uPD720400 PCI Express - PCI/PCI-X  
>> Bridge (rev 07)
>> 08:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 4770 [RV740]
>> 08:00.1 Audio device: ATI Technologies Inc RV710/730
>>
>> and for what it's worth I'm curious why my video card shows up as an  
>> audio device.
>>
> 
> I don't know if it will be useful, but can you do, as root,
> lspci -vvv -s 8:00.1
> I assume there will be a kernel driver in use.
> 
> Sound has always confused me.  Let me see if I can get this right this
> time.  Every time I try to explain sound, someone (correctly!) dings me.
> 
> Pulse Audio provides a framework through which applications should do
> audio (microphone/speakers/etc).  Pulse Audio speaks to Alsa.
> 
> Alsa speaks to the driver that actually drives the audio hardware.
> Then there is the driver, itself, which drives the hardware.
> 
> Pulse Audio is supposed to provide a consistent interface to audio.
> 
> Before we had Pulse Audio, applications would speak with alsa
> (or with ESD which also was supposed to provide a consistent interface
> to audio).  I guess an application could also talk to the driver itself,
> but I would hope this to be rare.
> 
> Now, I believe, we have the following:
> Pulse Audio provides the consistent interface.
> Pulse Audio uses Alsa.
> Alsa talks to the hardware driver.
> 
> Applications, that think they are talking directly to Alsa can actually
> be talking to Pulse Audio through a plugin,
> rpm -q -i alsa-plugins-pulseaudio
> 
> Applications that think they are talking directly to Esound can actually
> be talking to Pulse Audio through a plugin,
> rpm -q -i pulseaudio-esound-compat
> 
> I believe, Applications should, over time, be changed to talk to Pulse
> Audio.
> 
> Why this background?  We need to follow the audio path.
> 
> We need to see what Pulse Audio thinks.
> 
> We need to see what Alsa thinks.
> 
> We need to see if a driver has the hardware.
> 
> Pulse Audio can mute the audio.
> Alsa should be "controlled" by Pulse Audio, but is still best to make
> sure Alsa isn't muting the audio.
> I assume we have a kernel driver for the audio hardware.
> 
> Pulse Audio might have sound muted.
>>From xterm (gnome-terminal) please run pavucontrol,
> or from the menu, Applications,
> Sound & Video, please start Pulse Volume Control,
> Please check the "Output Devices" tab to see if you have volume and make
> sure it is not muted.
> pavucontrol is provided by rpm -q -i pavucontrol,
> yum install pavucontrol if necessary.
> You may have more than one Port...I have two ports.
> I have "Analog Output" and I have "Analog Headphones".
> Please make sure you have volume and it is not muted on all ports.
> By the way, if you don't mind me asking, what ports do you have?
> 
> If Pulse Audio is happy, please see what Alsa thinks.
> rpm -q -i alsa-utils  (yum install alsa-utils if necessary)
> 
>>From xterm (gnome-terminal) please run: alsamixer
> provided by alsa-utils
> 
> Controls for alsamixer can be found in the upper right corner.
> "F1" for help, "F3" for Playback, "F4" for Capture, Esc for exit.
> 
> I'd be curious to know what alsamixer shows you.
> For me, I only have a "[Playback]" Master for audio output and a
> "[Capture]" Capture for audio input.  I believe this is my case because
> I am going through Pulse Audio and having applications that think they
> are talking to Alsa really go through the alsa-plugins-pulseaudio.
> 
> Please make sure the "[Playback]" is not muted and has a reasonable volume.
> 
> Some people, I believe, do not use Pulse Audio, and do not have the
> alsa-plugins-pulseaudio.  Their applications go directly to Alsa.
> alsamixer will show a number of things for "[Playback]".
> Other people, with greater knowledge, can counsel whether or not this is
> a good idea.  I believe, personally, it is wiser to use Pulse Audio.
> 
> In Summary, what to check:
> 1) Do we have a kernel driver (lspci -vvv ...)
> 2) what does Pulse Audio think the volume is and is it muted?
> 3) what does Alsa think the volume is and is it muted?
> 
> There is one other question, I didn't think to ask.
> What application are you trying to use for the audio and what is its
> audio configuration?  I.e., does it think it is talking to Pulse Audio
> or Alsa or ESD?
> I assume no application makes any audio sound so this question may not
> be important.
> 

I started looking on my Fedora box, and discovered another possibility.

There is an older sound system, called OSS, which, I believe, should no
longer be used.

I found, in /etc/modprobe.d, a file, /etc/modprobe.d/dist-oss.conf,
which has a comment,
"
# OSS Sound Support
# This has been disabled in F11 onwards because it can interfere with the
# PulseAudio sound service (a legacy OSS application can prevent PulseAudio
# applications from playing sound by preventing PulseAudio from (re-)opening
# the sound device). To re-enable support, uncomment the following line:
"

I am wondering if OSS is enabled on your system.

Please look for things related to OSS in
/etc/modprobe.conf (if it exists)
and /etc/modprobe.d
Please make sure the line in /etc/modprobe.d/dist-oss.conf is
commented out.

Please do, lsmod | grep snd
Please make sure there is nothing like snd-pcm-oss or snd-seq-oss
installed.

In my system, when I do lsmod | grep snd, I get:
[email protected]:/etc/modprobe.d <2:28> $ lsmod | grep snd
snd_hda_codec_realtek   284527  1
snd_hda_intel          24200  2
snd_hda_codec          73671  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               6222  1 snd_hda_codec
snd_seq                50941  0
snd_seq_device          5895  1 snd_seq
snd_pcm                76131  2 snd_hda_intel,snd_hda_codec
snd_timer              19234  2 snd_seq,snd_pcm
snd                    60573  12
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore               6198  1 snd
snd_page_alloc          7221  2 snd_hda_intel,snd_pcm

Please also look in /etc/modprobe.conf -or- any file in
/etc/modprobe.d/*.conf
for lines like
options snd cards_limit=8
alias snd-card-0 snd-hda-intel
options snd-hda-intel index=0
alias snd-card-7 snd-usb-audio
options snd-usb-audio index=7
(above are lines I have in /etc/modprobe.d/local.conf)
I believe these lines are hardware dependent.
I'm not sure what lines to expect for a Sound Blaster card.
I'm not sure what created these lines in my /etc/modprobe.d/local.conf

I am curious about any and all lines that are like
alias snd-card-<some number> <driver associated with sound card>
options <driver associated with sound card> index=<some number>
in these files.  One set of those lines should be for the Sound Blaster.
I have not researched what <some number> should be in these entries.
I assume <some number> needs to be unique for each sound card.
-- 
users mailing list
[email protected]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]
  Powered by Linux