dapper upgrade no sound

[Daniel T. Chen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Indra Polak wrote:
> 0000:02:07.0 0401: 1102:0002 (rev 08)
>         Subsystem: 1102:8027
>         Flags: bus master, medium devsel, latency 64, IRQ 16
>         I/O ports at dc60 [size=32]
>         Capabilities: <available only to root>

This id definitely is detected:
emu10k1_main.c:864:     {.vendor = 0x1102, .device = 0x0002, .subsystem
= 0x80271102,

I have pointed out the real cause of your issues below.

> "If your hardware is not activated automatically..." it is activated
> automatically because its driver gets loaded at boot time using an entry
> in /etc/modules. There is no manual 
> action involved. I think you mean "If some piece of code (udev) does not
> recognize your card at some time (when udev runs) in the boot process".

It is pretty clear from the context of answering your query that we are
talking about the udev HardwareActivation case, not the /etc/modules case.

> Then there is the fact that it did work before the upgrade, it is an old
> card so why would there be a change in the {sub,}system & {sub,}vendor
> ids?

ids are often changed as it is discovered that existing ones are imprecise.

> What is the point of having these ID's when they change overnight for
> older cards?
> --O yeah, we changed the ids, so from now on some (version) of the card
> has the old id, and some (newer) version (but the same card of course) 
> can be recognized using the new id.

They often are /not/ identical.

> Then someone thinks: well, lets change the recognition process by
> assuming every card has the newer id, so everyone with a card 
> bought before date X must buy a new card. This makes no sense.

That is not the case at all. Reading the "changelog" history in
emu10k1_main.c should be enlightening as to how many iterations have
been made over different pci ids.

> I have a kernel Oops in my dmesg, maybe this destroys the proper
> recognision?

No, but it does actually reveal the root issue of all this mess. Note
the string printed next to the EFLAGS:

> [4294695.976000] EFLAGS: 00010086   (2.6.12-9-386)

Lo and behold, that is /not/ Dapper's kernel. By default Dapper's udev
/requires/ Dapper's kernel. Boot into 2.6.15-26-386, and you will find
that everything works properly without having to specify snd_emu10k1 in
/etc/modules.

> My thoughts: this udev thingy is not doing its job. You say well the
> udev system should also handle dynamic modules, but as I already
> showed, 
> then the sound does not get restored. So even though a dynamic driver is
> loaded which should trigger the udev init action, and at that point 
> the card is recognized and operational, udev does not restore its
> settings. So udev only restores when it ADD's the module itself, not
> when done later 
> by another process. 

If the correct kernel is not used, udev cannot "do its job."

> How can it be that some parts of the OS do know that the sound card is
> present and operational (I hear sound after unmuting) while other parts 
> (this udev part) is ignorant (since it is not restoring the settings by
> itself).

udev does not have anything to do with restoring mixer levels. You have
been thrown for a loop because you have mismatched udev/kernel versions.

> I looked in 
> /usr/share/misc/pci.ids
> for my card id.

/usr/share/misc/pci.ids is irrelevant. The driver contains the pci id.

> Correct, correct...it works for me. The "correct" way does not work for
> me. Probably 
> some other changed component after the upgrade is not totally correct
> either.

I am certain the correct way /will/ work for you once you stop booting
Breezy's kernel with Dapper's udev and start booting Dapper's kernel
with Dapper's udev.

Thanks,
- --
Daniel T. Chen            crimsun at ubuntu.com
GPG key:   www.sh.nu/~crimsun/pubkey.gpg.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEwS5ze9GwFciKvaMRAv7uAKC9sdQBgxeh0v7yWAd1qrAjl38WDgCcDUkt
3FuD1RsaNPesz8RYTIHuBPs=
=c1WB
-----END PGP SIGNATURE-----