| 1 |
Thank you for your help! |
| 2 |
2007/10/12, Hans-Werner Hilse <hilse@×××.de>: |
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> On Fri, 12 Oct 2007 09:50:16 +0800 |
| 6 |
> "Chuanwen Wu" <wcw8410@×××××.com> wrote: |
| 7 |
> |
| 8 |
> > > No, /dev/dsp is OSS stuff. Aplay shouldn't use that. But it makes me |
| 9 |
> > > wonder whether snd_pcm_oss is loaded? |
| 10 |
> > Yes,have loaded it: |
| 11 |
> > $ lsmod | grep snd_pcm_oss |
| 12 |
> > snd_pcm_oss 39648 0 |
| 13 |
> > snd_mixer_oss 14912 1 snd_pcm_oss |
| 14 |
> > snd_pcm 73800 2 snd_pcm_oss,snd_hda_intel |
| 15 |
> > snd 50216 6 |
| 16 |
> > snd_seq,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer |
| 17 |
> |
| 18 |
> Odd. /dev/dsp should be present under these circumstances. But the |
| 19 |
> other things below explain that: |
| 20 |
> |
| 21 |
> > I am sure I have re-run alsaconf and both the /etc/asound.state and |
| 22 |
> > /var/lib/alsa/asound.state 's content are: |
| 23 |
> > # cat /var/lib/alsa/asound.state |
| 24 |
> > state.Intel { |
| 25 |
> > control { |
| 26 |
> > } |
| 27 |
> > } |
| 28 |
> |
| 29 |
> Hm, so it seems there were problems with the mixer at that stage, too. |
| 30 |
> That file should contain settings for the various controls. |
| 31 |
> |
| 32 |
> > $ cat /proc/asound/cards |
| 33 |
> > 0 [Intel ]: HDA-Intel - HDA Intel |
| 34 |
> > HDA Intel at 0xfe9fc000 irq 21 |
| 35 |
> |
| 36 |
> So the kernel is interfacing it correctly, but only in parts: |
| 37 |
> |
| 38 |
> > $ cat /proc/asound/devices |
| 39 |
> > 0: [ 0] : control |
| 40 |
> > 1: : sequencer |
| 41 |
> > 33: : timer |
| 42 |
> > |
| 43 |
> > Here is the output of strace aplay and I hope it dose not bother you |
| 44 |
> > and I also attach it as a annex. |
| 45 |
> > [...] |
| 46 |
> > open("/dev/snd/pcmC0D0p", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file |
| 47 |
> > or directory) |
| 48 |
> |
| 49 |
> The playback and capture devices are completely missing, and udev |
| 50 |
> therefore didn't create /dev/snd/pcmC0D0p (PCM, card 0, device 0, |
| 51 |
> playback channel). The only explanation I can suggest is |
| 52 |
> broken/incomplete kernel/alsa-drivers support for your device. Does the |
| 53 |
> machine have BIOS settings for sound? What about the audio related |
| 54 |
> kernel log output? |
| 55 |
> |
| 56 |
Yes,both my Windows XP and another linux os Redflag have sound. Is |
| 57 |
there anyway that I can use the Redflag's modules to driver my |
| 58 |
gentoo? |
| 59 |
|
| 60 |
Where can I get the audio related kernel log output? |
| 61 |
|
| 62 |
> In any case, you should probably use the separate alsa-driver from |
| 63 |
> portage, preferably the newest (unstable in portage) version. There |
| 64 |
> were many changes (some of them adding support for more devices for the |
| 65 |
> hda driver) that are not yet in the kernel ALSA tree. |
| 66 |
> |
| 67 |
I have tried the version (~)1.0.15_rc2,which I heard from someone in |
| 68 |
some webpages that it could drive my hda sound card,but it still can't |
| 69 |
in my machine. |
| 70 |
|
| 71 |
And the one of version 9999, I think I can never emerge it: |
| 72 |
>>> Emerging (1 of 2) media-sound/alsa-headers-9999 to / |
| 73 |
* checking ebuild checksums ;-) ... [ ok ] |
| 74 |
* checking auxfile checksums ;-) ... [ ok ] |
| 75 |
* checking miscfile checksums ;-) ... [ ok ] |
| 76 |
>>> Unpacking source... |
| 77 |
* hg clone http://hg.alsa-project.org/alsa-kernel ... |
| 78 |
real URL is http://hg.alsa-project.org/alsa-kernel/ |
| 79 |
requesting all changes |
| 80 |
adding changesets |
| 81 |
|
| 82 |
The network is so slow and this status has already keep couples of hours. |
| 83 |
|
| 84 |
|
| 85 |
> -hwh |
| 86 |
> -- |
| 87 |
> gentoo-user@g.o mailing list |
| 88 |
> |
| 89 |
> |
| 90 |
|
| 91 |
|
| 92 |
-- |
| 93 |
wcw |
| 94 |
-- |
| 95 |
gentoo-user@g.o mailing list |
Archives