On Thu, 8 Jun 2006, Gene Heskett wrote: > Bill Unruh wrote: >> On Thu, 8 Jun 2006, Gene Heskett wrote: >> >>> Lee Revell wrote: >>>> On Fri, 2006-06-09 at 11:36 +1000, Claude Yu wrote: >>>>> Someone pls reply to my request. >>>>> My system unable to load snd-riptide even I have downloaded and >>>>> installed alsa-driver-1.0.11rc5. >>>>> >>>>> >>>> >>>> Why -rc5? Why not just use ALSA 1.0.11? >>>> >>>> Also please don't post HTML to this list. >>>> >>>> Lee >>>> >>> An interesting observation Lee, considering that alsa is stuck at rc2 in >>> the fc5 repos. Can you comment on the delay? >> >> I think you would have to ask Fedora. It is probable that the distro uses >> rc2, and they do not update. They just fix bugs. >> > > And where obviously my opinion isn't worth a bucket of warm spit. But IMO, > when ALL major VoIP programs have trouble with full duplex, its a bug.
Or ALL major VoIP programmers are stuck in the past and have not bothered to learn alsa. That is not an unkown thing. > > But I'm told to take my problems to the alsa list when I ask on the fedora Of course. The problem is that the distros tend to be very old in their distro's support of alsa. When alsa was put into the kernel, the delay between alsa support and kernel support and then distro support increased. Ie, kernel 2.6.12, which is what Mandriva 2006 uses is way behind the current kernel 2.6.17, and its alsa is as well 1.0.9b. And distros do not keep up with the changes of alsa once they have released their distro. Unfortunately users keep buying the very latest soundcards. > list. The alsa list claims its the apps, but the alsa performance is so poor > that even the most recent VoIP release, twinkle, only 3 weeks old, is STILL > USING OSS BECAUSE APPARENTLY those who subscribe to oss, DO have working > systems. Does that not tell the alsa people anything? I think you are attributing to the app makers motives which may be inappropriate. The oss users may hae working systems because the apps people have never bothered to learn how to use alsa. > > Its a classic case of the he said/she said pissing match. Maybe TPTB ought > to have themselves a game of rock, paper, scissors, with the loser finally > admitting there is a problem? > > I'd build and install 1.0.11 from the tarballs, but after it took me a year > to get all the major bugs squished in FC2 by doing that, then I find that > while my home FC2 system works very well indeed, the whole world says its > hopelessly broken when I do ask about howto do something new on it. No idea what you mean with this paragraph. FC2 is old. It has a number of security problems. This does not mean that it does not work well for you or for what you do. However IF you want to do something new, then it may well not have the capability. > > You cannot, IMO, have your cake and eat it too. If a package manager is to > be used, and its dependency rules adhered to, then as far as I'm concerned, > those glaring problems found by the users of certain chipsets can damned well > be fixed by the packagers IF the code to do so exists in the upstream > tarballs. However, finding out this information seems to require the > employment of a good private detective agency or something equally > unappetizing. ???? No. What you ask is not possible, unless you want to volunteer your time to do so. As you discovered, installing alsa 1.0.11 caused trouble on FC2 on your system. It tookk you time to straighten them out. Now imagine a packager having to do that but for 10,000 different systems. > > Or maybe I'm just tired, its now about 60 days of trying to make both this > and NM work on a laptop I bought to get me away from the outrageous telephone > costs of trying to get a job done just because its located in the upper > peninsula of Michigan. What is NM? And "this" is what? > > FWIW, skype AND the network both work rather well when this box is booted to > XP, so it CAN BE DONE. Unforch, windows gives me a rash I haven't found a > skin cream to fix. Unfortunately people like the ones who work on skype spend all their time on the windows versions, to make sure they work. And the soundcard manufacturers spend all their time on Windows to make sure it works, and in fact actively put roadblocks in the way of the Linux developers to make sure their drivers do not work. _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
