Hi Olivier, I prefer the other guy's answer "put it down to bad luck" [that you did not get answer so quickly].
On 3/11/13, Olivier Cailloux <olivier.caill...@gmail.com> wrote: > Le 10/03/2013 03:21, Zenaan Harkness a écrit : >>> My graphic card is connected through HDMI to my screen. I get no sound, > Yes indeed, my speakers are in my monitor, but I did not mention that > because I had absolutely no idea that it could possibly matter. Does it? There _were_ points of lack of clarity, which led to the possibility (not fact) that you had overlooked something really simple. I am not familiar with pci graphics cards, but I could imagine a separate connection for speakers and that you had tested your successful Ubuntu a long time ago. These things were not clear. Anyway, sorry I can't help so much on the technical side of this question. >> * I reader, cannot be sure if your problem is simply a sound problem, >> or a sound-through-hdmi problem. > I mentioned that sound through the other sound card works. I did not know hdmi is what is coming out of a sound card? :) Again, I am simply highlighting, because you asked re asking questions. So: there is sometimes assumption that when you make an ambiguous or unclear statement, you might be overlooking something simple. Or you might be emotional hot potato. Or ... >>> and no error messages: >> * Here, you do not say where you looked for error messages. Did you >> check syslog, did you check the docs for the sound player you are >> using to find out if it logs errors to some file somewhere? >> >> * You see, when you say "[I got] no error messages" it's still >> anybody's guess as how competant you are, or if you have truly made an >> effort yourself, or not. > Okay, I could have made it more explicit. I meant that when I try > "aplay" command line utility, it does not give an error message on the > line. I assume that it would say so (on sysout or syserr, thus visible > in the terminal) if it detected an error, as it seems to be designed for > testing, and since the troubleshooting guide does not mention to look > for anywhere else for error messages. But I may be wrong. Next is may be a search for kernel modules for hdmi sound? I don't know where to start next on this other than "man lsmod" and google. You could compare module list between the ubuntu and the debian installs. > I said the sound works on the same computer, with a different OS. It is > implicit that I do not change the cable configuration between two tests, > it seems to me. I thought it would be sufficient to exclude a hardware > problem such as an incorrect cable connection. >From your point of view ok. There are many people who have made simple errors. And, we don't know if you tested Ubuntu 2 years ago, or yesterday. So how can we know your "fair assumption"? Since you asked re how to ask ... >> You haven't said if you used a dual-boot or a live-cd of Ubuntu. > Does that matter? (It is a dual-boot in fact.) Probably would not matter if you had said "I tested Ubuntu 10.04 yesterday to make sure it is still working. It does with the following command: ... But there were various/"too many" assumptions that you were asking the reader of your question to make. This leads to assumptions in the readers mind which may be NOT in your favour.. This is my main point, regarding asking questions. > without these files. I checked for existence of any "*asound*" files in > my Ubuntu install: there is no. In debian, none either. So I thought > that’s not somewhere to search further. Good thought. Now we know you tested that. > The troubleshooting guide for alsa mentions that these files should not > be used in a working install (see Warning here: > http://alsa.opensrc.org/.asoundrc): "If your system won't work without > [these files], and you are running the most current version of ALSA, you > probably should file a bug report." Now I know that asoundrc should not be used on modern kernels. Perhaps you should file an alsa bug report? Just a thought :) Of course, if that quote had said "... you should probably contact the alsa-user mailing list" then I would have had the thought that doing so might be a good idea too :) >> * If you do not know what to look for, and are unwilling to google it, >> you could ask the question, eg "Can someone please advise which files >> I can compare, between the Ubuntu and Debian, so I can find out why my >> Debian sound does not work?" > Well, the Ubuntu install is much older than Debian, thus there is likely > many differences on the file level (the driver is older, alsa version is I agree. Also in light of above information (asoundrc is no longer expected to be used) - you have tought me something already. > Or course, if one place no upper bound on the time one is ready to Of course not assumed you will do :) > directions. It’s just that there’s a middle ground to be found... Definitely. This is why we are discussing how to ask good answer-friendly questions :) > However, the pathway you are talking about I do not see. My ubuntu > installation *is* working. I do not know how to remember what I did You could put this info in your alsa bug report, since bug report seems to be what the alsa devs want. >> * Again, you had it working on Ubuntu, so go and test this same >> command on your Ubuntu installation. Freedom does not mean free of >> effort. > I have, and it works. Once again here I thought I would skip this > information to reduce length of post and because it is not surprising If you did the test two years ago, you should do again now. You did not say you tested recently, that's all. Answer friendly questions :) 1) >>> When I play to the default card, I can see through pavucontrol that >>> pulse audio receives sound, but I can hear nothing. 2) >> * This sounds to me like you might have a pulseaudio configuration >> problem - 3) > As far as I understand, these tests I did with aplay do not go to > pulseaudio: only the first card (of the list given by aplay -L) sends > sound to pulseaudio, > the other cards I tried (with the aplay command) Again, there is lack of clarity, ambiguity, and/ or blunt contradiction, in your communication. Can you see it? Let me show: 1) you can see, but not hear, in PA 2) I suggest you check PA config 3) you say "these tests .. do not go to pulseaudio" And so now my head does backflips! 4) > should send sound directly to the card without going through pulseaudio. > I made these tests on purpose to bypass any possible pulseaudio related > problems. (Though I may be wrong again.) 4) does not fix up the problem of communication that you made. When you do test, you need to give result of test. Talk about what "should" happen separately. > To summarize, even though I do not agree with all your comments, it > definitely gives some ideas on how to improve my question. So thank you > for your answer once again. May be you can see some more answer-friendliness possibilities? :) > On the negative side, though, if I understand you well enough, you seem > to suggest I should start by working approximately at least three full > days non stop on that question (supplementary to the time I spent No. Not expected. But a bit more clarity or "due diligence" (time spent) in your asking your question, might assist to get better response (ie, any response :) Good luck with the sound problem, Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnstcd1fz3ntw_gwklf0676+w5w61uia_ogj2jqfonis...@mail.gmail.com
