Public bug reported:
I am trying a simple test using a loopback sound device.
pacat -r -d alsa_output.pci-_00_1b.0.analog-stereo.monitor \
--latency=1msec \
| pacat -p -d alsa_output.pci-_00_1b.0.analog-stereo \
--latency=1msec
I use the above command. This is to take the microphone in
I have removed the workround and no longer see the problem. I am
therefore closing the bug
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
h
I am happy to use the workround (modifying alsa-base.conf). So, this
issue is not high priority for me
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
Title:
[G41MT-S2P, V
I did "sudo hda-verb /dev/snd/hwC0D2 0x2b GET_PIN_SENSE 0"
nid = 0x2b, verb = 0xf09, param = 0x0
value = 0x8000
I also unplugged the mic and then got a value 0x0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Here is the log generated by running pulseaudio for a few seconds.
"a debug version of alsa driver" - how should I get this?
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+attachment/4223317/+files/pulseverbose.log
--
You received
The Sound Settings window does not suggest that the jack state is
rapidly changing.
I am not sure what the "verbose log" is
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
T
I checked the hda_proc.py file and it does not contain that patch.
So you could be right in saying that the patch might fix it.
I guess the package snd-hda-tools should be updated at some point
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
I forgot to mention that I have deleted ~/.asoundrc and /etc/asound.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
Title:
[G41MT-S2P, VIA VT2020, Pink Mic, Rear] No s
here is the output
** Attachment added: "alsa.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+attachment/4220358/+files/alsa.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://
Okay, moving to the latest driver did not help.
The change to alsa-base.conf did work.
I now see the microphone in Sound Settings
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/13657
I ran
sudo hda-jack-sense-test -c 0 -d 2
but I got an error "ValueError: wrong proc file format ( In-driver Connection:
6)"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
Public bug reported:
I run totem and then open a file. It then gets stuck and does not play the
file.
A lot of the time it works and if it does work, then totem never seems to have
a problem with subsequent files.
The issue is always with the first file opened it seems
ProblemType: Bug
DistroR
I have contacted the author. We will see what happens
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
Title:
[G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
Statu
Should I move to the latest alsa driver? If so, how do I do this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
Title:
[G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound a
okay, I installed snd-hda-tools.
I ran hda-jack-sense-test and got this output
Traceback (most recent call last):
File "/usr/bin/hda-jack-sense-test", line 47, in
codec = HDACodec(cardindex, codecindex)
File "/usr/share/snd-hda-tools/hda_codec.py", line 1023, in __init__
self.fd = os
I do not have the hda-jack-sense-test command.
I was not aware that I was overriding the pcm.default. Is it worth
changing this to see if the bug goes away? How would I do that?
Do I need to build my own version of the kernel to disable jack
detection?
--
You received this bug notification be
Well, I made a mistake and forgot to do the alsamixer command.
So I now attach the output after having done it
** Attachment added: "alsa2.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+attachment/4199972/+files/alsa2.txt
--
You received this bug notification becau
Well, I decided to go ahead with the actions in comment 8.
For this test, I am using the standard 14.04 kernel which is
3.13.0-34-generic
The output is attached.
In addition, I confirmed that the device is not displayed. In other
words, the bug was present
** Attachment added: "alsa.txt"
h
Yes, I see the kernel diff.
I need to know whether I should go ahead with the actions in comment 8.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1365769
Title:
[G41MT-S2P, VIA
Just to be clear, you want me to do the following
1. boot machine
2. change Input Source to "Read Mic" using alsamixer
3. run alsa-info.sh
4. provide output
Is that correct?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in
I had booted into an old version of the kernel.
I get the same problem with the current version which is
3.13.0-34-generic
> cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.13.0-34-generic.
I used alsamixer to change Input Source to "Read Mic" but the device is
still
Public bug reported:
The problem is that the microphone is not detected after a reboot. As a
result, some applications cannot get sound from the microphone.
The Input tab of the Sound window lists no device.
I have a workround which is to disconnect and then connect the
microphone after I have
22 matches
Mail list logo
