On Wed, Feb 07, 2007 at 09:51:23AM +0000, john gennard wrote:
If possible, I'd like someone to help me here. Sarge gives
the problem and Kubuntu (Debian based) works fine.
Well, Sarge is close to two years old. Kubuntu has also diverged from
Debian a great deal and you don't mention which version.
When I run '#lspci' on each I get the following results:-
1. Debian:
0000:80:01:0 0403 Via Technologies, Inc. :
Unknown device 3288 (rev 10)
Right, the device database in Sarge probably dates to before this device
even existed, so it can only identify the manufacturer.
2. Kubuntu:
80:01:0 Audio Device: Via Technologies, Inc.
Via High Definition Audio Controller (rev 10)
Kubuntu apparently has an updated device list.
Alsaconf doesn't 'see' the device in Sarge which could well
be my problem. Why, though, does 'lspci' give such differing
results - I assume each run gets its information from the
same source (the device/chip itself).
The information as to the actual identifiers come from the chip. Run
'lspci -vvv' to see them in their full glory. The pretty descriptions
come from a "database" (really a text file or something like that) on
disk.
Furthermore, my Motherboard Manual says the Audio is 'Realtek
ALC888 7.1 Channel audio CODEC with High Definition audio'.
Have Via used a Realtek chip and 'bundled' it with something of
its own?
That sort of thing happens all the time. Manufacturers will rebrand
other people's stuff and sell it as their own. In Linux, device drivers
are based on chipsets, not on the manufacturer of the whole device.
Hence the discrepancy.
My main aim is to get audio to work without getting a separate
card, but I'd like to have some light shed on this confusion
(in my simple mind that is!).
Update to Etch and it will probably work.
Regards,
-Roberto