On Thu, 2008-07-03 at 14:44 +1000, hce wrote: > Thanks both Alex and Willam. > <snip> > > # lspci -v # Snipped non-related stuff out > > 00:11.5 Multimedia audio controller: VIA Technologies, Inc. > > VT8233/A/8235/8237 AC97 Audio Controller (rev 60) > > Subsystem: EPoX Computer Co., Ltd. Unknown device 300c > > Flags: medium devsel, IRQ 201 > > I/O ports at eb00 [size=256] > > Capabilities: [c0] Power Management version 2 > > > > Note that my capabilities are listed while yours are "access denied". > > Were you root when you ran lspci? I don't know if that is significant. > > >From root, I got following Capabilities, I guess it is 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: [50] Power Management version 2 > Capabilities: [60] Message Signalled Interrupts: 64bit+ > Queue=0/0 Enable- > Capabilities: [70] Express Unknown type IRQ 0 > Capabilities: [100] Virtual Channel > Capabilities: [130] Unknown (5) > <snip> > >> > >> The only suspecious I could find was following boot message, but I am > >> not sure it was related or not, and not sure how could fix following. > >> > >> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report > >> PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0 > >> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0 > >> PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0 > >> PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.3 > >> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.3 > >> PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.3 > >> PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.5 > >> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.5 > >> PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.5 > ><snip> > > > > AFAICT, your stuff looks OK. We need more knowledgeable help. > > > > A useful command is modinfo. Do a "man modinfo" for details. It is > > useful in investigating this stuff. Note useful lines below, like > > "depends" and "parm". E.g > > > > # modinfo snd_via82xx > > filename: /lib/modules/2.6.18-92.1.6.el5/kernel/sound/pci/snd-via82xx.ko > > license: GPL > > description: VIA VT82xx audio > > author: Jaroslav Kysela <perex at suse.cz> > > srcversion: E4EB4562EAA5912A94BAAB7 > > alias: pci:v00001106d00003059sv*sd*bc*sc*i* > > alias: pci:v00001106d00003058sv*sd*bc*sc*i* > > depends: > > snd-ac97-codec,snd-pcm,snd-page-alloc,snd-mpu401-uart,snd,gameport > > vermagic: 2.6.18-92.1.6.el5 SMP mod_unload 686 REGPARM 4KSTACKS > > gcc-4.1 > > parm: index:Index value for VIA 82xx bridge. (int) > > parm: id:ID string for VIA 82xx bridge. (charp) > > parm: mpu_port:MPU-401 port. (VT82C686x only) (long) > > parm: joystick:Enable joystick. (VT82C686x only) (bool) > > parm: ac97_clock:AC'97 codec clock (default 48000Hz). (int) > > parm: ac97_quirk:AC'97 workaround for strange hardware. > > (charp) > > parm: dxs_support:Support for DXS channels (0 = auto, 1 = > > enable, 2 = disable, 3 = 48k only, 4 = no VRA, 5 = enable any sample > > rate) (int) > > parm: enable:bool > > module_sig: <snip a very long module sig line> > > > > Maybe that "pci=routeirq" suggestion above will help? > > > > Since it was a new install, I have to ask: did you have to dink with the > > hardware at all. Maybe open the case or move it? If so, maybe a cable > > got knocked loose or the speaker wires disconnected? > > > > Other than that, lets hope someone else knows something. > > $ /sbin/modinfo snd-hda-intel > filename: /lib/modules/2.6.18-92.el5/kernel/sound/pci/hda/snd-hda-intel.ko > description: Intel HDA driver > license: GPL > srcversion: 0084BB394FD45DA3C4033DC > alias: pci:v000010DEd0000055Dsv*sd*bc*sc*i* > alias: pci:v000010DEd0000055Csv*sd*bc*sc*i* > alias: pci:v000010DEd0000044Bsv*sd*bc*sc*i* > alias: pci:v000010DEd0000044Asv*sd*bc*sc*i* > alias: pci:v000010DEd000003F0sv*sd*bc*sc*i* > alias: pci:v000010DEd000003E4sv*sd*bc*sc*i* > alias: pci:v000010DEd00000371sv*sd*bc*sc*i* > alias: pci:v000010DEd0000026Csv*sd*bc*sc*i* > alias: pci:v000010B9d00005461sv*sd*bc*sc*i* > alias: pci:v00001039d00007502sv*sd*bc*sc*i* > alias: pci:v00001106d00003288sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA48sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA40sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA38sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA30sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA28sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA20sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA18sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA10sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA08sv*sd*bc*sc*i* > alias: pci:v00001002d0000AA00sv*sd*bc*sc*i* > alias: pci:v00001002d0000960Fsv*sd*bc*sc*i* > alias: pci:v00001002d00007919sv*sd*bc*sc*i* > alias: pci:v00001002d0000793Bsv*sd*bc*sc*i* > alias: pci:v00001002d00004383sv*sd*bc*sc*i* > alias: pci:v00001002d0000437Bsv*sd*bc*sc*i* > alias: pci:v00008086d00003A6Esv*sd*bc*sc*i* > alias: pci:v00008086d00003A3Esv*sd*bc*sc*i* > alias: pci:v00008086d0000293Fsv*sd*bc*sc*i* > alias: pci:v00008086d0000293Esv*sd*bc*sc*i* > alias: pci:v00008086d0000284Bsv*sd*bc*sc*i* > alias: pci:v00008086d0000269Asv*sd*bc*sc*i* > alias: pci:v00008086d000027D8sv*sd*bc*sc*i* > alias: pci:v00008086d00002668sv*sd*bc*sc*i* > depends: snd-pcm,snd-page-alloc,snd,snd-hda-codec > vermagic: 2.6.18-92.el5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1 > parm: index:Index value for Intel HD audio interface. (int) > parm: id:ID string for Intel HD audio interface. (charp) > parm: model:Use the given board model. (charp) > parm: position_fix:Fix DMA pointer (0 = auto, 1 = none, 2 = > POSBUF, 3 = FIFO size). (int) > parm: probe_mask:Bitmask to probe codecs (default = -1). (int) > parm: single_cmd:Use single command to communicate with > codecs (for debugging only). (bool) > parm: enable_msi:Enable Message Signaled Interrupt (MSI) (int) > parm: enable:bool > module_sig: > 883f350484fb1ad1f27370acbc602e1129ac809e2c727a047f8bf9bc9f3dcc3fcfdb738316c3f09f4bd96a5da74ad996b582b45a1b2aee454aaabb > > Seems it is OK. > > I've also looked at links from Alex message, but not sure if it was > compatibale to the CentOS. How can I check alsa was installed properly > or not in my CentOS 5.2? $ rpm -qa|grep -i alsa alsa-lib-1.0.14-1.rc4.el5.i386 alsa-utils-1.0.14-3.rc4.el5.i386 $ rpm -v --verify alsa-lib-1.0.14-1.rc4.el5.i386 \ alsa-utils-1.0.14-3.rc4.el5.i386 Without the "-v", an "echo $?" should return 0. Otherwise, 2. > > > Thank you both Bill and Alex. NP. I'm thinking now, we have garnered enough new information that an assault on google might yield results. I suggest you give it a try. I decided to investigate proc. I don't know if that might be fruitful, ... BRB Well, all directories or empty files all the way down the tree. No joy in mudville. <snip> Last idea, if no one else from here chimes in. Do a google (again) and try the alsa or other Linux lists. -- Bill