topic title: Sound from external speakers, but not internal
Posts: 17
MommaBear
Joined: 22 Aug 2015
#1
I'm trying to resurrect an old PC for a family with even less money than me.

I did have an old version of Kubuntu (2006, I think) running on this box. IIRC, everything just worked. But I can't recall if I needed external speakers or not.

I'd rather not have to tell these folks they have to go out and buy speakers, especially if it's not necessary.

The sound test tells me it was successful, alsamixer lets me play with all the controls (to no avail), I do hear beeps when appropriate.

I have done much googling, but most of the solutions refer to alsa-base.conf, which doesn't seem to exist on this antiX15 install. Nor do I have a /var/lib/alsa/asound.state. Or an .asoundrc. I'm new to antiX, so I don't know what's normal.

Code: Select all

aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
equal
plugequal
default
sysdefault:CARD=V8233A
    VIA 8233A, VIA 8233A
    Default Audio Device
front:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    Front speakers
surround21:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    4.0 Surround output to Front and Rear speakers
surround41:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
iec958:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    Direct sample mixing device
dmix:CARD=V8233A,DEV=1
    VIA 8233A, VIA 8233A
    Direct sample mixing device
dsnoop:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    Direct sample snooping device
dsnoop:CARD=V8233A,DEV=1
    VIA 8233A, VIA 8233A
    Direct sample snooping device
hw:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    Direct hardware device without any conversions
hw:CARD=V8233A,DEV=1
    VIA 8233A, VIA 8233A
    Direct hardware device without any conversions
plughw:CARD=V8233A,DEV=0
    VIA 8233A, VIA 8233A
    Hardware device with all software conversions
plughw:CARD=V8233A,DEV=1
    VIA 8233A, VIA 8233A
    Hardware device with all software conversions

Code: Select all

inxi -A
Audio:     Card VIA VT8233/A/8235/8237 AC97 Audio Controller
           driver: snd_via82xx
           Sound: Advanced Linux Sound Architecture v: k4.0.5-antix.1-486-smp

Hope I've given enough info. TIA.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#2
MommaBear wrote: I'm new to antiX...
We all were at one time and had to start learning somewhere. Because of this the following is a little more detailed than usual to help get you started.
MommaBear wrote: Sound from external speakers, but not internal (topic title)
[...]
The sound test tells me it was successful...
Based on those abstracts and the inxi report, the following assumes that you have all the correct drivers and such installed. If this assumption is incorrect none of the following will apply.

The sound system in antiX is named ALSA. It's configuration is based on cards and devices. To see their currect state do the following steps in a terminal.


Show the audio cards and devices known to the system

Code: Select all

aplay -l | grep card
Note that is lowercase letter L. The output should look something like this

Code: Select all

card 0: SI7018 [SiS SI7018], device 0: trident_dx_nx [Trident 4DWave]
card 0: SI7018 [SiS SI7018], device 1: trident_dx_nx IEC958 [Trident 4DWave IEC958]
card 1: Modem [SiS SI7013 Modem], device 0: Intel ICH - Modem [SiS SI7013 Modem - Modem]
In almost every case card 0 is the correct card and device 0 is its correct device. Subsequent steps are based on that idea. If your system uses a different card (perhaps for hdmi output) it might use a different card and/or device number.


Show the state of each audio control

Code: Select all

amixer --card 0
The output should look something like this truncated report

Code: Select all

Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 21 [68%] [-15.00dB] [on]
  Front Right: Playback 21 [68%] [-15.00dB] [on]
Simple mixer control 'Master Mono',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 31
  Mono: Playback 0 [0%] [-46.50dB] [off]
Simple mixer control 'Headphone',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 22 [71%] [-13.50dB] [on]
  Front Right: Playback 22 [71%] [-13.50dB] [on]
[...]
The key parts to note are the name in each section header (shown immediately following Simple mixer control, together with its state [on] or [off]. The state [off] indicates the control is muted.

It is possible that a needed control is set to [off] and simply needs to be toggled to [on] in order to output sound.

At this point alsamixer could be opened (Control Center-->Hardware-->Adjust Mixer).

The mixer interface will display the name of the selected card. The F6 key enables the card to be changed (if needed).

Each of the controls in the previous report corresponds to a control shown in the mixer display. It is possible to use the list to toggle an [off] state in order to activate the control. In the mixer display, toggling is done by using the arrow keys to select a control, then pressing the M key. At the foot of each slider control MM indicates the control is muted [off]. When toggled to unmute it, OO is displayed on a green background.

Note: some controls might not be able to be toggled.


The report used in this step contains both muted and unmuted controls. This can make the list very long and cumbersome to work with. If preferred a report can be produced that lists only controls that are muted [off].


Show the state of each muted audio control

Code: Select all

amixer contents | grep --before-context=3 'values=off' | grep --after-context=3 'numid='
The output should look something like this truncated report

Code: Select all

numid=5,iface=MIXER,name='Master Mono Playback Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
--
--
numid=28,iface=MIXER,name='3D Control - Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
--
--
numid=14,iface=MIXER,name='Line Playback Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
--
--
The key parts to note are the name in each section header, together with values=off. This indicates the control is muted.

Again, open the mixer and toggle the outputs.



Of course non of the steps using the terminal are essential. All the work could be done directly in the alsamixer interface. Hopefully, the terminal work will give you a peek at ways of finding additional information and help with your exploration of antiX.
Posts: 17
MommaBear
Joined: 22 Aug 2015
#3
Hi SamK:

Sorry for the delay in replying. I had another issue that took much longer to fix than I anticipated, but I think I've got it now.

I'm not on the antiX box right now, but I did all the stuff you suggested. The only things that were turned off were the capture settings. I'm assuming capture is for the mike, video, etc, as these are all muted in alsamixer.

When I ran aplay -l | grep card it listed 2 identical cards (V8233A) both card 0 but one is device 0 and one is device 1.
Of course non of the steps using the terminal are essential. All the work could be done directly in the alsamixer interface.
Yes, that's what I tried initially. This is a newer version of alsamixer than I have on my Mint 17 box. It has some controls I'm not familiar with, but considering the age of the antiX box (ca. 1995), I doubt they'd be relevant.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#4
MommaBear wrote:The only things that were turned off were the capture settings. I'm assuming capture is for the mike, video, etc, as these are all muted in alsamixer.
Yes, capture refers to controls related to recording sound.



The state reported of working with external speakers but not with internal speakers is an uncommon condition.

From your opening post
MommaBear wrote:I'm trying to resurrect an old PC...
...I do hear beeps when appropriate.
Question
Is the machine a laptop or desktop/tower system?

Laptops (even very old ones) were produced with internal speakers for audio replay. Desktops/towers were often manufactured with a miniscule onboard sounder device to output system beeps. In such a case audio replay was intended to be via external speakers.
Posts: 17
MommaBear
Joined: 22 Aug 2015
#5
SamK wrote:The state reported of working with external speakers but not with internal speakers is an uncommon condition.
I found quite a few posts on the web about it. As usual, they were mostly Ubuntu issues but I'm familiar enough with Debian-based distros to translate the answers. Trouble is, I've never used Gnome (KDE's my preferred desktop) and many of the answers refer to Gnome tools.
SamK wrote:Question
Is the machine a laptop or desktop/tower system?
A very old Proteva desktop/minitower, for which I found many complaints, but this machine has always worked reliably (touch wood).
Posts: 1,028
SamK
Joined: 21 Aug 2011
#6
MommaBear wrote:A very old Proteva desktop/minitower
A model and preferably a link to the manufacturer/user manual might be helpful.

Are you certain this desktop/tower unit contains stereo loudspeakers rather than only a simple mono beep sounder? A peek inside the case will confirm this and also give you an opportunity to check the loudspeaker cables to ensure they have not become disconnected. If they have detached it might account for the symptoms you reported.
MommaBear wrote:I found quite a few posts on the web about it.
If they are relevant to the posted matter,"Sound from external speakers, but not internal" the links might provide an insight into the matter.
Posts: 17
MommaBear
Joined: 22 Aug 2015
#7
SamK wrote:
MommaBear wrote:A very old Proteva desktop/minitower
A model and preferably a link to the manufacturer/user manual might be helpful.
The machine is a hand-me-down, no manuals. IIRC, it was built from parts at Staples.
SamK wrote:Are you certain this desktop/tower unit contains stereo loudspeakers rather than only a simple mono beep sounder?
See my original post. I was hoping something in the programs that give system info would tell me this. I did google how do I know if I have internal speakers but didn't find anything.
SamK wrote:A peek inside the case will confirm this and also give you an opportunity to check the loudspeaker cables to ensure they have not become disconnected. If they have detached it might account for the symptoms you reported.
Off to find a screwdriver ...
SamK wrote:
MommaBear wrote:I found quite a few posts on the web about it.
If they are relevant to the posted matter,"Sound from external speakers, but not internal" the links might provide an insight into the matter.
Again, see my original post. I can't find alsa-base.conf or /var/lib/alsa/asound.state or .asoundrc on this antiX15 install. But altering these files were suggested fixes.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#8
MommaBear wrote:The machine is a hand-me-down, no manuals. IIRC, it was built from parts at Staples.
Post the output of

Code: Select all

inxi -F
. This will include the motherboard details. In turn that will enabale you to search the web for manual for it. Hopefully, the manual will give details of the sound hardware and type of expansion slots. When you find it post the link.

MommaBear wrote:I can't find alsa-base.conf or /var/lib/alsa/asound.state or .asoundrc...
.asoundrc will not exist unless you create it yourself. It is a file which you would only use if you want to manage your alsa configuration. asound.state is usually saved automatically by antiX. It is a way of making your volume settings persist between boot ups. It is possible that it has not been created because the sound issues.
Posts: 17
MommaBear
Joined: 22 Aug 2015
#9
SamK, thanks for your patience.

Motherboard Gigabyte model: 7VKML v: 1.x


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.gigabyte.com/products/product-page.aspx?pid=1306#ov"
linktext was:"http://www.gigabyte.com/products/produc ... id=1306#ov"
====================================
I think this is the same one.
MommaBear wrote:I can't find alsa-base.conf or /var/lib/alsa/asound.state or .asoundrc...
SamK wrote:.asoundrc will not exist unless you create it yourself. It is a file which you would only use if you want to manage your alsa configuration. asound.state is usually saved automatically by antiX. It is a way of making your volume settings persist between boot ups. It is possible that it has not been created because the sound issues.
Thanks for the info. I had no idea about either one.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#10
It will be unwise to continue without the previously requested information.

Visual inspection with the case removed will remove all doubt about whether a pair of stereo loudspeakers are present (rather than a single mono sounder) and if they are present their cables have not become disconnected.

This is an essential step as it will potentially remove the need for further investigation. If it reveals internal stereo loudspeakers are not present, external loudspeakers will be required.

It will also give an opportunity to verify (and confirm in the forum) the motherboard details correspond to the information you posted. It is common practice for the manufacturer to stencil the make and model details onto the motherboard.


A system configuration report will provide a basic description of your system components together with their set up. It gives context to your reported issue.

In a terminal run the following command

Code: Select all

inxi -F -c 0
Post the results in the forum by copying and pasting within code tags.
Posts: 17
MommaBear
Joined: 22 Aug 2015
#11
Sorry again for the delay replying. I've never opened a computer case, didn't even have the right screwdriver. Then I realized I had no idea what internal speakers would look like, went googling.
SamK wrote:Visual inspection with the case removed will remove all doubt about whether a pair of stereo loudspeakers are present (rather than a single mono sounder) and if they are present their cables have not become disconnected.
So it seems there aren't any speakers in here. I realize now I asked the wrong question. The question should have been, Can I tell with software if I have internal speakers? The answer appears to be no.

I hope I haven't wasted too much of your time. At least I'll know where to start if I run into the problem again.

Thanks for your time.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#12
Must be something in the air

Instead of giving the link with all the advertisements. Here is just a quick quote.
trying to get internal sound to work

HI,

I had been using an old Labtech pulse 485 speaker system with my desktop machine, a System 76 Ratel running Ubuntu 14.04. The system 76 forum seems to have gone comatose, so I am trying here.

The external speakers are broken, and I don't want to try to repair them. I would rather use internal system sound, but I can't seem to get it to work. I tried both analog and digital using System -> Sound, rebooted, and checked for volume control and muting, but nothing worked. I assume there must be some sort of internal sound system there, how do I get it working?

Thanks.
<snip replies>
OK, after taking a look inside, although there is an internal sound connection, there is no internal speaker. No wonder it didn't work.

Sorry to waste people's time.
Posts: 17
MommaBear
Joined: 22 Aug 2015
#13
rokytnji, thanks for taking the time to post this. It made me feel better, knowing I'm not the only one.