On Mon, 5 Jun 2006, Stephen Mollett wrote: > On Monday 05 June 2006 15:42, Bill Unruh wrote: >>> Sounds like the snd-riptide.ko file isn't installed. Perhaps Mandrake >>> (Mandriva?) doesn't include this driver by default >> snd-riptide came into alsa with 1.0.10 I believe. Mandriva 2006 uses kernel >> 2.6.12 which uses alsa 1.0.9 > > Ah, that would explain it then. I'm intrigued, though (assuming that Claude > hadn't already tried installing alsa 1.0.11 manually), that the system > already knew that snd-riptide was the module to use, even though it didn't > yet exist :-) > > I would think that up-to-date Mandriva RPM packages would probably be > available by now, though.
No, Mandriva does not upgrade their packages except for security concerns. Thus they will stick with 2.6.12 and add security updates to it. Now I suppose they could also add alsa modules to the 1.0.9 in 2.6.12, but from what I can see they have not. Now they have the cooker (alpha) version of their next release 2007.0 and the kernel there could well have a later version of alsa. > >>> If you're going to install the drivers manually (it shouldn't really be >>> necessary if Mandrake have done their job properly), you'll need to get >> ??? Do you mean the kernel developers? Mandriva does not remove modules. > > I assumed that riptide would be an established module (given the vintage of > the hardware) rather than a new driver. What I was trying to say was that, if > the packages were built properly and whatever configurator program Mandriva > uses was fed the right data to enable it to choose an appropriate driver, it > should be unnecessary for the average user who just wants a working desktop > system to compile stuff from source just to get something as basic as sound > working. Well, riptide seems to be a very recent addition. Whether it is because the alsa people had trouble reverese engineering the driver, or noone had a copy I do not know. Unfortunately although sound may be basic, it is also highly highly idiosyncratic. Every sound card maker decides that they will impliment sound in a different manner. And change totally on each new card they release. And decide that everything is so proprietary they will not even tell you if the soundcard has a windows driver, never mind what is in that driver. Ie, sound is probably THE hardest thing to get working in Linux. > > I may not object to compiling my own software but I have seen countless > disgruntled users who have tried Linux after seeing me using it with apparent > ease then given up in disgust a few weeks (or even a few hours) later when > they can't get basic functionality to work properly or at all. They then pop > in a Windows CD and have a fully-working system in an hour or so. The worst Yell at the sound card manufacturers. Microsoft does not write the drivers, the manufacurers do. They do not even need to create drivers-- they can just release the specs. But the thought of doing that gets their knickers in a total twist. I asked Maudio whether a certain file on the windows system was the firmware for their (usb) sound card. They told me that was proprietary information. Damn it, it is something that you can figure out in 10 min, but it was proprietary. > of this is that they then spread the word to all their friends that Linux is > a waste of time for "normal" people - which doesn't exactly do the "cause" > much good. (It does, however, boost my reputation as some kind of IT > planet-brain... I'm not sure whether that's a good thing or not, given that > it raises expectations at "point of delivery".) > > I shall stop here before I go further off-topic. > > Regards, > Stephen > -- William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273 Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324 UBC, Vancouver,BC | Program in Cosmology | [EMAIL PROTECTED] Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/ _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
