Inaudible volume by default in Dapper with Acer TravelMate 3012

sorry for the wrong subject.
but in
http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/2006-April/003214.html
the reporter indicated the bug in
Package: alsa-base
Version: 1.0.10-3
Severity: grave
Justification: renders package unusable

alsa-base is a part of Ubuntu!

i read on www.alsa.org-project.org that this is a bug in alsa -driver which is fixed in version 1.0.11

You are right, I have the same chip with the same problem, no sound. this is my configration:

str@eva:~$ lspci | grep -i audio
0000:00:1b.0 0403: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

str@eva:~$ lsmod | grep snd
snd_hda_intel 20468 0
snd_hda_codec 150768 1 snd_hda_intel
snd_pcm_oss 56448 0
snd_mixer_oss 20544 1 snd_pcm_oss
snd_pcm 96676 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 26884 1 snd_pcm
snd 60004 6 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 10784 1 snd
snd_page_alloc 11304 2 snd_hda_intel,snd_pcm

My laptop is a Toshiba Satellite P105
Have you solved this problem?

Please attach ``lspci -nv && tail -2 /proc/asound/oss/sndstat && amixer''. No, it is not and will not be fixed prior to release, but if there is a fix, it may be committed for -updates.

my "lspci -nv && tail -2 /proc/asound/oss/sndstat"

000:00:00.0 0600: 8086:27a0 (rev 03)
        Subsystem: 1179:ff31
        Flags: bus master, fast devsel, latency 0
        Capabilities: <available only to root>

0000:00:01.0 0604: 8086:27a1 (rev 03)
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 00002000-00002fff
        Memory behind bridge: b1000000-b2ffffff
        Prefetchable memory behind bridge: 00000000c0000000-00000000cff00000
        Capabilities: <available only to root>

0000:00:1b.0 0403: 8086:27d8 (rev 02)
        Subsystem: 1179:ff31
        Flags: bus master, fast devsel, latency 0, IRQ 58
        Memory at b0000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <available only to root>

0000:00:1c.0 0604: 8086:27d0 (rev 02)
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: 00003000-00003fff
        Memory behind bridge: 52000000-520fffff
        Capabilities: <available only to root>

0000:00:1c.1 0604: 8086:27d2 (rev 02)
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        Memory behind bridge: 52100000-521fffff
        Capabilities: <available only to root>

0000:00:1c.2 0604: 8086:27d4 (rev 02)
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
        Capabilities: <available only to root>

0000:00:1d.0 0c03: 8086:27c8 (rev 02)
        Subsystem: 1179:ff31
        Flags: bus master, medium devsel, latency 0, IRQ 50
        I/O ports at 1800 [size=32]

0000:00:1d.1 0c03: 8086:27c9 (rev 02)
        Subsystem: 1179:ff31
        Flags: bus master, medium devsel, latency 0, IRQ 233
        I/O ports at 1820 [size=32]

0000:00:1d.2 0c03: 8086:27ca (rev 02)
        Subsystem: 1179:ff31
        Flags: bus master, medium devsel, latency 0, IRQ 185
        I/O ports at 1840 [size=32]

0000:00:1d.3 0c03: 8086:27cb (rev 02)
        Subsystem: 1179:ff31
        Flags: bus master, medium devsel, latency 0, IRQ 169
        I/O ports at 1860 [size=32]

0000:00:1d.7 0c03: 8086:27cc (rev 02) (prog-if 20)
        Subsystem: 1179:ff31
        Flags: bus master, medium devsel, latency 0, IRQ 50
        Memory at b0004000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: <available only to root>

0000:00:1e.0 0604: 8086:2448 (rev e2) (prog-if 01)
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=0a, subordinate=0e, sec-latency=32
        I/O behind bridge: 00004000-00004fff
        Memory behind bridge: b3200000-b32fffff
        Prefetchable memory behind bridge: 0000000050000000-0000000051f00000
        Capabilities: <available only to root>

0000:00:1f.0 0601: 8086:27b9 (rev 02)
        Subsystem: 1179:ff31
        Flags: bus master, medium devsel, latency 0
        Capabilities: <available only to root>

0000:00:1f.2 0101: 8086:27c4 (rev 02) (prog-if 80 [Master])
        S...

Thanks for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

It is still not working. I'm still having the same problem. I found a solution to make it work so it does sound, but I need to disable ACPI . I'm using kernel 2.6.20 (Linux version 2.6.20-16-generic (root@terranova) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Wed May 23 01:46:23 UTC 2007) with acpi=off and it does sound well, but now I don't know the status of my battery and those stuff.

Ubuntu 7.04 on Toshiba Satellite model# A-135-S4627
Has same intel sound chip as above. Please fix this asap. Thank you.

Toshiba-laptop:~$ lspci| grep -i audio
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

Hi, I also have this problem with Gutsy. I have an acer travelmate 3012WTMi. If you need any more information please let me know.

It unfortunately appears that this bug is not yet resolved. Does this issue still exist in the Hardy Heron 8.04 LTS release? If so, the Intrepid Ibex 8.10 Alpha2 is also scheduled for release today. It will appear at the following when available: http://www.ubuntu.com/testing/intrepid/alpha2 . It contains the actively developed 2.6.26 Ubuntu kernel. It would be great if you could test this upcoming release via a LiveCD and verify if the issue still exists. If so, please include the appropriate debugging information as outlined at https://wiki.ubuntu.com/DebuggingSoundProblems . Thanks in advance.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

<-- I didn't find this kernel for my current 8.04 instalation. Could you tell us what rep do we need to install 2.6.27?

Hi StR,

Since the 2.6.27 kernel is for Intrepid you need to enable the Intrepid repository to test. If you are unfamiliar with how to safely do this I'd recommend waiting for the Alpha5 release to test. Thanks.

Ok, I thought we could have some backport repository to test this kernel... let me add intrepid's repository and do the testing with that

Srt, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . Were you able to test with this beta release ?

Thanks.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!