Opinions on how to proceed with sound card issues.
Hello list, I have recently obtained a Audigy2 sound card and am having a few issues with it and I need some help/advice. I installed the card and went to packman's site and downloaded the new ALSA for SuSE 8.2. Installed it and tried to configure my sound card. Well it found it as a Audigy and I heard a pop through my speakers indicating that the system was trying to initialize the card. Tried to play a sound with it and all I got was silence. Well I went to opensource.creative.com and got the drivers there. I was able to compile them and after unloading the ALSA stuff out of the kernel, insert the module into the kernel. Well I got sound! On the next time I brought the machine up, I heard silence. Repeated the procedure again and I have sound once more. So I modified the modunes.conf to load just the one I compiled and not the ones that come with ALSA. This did not work. It looks like that I need the ones in ALSA to initialize this card then install the one I compiled. My question is this, Is there a way to put the 2 togeather so that everything will play nicely? Or am I going to have to do this procedure when I want sound? Any help will be appreciated! -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 28 August 2003 03:01 pm, Marshall Heartley wrote:
Hello list,
I have recently obtained a Audigy2 sound card and am having a few issues with it and I need some help/advice. I installed the card and went to packman's site and downloaded the new ALSA for SuSE 8.2. Installed it and tried to configure my sound card. Well it found it as a Audigy and I heard a pop through my speakers indicating that the system was trying to initialize the card. Tried to play a sound with it and all I got was silence. Well I went to opensource.creative.com and got the drivers there. I was able to compile them and after unloading the ALSA stuff out of the kernel, insert the module into the kernel. Well I got sound!
On the next time I brought the machine up, I heard silence. Repeated the procedure again and I have sound once more. So I modified the modunes.conf to load just the one I compiled and not the ones that come with ALSA. This did not work. It looks like that I need the ones in ALSA to initialize this card then install the one I compiled. My question is this, Is there a way to put the 2 togeather so that everything will play nicely? Or am I going to have to do this procedure when I want sound? Any help will be appreciated!
By default the volume levels on system are set to zero. I know it may sound silly but many (including myself) have done the "what's wrong" dance, installed new/various drivers, changed permissions, etc, etc..., only to find out that all the while the volume was set to zero and/or muted (usually just set to zero). I would recommend using gamix (though try kmix - if your using kde first for generic settings). Gamix is almost dizzying in the amount of parameters one can control - especially with the SBLive/Audigy cards. Check such things as anolog vs digital speakers settings and the various different volumes. The amount of options can almost become a problem in and of themsleves, until one figures out what controls what. HTH, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/TkS1iqnGhdjCOJsRAhz8AJ0U4J5pwdOUhOjzF5/CiMeXTP7GhACfeE0h 4PJRj/uk4PZ27Ty6ezDo0vI= =E6kB -----END PGP SIGNATURE-----
By default the volume levels on system are set to zero. I know it may sound silly but many (including myself) have done the "what's wrong" dance, installed new/various drivers, changed permissions, etc, etc..., only to find out that all the while the volume was set to zero and/or muted (usually just set to zero).
I would recommend using gamix (though try kmix - if your using kde first for generic settings). Gamix is almost dizzying in the amount of parameters one can control - especially with the SBLive/Audigy cards. Check such things as anolog vs digital speakers settings and the various different volumes. The amount of options can almost become a problem in and of themsleves, until one figures out what controls what.
Thanks for the suggestion Curtis! Unfortunately this doesn't help. I have tried several different mixer apps but still no sound. When I do the module dance (in my original email) the sound will work. I will happily try the mixers again though to see if magically one of them will gain control over this beast :) -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 28 August 2003 17:43, Marshall Heartley wrote:
By default the volume levels on system are set to zero. I know it may sound silly but many (including myself) have done the "what's wrong" dance, installed new/various drivers, changed permissions, etc, etc..., only to find out that all the while the volume was set to zero and/or muted (usually just set to zero).
I would recommend using gamix (though try kmix - if your using kde first for generic settings). Gamix is almost dizzying in the amount of parameters one can control - especially with the SBLive/Audigy cards. Check such things as anolog vs digital speakers settings and the various different volumes. The amount of options can almost become a problem in and of themsleves, until one figures out what controls what.
Thanks for the suggestion Curtis! Unfortunately this doesn't help. I have tried several different mixer apps but still no sound. When I do the module dance (in my original email) the sound will work. I will happily try the mixers again though to see if magically one of them will gain control over this beast :)
What does the sound/alsa section of your modules.conf say. Mine is as follows: ######################################################################## # # Aliases for OSS # # These aliases will be changed by YaST2 sound configurator. # If you would like to configure OSS drivers by yourself, please # take a look at the files on /usr/src/linux/Documentation/sound. # ######################################################################## alias sound off alias midi snd-synth-emu10k1 and: # Alsa sound support. # Warning: please don't modify comments over aliases 'snd-card-#' alias char-major-116 snd alias char-major-14 off options snd snd_cards_limit=1 snd_major=116 options snd-emu10k1 snd_enable=1 snd_extin=0x0fcf snd_extout=0x1f0f snd_index=0 snd_max_buffer_size=128 snd_max_synth_voices=64 snd_seq_ports=8 #options midi snd-emu10k1 # --- END: Generated by ALSACONF, do not edit. --- # YaST2: sound system dependent part # alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-slot-1 off alias sound-service-1-0 off alias sound-slot-2 off alias sound-service-2-0 off alias sound-slot-3 off alias sound-service-3-0 off # uniq.virtual:Sound Blaster Live! alias snd-card-0 snd-emu10k1 alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss Now mind you that I have been tweaking this for a bit here and there experimenting. The basick part is the "YaST2: sound system dependent part" as well as the: alias char-major-116 snd alias char-major-14 off options snd snd_cards_limit=1 snd_major=116 I say this because of the fact that you mention the "modules dance" that perhaps the modules that should be loaded and initialized during the boot process are. Another thing to consider is sometimes during certain upgrades (such as KDE, alsa, etc) the some of the user temp files can cause problems. If worse comes to worse you can also delete the unique hardware keys (in /var/admin/hardware IIRC) and reconfig the card again. But take a look at the modules.conf file and post any of the sound related sections. HTH, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/Tre6iqnGhdjCOJsRAop6AJsFWpkQsVeWROacxinNpJzfk8mAzACfaFjL VRHxXvRo8tBXk5gJ/uvlTfc= =Yse6 -----END PGP SIGNATURE-----
<snip>
What does the sound/alsa section of your modules.conf say. Mine is as follows: <snip>
Curtis, I went with the suggestion that Charles posted on the group. I compiled my own ALSA and it seemed to get me going. I appreciate the assistance! -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
On Thu, 28 Aug 2003 16:01:35 -0400
Marshall Heartley
Or am I going to have to do this procedure when I want sound? Any help will be appreciated!
(1) Download the ALSA sources from here: http://www.alsa-project.org/index-ok.php3 (2) Leave the previous drivers package installed so you will get the init script and compile the drivers by doing: ./configure --with-cards=emu10k1 --with-sequencer=yes make make install (3) Compile alsa-libs, alsa-oss-compat-lib and alsa-utils (you don't need alsa-tools). The procedure is the same: ./configure --prefix=/usr --sysconfdir=/etc make make install and hopefully you are using checkinstall. You can turn it into an rpm package by doing: checkinstall Don't forget to run ldconfig (4) Now run the alsaconf from the utils directory of the alsa driver source by doing: ./alsaconf you can copy it to /usr/bin or /usr/local/bin if you want to (5) Now run rcalsasound restart (6) Run alsamixer and unmute the channels you are going to use and set them to reasonable volumes. (7) Now try it out. If you still have problems, recompile the driver but use: ./configure --with-cards=emu10k1 --with-sequencer=yes --with-debug=full and send the output in /var/log/messages to the list. Charles -- Fatal Error: Found [MS-Windows] System -> Repartitioning Disk for Linux... (By cbbrown@io.org, Christopher Browne)
On Thu, 28 Aug 2003 21:04:14 -0400
Charles Philip Chan
(2) Leave the previous drivers package installed so you will get the init script and compile the drivers by doing:
I forgot to add, after installing the driver you should run: depmod -a
(7) Now try it out. If you still have problems, recompile the driver but use:
If everything works don't forget to editor your runlevels to make sure the drivers are loaded at boot time. Charles -- "It's God. No, not Richard Stallman, or Linus Torvalds, but God." (By Matt Welsh)
(1) Download the ALSA sources from here:
http://www.alsa-project.org/index-ok.php3
(2) Leave the previous drivers package installed so you will get the init script and compile the drivers by doing:
./configure --with-cards=emu10k1 --with-sequencer=yes make make install
(3) Compile alsa-libs, alsa-oss-compat-lib and alsa-utils (you don't need alsa-tools). The procedure is the same:
./configure --prefix=/usr --sysconfdir=/etc make make install
and hopefully you are using checkinstall. You can turn it into an rpm package by doing:
checkinstall
Don't forget to run ldconfig
(4) Now run the alsaconf from the utils directory of the alsa driver source by doing:
./alsaconf
you can copy it to /usr/bin or /usr/local/bin if you want to
(5) Now run
rcalsasound restart
(6) Run alsamixer and unmute the channels you are going to use and set them to reasonable volumes.
(7) Now try it out. If you still have problems, recompile the driver but use:
./configure --with-cards=emu10k1 --with-sequencer=yes --with-debug=full
and send the output in /var/log/messages to the list.
Charles, Thank you very much! That worked great! Now I have sound without alot of fuss! I owe you one! Again thanks! -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
participants (3)
-
Charles Philip Chan
-
Curtis Rey
-
Marshall Heartley