Sound from External speakers but NOT AT ALL from Notebook

[aus9]

Gentlemen, I am glad that we all have passion and want to help.

biased summary of Original Post by Original Poster. A link provided info for a specific model for a certain alsa config file and it did not work as OP did not have that file.

I tried to point out.....the alsa options vary with the kernel and unfortunately we still are introducing confusion on the exact options OP can try.

I notice that fehlix has offered "model=headset-mic" and not sure where he got that from when in post 8 I named 2 sets that might apply NONE contain that string.

In post 12 ForWIW thought that /etc/modprobe.d/alsa-base.conf might be obsolete?
I can assure that member that I am on MX 19 64 bit.....and I tested a file with contents NOT FOR OP that contained
options snd-hda-intel index=1 rebooted and as aplay -l shows I have only one card and its now card=1 but 7 sub-devices of hdmi and analog (PCH)
alsamixer -c0 gives an error......because my card is now on card 1. Don't worry I have deleted that file and rebooted.
And my point is.....alsa can use that config file.

But ForWIW does raise a significant question....that I missed in post 1 and elsewhere.

questions
########
Does OP have a bios setting that can configure onboard sound?

Has OP tested the actual speakers using a different operation system before installing MX?

And seaken64 mentions to try a live USB

and thanks for your patience

[fehlix]

See still some confusion here, re module loading modprobe and kernel parameter.

First step would be to to get the audio device information.
A good start might be
inxi -Fxxxz

or for audio only

inxi -Axxx

Further as already mentioned the audio model string might als be shown with

aplay -l
or
aplay -L

Assume now we found and audio-model
e.g this one:
ALC269

Let's look into the kernel specfifc doc, e.g for kernel 4.19* we get this doc with

sudo apt install linux-doc-4.19

Let's look for the example audio model ALC269
here
file:///usr/share/doc/linux-doc-4.19/html/sound/hd-audio/index.html
and

file:///usr/share/doc/linux-doc-4.19/html/sound/hd-audio/models.html#alc22x-23x-25x-269-27x-28x-29x-and-vendor-specific-alc3xxx-models
where we find quite a lot of model options
including this one:

headset-mic
Indicates a combined headset (headphone+mic) jack

How to apply an option to the sound module "snd-hda-intel" (or how find out whether it helps to sort the issue)

Let's have a look here:

file:///usr/share/doc/linux-doc-4.19/html/admin-guide/kernel-parameters.html
where we find:

Module parameters can be specified in two ways: via the kernel command line with a module name prefix, or via modprobe, e.g.:

(kernel command line) usbcore.blinkenlights=1
(modprobe command line) modprobe usbcore blinkenlights=1

So we can try the option available for the identified hd-audio model
e.g. as kernel parameter

snd-hda-intel.model=headset-mic

for testing add manually to the grub-menu entry as kernel parameter
and permamently to the GRUB_CMDLINE_LINUX within /etc/default/grub

or for modprobe using the conf-files files within /etc/modprobe.d
e.g within a new file /etc/modprobe.d/snd-hda-intel.conf
with a content
options snd-hda-intel model=headset-mic

After we have applied the audio model specific modprobe instructions
which fixes the issues we can further fine-tune with alsa and pulsaudio.
HTH

[fehlix]

My question, then, would it be better to create the file content as options snd-hda-intel model=generic in this case? ...

So you finally see the light
The use the option parameter manually entered as the kernel parameter is just only for testing to see it works.
To permanently fix, it would probably best to create a new conf-file within that /etc/modprobe.d conf-directory.
From kernel perspective it does not matter, where the options comes from as the kernel initiated modprobes inspect first the kernel "command line" parameter ( see this: cat /proc/cmdline) and then the /etc/modprobe.d/*.conf files.

[aus9]

grumpy is back

thanks for the doc which I have just viewed fehlix.

ALC22x/23x/25x/269/27x/28x/29x (and vendor-specific ALC3xxx models)

that does not help IMHO.

It means that we have to try each model=string and can not eliminate the alc3 series because its included models with the 2 series.

in post 8 section 3 I asked

Code: Select all

aplay -l
aplay -L
cat /proc/asound/devices
cat /proc/asound/pcm

and gave reasons too. Namely does OP have a digital mic or analog so
being grumpy.....I will now spit the dummy and refuse to help unless Beratung posts the output to those questions.

Gentlemen....you may feel I am being too grumpy.....but we have wasted a number of pages because the OP elects which info to share.....and has not posted recently.....maybe scared off by our chat.

So be it....I accept that....believe or not

Good night

[aus9]

ignoring software, thanks to ForWIW I dl the English mobo manual and report

There are hardware keys to mute/unmute the speaker
Fn + F10

There are hardware keys to lower/raise volume etc
Fn + F11/F12

on page 49 it says the model is EEE PC 1001 PX

For OP info if interested

[Beratung]

@ForWIW @Everyone else ...

Utilizing Thunar as root, I created the needed .conf file and inserted booth lines between reboots. Actually I inserted both of them at the same time and then just kept one of them disabled while the other one was being enabled/tested. Both lines worked i.e. the sound worked just fine from the external speakers, but not at all from the internal speakers. Each line was tested individually after a reboot.

MX Paket Manager had no Alsa anywhere. I searched every category individually as well as by using the searchbox. Finally, by actually getting into the MX Menu, I was able to see that Alsamixer was there, greyed out, and hidden. So I unchecked "hidden" and then the Alsamixer showed up in the Start/Multimedia option menu. But no matter what I did within Alsamixer, I was never able to generate any sound out of the internal speakers of the EeePC. The tiny 3 watt external speakers on the other hand sound friggen fantastic, and they're pretty loud too.

Okay, back to Alsa ... which provides options for soundcard selection with the F6 key. There was only the default option and one additional option, so testing both of those with music playing was no problem. No such luck, music played on the external speakers no matter what was selected, but not at all on the internal speakers. I'm beginning to wonder if this EeePC even has internal speakers since there's nothing visible on the face of the keypad body ... ???
Also, using F2 key in Alsa provides multiple selections, but I wouldn't know what to do with those.

Part of the soundcard selection process in Alsa showed me that when I moved the volume up and down, absolutely NOTHING happened for the volume bars in Alsa. I might be getting a little mixed up here since I'm on another computer and just going by memory. In any case, when I switched Alsa back to the original option which just displayed single sound/volume bar in the center, the the volume actually turned up and down when I moved the volume with the mouse from the XFCE panel. I'm thinking that perhaps I should just remove the file which was created in etc/whatever ... and then go back to starting over with Alsa only?
There are just too many options, too many functions, and between them all ... too much confusion. Not giving up yet though.

.

[Beratung]

Also, when I utilize the F6 key and view the options on the bottom of the screen ...
one of those is Auto-Mute and that one appears to be enabled. Perhaps that's the problem?

There's actually another post right here on the forum with a solution. But aside from installing alsa, the user didn't explain which commands to use or enter where, so to me the whole thing looks a little confusing without any kind of explanation for the steps whch this user took:
viewtopic.php?t=43687

Last but not least, here's the system info:

Code: Select all

System:
  Host: Kernel: 4.15.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0 
  Desktop: Xfce 4.12.3 Distro: MX-18.3_386 Continuum March 12  2017 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Laptop System: ASUSTeK product: 1001PXD v: x.x serial: <filter> 
  Mobo: ASUSTeK model: 1001PXD v: x.xx serial: <filter> 
  BIOS: American Megatrends v: 0703 date: 04/12/2011 
Battery:
  ID-1: BAT0 charge: 19.9 Wh condition: 20.2/23.8 Wh (85%) 
  model: ASUS 1001PXD status: Unknown 
CPU:
  Topology: Single Core model: Intel Atom N455 bits: 64 type: MT 
  arch: Bonnell rev: A L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6665 
  Speed: 1000 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1000 2: 1000 
Graphics:
  Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
  vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.2 driver: intel 
  unloaded: fbdev,modesetting,vesa resolution: 1024x600~60Hz 
  OpenGL: renderer: Mesa DRI Intel Pineview M x86/MMX/SSE2 
  v: 1.4 Mesa 18.2.6 direct render: Yes 
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k4.15.0-1-686-pae 
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: ASUSTeK 
  driver: atl1c v: 1.0.1.1-NAPI port: ec00 bus ID: 01:00.0 
  IF: eth0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter 
  vendor: AzureWave AW-NE785 / AW-NE785H 802.11bgn driver: ath9k v: kernel 
  port: ec00 bus ID: 02:00.0 
  IF: wlan0 state: down mac: <filter> 
  Device-3: D-Link DWA-140 RangeBooster N Adapter(rev.B3) [Ralink RT5372] 
  type: USB driver: rt2800usb bus ID: 1-3:3 
  IF: wlan1 state: up mac: <filter> 
Drives:
  Local Storage: total: 298.09 GiB used: 8.23 GiB (2.8%) 
  ID-1: /dev/sda vendor: Seagate model: ST9320325AS size: 298.09 GiB 
Partition:
  ID-1: / size: 284.53 GiB used: 8.23 GiB (2.9%) fs: ext4 dev: /dev/sda2 
  ID-2: swap-1 size: 8.00 GiB used: 264 KiB (0.0%) fs: swap dev: /dev/sda1 
Sensors:
  System Temperatures: cpu: 63.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb https://mirrors.evowise.com/mxlinux-packages/antix/stretch/ stretch main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.de.debian.org/debian/ stretch-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.de.debian.org/debian/ stretch main contrib non-free
  2: deb http://security.debian.org/ stretch/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb https://mirrors.evowise.com/mxlinux-packages/mx/repo/ stretch main non-free
  Active apt repos in: /etc/apt/sources.list.d/spotify.list 
  1: deb http://repository.spotify.com testing non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list 
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
  1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 175 Uptime: 1h 36m Memory: 993.4 MiB used: 295.7 MiB (29.8%) 
  Init: systemd runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 
  inxi: 3.0.36 

.

[aus9]

when I utilize the F6 key and view the options on the bottom of the screen ...
one of those is Auto-Mute and that one appears to be enabled. Perhaps that's the problem?

No ......auto-mute means.....when you plug in headphones.....speakers auto mute

and you may expect me to help you when you still refuse to reply with the results of commands requested at post 20

Secondly your link appears to say that .....this speaker you can not find is only a mono speaker and not a stereo (2 channel speaker)
Be careful what you ask for ....your external speakers sound great.

MX Menu, I was able to see that Alsamixer was there, greyed out, and hidden

Do you have any explanation of how it was hidden in the menu but you could see it?

Now if you do not want me to help you.....just say so. I get peeved off when I make a request at post 8, you ignore it
I repeat it at post 20 and you ignore it......Just say the word and I will not post on this thread again.
and I will respect your decision.

cheers

[Beratung]

@aus9

I don't know why you're being so impatient. There were quite a few replies for me to go through and consequently it's not easy to be as accommodating as you might expect. That EeePC is in another room, so I have to go back and forth with a USB stick for easy information access, testing, copying files with information for you, etc. etc. etc. And it's not like I have nothing else to do either, so a little patience would go a long way. Thank you. Here's a copy of the actual snd-hda-intel.conf which I created. I have no idea if that information was entered correctly, but that's the file that I created for that EeePC netbook.

Code: Select all

#Newly created file to get internal sound to work.
#
#If enabled line below doesn't work, try this next one instead.
#
#options snd-hda-intel model=generic

options snd-hda-intel model=headset-mic

Even though the sound is excellent, the external speakers are not an option since I'll be giving the EeePC to a child for their first computer. The external speakers with their wires are too cumbersome to be carrying around.

.

[richb]

Moderator.

Please keep your responses to the title of this thread and not personalize That is not helpful.