FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 07-06-2010, 02:11 AM
JD
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

On 07/05/2010 06:45 PM, Dave Stevens wrote:
> The subject line pretty much says it. It's quite frustrating to be unable to
> get this working. I am, open to suggestions. The same system with the thingy
> plugged into the same little hole(in the back of a Sound Blaster Ensoniq)
> makes no sound in the Fedoras but good sound in Omega. Is there some config
> file I can adduce as a hint? I have no idea where to look. pulseaudio shows in
> top.
>
> Dave
Does your audio device show up in
/var/log/boo.log or in /var/log/messages?

Can you post output of lspci?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-06-2010, 02:26 AM
Dave Stevens
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

Quoting JD <jd1008@gmail.com>:

> On 07/05/2010 06:45 PM, Dave Stevens wrote:
>> The subject line pretty much says it. It's quite frustrating to be unable to
>> get this working. I am, open to suggestions. The same system with the thingy
>> plugged into the same little hole(in the back of a Sound Blaster Ensoniq)
>> makes no sound in the Fedoras but good sound in Omega. Is there some config
>> file I can adduce as a hint? I have no idea where to look.
>> pulseaudio shows in
>> top.
>>
>> Dave
> Does your audio device show up in
> /var/log/boo.log or in /var/log/messages?

not in boot but in messages, yes like this:

Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c:
snd_pcm_avail() returned a value that is exceptionally large:
18446744073709522368 bytes (418293516244 ms).
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: Most likely
this is a bug in the ALSA driver 'snd_ens1370'. Please report this
issue to the ALSA developers.
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: snd_pcm_dump():
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: Hardware PCM
card 0 'Ensoniq AudioPCI' device 0 subdevice 0
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: Its setup is:
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: stream
: CAPTURE
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: access
: MMAP_INTERLEAVED
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: format
: S16_LE
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: subformat : STD
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: channels : 2
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: rate : 44100
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: exact rate
: 44100 (1411200/32)
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: msbits : 16
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: buffer_size : 16384
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: period_size : 16384
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: period_time
: 371519
:

in /var/log/messages and about another 20 lines like that, should I
report as suggested in line two above?

>
> 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.

Dave

>
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>



--
"It is no measure of health to be well adjusted to a profoundly sick society."
Krishnamurti

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-06-2010, 03:23 AM
Rick Sewill
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

On 07/05/2010 09:26 PM, Dave Stevens wrote:
> Quoting JD <jd1008@gmail.com>:

>> 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.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-06-2010, 06:35 AM
Rick Sewill
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

On 07/05/2010 10:23 PM, Rick Sewill wrote:
> On 07/05/2010 09:26 PM, Dave Stevens wrote:
>> Quoting JD <jd1008@gmail.com>:
>
>>> 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:
rsewill@rsewill:/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
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-06-2010, 03:38 PM
Bill Davidsen
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

Rick Sewill wrote:
> On 07/05/2010 10:23 PM, Rick Sewill wrote:
.
> 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.
>
I think you have this totally backward. There are many applications which use
the /dev/dsp* devices, and which will produce no sound unless they are present.
In fact, I think the majority of older hardware does not have support for sound
other than oss. As I look at my newest TV card it has stuff in /dev/dvb, while
the other 4-5 cards which have been happily in use do not.

To test (as root):
modprobe -v snd-pcm-oss
{test applications for sound here}

A lot of people have functional old hardware they can't replace, for financial
or technical reasons. That's why there is oss support, to support the hardware
which needs it.

--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-07-2010, 12:28 AM
JD
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

On 07/06/2010 04:57 PM, Dave Stevens wrote:
> snip!!
>
>>>> support the hardware which needs it.
>>> [root@davehost dave]# lsmod | grep ens
>>> snd_ens1370 20973 2
>>> gameport 8936 1 snd_ens1370
>>> snd_rawmidi 19917 1 snd_ens1370
>>> snd_pcm 76131 3 snd_hda_intel,snd_hda_codec,snd_ens1370
>>> snd 60573 13
>>> snd_hda_intel,snd_hda_codec,snd_hwdep,snd_ens1370, snd_rawmidi,snd_seq,snd
>>> _seq_device,snd_pcm,snd_timer snd_page_alloc 7221 3
>>> snd_hda_intel,snd_ens1370,snd_pcm
>> So still no sound, I take it.
>> When you open the mixer like gst-mixer or gmixer,
>> does it show anything muted or volume all the way down?
> no, gst-mixer shows normal mid-level volume and I can't see any indication of
> muting. gmixer seems to not be installed. But muting is exactly how it
> behaves, when I try to play a tune the programs (amarok or kplayer) go through
> the motions but no audio.
>
> Dave
And yet, windows has no problems playing audio, correct?
If this is so, I think it is a bug in the ens1370 driver.
The strange thing is, there is a dearth of bugs filed against
it.


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-07-2010, 01:24 PM
Rick Sewill
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/2010 10:38 AM, Bill Davidsen wrote:
> Rick Sewill wrote:
>> On 07/05/2010 10:23 PM, Rick Sewill wrote:
> .
>> 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.
>>
> I think you have this totally backward. There are many applications which use
> the /dev/dsp* devices, and which will produce no sound unless they are present.
> In fact, I think the majority of older hardware does not have support for sound
> other than oss. As I look at my newest TV card it has stuff in /dev/dvb, while
> the other 4-5 cards which have been happily in use do not.
>
> To test (as root):
> modprobe -v snd-pcm-oss
> {test applications for sound here}
>
> A lot of people have functional old hardware they can't replace, for financial
> or technical reasons. That's why there is oss support, to support the hardware
> which needs it.
>

This is something I didn't know. As I said, audio still confuses me.

Our goal should be to help the original poster.

In this regard, this new information raises a number of questions.

I am hoping someone will say there is a wiki or web page that answers
these questions (and questions I didn't think of).

The questions, I hope, which might be of use to the original poster are
as follows:
1) for what hardware should one use OSS as opposed to Pulse Audio.
I did a quick internet search, but failed to find such a list.
I am hoping others can help.

This question is to help the original poster decide if they should
switch to OSS and see if it works.

2) How does one tell if OSS is being used?
I assume, if I do lsmod | grep oss, I will see if the OSS modules
are being loaded.

3) How does one switch from Pulse Audio to OSS?
I assume one needs to edit files in /etc/modules.d/*.conf
or /etc/modules.conf.
Files to be edited might include dist-oss.conf and blacklist.conf
and others? Am I right?

Are there other files one needs to edit?
Are there any rpms one needs to install?
Are there any rpms one needs to remove?

Are there any application configuration changes one needs to make?
I assume applications can be configured to use the OSS api, as well
as the ALSA api and/or Pulse Audio API.

4) How does one switch from OSS back to Pulse Audio?
Is the answer to this the inverse of the answer to question 3?
I.e., edit files /etc/modules.d/*.conf or /etc/modules.conf
Install certain rpms?
Remove certain rpms?

5) is there a web page that describes the tools one uses when using OSS?
Are these the tools: http://www.opensound.com/ossapps.html#mixer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkw0f/IACgkQyc8Kn0p/AZRCogCgqMIl3yxUUveNk+MNcnvhq0um
sRkAoIsCgZcczEiEWmrk2gY+ZxljtbJf
=Uu8V
-----END PGP SIGNATURE-----
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-07-2010, 02:08 PM
Rick Sewill
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On a different track, again to help the original poster.

In other messages on this thread, it sounded like the original poster
was using a driver, ens1370, which some people thought was suspect.

Is there a tool that can talk directly to the driver, bypassing Alsa,
OSS, Pulse Audio, everything, so one can see if the driver can generate
sound through the card?

We will probably need to know all the steps to use such a tool?

For example, wouldn't we need to stop certain services or applications
that might have exclusive use of the driver/device/card?

==========

Another question, in regard to this ens1370 driver, are there any
/var/log/messages regarding this driver.

==========

Another question, should the original poster try OSS?

- From the /var/log/messages in another message from the original poster,
"Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c:
snd_pcm_avail() returned a value that is exceptionally large:
18446744073709522368 bytes (418293516244 ms).
Jul 4 14:55:03 davehost pulseaudio[2120]: alsa-util.c: Most likely
this is a bug in the ALSA driver 'snd_ens1370'. Please report this
issue to the ALSA developers."

Is it possible OSS would use a different driver and have more success
with that driver? Is the ens1370 driver an ALSA driver?

==========

Another question regarding what is in the /var/log/messages please?
Are there many Pulse Audio messages just prior to this message that says
"value that is exceptionally large?"

I ask, because, I tried searching Bugzilla for similar bugs.
Some bug reports indicate sound continued to work, but there was
stuttering. Others said sound stopped working after a few minutes. One
said sound did not work.

Following said sound stopped working after a yum update:
https://bugzilla.redhat.com/show_bug.cgi?id=572322

Following said "log of alsa-util's messages about snd_hda_intel
malfunction" and "When I try to obtain Surround 4.0 sound instead of
classic Stereo sound from a soundcard capable of Surround 5.1 I see in
/var/log/messages"
https://bugzilla.redhat.com/show_bug.cgi?id=537714
This bug report brings up a question about the Sound Blaster card,
(again I am showing my ignorance), does the Sound Blaster Card support
multiple variations in sound (Surround sound, classic stereo, etc)?
Do any of these other variations in sound work?

Finally, is the Pulse Audio server crashing? I found the following bug
report, which said pulseaudio is crashing?
https://bugzilla.redhat.com/show_bug.cgi?id=530650

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkw0ikQACgkQyc8Kn0p/AZRb8ACfWi9Ky/zE8Wbfgtl6uZPD4pqd
I2EAoJVwUAL7JjzBF2RZX/Xovp0udAfw
=nNgw
-----END PGP SIGNATURE-----
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-09-2010, 07:51 PM
Bill Davidsen
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

Dave Stevens wrote:
> On Tuesday, July 06, 2010 08:38:38 am Bill Davidsen wrote:
>> Rick Sewill wrote:
>>> On 07/05/2010 10:23 PM, Rick Sewill wrote:
>> .
>>
>>> 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.
>> I think you have this totally backward. There are many applications which
>> use the /dev/dsp* devices, and which will produce no sound unless they are
>> present. In fact, I think the majority of older hardware does not have
>> support for sound other than oss. As I look at my newest TV card it has
>> stuff in /dev/dvb, while the other 4-5 cards which have been happily in
>> use do not.
>>
>> To test (as root):
>> modprobe -v snd-pcm-oss
>> {test applications for sound here}
>
> [root@davehost dave]# modprobe -v snd-pcm-oss
> insmod /lib/modules/2.6.33.5-124.fc13.x86_64/kernel/sound/core/oss/snd-mixer-
> oss.ko
> insmod /lib/modules/2.6.33.5-124.fc13.x86_64/kernel/sound/core/oss/snd-pcm-
> oss.ko
> [root@davehost dave]#
>
Yes, that should get the sound working if it's going to work at all. If adding
OSS will provide the dsp needed, the modules will be loaded.

As you note, the default is not to load the oss modules, starting with fc11,
which is where the problem seems to have started. So if sound suddenly started
working on a machine (and that has happened for me) the solution would be clear.

> also
> [root@davehost core]# pwd
> /lib/modules/2.6.33.5-124.fc13.x86_64/kernel/sound/core
> [root@davehost core]# ls
> oss snd-hrtimer.ko snd.ko snd-pcm.ko snd-timer.ko
> seq snd-hwdep.ko snd-page-alloc.ko snd-rawmidi.ko
> [root@davehost core]#
>
> dist-oss.conf has the module load line commented out,
>
> and
>
> [root@davehost modprobe.d]# cat dist-alsa.conf
> # ALSA Sound Support
> #
> # We want to ensure that snd-seq is always loaded for those who want to use
> # the sequencer interface, but we can't do this automatically through udev
> # at the moment...so we have this rule (just for the moment).
> #
> # Remove the following line if you don't want the sequencer.
>
> install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-
> seq
> [root@davehost modprobe.d]#
>
>
>
>
>
>
>> A lot of people have functional old hardware they can't replace, for
>> financial or technical reasons. That's why there is oss support, to
>> support the hardware which needs it.
>
> [root@davehost dave]# lsmod | grep ens
> snd_ens1370 20973 2
> gameport 8936 1 snd_ens1370
> snd_rawmidi 19917 1 snd_ens1370
> snd_pcm 76131 3 snd_hda_intel,snd_hda_codec,snd_ens1370
> snd 60573 13
> snd_hda_intel,snd_hda_codec,snd_hwdep,snd_ens1370, snd_rawmidi,snd_seq,snd_seq_device,snd_pcm,snd_tim er
> snd_page_alloc 7221 3 snd_hda_intel,snd_ens1370,snd_pcm


--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-09-2010, 08:03 PM
Bill Davidsen
 
Default no sound on F11, F12 and now F13 but sound on Omega 12 live??? wtf??

Rick Sewill wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/06/2010 10:38 AM, Bill Davidsen wrote:
>> Rick Sewill wrote:
>>> On 07/05/2010 10:23 PM, Rick Sewill wrote:
>> .
>>> 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.
>>>
>> I think you have this totally backward. There are many applications which use
>> the /dev/dsp* devices, and which will produce no sound unless they are present.
>> In fact, I think the majority of older hardware does not have support for sound
>> other than oss. As I look at my newest TV card it has stuff in /dev/dvb, while
>> the other 4-5 cards which have been happily in use do not.
>>
>> To test (as root):
>> modprobe -v snd-pcm-oss
>> {test applications for sound here}
>>
>> A lot of people have functional old hardware they can't replace, for financial
>> or technical reasons. That's why there is oss support, to support the hardware
>> which needs it.
>>
>
> This is something I didn't know. As I said, audio still confuses me.
>
> Our goal should be to help the original poster.
>
> In this regard, this new information raises a number of questions.
>
> I am hoping someone will say there is a wiki or web page that answers
> these questions (and questions I didn't think of).
>
> The questions, I hope, which might be of use to the original poster are
> as follows:
> 1) for what hardware should one use OSS as opposed to Pulse Audio.
> I did a quick internet search, but failed to find such a list.
> I am hoping others can help.
>
> This question is to help the original poster decide if they should
> switch to OSS and see if it works.
>
Since the manual load is a one time test, the modules can be removed if they
don't help, with rmmod or the handy reboot command, or any other means you like
for reboot.

> 2) How does one tell if OSS is being used?
> I assume, if I do lsmod | grep oss, I will see if the OSS modules
> are being loaded.
>
Correct. Telling if it would be used if present is harder, I just load oss and
see if things start to work.

> 3) How does one switch from Pulse Audio to OSS?
> I assume one needs to edit files in /etc/modules.d/*.conf
> or /etc/modules.conf.

I'm going out on a limb here, on systems where enabling oss helped there was no
"switch" because AFAIK the oss modules don't impact the alsa and PA
applications. I see notes that there might be an issue, I can just say that on
three system I have using OSS for old apps, nothing has ever stopped working, so
the term "switch" is probably not an issue in most cases.

> Files to be edited might include dist-oss.conf and blacklist.conf
> and others? Am I right?
>
> Are there other files one needs to edit?
> Are there any rpms one needs to install?
> Are there any rpms one needs to remove?
>
> Are there any application configuration changes one needs to make?
> I assume applications can be configured to use the OSS api, as well
> as the ALSA api and/or Pulse Audio API.
>
> 4) How does one switch from OSS back to Pulse Audio?
> Is the answer to this the inverse of the answer to question 3?
> I.e., edit files /etc/modules.d/*.conf or /etc/modules.conf
> Install certain rpms?
> Remove certain rpms?
>
See above, to get OSS I uncomment the load in modprobe.d, I never touched
anything else, and I have used OSS fairly heavily rather than change software.

> 5) is there a web page that describes the tools one uses when using OSS?
> Are these the tools: http://www.opensound.com/ossapps.html#mixer
>
I have seen no indication that you need such things, or maybe it's because I
load a bunch of mixers, advanced and stupid, and just try one after the other
until I find the one with the right slider (there are usually three useful at most).

Unless you hit problems, regard this as a switch, turn it on and see if you need
tools or techniques, or if it even helps. Don't oversolve the problem.

--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 04:18 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org