Dazed_75 wrote:
> This is getting too frustrating since Fry's will let me return the
> machine. As I had already written the following and this is apparently
> a common problem I am submitting the email. I would still be interested
> in comments, but don't waste time on it as I am ready to give up.
OK, here I am looking at my settings.
> The information I found is at:
> http://www.gidnetwork.com/b-106.html
> http://www.alsa-project.org/ (just the home page for:)
>
> http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Intel&card=ICH+southbridge+HD-audio+and+modem.&chip=ICH6%2C+ICH6M%2C+ICH7%2C+ESB2&module=hda-intel
These look like good information. Did you already check on all the
settings they describe? I assume you did.
> Shortest form is that the articles say I should have a module called
> snd_seq_oss running and it appears do not but have a snd_seq_device
> [instead?]. As this is SUSE 10.1 it is also possible that they renamed
> it or incorporated the alsa stuff into their .._device version.
Neither of the pages you site above say anything about snd_seq_oss. Did
you forget a reference somewhere? I don't think it matters since I
don't have snd_seq_oss running either.
My direct comments follow my settings display...
> lapdog2:/home/larry/download # lspci | grep Audio
>
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
> Definition Audio Controller (rev 02)
# lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 02)
> lapdog2:/home/larry # modinfo soundcore
>
> filename:
> /lib/modules/2.6.16.21-0.25-smp/kernel/sound/soundcore.ko
> description: Core sound module
> author: Alan Cox
> license: GPL
> alias: char-major-14-*
> vermagic: 2.6.16.21-0.25-smp SMP 586 REGPARM gcc-4.1
> supported: yes
> depends:
> srcversion: DD426F1CCA2CC5F060F6F92
>
# modinfo soundcore
filename:
/lib/modules/2.6.16.21-0.21-default/kernel/sound/soundcore.ko
description: Core sound module
author: Alan Cox
license: GPL
alias: char-major-14-*
vermagic: 2.6.16.21-0.21-default 586 REGPARM gcc-4.1
supported: yes
depends:
srcversion: DD426F1CCA2CC5F060F6F92
> lapdog2:/home/larry/download # lsmod | grep snd
>
> snd_pcm_oss 47104 0
> snd_mixer_oss 20224 1 snd_pcm_oss
> snd_seq 53104 0
> snd_seq_device 11916 1 snd_seq
> snd_hda_intel 21652 2
> snd_hda_codec 139136 1 snd_hda_intel
> snd_pcm 86532 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
> snd_timer 25860 2 snd_seq,snd_pcm
> snd 56708 12
> snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
>
> soundcore 13024 1 snd
> snd_page_alloc 13576 2 snd_hda_intel,snd_pcm
# lsmod | grep snd
snd_rtctimer 3468 1
snd_seq_dummy 3588 0
snd_pcm_oss 42752 0
snd_mixer_oss 16256 1 snd_pcm_oss
snd_seq 46960 2 snd_seq_dummy
snd_seq_device 7948 2 snd_seq_dummy,snd_seq
snd_hda_intel 17044 1
snd_hda_codec 135296 1 snd_hda_intel
snd_pcm 79880 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer 20868 3 snd_rtctimer,snd_seq,snd_pcm
snd 50692 13
snd_rtctimer,snd_seq_dummy,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
soundcore 8672 1 snd
snd_page_alloc 9608 2 snd_hda_intel,snd_pcm
Comments:
1. Note the modinfo output shows that you are using an smp kernel while
I am not. Did you check your kernel configuration settings? That first
web pager reference states:
"Kernel 2.6.16 Note: Interestingly enough, the driver for the Intel HD
Audio in kernel 2.6.16 is broken. Everything appears to work fine, but
alas there is absolutely no sound no matter what you do. I was able to
get my sound card working by installing the latest ALSA driver, lib and
utility.
If you need to do this, you need to turn off ALSA support in the kernel.
You still need to enable sound support though:"
We are both running the 2.6.16 kernel but, since yours is smp maybe the
packager for your binary enabled the ALSA driver in the kernel, thus
breaking your sound as the quote above states.
2. The list of snd related drivers is a bit different but appears the
same for the drivers that I think "count" for this situation. Does
anything jump out at you or anyone else?
At the moment I think the kernel setting of the ALSA driver is the first
thing to check. I did not check the settings of my own kernel. I'll
have to do that as soon as I remember how to derive the settings out of
the kernel binary.
How do you want to proceed from here?
Alan
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)