> Do you mean a problem with the missing LFE? The missing LFE sounds > like a different problem. AFAIK, the device itself _is_ set up > properly as expected. I mean the missing LFE. I can confirm the device otherwise works as adverticed. In fact I only (kind of) miss the LFE since I read in another post it should be there :-) > And, if it's about debugging, let's discuss on alsa-devel ML and drop > Cc from alsa-users. I've run the current alsa-info.sh as suggested by Tobis Davis (thanks for the pointer BTW) and had it upload the result automatically. > Why not patch the code :) That was my first idea :) When I boldly started looking at it I realized I'm in for a steep learning curve. Not that I won't walk that road, but it will take me some time... For a start I downloaded "Writing an alsa driver" and alsa-driver-api and will start reading it "real soon" (TM) > As a hint, if it's really a regression, try to revert to the version > it did work. Check /proc/asound/card0/codec#* file to see which > widget is changed by the LFE volume. That's the vital information. I don't know whether it actually is a regression or a not-yet-implemented feature. I do own my XPS M1710 since around March/April 2007 and I don't recall to have seen it. However sound worked right from the start and until recently I wasn't even aware there should be a LFE control. In fact the only "evidence" I have there should be one is already mentioned other post. That having said: The link http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh should probably go into ALSA-Configuration.txt I also suggest to add a troubleshooting section into the navigation block of the entry page of alsa wiki (or move the existing one there -- I have not been able to easily find an existing one though) which mentions this link as well as all other stuff that a user should be aware of when reporting a problem. If it isn't easy to provide concise troubleshooting instructions it would at least be helpful to give an overview where and how to find the relevant info in the wiki. After all the user having a problem often is just starting learning alsa. Best, Michael -- Vote against SPAM - see http://www.politik-digital.de/spam/ !tagline Michael Gerdau email: mgerdau@xxxxxxxxxx GPG-keys available on request or at public keyserver
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel