Peter Humphrey wrote:
Hello list,
Having finished building KDE on my new box (if that task can ever be
considered finished) I'm now tying up some loose ends.
When I log in to kde via kdm, I get a dialogue box telling me it wants to
remove my sound devices. It says "KDE detected that one or more internal
sound devices were removed. Do you want KDE to permanently forget about
these devices? This is the list of devices KDE thinks can be removed:
Capture: HDA Intel (); Output: HDA Intel ()".
I don't get the log-in sound played. Later, though, Firefox and Flash manage
between them to stream BBC radio to the speakers and I can listen to the
music.
What's going on here? The Gentoo sound page is woefully out of date, and the
KDE page is concerned with other things. I haven't found anything useful
about Gentoo and phonon.
The only sound hardware in the box is on the Asus P7P55D motherboard; it's
an Intel HD Ibex Peak high-definition audio chip according to lspci:
$ sudo lspci -v -s 00:1b.0
00:1b.0 Audio device: Intel Corporation Ibex Peak High Definition Audio (rev
05)
Subsystem: ASUSTeK Computer Inc. Device 8375
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at f7ff8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
The kernel clearly has control of the device, as I can hear some sounds.
Any ideas?
From your post, it appears that the kernel sees the card. However, the
only time I have seen this error was when I didn't have the right driver
for my sound card. Can you check again to make very sure you have the
right driver? Maybe there is two that are really close or something.
You may also want to make sure you remove any other drivers that may
have been enabled by default but that you don't need. Maybe some sort
of a driver clash going on.
Since it works for some things and not others, it is odd. It may be one
of those 'shot in the dark' things that fixes it.
Dale
:-) :-)
