1 |
On Sat, 2005-10-22 at 08:27 -0700, Mark Knecht wrote: |
2 |
> On 10/22/05, Michael Sullivan <michael@××××××××××××.com> wrote: |
3 |
> > On Sat, 2005-10-22 at 17:04 +0200, Holly Bostick wrote: |
4 |
> > > Michael Sullivan schreef: |
5 |
> > > > camille ~ # emerge -pv alsa-tools alsa-utils alsa-lib alsa-headers |
6 |
> > > > alsa-jack alsa-oss alsa-firmware |
7 |
> > > > |
8 |
> > > > These are the packages that I would merge, in order: |
9 |
> > > > |
10 |
> > > > Calculating dependencies ...done! [ebuild R ] |
11 |
> > > > media-sound/alsa-tools-1.0.9 +X 0 kB [ebuild R ] |
12 |
> > > > media-sound/alsa-utils-1.0.10_rc2 +nls 0 kB [ebuild R ] |
13 |
> > > > media-libs/alsa-lib-1.0.10_rc2 +doc +jack* 0 kB [ebuild R ] |
14 |
> > > > media-sound/alsa-headers-1.0.10_rc2 0 kB [ebuild R ] |
15 |
> > > > media-plugins/alsa-jack-1.0.10_rc1 0 kB [ebuild R ] |
16 |
> > > > media-libs/alsa-oss-1.0.10_rc2 0 kB [ebuild R ] |
17 |
> > > > media-sound/alsa-firmware-1.0.9 0 kB |
18 |
> > > |
19 |
> > > |
20 |
> > > |
21 |
> > > >From www.alsa-project.org: |
22 |
> > > |
23 |
> > > Latest Software Releases |
24 |
> > > Package |
25 |
> > > |
26 |
> > > * Driver |
27 |
> > > * Library |
28 |
> > > * Lib-plugins |
29 |
> > > * Utilities |
30 |
> > > * Tools |
31 |
> > > * Firmware |
32 |
> > > * OSS Compat. Library |
33 |
> > > |
34 |
> > > Stable release |
35 |
> > > |
36 |
> > > * 1.0.9b |
37 |
> > > * 1.0.9 |
38 |
> > > * 1.0.9 |
39 |
> > > * 1.0.9a |
40 |
> > > * 1.0.9 |
41 |
> > > * 1.0.9 |
42 |
> > > * 1.0.9 |
43 |
> > > |
44 |
> > > Development release |
45 |
> > > |
46 |
> > > * 1.0.10rc2 |
47 |
> > > * 1.0.10rc2 |
48 |
> > > * 1.0.10rc1 |
49 |
> > > * 1.0.10rc2 |
50 |
> > > * 1.0.10rc2 |
51 |
> > > * --- |
52 |
> > > * 1.0.10rc2 |
53 |
> > > |
54 |
> > > So there is an alsa-tools devel release higher than what you've got, as |
55 |
> > > well as a firmware devel-release. |
56 |
> > > |
57 |
> > > It's possible that part of the issue is the version mismatch you've got |
58 |
> > > happening (for example, the devel release of alsa-tools might well |
59 |
> > > understand how the hda-intel cards work, whereas 1.0.9 does not). |
60 |
> > > |
61 |
> > > I would consider copying the alsa-firmware and alsa-tools ebuilds to |
62 |
> > > your overlay, updating them to 1.0.10rc2, and seeing if they will then |
63 |
> > > upgrade, and if so, whether that helps. |
64 |
> > > |
65 |
> > > Just an idea. |
66 |
> > > |
67 |
> > > Holly |
68 |
> > |
69 |
> > Are there ebuilds for alsa-firmware-1.0.10-rc2 and |
70 |
> > alsa-tools-1.0.10.rc2??? I looked in portage (I sync every night at |
71 |
> > midnight) and I didn't see them... |
72 |
> |
73 |
> I believe that alsa-firmware is only supporting the HDSP devices |
74 |
> (Digiface and Multiface) that need to have firmware loaded into them |
75 |
> before they will operate. My HDSP 9652 doesn't need it since the |
76 |
> firmware is on the card. |
77 |
> |
78 |
> I find it doubtful that this will fix your problem, but it doesn't hurt to try. |
79 |
> |
80 |
> Did you do the aplay experiment? |
81 |
|
82 |
Yes. I sent the output in a previous post. I don't use aplay very |
83 |
often, but I believe that the output it gave was the output it's |
84 |
supposed to give on a working sound system, except that there was no |
85 |
sound coming out of the speakers. I checked and the speakers are turned |
86 |
on and plugged into the PC and I turned the volume all the way up before |
87 |
running aplay and still didn't hear the wav file. |
88 |
> |
89 |
> - Mark |
90 |
|
91 |
|
92 |
-- |
93 |
gentoo-user@g.o mailing list |