http://bugzilla.novell.com/show_bug.cgi?id=541565 User tiwai@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=541565#c6 Takashi Iwai <tiwai@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |root.aimcmp2@cox.net --- Comment #6 from Takashi Iwai <tiwai@novell.com> 2009-09-24 00:46:29 MDT --- First off, please be more specific about the symptom. What do you mean "the system says it can not use the intel sound"? What is "system" you refer to? What desktop system are you using with which setup? And, "sometimes is falls back to some kind of default sound and sometimes you get no sound at all" -- too many "some", and I can't see what is broken exactly. Which application is used with which setup? If it's about KDE4 sound setup, try to uninstall pulseaudio. If it's difficult because of dependency, at least, uninstall libflashsupport. If it's a driver issue -- that is, if you've never heard any sound at all on your system, then try alsa-driver-kmp on OBS multimedia:audio:KMP repo http://download.opensuse.org/repositories/multimedia:/audio:/KMP/ Choose openSUSE_11.1-Updates if you are using the online-update kernel. The openSUSE_11.1 is for GM kernel. Install only one alsa-driver-kmp package corresponding to your running kernel flavor. Don't install alsa-driver-unstable-kmp. Zypper tends to install both, so safer to install manually via rpm. Once after installing the kmp, run "rcalsasound restart" or do reboot. After that, check again the all mixer setup, unmute and raise the volumes. If the latest alsa-drvier-kmp doesn't work, run alsa-info.sh with --no-upload option, and attach the generated file to analyze more. This will be really helpful. Regarding the support HD-audio: You are apparently fooled by marketing. It's not a question of the quality but about a system setup. HD-audio is a crap like ACPI regarding the system setup, because of many reasons like BIOS breakage. It's getting better, but it's still often buggy and broken. Thus many workarounds are needed in the driver side. So, unless *USER* provides the sufficient information to analyze and debug, we can't do anything against. Take a deep breath once, then please explain precisely (but concisely) how to reproduce the problem on anyone else's machine :) After that, we can go forward. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.