On 05/06/2010 04:57 PM, Daniel T Chen wrote:
> On Thu, May 6, 2010 at 7:22 PM, NoOp wrote:
>> Should this report marked as a duplicate of
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/549289
> 
> No, that one's PCI SSID is different:
> Subsystem: Lenovo Device [17aa:21b4]
> 
> (which is precisely why I retitled this bug report earlier).
> 
>> or
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/477154
> 
> No, that one's PCI SSID is also different:
> 00:1b.0 0403: 8086:293e (rev 03)
> 	Subsystem: 1028:0402
> 
> We use one bug report per PCI SSID (or codec SSID if the OEM is
> cracktastic).

So should I file a separate report for Subsystem Id: 0x103c360b?

....
> 
>> There is still an issue with karmic on the same notebook due to the Ubuntu version of
>> alsa-base for karmic is 1.0.20+dsfg-1ubuntu5 and does not include code for:
> 
> The version of the alsa-base package has nothing to do with the
> version of the driver. See /proc/asound/version instead

On the laptop with karmic booted:
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Compiled on Mar 25 2010 for kernel 2.6.31-21-generic (SMP).

but alsa-base is showing:
1.0.20
so is there an mismatch between the two?

And with lucid booted:
 cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Compiled on Apr 29 2010 for kernel 2.6.32-22-generic (SMP).

So why the huge difference between the two? Note: in karmic internal mic
works, sound from headphone & speakers at the same time. I also get
additional internal mic options (Mic B, Mic C, Mic E, and Mic F (Mic F
works).
  In lucid internal mic does not work, sound from headphones & speakers
are separated when the headphones are plugged in (sound in headphones,
no sound in speakers - works as expected). No added Mic x options as in
Karmic.

Both have the
options snd-hda-intel model=dell-vostro
or
options snd-hda-intel model=olpc-xo-1_5
in /etc/modeprobe.d/alsa-base.conf
(meaning that I can put either in lucid & speaker/headphones work as
expected. Neither make any difference in karmic).

> 
>> http://package-import.ubuntu.com/diffs/alsa-driver
>> Note that this is for 1.0.21 and 1.0.22.1. 1.0.21 is missing from the
>> releases:
>> https://launchpad.net/ubuntu/+source/alsa-driver
>> They went from 1.0.20 (karmic) directly to 1.0.22 (lucid).
> 
> You're looking in the wrong place.

And where should I look? Is alsa-base not the correct module affecting
this?

>> Maybe https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/549289
>> could be a [MASTER] for Conexant CX2058x (Pebble) issues? And perhaps
>> the 'Fix Committed' could also include karmic as well?
> 
> No, it does not belong as a master tracking bug. The hardware is all
> different. Karmic kernels receive different treatment, so unless
> there's an SRU for it, they won't receive these updates. For Karmic,
> use linux-alsa-driver-modules-$(uname -r) from ppa:ubuntu-audio-dev
> instead.

No. It took me quite some time the othere day to back out the -dev mess
and restore my systems (karmic and lucid) back to standard after your
previous suggestions. I had to 'force versions' to back out the -dev
packages. No *user* should be advised to use ppa:ubuntu-audio-dev.