[CentOS] Acer 5920 audio chip does not work in CentOS 5.2?
William L. Maltby
CentOS4Bill at triad.rr.com
Wed Jul 2 11:36:10 UTC 2008
On Wed, 2008-07-02 at 16:52 +1000, hce wrote:
> On Tue, Jul 1, 2008 at 7:20 PM, William L. Maltby
> <CentOS4Bill at triad.rr.com> wrote:
> > On Mon, 2008-06-30 at 23:51 -0500, Alex White wrote:
> > hce wrote:
> >> Hi,
> >> I've installed CentOS 5.2 to a laptop Acer 5920 for dual boot, the
> >> audio works in Window Vista, but does not work in CentOS 5.2. Does
> >> CentOS 5.2 support following audio chip or not?
> >> Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> >> Controller (rev 03)
> >> Thank you.
> >> Kind Regards,
> >> Jim
> > When you say it doesn't work, are you getting an error message
> > saying that there's no sound device?
> >> Does lspci list your soundcard? If you have a super long list and
> >> can't locate it easily, you can try (but I can't promise this will
> >> work for you, it does for me however) lspci | grep audio
> Please see following lspci information for the audio, seems ok.
> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> Controller (rev 03)
> Subsystem: Acer Incorporated [ALI] Unknown device 0121
> Flags: bus master, fast devsel, latency 0, IRQ 66
> Memory at f0500000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
I'm certainly not expert on this, but I can think of a few things to
examine that might give a clue.
First, under 5.1, do an lsmod and note the driver(s) loaded for the
audio. Might want to examine the modprobe.conf file too.
Under 5.2, was that file changed by update? Do "updatedb" and then
"locate rpmnew" and "locate rpmsave". If any are found, that indicates
that a new config (usually) file is available or was installed. These
need to be examined and sometimes adjusted (rpmsave) or adjusted and
Check (5.1 and 5.2) /var/log/dmesg and /var/log/messages for anything
related to the sound. If the device was found, there should be something
Under 5.2, do an lsmod and see if the drivers were loaded. Also, after
the updatedb, use locate and see if the module is found.
More information about the CentOS