FWIW I found a page giving a nice summary of audio setup for freebsd here https://freebsdfoundation.org/resource/audio-on-freebsd-quick-guide/
The command appears to accept either 100 or 1.00. If I set mixer pcm=100 or mixer pcm=1.00, in both cases I see the same output showing it has been set to 1.00.The maximum mixer value is 100 up to 13.5R.
In 14.0R, the mixer was modified, and the maximum value became 1.00.
mixer(8)
Not 100% sure (not tried recently), but ifAnd this thread about making mixer settings permanent.
Is there any way to change the mixer vol permanently? The default mixer vol is 75 which is too low for me. I use
mixer vol 100
which give me good volume. However, once I reboot the computer the mixer vol is set to default 75 again. I'm wondering if there is any configuration file for mixer.
- everypot
- Replies: 7
- Forum: Multimedia/Gaming
varmfs is set to "YES" in your /etc/rc.conf, possibly the saved states vanishes on reboot."AUTO") preferred "YES" and entire /var vanished on first restart after updated main (aka *-CURRENT) environment years ago (several major releases ago).Possibly because something grabs mixer0, causing failed reads and existing one remains?Furthermore the pcm.volume fields in /var/db/mixer?-state all get set to 1.00, EXCEPT for mixer0-state which is set to 0.97, which seems like some kind of a bug.
Are you sure you've NOT overridden the defaultI can confirm that the saved states in /var/db do survive the reboot. But it looks like '/etc/rc.d/mixer start' never gets called.
mixer_enable="YES" in your /etc/rc.conf (or /etc/rc.conf.local if exists) with mixer_enable="NO"?Hello, "Grandpa"! Well, I am 84, so how old are you? (Just kidding!). Yes. In point of fact, what you have described above is ONE of the issues I am having. I'll dig out some DeOxit Fader Lube to fix that. However, my sound-level problem IS based in software somewhere, which I have not yet figured out. It is dynamic also, meaning it changes, seemingly at random.The more I've been fiddling with computers over the years the more I've caught myself fixing problems with software. Back in the 70s and 80s it was different. The starting point back then was always hardware issues.
I'm just guessing here.
You haven't described what it is that actually produces your sound so I'll just blatantly assume that you have something connected to audio out and I'll also assume, again blatantly, that this something is not a headset but an amplifier of some kind that passes the sound on to a set of speakers.
Having alot of old junk from "yorn" I've more and more often found that potentiometers (volume, bass, treble knobs etc) have a tendency to age and with that age comes reduction of sound. It's very common for electric guitars and old amplifiers.
The quick fix is to turn those knobs back and forth for a while. Sometimes there will be a scraping sound if this is done with power on which will confirm the ageing. The better fix is to get a spray that dissolves the buildup inside the pots.
Anyway, all I want to say is that sometimes it's not the software.
/grandpa
I'd disable PulseAudio auto-start in Session settings, and domixer pcm=100
Mixer is set PCM=.75 to start with. I'll do as you suggest and will wait to see what happens.I use mixer to adjust vol, but on fresh installs sometimes see pcm not at 100. I set it to 100 once and it seemingly sticks.
This definitely sounds like something that shouldn't be happening. I never get the volume spontaneously changing on my system, once I have set the level it stays set. Very strange, yes it must be incredibly annoying. I can only suggest trying a different motherboard.What is really bothering me about this audio problem is that it is "dynamic" in that once I have set it to the levels I need, unless I keep playing music (from www.sundaybaroque.org/listen/) or some other source of constant music, or sound, it suddenly drops back to the original almost silent settings, and I must reboot the system to get the sound levels set back to where I like it.
Hello, "Grandpa"! Well, I am 84, so how old are you? (Just kidding!). Yes. In point of fact, what you have described above is ONE of the issues I am having. I'll dig out some DeOxit Fader Lube to fix that. However, my sound-level problem IS based in software somewhere, which I have not yet figured out. It is dynamic also, meaning it changes, seemingly at random.
I have been involved with the HDD which carries my FreeBSD install beginning to finally fail. I have ordered a new Seagate Iron Wolf drive from NewEgg to replace the old 320GB drive, and will move my install of FreeBSD 14.4 over to that, OR I may decide to bite the bullet and rebuild it from scratch onto the new HDD.
(It is always "fun" to build a new system....and it gives me practice...)
I hope I will find the source of the variable audio sound level problem in the process.
Thank you for the encouragement.
God bless.
Ken Gordon
Or is it the system has one level (root user doing the mixer command) and then a user application overridding the current value. User value in effect while application running, then when done, system value takes precedent.What is needed is to get some trace out of the sound driver to identify what process is setting the volume back to the low level. Someone must be calling the device ioctl to do that. Unless it's genuinly a hardware bug that is happening below the driver.
I think Settings has it as a green circle icon near the bottom, but the command isHmmm....so...where do I find an editable "session settings"?
xfce4-session-settingsI did a fresh 16.0 install last night and mixer -a had pcm for everything at 100 out-the-box. Not sure what might change that but know it wasn't 100 a couple installs ago. I have basic Realtek HDA on Skylake (built-in speakers + 3.5mm line-out)I am leaning, heavily, towards building a new FreeBSD install from scratch
Well, in my case, the reason I am electing to do a "re-install" is because the present old 320 GB HDD which contains my present working FreeBSD install is failing, finally.Get a $10 USB sound"card". Cheaper than a reinstall.