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
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
If I recall you're using gnome. You should (but may not) have a volume icon on your panel. Right click that icon and ensure that the mute box is not checked. If it's not checked, select "Open Volume Control" and make sure your volume is turned up. If you still do not have sound try right clicking the volume speaker icon again and selecting "Preferences". Make sure that the correct device is selected.
I googled around and found various issues with the model of Acer you have listed, but sound didn't seem to be a problem save for one user using Ubuntu (I didn't spend that much time looking, sorry) who only got sound out of one speaker. A Fedora review of sorts listed the chipset as just working, but I believe that was for Fedora 8.
HTH
Alex White
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
If I recall you're using gnome. You should (but may not) have a volume icon on your panel. Right click that icon and ensure that the mute box is not checked. If it's not checked, select "Open Volume Control" and make sure your volume is turned up. If you still do not have sound try right clicking the volume speaker icon again and selecting "Preferences". Make sure that the correct device is selected.
Be aware that the volume control panel default settings may not show all the pertinent controls. In that panel you may need to edit preferences to show such things as PCM control, etc. Some of these may also be muted and/or set to very low volumes.
<snip>
HTH
Alex White
On Tue, Jul 1, 2008 at 7:20 PM, William L. Maltby CentOS4Bill@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?
No.
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>
If I recall you're using gnome. You should (but may not) have a volume icon on your panel. Right click that icon and ensure that the mute box is not checked. If it's not checked, select "Open Volume Control" and make sure your volume is turned up. If you still do not have sound try right clicking the volume speaker icon again and selecting "Preferences". Make sure that the correct device is selected.
All checked, no problem at all.
Be aware that the volume control panel default settings may not show all the pertinent controls. In that panel you may need to edit preferences to show such things as PCM control, etc. Some of these may also be muted and/or set to very low volumes.
The Volume Control Preference is set to:
HDA Intel (Alsa mixer)
PCM
Mute is not checked, and the volumes are adjusted to maximum levels.
Thank you.
Kind Regards,
Jim
On Wed, 2008-07-02 at 16:52 +1000, hce wrote:
On Tue, Jul 1, 2008 at 7:20 PM, William L. Maltby CentOS4Bill@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?
No.
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>
<snip>
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 installed (rpmnew).
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 there.
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.
HTH
On Wed, Jul 2, 2008 at 9:36 PM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Wed, 2008-07-02 at 16:52 +1000, hce wrote:
On Tue, Jul 1, 2008 at 7:20 PM, William L. Maltby CentOS4Bill@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?
No.
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>
<snip>
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.
Please see following results from modproble.conf and lsmod. I can see that the soundcore was loaded, I guess the audio module was loaded, right?
$ cat /etc/modprobe.conf alias eth0 tg3 alias scsi_hostadapter ata_piix alias scsi_hostadapter1 ahci alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel
$ /sbin/lsmod Module Size Used by i915 23745 2 drm 65493 3 i915 ipv6 258273 24 xfrm_nalgo 13765 1 ipv6 crypto_api 11969 1 xfrm_nalgo autofs4 24517 2 hidp 23105 2 rfcomm 42457 0 l2cap 29505 10 hidp,rfcomm bluetooth 53797 5 hidp,rfcomm,l2cap sunrpc 144893 1 cpufreq_ondemand 12493 1 dm_mirror 29253 0 dm_multipath 22089 0 dm_mod 61661 2 dm_mirror,dm_multipath video 21193 0 sbs 18533 0 backlight 10049 1 video i2c_ec 9025 1 sbs button 10705 0 battery 13637 0 asus_acpi 19289 0 ac 9157 0 parport_pc 29157 0 lp 15849 0 parport 37513 2 parport_pc,lp joydev 13313 0 snd_hda_intel 24793 1 snd_hda_codec 210881 1 snd_hda_intel snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 11725 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 42945 0 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72005 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 24517 2 snd_seq,snd_pcm snd 52421 11 snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 11553 1 snd sg 36189 0 ide_cd 40033 0 snd_page_alloc 14281 2 snd_hda_intel,snd_pcm sdhci 21337 0 mmc_core 27457 1 sdhci cdrom 36705 1 ide_cd pcspkr 7105 0 tg3 107717 0 i2c_i801 11597 0 i2c_core 23745 2 i2c_ec,i2c_i801 serio_raw 10693 0 ata_piix 22341 0 ahci 30149 2 libata 143997 2 ata_piix,ahci sd_mod 24897 3 scsi_mod 134605 3 sg,libata,sd_mod ext3 123593 2 jbd 56553 1 ext3 uhci_hcd 25421 0 ohci_hcd 23261 0 ehci_hcd 33357 0
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 installed (rpmnew).
The 5.2 was installed from scratch, it was not updated from an old version.
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 there.
I've checked dmesg and messages, but could not find any word to Audio, or audio, or sound. But again, I checked dmesg and messages from my desktop which installed FC7 and I could not find anything to audio and sound as well.
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
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.
What is the name of the audio module and driver from lsmod? I can only found soundcore as above.
Thank you so much.
Kind Regards,
Jim
HTH
Bill
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
hce wrote:
I'm certainly not expert on this, but I can think of a few things to examine that might give a clue.
That makes you and me both.
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.
Please see following results from modproble.conf and lsmod. I can see that the soundcore was loaded, I guess the audio module was loaded, right?
$ cat /etc/modprobe.conf alias eth0 tg3 alias scsi_hostadapter ata_piix alias scsi_hostadapter1 ahci alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel
<snipped some of the output>
snd_hda_intel 24793 1 snd_hda_codec 210881 1 snd_hda_intel snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 11725 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 42945 0 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72005 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 24517 2 snd_seq,snd_pcm snd 52421 11 snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 11553 1 snd sg 36189 0 ide_cd 40033 0 snd_page_alloc 14281 2 snd_hda_intel,snd_pcm
The 5.2 was installed from scratch, it was not updated from an old version.
<snipped>
I've checked dmesg and messages, but could not find any word to Audio, or audio, or sound. But again, I checked dmesg and messages from my desktop which installed FC7 and I could not find anything to audio and sound as well.
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
I can't speak to this, I'm not familiar with the above output. I'll look into it this evening.
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.
What is the name of the audio module and driver from lsmod? I can only found soundcore as above.
The module's name is snd-hda-intel. It's listed in your output from lsmod. I see it up there, I removed most of the irrelevant (to me at least) modules that were in there so you could more easily see it.
Thank you so much.
Kind Regards,
Jim
What's interesting about your problem is that it was mentioned in several Ubuntu forums while I was googling. The solutions I've seen mentioned both in Suse and Ubuntu forums is to use the latest version of Alsa. That may require some 'by hand' installation, and I am not sure you want to do that.
Here are a couple of links that mention the card "just working" and issues similar to yours.
http://bluegargoyle.com/Lenovo-ThinkPad-R61i-CentOS5-MAJ20080428.html Mind the wrapping, but this link shows the controller just working.
http://ubuntuforums.org/archive/index.php/t-511058.html Someone having the no sound problem on a different laptop make and model, but same sound controller as yours.
I looked around for some devices with that chipset, but I don't have any, so I can't experiment. I'll keep scouring the net.
On Thu, 2008-07-03 at 10:22 +1000, hce wrote:
On Wed, Jul 2, 2008 at 9:36 PM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Wed, 2008-07-02 at 16:52 +1000, hce wrote:
On Tue, Jul 1, 2008 at 7:20 PM, William L. Maltby CentOS4Bill@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?
No.
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>
Hmmm... Since I know very little about this stuff, I thought I would look (and maybe learn something too). I have a different chip set, but some things should be in common. My hope is something visual will jump out at you or someone who is knowledgeable will spot something.
# 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.
<snip>
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.
Please see following results from modproble.conf and lsmod. I can see that the soundcore was loaded, I guess the audio module was loaded, right?
$ cat /etc/modprobe.conf alias eth0 tg3 alias scsi_hostadapter ata_piix alias scsi_hostadapter1 ahci alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel
# Pertinent portion of my modprobe.conf
alias snd-card-0 snd-via82xx options snd-card-0 index=0 options snd-via82xx index=0 remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-via82xx
Looks OK to me.
$ /sbin/lsmod Module Size Used by
<snip unrelated stuff>
snd_hda_intel 24793 1 snd_hda_codec 210881 1 snd_hda_intel snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 11725 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 42945 0 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72005 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 24517 2 snd_seq,snd_pcm snd 52421 11 snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 11553 1 snd sg 36189 0 ide_cd 40033 0 snd_page_alloc 14281 2 snd_hda_intel,snd_pcm
<snip unrelated stuff>
Here is the relevant stuff from my unit.
# Snipped out irrelevant stuff, edited long lines Module Size Used by snd_via82xx 30041 1 gameport 18633 1 snd_via82xx snd_ac97_codec 93025 1 snd_via82xx ac97_bus 6337 1 snd_ac97_codec snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_pcm_oss 42945 0 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72005 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss snd_timer 24517 2 snd_seq,snd_pcm snd_page_alloc 14281 2 snd_via82xx,snd_pcm snd_mpu401_uart 12097 1 snd_via82xx snd_rawmidi 26561 1 snd_mpu401_uart snd_seq_device 11725 4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi snd 52421 13 snd_via82xx,snd_ac97_codec,\ snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,\ snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 11553 1 snd
Again, looks OK to my ignorant eyes.
<snip>
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 there.
I've checked dmesg and messages, but could not find any word to Audio, or audio, or sound. But again, I checked dmesg and messages from my desktop which installed FC7 and I could not find anything to audio and sound as well.
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
Except for the first line, I don't know if the above lines hold any hope. But I think the first line might be useful suggestion?
Mine has that first line too
# I thought this might be useful, unsure though. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
<snip>
What is the name of the audio module and driver from lsmod? I can only found soundcore as above.
Mine is the snd_via82xx. Yours s/b snd-hda-intel.
Thank you so much.
Kind Regards,
Jim
<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@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.
HTH
Thanks both Alex and Willam.
On Thu, Jul 3, 2008 at 11:54 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Thu, 2008-07-03 at 10:22 +1000, hce wrote:
On Wed, Jul 2, 2008 at 9:36 PM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Wed, 2008-07-02 at 16:52 +1000, hce wrote:
On Tue, Jul 1, 2008 at 7:20 PM, William L. Maltby CentOS4Bill@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?
No.
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>
Hmmm... Since I know very little about this stuff, I thought I would look (and maybe learn something too). I have a different chip set, but some things should be in common. My hope is something visual will jump out at you or someone who is knowledgeable will spot something.
# 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>
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.
Please see following results from modproble.conf and lsmod. I can see that the soundcore was loaded, I guess the audio module was loaded, right?
$ cat /etc/modprobe.conf alias eth0 tg3 alias scsi_hostadapter ata_piix alias scsi_hostadapter1 ahci alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel
# Pertinent portion of my modprobe.conf
alias snd-card-0 snd-via82xx options snd-card-0 index=0 options snd-via82xx index=0 remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-via82xx
Looks OK to me.
$ /sbin/lsmod Module Size Used by
<snip unrelated stuff>
snd_hda_intel 24793 1 snd_hda_codec 210881 1 snd_hda_intel snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 11725 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 42945 0 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72005 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 24517 2 snd_seq,snd_pcm snd 52421 11 snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 11553 1 snd sg 36189 0 ide_cd 40033 0 snd_page_alloc 14281 2 snd_hda_intel,snd_pcm
<snip unrelated stuff>
Here is the relevant stuff from my unit.
# Snipped out irrelevant stuff, edited long lines Module Size Used by snd_via82xx 30041 1 gameport 18633 1 snd_via82xx snd_ac97_codec 93025 1 snd_via82xx ac97_bus 6337 1 snd_ac97_codec snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_pcm_oss 42945 0 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72005 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss snd_timer 24517 2 snd_seq,snd_pcm snd_page_alloc 14281 2 snd_via82xx,snd_pcm snd_mpu401_uart 12097 1 snd_via82xx snd_rawmidi 26561 1 snd_mpu401_uart snd_seq_device 11725 4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi snd 52421 13 snd_via82xx,snd_ac97_codec,\ snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,\ snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 11553 1 snd
Again, looks OK to my ignorant eyes.
<snip>
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 there.
I've checked dmesg and messages, but could not find any word to Audio, or audio, or sound. But again, I checked dmesg and messages from my desktop which installed FC7 and I could not find anything to audio and sound as well.
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
Except for the first line, I don't know if the above lines hold any hope. But I think the first line might be useful suggestion?
Mine has that first line too
# I thought this might be useful, unsure though. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
<snip>
What is the name of the audio module and driver from lsmod? I can only found soundcore as above.
Mine is the snd_via82xx. Yours s/b snd-hda-intel.
Thank you so much.
Kind Regards,
Jim
<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@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?
Thank you both Bill and Alex.
HTH
Bill
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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@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.
William L. Maltby wrote:
Thank you both Bill and Alex.
NP.
We're happy to try to help. I have a friend with your model of laptop, I'll see if I can sucker him into letting me futz around with it for a day or two. I'll report back!
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.
Not entirely sure what one would glean from /proc other than that the card is present and drivers are loaded for it. There's lengthy output for my sound device. I won't paste all of it, but everything is located in /proc/asound. My device is also listed under /proc/devices as one would expect.
I don't muck in /proc very often other than for testing network setups and obtaining cpu and memory information, so the output for my soundcard means next to nothing to me other than I know the correct driver is loaded.
[prata@crane asound]$ ls card0 cards devices modules oss pcm seq timers V8237 version
[prata@crane asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_via82xx 0 [V8237 ]: VIA8237 - VIA 8237 VIA 8237 with ALC850 at 0xe800, irq 209
Given that your machine is reporting the device as present (despite not getting any sound) I am under the impression anything you get out of proc would be correct as well. Just to through more confusion on the issue. ^_^
Last idea, if no one else from here chimes in. Do a google (again) and try the alsa or other Linux lists.
I don't know why I never googled around on the Alsa lists. That was stupid of me. Opensuse has some forums with this problem as well. I didn't see a fix, but I didn't spend too much time looking there. If there is a fix, maybe they have an srpm that could be massaged into working in CentOS?
If you do find a solution elsewhere I'd really appreciate a link or something just for my own knowledge down the road.
Sincerely,
Alex White
On Thu, 2008-07-03 at 07:57 -0500, Alex White wrote:
<snip>
Not entirely sure what one would glean from /proc other than that the card is present and drivers are loaded for it. There's lengthy output for my sound device. I won't paste all of it, but everything is located in /proc/asound. My device is also listed under /proc/devices as one would expect.
/proc delivers the *truth*. And for some things, settings can be changed there that are not easily addressed through utilities.
I don't muck in /proc very often other than for testing network setups and obtaining cpu and memory information, so the output for my soundcard means next to nothing to me other than I know the correct driver is loaded.
[prata@crane asound]$ ls card0 cards devices modules oss pcm seq timers V8237 version
[prata@crane asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_via82xx 0 [V8237 ]: VIA8237 - VIA 8237 VIA 8237 with ALC850 at 0xe800, irq 209
*chuckle* I forgot I was looking at files that always report 0 length - /proc. So, just in case something is useful, I ran the following and included its output. Then I snipped out things like hex values that I figured would be *really* machine specific or indecipherable by the likes of me (us?).
I inserted some commentry if one of the settings looked like it might yield a clue, like "closed" when we might expect open. I'm not using my sound ATM, so mine s/b closed.
After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files.
# cd /proc/asound # find . -type f -exec echo {} ; -exec cat {} ; >/tmp/asound ./card0/oss_mixer #### Control panel settings? #### VOLUME "Master" 0 BASS "" 0 TREBLE "" 0 SYNTH "" 0 PCM "PCM" 0 SPEAKER "PC Speaker" 0 LINE "Line" 0 MIC "Mic" 0 CD "CD" 0 IMIX "" 0 ALTPCM "" 0 RECLEV "" 0 IGAIN "Capture" 0 OGAIN "" 0 LINE1 "Aux" 0 LINE2 "" 0 LINE3 "" 0 DIGITAL1 "IEC958" 0 DIGITAL2 "" 0 DIGITAL3 "" 0 PHONEIN "Phone" 0 PHONEOUT "Master Mono" 0 VIDEO "Video" 0 RADIO "" 0 MONITOR "" 0 ./card0/id V8237 ./card0/via82xx VIA 8237 with ALC655 at 0xeb00, irq 201 <snip "greek to me"> ./card0/pcm1c/oss ./card0/pcm1c/sub0/prealloc_max 128 ./card0/pcm1c/sub0/prealloc 64 #### On some of the following, should see open if sound is in use? #### ./card0/pcm1c/sub0/status closed ./card0/pcm1c/sub0/sw_params closed ./card0/pcm1c/sub0/hw_params closed ./card0/pcm1c/sub0/info card: 0 device: 1 subdevice: 0 stream: CAPTURE id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 #### Devices available should = count? #### subdevices_count: 1 subdevices_avail: 1 ./card0/pcm1c/info card: 0 device: 1 subdevice: 0 stream: CAPTURE id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ./card0/pcm1p/oss ./card0/pcm1p/sub0/prealloc_max 128 ./card0/pcm1p/sub0/prealloc 64 ./card0/pcm1p/sub0/status closed ./card0/pcm1p/sub0/sw_params closed ./card0/pcm1p/sub0/hw_params closed ./card0/pcm1p/sub0/info card: 0 device: 1 subdevice: 0 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ./card0/pcm1p/info card: 0 device: 1 subdevice: 0 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ./card0/pcm0c/oss ./card0/pcm0c/sub0/prealloc_max 128 ./card0/pcm0c/sub0/prealloc 64 ./card0/pcm0c/sub0/status closed ./card0/pcm0c/sub0/sw_params closed ./card0/pcm0c/sub0/hw_params closed ./card0/pcm0c/sub0/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ./card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ./card0/pcm0p/oss ./card0/pcm0p/sub3/prealloc_max 128 ./card0/pcm0p/sub3/prealloc 64 ./card0/pcm0p/sub3/status closed ./card0/pcm0p/sub3/sw_params closed ./card0/pcm0p/sub3/hw_params closed ./card0/pcm0p/sub3/info card: 0 device: 0 subdevice: 3 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #3 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ./card0/pcm0p/sub2/prealloc_max 128 ./card0/pcm0p/sub2/prealloc 64 ./card0/pcm0p/sub2/status closed ./card0/pcm0p/sub2/sw_params closed ./card0/pcm0p/sub2/hw_params closed ./card0/pcm0p/sub2/info card: 0 device: 0 subdevice: 2 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #2 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ./card0/pcm0p/sub1/prealloc_max 128 ./card0/pcm0p/sub1/prealloc 64 ./card0/pcm0p/sub1/status closed ./card0/pcm0p/sub1/sw_params closed ./card0/pcm0p/sub1/hw_params closed ./card0/pcm0p/sub1/info card: 0 device: 0 subdevice: 1 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #1 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ./card0/pcm0p/sub0/prealloc_max 128 ./card0/pcm0p/sub0/prealloc 64 ./card0/pcm0p/sub0/status closed ./card0/pcm0p/sub0/sw_params closed ./card0/pcm0p/sub0/hw_params closed ./card0/pcm0p/sub0/info card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ./card0/pcm0p/info card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: VIA 8237 name: VIA 8237 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ./card0/codec97#0/ac97#0-0+regs <snip "it's greek to me"> ./card0/codec97#0/ac97#0-0 0-0/0: Realtek ALC655 rev 0
PCI Subsys Vendor: 0x1695 PCI Subsys Device: 0x300c
Revision : 0x00 Compat. Class : 0x00 Subsys. Vendor ID: 0xffff Subsys. ID : 0xffff
Capabilities : DAC resolution : 16-bit ADC resolution : 16-bit 3D enhancement : No 3D Stereo Enhancement
Current setup Mic gain : +0dB [+0dB] POP path : pre 3D Sim. stereo : off 3D enhancement : off Loudness : off Mono output : MIX Mic select : Mic1 ADC/DAC loopback : off Extended ID : codec=0 rev=2 LDAC SDAC CDAC DSA=0 SPDIF Extended status : SPCV LDAC SDAC CDAC SPDIF=10/11 SPDIF Control : Consumer PCM Category=0x2 Generation=1 Rate=48kHz ./pcm 00-01: VIA 8237 : VIA 8237 : playback 1 : capture 1 00-00: VIA 8237 : VIA 8237 : playback 4 : capture 1 ./timers <snip "it's greek to me"> ./modules 0 snd_via82xx ./cards 0 [V8237 ]: VIA8237 - VIA 8237 VIA 8237 with ALC655 at 0xeb00, irq 201 ./devices 2: : timer 3: : sequencer 4: [ 0- 1]: digital audio playback 5: [ 0- 1]: digital audio capture 6: [ 0- 0]: digital audio playback 7: [ 0- 0]: digital audio capture 8: [ 0] : control ./version Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC). ./seq/oss OSS sequencer emulation version 0.1.8 ALSA client number 15 ALSA receiver port 0
Number of applications: 0
Number of synth devices: 0
Number of MIDI devices: 1
midi 0: [Midi Through Port-0] ALSA port 14:0 capability read/write / opened none ./seq/timer ./seq/clients Client info cur clients : 3 peak clients : 3 max clients : 192
Client 0 : "System" [Kernel] Port 0 : "Timer" (Rwe-) Port 1 : "Announce" (R-e-) Connecting To: 15:0 Client 14 : "Midi Through" [Kernel] Port 0 : "Midi Through Port-0" (RWe-) Client 15 : "OSS sequencer" [Kernel] Port 0 : "Receiver" (-we-) Connected From: 0:1 ./seq/queues ./seq/drivers snd-seq-oss,loaded,0 ./oss/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.14rc3 emulation code) Kernel: Linux centos501.homegroannetworking 2.6.18-92.1.1.el5 #1 SMP Sat Jun 21 19:04:27 EDT 2008 i686 Config options: 0
Installed drivers: Type 10: ALSA emulation
Card config: VIA 8237 with ALC655 at 0xeb00, irq 201
Audio devices: 0: VIA 8237 (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers: 31: system timer
Mixers: 0: Realtek ALC655 rev 0 ./oss/devices 0: [0- 0]: mixer 1: : sequencer 3: [0- 0]: digital audio 4: [0- 0]: digital audio 8: : sequencer 12: [0- 1]: digital audio
Given that your machine is reporting the device as present (despite not getting any sound) I am under the impression anything you get out of proc would be correct as well. Just to through more confusion on the issue. ^_^
As you can see above, we would expect to see some things change if things are working. I'll follow up with a diff when the CD is playing.
Last idea, if no one else from here chimes in. Do a google (again) and try the alsa or other Linux lists.
I don't know why I never googled around on the Alsa lists. That was stupid of me. Opensuse has some forums with this problem as well. I didn't see a fix, but I didn't spend too much time looking there. If there is a fix, maybe they have an srpm that could be massaged into working in CentOS?
I'm still looking for a fix on mine to get all 4 speakers working. I found the duplicate front fix, but no joy with that.
If you do find a solution elsewhere I'd really appreciate a link or something just for my own knowledge down the road.
Sincerely,
Alex White
On Thu, 2008-07-03 at 10:18 -0400, William L. Maltby wrote:
<snip>
After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files.
<snip>
OK. I've attached a diff and sdiff output. Used together, fast identification of what changed from idle to playing can be achieved.
I would expect you should see something similar, adjusted for your setup.
Maybe a clue will emerge.
This is on a fully updated CentOS 5.2.
BTW, forgot to ask if you have a CD player (can't remember the start of thread). If so, when you insert a CD, does it show on the desktop? And what application do you use to play it? I'm using the stock cd player that comes with the Gnome desktop. On 5.1 I've also used mplayer for DVD on this w/o problems (totem doesn't work - missing plugins and never had an interesting in tracking them down).
HTH
On Fri, Jul 4, 2008 at 12:18 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Thu, 2008-07-03 at 07:57 -0500, Alex White wrote:
<snip>
Not entirely sure what one would glean from /proc other than that the card is present and drivers are loaded for it. There's lengthy output for my sound device. I won't paste all of it, but everything is located in /proc/asound. My device is also listed under /proc/devices as one would expect.
/proc delivers the *truth*. And for some things, settings can be changed there that are not easily addressed through utilities. ..... After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files. # cd /proc/asound # find . -type f -exec echo {} ; -exec cat {} ; >/tmp/asound
I guess alsa and /proc are all fine on my machine, but I've got a blank result on /proc/asound running following find, no sure if that was significant:
[asound]$ find . -type f -exec echo {} ; -exec cat {} ; > /tmp/asound
$ rpm -qa | grep -i alsaalsa-utils-1.0.14-3.rc4.el5 alsa-lib-devel-1.0.14-1.rc4.el5 alsa-lib-1.0.14-1.rc4.el5
]$ rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 alsa-utils-1.0.14-3.rc4.el5.i386 | echo $? 0
[asound]$ ls card0 cards devices Intel modules oss pcm seq timers version
[asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_hda_intel 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf0500000 irq 66
I've also tried to ls in /proc/asound/Intel:
$ ls codec#0 codec#1 id oss_mixer pcm0c pcm0p pcm2c
Seems, all drivers there, is there any command such as cat to verify low level drivers by playing a sound?
Thank you.
Jim
On Fri, 2008-07-04 at 12:41 +1000, hce wrote:
On Fri, Jul 4, 2008 at 12:18 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Thu, 2008-07-03 at 07:57 -0500, Alex White wrote:
<snip>
<snip>
/proc delivers the *truth*. And for some things, settings can be changed there that are not easily addressed through utilities. ..... After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files. # cd /proc/asound # find . -type f -exec echo {} ; -exec cat {} ; >/tmp/asound
I guess alsa and /proc are all fine on my machine, but I've got a blank result on /proc/asound running following find, no sure if that was significant:
Blank result? I'm skeptical about that. <*scratching head*>
[asound]$ find . -type f -exec echo {} ; -exec cat {} ; > /tmp/asound
The /tmp/asound file should contain at least the file names that it found. And I can't believe that trying to play something would remove the contents of those files. 1) It would have to be root and 2) IIRC, we can't remove stuff in /proc as it is from the kernel and not a real file system and 3) We could only change the contents of *some* things.
I tested the above command with a C&P and it worked. Maybe you had a typo or the frustration is getting to you and you examined the wrong file?
$ rpm -qa | grep -i alsaalsa-utils-1.0.14-3.rc4.el5 alsa-lib-devel-1.0.14-1.rc4.el5 alsa-lib-1.0.14-1.rc4.el5
]$ rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 alsa-utils-1.0.14-3.rc4.el5.i386 | echo $? 0
The above command s/b rpm --verify .... ; echo $? ----------------------------------------|
If you meant "||", it would still be logically incorrect as we want to see the return value, regardless.
[asound]$ ls card0 cards devices Intel modules oss pcm seq timers version
[asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_hda_intel 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf0500000 irq 66
I've also tried to ls in /proc/asound/Intel:
$ ls codec#0 codec#1 id oss_mixer pcm0c pcm0p pcm2c
Seems, all drivers there, is there any command such as cat to verify low level drivers by playing a sound?
You need an application to do that. I've only used various Gnome desktop facilities. The file manager (Nautilus?) should do that when you double click a sound file. I'll test ... BRB
Yep. I went to /usr/share/sounds/alsa, using file manager, and it opened totem and played the sounds. This means that you could open totem directly, or any other sound playing application and try it. Unfortunately, unless we suspect broken applications are the problem, this really only is the same as what you tried to do originally, less the CD.
Thank you.
Jim
<snip>
On Fri, Jul 4, 2008 at 3:10 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
You need an application to do that. I've only used various Gnome desktop facilities. The file manager (Nautilus?) should do that when you double click a sound file. I'll test ... BRB
Yep. I went to /usr/share/sounds/alsa, using file manager, and it opened totem and played the sounds. This means that you could open totem directly, or any other sound playing application and try it. Unfortunately, unless we suspect broken applications are the problem, this really only is the same as what you tried to do originally, less the CD.
This is too weird for me. Yesterday, I could not get the volume control to do anything, including unmute the sound.
Today, I went to /usr/share/sounds/alsa and played the sounds with mplayer. After fiddling with the volume controls for a few seconds, suddenly everything is working fine.
Note that this _is_ a desktop, but hanged if I know what happened. Pilot error? (Nah, couldn't be! ;^)
mhr
PS: Another really strange item - on the FC8 boot, mplayer (the kernel?) was running the sound too fast, so I had to slow it down to 95% speed. On C 5.2, it works as advertised (no speed reduction required).
On 7/4/08, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Fri, 2008-07-04 at 12:41 +1000, hce wrote:
On Fri, Jul 4, 2008 at 12:18 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Thu, 2008-07-03 at 07:57 -0500, Alex White wrote:
<snip>
<snip>
/proc delivers the *truth*. And for some things, settings can be changed there that are not easily addressed through utilities. ..... After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files. # cd /proc/asound # find . -type f -exec echo {} ; -exec cat {} ; >/tmp/asound
I guess alsa and /proc are all fine on my machine, but I've got a blank result on /proc/asound running following find, no sure if that was significant:
Blank result? I'm skeptical about that. <*scratching head*>
[asound]$ find . -type f -exec echo {} ; -exec cat {} ; > /tmp/asound
The /tmp/asound file should contain at least the file names that it found. And I can't believe that trying to play something would remove the contents of those files. 1) It would have to be root and 2) IIRC, we can't remove stuff in /proc as it is from the kernel and not a real file system and 3) We could only change the contents of *some* things.
I tested the above command with a C&P and it worked. Maybe you had a typo or the frustration is getting to you and you examined the wrong file?
I used above command with a C&P as well. I've also verified the command to my another FC7 box which has sound worked well, it also shown a blank result as well.
$ rpm -qa | grep -i alsaalsa-utils-1.0.14-3.rc4.el5 alsa-lib-devel-1.0.14-1.rc4.el5 alsa-lib-1.0.14-1.rc4.el5
]$ rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 alsa-utils-1.0.14-3.rc4.el5.i386 | echo $? 0
The above command s/b rpm --verify .... ; echo $? ----------------------------------------|
If you meant "||", it would still be logically incorrect as we want to see the return value, regardless.
Actually, I tried without echo $? first, it display lots of parameters, seems file. I can try the echo $? again, what is the correct command for it? Is following command correct?
rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 lsa-utils-1.0.14-3.rc4.el5.i386; echo $?
[asound]$ ls card0 cards devices Intel modules oss pcm seq timers version
[asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_hda_intel 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf0500000 irq 66
I've also tried to ls in /proc/asound/Intel:
$ ls codec#0 codec#1 id oss_mixer pcm0c pcm0p pcm2c
Seems, all drivers there, is there any command such as cat to verify low level drivers by playing a sound?
You need an application to do that. I've only used various Gnome desktop facilities. The file manager (Nautilus?) should do that when you double click a sound file. I'll test ... BRB
Yep. I went to /usr/share/sounds/alsa, using file manager, and it opened totem and played the sounds. This means that you could open totem directly, or any other sound playing application and try it. Unfortunately, unless we suspect broken applications are the problem, this really only is the same as what you tried to do originally, less the CD.
I can use vlc to play the *.wav or other audio files, but I tried to figure out where is the block or missing link with the audio. Right now, no sound when I run vlc to play audio files. If I could check and play in some means with low level driver first, I guess I could find if the problem is high level applications or low lever drivers. Seems that the drivers all there, but don't know if them are working or not.
Thank you.
Kind Regards,
Jim
Thank you.
Jim
<snip>
-- Bill
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, 2008-07-07 at 11:48 +1000, hce wrote:
On 7/4/08, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Fri, 2008-07-04 at 12:41 +1000, hce wrote:
On Fri, Jul 4, 2008 at 12:18 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
<snip>
After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files. # cd /proc/asound # find . -type f -exec echo {} ; -exec cat {} ; >/tmp/asound
I guess alsa and /proc are all fine on my machine, but I've got a blank result on /proc/asound running following find, no sure if that was significant:
If all files below /proc/asound are empty after trying to play a sound are empty, things can't be alright and that is significant. What it implies, I haven't a clue.
Blank result? I'm skeptical about that. <*scratching head*>
[asound]$ find . -type f -exec echo {} ; -exec cat {} ; > /tmp/asound
The /tmp/asound file should contain at least the file names that it
s/file/files found under asound and its sub-dirs/
found. And I can't believe that trying to play something would remove the contents of those files. 1) It would have to be root and 2) IIRC, we can't remove stuff in /proc as it is from the kernel and not a real file system and 3) We could only change the contents of *some* things.
I tested the above command with a C&P and it worked. Maybe you had a typo or the frustration is getting to you and you examined the wrong file?
I used above command with a C&P as well. I've also verified the command to my another FC7 box which has sound worked well, it also shown a blank result as well.
That puts me at a total loss. If every file below the /proc/asound tree is empty after trying to play a file/CD is empty, then all the driver modules would be gone. Then an lsmod should show no drivers loaded. If drivers appear in lsmod, some files under asound and its sub-directories have to be non-empty.
Remember that an ls -lR /proc/asound will show 0-length files even though there is something in those files. If you depended on ls to determine if a file was empty, that's a mistake.
$ rpm -qa | grep -i alsaalsa-utils-1.0.14-3.rc4.el5 alsa-lib-devel-1.0.14-1.rc4.el5 alsa-lib-1.0.14-1.rc4.el5
]$ rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 alsa-utils-1.0.14-3.rc4.el5.i386 | echo $? 0
The above command s/b rpm --verify .... ; echo $? ----------------------------------------|
If you meant "||", it would still be logically incorrect as we want to see the return value, regardless.
Actually, I tried without echo $? first, it display lots of parameters, seems file. I can try the echo $? again, what is the correct command for it? Is following command correct?
rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 lsa-utils-1.0.14-3.rc4.el5.i386; echo $?
If that is all on one line or the first line ends with a " ", yes. But the form with "-v --verify" is useful too. It will let you know if something is scrogged. The man page for rpm will tell the meaning of the output. If you put a redirect to a temporary file, you can look at the results. Something like this
rpm -v --verify ... ... >/tmp/rpm.lst; echo $?
[asound]$ ls card0 cards devices Intel modules oss pcm seq timers version
[asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_hda_intel 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf0500000 irq 66
I've also tried to ls in /proc/asound/Intel:
$ ls codec#0 codec#1 id oss_mixer pcm0c pcm0p pcm2c
Seems, all drivers there, is there any command such as cat to verify low level drivers by playing a sound?
You need an application to do that. I've only used various Gnome desktop facilities. The file manager (Nautilus?) should do that when you double click a sound file. I'll test ... BRB
Yep. I went to /usr/share/sounds/alsa, using file manager, and it opened totem and played the sounds. This means that you could open totem directly, or any other sound playing application and try it. Unfortunately, unless we suspect broken applications are the problem, this really only is the same as what you tried to do originally, less the CD.
I can use vlc to play the *.wav or other audio files, but I tried to figure out where is the block or missing link with the audio. Right now, no sound when I run vlc to play audio files. If I could check and play in some means with low level driver first, I guess I could find if the problem is high level applications or low lever drivers. Seems that the drivers all there, but don't know if them are working or not.
ISTR that long ago there were CLI sound/CD players. I don't know if there are any left. I suggest a Google.
Thank you.
Kind Regards,
Jim
<snip sig stuff>
On Monday 07 July 2008 10:50:11 William L. Maltby wrote:
On Mon, 2008-07-07 at 11:48 +1000, hce wrote:
On 7/4/08, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Fri, 2008-07-04 at 12:41 +1000, hce wrote:
On Fri, Jul 4, 2008 at 12:18 AM, William L. Maltby
CentOS4Bill@triad.rr.com wrote:
<snip>
After this, I'll pop in Mark Knoppfler's "Shangri-La" and diff the two files. # cd /proc/asound # find . -type f -exec echo {} ; -exec cat {} ; >/tmp/asound
I guess alsa and /proc are all fine on my machine, but I've got a blank result on /proc/asound running following find, no sure if that was significant:
If all files below /proc/asound are empty after trying to play a sound are empty, things can't be alright and that is significant. What it implies, I haven't a clue.
Blank result? I'm skeptical about that. <*scratching head*>
[asound]$ find . -type f -exec echo {} ; -exec cat {} ; > /tmp/asound
The /tmp/asound file should contain at least the file names that it
s/file/files found under asound and its sub-dirs/
found. And I can't believe that trying to play something would remove the contents of those files. 1) It would have to be root and 2) IIRC, we can't remove stuff in /proc as it is from the kernel and not a real file system and 3) We could only change the contents of *some* things.
I tested the above command with a C&P and it worked. Maybe you had a typo or the frustration is getting to you and you examined the wrong file?
I used above command with a C&P as well. I've also verified the command to my another FC7 box which has sound worked well, it also shown a blank result as well.
That puts me at a total loss. If every file below the /proc/asound tree is empty after trying to play a file/CD is empty, then all the driver modules would be gone. Then an lsmod should show no drivers loaded. If drivers appear in lsmod, some files under asound and its sub-directories have to be non-empty.
Remember that an ls -lR /proc/asound will show 0-length files even though there is something in those files. If you depended on ls to determine if a file was empty, that's a mistake.
$ rpm -qa | grep -i alsaalsa-utils-1.0.14-3.rc4.el5 alsa-lib-devel-1.0.14-1.rc4.el5 alsa-lib-1.0.14-1.rc4.el5
]$ rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 alsa-utils-1.0.14-3.rc4.el5.i386 | echo $? 0
The above command s/b rpm --verify .... ; echo $? ----------------------------------------|
If you meant "||", it would still be logically incorrect as we want to see the return value, regardless.
Actually, I tried without echo $? first, it display lots of parameters, seems file. I can try the echo $? again, what is the correct command for it? Is following command correct?
rpm --verify alsa-lib-1.0.14-1.rc4.el5.i386 lsa-utils-1.0.14-3.rc4.el5.i386; echo $?
If that is all on one line or the first line ends with a " ", yes. But the form with "-v --verify" is useful too. It will let you know if something is scrogged. The man page for rpm will tell the meaning of the output. If you put a redirect to a temporary file, you can look at the results. Something like this
rpm -v --verify ... ... >/tmp/rpm.lst; echo $?
[asound]$ ls card0 cards devices Intel modules oss pcm seq timers version
[asound]$ pwd && cat modules && cat cards /proc/asound 0 snd_hda_intel 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf0500000 irq 66
I've also tried to ls in /proc/asound/Intel:
$ ls codec#0 codec#1 id oss_mixer pcm0c pcm0p pcm2c
Seems, all drivers there, is there any command such as cat to verify low level drivers by playing a sound?
You need an application to do that. I've only used various Gnome desktop facilities. The file manager (Nautilus?) should do that when you double click a sound file. I'll test ... BRB
Yep. I went to /usr/share/sounds/alsa, using file manager, and it opened totem and played the sounds. This means that you could open totem directly, or any other sound playing application and try it. Unfortunately, unless we suspect broken applications are the problem, this really only is the same as what you tried to do originally, less the CD.
I can use vlc to play the *.wav or other audio files, but I tried to figure out where is the block or missing link with the audio. Right now, no sound when I run vlc to play audio files. If I could check and play in some means with low level driver first, I guess I could find if the problem is high level applications or low lever drivers. Seems that the drivers all there, but don't know if them are working or not.
ISTR that long ago there were CLI sound/CD players. I don't know if there are any left. I suggest a Google.
Thank you.
Kind Regards,
Jim
<snip sig stuff>
Stupid question, have you tested the speakers on another system, is the cable plugged into the correct socket on the back plane / sound card? John
-
Alex White -
hce -
John Bowden -
MHR -
William L. Maltby