From: BitTwister@mouse-potato.com   
      
   On Wed, 8 Mar 2017 14:32:57 +0100, Carlos E. R. wrote:   
   > On 2017-03-08 11:03, Elvish wrote:   
   >   
   >> Have not tried that, but I see no reason to give up the HDMI sound when   
   >> it works well in Winders.   
   >   
   > I have a little machine connected via hdmi to a display. Sound doesn't   
   > initially work, till I connect earphones to the box, then disconnect   
   > them. Now sounds go to the monitor, and stays till next reboot, I think.   
   > Using XFCE or LXDE.   
      
   Usual sound problem like that is because pulseaudio usually picks the   
   wrong hardware upon boot.  :(   
      
   Running pavucontrol in a terminal, using Configuration, turn off   
   undesired device usually fixes the problem. On Xfce, left click   
   sound icon, pick Audio mixer launches pavucontrol.   
      
   I got tired of having to configure audio device and sound levels so I   
   created a pulseaudio configuration file.   
      
   Suggested reading   
   man pulseaudio           for background info and configuration file locations   
   man pulse-cli-syntax     for a whole lot of configuration commands   
      
   I wasted a whole lot of time with the pulse-cli-syntax.   
      
   Easy method, configure everything in pavucontrol, hit Esc key to exit.   
      
   Run     pacmd dump > pulse_card.dump   
   Edit pulse_card.dump and remove all the load-module lines, add comment   
   header telling yourself how/what you did to get the contents, save and exit.   
      
   Now go back to "man pulseaudio" and decide where and what name to   
   place the pulse_card.dump contents.   
      
   After testing (log out/in then system reboot) modify the configuration   
   file comment header to have the selected file location and name.   
      
   All that would be left to do is do whatever you do to be able get back   
   to this point when doing a clean install.   
      
   Personally, I write scripts to automate all my configuration changes   
   and call those scripts from install scripts. For example:   
      day_one_install - add basic packages and changes then reboot   
      new_install - add additional baseline packages and package changes   
      install_addons - adds a bunch additional packages   
      install_toys - adds games   
      install_changes - final list of changes   
      
   Makes it easy to do clean installs on four different systems I   
   maintain.   
      
   For instance on this node, distribution, release, phase:   
   $ grep Elapsed *   
   wb_mga6_6_sta2_day_one_install.rpt_001:Elapsed: 0 00:07:41 for 33 packages   
   wb_mga6_6_sta2_install_addons.rpt_001:Elapsed:  0 00:10:49 for 145 packages   
   wb_mga6_6_sta2_install_changes.rpt_001:Elapsed: 0 00:10:13 for 16 packages   
   wb_mga6_6_sta2_install_toys.rpt_001:Elapsed:    0 00:44:56 for 56 packages   
   wb_mga6_6_sta2_new_install.rpt_001:Elapsed:     0 00:05:39 for 39 packages   
      
   Those five scripts execute   
        $ ls -1 *install* | wc -l   
        52   
   scripts which execute   
        $ ls -1 *change* | wc -l   
        99   
   scripts.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)