How long does it take to get a bug fixed?

Asked by Timo Karhu

Hello,

I am asking this in friendly and constructive manner as I just don't know the answer and I'm curious. I have a bug https://bugs.launchpad.net/ubuntu/+bug/109236 filed. No sound with Acer Aspire 5044 WLMi in Ubuntu 7.04.

Now I am just fine after reverting back to Edgy, so I seek answer only out of my curiosity (and awaiting opportunity to get back to Feisty).

Is there a place where I could get an estimation when this will be fixed? Or is the "Status" field the only source for me to see the progress?
With this question I mean to ask if I need to wait until next major release or will these kind of bugs be fixed via some patch from update manager?

best regards,
Timo Karhu

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu alsa-driver Edit question
Assignee:
No assignee Edit question
Solved by:
Timo Karhu
Solved:
Last query:
Last reply:
Revision history for this message
Cesare Tirabassi (norsetto) said :
#1

Tino,

can you run this command for me and tell me the output:

cat /proc/asound/card0/codec#0

Thanks.

Revision history for this message
Timo Karhu (nalle-karhulitos) said :
#2

Hello there and thanks for replying,

Like I told I'm on 6.10 now. I hope that doesn't make this fail.

**1**
:~$ cat /proc/asound/card0/codec#0
cat: /proc/asound/card0/codec#0: No such file or directory

**2**
:~$ ls -la /proc/asound/card0
yhteensä 0
dr-xr-xr-x 5 root root 0 2007-05-13 13:32 .
dr-xr-xr-x 5 root root 0 2007-05-13 13:32 ..
-r--r--r-- 1 root root 0 2007-05-13 13:32 codec#1
-r--r--r-- 1 root root 0 2007-05-13 13:32 codec#3
-r--r--r-- 1 root root 0 2007-05-13 13:32 id
-rw-r--r-- 1 root root 0 2007-05-13 13:32 oss_mixer
dr-xr-xr-x 4 root root 0 2007-05-13 13:32 pcm0c
dr-xr-xr-x 3 root root 0 2007-05-13 13:32 pcm0p
dr-xr-xr-x 4 root root 0 2007-05-13 13:32 pcm1c

**3**
:~$ cat /proc/asound/card0/codec#1
Codec: Generic 14f1 ID 2bfa
Address: 1
Vendor Id: 0x14f12bfa
Subsystem Id: 0x10250080
Revision Id: 0x90000

**4**
:~$ cat /proc/asound/card0/codec#3
Codec: Realtek ALC883
Address: 3
Vendor Id: 0x10ec0883
Subsystem Id: 0x801235
Revision Id: 0x100002
Default PCM: rates 0x560, bits 0x0e, types 0x1
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
...
(this one continues for a long time)

If Feisty is needed to run the commands, I'll burn a live CD to test.
Let me know if it's needed!

best regards,
Timo

la, 2007-05-12 kello 20:42 +0000, Cesare Tirabassi kirjoitti:
> cat /proc/asound/card0/codec#0

Revision history for this message
Cesare Tirabassi (norsetto) said :
#3

Well,

I have a suspicion which arose looking at your information.
I believe that in 7.04 the right module for your sound chip is not loaded (the codec is not shown), and I wanted to check.

Now, if you want to install 7.04, we have a chance to correct this error. Its just a chance, it may not work, so you may not want to give it a try.
If you want, reinstall 7.04 and add this line to your /etc/modprobe.d/otions file:

options snd-hda-intel module=XXX

Where XXX can be taken from this list:

3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
auto auto-config reading BIOS (default)

So, if your system is an acer you may want to try with XXX=acer, or XXX=auto. If any of the other descriptions match your hardware, you can also try those.

Mind you that you need to reboot for the change to take place, and you may need to set your sound correctly (mixer, devices, etc.).

Revision history for this message
Timo Karhu (nalle-karhulitos) said :
#4

Hi,

I'm now on Feisty Live CD. I have sound just like in Edgy.
I checked that this is 2.6.20-10-generic compared to my upgraded 7.04 which had
(if I remember correctly) 2.6.20-15-generic.

Your original command looks now like this:
:~$ cat /proc/asound/card0/codec#0
cat: /proc/asound/card0/codec#0: No such file or directory

and

:~$ cat /proc/asound/card0/codec#1
Codec: Conexant ID 2bfa
Address: 1
Vendor Id: 0x14f12bfa
Subsystem Id: 0x10250080
Revision Id: 0x90000

and

:~$ cat /proc/asound/card0/codec#3
Codec: Realtek ALC883
Address: 3
Vendor Id: 0x10ec0883
Subsystem Id: 0x801235
Revision Id: 0x100002
(this output continues..)

While I was on Feisty, I tried "options snd-hda-intel module=XXX" with options
what people in ubuntuforums suggested. Those didn't help. However, module=acer I
did not try (no one suggested).

On the other hand, knowing that Feisty with "2.6.20-10-generic" gives me sound
now but after kernel upgrade it does not, does not give me comfortable feeling
to do upgrade again and try that module=acer. Would you think it really helps me?
What is the current kernel in Feisty? Any kernel upgrades in past 2 weeks (I
reverted back to Edgy about 2 weeks ago)?

Thanks for helping me out!

best regards,
Timo

Lainaus Cesare Tirabassi <email address hidden>:

> Your question #6477 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/6477
>
> Status: Open => Answered
>
> Cesare Tirabassi proposed the following answer:
> Well,
>
> I have a suspicion which arose looking at your information.
> I believe that in 7.04 the right module for your sound chip is not loaded
> (the codec is not shown), and I wanted to check.
>
> Now, if you want to install 7.04, we have a chance to correct this error. Its
> just a chance, it may not work, so you may not want to give it a try.
> If you want, reinstall 7.04 and add this line to your /etc/modprobe.d/otions
> file:
>
> options snd-hda-intel module=XXX
>
> Where XXX can be taken from this list:
>
> 3stack-dig 3-jack with SPDIF I/O
> 6stack-dig 6-jack digital with SPDIF I/O
> 3stack-6ch 3-jack 6-channel
> 3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
> 6stack-dig-demo 6-jack digital for Intel demo board
> acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
> auto auto-config reading BIOS (default)
>
> So, if your system is an acer you may want to try with XXX=acer, or
> XXX=auto. If any of the other descriptions match your hardware, you can
> also try those.
>
> Mind you that you need to reboot for the change to take place, and you
> may need to set your sound correctly (mixer, devices, etc.).
>
> _______________________________________________________________________
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/6477/+confirm?answer_id=2
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/6477
>

Revision history for this message
Cesare Tirabassi (norsetto) said :
#5

>While I was on Feisty, I tried "options snd-hda-intel module=XXX" with options
>what people in ubuntuforums suggested. Those didn't help. However, module=acer I
>did not try (no one suggested).

You can't just use what worked for other people and hope it works for you, you have to choose the model which match your hardware. In your case your codec chip is an 883, and the options I gave you are those for the 883.

As for deciding to upgrade or not, it is totally up to you. In most cases choosing the right model works, wether it is working for you or not we don't know yet. Chances are that it will, but I can't rule out that it won't.

We are now on kernel 2.6.20.15. Anyhow, don't worry about kernel, you can always install 2.6.20.10 if that works for you.

Revision history for this message
Cesare Tirabassi (norsetto) said :
#6

Forgot to mention, you can also refuse the upgrade to 2.6.20.15 when that is offered to you.

Revision history for this message
Timo Karhu (nalle-karhulitos) said :
#7

Hi,

ok, I'll try to find instructions how to get older kernel after the
upgrade. Or stay at Edgy as all works fine now.. ;)

Thanks.

r, Timo

su, 2007-05-13 kello 19:00 +0000, Cesare Tirabassi kirjoitti:
> Your question #6477 on alsa-driver in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/6477

Revision history for this message
Cesare Tirabassi (norsetto) said :
#8

To get the older kernel is no problem, I can tell you how, but its not even needed. Once you install, you have 2.6.20.10
You can even accept to upgrade to 2.6.20.15, try to use the module hack, and if that doesn't work you just boot choosing the 2.6.20.10 kernel (its not removed by the installation of the updated kernel).

Revision history for this message
Timo Karhu (nalle-karhulitos) said :
#9

Is that valid also for upgrade from 6.10 to 7.04? (I don't remember having option to select older working kernel. I tried some Edgy level kernel but it didn't even want to start)

Revision history for this message
Cesare Tirabassi (norsetto) said :
#10

Timo,

I don't think you are confortable to upgrade and I don't want to force you.
If you are happy please remain with Edgy, and when the problem will be solved for Feisty move to Feisty.
Check from time to time in the Feisty repository if a new kernel is uploaded and if that solves the snd-hda-intel problem.
If you decide any time in the future to upgrade to Feisty, and you still have problems, please come back to us and we will be happy to help you.

Revision history for this message
Timo Karhu (nalle-karhulitos) said :
#11

Very well, this now leads into my original question:
> Check from time to time in the Feisty repository if a new kernel is uploaded and if that solves the snd-hda-intel problem.
So if I got you right the answer to my question
> Is there a place where I could get an estimation when this will be fixed?
is no but I need to check repository every now and then. OK, this answers my question.

I found a spare disk so I was able to install pristine Feisty. Will do another post to continue with your suggestions!

Cheers.

Revision history for this message
Timo Karhu (nalle-karhulitos) said :
#12

OK,

now I have a clean 7.04 running on the spare disk. Right after install, sounds was ok just like with Live CD.
I tried to do what you suggested. From the 362 updates in update manager I located these and unchecked them:
linux-generic
linux-headers-generic
linux-image-generic
linux-restricted-modules-common
linux-restricted-modules-generic
while update manager was running I noticed something like "configuring 2.6.20-15-generic". Jee jee, it updated it although I didn't want it to. After reboot Update manager says that I have those 5 kernel updates waiting for me.. But as I can select 2.6.20-10 in the boot menu, let's drop this.

I will now try that module=acer.

Revision history for this message
Best Timo Karhu (nalle-karhulitos) said :
#13

OK, here I am again after reboot. Actually 2 reboots. First one didn't produce expected results. In another words module=acer didn't help me.

Checked forums one more time and noticed someone having sound working with Lenovo 3000 by installing latest alsa (alsa-driver-1.0.14rc4). I did the same and after reboot sound is here again!!

If I get back to the original question again, perhaps what I would have wanted to see in my original bug is a comment like 'fixed in alsa-driver' or 'try latest alsa to see if it helps'. But, nevermind, I am very happy now - I have sound.