|
I have Direwolf working in a Pi 3B, and I am unable to have the sound devices volumes get properly restored after a reboot.
It receives fine, and transmits fine, and I can adjust volumes easily using alsamixer, but on the next power-up, all of the volumes need to get re-adjusted again.? I can use
sudo alsactl store 1? (or no channel, or 2 or 3) and the next power-up the sound devices are messed up yet again.
I'm using a usual CM108 sound card, so nothing unusual.
?
It should be easy, but I haven't seen the clue as to what yet.
?
Thanks.
Arnold, KQ6DI
|
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your
direwolf.conf file, what sound devices are you using via your
various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file /var/lib/alsa/asound.state file
exist?
?? - Upon restart, how are you running "alsastl restore" to restore
the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL sound
device levels and not just specific cards.
--David
KI6ZHD
toggle quoted message
Show quoted text
I have Direwolf
working in a Pi 3B, and I am unable to have the sound devices
volumes get properly restored after a reboot.
It receives fine,
and transmits fine, and I can adjust volumes easily using alsamixer,
but on the next power-up, all of the volumes need to get
re-adjusted again.? I can use
sudo alsactl
store 1? (or no channel, or 2 or 3) and the next
power-up the sound devices are messed up yet again.
I'm using a usual
CM108 sound card, so nothing unusual.
?
It should be
easy, but I haven't seen the clue as to what yet.
?
Thanks.
Arnold, KQ6DI
|
David,
Yes, it is Raspberry Pi OS, Bookworm.
?
Looks like I didn't use "alsastl restore".? Where should this go?
I didn't look for /var/lib/alsa/asound.state file yet, but I'll try Restore first.
?
Thanks again,
Arnold, KQ6DI
On 12/08/2024 3:14 PM PST David Ranch via groups.io <direwolf-groupsio@...> wrote:
?
?
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your direwolf.conf file, what sound devices are you using via your various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file /var/lib/alsa/asound.state file exist?
?? - Upon restart, how are you running "alsastl restore" to restore the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL sound device levels and not just specific cards.
--David
KI6ZHD
I have Direwolf working in a Pi 3B, and I am unable to have the sound devices volumes get properly restored after a reboot.
It receives fine, and transmits fine, and I can adjust volumes easily using alsamixer, but on the next power-up, all of the volumes need to get re-adjusted again.? I can use
sudo alsactl store 1? (or no channel, or 2 or 3) and the next power-up the sound devices are messed up yet again.
I'm using a usual CM108 sound card, so nothing unusual.
?
It should be easy, but I haven't seen the clue as to what yet.
?
Thanks.
Arnold, KQ6DI
|
Greetings Arnold.
After <F6> and choosing the correct sound card before making
adjustments, then <Esc> to exit, did you "sudo alsactl store"?
Your Rpi may have several audio devces, so <F6> to choose the
correct one is important. If I may ask, please. how did you
determine " alsactl
store 1 " as the correct device?
On 12/8/24 15:00, Arnold Harding -
KQ6DI via groups.io wrote:
toggle quoted message
Show quoted text
I have
Direwolf working in a Pi 3B, and I am unable to have the sound
devices volumes get properly restored after a reboot.
It receives
fine, and transmits fine, and I can adjust volumes easily
using alsamixer, but on the next power-up, all of
the volumes need to get re-adjusted again.? I can use
sudo
alsactl store 1? (or no channel, or 2 or 3) and the
next power-up the sound devices are messed up yet again.
I'm using a
usual CM108 sound card, so nothing unusual.
?
It should be
easy, but I haven't seen the clue as to what yet.
|
I too have found this to be an issue with bookworm while running Direwolf 1.7. My guess is that this will also work with 1.8. My workaround was to install pule audio then install pauvcontrol
sudo apt-get install pauvcontrol
This will allow for adjustment of levels.
Default is 100% which is too high. It won't
save settings after reboot.
To set pulse settings permenantly:
pactl get-default-source // make sure default is USB card
// this is for input / rcv
pactl get-default-source
alsa_input.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.mono-fallback
pactl get-default-sink // This is for output / xmit
pactl get-default-sink
alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.analog-stereo
FOR INPUT (rcv):
pactl set-source-volume alsa_input.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.mono-fallback 10%
FOR OUTPUT (xmit): pactl set-sink-volume $(pactl get-default-sink) 73%
pactl set-sink-volume alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.analog-stereo 73%
These percent settings are for my particular sound card. Re-run each command to adjust the settings to your liking.
This will remember your audio settings for you. This command is only found in bookworm, not in previous OS's.
-- Mike WB8ERJ
Packet BBS email:
WB8ERJ@WB8ERJ.#NEOH.OH.USA.NOAM
Geeze! What is he up to now?
|
Hello Arnold,
Raspberry Pi OS Bookworm uses systemd and it should have already
installed the following Systemd unit files to restore your saved
audio levels via:
??? /usr/lib/systemd/system/alsa-restore.service
You can see if it's recognized by running this command:
?? systemctl | grep alsa
?? --
?? alsa-restore.service???????????????????????????????????????
loaded??? active exited??? Save/Restore Sound Card State
?? --
If it's not showing up on your Pi, you need to troubleshoot that.?
There is one noted caveat mentioned in the "1.3 ALSA and systemd"
section in
of why that might happen.? Specifically the
/etc/alsa/state-daemon.conf file cannot exist to let the audio
levels be restored.? Does that /etc/alsa/state-daemon.conf file
exist on your Pi?? If so, do you need it??
Maybe you just saved the audio levels of the wrong souncard card??
Try just running:
?? #saves the levels of all sound devices
?? sudo alsactl save
where this more basic command will save ALL sound device levels and
then reboot.? Did your required levels now get saved?
--David
KI6ZHD
On 12/08/2024 03:21 PM, Arnold Harding
- KQ6DI via groups.io wrote:
toggle quoted message
Show quoted text
David,
Yes, it is
Raspberry Pi OS, Bookworm.
?
Looks like I
didn't use "alsastl restore".? Where should this go?
I didn't look for
/var/lib/alsa/asound.state file yet, but I'll try Restore
first.
?
Thanks again,
Arnold, KQ6DI
?
?
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your
direwolf.conf file, what sound devices are you using via your
various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file /var/lib/alsa/asound.state
file exist?
?? - Upon restart, how are you running "alsastl restore" to
restore the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL sound
device levels and not just specific cards.
--David
KI6ZHD
I have
Direwolf working in a Pi 3B, and I am unable to have the
sound devices volumes get properly restored after a
reboot.
It receives
fine, and transmits fine, and I can adjust volumes easily
using alsamixer, but on the next power-up, all
of the volumes need to get re-adjusted again.? I can use
sudo
alsactl store 1? (or no channel, or 2 or 3) and the
next power-up the sound devices are messed up yet again.
I'm using a
usual CM108 sound card, so nothing unusual.
?
It should be
easy, but I haven't seen the clue as to what yet.
?
Thanks.
Arnold, KQ6DI
|
One addition here: back on 11/11/23, I had updated
my
doc to include an addition command line option:
?? sudo alsactl --no-ucm store
This was needed to avoid some warnings.? You can learn more about
UCM at:
??
--David
KI6ZHD
On 12/09/2024 07:59 AM, David Ranch
wrote:
toggle quoted message
Show quoted text
Hello Arnold,
Raspberry Pi OS Bookworm uses systemd and it should have already
installed the following Systemd unit files to restore your saved
audio levels via:
??? /usr/lib/systemd/system/alsa-restore.service
You can see if it's recognized by running this command:
?? systemctl | grep alsa
?? --
?? alsa-restore.service???????????????????????????????????????
loaded??? active exited??? Save/Restore Sound Card State
?? --
If it's not showing up on your Pi, you need to troubleshoot
that.? There is one noted caveat mentioned in the "1.3 ALSA and
systemd" section in
of why that might happen.? Specifically the
/etc/alsa/state-daemon.conf file cannot exist to let the audio
levels be restored.? Does that /etc/alsa/state-daemon.conf file
exist on your Pi?? If so, do you need it??
Maybe you just saved the audio levels of the wrong souncard card??
Try just running:
?? #saves the levels of all sound devices
?? sudo alsactl save
where this more basic command will save ALL sound device levels
and then reboot.? Did your required levels now get saved?
--David
KI6ZHD
On 12/08/2024 03:21 PM, Arnold
Harding - KQ6DI via groups.io wrote:
David,
Yes, it is
Raspberry Pi OS, Bookworm.
?
Looks like I
didn't use "alsastl restore".? Where should this go?
I didn't look
for /var/lib/alsa/asound.state file yet, but I'll try
Restore first.
?
Thanks again,
Arnold, KQ6DI
?
?
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your
direwolf.conf file, what sound devices are you using via your
various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file /var/lib/alsa/asound.state
file exist?
?? - Upon restart, how are you running "alsastl restore" to
restore the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL sound
device levels and not just specific cards.
--David
KI6ZHD
I have
Direwolf working in a Pi 3B, and I am unable to have the
sound devices volumes get properly restored after a
reboot.
It
receives fine, and transmits fine, and I can adjust
volumes easily using alsamixer, but on the
next power-up, all of the volumes need to get
re-adjusted again.? I can use
sudo
alsactl store 1? (or no channel, or 2 or 3) and
the next power-up the sound devices are messed up yet
again.
I'm
using a usual CM108 sound card, so nothing unusual.
?
It
should be easy, but I haven't seen the clue as to what
yet.
?
Thanks.
Arnold,
KQ6DI
|
David,
I have used sudo alsactl save , but put in the port number to also try.
systemctl | grep alsa does respond with "loaded active exited"
?
The only thing in /etc/alsa/ is a directory conf.d .? Not the state-daemon.conf? file.
?? In /etc/alsa/conf.d are multiple additional directories.
?
?
~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 2: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
?
?
I've loaded Bookworm and Direwolf on 4 other Pi's without any other issues several months ago.? Now things are fighting me.? One difference is I don't want WiFi running on this Pi, so I did not set this up.? I wouldn't think WiFi settings would cause a problem, but I do get a warning when I log in after a reboot.
---------------------
Linux mine 6.6.62+rpt-rpi-v7 #1 SMP Raspbian 1:6.6.62-1+rpt1 (2024-11-25) arm v7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Dec 9 11:05:06 2024
Wi-Fi is currently blocked by rfkill.
Use raspi-config to set the country before use.
mine@mine:~ $
-----------------------
?
I'm going to keep carefully looking, but help is appreciated.
Arnold, KQ6DI
?
On 12/09/2024 7:59 AM PST David Ranch via groups.io <direwolf-groupsio@...> wrote:
?
?
Hello Arnold,
Raspberry Pi OS Bookworm uses systemd and it should have already installed the following Systemd unit files to restore your saved audio levels via:
??? /usr/lib/systemd/system/alsa-restore.service
You can see if it's recognized by running this command:
?? systemctl | grep alsa
?? --
?? alsa-restore.service??????????????????????????????????????? loaded??? active exited??? Save/Restore Sound Card State
?? --
If it's not showing up on your Pi, you need to troubleshoot that.? There is one noted caveat mentioned in the "1.3 ALSA and systemd" section in of why that might happen.? Specifically the /etc/alsa/state-daemon.conf file cannot exist to let the audio levels be restored.? Does that /etc/alsa/state-daemon.conf file exist on your Pi?? If so, do you need it??
Maybe you just saved the audio levels of the wrong souncard card?? Try just running:
?? #saves the levels of all sound devices
?? sudo alsactl save
where this more basic command will save ALL sound device levels and then reboot.? Did your required levels now get saved?
--David
KI6ZHD
On 12/08/2024 03:21 PM, Arnold Harding - KQ6DI via groups.io wrote:
David,
Yes, it is Raspberry Pi OS, Bookworm.
?
Looks like I didn't use "alsastl restore".? Where should this go?
I didn't look for /var/lib/alsa/asound.state file yet, but I'll try Restore first.
?
Thanks again,
Arnold, KQ6DI
?
?
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your direwolf.conf file, what sound devices are you using via your various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file /var/lib/alsa/asound.state file exist?
?? - Upon restart, how are you running "alsastl restore" to restore the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL sound device levels and not just specific cards.
--David
KI6ZHD
I have Direwolf working in a Pi 3B, and I am unable to have the sound devices volumes get properly restored after a reboot.
It receives fine, and transmits fine, and I can adjust volumes easily using alsamixer, but on the next power-up, all of the volumes need to get re-adjusted again.? I can use
sudo alsactl store 1? (or no channel, or 2 or 3) and the next power-up the sound devices are messed up yet again.
I'm using a usual CM108 sound card, so nothing unusual.
?
It should be easy, but I haven't seen the clue as to what yet.
?
Thanks.
Arnold, KQ6DI
|
Hello Arnold,
On 12/09/2024 11:10 AM, Arnold Harding
- KQ6DI via groups.io wrote:
David,
I have used
sudo alsactl save , but put in the port number to also
try.
Please try NOT specifying a specific number:
?? sudo alsactl store
Once that's run, make sure you have the following file present with
today's date/time:
?? sudo ls -la /var/lib/alsa/asound.state
systemctl |
grep alsa does respond with "loaded active exited"
Ok.. that's good.
? The only thing in
/etc/alsa/ is a directory conf.d .? Not the state-daemon.conf?
file.
?? In
/etc/alsa/conf.d are multiple additional directories.
Ok. good.
?Wi-Fi is currently blocked
by rfkill.
Use raspi-config to set
the country before use.
That shouldn't matter
I'm going to
keep carefully looking, but help is appreciated.
One thing to try... open up two CLI terminal sessions to your Rpi.?
?? - In session #1, open up alsamixer and select the correct sound
device that's connected to your radio.? Make sure nothing important
is muted, etc.
?????? Now, go and CHANGE either the microphone or playback levels
to something you DON'T want.? Once changed.. just leave the
alsamixer
?????? program running
?? - In session #2, run the command:
????? sudo alsactl store
? ? ?? In session #1, you should see your changed volume levels
RETURN to where you expect them LIVE.? If they don't change,
something isn't correct here.
? ? ?? Maybe you see some errors here??? Maybe you see some errors
running "sudo journalctl -f" ?
--David
KI6ZHD
On 12/09/2024 7:59 AM PST David Ranch via groups.io
<direwolf-groupsio@...> wrote:
?
?
Hello Arnold,
Raspberry Pi OS Bookworm uses systemd and it should have already
installed the following Systemd unit files to restore your saved
audio levels via:
??? /usr/lib/systemd/system/alsa-restore.service
You can see if it's recognized by running this command:
?? systemctl | grep alsa
?? --
?? alsa-restore.service???????????????????????????????????????
loaded??? active exited??? Save/Restore Sound Card State
?? --
If it's not showing up on your Pi, you need to troubleshoot
that.? There is one noted caveat mentioned in the "1.3 ALSA and
systemd" section in
of why that might happen.? Specifically the
/etc/alsa/state-daemon.conf file cannot exist to let the audio
levels be restored.? Does that /etc/alsa/state-daemon.conf file
exist on your Pi?? If so, do you need it??
Maybe you just saved the audio levels of the wrong souncard
card?? Try just running:
?? #saves the levels of all sound devices
?? sudo alsactl save
where this more basic command will save ALL sound device levels
and then reboot.? Did your required levels now get saved?
--David
KI6ZHD
On 12/08/2024 03:21 PM, Arnold
Harding - KQ6DI via groups.io wrote:
David,
Yes, it is
Raspberry Pi OS, Bookworm.
?
Looks like I
didn't use "alsastl restore".? Where should this go?
I didn't look
for /var/lib/alsa/asound.state file yet, but I'll try
Restore first.
?
Thanks again,
Arnold, KQ6DI
?
?
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your
direwolf.conf file, what sound devices are you using via
your various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file
/var/lib/alsa/asound.state file exist?
?? - Upon restart, how are you running "alsastl restore" to
restore the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL
sound device levels and not just specific cards.
--David
KI6ZHD
I have Direwolf working in a Pi 3B, and I am
unable to have the sound devices volumes get properly
restored after a reboot.
It receives fine, and transmits fine, and I can
adjust volumes easily using alsamixer, but
on the next power-up, all of the volumes need to get
re-adjusted again.? I can use
sudo alsactl store 1? (or no channel,
or 2 or 3) and the next power-up the sound devices are
messed up yet again.
I'm using a usual CM108 sound card, so nothing
unusual.
?
It should be easy, but I haven't seen the clue
as to what yet.
?
Thanks.
Arnold, KQ6DI
|
I have a Pi 3A, 3B, 3B+ all running Bookworm and Direwolf 1.8, and all work fine.? It's only this attempt at another 3B giving me issues, so something odd happened.
I think my best option is to re-format the SD Card, and start over at the point of loading the OS.? It seems like a better option than fighting what might be missing...
?
Arnold, KQ6DI
On 12/09/2024 12:01 PM PST David Ranch via groups.io <direwolf-groupsio@...> wrote:
?
?
Hello Arnold,
On 12/09/2024 11:10 AM, Arnold Harding - KQ6DI via groups.io wrote:
David,
I have used sudo alsactl save , but put in the port number to also try.
Please try NOT specifying a specific number:
?? sudo alsactl store
Once that's run, make sure you have the following file present with today's date/time:
?? sudo ls -la /var/lib/alsa/asound.state
?
systemctl | grep alsa does respond with "loaded active exited"
Ok.. that's good.
?
? The only thing in /etc/alsa/ is a directory conf.d .? Not the state-daemon.conf? file.
?? In /etc/alsa/conf.d are multiple additional directories.
Ok. good.
?
?Wi-Fi is currently blocked by rfkill.
Use raspi-config to set the country before use.
That shouldn't matter
I'm going to keep carefully looking, but help is appreciated.
One thing to try... open up two CLI terminal sessions to your Rpi.?
?? - In session #1, open up alsamixer and select the correct sound device that's connected to your radio.? Make sure nothing important is muted, etc.
?????? Now, go and CHANGE either the microphone or playback levels to something you DON'T want.? Once changed.. just leave the alsamixer
?????? program running
?? - In session #2, run the command:
????? sudo alsactl store
? ? ?? In session #1, you should see your changed volume levels RETURN to where you expect them LIVE.? If they don't change, something isn't correct here.
? ? ?? Maybe you see some errors here??? Maybe you see some errors running "sudo journalctl -f" ?
--David
KI6ZHD
On 12/09/2024 7:59 AM PST David Ranch via groups.io <direwolf-groupsio@...> wrote:
?
?
Hello Arnold,
Raspberry Pi OS Bookworm uses systemd and it should have already installed the following Systemd unit files to restore your saved audio levels via:
??? /usr/lib/systemd/system/alsa-restore.service
You can see if it's recognized by running this command:
?? systemctl | grep alsa
?? --
?? alsa-restore.service??????????????????????????????????????? loaded??? active exited??? Save/Restore Sound Card State
?? --
If it's not showing up on your Pi, you need to troubleshoot that.? There is one noted caveat mentioned in the "1.3 ALSA and systemd" section in of why that might happen.? Specifically the /etc/alsa/state-daemon.conf file cannot exist to let the audio levels be restored.? Does that /etc/alsa/state-daemon.conf file exist on your Pi?? If so, do you need it??
Maybe you just saved the audio levels of the wrong souncard card?? Try just running:
?? #saves the levels of all sound devices
?? sudo alsactl save
where this more basic command will save ALL sound device levels and then reboot.? Did your required levels now get saved?
--David
KI6ZHD
On 12/08/2024 03:21 PM, Arnold Harding - KQ6DI via groups.io wrote:
David,
Yes, it is Raspberry Pi OS, Bookworm.
?
Looks like I didn't use "alsastl restore".? Where should this go?
I didn't look for /var/lib/alsa/asound.state file yet, but I'll try Restore first.
?
Thanks again,
Arnold, KQ6DI
?
?
Hello Arnold,
I assume you're using Raspberry Pi OS correct?? In your direwolf.conf file, what sound devices are you using via your various specified ADEVICEs?? Few things to check:
?? - does the saved ALSA level file /var/lib/alsa/asound.state file exist?
?? - Upon restart, how are you running "alsastl restore" to restore the saved audio levels?
Btw, I recommend to just run "alsactl store" to save ALL sound device levels and not just specific cards.
--David
KI6ZHD
I have Direwolf working in a Pi 3B, and I am unable to have the sound devices volumes get properly restored after a reboot.
It receives fine, and transmits fine, and I can adjust volumes easily using alsamixer, but on the next power-up, all of the volumes need to get re-adjusted again.? I can use
sudo alsactl store 1? (or no channel, or 2 or 3) and the next power-up the sound devices are messed up yet again.
I'm using a usual CM108 sound card, so nothing unusual.
?
It should be easy, but I haven't seen the clue as to what yet.
?
Thanks.
Arnold, KQ6DI
|
