Alex wrote: >> "[If] Advanced Linux Sound Architecture Driver Version >> [is not] 1.0.19, that's your [HDMI] problem", >> >> the above statement would be a little disingenuous: >> >> We all know that with the _latest_ kernel, 2.6.29.1, >> the /proc/asound/versionis 1.0.18a (i.e. not 1.0.19). >> >> In other words, any Intel guy still has this problem. On Mon, Apr 13, 2009 at 7:13 PM, Geoffrey Leach wrote: > Hmmmm .... I'm not sure what to make of this. Let me make my point > again. The latest alsa version is 1.0.19. The version numbering belongs > to the Alsa maintainers, not the kernel maintainers. That the kernel > maintainers chose to ship 1.0.18a is neither here nor there. I had HDMI > problems with 1.0.17 which were resolved with 1.0.19. Expecting to get > 18a with my next kernel, I checked the history on the driver and > discovered that significant changes to sndl _hda_intel took place > between 18a and 19. Hence my suggestion. Hi Jeoffrey, Regarding your comments: > The latest alsa version is 1.0.19. 120% True > The version numbering belongs to the Alsa maintainers, > not the kernel maintainers. 120% True > That the kernel maintainers chose to ship 1.0.18a > is neither here nor there. Here, there's seems to be a confusion all around, so I'll make an attempt to clear it up the best I can. ALSA Linux users fall into three categories (IMHO): 1. People who use a Distro and they take whatever ALSA and Kernel versions they get. I suspect Marco is in their number (although we'll probably never know what distro, kernel and alsa he has. However, that's immaterial to this classification.) 2. People who use whatever the kernel "maintainers" provide (and not the "original", latest ALSA distribution). I belong to this category, so what they choose to ship with their kernel (latest, 1.0.18a) _is_ very much "here and there" (so to speak), especially as you pointed out, and rumor on the web has confirmed recently, that here an Intel/HDMI guy doesn't stand a chance until 1.0.19. 3. People who combine the above two approaches - I believe you might be one of them. They take whatever kernel and alsa their "distro" provide and when things are unsatisfactory they upgrade ALSA on their own, the way you did by going to 1.0.19 in order to make your HDMI finally work. ---- Now, a few comments. A. Obviously, the "classification" above is not cast in stone nor necessarily complete or accurate. You and anybody else is warmly invited to flesh it out, modify, trash it, etc. I issued it mostly because I personally haven't seen any kind of meaningful words about ALSA versus Kernel, especially since ALSA was finally "absorbed" into the Kernel. Also, like with HDMI, I think people might find some of the clarifications helpful in avoiding unnecessary posts, questions and much grief. B. I'd very much like to move to the flexibility of the 3rd category. My machine has remained frozen at "genuine" ALSA 1.0.9a, whose libs, utilities, tools, I use together with the current kernel's ALSA drivers. I made an effort to install 1.0.16 at one point (i.e. to keep up) but I failed ignominiously for reasons too complicated to mention. I'm wondering though if I can install just the drivers package from the ALSA (1.0.19) original sources somehow and break this unhealthy dependency to what the kernel maintainers would trickle down. Have you actually done that (as per category 3 above)? Would "/proc/asound/version" show 1.0.18a or 1.0.19 in that case? Thanks, -- Alex ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
