Tiny Core Extensions > TCE Q&A Forum

Retaining alsamixer settings between boots

<< < (7/8) > >>

neonix:
If I create optional extension alsamixer-set.tcz with

asound.state
and "xterm alsamixer" in menu list. Would you put it into repo?

Rich:
Hi neonix
I think asound.state might include hardware specific
information. If that is the case, then I would say no.

neonix:
And if alsa-set.tcz or alsamixer-set.tcz will contains this?


--- Code: ---pause 5
amixer set Master unmute
amixer set PCM unmute
amixer set Headphone unmute

amixer set Master 75%
amixer set PCM 75%
amixer set Headphone 75%
--- End code ---


--- Code: ---[Desktop Entry]
Name=alsamixer
Exec=aterm -e alsamixer
Icon=
Terminal=false
X-FullPathIcon=
Type=Application
;OnlyShowIn=Old;
Categories=Utility;
--- End code ---

Rich:
Hi neonix

--- Quote from: neonix on February 05, 2025, 04:29:42 AM ---And if alsa-set.tcz or alsamixer-set.tcz will contains this?


--- Code: ---pause 5
amixer set Master unmute
amixer set PCM unmute
amixer set Headphone unmute

amixer set Master 75%
amixer set PCM 75%
amixer set Headphone 75%
--- End code ---
...
--- End quote ---
I'm guessing you meant  sleep 5  for the first line.
If that is supposed to be a startup script that goes in
/usr/local/tce.installed , then no.

When Tinycore boots, it first loads all of the extensions
in onboot.lst. it then runs all of the startup scripts for
those extensions. Any extensions that were loaded after
yours, would now have their startup scripts blocked from
running while yours sits there and sleeps.



--- Quote --- ...
--- Code: ---[Desktop Entry]
Name=alsamixer
Exec=aterm -e alsamixer
Icon=
Terminal=false
X-FullPathIcon=
Type=Application
;OnlyShowIn=Old;
Categories=Utility;
--- End code ---

--- End quote ---
That one is fine. As shown, it will only provide an entry
for the desktop menu, but no icon for the wbar.
If you want an icon, you need to provide one and add
something like this:

--- Code: ---Icon=alsamixer
X-FullPathIcon=/usr/local/share/pixmaps/alsamixer.png
--- End code ---

neonix:
SliTaz 2.0 has something like this.



--- Code: ---#!/bin/sh
# Set and store default mixer volumes for SliTaz. Used at boot time
# if a sound card has been detected automatically and can be used
# directly.
#

echo "Setting default mixer volumes..."
amixer -s -q <<EOF
set Master 75% unmute
set Master -12dB
set 'Master Mono' 75% unmute
set 'Master Mono' -12dB
set Front 75% unmute
set Front -12dB
set PCM 90% unmute
set PCM 0dB
mixer Synth 90% unmute
mixer Synth 0dB
mixer CD 90% unmute
mixer CD 0dB
# mute mic
set Mic 0% mute
# ESS 1969 chipset has 2 PCM channels
set PCM,1 90% unmute
set PCM,1 0dB
# Trident/YMFPCI/emu10k1
set Wave 100% unmute
set Music 100% unmute
set AC97 100% unmute
# CS4237B chipset:
set 'Master Digital' 75% unmute
# Envy24 chips with analog outs
set DAC 90% unmute
set DAC -12dB
set DAC,0 90% unmute
set DAC,0 -12dB
set DAC,1 90% unmute
set DAC,1 -12dB
# some notebooks use headphone instead of master
set Headphone 75% unmute
set Headphone -12dB
set Playback 100% unmute
# turn off digital switches
set "SB Live Analog/Digital Output Jack" off
set "Audigy Analog/Digital Output Jack" off
EOF

# Store config
alsactl store
--- End code ---

If alsa.tcz is executed/mounted before alsa-set.tcz then this script will works theoretically (in TCL)?
Other solution is to execute this script from (jwm) menulist manually.

The question is, can I put this solution in to the repo?

Navigation

[0] Message Index

[#] Next page

[*] Previous page