Re: [gentoo-user] alsa problem
The problem is fixed now! I tried the alsa-driver-1.0.14_rc3, which is used by the Redflag os, and everything is fine, now. It's very weird. Just as what I mentioned above, the 1.0.14_rc3 version one is a unstable one. I have tried both version 1.0.14,the stable one that come out after 1.0.14_r3, and the 1.0.15_rc2 one, but both of them can't drive my sound card. But now, the 1.0.14_rc3 fixed it! It's a big surprise. 2007/10/14, Chuanwen Wu [EMAIL PROTECTED]: 2007/10/14, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Sun, 14 Oct 2007 15:25:12 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). Hm, I see. I think the different IRQs are not really worth mentioning, since they get automatically assigned. All that fooling around with different versions of ALSA didn't help much, so it boils down to - either it's a modified kernel what Redflag uses (I agree they use in-kernel ALSA), or - it's really an AMD64 vs. i386 matter. When I do #modprobe snd_hda_intel(or #alsaconf), I can see the message below appending to the ouput of dmesg: ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 PCI: Setting latency timer of device :00:1b.0 to 64 stac92xx_auto_fill_dac_nids: No available DAC for pin 0x0 I had a really deep look into /usr/src/linux/sound/pci/hda/patch_sigmatel.c, but nothing really rings a bell. I think this indicates the problem (since nothing will get routed correctly when it fails on the first pin, 0). But I don't think the problem is located in the function that prints this error. In any case, after printing that error, the initialization of the pin routing fails with an error. So it's definately a driver issue, not something about machine configuration. In any case, I think you should report to the alsa mailinglist. FWIW, I can't currently access www.alsa-project.org either. You can find the subscription interface here: https://lists.sourceforge.net/lists/listinfo/alsa-user I'm sorry that after all this there isn't really much success. One I am really appreciate for your patience and help. And I have learned some ways to detect and trace my os's status from you. could certainly do more debugging by comparing a 32bit vs a 64bit kernel with the exact same config otherwise. That might actually prove that there's something fishy. The 64bit os support is not very well at the moment. After I switch to 64bit os, I have found some applications and driver did not support 64bit os,like Eclipse. But thing will get better and better. -hwh -- [EMAIL PROTECTED] mailing list -- wcw -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Hi, On Mon, 15 Oct 2007 21:33:17 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: The problem is fixed now! I tried the alsa-driver-1.0.14_rc3, which is used by the Redflag os, and everything is fine, now. It's very weird. Just as what I mentioned above, the 1.0.14_rc3 version one is a unstable one. I have tried both version 1.0.14,the stable one that come out after 1.0.14_r3, and the 1.0.15_rc2 one, but both of them can't drive my sound card. But now, the 1.0.14_rc3 fixed it! It's a big surprise. I'm very happy to hear that. And I don't have a good explanation, either. Some regression must have crept into newer versions -- or some kind of sanity check that now triggers for newer versions. In any case: Good to hear it's working! (and of course, you were very welcome, thanks for the thanks!) -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/13, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Sat, 13 Oct 2007 22:23:35 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). I think it would at least be interesting what /proc/asound/version is like on the redflag distro. Also it would be interesting if they use in-kernel ALSA or separate drivers and if the latter is the case, then they might provide source packages -- which potentially include patches that add support for your device. Let 's have a look at the Redflag's alsa information:(all the operations I did below were in the Redflag OS) # cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfe9fc000 irq 20 ***in gentoo it is irq 21 here. ** # cat /proc/asound/devices 0: [ 0] : control 1:: sequencer 16: [ 0- 0]: digital audio playback 17: [ 0- 1]: digital audio playback 24: [ 0- 0]: digital audio capture 33:: timer # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.14rc3. Compiled on Jul 25 2007 for kernel 2.6.22.1-9 (SMP). I notice that the alsa version is 1.0.14rc3 which is the unstable one before 1.0.14. But I tried 1.0.14rc3, and the result is as similar as when I use in-kernel alsa driver. # grep SND /boot/config-2.6.22.1-9 CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_RTCTIMER=m CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y CONFIG_SND_DYNAMIC_MINORS=y # CONFIG_SND_SUPPORT_OLD_API is not set CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_OPL4_LIB=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DUMMY=m CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m CONFIG_SND_MTS64=m # CONFIG_SND_SERIAL_U16550 is not set CONFIG_SND_MPU401=m CONFIG_SND_PORTMAN2X4=m CONFIG_SND_CS4231_LIB=m CONFIG_SND_ADLIB=m # CONFIG_SND_AD1816A is not set # CONFIG_SND_AD1848 is not set # CONFIG_SND_ALS100 is not set # CONFIG_SND_AZT2320 is not set # CONFIG_SND_CMI8330 is not set # CONFIG_SND_CS4231 is not set # CONFIG_SND_CS4232 is not set CONFIG_SND_CS4236=m # CONFIG_SND_DT019X is not set # CONFIG_SND_ES968 is not set # CONFIG_SND_ES1688 is not set CONFIG_SND_ES18XX=m # CONFIG_SND_GUSCLASSIC is not set # CONFIG_SND_GUSEXTREME is not set # CONFIG_SND_GUSMAX is not set # CONFIG_SND_INTERWAVE is not set # CONFIG_SND_INTERWAVE_STB is not set CONFIG_SND_OPL3SA2=m # CONFIG_SND_OPTI92X_AD1848 is not set # CONFIG_SND_OPTI92X_CS4231 is not set # CONFIG_SND_OPTI93X is not set CONFIG_SND_MIRO=m # CONFIG_SND_SB8 is not set CONFIG_SND_SB16=m CONFIG_SND_SBAWE=m # CONFIG_SND_SB16_CSP is not set # CONFIG_SND_SGALAXY is not set # CONFIG_SND_SSCAPE is not set # CONFIG_SND_WAVEFRONT is not set CONFIG_SND_AD1889=m CONFIG_SND_ALS300=m CONFIG_SND_ALS4000=m CONFIG_SND_ALI5451=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m CONFIG_SND_AZT3328=m CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_CS4281=m CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y CONFIG_SND_CS5535AUDIO=m CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m CONFIG_SND_ES1938=m CONFIG_SND_ES1968=m CONFIG_SND_FM801=m CONFIG_SND_FM801_TEA575X_BOOL=y CONFIG_SND_FM801_TEA575X=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_KORG1212_FIRMWARE_IN_KERNEL=y CONFIG_SND_MAESTRO3=m CONFIG_SND_MAESTRO3_FIRMWARE_IN_KERNEL=y CONFIG_SND_MIXART=m CONFIG_SND_NM256=m CONFIG_SND_PCXHR=m CONFIG_SND_RIPTIDE=m CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m CONFIG_SND_SONICVIBES=m CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VX222=m CONFIG_SND_YMFPCI=m CONFIG_SND_YMFPCI_FIRMWARE_IN_KERNEL=y CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_USB_AUDIO=m
Re: [gentoo-user] alsa problem
Hi, On Sun, 14 Oct 2007 15:25:12 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). Hm, I see. I think the different IRQs are not really worth mentioning, since they get automatically assigned. All that fooling around with different versions of ALSA didn't help much, so it boils down to - either it's a modified kernel what Redflag uses (I agree they use in-kernel ALSA), or - it's really an AMD64 vs. i386 matter. When I do #modprobe snd_hda_intel(or #alsaconf), I can see the message below appending to the ouput of dmesg: ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 PCI: Setting latency timer of device :00:1b.0 to 64 stac92xx_auto_fill_dac_nids: No available DAC for pin 0x0 I had a really deep look into /usr/src/linux/sound/pci/hda/patch_sigmatel.c, but nothing really rings a bell. I think this indicates the problem (since nothing will get routed correctly when it fails on the first pin, 0). But I don't think the problem is located in the function that prints this error. In any case, after printing that error, the initialization of the pin routing fails with an error. So it's definately a driver issue, not something about machine configuration. In any case, I think you should report to the alsa mailinglist. FWIW, I can't currently access www.alsa-project.org either. You can find the subscription interface here: https://lists.sourceforge.net/lists/listinfo/alsa-user I'm sorry that after all this there isn't really much success. One could certainly do more debugging by comparing a 32bit vs a 64bit kernel with the exact same config otherwise. That might actually prove that there's something fishy. -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/14, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Sun, 14 Oct 2007 15:25:12 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). Hm, I see. I think the different IRQs are not really worth mentioning, since they get automatically assigned. All that fooling around with different versions of ALSA didn't help much, so it boils down to - either it's a modified kernel what Redflag uses (I agree they use in-kernel ALSA), or - it's really an AMD64 vs. i386 matter. When I do #modprobe snd_hda_intel(or #alsaconf), I can see the message below appending to the ouput of dmesg: ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 PCI: Setting latency timer of device :00:1b.0 to 64 stac92xx_auto_fill_dac_nids: No available DAC for pin 0x0 I had a really deep look into /usr/src/linux/sound/pci/hda/patch_sigmatel.c, but nothing really rings a bell. I think this indicates the problem (since nothing will get routed correctly when it fails on the first pin, 0). But I don't think the problem is located in the function that prints this error. In any case, after printing that error, the initialization of the pin routing fails with an error. So it's definately a driver issue, not something about machine configuration. In any case, I think you should report to the alsa mailinglist. FWIW, I can't currently access www.alsa-project.org either. You can find the subscription interface here: https://lists.sourceforge.net/lists/listinfo/alsa-user I'm sorry that after all this there isn't really much success. One I am really appreciate for your patience and help. And I have learned some ways to detect and trace my os's status from you. could certainly do more debugging by comparing a 32bit vs a 64bit kernel with the exact same config otherwise. That might actually prove that there's something fishy. The 64bit os support is not very well at the moment. After I switch to 64bit os, I have found some applications and driver did not support 64bit os,like Eclipse. But thing will get better and better. -hwh -- [EMAIL PROTECTED] mailing list -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Hi, On Fri, 12 Oct 2007 22:59:28 -0400 Walter Dnes [EMAIL PROTECTED] wrote: After this sequence, my ALSA sound finally started working again. I don't know what happened. A wild guess is that make was trying to be efficient and kept some code from a previous version, that doesn't work with the current version. Pretty unlikely, make doesn't do these things. I'm more thinking of stale modules lingerin' around, but we will never know. In this thread's case, however, I had the impression that sound on this machine never worked at all? -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Thank you for your help!
2007/10/12, Hans-Werner Hilse [EMAIL PROTECTED]:
Hi,
On Fri, 12 Oct 2007 09:50:16 +0800
Chuanwen Wu [EMAIL PROTECTED] wrote:
No, /dev/dsp is OSS stuff. Aplay shouldn't use that. But it makes me
wonder whether snd_pcm_oss is loaded?
Yes,have loaded it:
$ lsmod | grep snd_pcm_oss
snd_pcm_oss39648 0
snd_mixer_oss 14912 1 snd_pcm_oss
snd_pcm73800 2 snd_pcm_oss,snd_hda_intel
snd50216 6
snd_seq,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
Odd. /dev/dsp should be present under these circumstances. But the
other things below explain that:
I am sure I have re-run alsaconf and both the /etc/asound.state and
/var/lib/alsa/asound.state 's content are:
# cat /var/lib/alsa/asound.state
state.Intel {
control {
}
}
Hm, so it seems there were problems with the mixer at that stage, too.
That file should contain settings for the various controls.
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfe9fc000 irq 21
So the kernel is interfacing it correctly, but only in parts:
$ cat /proc/asound/devices
0: [ 0] : control
1:: sequencer
33:: timer
Here is the output of strace aplay and I hope it dose not bother you
and I also attach it as a annex.
[...]
open(/dev/snd/pcmC0D0p, O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
The playback and capture devices are completely missing, and udev
therefore didn't create /dev/snd/pcmC0D0p (PCM, card 0, device 0,
playback channel). The only explanation I can suggest is
broken/incomplete kernel/alsa-drivers support for your device. Does the
machine have BIOS settings for sound? What about the audio related
kernel log output?
Yes,both my Windows XP and another linux os Redflag have sound. Is
there anyway that I can use the Redflag's modules to driver my
gentoo?
Where can I get the audio related kernel log output?
In any case, you should probably use the separate alsa-driver from
portage, preferably the newest (unstable in portage) version. There
were many changes (some of them adding support for more devices for the
hda driver) that are not yet in the kernel ALSA tree.
I have tried the version (~)1.0.15_rc2,which I heard from someone in
some webpages that it could drive my hda sound card,but it still can't
in my machine.
And the one of version , I think I can never emerge it:
Emerging (1 of 2) media-sound/alsa-headers- to /
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ...[ ok ]
* checking miscfile checksums ;-) ... [ ok ]
Unpacking source...
* hg clone http://hg.alsa-project.org/alsa-kernel ...
real URL is http://hg.alsa-project.org/alsa-kernel/
requesting all changes
adding changesets
The network is so slow and this status has already keep couples of hours.
-hwh
--
[EMAIL PROTECTED] mailing list
--
wcw
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/13, Walter Dnes [EMAIL PROTECTED]: I ran into a similar problem after an update. audacious and mpg123 which use ALSA, died; Realplayer and mpg321 get by with the OSS api on ALSA. revdep-rebuild didn't find anything wrong. I tried various things without success. What finally worked was the following... 1) rebuild the kernel with sound support but no ALSA support at all 2) reboot 3) add the appropriate ALSA_CARDS line to /etc/make.conf, in your case ALSA_CARDS=hda-intel 4) emerge alsa-driver (and it probably still won't work) 5) emerge -C alsa-driver 6) rebuild the kernel with sound support and ALSA support 7) reboot 8) run alsaconf After this sequence, my ALSA sound finally started working again. I don't know what happened. A wild guess is that make was trying to be efficient and kept some code from a previous version, that doesn't work with the current version. It had to be totally removed in order to get make to build the new version of the code. I admit that your situation is very weird. But I still don't think that the old version will affect the new one. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 Q. Mr. Ghandi, what do you think of Microsoft security? A. I think it would be a good idea. -- [EMAIL PROTECTED] mailing list -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/13, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Fri, 12 Oct 2007 22:59:28 -0400 Walter Dnes [EMAIL PROTECTED] wrote: After this sequence, my ALSA sound finally started working again. I don't know what happened. A wild guess is that make was trying to be efficient and kept some code from a previous version, that doesn't work with the current version. Pretty unlikely, make doesn't do these things. I'm more thinking of stale modules lingerin' around, but we will never know. In this thread's case, however, I had the impression that sound on this machine never worked at all? It's my new Dell1400 laptop. Sound never works on the Gentoo OS but just as I mention in the above post, it works in Windows and another distribution Redflag. -hwh -- [EMAIL PROTECTED] mailing list -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Hi, On Sat, 13 Oct 2007 22:23:35 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. I think it would at least be interesting what /proc/asound/version is like on the redflag distro. Also it would be interesting if they use in-kernel ALSA or separate drivers and if the latter is the case, then they might provide source packages -- which potentially include patches that add support for your device. Before trying all that: Did you had a look at the kernel log (use dmesg)? Were there errors or warnings around the lines that were printed when the ALSA driver was loaded? When you emerge alsa-drivers, also make sure that there are no stale in-kernel modules in /lib/modules/$(uname -r)/kernel/sound/*. You can delete them manually, just run depmod -ae afterwards. Where can I get the audio related kernel log output? look at the output of dmesg (e.g. piping it to less: dmesg|less). However, for me (different card and all works well), there is zero output. You might change that by enabling ALSA debug output in kernel configuration, though... But I'm not sure whether that's worth it. In any case, you should probably use the separate alsa-driver from portage, preferably the newest (unstable in portage) version. There were many changes (some of them adding support for more devices for the hda driver) that are not yet in the kernel ALSA tree. I have tried the version (~)1.0.15_rc2,which I heard from someone in some webpages that it could drive my hda sound card,but it still can't in my machine. The newer ALSA versions are at least supposed to handle the hda better w/ regard to supported hardware configurations. Doing a little recherche for the little I know about your laptop, I came across this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg20707.html which seems to indicate similar problems which were partly solved by a newer version of alsa-driver. When experimenting with out-of-kernel drivers, always keep an eye on potential conflicts in /lib/modules/$(uname -r), and compare /proc/asound/version against what you think it should be. The thread also indicates that problems with HDA based audio is not a seldom thing to see. You can download newer versions of alsa-driver from their homepage and experiment with it in /usr/local/src. Currently they offer -1.0.15rc3, you might want to try it, it lists changes w/ regard to the hda driver. http://www.alsa-project.org/ And the one of version , I think I can never emerge it: Emerging (1 of 2) media-sound/alsa-headers- to / * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ...[ ok ] * checking miscfile checksums ;-) ... [ ok ] Unpacking source... * hg clone http://hg.alsa-project.org/alsa-kernel ... real URL is http://hg.alsa-project.org/alsa-kernel/ requesting all changes adding changesets The network is so slow and this status has already keep couples of hours. Yes, that's the culprit with distributed versioning systems. You have to download the full change history. I've not used mercurial recently, so I don't have a suggestion how to only download HEAD or something like that, if that's possible at all. I think at the moment there is no point in using a current Mercurial checkout. From what I see on http://hg-mirror.alsa-project.org/alsa-driver/ the last changes after 1.0.15rc3 don't matter in your case, so start trying that (as said, you can download it from their homepage). -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Hi,
On Fri, 12 Oct 2007 09:50:16 +0800
Chuanwen Wu [EMAIL PROTECTED] wrote:
No, /dev/dsp is OSS stuff. Aplay shouldn't use that. But it makes me
wonder whether snd_pcm_oss is loaded?
Yes,have loaded it:
$ lsmod | grep snd_pcm_oss
snd_pcm_oss39648 0
snd_mixer_oss 14912 1 snd_pcm_oss
snd_pcm73800 2 snd_pcm_oss,snd_hda_intel
snd50216 6
snd_seq,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
Odd. /dev/dsp should be present under these circumstances. But the
other things below explain that:
I am sure I have re-run alsaconf and both the /etc/asound.state and
/var/lib/alsa/asound.state 's content are:
# cat /var/lib/alsa/asound.state
state.Intel {
control {
}
}
Hm, so it seems there were problems with the mixer at that stage, too.
That file should contain settings for the various controls.
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfe9fc000 irq 21
So the kernel is interfacing it correctly, but only in parts:
$ cat /proc/asound/devices
0: [ 0] : control
1:: sequencer
33:: timer
Here is the output of strace aplay and I hope it dose not bother you
and I also attach it as a annex.
[...]
open(/dev/snd/pcmC0D0p, O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
The playback and capture devices are completely missing, and udev
therefore didn't create /dev/snd/pcmC0D0p (PCM, card 0, device 0,
playback channel). The only explanation I can suggest is
broken/incomplete kernel/alsa-drivers support for your device. Does the
machine have BIOS settings for sound? What about the audio related
kernel log output?
In any case, you should probably use the separate alsa-driver from
portage, preferably the newest (unstable in portage) version. There
were many changes (some of them adding support for more devices for the
hda driver) that are not yet in the kernel ALSA tree.
-hwh
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
I ran into a similar problem after an update. audacious and mpg123 which use ALSA, died; Realplayer and mpg321 get by with the OSS api on ALSA. revdep-rebuild didn't find anything wrong. I tried various things without success. What finally worked was the following... 1) rebuild the kernel with sound support but no ALSA support at all 2) reboot 3) add the appropriate ALSA_CARDS line to /etc/make.conf, in your case ALSA_CARDS=hda-intel 4) emerge alsa-driver (and it probably still won't work) 5) emerge -C alsa-driver 6) rebuild the kernel with sound support and ALSA support 7) reboot 8) run alsaconf After this sequence, my ALSA sound finally started working again. I don't know what happened. A wild guess is that make was trying to be efficient and kept some code from a previous version, that doesn't work with the current version. It had to be totally removed in order to get make to build the new version of the code. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 Q. Mr. Ghandi, what do you think of Microsoft security? A. I think it would be a good idea. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/11, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Wed, 10 Oct 2007 11:04:11 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: I just setup a gentoo in my dell1400 laptop,and until now,the sound problem is not solved yet. Here is the problem: $ aplay 01.mp3 ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave aplay: main:545: audio open error: No such file or directory This indicates that the dmix module (NOT kernel, but alsa-lib!) might be missing. I ran into some similar problems, I think they modified the way alsa-lib is configured and made it more fine-grained. Missing an ALSA_PCM_PLUGINS setting in my /etc/make.conf, I had no plugins at all. So I suggest to check your /etc/make.conf, and if not present and you want minimum hassle, append that line to /etc/make.conf: ---snip ALSA_PCM_PLUGINS=adpcm alaw copy dshare dsnoop extplug file hooks ladspa lfloat linear meter mulaw multi null rate route share shm ---snip (works for me) then re-emerge alsa-lib. Thanks for your tips! I have tried, but the result is all the same. Here is my ALSA_PCM_PLUGINS: (I have also tried your choose too) ALSA_PCM_PLUGINS=adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol Here is my in-kernel alsa options: M Advanced Linux Sound Architecture │ │ │ │ M Sequencer support │ │ │ │ Sequencer dummy client │ │ │ │ M OSS Mixer API │ │ │ │ M OSS PCM (digital audio) API │ │ │ │ [*] OSS PCM (digital audio) API - Include plugin system │ │ │ │ [ ] OSS Sequencer API │ │ │ │ M RTC Timer support │ │ │ │ [*] Use RTC as default sequencer timer │ │ │ │ [ ] Dynamic device file minor numbers │ │ │ │ [*] Support old ALSA API │ │ │ │ [*] Verbose procfs contents Here is my /etc/modules.d/alsa: $ cat /etc/modules.d/alsa alias char-major-116 snd alias char-major-14 soundcore alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss option snd cards_limit=1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss # Set this to the correct number of cards. # --- BEGIN: Generated by ALSACONF, do not edit. --- # --- ALSACONF version 1.0.14 --- alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel # --- END: Generated by ALSACONF, do not edit. --- I can't find the /dev/dsp : # ls /dev/dsp ls: cannot access /dev/dsp: No such file or directory My os is a 64bit gentoo, so may it be the problem? And here is my hardware: [...] looks OK. -hwh -- [EMAIL PROTECTED] mailing list -- wcw
Re: [gentoo-user] alsa problem
Hi, On Thu, 11 Oct 2007 23:53:42 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: I can't find the /dev/dsp : # ls /dev/dsp ls: cannot access /dev/dsp: No such file or directory My os is a 64bit gentoo, so may it be the problem? No, /dev/dsp is OSS stuff. Aplay shouldn't use that. But it makes me wonder whether snd_pcm_oss is loaded? Anyway, that shouldn't bother us here, that's not used by aplay. (BTW: For me, aplay will play noise when trying to play an MP3, but at least it *does* play something) Do you by chance have some older /etc/asound.* files around? Did you try re-running alsaconf? If all this doesn't work, try running strace on the aplay process (call strace aplay) and post back some output. Also, the contents of /proc/asound/cards and /proc/asound/devices might be interesting. -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/10, Randy Barlow [EMAIL PROTECTED]: Chuanwen Wu wrote: I also tried to emerge alsa-driver and didn't use the driver in the kernel,but the result was all the same. I don't know the module name for the HD, but did you add it to /etc/modules.autoload.d/kernel-2.6 and/or modprobe it first? $ lsmod Module Size Used by snd_seq48224 0 snd_hda_intel 302688 0 snd_pcm73288 1 snd_hda_intel snd_timer 19592 2 snd_seq,snd_pcm snd44208 4 snd_seq,snd_hda_intel,snd_pcm,snd_timer snd_page_alloc 8080 2 snd_hda_intel,snd_pcm The one snd_hda_intel is the driver for HD. I just can't see the problem except that the driver can't drive my audio card. Is there any ways to solve this problme? -- Randy Barlow http://electronsweatshop.com -- [EMAIL PROTECTED] mailing list -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Hi, On Wed, 10 Oct 2007 11:04:11 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: I just setup a gentoo in my dell1400 laptop,and until now,the sound problem is not solved yet. Here is the problem: $ aplay 01.mp3 ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave aplay: main:545: audio open error: No such file or directory This indicates that the dmix module (NOT kernel, but alsa-lib!) might be missing. I ran into some similar problems, I think they modified the way alsa-lib is configured and made it more fine-grained. Missing an ALSA_PCM_PLUGINS setting in my /etc/make.conf, I had no plugins at all. So I suggest to check your /etc/make.conf, and if not present and you want minimum hassle, append that line to /etc/make.conf: ---snip ALSA_PCM_PLUGINS=adpcm alaw copy dshare dsnoop extplug file hooks ladspa lfloat linear meter mulaw multi null rate route share shm ---snip (works for me) then re-emerge alsa-lib. And here is my hardware: [...] looks OK. -hwh -- [EMAIL PROTECTED] mailing list
[gentoo-user] alsa problem
I just setup a gentoo in my dell1400 laptop,and until now,the sound problem is not solved yet. Here is the problem: $ aplay 01.mp3 ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave aplay: main:545: audio open error: No such file or directory And here is my hardware: # lspci | grep Audio 00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 02) I compiled the alsa driver as the modules: M Intel HD Audio And I can start my alsasound: # /etc/init.d/alsasound start * Loading ALSA modules ... * Loading: snd-card-0 ... [ ok ] * Loading: snd-seq ... [ ok ] * Restoring Mixer Levels ... [ ok ] I can alsaconf,but not alsamixer: $ alsamixer No mixer elems found I also tried to emerge alsa-driver and didn't use the driver in the kernel,but the result was all the same. Any advice? Thanks in advanced! -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
Chuanwen Wu wrote: I also tried to emerge alsa-driver and didn't use the driver in the kernel,but the result was all the same. I don't know the module name for the HD, but did you add it to /etc/modules.autoload.d/kernel-2.6 and/or modprobe it first? -- Randy Barlow http://electronsweatshop.com -- [EMAIL PROTECTED] mailing list
