You are here: welcome » wiki » setting_up_sound

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
wiki:setting_up_sound [2012/10/27 09:34] – [Part 1 where you also have a blacklist] model=auto aus9wiki:setting_up_sound [2018/10/04 20:21] (current) – [Rich setup guide] aus9
Line 1: Line 1:
-under re-construction Now 2 pages will fix up contents later 
- 
 ======ALSA====== ======ALSA======
 Sound is NOT built into base CorePlus, MicroCore or TinyCore, sound is implemented via extensions. I assume you are reading this because you a newbie.  Sound is NOT built into base CorePlus, MicroCore or TinyCore, sound is implemented via extensions. I assume you are reading this because you a newbie. 
- 
- 
- 
  
 =====OSS versus ALSA===== =====OSS versus ALSA=====
Line 28: Line 23:
  
 {{wiki:twid_70_mob.jpg}} {{wiki:twid_70_mob.jpg}}
 +
 +</code>
 +
 +
 +
 +=====Rich setup guide=====
 +Install alsa-config.tcz and alsa.tcz
 +
 +Install alsamixergui.tcz (optional)
 +
 +Set the volume control on the front of the speaker about 1/3 of the way up
 +
 +Run:
 +<code>alsactl init</code>
 +
 +This produced a slight thump as the card was found and initialized. That command
 +also unmuted the speakers and set the mixer volumes at sane levels.
 +
 +Run:
 +<code>speaker-test [-Ddefault:1] -c2 -t wav -l1</code>
 +
 +If all went well, you should hear the phrases  "Front Left"  and  "Front Right"  from
 +your left and right speakers respectively.
 +
 +Run:
 +<code>sudo alsactl store</code>
 +
 +Run:
 +<code>echo alsactl restore >> /opt/bootlocal.sh</code>
 +
 +Run:
 +<code>echo usr/local/etc/alsa/asound.state >> /opt/.filetool.lst</code>
 +
 +Run a backup to save your setup.
 =====Hearing sound using ALSA===== =====Hearing sound using ALSA=====
  
Line 120: Line 149:
 =====asoundrc wiki=====\\ =====asoundrc wiki=====\\
 http://alsa.opensrc.org/.asoundrc http://alsa.opensrc.org/.asoundrc
- 
- 
  
      
Line 164: Line 191:
  
 If you have multiple sound devices or the mixer channels are not correct or still no sound continue reading please. If you have multiple sound devices or the mixer channels are not correct or still no sound continue reading please.
 +
 =====Technical details for Newbies if no sound===== =====Technical details for Newbies if no sound=====
 To hear sound, you need a sound tcz to load called alsa.tcz (this also loads dependencies)\\ To hear sound, you need a sound tcz to load called alsa.tcz (this also loads dependencies)\\
Line 220: Line 248:
    * modules exist, but a system setting such as the bootcode has "blacklisted" the loading of the module\\    * modules exist, but a system setting such as the bootcode has "blacklisted" the loading of the module\\
    * modules exist, but a module "option" disables sound outputs     * modules exist, but a module "option" disables sound outputs 
 +
 =====alsaconf when the aplay list is empty===== =====alsaconf when the aplay list is empty=====
 If you downloaded alsa and its in your onboot list and you rebooted, you should have sound devices configured. You may need to adjust the mixers to **hear** sound. However, if  If you downloaded alsa and its in your onboot list and you rebooted, you should have sound devices configured. You may need to adjust the mixers to **hear** sound. However, if 
Line 232: Line 261:
  
 Users with ISA sound devices may need alsaconf. If the only changes were to mixer levels or running alsaconf you can now jump to [[alsa_part2#persistence|persistence]] Users with ISA sound devices may need alsaconf. If the only changes were to mixer levels or running alsaconf you can now jump to [[alsa_part2#persistence|persistence]]
 +
 ===== blacklist ===== ===== blacklist =====
 This option needs edit of your boot loader config with root powers. This is **unofficial** recommended way for all users where:\\ This option needs edit of your boot loader config with root powers. This is **unofficial** recommended way for all users where:\\
Line 249: Line 279:
 If you have multiple modules to blacklist you can use the formula If you have multiple modules to blacklist you can use the formula
 ^blacklist=sound_module_name,module_2,module_3 etc^ ^blacklist=sound_module_name,module_2,module_3 etc^
 +
 =====Blacklist for permanent disable of internal sound device===== =====Blacklist for permanent disable of internal sound device=====
 So if you have a computer where the internal sound, onboard or isa or pci is faulty or deficient, blacklist the internal sound module. So if you have a computer where the internal sound, onboard or isa or pci is faulty or deficient, blacklist the internal sound module.
Line 271: Line 302:
 </code> </code>
 In other words, what we test live, is roughly what we show in bootlocal but drop the word sudo In other words, what we test live, is roughly what we show in bootlocal but drop the word sudo
 +
 =====Reasons for changing===== =====Reasons for changing=====
 In this section, the blacklist is the same as the modprobe -r command. But we are doing it, because you find that the mixer channels or switches or options are not a match to your actual hardware. This is true for my intel device and may be true of a number of intel devices but also affects some other sound module users such as AC97. In this section, the blacklist is the same as the modprobe -r command. But we are doing it, because you find that the mixer channels or switches or options are not a match to your actual hardware. This is true for my intel device and may be true of a number of intel devices but also affects some other sound module users such as AC97.
Line 298: Line 330:
 </code> </code>
 If this is too much info for newbies, ignore the modinfo command. If this is too much info for newbies, ignore the modinfo command.
 +
 =====Research your sound device===== =====Research your sound device=====
 lsmod shows what your sound module is. Now use that information to check the list of files for {{http://www.kernel.org/doc/Documentation/sound/alsa/|sound module options and tweaks}} lsmod shows what your sound module is. Now use that information to check the list of files for {{http://www.kernel.org/doc/Documentation/sound/alsa/|sound module options and tweaks}}
Line 335: Line 368:
  
 and so we now use model=auto. and so we now use model=auto.
 +
 =====bootlocal.sh tweaks - Part two -- to change mixer controls or settings===== =====bootlocal.sh tweaks - Part two -- to change mixer controls or settings=====
  
Line 343: Line 377:
  
 eg I use /sbin/modprobe snd_hda_intel model=auto eg I use /sbin/modprobe snd_hda_intel model=auto
 +
 ====Part 2 where you have not blacklisted==== ====Part 2 where you have not blacklisted====
 You will need a remove module and re-insert module command, using formula You will need a remove module and re-insert module command, using formula
Line 356: Line 391:
 {{wiki:twid_66_surround1.jpg?400x250}} {{wiki:twid_66_surround1.jpg?400x250}}
  
-=====index issues=====+=====index or sound device number issues=====
 As a general rule, most software applications, wanting to play or record sound, prefer to use the first detected sound device. We call this index=0 even if you have not setup any index value.  Its the same as saying the card number and ALSA counts devices from zero not from one. As a general rule, most software applications, wanting to play or record sound, prefer to use the first detected sound device. We call this index=0 even if you have not setup any index value.  Its the same as saying the card number and ALSA counts devices from zero not from one.
  
Line 374: Line 409:
 =====Page 2===== =====Page 2=====
 [[wiki:alsa_part2|click here to next page]] [[wiki:alsa_part2|click here to next page]]
- 
- 
- 
- 
- 
  
  
Print/export
QR Code
QR Code wiki:setting_up_sound (generated for current page)