2:48 p.m.
Hey all,
I have Fedora 10 and a machine with a (please, no laughing or
snickering) Creative Labs Sound Blaster AWE 64 Value sound card and a
Sigma Designs RealMagic Hollywood Plus DVD decoder card. While the
computer loads the ALSA drivers needed for both cards, the sound
controls in GNOME only display the Hollywood+ controls, and nothing is
available for the AWE 64. I have used the AWE 64 successfully in another
computer before that already had another sound card in it, so I don't
know what the deal is here.
Help. Please?
Peace,
William
5:15 p.m.
William M. Quarles wrote:
I have Fedora 10 and a machine with a (please, no laughing or
snickering) Creative Labs Sound Blaster AWE 64 Value sound card and a
Sigma Designs RealMagic Hollywood Plus DVD decoder card. While the
computer loads the ALSA drivers needed for both cards,
As evidenced by ?
I'm not sure which mod the awe needs, but check lsmod |grep snd
Maybe fpaste.org your alsa-info results for others to check
the sound
controls in GNOME only display the Hollywood+ controls, and nothing is
available for the AWE 64.
In gnome-volume-control I see Device entries for eg:
CA0106 alsa
Nvidia nforce2 alsa
mixer oss
playback CA PA
playback NF PA
capture CA PA
capture NF PA
capture-monitor CA PA
capture-monitor NF PA
and I need to change the device to control the appropriate card.
Did you try alsamxixer, and alsaunmute ?
DaveT.
9:08 p.m.
David Timms wrote:
William M. Quarles wrote:
> I have Fedora 10 and a machine with a (please, no laughing or
> snickering) Creative Labs Sound Blaster AWE 64 Value sound card and a
> Sigma Designs RealMagic Hollywood Plus DVD decoder card. While the
> computer loads the ALSA drivers needed for both cards,
As evidenced by ?
Uh, as evidenced by lsmod? I'm not a newbie if that's what you're implying.
[root@quarlewm ~]# lsmod
Module Size Used by
udf 69388 0
fuse 49436 2
bridge 43796 0
stp 6148 1 bridge
bnep 14848 2
sco 12932 2
l2cap 21504 3 bnep
bluetooth 48608 5 bnep,sco,l2cap
sunrpc 156052 3
ip6t_REJECT 7296 2
nf_conntrack_ipv6 15864 2
ip6table_filter 6400 1
ip6_tables 14736 1 ip6table_filter
ipv6 230516 36 ip6t_REJECT,nf_conntrack_ipv6
dm_multipath 17164 0
uinput 10624 0
ppdev 10500 0
snd_sbawe 31180 0
snd_opl3_lib 12800 1 snd_sbawe
adv717x 11684 1
snd_hwdep 10500 1 snd_opl3_lib
snd_sb16_dsp 11648 1 snd_sbawe
snd_sb_common 18432 2 snd_sbawe,snd_sb16_dsp
snd_mpu401_uart 10368 1 snd_sbawe
em8300 62380 1
snd_seq_dummy 6660 0
snd_rawmidi 22528 1 snd_mpu401_uart
firewire_ohci 22532 0
snd_seq_oss 30364 0
firewire_core 35616 1 firewire_ohci
snd_seq_midi_event 9600 1 snd_seq_oss
crc_itu_t 5760 2 udf,firewire_core
snd_seq 48576 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10124 6
snd_sbawe,snd_opl3_lib,snd_seq_dummy,snd_rawmidi,snd_seq_oss,snd_seq
radeon 237912 2
snd_pcm_oss 42496 0
snd_mixer_oss 16896 1 snd_pcm_oss
snd_pcm 65924 4 snd_sbawe,snd_sb16_dsp,em8300,snd_pcm_oss
ns558 8320 0
drm 158260 3 radeon
floppy 51988 0
ata_generic 8452 0
snd_timer 22024 3 snd_opl3_lib,snd_seq,snd_pcm
gameport 13452 2 ns558
pata_acpi 7680 0
snd_page_alloc 11016 1 snd_pcm
i2c_algo_bit 8836 2 em8300,radeon
3c59x 40232 0
pcspkr 6272 0
parport_pc 25620 0
mii 8192 1 3c59x
snd 50616 18
snd_sbawe,snd_opl3_lib,snd_hwdep,snd_sb16_dsp,snd_sb_common,snd_mpu401_uart,em8300,snd_seq_dummy,snd_rawmidi,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9416 2 em8300,snd
i2c_viapro 10772 0
i2c_core 21396 6
adv717x,em8300,radeon,drm,i2c_algo_bit,i2c_viapro
pata_via 12036 0
parport 31956 2 ppdev,parport_pc
pata_pdc2027x 11012 3
I'm not sure which mod the awe needs, but check lsmod |grep snd
Maybe fpaste.org your alsa-info results for others to check
The AWE 64 cards use snd-sbawe module, which can be easily checked on
http://www.alsa-project.org/'s sound card matrix.
I have no idea what you mean by fpaste.org, but alsa-info does seem like
a good idea in this case; however it also unfortunately seems a little
useless since it reveals a great deal of output, but I can't copy and
paste any of it into this post, and the final message upon exiting the
program says:
Your ALSA information is located at
Please inform the person helping you.
So, uh, LOCATED AT big blank? Gee, thanks, stupid diagnostic program.
> the sound controls in GNOME only display the Hollywood+ controls,
and
> nothing is available for the AWE 64.
In gnome-volume-control I see Device entries for eg:
CA0106 alsa
Nvidia nforce2 alsa
mixer oss
playback CA PA
playback NF PA
capture CA PA
capture NF PA
capture-monitor CA PA
capture-monitor NF PA
and I need to change the device to control the appropriate card.
Did you try alsamxixer, and alsaunmute ?
DaveT.
I am aware that you need to change the device to the appropriate card in
the GNOME mixer. The Hollywood+ card is the only option available.
[root@quarlewm ~]# alsamixer
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect:
Connection refused
alsamixer: function snd_ctl_open failed for default: Connection refused
[root@quarlewm ~]# alsaunmute
Unknown hardware: "SB AWE" "CTL1745" "CTL1745" ""
""
Hardware is initialized using a guess method
/lib/alsa/init/default:17: unable to convert dB value '-20dB' to
internal integer range
/lib/alsa/init/default:23: unable to convert dB value '-20dB' to
internal integer range
/lib/alsa/init/default:62: unable to convert dB value '-20dB' to
internal integer range
/lib/alsa/init/default:84: unable to convert dB value '-20dB' to
internal integer range
/lib/alsa/init/default:105: unable to convert dB value '-20dB' to
internal integer range
/lib/alsa/init/default:143: unable to convert dB value '12dB' to
internal integer range
You're help is appreciated.
Thanks,
William
3:40 a.m.
William M. Quarles wrote:
David Timms wrote:
> William M. Quarles wrote:
>> I have Fedora 10 and a machine with a (please, no laughing or
>> snickering) Creative Labs Sound Blaster AWE 64 Value sound card and a
>> Sigma Designs RealMagic Hollywood Plus DVD decoder card. While the
>> computer loads the ALSA drivers needed for both cards,
> As evidenced by ?
Uh, as evidenced by lsmod? I'm not a newbie if that's what you're
implying.
Yes, but really was it an alsa util you used, lsmod or looking at /proc ?
[root@quarlewm ~]# lsmod
I suggested grep snd so that we would
get sound related modules, not the
whole thing. It's just faster to look at the reduced version. I can
however see all the modules seem to be linked up.
> I'm not sure which mod the awe needs, but check lsmod |grep
snd
> Maybe fpaste.org your alsa-info results for others to check
The AWE 64 cards use snd-sbawe module, which can be easily checked on
http://www.alsa-project.org/'s sound card matrix.
Given that your asking for
help, I probably won't be going searching
sites to try to find appropriate info; I'll ask you to, or you could
offer that info, and hence we know what you've tried.
I have no idea what you mean by fpaste.org
One of many
paste-bin web sites. These allow anonymous (you do need to
supply an email address that is used to limit bad usage of the site)
text upload site. It's really just a holder for bits of text from logs /
compiles etc that would unnecessarily fill up mailing list user's email
boxes.
http://fpaste.org is targeted towards Fedora users.
, but alsa-info does seem like
a good idea in this case; however it also unfortunately seems a little
useless since it reveals a great deal of output, but I can't copy and
paste any of it into this post
That's the point of the paste-bin, we don't
really want large log files
in our email boxes.
, and the final message upon exiting the program says:
Your ALSA information is located at
Please inform the person helping you.
So, uh, LOCATED AT big blank?
Yeah, that didn't work out well:
Your ALSA information is located at
http://www.alsa-project.org/db/?f=23db04e4a7aeaa23357d00481f38b86638e90b21
Please inform the person helping you.
$
Well it normally pastes to the alsa project pastebin, and gives the link
(which worked for me). I'm guessing your internet/web access is normal,
so perhaps this is further indication of something going wrong during
alsa calls ?
Gee, diagnostic program.
has a --help capability:
alsa-info --help
shows a debug option, that stores the large alsa log on your local
disk so that you could manually put it on a pastebin, and post the link
back here.
>> the sound controls in GNOME only display the Hollywood+
controls, and
>> nothing is available for the AWE 64.
Bugger.
[root@quarlewm ~]# alsamixer
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect:
Connection refused
If pulseaudio wasn't running, I think you would get a
different error like:
$ alsamixer
E: socket-client.c: socket(): Address family not supported by protocol
alsamixer: function snd_ctl_open failed for default: Connection
refused
[root@quarlewm ~]# alsaunmute
Unknown hardware: "SB AWE" "CTL1745" "CTL1745" ""
""
Hardware is initialized using a guess method
/lib/alsa/init/default:17: unable to convert dB value '-20dB' to
internal integer range
Mine:
$ alsaunmute
Unknown hardware: "CA0106" "" "" "" ""
Hardware is initialized using a guess method
$
I guess aplay wont work either ?
alsamixer -c0 ?
ps aux|grep -E 'pad|pav|pul'
I'm assuming playback is a problem as well, not just mixer control ?
Do you have the option to try without the decoder card installed, for a
giggle ?
DaveT.
9:20 p.m.
David Timms wrote:
William M. Quarles wrote:
> David Timms wrote:
>> William M. Quarles wrote:
>>> I have Fedora 10 and a machine with a (please, no laughing or
>>> snickering) Creative Labs Sound Blaster AWE 64 Value sound card and a
>>> Sigma Designs RealMagic Hollywood Plus DVD decoder card. While the
>>> computer loads the ALSA drivers needed for both cards,
>> As evidenced by ?
>
> Uh, as evidenced by lsmod? I'm not a newbie if that's what you're
implying.
Yes, but really was it an alsa util you used, lsmod or looking at /proc ?
lsmod and /proc were used, and they were used before I wrote the
original message, thank you.
> [root@quarlewm ~]# lsmod
I suggested grep snd so that we would get sound related modules, not the
whole thing. It's just faster to look at the reduced version. I can
however see all the modules seem to be linked up.
I know you did make that suggestion. I had different purposes in mind,
as it seems you inadvertently stumbled upon them.
>> I'm not sure which mod the awe needs, but check lsmod
|grep snd
>> Maybe fpaste.org your alsa-info results for others to check
>
> The AWE 64 cards use snd-sbawe module, which can be easily checked on
> http://www.alsa-project.org/'s sound card matrix.
Given that your asking for help, I probably won't be going searching
sites to try to find appropriate info; I'll ask you to, or you could
offer that info, and hence we know what you've tried.
> I have no idea what you mean by fpaste.org
One of many paste-bin web sites. These allow anonymous (you do need to
supply an email address that is used to limit bad usage of the site)
text upload site. It's really just a holder for bits of text from logs /
compiles etc that would unnecessarily fill up mailing list user's email
boxes.
http://fpaste.org is targeted towards Fedora users.
Great, guess I'm a old fogey not up on the current trends. Then again, I
did stop using GNU/Linux for about three or four years up until recently.
I uploaded my alsa-info.txt to <http://fpaste.org/paste/11316>;.
>, but alsa-info does seem like
> a good idea in this case; however it also unfortunately seems a little
> useless since it reveals a great deal of output, but I can't copy and
> paste any of it into this post
That's the point of the paste-bin, we don't really want large log files
in our email boxes.
This stuff should all be in newsgroups anyway, that's why I am very glad
to have found out about GMANE back around when Fedora Core 1 came out.
> , and the final message upon exiting the program says:
>
> Your ALSA information is located at
> Please inform the person helping you.
>
> So, uh, LOCATED AT big blank?
Yeah, that didn't work out well:
Your ALSA information is located at
http://www.alsa-project.org/db/?f=23db04e4a7aeaa23357d00481f38b86638e90b21
Please inform the person helping you.
$
Well it normally pastes to the alsa project pastebin, and gives the link
(which worked for me). I'm guessing your internet/web access is normal,
so perhaps this is further indication of something going wrong during
alsa calls ?
Define normal. I'm using a docked Win XP Pro laptop right now as a router.
> Gee, diagnostic program.
has a --help capability:
alsa-info --help
shows a debug option, that stores the large alsa log on your local
disk so that you could manually put it on a pastebin, and post the link
back here.
I know that it has a help function, but I did not know that the debug
option left the log file that we were looking for behind on the hard
drive. It would make more sense to me if they did both a local dump and
an upload simultaneously.
However, since you suggested, I tried the debug option. The program left
the file behind, but not where the help function said that it would
leave it behind, so basically there is a bug in the debug function, or a
bug in the help function. depending on your point of view I suppose.
Curiosity, alsa-info is offering to update itself, which I didn't do in
hear of breaking any Fedora customizations. Did you do the update? Would
you suggest that I do the update?
>>> the sound controls in GNOME only display the Hollywood+
controls, and
>>> nothing is available for the AWE 64.
Bugger.
You betcha.
> [root@quarlewm ~]# alsamixer
> ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect:
> Connection refused
If pulseaudio wasn't running, I think you would get a different error like:
$ alsamixer
E: socket-client.c: socket(): Address family not supported by protocol
> alsamixer: function snd_ctl_open failed for default: Connection refused
alsamixer decided to work today. ;-) Or maybe it was Pulseaudio, which
is new to me. Same stuff as in the GNOME mixer, unfortuntely.
> [root@quarlewm ~]# alsaunmute
> Unknown hardware: "SB AWE" "CTL1745" "CTL1745"
"" ""
> Hardware is initialized using a guess method
> /lib/alsa/init/default:17: unable to convert dB value '-20dB' to
> internal integer range
Mine:
$ alsaunmute
Unknown hardware: "CA0106" "" "" "" ""
Hardware is initialized using a guess method
$
alsaunmute behaved the same as yesterday, pretty much.
I guess aplay wont work either ?
It doesn't seem to... then again I don't have a file on hand for it to play.
alsamixer -c0 ?
Wow, that's the spirit! So how do I get the GNOME sound stuff to
recognize it?
ps aux|grep -E 'pad|pav|pul'
I'm assuming playback is a problem as well, not just mixer control ?
Well, now that alsamixer is working, yes, I am getting sound. Do you
know how to fix the GNOME mixer issues?
Do you have the option to try without the decoder card installed, for
a
giggle ?
DaveT.
Yeah, I can give that a shot, I'll get back to you on it. But please,
give me a reply to what I have written here already before I do.
Thanks,
William
9:52 p.m.
William M. Quarles wrote:
David Timms wrote:
<snip>
> I'm assuming playback is a problem as well, not just mixer
control ?
Well, now that alsamixer is working, yes, I am getting sound. Do you
know how to fix the GNOME mixer issues?
OK, unfortunately, the sound that I am getting from XMMS playing MP3
files is intermittently distorted, and is somehow actually coming from
the decoder card instead of the sound card, then getting passed through
to the sound card via the internal patch cable that I have installed. I
checked this by using alsamixer to vary the volume on the sound card's
CD input, and also by varying the volume on the decoder card.
> Do you have the option to try without the decoder card installed,
for a
> giggle ?
>
> DaveT.
>
Yeah, I can give that a shot, I'll get back to you on it. But please,
give me a reply to what I have written here already before I do.
Thanks,
William
Haven't gotten around to that yet still, I'll probably try it tomorrow.
8:37 p.m.
William M. Quarles wrote:
William M. Quarles wrote:
> David Timms wrote:
<snip>
>> I'm assuming playback is a problem as well, not just mixer control ?
>
> Well, now that alsamixer is working, yes, I am getting sound. Do you
> know how to fix the GNOME mixer issues?
>
OK, unfortunately, the sound that I am getting from XMMS playing MP3
files is intermittently distorted, and is somehow actually coming from
the decoder card instead of the sound card, then getting passed through
to the sound card via the internal patch cable that I have installed. I
checked this by using alsamixer to vary the volume on the sound card's
CD input, and also by varying the volume on the decoder card.
alsamixer -c0 works intermittently, still no help with the GNOME mixer.
Very annoying.
>> Do you have the option to try without the decoder card
installed, for a
>> giggle ?
>>
>> DaveT.
>>
>
> Yeah, I can give that a shot, I'll get back to you on it. But please,
> give me a reply to what I have written here already before I do.
>
> Thanks,
> William
>
Haven't gotten around to that yet still, I'll probably try it tomorrow.
Well, I got the PC to successfully boot once without the DVD decoder
card, which did not help any of the problems. Then it locked up while
attempting to start X the subsequent 10 times that I tried to boot. And
once again, the computer is booting successfully, but I didn't change
anything to make it start booting properly again. Once I got it going,
alsamixer -c0 decided to work again, but I still can't get the card to
show up in any GUI program in GNOME except for alsamixergui -c0, and
that locks up when I attempt to make adjustments.
David, or Fernando, or ANYBODY else out there, do you have any idea why
this isn't working for me? Something smells funny about Pulseaudio, but
I don't know enough about it to be able to say why.
Peace,
William
4949
days inactive
4957
days old
6 comments
2 participants
participants (2)
-
Development discussions related to Fedora -
William M. Quarles