Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX Sound - speakers maxed are only a wisper

Problems with your sound card are to be posted here, as well as tutorials to share with others.
Message
Author
User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9059
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX Sound - speakers maxed are only a wisper

#11 Post by dolphin_oracle » Fri May 09, 2014 3:59 pm

you could try:

alsactl init

and see if your hardware gets re-recognized. I think you would run that command as root.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9301
Joined: Wed Jul 12, 2006 2:26 pm

Re: MX Sound - speakers maxed are only a wisper

#12 Post by kmathern » Fri May 09, 2014 4:24 pm

dolphin_oracle wrote:
Forgot to indicate, believe I had a bit more sound volume before doing the updates this week, currently can not be certain now after trying front and rear, and changing speakers:
You are the second person I've heard with low/whisper volume after an update. I think jdmeaux1952 also has this problem on his antiX and MX install.

http://antix.freeforums.org/viewtopic.php?f=49&t=5044

no solution there though. Just cross-referencing the threads.
The only packages in that upgrade that I think might mess with the volume are the ones I highlighted in red and possibly the libmtp updates. Does jdmeaux1952 also have the "google-talkplugin" package installed? That (and "google-chrome-stable") aren't from the regular MX-14 repos.
Dvegas wrote:Forgot to indicate, believe I had a bit more sound volume before doing the updates this week, currently can not be certain now after trying front and rear, and changing speakers:

Commit Log for Fri May 9 08:38:06 2014


Upgraded the following packages:
smxi-inxi-antix (0.2.7) to 0.2.8


Commit Log for Wed May 7 13:59:00 2014


Upgraded the following packages:
base-files (7.1wheezy4) to 7.1wheezy5
catfish (0.3.2-2) to 0.3.2-2+deb7u1
curl (7.26.0-1+wheezy8) to 7.26.0-1+wheezy9
dpkg (1.16.12) to 1.16.14
dpkg-dev (1.16.12) to 1.16.14
google-chrome-stable (33.0.1750.152-1) to 34.0.1847.132-1
google-talkplugin (5.2.4.0-1) to 5.3.1.0-1
gstreamer0.10-plugins-bad (0.10.23-7.1) to 0.10.23-7.1+deb7u1
gvfs (1.12.3-4) to 1.12.3-5mx14
gvfs-backends (1.12.3-4) to 1.12.3-5mx14
gvfs-common (1.12.3-4) to 1.12.3-5mx14
gvfs-daemons (1.12.3-4) to 1.12.3-5mx14
gvfs-fuse (1.12.3-4) to 1.12.3-5mx14
gvfs-libs (1.12.3-4) to 1.12.3-5mx14
libcurl3 (7.26.0-1+wheezy8) to 7.26.0-1+wheezy9
libcurl3-gnutls (7.26.0-1+wheezy8) to 7.26.0-1+wheezy9
libdpkg-perl (1.16.12) to 1.16.14
libfreerdp1 (1.0.1-1.1+deb7u2) to 1.0.1-1.1+deb7u3
libgstreamer-plugins-bad0.10-0 (0.10.23-7.1) to 0.10.23-7.1+deb7u1
libjbig-dev (2.0-2) to 2.0-2+deb7u1
libjbig0 (2.0-2) to 2.0-2+deb7u1
liblcms2-2 (2.2+git20110628-2.2) to 2.2+git20110628-2.2+deb7u1
libmms0 (0.6.2-3) to 0.6.2-3+deb7u1
libmtp-common (1.1.6-20-g1b9f164-2mcr120+1) to 1.1.6-51-g1a2669c~ds0-1mcr120+1
libmtp-runtime (1.1.6-20-g1b9f164-2mcr120+1) to 1.1.6-51-g1a2669c~ds0-1mcr120+1
libmtp9[/color (1.1.6-20-g1b9f164-2mcr120+1) to 1.1.6-51-g1a2669c~ds0-1mcr120+1
libopenjpeg2 (1.3+dfsg-4.7) to 1.3+dfsg-4.8
libqupzilla1 (1.6.3-1mcr120+1) to 1.6.4-1mcr120+1
libsnmp-base (5.4.3~dfsg-2.7) to 5.4.3~dfsg-2.8
libsnmp-dev (5.4.3~dfsg-2.7) to 5.4.3~dfsg-2.8
libsnmp-perl (5.4.3~dfsg-2.7) to 5.4.3~dfsg-2.8
libsnmp15 (5.4.3~dfsg-2.7) to 5.4.3~dfsg-2.8
libsoup-gnome2.4-1 (2.38.1-2) to 2.38.1-3
libsoup2.4-1 (2.38.1-2) to 2.38.1-3
libssl-dev (1.0.1e-2+deb7u4) to 1.0.1e-2+deb7u7
libssl1.0.0 (1.0.1e-2+deb7u4) to 1.0.1e-2+deb7u7
libxml2 (2.8.0+dfsg1-7+nmu2) to 2.8.0+dfsg1-7+nmu3
linux-compiler-gcc-4.6-x86 (3.13.7-1~bpo70+1) to 3.13.10-1~bpo70+1
linux-libc-dev (3.13.7-1~bpo70+1) to 3.13.10-1~bpo70+1
openjdk-7-jre (7u25-2.3.10-1~deb7u1) to 7u55-2.4.7-1~deb7u1
openjdk-7-jre-headless (7u25-2.3.10-1~deb7u1) to 7u55-2.4.7-1~deb7u1
openjdk-7-jre-lib (7u25-2.3.10-1~deb7u1) to 7u55-2.4.7-1~deb7u1
openssh-client (1:6.5p1-6~bpo70+1) to 1:6.6p1-4~bpo70+1
openssh-server (1:6.5p1-6~bpo70+1) to 1:6.6p1-4~bpo70+1
openssh-sftp-server (1:6.5p1-6~bpo70+1) to 1:6.6p1-4~bpo70+1
openssl (1.0.1e-2+deb7u4) to 1.0.1e-2+deb7u7
python-cups (1.9.48-1.1) to 1.9.63-1mcr120+1
python-cupshelpers (1.3.7-4) to 1.4.3-4~bpo70+1
python-libxml2 (2.8.0+dfsg1-7+nmu2) to 2.8.0+dfsg1-7+nmu3
python-six (1.1.0-2) to 1.6.1-1~bpo70+1
qupzilla (1.6.3-1mcr120+1) to 1.6.4-1mcr120+1
shared-mime-info (1.0-1+b1) to 1.2-1~bpo70+1
spamassassin (3.3.2-5) to 3.3.2-5+deb7u1
system-config-printer (1.3.7-4) to 1.4.3-4~bpo70+1
system-config-printer-udev (1.3.7-4) to 1.4.3-4~bpo70+1
tzdata (2013i-0wheezy1) to 2014a-0wheezy1
tzdata-java (2013i-0wheezy1) to 2014a-0wheezy1

Installed the following packages:
gir1.2-notify-0.7 (0.7.5-1)
gir1.2-packagekitglib-1.0 (0.7.6-3)
libpackagekit-glib2-14 (0.7.6-3)

Dvegas
Forum Novice
Forum  Novice
Posts: 31
Joined: Thu Feb 20, 2014 9:23 pm

Re: MX Sound - speakers maxed are only a wisper

#13 Post by Dvegas » Fri May 09, 2014 4:52 pm

I just booted into windows (Posting from win7), and remembered to turn the sound on the speakers down. Start up sound was quite loud, I guess this is only a MX-14 sound problem.

This system always had low volume the speakers had to be turned up to 7/10s to get audible sound in MX-14, and using the 10/10 setting to hear music and on-line video close to computer.
In Windows the volume is about 3/10 for the same speaker level as maximum volume in MX-14. But now there is no sound in the MX-14 install.

Another step to work out: think it might be far faster to purchase a known working sound card from store, and turn off the on-board sound and black list the HDMI sound card to solve this situation. Earlier I had problems with no sound, but read another thread where Stevo made suggestions about changing the sound card order and that gave me a working sound in Linux. After re-enabling the sound card, would sound card order be changed? I can not find that thread again, hopefully Stevo or some else has armed with this info can help or knows the thread I am discussing and used earlier.

David

NGIB
Forum Regular
Forum Regular
Posts: 462
Joined: Sat Apr 05, 2014 12:12 pm

Re: MX Sound - speakers maxed are only a wisper

#14 Post by NGIB » Fri May 09, 2014 5:33 pm

My little HP has Radeon HDMI/Azalia sound and Pulseaudio gives a bit better control. Turn the BIOS sound back on, load Pulse and experiment some...
Life's tough, it's tougher if you're stupid...

Dvegas
Forum Novice
Forum  Novice
Posts: 31
Joined: Thu Feb 20, 2014 9:23 pm

Re: MX Sound - speakers maxed are only a wisper

#15 Post by Dvegas » Fri May 09, 2014 6:53 pm

Pulseaudio is loaded, now have sound turned HDMI off in pavucontrol and it found left and right front sound controls. They do not work in front control, but work in the read panel of thje desktop system instead. Have same sound volume as windows...

Thanks everyone for assisting...

I did need to remove Google Chrome and install Chromium instead, as Google Chrome kept crashing in Youtube...

David

User avatar
jdmeaux1952
Forum Regular
Forum Regular
Posts: 404
Joined: Wed Jan 08, 2014 11:55 pm

Re: MX Sound - speakers maxed are only a wisper

#16 Post by jdmeaux1952 » Sun May 11, 2014 6:35 am

Per anti, I installed pulseaudio and solved my problems with both antix and MX-14 having low sound levels. It's nice to be able to hear the audio again.
MSI S6000 i5-460M 4Gb mem
I am not CrAzY. And I have a paper from the doctors to prove it!
LRU# 563815
Phear the Penguin

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 22222
Joined: Wed Jul 19, 2006 6:13 am

Re: MX Sound - speakers maxed are only a wisper

#17 Post by Jerry3904 » Sun May 11, 2014 7:23 am

Glad this worked for you!

Pulseaudio was raised a couple of times during MX-14 development, but there were objections each time for some reason. Perhaps we will need to look again next cycle.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB

User avatar
zeeone
Forum Regular
Forum Regular
Posts: 901
Joined: Fri Jul 14, 2006 12:50 am

Re: MX Sound - speakers maxed are only a wisper

#18 Post by zeeone » Sun May 11, 2014 11:24 am

Jerry3904 wrote:Glad this worked for you!

Pulseaudio was raised a couple of times during MX-14 development, but there were objections each time for some reason. Perhaps we will need to look again next cycle.
Maybe it will work, snd_hsa_intel driver is the problem when one has the AMD HDMI chip, most likely will not work RIGHT.

Here, the fix was to pull an old Turtle Beach PCI sound card from the bone yard, turn off the HDMI in the BIOS, install
the Turtle Beach start the system.

Do not care, Pulseaudio and ALSA can update 30 times a day if they want, no changes happen to the sound card it stays
rock solid. All sound apps have their own sound adjustments, separate from the main volume, with no distortion to the
speakers as they are turned up. :popcorn:
Research, Research, Research, Before You Walk The Plank.
Registered Linux User # 398829

User avatar
lucky9
Forum Veteran
Forum Veteran
Posts: 11380
Joined: Wed Jul 12, 2006 5:54 am

Re: MX Sound - speakers maxed are only a wisper

#19 Post by lucky9 » Sun May 11, 2014 12:00 pm

My Logitech SoundBlaster has been great also.
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

Post Reply

Return to “Sound”