MX Linux Forum

Posted: **Mon Jan 13, 2020 11:51 am**

Hi everyone. I'm having some issues getting audio files to work correctly. I've also tried to use this link as a reference which didn't work, due to a lack of alsamixer? https://forums.linuxmint.com/viewtopic. ... 2&t=264417

The system is an Asus EeePC Netbook on which I installed MX Linux 18.3
Everything works perfectly with only 1GB of RAM and I can't believe how fast (relatively speaking) everything is.
This Netbook only has an Atom N455 Processor. The model is an EeePC R101D.

If I connect external speakers the sound works fantastic on everything. MP3, WAV, MP4, FLV, MKV, AVI, all of them audible with external speakers which are connected to the headphone jack. Since I couldn't use the above reference becaue of not being able to find alsamixer on the system and sudo apt-get install alsamixer not working, I went ahead and pulled in spotify as well as audacity, hoping that between the two I'll get whatever I'm misson on the system. Didn't do me any good though. I also tried fiddling with the pulse audio settings and the VLC audio settings while playing back an MP3 file. That didn't work either.
I would really love to get the speakers working on this netbook. I'm sure that there's nothing wrong with them because I've been able to find this problem Online a lot, speaker sound + linux not being compatible out of the box with the Asus EeePC Netbooks. Anyone have some easy to follow tricks up their sleeve that might work for me? Thanks.

.

Posted: **Mon Jan 13, 2020 1:31 pm**

I have alsamixer on my MX-18 installs. Have you tried starting it from the command line? Maybe you have to use sudo?

Usually I solve these issues by running alsamixer and turning everything on/up one at a time until I get sound. There could also be a key combo on the netbook that disables the speakers, or sometimes a switch/roller.

Maybe Pulseaudio is getting in the way? Maybe try a LiveUSB and remove PulseAudio?

Seaken64

Posted: **Mon Jan 13, 2020 1:35 pm**

Have you tried MX sound select?

Posted: **Mon Jan 13, 2020 1:49 pm**

Beratung wrote: Mon Jan 13, 2020 11:51 am I've also tried to use this link as a reference which didn't work, due to a lack of alsamixer? https://forums.linuxmint.com/viewtopic. ... 2&t=264417

Did you try adding the suggested line to /etc/modprobe.d/alsa-base.conf?

Code: Select all

options snd-hda-intel model=headset-mic

The alsamixer program is supplied by the alsa-utils package but PulseAudio is supposed to be controlling the sound in MX so I don't think that will work.

Posted: **Mon Jan 13, 2020 2:16 pm**

ForWIW wrote: Mon Jan 13, 2020 1:36 pm uninstalling pulseaudio is NOT a good idea as many apps depend on it ...

True, but as a troubleshooting device it might be best to go back to the alsa tools. That's why I recommended using a LiveUSB.

Seaken64

Posted: **Mon Jan 13, 2020 6:42 pm**

HI

options snd-hda-intel model=headset-mic

IMHO this is wrong. see link
https://github.com/spotify/linux/blob/m ... Models.txt

search for 269 gives us model=strings of

ALC269
======
basic Basic preset
quanta Quanta FL1
eeepc-p703 ASUS Eeepc P703 P900A
eeepc-p901 ASUS Eeepc P901 S101
fujitsu FSC Amilo
lifebook Fujitsu Lifebook S6420
auto auto-config reading BIOS (default)

but OP

The model is an EeePC R101D

my old HD-Audio-Models.txt shows
ALC269/270/275/276/28x/29x
======
laptop-amic Laptops with analog-mic input
laptop-dmic Laptops with digital-mic input
alc269-dmic Enable ALC269(VA) digital mic workaround
alc271-dmic Enable ALC271X digital mic workaround
inv-dmic Inverted internal mic workaround
lenovo-dock Enables docking station I/O for some Lenovos
dell-headset-multi Headset jack, which can also be used as mic-in
dell-headset-dock Headset jack (without mic-in), and also dock I/O

so my suggestion is to edit with root powers the file
/etc/modprobe.d/alsa-base.conf
and have only one line in there
first attempt contents will be

options snd-hda-intel model=auto

full reboot to test

if fails then change that line to read

options snd-hda-intel model=laptop-amic

we may have to change that as I am only guessing you have anolog microphone see below. If you do have a digital mic
we would have more options. NOTE that these model numbers change when we update our kernels.
The first link is for the latest kernel. YMMV

2) we can also add other parameters as per

Code: Select all

modinfo snd_hda_intel
filename:       /lib/modules/4.19.0-6-amd64/kernel/sound/pci/hda/snd-hda-intel.ko
description:    Intel HDA driver
license:        GPL
alias:          pci:v00001022d*sv*sd*bc04sc03i00*
alias:          pci:v00001002d*sv*sd*bc04sc03i00*
alias:          pci:v000015ADd00001977sv*sd*bc*sc*i*
alias:          pci:v000017F3d00003010sv*sd*bc*sc*i*
alias:          pci:v000013F6d00005011sv*sd*bc*sc*i*
alias:          pci:v00001102d00000009sv*sd*bc*sc*i*
alias:          pci:v00001102d00000012sv*sd*bc*sc*i*
alias:          pci:v00001102d00000010sv*sd*bc*sc*i*
alias:          pci:v00006549d00002200sv*sd*bc*sc*i*
alias:          pci:v00006549d00001200sv*sd*bc*sc*i*
alias:          pci:v000010DEd*sv*sd*bc04sc03i00*
alias:          pci:v000010B9d00005461sv*sd*bc*sc*i*
alias:          pci:v00001039d00007502sv*sd*bc*sc*i*
alias:          pci:v00001106d00009140sv*sd*bc*sc*i*
alias:          pci:v00001106d00009170sv*sd*bc*sc*i*
alias:          pci:v00001106d00003288sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAF0sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAE0sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAE8sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAD8sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAC8sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAC0sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAB0sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAA8sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AAA0sv*sd*bc*sc*i*
alias:          pci:v00001002d00009902sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA98sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA90sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA88sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA80sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA68sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA60sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA58sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA50sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA48sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA40sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA38sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA30sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA28sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA20sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA18sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA10sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA08sv*sd*bc*sc*i*
alias:          pci:v00001002d0000AA00sv*sd*bc*sc*i*
alias:          pci:v00001002d00009840sv*sd*bc*sc*i*
alias:          pci:v00001002d0000970Fsv*sd*bc*sc*i*
alias:          pci:v00001002d0000960Fsv*sd*bc*sc*i*
alias:          pci:v00001002d00007919sv*sd*bc*sc*i*
alias:          pci:v00001002d0000793Bsv*sd*bc*sc*i*
alias:          pci:v00001002d000015B3sv*sd*bc*sc*i*
alias:          pci:v00001002d0000157Asv*sd*bc*sc*i*
alias:          pci:v00001002d00001308sv*sd*bc*sc*i*
alias:          pci:v00001002d00000002sv*sd*bc*sc*i*
alias:          pci:v00001022d000015E3sv*sd*bc*sc*i*
alias:          pci:v00001022d0000157Asv*sd*bc*sc*i*
alias:          pci:v00001022d00001457sv*sd*bc*sc*i*
alias:          pci:v00001022d0000780Dsv*sd*bc*sc*i*
alias:          pci:v00001002d00004383sv*sd*bc*sc*i*
alias:          pci:v00001002d0000437Bsv*sd*bc*sc*i*
alias:          pci:v00008086d*sv*sd*bc04sc03i00*
alias:          pci:v00008086d00003A6Esv*sd*bc*sc*i*
alias:          pci:v00008086d00003A3Esv*sd*bc*sc*i*
alias:          pci:v00008086d0000293Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000293Esv*sd*bc*sc*i*
alias:          pci:v00008086d0000284Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000269Asv*sd*bc*sc*i*
alias:          pci:v00008086d000027D8sv*sd*bc*sc*i*
alias:          pci:v00008086d00002668sv*sd*bc*sc*i*
alias:          pci:v00008086d00002284sv*sd*bc*sc*i*
alias:          pci:v00008086d00000F04sv*sd*bc*sc*i*
alias:          pci:v00008086d0000080Asv*sd*bc*sc*i*
alias:          pci:v00008086d0000811Bsv*sd*bc*sc*i*
alias:          pci:v00008086d00003B56sv*sd*bc*sc*i*
alias:          pci:v00008086d0000160Csv*sd*bc*sc*i*
alias:          pci:v00008086d00000D0Csv*sd*bc*sc*i*
alias:          pci:v00008086d00000C0Csv*sd*bc*sc*i*
alias:          pci:v00008086d00000A0Csv*sd*bc*sc*i*
alias:          pci:v00008086d00003198sv*sd*bc*sc*i*
alias:          pci:v00008086d00001A98sv*sd*bc*sc*i*
alias:          pci:v00008086d00005A98sv*sd*bc*sc*i*
alias:          pci:v00008086d000034C8sv*sd*bc*sc*i*
alias:          pci:v00008086d00009DC8sv*sd*bc*sc*i*
alias:          pci:v00008086d0000A348sv*sd*bc*sc*i*
alias:          pci:v00008086d0000A2F0sv*sd*bc*sc*i*
alias:          pci:v00008086d00009D71sv*sd*bc*sc*i*
alias:          pci:v00008086d0000A171sv*sd*bc*sc*i*
alias:          pci:v00008086d00009D70sv*sd*bc*sc*i*
alias:          pci:v00008086d0000A170sv*sd*bc*sc*i*
alias:          pci:v00008086d00009CA0sv*sd*bc*sc*i*
alias:          pci:v00008086d00009C21sv*sd*bc*sc*i*
alias:          pci:v00008086d00009C20sv*sd*bc*sc*i*
alias:          pci:v00008086d0000A270sv*sd*bc*sc*i*
alias:          pci:v00008086d0000A1F0sv*sd*bc*sc*i*
alias:          pci:v00008086d00008D21sv*sd*bc*sc*i*
alias:          pci:v00008086d00008D20sv*sd*bc*sc*i*
alias:          pci:v00008086d00008CA0sv*sd*bc*sc*i*
alias:          pci:v00008086d00008C20sv*sd*bc*sc*i*
alias:          pci:v00008086d00001E20sv*sd*bc*sc*i*
alias:          pci:v00008086d00001D20sv*sd*bc*sc*i*
alias:          pci:v00008086d00001C20sv*sd*bc*sc*i*
depends:        snd-hda-core,snd-hda-codec,snd-pcm,snd
retpoline:      Y
intree:         Y
name:           snd_hda_intel
vermagic:       4.19.0-6-amd64 SMP mod_unload modversions 
parm:           index:Index value for Intel HD audio interface. (array of int)
parm:           id:ID string for Intel HD audio interface. (array of charp)
parm:           enable:Enable Intel HD audio interface. (array of bool)
parm:           model:Use the given board model. (array of charp)
parm:           position_fix:DMA pointer read method.(-1 = system default, 0 = auto, 1 = LPIB, 2 = POSBUF, 3 = VIACOMBO, 4 = COMBO, 5 = SKL+, 6 = FIFO). (array of int)
parm:           bdl_pos_adj:BDL position adjustment offset. (array of int)
parm:           probe_mask:Bitmask to probe codecs (default = -1). (array of int)
parm:           probe_only:Only probing and no codec initialization. (array of int)
parm:           jackpoll_ms:Ms between polling for jack events (default = 0, using unsol events only) (array of int)
parm:           single_cmd:Use single command to communicate with codecs (for debugging only). (bint)
parm:           enable_msi:Enable Message Signaled Interrupt (MSI) (bint)
parm:           patch:Patch file for Intel HD audio interface. (array of charp)
parm:           beep_mode:Select HDA Beep registration mode (0=off, 1=on) (default=1). (array of bool)
parm:           power_save:Automatic power-saving timeout (in second, 0 = disable). (xint)
parm:           pm_blacklist:Enable power-management blacklist (bool)
parm:           power_save_controller:Reset controller in power save mode. (bool)
parm:           align_buffer_size:Force buffer and period sizes to be multiple of 128 bytes. (bint)
parm:           snoop:Enable/disable snooping (bint)

but that may scare the OP?

3) How about a screenshot of your sound device and some outputs please

post your screenshot to ingur.com and then link to it please
and show the outputs to

Code: Select all

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

Code: Select all

I will show my proc asound devices snippet as I have a digital mic but hoping yours is analog
cat /proc/asound/devices   NOT OP
  2: [ 1- 0]: digital audio playback
  3: [ 1- 0]: digital audio capture
  4: [ 1- 1]: digital audio playback
  5: [ 1- 2]: digital audio capture
  6: [ 1- 3]: digital audio playback
  7: [ 1- 7]: digital audio playback
  8: [ 1- 8]: digital audio playback
  9: [ 1- 9]: digital audio playback
 10: [ 1-10]: digital audio playback
 11: [ 1- 0]: hardware dependent
 12: [ 1- 2]: hardware dependent
 13: [ 1]   : control
 33:        : timer

Posted: **Mon Jan 13, 2020 8:02 pm**

YIKES that model R101D appears to be the same as 1001 "something" link
https://wiki.debian.org/DebianEeePC/HowTo/Sound

and in both LM and debian wiki links.....images show various models, so it is important to see what your /proc/asound/pcm result is in above request.

Posted: **Tue Jan 14, 2020 2:20 am**

Well, the R101D Model is part of the problem for me.
Using Thunar as root, there is no ... /etc/modprobe.d/alsa-base.conf ... for me to find.

That's actually the reason why I posted here, because I thought it might have something spoecific to do with MX Linux?
I'll go through all of the posted responses as I find the time today and will follow-up with results in the next day or two.
Thanks.

.

Posted: **Tue Jan 14, 2020 3:41 am**

ahh well just make one....it does not have to have that name but here is how

Code: Select all

sudo su
echo 'options snd-hda-intel model=auto' > /etc/modprobe.d/alsa-base.conf

and then use root powers to edit the model=string if that fails

Posted: **Tue Jan 14, 2020 7:13 pm**

ForWIW wrote: Tue Jan 14, 2020 4:09 pm @ aus9 said
... the packages (alsa-base, linux-sound-base) don't exist in MX or recent Debian (Stretch/Buster) ... these are necessary for your assertion that alsa-base.conf works! ... without them your "fix" is worthless.

@ForWIW, please calm down. The advice given by @aus9 is correct.
The name of the conf-file within /etc/modprobe.d/ is irrelevant.
The content of the file within /etc/modprobe.d is more relevant

Code: Select all

options snd-hda-intel model=auto

which is just an instruction to the kernel to load the module snd-hda-intel with option-parameter "model=auto"
Based on OP's finding a potential better option to test might "model=headset-mic" .
Note, further to check/test kernel instructions to load module with specific options,
it is sufficient to at a kernel parameter with the GRUB menu to the linux-line in form of
e.g
snd-hda-intel.model=auto
snd-hda-intel.model=headset-mic

Posted: **Wed Jan 15, 2020 2:24 am**

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

Posted: **Wed Jan 15, 2020 7:42 am**

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

Posted: **Wed Jan 15, 2020 4:20 pm**

ForWIW wrote: Wed Jan 15, 2020 4:10 pm 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.

Posted: **Wed Jan 15, 2020 7:43 pm**

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

Posted: **Thu Jan 16, 2020 5:37 am**

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

Posted: **Sat Jan 18, 2020 6:06 am**

@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.

.

Posted: **Sat Jan 18, 2020 7:04 am**

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

.

Posted: **Sat Jan 18, 2020 7:45 am**

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

Posted: **Sat Jan 18, 2020 9:00 am**

@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.

.

Posted: **Sat Jan 18, 2020 9:45 am**

Moderator.

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

Posted: **Sat Jan 18, 2020 6:16 pm**

@Beratung

I believe your best solution it to post to the other member's post link in post 25

richb
I believe this member has shown me dis-respect in refusing to answer my questions from Jan14.

Bye

Posted: **Mon Jan 20, 2020 2:34 am**

@ForWIW

I really don't understand what you want me to do with this line here?

Code: Select all

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

Do you actually want me to place that entire line, exactly as you presented it here, within the mod.conf file ???

@aus9

I'm sorry that you're offended and that your english skills aren't good enough to understand that I'm doing the best that I can and that with the many many replies here, it actually became more difficult to respond ... not just to you personally, but also to others. If you become "peeved" so easily and feel "disrespected" then by all means feel free not to respond to my questions anymore. If you feel the need to respond to this, please send me a PM and let's stop writing posts like these in the forum where they don't belong. Patience is a virtue! Thank you.

.

Posted: **Tue Jan 21, 2020 6:10 pm**

Beratung, forget about alsamixer, MX does not use it directly.

My advice is to use PulseAudio Volume Control, because MX uses pulseaudio for all sounds.
PulseAudio Volume Control is a very comprehensive tool - more than its title might suggest.

I use MX and PAVC on several eeePCs without any problems.

Posted: **Wed Jan 22, 2020 8:02 am**

Bump - hope Beratung will see it.

Posted: **Wed Jan 22, 2020 8:37 am**

Mod note: He will not be able to reply, he got himself banned.

Posted: **Wed Jan 22, 2020 10:36 am**

Eadwine Rose wrote: Wed Jan 22, 2020 8:37 am Mod note: He will not be able to reply, he got himself banned.

Thanks for info, Eadwine. Why was he banned?

Posted: **Wed Jan 22, 2020 10:37 am**

We do not disclose that information.

Posted: **Wed Jan 22, 2020 10:42 am**

Eadwine Rose wrote: Wed Jan 22, 2020 10:37 am We do not disclose that information.

Understood.
An intriguing mystery!

Posted: **Wed Jan 22, 2020 1:12 pm**

Beratung was banned.

Posted: **Wed Jan 22, 2020 5:03 pm**

Beratung, you cannot post due to the mysterious banning but you can still read the messages.

You should forget all the "alsamixer" nonsense, do a fresh MX install on the eeePC and use
"PulseAudio Volume Control" to get the laptop speakers working.

That is how I have made several eeePCs run with usable audio from the internal speakers.
If it fails for you I suspect your eeePC is faulty.

Posted: **Thu Jan 23, 2020 10:39 am**

Alsamixer is not nonsense, but MX does not use it directly.

Note: my working eeePCs are on MX18, not MX19; don't know whether this makes any difference.

Posted: **Thu Jan 23, 2020 12:28 pm**

@ForWIW
We seem to agree: my only caveat is that re-installation is very quick and easy with the live USB.

Posted: **Thu Jan 23, 2020 5:49 pm**

@ForWIW,

I learned a lot from this thread. Don't think your efforts were in vain just because the OP didn't get to collaborate fully. A lot of us lurk and read these topics even if we don't have the skills to participate in the technical aspects of the discussion.

Thanks,
Seaken64

MX Linux Forum

Sound from External speakers but NOT AT ALL from Notebook

Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook

Re: Sound from External speakers but NOT AT ALL from Notebook