This is useless with the tiny speakers on my laptop; I've spent about two hours and entered around 50 command lines using ChatGPT's advice and mostly from my recollection of events during this repetitive process it's seems that it's not in Pulse audio but somewhere in Pipewire. AI's responses are beguiling as they are confidently expressed and it's fairly easy to copy the command lines; in my experience most of which fail but then there is another confidently expressed solution etc. etc.
On the other hand asking on Forums such as this seems to be the only other option and would have been far less time consuming and almost equally productive even with no responses.
From what I can tell the Debian documentation is probably of no use unless one wants to essentially gain in depth understanding; my guess would be something like 50 hours of study to maybe then find a solution to my issue and be equipped to solve similar problems. So there are three questions implied or stated here.
Default Audio volume stuck at 40%
-
- Posts: 1801
- Joined: 2008-02-21 17:03
- Location: Finland
- Has thanked: 1 time
- Been thanked: 104 times
Re: Default Audio volume stuck at 45%
Chat robots are not the best option to get Debian spesific info.
Debian wiki, this forum and debian irc are the most valid.
Install package inxi
Then run in terminal
It shows specs of your Debian installation, but hides any sensitive data.
Post the result in code tags as I did above. The fifth item in the top row which starts with B,
Debian wiki, this forum and debian irc are the most valid.
Install package inxi
Then run in terminal
Code: Select all
inxi -Fxxxmprz
Post the result in code tags as I did above. The fifth item in the top row which starts with B,
- sunrat
- Site admin
- Posts: 7494
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 135 times
- Been thanked: 677 times
Re: Default Audio volume stuck at 45%
All higher level audio servers depend on ALSA so you should also check ALSA levels. Install the alsa-utils package and check alsamixer in CLI. Or if you're scared of CLI, qasmixer does the same in GUI.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Re: Default Audio volume stuck at 40%
I'm reminded why I didn't consider that any other real option to AI was likely; on the other device I've run the inxi etc. asked Google Gemini if it could work out what ....5th item ...with B might mean; it suggested it was gibberish; noticed the "Paste bin" and pasted the details; could see nothing indicating that it pasted into the current post; tried to find this post; no notifications current or past and I have little idea of what sub forum this is in as there is no indication on the page. I'm sure with AI's help and a few hours one could work out how to paste something here.
Re: Default Audio volume stuck at 40%
Bing Co-Pilot came up with a verified solution involving four or five command lines; the only information I gave that ChatGPT may not have got is that I'd spent hours and input dozens of command lines to no effect. What I've got is probably a "workaround" type of solution, but it's welcome.
- FreewheelinFrank
- Global Moderator
- Posts: 2584
- Joined: 2010-06-07 16:59
- Has thanked: 51 times
- Been thanked: 285 times
Re: Default Audio volume stuck at 40%
AI cannot tell you why your speakers are stuck at a low volume, and neither can we without knowing anything about your hardware and your system.
You can simply post the output requested as text here: it is not that long.
You can simply post the output requested as text here: it is not that long.
-
- Global Moderator
- Posts: 4311
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 126 times
- Been thanked: 579 times
Re: Default Audio volume stuck at 40%
Hello,
Maybe you might share the "workaround" type of solution.dech wrote: 2025-02-06 23:54 Bing Co-Pilot came up with a verified solution involving four or five command lines; the only information I gave that ChatGPT may not have got is that I'd spent hours and input dozens of command lines to no effect. What I've got is probably a "workaround" type of solution, but it's welcome.