Jack select Line In / Mic in old laptop Fujitsu Siemens Amilo Pi 1505

[Jeronimo17]

Fujitsu Siemens Amilo Pi 1505 jack select Line In / Mic

Hello, I have been with this problem in linux for a long time, the laptop has 2 connectors for jack, the one for the articular / digital outputs works well (the digital output is broken) but the microphone / line input do not know how to change the mode.

In principle it is in line-in mode (it records well from a line source and in stereo), but I can't get it to change to mono recording and make the microphone work well.

In Windows, the Realtek program has to change modes and it works well, I can also activate the hardware feedback by listening to the microphone completely in real time (when I restart and switch to Linux, the microphone mode is lost and also feedback hardware)

I have tried Jack retasking for HDA Intel sound cards and was surprised that the microphone input / line input can be converted to a line output and I have found that it works, but impossible to do its normal microphone functionality

I have also tried adding in /etc/modprobe.d/alsa-base.conf

Code: Select all

options snd-hda-intel model = fujitsu-pi2515

I have tried quite a few models and do not notice any changes at all, my model does not appear in the list.

Code: Select all

System:
  Host: jeronimo17-AMILO-Pi-1505 Kernel: 4.15.0-99-generic x86_64 bits: 64 
  Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia 
Machine:
  Type: Laptop System: FUJITSU SIEMENS product: AMILO Pi 1505 v: N/A 
  serial: <root required> 
  Mobo: FUJITSU SIEMENS model: AMILO Pi 1505 serial: <root required> 
  BIOS: FUJITSU SIEMENS v: 1.14C date: 07/30/2007 



jeronimo17@jeronimo17-AMILO-Pi-1505 ~ $ cat /proc/asound/card0/codec* | grep Codec
Codec: Motorola Si3054
Codec: Realtek ALC883

jeronimo17@jeronimo17-AMILO-Pi-1505 ~ $ cat /proc/asound/card0/pcm0c/info
card: 0
device: 0
subdevice: 0
stream: CAPTURE
id: ALC883 Analog
name: ALC883 Analog
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 1

jeronimo17@jeronimo17-AMILO-Pi-1505 ~ $ sudo inxi -A
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio 
  driver: snd_hda_intel 
  Sound Server: ALSA v: k4.15.0-99-generic 

So my questions are:

How to change the microphone input / line input mode on the jack?
How to trigger input feedback through speakers without creating a software loop?
Should the Realtek ALC883 codec be 1st instead of Motorola Si3054?

Thank you all

[MrEen]

Hi Jeronimo17,

Install (if necessary) and run PulseAudio Volume Control (pavucontrol) and on the Input Devices tab try lower one channel to zero. If that doesn't work, switch the channels lowering the other side. If you don't see both the left and right channels, click on the lock icon.

[Jeronimo17]

Hi MrEen,

This is executed with that command,

The mode is not really microphone mode as it says, it is line input (according to tests)

I have tried all the similar ones, gnome-alsamixer, alsamixer ... and changing all the settings and I don't see anything that resembles the mode change

Here is the name of the modem instead of the chip of the sound card, as I said before

With the switches it does not change to microphone mode, neither do I hear the input through the output

The modem name is also displayed here.

[MrEen]

Okay, run this command and paste the output please:

Code: Select all

curl https://gitlab.freedesktop.org/pulseaudio/pulseaudio/raw/master/src/utils/pa-info?inline=false | bash | nc termbin.com 9999

The last line will have a termbin.com URL that will point to a thorough listing of your sound setup.

[Jeronimo17]

https://termbin.com/hrvl

thanks for looking at it

[MrEen]

Try this; In the terminal enter amixer -c0 set Mic 75% unmute then test the mic. Does that get the mic working?

We'll deal with being able to hear through the speakers after we get the mic working first.

[Jeronimo17]

Capture, but not aligned to 0V DC, and capture in stereo, not mono as in windows, it seems a super gain of line input

Testing with line input at minimum volume, it takes a long time to go to 0v DC.

[MrEen]

In your screenshots right below "Clic para comenzar monitorizacion" the slider for the Mic is at the maximum. Try turning that down a bit.

Also, I forgot in my last post to mention to also run this:

Code: Select all

pacmd set-default-source alsa_input.pci-0000_00_1b.0.analog-stereo

[Jeronimo17]

Try turning that down a bit.

Impossible to modify that in Audacity

In Base it is at 0VDC but it hardly has gain for the microphone when you go up from base it is no longer in 0VDC but if the microphone is with good gain

Here if it stays at 0VDC and it sounds pretty good, although I have seen that it also records in stereo with the microphone (I have done the tests with win7 before I have always had XP)

Give extra profit with this in windows also the recording fails does strange things the graph

And what about hear through the speakers, how would it be?

[MrEen]

And what about hear through the speakers, how would it be?

For that, pactl load-module module-loopback latency_msec=1 should do it. See the first big answer here.

[Jeronimo17]

Although the delay is very good, some delay is noticeable (almost negligible) and it seems to consume some cpu

In the original driver in windows it seems that there is no delay, as if everything was really due to hardware internally
Is that so?

Edit: according to the big answer it talks about micro usb, there yes this is necessary

Edit2: Yess, the first time that it works, this is real time loopback without using a cpu

It only remains to set to 0 VDC, is it possible?

[MrEen]

Input is my weakness in sound things. All I can do is offer sensible settings.

In your case, you had the wrong device as the default input (Default Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor) and in your original alsamixer screenshot, you can see the Mic has no volume and is muted (the MM at the bottom means muted. Pressing the m key when the column is selected will unmute)

Also, this may help you get closer to something acceptable. Again with the alsamixer screenshot, you'll see the Mic Boost volume is all the way down. Pressing the up arrow on that column once or maybe twice, might help getting better results from the mic.

It only remains to set to 0 VDC, is it possible?

This is beyond my understanding, I'm afraid.

[Jeronimo17]

Using the mic boost makes recording even worse, moving more than centered to 0

Thank you very much for the help, at least I have the loopback

Edit: https://manual.audacityteam.org/man/dc_offset.html


Edit2: This seems to be my problem https://bugs.launchpad.net/linuxmint/+bug/1324588

[MrEen]

Ahh, thanks for those. Now I get it.

This is not my area, but some things you could try. In alsamixer use the z and c keys to lower the left and right channels independently. The q and e keys do the raising. So you could try lowering one side to zero with this on both the Mic, and the Capture columns. To see the Capture column, you'll need to press F4. I doubt this is going to help the offset, but it will get you a mono recording.

Also, that Audacity page mentione LADSPA plugins. In Linux, you can install swh-plugins to get a bunch of LADSPA plugins. At the moment, I can't find any source of documentation for this. The web site doesn't seem to have any working links. In case it helps, the sources are here.

[Jeronimo17]

Ahh, thanks for those. Now I get it.

This is not my area, but some things you could try. In alsamixer use the z and c keys to lower the left and right channels independently. The q and e keys do the raising. So you could try lowering one side to zero with this on both the Mic, and the Capture columns. To see the Capture column, you'll need to press F4. I doubt this is going to help the offset, but it will get you a mono recording.

It seemed like a good idea but it's only modifying 50% of the problem
https://anonfile.com/h9eae6x0o7/vokoscr ... -54-33_mp4

I don't know if the driver in windows makes the correction or the linux driver would need to activate any action in the hardware.

So the line or microphone input depends on the gain alone?

[MrEen]

All I can say is you're only showing a Mic in, but no Line in. This is shown near the bottom of your output:

Code: Select all

[    7.214207] snd_hda_codec_realtek hdaudioC0D1: autoconfig for ALC883: line_outs=1 (0x15/0x0/0x0/0x0/0x0) type:speaker
[    7.214212] snd_hda_codec_realtek hdaudioC0D1:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    7.214214] snd_hda_codec_realtek hdaudioC0D1:    hp_outs=1 (0x14/0x0/0x0/0x0/0x0)
[    7.214216] snd_hda_codec_realtek hdaudioC0D1:    mono: mono_out=0x0
[    7.214218] snd_hda_codec_realtek hdaudioC0D1:    dig-out=0x1e/0x0
[    7.214220] snd_hda_codec_realtek hdaudioC0D1:    inputs:
[    7.214223] snd_hda_codec_realtek hdaudioC0D1:      Mic=0x18

Here's mine for comparison:

Code: Select all

[   29.238446] snd_hda_codec_realtek hdaudioC2D0: autoconfig for ALC221: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[   29.238448] snd_hda_codec_realtek hdaudioC2D0:    speaker_outs=1 (0x17/0x0/0x0/0x0/0x0)
[   29.238450] snd_hda_codec_realtek hdaudioC2D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   29.238451] snd_hda_codec_realtek hdaudioC2D0:    mono: mono_out=0x0
[   29.238453] snd_hda_codec_realtek hdaudioC2D0:    inputs:
[   29.238454] snd_hda_codec_realtek hdaudioC2D0:      Mic=0x1a
[   29.238456] snd_hda_codec_realtek hdaudioC2D0:      Line=0x1b

The drivers in Linux are in the kernel, but they act on what the BIOS reports as available. There are ways to work around some issues, but I'm not sure what would be needed in your case. Some examples for workarounds are config settings, HDAJackRetask and hda_analyzer.py.

Maybe changing the microphone pin with HDAJackRetask would get around this issue, but I cannot say for sure. It might need changes to the COEF or something else and that's well beyond my knowledge.

[Jeronimo17]

I can't with HDAJackRetask it only works to turn it into output, for now as a line input I think it more or less works

Thank you so much for everything

[MrEen]

You can change it to a different pin. For example, change 0x18 to Not connected, then check the box for Show unconnected pins, and set a new pin to Microphone. It might work, but I cannot say it will.

[Jeronimo17]

I have tried but no, 0x18 physically corresponds to that connector and the other never allows me to put it as input, with that program it is useful to use an output 4.0

Maybe the port is physically damaged and the windows drivers self-correct the deviation

[MrEen]

The only other suggestion I can make is hda_analyzer. Maybe changing the VREF on 0x18 will have some effect. I can't help in using that, but can say you'll need to download all of those files into one directory to be able to use hda_analyzer.py