Tiny Core Base > CorePlus

VT8237A/VT8251 No Sound

<< < (8/11) > >>

Juanito:
"~" means /home/$USER

..so by default, ~/.X.d/alsaunmute = /home/tc/.X.d/alsaunmute

Note that the leading dot in .X.d makes it hidden, so to see it you need, for example, "ls -a ~"

evertvaningen:

--- Quote from: coreplayer2 on June 13, 2017, 11:32:36 PM ---
--- Quote ---sudo alsactl store is always required to be ran before backup + reboot/shutdown, for the config file to be updated so the settings can be restored after reboot.
--- End quote ---

Sure you can take that route if it works for you..  My argument is that saving the alsa settings hasn't been the most successful plan (for me anyhow), so I don't take that route anymore.  In fact I haven't made a backup of asound.state in a long time despite various complex hardware configurations and TC versions.    After some research I found you can command a change to any alsamixer control via the command line, Including unmuting any control eg: master control, SPDIF additionally set the volume to specific levels, etc. etc.   Typically I find that after allowing Alsa to configure itself on bootup there remains only unmuting a few specific volume controls, SPDIF channels and volume levels to get sound.  All of this can all be accomplished reliably with a few commands run from ~/.X.d/alsa  which is by far more reliable than hoping alsa will restore every custom setting, which appears to be somewhat temperamental in that department..

I'm not sure yet what other alsamixer controls the OP changed to get sound.   However, this and a few similar commands for other controls resolves my dilemma and will probably resolve his issue too.
echo "amixer set "Master" 80 unmute" > ~/.X.d/alsaunmute

Obviously ~/.X.d/alsaunmute will be needing some persistence over reboot

--- End quote ---

It's so difficult for me to understand all this this even with the corebook. This is all new for me and so far im enjoying the OS and trying to find solutions.

You guys are awesome for helping me.

So the next step is to issue -> echo "amixer set "Master" 80 unmute" > ~/.X.d/alsaunmute
In the terminal and then nano somewhere and add ~/.X.d/alsaunmute somewhere in /opt/.filetool.lst or somewhere else?

I dont know...

Juanito:

--- Code: ---$echo "amixer set "Master" 80 unmute" > ~/.X.d/alsaunmute
--- End code ---
..will create a file named ~/.X.d/alsaunmute containing "amixer set "Master" 80 unmute"

By default, everything contained in /home/tc and its subdirectories will be backed up.

There is a dry run mode to filetool.sh that will list everything that would be inlcuded in your backup.

evertvaningen:

--- Quote from: Juanito on June 14, 2017, 06:47:30 AM ---
--- Code: ---$echo "amixer set "Master" 80 unmute" > ~/.X.d/alsaunmute
--- End code ---
..will create a file named ~/.X.d/alsaunmute containing "amixer set "Master" 80 unmute"

By default, everything contained in /home/tc and its subdirectories will be backed up.

There is a dry run mode to filetool.sh that will list everything that would be included in your backup.

--- End quote ---

cd /home/tc/.X.d | ls tells me the file is there so all good. But why does it still reset after reboot?

evertvaningen:
Amixer set "Master" 39

Works and when I check AlsaMixer master is set to 83...

echo "amixer set "Master" 39 unmute" > ~/.X.d/alsaunmute

Did the trick, glad that part is over.


I want to thank everyone that helped me in this matter. All my topics solutions are used in a tutorial for a HP T510 Thin Client Internet Radio.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version