LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices


Reply
  Search this Thread
Old 04-29-2017, 04:37 PM   #1
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Rep: Reputation: Disabled
Sound issues ( Distortion and High Pitched Noise) with any kernel version superior to 3.2 in different distributions


Hi first let me say that English it's not my mother language, so i ask for forgiveness for my bad spelling and inappropriate way of expressing beforehand.

Second this is my first time asking help in a forum, and i apologize if i put it in the wrong section for lack of experience.

Well i will begin telling you that my problem is in different OS's, i mean i have proved Linux mint 18.1, Debian Jessie 8.7 and fedora 25, and all have this issues all coming from the headphones and the speakers:
1. Distorted sound
2. High pitched noise

After numerous intents of trial and error i discovered that the problem is in the kernel, the kernel 3.2.0 don't give me any problems at all in fact it solves everything, except that i can't use mpv, whine and other programs that depend on new kernels versions. The problem itself seems to lie in a single channel the PCM loopback, apparently the "big" difference in this version, when is activated the sound become the same as in the other versions.

The High Pitched Noise is only heard when is not muted and i was able to partially low the distortion editing /etc/pulse/daemon.conf uncommenting the line realtime-scheduling = yes and changing the value from 10 to 5 in the parameter default-fragment-size-msec

I have proved with clean installations in UEFI mode and Legacy BIOS mode with 32 and 64 bits images. All disabling intel_pstate just in case

If there is a way to solve my problem without depending in the installing and use of other kernels i will be deeply grateful.

I have a BANGHO max 1524 with vt1802. Others details:

lspci -v | grep -i audio
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)

lsmod | grep snd
snd_hda_codec_hdmi 30824 1
snd_hda_codec_via 41160 1
snd_hda_intel 26259 5
snd_hda_codec 78031 3 snd_hda_intel,snd_hda_codec_via,snd_hda_codec_hdmi
snd_hwdep 13186 1 snd_hda_codec
snd_pcm 68083 4 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc 13003 2 snd_pcm,snd_hda_intel
snd_seq_midi 12848 0
snd_seq_midi_event 13316 1 snd_seq_midi
snd_rawmidi 23163 1 snd_seq_midi
snd_seq 45222 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 22930 3 snd_seq,snd_pcm
snd 52893 18 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_c odec_via,snd_hda_codec_hdmi
soundcore 13065 1 snd

cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7d10000 irq 44
 
Old 04-30-2017, 11:39 AM   #2
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
Is the mic enabled? Is that what you want? You're probably creating feedback. Turning down the mic or off completely (muted) might help rid yourself of that feedback. On cheaper sound devices, there's crossover between the lines. Even if you have no physical hardware plugged into the mic port. There's also plugin power to power certain mic types which tends to add noise to the line.

Loopback though is more for special use cases. I have not had it enabled by default. But I tend to do minimal installs and build up as I need things.

$ sudo modprobe snd-aloop

or modprobe -r to remove it. It's not needed unless you are doing some sort of fancy setup. Alsa + Jack + Pulse??? I tend to do a pulse over jack setup, but still don't use the loopback features.

$ aplay -l
$ cat /proc/asound/cards
 
Old 04-30-2017, 01:47 PM   #3
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
open alsamixer, press F4 and make sure all capture channels are turned down to zero or muted.
 
Old 04-30-2017, 04:58 PM   #4
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Original Poster
Rep: Reputation: Disabled
Ondoho:
I has already proved with muting the capturing channels and it didn't work.

Shadow 7:
$ sudo modprobe snd-aloop creates a loopback mixer but is separate from the others channels in the HDA Intel PCH default card from alsamixer and it doesn't do nothing.

$ sudo modprobe -r

modprobe: ERROR: missing parameters. See -h.

$ aplay -l
**** List of PLAYBACK hardware devices ****
Card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
Sub devices: 0/1
Subdevice # 0: subdevice # 0
Card 0: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog]
Sub devices: 1/1
Subdevice # 0: subdevice # 0
Card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Sub devices: 1/1
Subdevice # 0: subdevice # 0
Card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
Sub-Devices: 7/8
Subdevice # 0: subdevice # 0
Subdevice # 1: subdevice # 1
Subdevice # 2: subdevice # 2
Subdevice # 3: subdevice # 3
Subdevice # 4: subdevice # 4
Sub-device # 5: subdevice # 5
Subdevice # 6: subdevice # 6
Subdevice # 7: subdevice # 7
Card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
Sub-Devices: 8/8
Subdevice # 0: subdevice # 0
Subdevice # 1: subdevice # 1
Subdevice # 2: subdevice # 2
Subdevice # 3: subdevice # 3
Subdevice # 4: subdevice # 4
Sub-device # 5: subdevice # 5
Subdevice # 6: subdevice # 6
Subdevice # 7: subdevice # 7

$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7d10000 irq 30
1 [Loopback ]: Loopback - Loopback
Loopback 1

I don't know if this is going to be important but from the notebook speakers the right one is always less loud than the left one and is the first one where are the jack's for the microphone and headphones/speakers, also sometimes depending on the frequency it turns too hot but nothing burns or stop working, this was under windows 8.1 OS that doesn't have problems with sound except the overheating in the internal speakers with the "studio quality option".
 
Old 05-01-2017, 01:27 PM   #5
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
$ sudo modprobe -r snd-aloop

To remove it.

$ sudo modinfo snd-hda-intel

Taking note of the parm: ones which are flags you can pass to the driver if you have "special" hardware. Loopback seems to be useful if you want alsa as the primary driver and pipe that to jack. Or to record everything that your soundcard outputs. And other tricks. But you're not using it so not applicable.

For pulseaudio over a network, you need to sync your clocks, or odd artifacts happen. Many distros have ntp daemons running, so not normally an issue, and you're probably not networking your sound.

Normally that noise is a cheap soundcard, solution = use a different and not cheap soundcard. Otherwise fiddle until it goes away. Mixer settings, driver parms, changing periods or buffer sizes and other things detailed under /proc/asound/*. The default periods is 2, recalling needing to use 3 bitd to get decent audio. Although one of the options passed to jackd in my case.

As far as L to R levels, you can adjust those independently.

$ alsamixer -c 0

And press F1 for the help screen. If you press "q" like you would to exit a lot of unix things, it will increase the left channel while leaving the right one at it's current level. "z" to bring that down, or max out booth and bring back to the desired level with cursor keys, then exit with ESCape (aka boss key).
 
Old 05-01-2017, 06:59 PM   #6
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Original Poster
Rep: Reputation: Disabled
Shadow 7:

I am going to try with the files in /proc/asound/*. I am currently comparing the files between the different kernels to see if i could found a difference and inform it.

About the cheap sound card, i discovered it out with windows 8.1. I mean, how can the speakers overheat when using them?!. Though this doesn't happen witch any GNU/Linux distribution, unfortunately i have issues with the sound in the recently kernel versions. On the other hand the similarities I have found between operating systems is that when I am muting and unmuting there is a sound like when the microphone channel is being enabled and disabled, the only exception is the kernel 3.2, i presume this is the cross between lines that you mention earlier. Still with all this I wonder, why this kernel doesn't give me any problems with the sound?

By the way thanks for the help until now.
 
Old 05-01-2017, 07:25 PM   #7
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
Sound tends to be amplified pre-speakers #headphonepreamp. But I would imagine that if they're getting hot, it's probably not anything speaker related. Maybe you're missing some CPU microcode that regulates things. Where older things played it safe and had fans at max at all times.
 
Old 05-01-2017, 10:14 PM   #8
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Original Poster
Rep: Reputation: Disabled
Well first off the alsa driver version that doesn't give me problems is the 1.0.24. Second i have found many differences but to me the most important is the change from VT1802 HP to VT1802 Alt Analog, being the first the good one. That and the fact that i am not an expert.

About the mixer settings when running in the terminal $ amixer under the kernel 3.2 the differences are:

Simple mixer control 'PCM Loopback',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 0 [0%] [-34.50dB] [off]
Front Right: Playback 0 [0%] [-34.50dB] [off]

Simple mixer control 'Capture',1
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 31
Front Left: Capture 0 [0%] [-16.50dB] [on]
Front Right: Capture 0 [0%] [-16.50dB] [on]

Simple mixer control 'Input Source',0
Capabilities: cenum
Items: 'Internal Mic' 'Mic' 'Stereo Mixer'
Item0: 'Internal Mic'

Simple mixer control 'Input Source',1
Capabilities: cenum
Items: 'Internal Mic' 'Mic' 'Stereo Mixer'
Item0: 'Internal Mic'

Within /proc/asound/card0/pcm0c/info

subdevices_count: 2
subdevices_avail: 2

Within /proc/asound/card0/codec#0

Node 0x20 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x21 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In
Control: name="PCM Loopback Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=3, ofs=0
Control: name="PCM Loopback Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=In, idx=3, ofs=0
Control: name="Internal Mic Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=2, ofs=0
Control: name="Internal Mic Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=In, idx=2, ofs=0
Control: name="Mic Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=0, ofs=0
Control: name="Mic Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80]
Power states: D0 D1 D2 D3
Power: setting=D3, actual=D3
Connection: 3
0x2b 0x2a 0x29

This is the more relevant thing i saw...

Shadow 7:

Thanks for answering fast. If the problem is a CPU microcode, where i can found more about this? I have been reading about saving the mixer settings configurations, do you think is going to work if i applied that to my case?
 
Old 05-01-2017, 10:48 PM   #9
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
$ lspci -nnk | grep -i audio

The FFFF:FFFF vendor:device is a good thing to google with quirky hardware. You're probably not the only one with the issue.

Long long ago in a galaxy far far away, alsa was NOT integrated into the kernel. Just curious that if you compiled that version of alsa on your current kernel if that would fix things.

http://alsa-project.org/

You could also be missing firmware, but you'd probably have other issues if that were the case. Like no sound at all. Looks like the driver integration into the kernel is more complete, so compiling the old version on a new kernel would be tricky at best to accomplish. But not impossible. Although I'd hazard a guess that some parm to the module would shift things in your favor. If it's not some odd configuration issue / mixer setting.
 
Old 05-01-2017, 10:58 PM   #10
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
In debian it's something like:
# sudo apt-get install amd64-microcode intel-microcode

Obviously you don't need both, unless you use the same install booted to multiple machines of differing hardware. There's some distro magic and it just works for debian. In arch the microcode was kind of an extra initrd image, and the initrd line in grub needed both the initrd for the kernel and the microcode file links. And of course check that the microcode gets used.

# cat /var/log/kern.log | grep -i microcode

# journalctl -a
And navigate less style with [/] and "microcode", then [enter]. With [/] and [enter] for find next.

YMMV
 
Old 05-02-2017, 09:55 PM   #11
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Original Poster
Rep: Reputation: Disabled
Nice reference to star wars. What you say about the integration of alsa to the kernel is indeed correct according to http://alsa-project.org/main/index.php/Download , luckily and unluckily for me i have found a page that could help me http://duopetalflower.blogspot.com.a...untu-1010.html the sad part is that i can't install the most important part, the driver, because of the kernels header apparently... also in the process the kernel version 3.2 now doesn't have sound, such is my luck. Anyways i have found something funny about the vendor and it's that apparently it's problematic for linux distributions, but according to https://h-node.org/soundcards/view/e...oller--rev-04- it's great for libre distros, however when i was testing trisquel 7 the distortion and noise was there.

About the sound issues, what I have found refers to:
1.An absence of sound
2.Crappy and distorted sound under recording.
3.Low quality of sound

All most all of them come from Ubuntu distros but neither of the solutions posted about them that i have proved have worked. Maybe the sound card come with a failure?
 
Old 05-03-2017, 05:30 AM   #12
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
http://duopetalflower.blogspot.com.a...untu-1010.html

That would be the steps to compile the OLD version on a NEW kernel. Although the guide itself is for compiling the NEW version on an OLD kernel. Assuming that the download links still work (didn't test it). You will need the linux-headers-amd64 or whatever applies which is the /lib/modules/$(uname -r)/build link to the linux source stuff used for your kernel. Which is part of the steps / instructions, notice the comments below on that page with the build-essential, not build-essentials typo.

I wouldn't rule out hardware failure. Try the headphone jack and external speakers to see if the issue persists. Speakers are known to fail. For car thieves it's the one thing they ignore as they have little to no after market value. Perhaps you could record the sound on another piece of hardware which would help me to recognize it as hardware or software as the likely / familiar causation.

It looks like debian wheezy which uses the 3.2 kernel had alsa version 1.0.25, so the driver wasn't likely to break on newer versions. Although I've had issues with the snd-hda-intel driver since it supports sooooo many chip variants. But that was back in the 1.0.15-ish era circa late 2007? The changes between 1.0.14 to 1.0.16 were dramatic relative to the effects on that hardware I used at the time. I had to override the periods from 2 to 3 via jack for a less crackly sound scape. And by 1.0.16 it just worked out of the box.

You could have other things going on though. pcspkr might have loaded.

$ lsmod

Normally it's blacklisted or low priority (-2). It's meant to drive the beep thing on the motherboard, but can interfere with alsa. And depending on the distro, OSS drivers which are ancient might exist. But these days alsa has an oss layer(snd-pcm-oss) to simulate that driver (/dev/dsp) so it's excluded from most modern distros. And various bad configurations which can be solved by removing the configurations and rebooting.

$ rm -rf .config/pulse
$ rm -rf .pulse*
$ rm .asoundrc
$ sudo rm -rf /.pulse*
$ sudo reboot

There could also be some corruption if you tried starting / stopping pulse as root.

$ ls -l /run/user/####/

Where #### is the user ID.

$ id

uid=####(user)

When you goof the root thing with pulse the owner:group perms change to root:root and will likely need manual efforts to undo that corruption.

$ sudo chown -R user:user /run/user/####/pulse

Where #### is the user ID. Not normally an issue, but if you've done a lot of fiddling could be. It will show up as an issue in the various logs (/var/log/syslog) as a permission denied type thing. Or when you try to start/stop pulseaudio.

$ pulseaudio --kill
$ pulseaudio --start

Although by default it auto-restarts itself unless the /etc/pulse/client.conf has "autospawn = no" in it. You don't have to use pulseaudio, but enough things are configured for it by default that it's less of a hassle if you do.
 
Old 05-04-2017, 12:49 AM   #13
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Original Poster
Rep: Reputation: Disabled
Yeah it's old but the only one, the others post that ask how to install the alsa driver say the same: "update the kernel if you want a new version of alsa, because it's integrated on it", if only i could find a guide for modern kernels it would be great.

I have recorded 3 clips with audacity using the notebook: the first (without loopback) and the second (with loopback) were recorded with the internal microphone. The third it was recorded using a genius microphone with loopback activated. All were recorded form this track https://www.youtube.com/watch?v=U0Jom-1JyRc i used it because it's one of the most distorted i had reproduced and because it was from this track that i discovered the great distortion. Now... How do I send it to you?

The kernel version 3.2 that i was using was from Debian wheezy, the best i have proved, the others were very conflicting, except the one from Trisquel 6 but i could not low the brightness or use the network card wifi.

$ lsmod
Module Size Used by
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
snd_rawmidi 32768 1 snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
binfmt_misc 20480 1
intel_rapl 20480 0
x86_pkg_temp_thermal 16384 0
arc4 16384 2
intel_powerclamp 16384 0
uvcvideo 90112 0
iwldvm 233472 0
coretemp 16384 0
mac80211 737280 1 iwldvm
videobuf2_vmalloc 16384 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
kvm_intel 172032 0
videobuf2_v4l2 28672 1 uvcvideo
videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2
kvm 540672 1 kvm_intel
v4l2_common 16384 1 videobuf2_v4l2
videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
snd_hda_codec_hdmi 49152 1
snd_hda_codec_via 24576 1
snd_hda_codec_generic 73728 1 snd_hda_codec_via
media 24576 2 uvcvideo,videodev
irqbypass 16384 1 kvm
snd_hda_intel 40960 9
snd_hda_codec 135168 4 snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 90112 5 snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep 16384 1 snd_hda_codec
iwlwifi 200704 1 iwldvm
snd_pcm 106496 6 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
aesni_intel 167936 0
aes_x86_64 20480 1 aesni_intel
snd_timer 32768 2 snd_pcm,snd_seq
lrw 16384 1 aesni_intel
rtsx_pci_ms 20480 0
gf128mul 16384 1 lrw
cfg80211 565248 3 iwlwifi,mac80211,iwldvm
snd 81920 27 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_via,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_g eneric,snd_hda_codec,snd_hda_intel,snd_seq_device
glue_helper 16384 1 aesni_intel
soundcore 16384 1 snd
memstick 20480 1 rtsx_pci_ms
ablk_helper 16384 1 aesni_intel
cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper
mei_me 36864 0
mei 98304 1 mei_me
lpc_ich 24576 0
shpchp 36864 0
joydev 20480 0
input_leds 16384 0
serio_raw 16384 0
mac_hid 16384 0
tpm_infineon 20480 0
parport_pc 32768 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,ppdev,parport_pc
autofs4 40960 2
btrfs 987136 0
xor 24576 1 btrfs
raid6_pq 102400 1 btrfs
dm_mirror 24576 0
dm_region_hash 24576 1 dm_mirror
dm_log 20480 2 dm_region_hash,dm_mirror
i915 1208320 5
rtsx_pci_sdmmc 24576 0
i2c_algo_bit 16384 1 i915
drm_kms_helper 155648 1 i915
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
psmouse 131072 0
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
drm 364544 6 i915,drm_kms_helper
pata_acpi 16384 0
r8169 81920 0
rtsx_pci 53248 2 rtsx_pci_ms,rtsx_pci_sdmmc
mii 16384 1 r8169
wmi 20480 0
video 40960 1 i915
fjes 28672 0

and /etc/modprobe.d/blacklist.conf

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac

Interesting is the fact that i have a Beep channel in alsamixer, but i always have it muted.

Thanks to you, I've learned about the corruption. Now I just have to repair it, worst case scenario fresh installation of Mint 18.1, though i am considering moving to Debian or Fedora they are less bloated OS's on my experience.

I used to disable pulseaudio for test if the distortion wasn't coming for it, imagine it my disappointment when i figured it out it was from alsa.
 
Old 05-04-2017, 06:56 PM   #14
ambix
LQ Newbie
 
Registered: Apr 2017
Distribution: Mint 18.1
Posts: 10

Original Poster
Rep: Reputation: Disabled
New test with fresh install from mint 18.1 under kernel 3.2.0-24 with alsa Version 1.0.24.

I have discovered that when enabling the loopback mixing the sound stop even if the channels headphone and speakers are unmute, curiously if the two are activated when plugged the headphones or the outside speakers the internal speakers of the notebook remain muted. Contrary to what happens under others Kernels when plugged in the headphones or the outside speakers and turned on the channel speaker, the internals ones work like regularly they would except for the right speaker where the jacks are connected.
To have sound when loopback mixing is activated i have to choose the input source option previously of enabling it, they are : internal mic, mic or stereo mixer. Depending on what i choose when enabling the loopback the sound is heard only when i unmute the corresponding channel and the PCM loopback. The exception only applies when choosing stereo mixer, in this case wich PCM loopback unmuted is enough. And guess what, when the sound is listened again the distortion and the high pitched noise is hear like in all the others kernels.

Lastly if the music and the microphone are separated then there is not distortion. So i guess the problem is the crossing signals.

In the new kernels the loopback mixer only make the sound more distorted but doesn't stop it or make it more louder.

I am very sorry, i have messed to much the previous alsa and pulseaudio configuration files that i has give the details wrong, i hope this time i give the right details and thanks for helping me.
 
Old 05-04-2017, 09:28 PM   #15
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874Reputation: 874
Quote:
Originally Posted by ambix View Post
How do I send it to you?
Various methods. Posting a youtube video, soundcloud, and other ways. Although a lot of those require accounts. I'm not sure if this site lets you attach sound files. But it can do images and various ways to create an image from a sound file. Although samples would be short, as 1920 pixels to samples at 44.1kHz would be < 2 seconds of sound. And making that conversion probably isn't simple for either of us.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Laptop making high pitched noise while charging Valkyrie_of_valhalla General 5 03-21-2009 06:34 PM
High pitched noise after installing ATI graphics drivers Speedsoda Linux - Software 2 03-01-2009 06:53 PM
high pitched noise on booting lailadb Linux - Newbie 2 11-28-2008 01:28 PM
High-pitched noise after installing ati drivers VNF Slackware 7 09-15-2007 01:45 PM
Weird, high pitched noise upon rebooting. Slovak Linux - Hardware 2 11-29-2004 10:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook

All times are GMT -5. The time now is 12:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration