Re: No sound-inputs but sound recording FMIT
On Saturday 04 March 2017 13:32:28 rhkra...@gmail.com wrote: > On Friday, March 03, 2017 02:53:26 PM The Wanderer wrote: > > Because hitting New means you have to put in the To address, but hitting > > Reply means the address is already there and you can just start typing > > your message (and possibly delete the quoted text, change the Subject > > line, et cetera). > > > > Yes, this apparently is enough of a convenience factor to affect > > people's behavior. > > Just to add $0.02 (I don't know who it belongs to, so didn't call it "my > $0.02")--in kmail, just right click on the address to which you want to > send the new email, and choose "New Message to" from the context menu... Or, in KMail-Trinity, left click on the address, et voilà! A _new_, correctly addressed message with a pristine subject line. Lisi
Re: No sound-inputs but sound recording FMIT
cbannis...@slingshot.co.nz: > On Sun, Mar 05, 2017 at 07:13:22PM -0500, Gene Heskett wrote: > > In other words Back EMF? > > I know a chap who found about that the hard way when he tried to get > something from nothing by charging a battery from a generator which he > turned by having a fan connected to it. :) What do you mean? A generator or an alternator? Given enough power from mechanical source (wind) to overpower the resistance of the generator it would produce current. Most of them, except for brush dynamos, will produce AC which needs to be rectified back to DC and regulated at a current a little above that of the battery. Whether it is a bicycle or wind generator or your auto/moto charging circuit, isn't it how it all works? Now if you put a 3' fan in a truck alternator and a 100Amph battery I suspect it would take a hurricane to get it moving. > He didn't get electrocuted or anything, the fan abruptly stops turning. This all started from the OP stating that FMIT (on all debian main rep's) records sound without any audio inputs in the system. Thread cannibals! ;)
Re: No sound-inputs but sound recording FMIT
On Sun, Mar 05, 2017 at 07:13:22PM -0500, Gene Heskett wrote: > On Sunday 05 March 2017 17:16:36 John Hasler wrote: > > > Gene Heskett writes: > > > Very simple. With the glaring exception of the modern AC induction > > > motor that in 99% of the stuff we buy, ANY other generator can also > > > be used as a motor... > > > > Induction motors can function as generators. You just need to connect > > them to an appropriate AC source and drive them above synchronous > > speed. > > > Yes, there is that exception, they need an excitation current, true, but > in that case they make excellent brakes as they don't like spinning > above synchronous any better than they like running below it. And with > enough dc current you can come pretty close to stopping them dead in > their tracks. Certainly within one revolution. But the armature is > soft, and its not possible to maintain the magnetic field from its > shorted turns armature long enough to extract any output power from it > for more than a few milliseconds. In other words Back EMF? I know a chap who found about that the hard way when he tried to get something from nothing by charging a battery from a generator which he turned by having a fan connected to it. :) He didn't get electrocuted or anything, the fan abruptly stops turning. -- The media's the most powerful entity on earth. They have the power to make the innocent guilty and to make the guilty innocent, and that's power. -- Malcolm X
Re: No sound-inputs but sound recording FMIT
I wrote: > Induction motors can function as generators. You just need to connect > them to an appropriate AC source and drive them above synchronous > speed. Gene writes: > Yes, there is that exception, they need an excitation current, true, > but in that case they make excellent brakes as they don't like > spinning above synchronous any better than they like running below it. > And with enough dc current you can come pretty close to stopping them > dead in their tracks. Certainly within one revolution. But the > armature is soft, and its not possible to maintain the magnetic field > from its shorted turns armature long enough to extract any output > power from it for more than a few milliseconds. That's not what I mean. Hook an induction motor to utility power and drive it above synchonous speed. It will power *to* the network. When you put DC current through the field of an induction motor to brake it you are also using it as a generator. It's just that all the power gets dissipated in the armature. -- John Hasler jhas...@newsguy.com Elmwood, WI USA
Re: No sound-inputs but sound recording FMIT
On Sunday 05 March 2017 17:16:36 John Hasler wrote: > Gene Heskett writes: > > Very simple. With the glaring exception of the modern AC induction > > motor that in 99% of the stuff we buy, ANY other generator can also > > be used as a motor... > > Induction motors can function as generators. You just need to connect > them to an appropriate AC source and drive them above synchronous > speed. > Yes, there is that exception, they need an excitation current, true, but in that case they make excellent brakes as they don't like spinning above synchronous any better than they like running below it. And with enough dc current you can come pretty close to stopping them dead in their tracks. Certainly within one revolution. But the armature is soft, and its not possible to maintain the magnetic field from its shorted turns armature long enough to extract any output power from it for more than a few milliseconds. > GiaThnYgeia writes: > > So, are you saying the standard motherboard beeper/speaker (the one > > that beeps when you hit too many keys at once or that bios is > > telling you I am booting up ... any minute now bepp) is a > > microphone that feeds sound back into the system and mysteriously > > debian is allowing it to be recognized as an input device. > > No, due to the absence of all the other parts needed deliver any > signals generated by the speaker back to the computer (not to mention > that it would make a very poor microphone). Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: No sound-inputs but sound recording FMIT
On Sunday 05 March 2017 17:04:00 GiaThnYgeia wrote: > ΟΚ! > > Gene Heskett: > > On Sunday 05 March 2017 15:18:00 GiaThnYgeia wrote: > >> Back to shanity, how does a microphone produce an electrical wave > >> that can be translated into sound and how a wave may take the form > >> of electrical current that produces sound through a speaker? > > > > Very simple. With the glaring exception of the modern AC induction > > motor that in 99% of the stuff we buy, ANY other generator can also > > be used as a motor, including the ultra cheap electret condenser > > microphones, ditto any speaker, including the peizo tweeters, is > > also a microphone. Its part of the basic physics everything we use > > works by. > > So, are you saying the standard motherboard beeper/speaker (the one > that beeps when you hit too many keys at once or that bios is telling > you I am booting up ... any minute now bepp) is a microphone that > feeds sound back into the system and mysteriously debian is allowing > it to be recognized as an input device. > > I do not claim to have reinvented the wheel here, but how can this be > acceptable if it does hold any truth? > > > Cheers, Gene Heskett > > kAt If debian identify's it as a microphone, take it up with debian. Udev has been know to goose the moose before. File a bug if that is the actual case. And yes, that "speaker" might be a piezo beeper, but with the right amps looking at it, it will make a halfway decent microphone. This is paranoid scary given some of the tricks the NSA has pulled off. But commercial intercoms have been using a small speaker as the talkback microphone for at least the 70 years that I have been chasing electrons for a living. That dates back to well before the transistor was invented. And yes, I am now an old fart of 82. But I was an electronics geek well before the term became popular. I quit school in '48, and started fixing them newfangled things called tv's for a living. I finished off the last 18 years I worked by having a nameplate on my office door that said I was the Chief Engineer, w/o ever going back to school unless it was as the teacher. Along the way I collected a 1st phone ticket from the FCC, and a CET from a small town college prof in Nebraska, turning in the test in about 45 minutes. He had been teaching students for that certification for several years. I was the first to walk in, hand him the 20 to take it, and passed it. Its normally allowed 4 hours. IMO? He had no business teaching it if in 5 years or so, none of his students had passed it. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: No sound-inputs but sound recording FMIT
Gene Heskett writes: > Very simple. With the glaring exception of the modern AC induction motor > that in 99% of the stuff we buy, ANY other generator can also be used as > a motor... Induction motors can function as generators. You just need to connect them to an appropriate AC source and drive them above synchronous speed. GiaThnYgeia writes: > So, are you saying the standard motherboard beeper/speaker (the one > that beeps when you hit too many keys at once or that bios is telling > you I am booting up ... any minute now bepp) is a microphone that > feeds sound back into the system and mysteriously debian is allowing > it to be recognized as an input device. No, due to the absence of all the other parts needed deliver any signals generated by the speaker back to the computer (not to mention that it would make a very poor microphone). -- John Hasler jhas...@newsguy.com Elmwood, WI USA
Re: No sound-inputs but sound recording FMIT
ΟΚ! Gene Heskett: > On Sunday 05 March 2017 15:18:00 GiaThnYgeia wrote: > >> Back to shanity, how does a microphone produce an electrical wave that >> can be translated into sound and how a wave may take the form of >> electrical current that produces sound through a speaker? > > Very simple. With the glaring exception of the modern AC induction motor > that in 99% of the stuff we buy, ANY other generator can also be used as > a motor, including the ultra cheap electret condenser microphones, ditto > any speaker, including the peizo tweeters, is also a microphone. Its > part of the basic physics everything we use works by. So, are you saying the standard motherboard beeper/speaker (the one that beeps when you hit too many keys at once or that bios is telling you I am booting up ... any minute now bepp) is a microphone that feeds sound back into the system and mysteriously debian is allowing it to be recognized as an input device. I do not claim to have reinvented the wheel here, but how can this be acceptable if it does hold any truth? > Cheers, Gene Heskett kAt -- "The most violent element in society is ignorance" rEG
Re: No sound-inputs but sound recording FMIT
On Sunday 05 March 2017 15:18:00 GiaThnYgeia wrote: > Curt: > > In case this wasn't clear: we're imagining clay being fashioned upon > > a potter's wheel, and the striations that occur in the clay as it is > > molded (which might possibly produce, according to Charpak's > > conjecture, a sort of analog audio recording of ambient sounds in > > the finished product, e.g.--"Hey Mosche, got any more of that > > Egyptian beer we were drinking the other day?" spoken in some > > obsolete language no one has ever heard before). > > I don't know about clay, it sounds more probable that prehistoric > voices affected reflected light to the universe and its returning > reflection may incorporate data that when decoded may reveal those > voices. In other words some prehistoric sounds may not be heard yet. > > Back to shanity, how does a microphone produce an electrical wave that > can be translated into sound and how a wave may take the form of > electrical current that produces sound through a speaker? Very simple. With the glaring exception of the modern AC induction motor that in 99% of the stuff we buy, ANY other generator can also be used as a motor, including the ultra cheap electret condenser microphones, ditto any speaker, including the peizo tweeters, is also a microphone. Its part of the basic physics everything we use works by. > It is not > like particle acceleration science, it is stuff that many guitarists > now and most guitar repair-persons know. The question that is > relevant to the list is why would a security minded system allow such > noise to be communicated? Whatever that noise is, it shouldn't be > there, as if it is there it can be anywhere. > > Your appeal for case dismissal is denied! > > By the way, it takes about 3' to download FMIT or something similar, > lower the db cutoffs and increase the frequency range and if it is not > there we may have something to compare. I don't readily have a laptop > with a battery strong enough to stay on without AC, I assume they have > less electrical noise. My noise is around 21,5KHz-23KHz with an > emphasis around 22,2... which can't be random, but abrupt vibrations > on the case register within that noise wave. We are in the 220v/50hz > world, so it would be interesting what the noise freq. is on 110v/60Hz > > ... wait did you hear that? It is the noise of your world crumbling > ;) Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: No sound-inputs but sound recording FMIT
Curt: > > In case this wasn't clear: we're imagining clay being fashioned upon a > potter's wheel, and the striations that occur in the clay as it is > molded (which might possibly produce, according to Charpak's conjecture, > a sort of analog audio recording of ambient sounds in the finished > product, e.g.--"Hey Mosche, got any more of that Egyptian beer we were > drinking the other day?" spoken in some obsolete language no one has > ever heard before). I don't know about clay, it sounds more probable that prehistoric voices affected reflected light to the universe and its returning reflection may incorporate data that when decoded may reveal those voices. In other words some prehistoric sounds may not be heard yet. Back to shanity, how does a microphone produce an electrical wave that can be translated into sound and how a wave may take the form of electrical current that produces sound through a speaker? It is not like particle acceleration science, it is stuff that many guitarists now and most guitar repair-persons know. The question that is relevant to the list is why would a security minded system allow such noise to be communicated? Whatever that noise is, it shouldn't be there, as if it is there it can be anywhere. Your appeal for case dismissal is denied! By the way, it takes about 3' to download FMIT or something similar, lower the db cutoffs and increase the frequency range and if it is not there we may have something to compare. I don't readily have a laptop with a battery strong enough to stay on without AC, I assume they have less electrical noise. My noise is around 21,5KHz-23KHz with an emphasis around 22,2... which can't be random, but abrupt vibrations on the case register within that noise wave. We are in the 220v/50hz world, so it would be interesting what the noise freq. is on 110v/60Hz ... wait did you hear that? It is the noise of your world crumbling ;) -- "The most violent element in society is ignorance" rEG
Re: No sound-inputs but sound recording FMIT
On 2017-03-05, Curtwrote: > On 2017-03-04, deloptes wrote: >> GiaThnYgeia wrote: >> >>> PS Suddenly, the noises in one's head that nobody else hears are >>> recorded by one's only true friend, the PC :)) :))) >> >> Paranormal activities :D >> >> I think it could be some voltage induced by physical contact. >> >> Think logically - if there is no mic or nothing plugged in to your inputs, >> then nothing can be recorded. > > Georges Charpak hypothesized the possibility of restoring the voices of > ancient potters "recorded" in the microscopic grooves of earthenware > deformed by their voices as they worked. > > Interesting idea, anyway. > >> regards >> In case this wasn't clear: we're imagining clay being fashioned upon a potter's wheel, and the striations that occur in the clay as it is molded (which might possibly produce, according to Charpak's conjecture, a sort of analog audio recording of ambient sounds in the finished product, e.g.--"Hey Mosche, got any more of that Egyptian beer we were drinking the other day?" spoken in some obsolete language no one has ever heard before). -- "It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the far side of the hedge; or it might be the glory of speed; no one knew." --Mrs. Ramsay, speculating on why her little daughter might be dashing about, in "To the Lighthouse," by Virginia Woolf.
Re: No sound-inputs but sound recording FMIT
On 2017-03-04, delopteswrote: > GiaThnYgeia wrote: > >> PS Suddenly, the noises in one's head that nobody else hears are >> recorded by one's only true friend, the PC :)) :))) > > Paranormal activities :D > > I think it could be some voltage induced by physical contact. > > Think logically - if there is no mic or nothing plugged in to your inputs, > then nothing can be recorded. Georges Charpak hypothesized the possibility of restoring the voices of ancient potters "recorded" in the microscopic grooves of earthenware deformed by their voices as they worked. Interesting idea, anyway. > regards > > -- "It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the far side of the hedge; or it might be the glory of speed; no one knew." --Mrs. Ramsay, speculating on why her little daughter might be dashing about, in "To the Lighthouse," by Virginia Woolf.
Re: No sound-inputs but sound recording FMIT
GiaThnYgeia wrote: > PS Suddenly, the noises in one's head that nobody else hears are > recorded by one's only true friend, the PC :)) :))) Paranormal activities :D I think it could be some voltage induced by physical contact. Think logically - if there is no mic or nothing plugged in to your inputs, then nothing can be recorded. regards
Re: No sound-inputs but sound recording FMIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Mar 04, 2017 at 11:25:00AM +, GiaThnYgeia wrote: [...] > Come to think of it, do newsgroups still exist? To round-up this thread's recursive meta-hijacking: oh, yes, they definitely exist. There are a couple of providers out there keeping the service up, my favourite being eternal september: http://www.eternal-september.org/ Yes. Real NNTP. Gmane could be interesting too -- they offer (among other things) mailing lists via nntp. Regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAli6104ACgkQBcgs9XrR2kYr/wCcC1TUgngHl++zKLk24JeGXDKk hXsAnjic0xBZeVgfuNMnoG/H3Ce4biLq =nDFk -END PGP SIGNATURE-
Re: No sound-inputs but sound recording FMIT
On Friday, March 03, 2017 02:53:26 PM The Wanderer wrote: > Because hitting New means you have to put in the To address, but hitting > Reply means the address is already there and you can just start typing > your message (and possibly delete the quoted text, change the Subject > line, et cetera). > > Yes, this apparently is enough of a convenience factor to affect > people's behavior. Just to add $0.02 (I don't know who it belongs to, so didn't call it "my $0.02")--in kmail, just right click on the address to which you want to send the new email, and choose "New Message to" from the context menu...
Re: No sound-inputs but sound recording FMIT
https://packages.debian.org/jessie/fmit https://packages.debian.org/stretch/fmit Here are the two current versions of it and I like it because it gives a little more control in tuning out noise and concentrate in what I want to measure. It is most probably electrical noise and fluctuations of voltage and/or frequency, which may get amplified to look like an unstable wave form. This part may be understood enough to leave it to the sound experts. What is interesting is that a mechanical vibration may actually cause electrical contacts on the whole system to create an instability within that electrical noise. One does not need to be a sound physicist to translate this into an effective microphone. How many pc's don't have panels that act as drums and amplify noise and transform noise into a mechanical vibration? No, there is no onboard mic, there are only two audio inputs front and back, and as I said trying this in 2 other systems with different debian builds had similar results (some noise registering and affected by abrupt vibration). Yes I have pavucontrol installed, pulseaudio and utils. PS Suddenly, the noises in one's head that nobody else hears are recorded by one's only true friend, the PC :)) :))) deloptes: > GiaThnYgeia wrote: > >> I don't see how the previous got linked to a previous thread so I am >> reposting with additional clarification. >> >> OK, I did some testing on an other machine with a testing installation, >> downloaded FMIT (an instrument tuner that will pickup audio input/analog >> and tell you all kinds of stuff about the wave that is fed). >> Same exact behavior, hardware only lists two audio inputs and are both >> unplugged. The lower the db threshold for sound recording the more >> apparent the sound becomes. Each knock on the box shows corresponding >> amplification of that noise. >> >> Ok, so I picked up 2-3 live debian based USB sticks I have. I plugged >> then in to 3 different machines, downloaded FMIT and run it. Similar >> results. So it has nothing to do with my configuration of stuff. I say >> if some software is picking up sound from your environment and records >> it when no inputs are plugged in I would call this a "security" issue >> not a malfunction. >> >> What is there MORE to post so it can be reproduced? Blank live debian >> installations adding FMIT in 3 machines Jessie + Stretch (one on UPS, >> one on mains-plug, on laptop) if you allow it to see a wide spectrum of >> frequencies it records noise (mostly hi-freq) and only hardware inputs >> are unplugged. Where is the noise coming from? >> >> It probably has nothing to do with the program itself but its >> dependencies and some code feeding in wrong data as audio input. But it >> is actual sound > > I was interested in your mainboard - perhaps it has integrated mic. > > Do you have pavucontrol installed? Go to input devices and mute the mic > > regards > > -- "The most violent element in society is ignorance" rEG
Re: No sound-inputs but sound recording FMIT
The Wanderer: > On 2017-03-03 at 14:35, deloptes wrote: > >> The Wanderer wrote: >> >>> True, although someone who doesn't know that hitting Reply on an >>> existing message threads the reply in under the existing message >>> is unlikely to even know what message headers are, much less know >>> how to do this. (Or be using a mail client which does permit >>> that.) >> >> But why would you do this. You could simply press new and start a >> thread with your question > > Because hitting New means you have to put in the To address, but hitting > Reply means the address is already there and you can just start typing > your message (and possibly delete the quoted text, change the Subject > line, et cetera). > > Yes, this apparently is enough of a convenience factor to affect > people's behavior. > Since you guys now have hijacked the thread it is ok for me to continue On my second try to address a related issue I "forwarded" to the list the previous text as part of a reference with a new subject. As I use a non-html editor, txt comes in and txt comes out, I forget that the headers are hidden, but never thought they were included in forward, only in replies. It is good to know that mozilla in providing with a clean email gui does such things. Also if you use reply instead of reply-all or reply-list the headers that are picked up "by the list" are threading the messages. So it is partly the list-laundering activity that creates all the confusion. I'm willing to bet that in interpersonal exchange some of those messages wouldn't be threaded. But I've seen it happen both ways, Re: same-subject unthreaded and Re: different-subject threaded. So it must have to do with some mailing systems stripping headers and some that don't do it, and effective stripping goes two ways. Come to think of it, do newsgroups still exist? -- "The most violent element in society is ignorance" rEG
Re: No sound-inputs but sound recording FMIT
On 2017-03-03 at 14:35, deloptes wrote: > The Wanderer wrote: > >> True, although someone who doesn't know that hitting Reply on an >> existing message threads the reply in under the existing message >> is unlikely to even know what message headers are, much less know >> how to do this. (Or be using a mail client which does permit >> that.) > > But why would you do this. You could simply press new and start a > thread with your question Because hitting New means you have to put in the To address, but hitting Reply means the address is already there and you can just start typing your message (and possibly delete the quoted text, change the Subject line, et cetera). Yes, this apparently is enough of a convenience factor to affect people's behavior. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: No sound-inputs but sound recording FMIT
On 03/03/2017 08:53 AM, GiaThnYgeia wrote: I plugged then in to 3 different machines, downloaded FMIT and run it. Similar results. Is it in the repos?? Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: No sound-inputs but sound recording FMIT
The Wanderer wrote: > True, although someone who doesn't know that hitting Reply on an > existing message threads the reply in under the existing message is > unlikely to even know what message headers are, much less know how to do > this. (Or be using a mail client which does permit that.) But why would you do this. You could simply press new and start a thread with your question
Re: No sound-inputs but sound recording FMIT
GiaThnYgeia wrote: > I don't see how the previous got linked to a previous thread so I am > reposting with additional clarification. > > OK, I did some testing on an other machine with a testing installation, > downloaded FMIT (an instrument tuner that will pickup audio input/analog > and tell you all kinds of stuff about the wave that is fed). > Same exact behavior, hardware only lists two audio inputs and are both > unplugged. The lower the db threshold for sound recording the more > apparent the sound becomes. Each knock on the box shows corresponding > amplification of that noise. > > Ok, so I picked up 2-3 live debian based USB sticks I have. I plugged > then in to 3 different machines, downloaded FMIT and run it. Similar > results. So it has nothing to do with my configuration of stuff. I say > if some software is picking up sound from your environment and records > it when no inputs are plugged in I would call this a "security" issue > not a malfunction. > > What is there MORE to post so it can be reproduced? Blank live debian > installations adding FMIT in 3 machines Jessie + Stretch (one on UPS, > one on mains-plug, on laptop) if you allow it to see a wide spectrum of > frequencies it records noise (mostly hi-freq) and only hardware inputs > are unplugged. Where is the noise coming from? > > It probably has nothing to do with the program itself but its > dependencies and some code feeding in wrong data as audio input. But it > is actual sound I was interested in your mainboard - perhaps it has integrated mic. Do you have pavucontrol installed? Go to input devices and mute the mic regards
Re: No sound-inputs but sound recording FMIT
Op 03-03-17 om 14:15 schreef Greg Wooledge: Or manually remove the In-Reply-To: header, if your mail user agent permits you to do this. Don't forget the References: header. Regards, Frank
No sound-inputs but sound recording FMIT
I don't see how the previous got linked to a previous thread so I am reposting with additional clarification. OK, I did some testing on an other machine with a testing installation, downloaded FMIT (an instrument tuner that will pickup audio input/analog and tell you all kinds of stuff about the wave that is fed). Same exact behavior, hardware only lists two audio inputs and are both unplugged. The lower the db threshold for sound recording the more apparent the sound becomes. Each knock on the box shows corresponding amplification of that noise. Ok, so I picked up 2-3 live debian based USB sticks I have. I plugged then in to 3 different machines, downloaded FMIT and run it. Similar results. So it has nothing to do with my configuration of stuff. I say if some software is picking up sound from your environment and records it when no inputs are plugged in I would call this a "security" issue not a malfunction. What is there MORE to post so it can be reproduced? Blank live debian installations adding FMIT in 3 machines Jessie + Stretch (one on UPS, one on mains-plug, on laptop) if you allow it to see a wide spectrum of frequencies it records noise (mostly hi-freq) and only hardware inputs are unplugged. Where is the noise coming from? It probably has nothing to do with the program itself but its dependencies and some code feeding in wrong data as audio input. But it is actual sound -- "The most violent element in society is ignorance" rEG
Re: No sound-inputs but sound recording FMIT
On 2017-03-03 at 08:15, Greg Wooledge wrote: > On Fri, Mar 03, 2017 at 07:13:37AM -0500, The Wanderer wrote: > >> In order to start a new thread, you have to create the E-mail from >> scratch, e.g. by using a "New Mail" button or the equivalent. >> Creating an E-mail by replying to an existing message puts the new >> message into an existing thread, even if the Subject line is >> changed. > > Or manually remove the In-Reply-To: header, if your mail user agent > permits you to do this. True, although someone who doesn't know that hitting Reply on an existing message threads the reply in under the existing message is unlikely to even know what message headers are, much less know how to do this. (Or be using a mail client which does permit that.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: No sound-inputs but sound recording FMIT
On Fri, Mar 03, 2017 at 07:13:37AM -0500, The Wanderer wrote: > In order to start a new thread, you have to create the E-mail from > scratch, e.g. by using a "New Mail" button or the equivalent. Creating > an E-mail by replying to an existing message puts the new message into > an existing thread, even if the Subject line is changed. Or manually remove the In-Reply-To: header, if your mail user agent permits you to do this.
Re: No sound-inputs but sound recording FMIT
On 2017-03-03 at 05:46, deloptes wrote: > GiaThnYgeia wrote: > >> It probably has nothing to do with the program itself but its >> dependencies and some code feeding in wrong data as audio input. >> But it is actual sound > > you have to provide information so that it may be reproduced. Please > open another thread. The information you provided so far is a user > story and does not help further. To clarify this, since many people in the modern era apparently don't realize it: Changing the Subject line on a reply E-mail does not make that E-mail be the first mail in a new thread. (Although some E-mail clients, such as Outlook, will probably display it as if it was.) In order to start a new thread, you have to create the E-mail from scratch, e.g. by using a "New Mail" button or the equivalent. Creating an E-mail by replying to an existing message puts the new message into an existing thread, even if the Subject line is changed. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: No sound-inputs but sound recording FMIT
GiaThnYgeia wrote: > It probably has nothing to do with the program itself but its > dependencies and some code feeding in wrong data as audio input. But it > is actual sound you have to provide information so that it may be reproduced. Please open another thread. The information you provided so far is a user story and does not help further. regards
No sound-inputs but sound recording FMIT
OK, I did some testing on an other machine with a testing installation, downloaded FMIT (an instrument tuner that will pickup audio inpur/analog and tell you all kinds of stuff about the wave that is fed). Same exact behavior, hardware only lists two audio inputs and are both unplugged. The lower the db threshold for sound recording the more apparent the sound becomes. Each nock on the box shows corresponding amplification of that noise. Ok, so I picked up 2-3 live debian based USB sticks I have. I plugged then in to 3 different machines, downloaded FMIT and run it. Similar results. So it has nothing to do with my configuration of stuff. I say if some software is picking up sound from your environment and records it when no inputs are plugged in I would call this a "security" issue not a malfunction. It probably has nothing to do with the program itself but its dependencies and some code feeding in wrong data as audio input. But it is actual sound Forwarded Message Subject: Re: [solved] Re: No sound Resent-Date: Tue, 28 Feb 2017 22:30:30 + (UTC) Resent-From: debian-user@lists.debian.org Date: Tue, 28 Feb 2017 23:27:17 +0100 From: deloptes <delop...@gmail.com> Reply-To: delop...@gmail.com To: debian-user@lists.debian.org GiaThnYgeia wrote: > How does one trace the inputs of the audio system? Basic hardware > configuration only shows usual mic input, but using FMT for example > after mic gets unplugged some sound input is getting recorded. Banging > on the box records well. None of the hardware specs I've found list any > other device. Could the mini-speaker-beeper on the board act as a mic? > Why would audio software be allowed to use a speaker as a mic? don't hijack please. open new thread show us your hardware and other useful info. may be you have built in mic?
Re: Crackling sound from usb sound device
Does it crackle, when the USB storage device and the USB video device are unplugged? Were the USB storage and video devices plugged to other USB slots in the past? Hi Ralf, changed the slot for the audio device, now it works. Thanks for the hint Klaus -- 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/kiprkj$ct4$1...@news.m-online.net
Crackling sound from usb sound device
Hi, I have been using an external dac over usb for some months. Since about two weeks sometimes sound is distorted (irregualar crackles, which usually diappear after closing and reopening the application, i.e. mpd, xine, rhythmbox or a stream from firefox, some times). I am under the impression that this happens since a kernel upgrade a week ago. The message cannot get freq at ep 0x1 appeared in the logs before. Where does it come from and what does it mean? Any ideas? Thanks Klaus root@x200:~# cat /etc/debian_version 7.0 --- [UPGRADE] linux-image-3.2.0-4-amd64:amd64 3.2.35-2 - 3.2.39-2 Log complete. Aptitude 0.6.8.2: log report Thu, Mar 14 2013 16:46:14 +0100 [ 165.287224] usb 1-5.4: New USB device found, idVendor=0451, idProduct=adac [ 165.287233] usb 1-5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.287240] usb 1-5.4: Product: Audiolab M-DAC [ 165.287245] usb 1-5.4: Manufacturer: Lakewest Audio [ 165.295131] input: Lakewest Audio Audiolab M-DAC as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input13 [ 165.296463] generic-usb 0003:0451:ADAC.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Lakewest Audio Audiolab M-DAC] on usb-:00:1a.7-5.4/input0 [ 165.368060] 7:2:1: cannot get freq at ep 0x1 [ 165.380535] usbcore: registered new interface driver snd-usb-audio [ 194.468488] 7:2:1: cannot get freq at ep 0x1 -- 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/kika0b$bki$1...@news.m-online.net
Re: Crackling sound from usb sound device
With a new kernel there could be a different IRQ assignment, run $ lsusb -t $ cat /proc/interrupts And if in use $ /etc/init.d/rtirq status -- 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/1364046987.620.38.camel@archlinux
Re: Crackling sound from usb sound device
On 03/23/2013 03:00 PM, Ralf Mardorf wrote: With a new kernel there could be a different IRQ assignment, run $ lsusb -t /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M |__ Port 5: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M |__ Port 1: Dev 6, If 0, Class=stor., Driver=usb-storage, 480M |__ Port 2: Dev 4, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 3: Dev 5, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 4: Dev 7, If 0, Class=HID, Driver=usbhid, 12M |__ Port 4: Dev 7, If 1, Class=audio, Driver=snd-usb-audio, 12M |__ Port 4: Dev 7, If 2, Class=audio, Driver=snd-usb-audio, 12M |__ Port 6: Dev 3, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M $ cat /proc/interrupts CPU0 CPU1 0:32696843403876 IO-APIC-edge timer 1: 5 4 IO-APIC-edge i8042 8: 1 0 IO-APIC-edge rtc0 9: 14598 14334 IO-APIC-fasteoi acpi 12: 80 78 IO-APIC-edge i8042 16: 0 0 IO-APIC-fasteoi uhci_hcd:usb6 17: 0 0 IO-APIC-fasteoi uhci_hcd:usb7 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb8 19: 0 0 IO-APIC-fasteoi ehci_hcd:usb2 20: 0 0 IO-APIC-fasteoi uhci_hcd:usb3 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 22: 0 0 IO-APIC-fasteoi uhci_hcd:usb5 23:13358371235210 IO-APIC-fasteoi ehci_hcd:usb1 40: 0 0 PCI-MSI-edge PCIe PME, pciehp 41: 0 0 PCI-MSI-edge PCIe PME, pciehp 42: 0 0 PCI-MSI-edge PCIe PME, pciehp 43:10888001086909 PCI-MSI-edge eth0 44: 89271 86161 PCI-MSI-edge ahci 45: 1 0 PCI-MSI-edge iwlwifi 46: 79040 50447 PCI-MSI-edge i915 47: 69 72 PCI-MSI-edge snd_hda_intel NMI:279287 Non-maskable interrupts LOC:74342067155189 Local timer interrupts SPU: 0 0 Spurious interrupts PMI:279287 Performance monitoring interrupts IWI: 0 0 IRQ work interrupts RES:18153351836327 Rescheduling interrupts CAL: 10403 11478 Function call interrupts TLB: 56509 46165 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP:116116 Machine check polls ERR: 0 MIS: 0 And if in use $ /etc/init.d/rtirq status /etc/init.d/rtirq: No such file or directory -- 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/kikg8k$vsi$1...@news.m-online.net
Re: Crackling sound from usb sound device
On Sat, 2013-03-23 at 16:04 +0100, Klaus Pieper wrote: $ lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M |__ Port 5: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M |__ Port 1: Dev 6, If 0, Class=stor., Driver=usb-storage, 480M |__ Port 2: Dev 4, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 3: Dev 5, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 4: Dev 7, If 0, Class=HID, Driver=usbhid, 12M |__ Port 4: Dev 7, If 1, Class=audio, Driver=snd-usb-audio, 12M |__ Port 4: Dev 7, If 2, Class=audio, Driver=snd-usb-audio, 12M |__ Port 6: Dev 3, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M Does it crackle, when the USB storage device and the USB video device are unplugged? Were the USB storage and video devices plugged to other USB slots in the past? $ cat /proc/interrupts 16: 0 0 IO-APIC-fasteoi uhci_hcd:usb6 17: 0 0 IO-APIC-fasteoi uhci_hcd:usb7 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb8 19: 0 0 IO-APIC-fasteoi ehci_hcd:usb2 20: 0 0 IO-APIC-fasteoi uhci_hcd:usb3 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 22: 0 0 IO-APIC-fasteoi uhci_hcd:usb5 23:13358371235210 IO-APIC-fasteoi ehci_hcd:usb1 No IRQ issue. -- 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/1364055092.620.49.camel@archlinux
Re: Crackling sound from usb sound device
On Sat, 2013-03-23 at 17:11 +0100, Ralf Mardorf wrote: On Sat, 2013-03-23 at 16:04 +0100, Klaus Pieper wrote: $ lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M |__ Port 5: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M |__ Port 1: Dev 6, If 0, Class=stor., Driver=usb-storage, 480M |__ Port 2: Dev 4, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 3: Dev 5, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 4: Dev 7, If 0, Class=HID, Driver=usbhid, 12M |__ Port 4: Dev 7, If 1, Class=audio, Driver=snd-usb-audio, 12M |__ Port 4: Dev 7, If 2, Class=audio, Driver=snd-usb-audio, 12M |__ Port 6: Dev 3, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M Does it crackle, when the USB storage device and the USB video device are unplugged? Were the USB storage and video devices plugged to other USB slots in the past? $ cat /proc/interrupts 16: 0 0 IO-APIC-fasteoi uhci_hcd:usb6 17: 0 0 IO-APIC-fasteoi uhci_hcd:usb7 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb8 19: 0 0 IO-APIC-fasteoi ehci_hcd:usb2 20: 0 0 IO-APIC-fasteoi uhci_hcd:usb3 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 22: 0 0 IO-APIC-fasteoi uhci_hcd:usb5 23:13358371235210 IO-APIC-fasteoi ehci_hcd:usb1 No IRQ issue. No IRQ issue in the sense of, no other device does share USB IRQs, but OTOH all USB devices use the same bus. -- 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/1364055805.620.53.camel@archlinux
Re: Crackling sound from usb sound device
Does it crackle, when the USB storage device and the USB video device are unplugged? Were the USB storage and video devices plugged to other USB slots in the past? The video device is the builtin camera of the Thinkpad. I unplugged the USB CD and got the same behaviour (reboot, while mpd is playing, get the crackle after reboot). No hardware changes whatsoever in the last weeks. -- 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/kikn7f$hrl$1...@news.m-online.net
Re: Sound But No Sound - Finally Puzzled It Out
On Sat, Nov 22, 2008 at 06:07:33PM +0100, Jonathan Kaye wrote: Thomas H. George wrote: Sound: alsaplayer plays cd's totem plays videos. alsamixer adjusts volume. No Sound: Audacity has no input control - input options are determined by the sound card so presumably Audacity doesn't see the sound card. Neither does alsactl. alsactl names returns nothing and alsactl card0 says card0 is an unknown command. less /proc/asound/card0/id returns NVidia. The system is Lenny and Audacity 1.3.5-beta was installed with apt-get. Since this is a beta version perhaps the problem is an Audacity bug but, if so, what is alsactl's problem. Any suggestins? Tom Open audacity and look in the Preferences-Audio I/O and see which device Audacity is using. In my Audacity it defaults to OSS:/dev/dsp in which case I have to manually load the snd_pcm-oss module (using modprobe). Alternatively you can click on the arrows to the right of the device drop down menu and it may give you a choice to use your alsa device rather than First, Audacity shows no source bar because it only sees one source, line in. Second, as Jonathon suggested, the proper selections must be made in Audacity's Edit/Preferences/Audio I/O window. This is not obvious as when first loaded ALSA: HDA NVidia AD198x Analog (hw:0,0) is already selected for both input and output. This works for input but not for output. Other choices are offered but ultimately found ALSA: default works for both input and output. Third, getting this far does not guarantee either authe Alsamixer man page is necessary. When the correct capture channel is selected (There are at least three) and the proper output volumes are set and not muted you are in business. When all this is done it works very nicely. Having only line input is okay for me as the line is from my stereo system which includes phono, tape, cd, radio and tv. Still it is annoying not to be able to capture directly from the systems optical drive. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound But No Sound
Thomas H. George wrote: Sound: alsaplayer plays cd's totem plays videos. alsamixer adjusts volume. No Sound: Audacity has no input control - input options are determined by the sound card so presumably Audacity doesn't see the sound card. Neither does alsactl. alsactl names returns nothing and alsactl card0 says card0 is an unknown command. less /proc/asound/card0/id returns NVidia. The system is Lenny and Audacity 1.3.5-beta was installed with apt-get. Since this is a beta version perhaps the problem is an Audacity bug but, if so, what is alsactl's problem. Any suggestins? Tom Open audacity and look in the Preferences-Audio I/O and see which device Audacity is using. In my Audacity it defaults to OSS:/dev/dsp in which case I have to manually load the snd_pcm-oss module (using modprobe). Alternatively you can click on the arrows to the right of the device drop down menu and it may give you a choice to use your alsa device rather than oss. Either move should sort out the sound problems. Cheers, Jonathan -- Registerd Linux user #445917 at http://counter.li.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sound But No Sound
Sound: alsaplayer plays cd's totem plays videos. alsamixer adjusts volume. No Sound: Audacity has no input control - input options are determined by the sound card so presumably Audacity doesn't see the sound card. Neither does alsactl. alsactl names returns nothing and alsactl card0 says card0 is an unknown command. less /proc/asound/card0/id returns NVidia. The system is Lenny and Audacity 1.3.5-beta was installed with apt-get. Since this is a beta version perhaps the problem is an Audacity bug but, if so, what is alsactl's problem. Any suggestins? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound and no sound
On Sat, 12 May 2007 17:07:40 +0200 (CEST) chadjensen [EMAIL PROTECTED] wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Thanks for your help, Michael I had the same problem just barely and I fixed by going to the users and groups section and giving permissions to the user. It must be a bug in an update or something that wipes out the users permissions. users and groups-highlight user-properties and change it from there. chad Or add the user to the audio group. The web forums force people to change subject lines and remove context? No, but when you push the reply button a blank screen comes up. I just figured that the reply would be attached to the thread so I didn't need to reply with the same subject line and context. Sorry I am kind of new on this forum so a little slack would be nice. chad -- Szia: Nyizsa. -- Finally - A spam blocker that actually works. http://www.bluebottle.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sound and no sound
Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Thanks for your help, Michael I had the same problem just barely and I fixed by going to the users and groups section and giving permissions to the user. It must be a bug in an update or something that wipes out the users permissions. users and groups-highlight user-properties and change it from there. chad The web forums force people to change subject lines and remove context? No, but when you push the reply button a blank screen comes up. I just figured that the reply would be attached to the thread so I didn't need to reply with the same subject line and context. Sorry I am kind of new on this forum so a little slack would be nice. chad -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound and no sound
[quote]No, but when you push the reply button a blank screen comes up. I just figured that the reply would be attached to the thread so I didn't need to reply with the same subject line and context. Sorry I am kind of new on this forum so a little slack would be nice. chad[/quote] I just registered and try to post from the forum. Curios what will be the outcome (I left the subject blank, but included a quote with the quote tags). Andrei -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
Greg Folkert wrote: If the logout and login happens quickly, perhaps esound for the other person is not ending soon enough. You might look and see if things are hanging around for the other user. Oh, this might be important too if you are using fast user switching in GNOME, which just opens a new X on the next VT. I tried this on a freshly-rebooted host, logging in the first time as the no-sound user -- still no sound. Log out and back in as me, and I get sound. Mind you, I'm logging out, not switching users. I suspect that he has something in his dot files or his environment that's screwing thing up. I just dont' know what. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
On Thu, 2007-04-19 at 17:10 -0400, Michael S. Peek wrote: Greg Folkert wrote: If the logout and login happens quickly, perhaps esound for the other person is not ending soon enough. You might look and see if things are hanging around for the other user. Oh, this might be important too if you are using fast user switching in GNOME, which just opens a new X on the next VT. I tried this on a freshly-rebooted host, logging in the first time as the no-sound user -- still no sound. Log out and back in as me, and I get sound. Mind you, I'm logging out, not switching users. I suspect that he has something in his dot files or his environment that's screwing thing up. I just dont' know what. OK, now here is where you need to file a bug so Joss can't say *I've never seen it* File the bug on the gnome package. Explain everything. Use reportbug as your regular user. This needs a fix. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Sound and No Sound
Greg Folkert wrote: On Tue, 2007-04-17 at 16:47 -0400, Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. sudo adduser nosounduser sound Cheers. nosounduser is already a part of the audio group Is there anything else that I can check? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
Florian Kulzer wrote: On Tue, Apr 17, 2007 at 16:47:11 -0400, Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Is the second user a member of the audio group? Yes. Is there anything else I can check? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
On Wed, 2007-04-18 at 07:28 -0400, Michael S. Peek wrote: Florian Kulzer wrote: On Tue, Apr 17, 2007 at 16:47:11 -0400, Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Is the second user a member of the audio group? Yes. Is there anything else I can check? If the logout and login happens quickly, perhaps esound for the other person is not ending soon enough. You might look and see if things are hanging around for the other user. Oh, this might be important too if you are using fast user switching in GNOME, which just opens a new X on the next VT. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Sound and No Sound
On 04/18/2007 08:10 AM, Greg Folkert wrote: On Wed, 2007-04-18 at 07:28 -0400, Michael S. Peek wrote: Florian Kulzer wrote: On Tue, Apr 17, 2007 at 16:47:11 -0400, Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Is the second user a member of the audio group? Yes. Is there anything else I can check? If the logout and login happens quickly, perhaps esound for the other person is not ending soon enough. You might look and see if things are hanging around for the other user. Oh, this might be important too if you are using fast user switching in GNOME, which just opens a new X on the next VT. I had this no-sound problem (sans the error message) on a sarge system that was never solved. As Greg suggests, check what processes the user left running (ps -ef |grep username) and see if esound is locked to another user (ps -ef |grep esd , then iirc, check the sockets in /tmp for username). Good luck, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
On Wed, Apr 18, 2007 at 08:24:55AM -0400, Ralph Katz wrote: I had this no-sound problem (sans the error message) on a sarge system that was never solved. As Greg suggests, check what processes the user left running (ps -ef |grep username) and see if esound is locked to another user (ps -ef |grep esd , then iirc, check the sockets in /tmp for username). I see a similar problem in etch on the family machine. Whoever logs in first gets system sounds. if you then switch to and log in another user, that user gets no system sounds. other sound works fine for all users, just the system sounds. I notice that the esd socket is owned by whoever first logged in, but it has very liberal permissions so that anyone should be able to access the server. Not sure how to fix this. I tried running esd before starting up gdm so that the socket perms were root:root rwxrwxrwx but no luck. Any thoughts A signature.asc Description: Digital signature
Sound and No Sound
Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Thanks for your help, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
On Tue, 2007-04-17 at 16:47 -0400, Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. sudo adduser nosounduser sound Cheers. -- greg, [EMAIL PROTECTED] That was as boring as a performance of Richard the 3rd with potatoes for actors. They're all eyes. signature.asc Description: This is a digitally signed message part
Re: Sound and No Sound
On Tue, Apr 17, 2007 at 16:47:11 -0400, Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Is the second user a member of the audio group? -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound and No Sound
Michael S Peek wrote: Hello all, I have a machine. One user logs in (using gnome) and has sound. The second user logs in (also using gnome) and does not. When the second user double-clicks on the volume applet he gets the following error: The volume control did not find any elements and/or devices to control. This means that either you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting Remove from panel from the menu. Anyone have any advice on how to track down this problem? I figure it has to be something in the second users' environment or dot files, but I haven't a clue where to start. Thanks for your help, Michael Oh yeah, and: - both users are in the audio group - permissions on /dev/dsp are crw-rw, and owned by root:audio - contents of .xession-errors for second user contain the following: /dev/dsp: Permission denied *** (gnome-session:4512): WARNING **: Esound failed to start. I don't know why esound would fail to start if both users are in the audio group. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issue: slow sound?
Hi Dennis, Recently, sound started misbehaving. First, sound would not only fail to play, any application that called for use of sound would freeze, only to die (in the case of Totem) on a kill -9. A reboot later, and it now does play, but it sounds like a 33 rpm record knocked down to 16 rpm. Do you use some sound system like aRts or Jack? It sounds (haha :) more like a problem of such a system than of ALSA / OSS. Regards, Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sound issue: slow sound?
OK, weirdness here. Running Sarge, all updates current. Only thing out of distro is OOo 2.0 from backports. Sound card uses snd-cmipci. Recently, sound started misbehaving. First, sound would not only fail to play, any application that called for use of sound would freeze, only to die (in the case of Totem) on a kill -9. A reboot later, and it now does play, but it sounds like a 33 rpm record knocked down to 16 rpm. Since finding this problem, I've tried an apt-get --reinstall of alsa-base, a --purge (and subsequent installation) of all alsa-related items in my system (-base, -oss (which I think is required by xmms), -utils, and mixergui), and likewise, a dpkg-reconfigure of everything but alsamixergui - and none of these has helped. What am I missing, where should I look for errors, and what more information is needed for this problem? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Oh, NO! Not that same No Sound question again... (Sound now working)
Just in case anyone can use the two bits of information I turned up... Having tried everything I could find to try to make the OSS (i810_audio) driver work, based on what little information I could find about it in the docs or online , I finally gave up and compiled and installed Alsa drivers for my 2.4.18-bf2.4 kernel. Then, by using alsamixer and unmuting the usual suspects, I was able to get sound working. None of the other mixers I had previously installed (aumix, kmix, and xamixer2 (which crashed completely)) would enable sound to work. One point of interest was that the alsamixer GUI has a slider for headphone, which none of the other mixers have, and which was what I discovered by trial and error to be what controlled the sound output jack on my MB. I'm wondering if the i810_audio OSS driver was really at fault or if the mixers I was using with it were just incapable of controlling the output to the jack on my motherboard (and more significantly, how one could make such a determination). But, I gather there's no way do diagnose such things, so I guess I'll just Move On. I am disappointed, saddened, troubled, disheartened, and discouraged (did I miss any?) that it was only possible to get this working by trial and error. Auto mechanics discriminate between real mechanics who troubleshoot problems and fix them, and parts replacers who, just keep on replacing things (and charging the customer for it) until something works. The latter are generally considered by their cow orkers to be subhumans at best. If there's no way to actually troubleshoot these problems, and we have to resort to swapping modules in and out until something works, we're no better than the parts replacers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Oh, NO! Not that same No Sound question again... (Sound now working)
On Thu, 18 Nov 2004 11:46:51 -0800, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Just in case anyone can use the two bits of information I turned up... Having tried everything I could find to try to make the OSS (i810_audio) driver work, based on what little information I could find about it in the docs or online , I finally gave up and compiled and installed Alsa drivers for my 2.4.18-bf2.4 kernel. Then, by using alsamixer and unmuting the usual suspects, I was able to get sound working. None of the other mixers I had previously installed (aumix, kmix, and xamixer2 (which crashed completely)) would enable sound to work. One point of interest was that the alsamixer GUI has a slider for headphone, which none of the other mixers have, and which was what I discovered by trial and error to be what controlled the sound output jack on my MB. I'm wondering if the i810_audio OSS driver was really at fault or if the mixers I was using with it were just incapable of controlling the output to the jack on my motherboard (and more significantly, how one could make such a determination). But, I gather there's no way do diagnose such things, so I guess I'll just Move On. I am disappointed, saddened, troubled, disheartened, and discouraged (did I miss any?) that it was only possible to get this working by trial and error. Auto mechanics discriminate between real mechanics who troubleshoot problems and fix them, and parts replacers who, just keep on replacing things (and charging the customer for it) until something works. The latter are generally considered by their cow orkers to be subhumans at best. If there's no way to actually troubleshoot these problems, and we have to resort to swapping modules in and out until something works, we're no better than the parts replacers. IIRC, the 2.4.18-bf2.4 is one of the kernel used in the Woody boot floppy, so for space restriction and compatibility measures, his scope is only to have a bare system up and running, it doesn't have all the modules a default kernel sports. You can really troubleshoot the problems, the sources are out there, you only need the HW documentation on how your hardware works, but usually HW vendors don't cooperate, and here i'm not talking about asking for HW drivers, but only HW specs or documentations. Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues-no sound from cd players
On Wed, Dec 10, 2003 at 10:00:01PM -0600, tripolar wrote: | Thanks | hooked up the cdrom drive to soundcard. | now enjoying Tool cd :-) | In the past( I think) I have listened to cd's without that cable. | any idea how that worked? Some cd player software simply sends commands to the drive to play the cd. This requires the drive's audio-out to be connected to the sound card's audio-in. The other option is for the software to extract the data from the cd, process it, and write it out to the sound card. This does not require a direct audio connected between the two. It also requires more complex software processing, and as a result more CPU and bus bandwidth to play. -- One man gives freely, yet gains even more; another withholds unduly, but comes to poverty. Proverbs 11:24 www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Sound issues-no sound from cd players
$ playsound english.au /dev/dsp did work then I tried cd players again- both gnome kde cdplayers. each cd player picked up my music cd but played no sound. I then tried to listen to linus again $ playsound english.au /dev/dsp this time bash: /dev/dsp: Device or resource busy this is what fuser shows # fuser -v /dev/dsp USERPID ACCESS COMMAND /dev/dsp suley 2025 f artsd suley 2080 f artsd ok did #killall artsd now playsound works again what am i missing to get cdplayers to play sound? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues-no sound from cd players
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Dec 10, 2003 at 08:48:37PM -0600, tripolar wrote: $ playsound english.au /dev/dsp did work then I tried cd players again- both gnome kde cdplayers. each cd player picked up my music cd but played no sound. Is your CD player connected to your sound card? Do you have read access to the CD player device? - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/19wUUzgNqloQMwcRAitjAJwJnehfMUw4CuWOfp4PMLBJzqPGAwCgrGMj 8QGgm3VL9xvG0EdfKGT4K4A= =kL50 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound issues-no sound from cd players
Thanks hooked up the cdrom drive to soundcard. now enjoying Tool cd :-) In the past( I think) I have listened to cd's without that cable. any idea how that worked? On Wed, 2003-12-10 at 20:53, Paul Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Dec 10, 2003 at 08:48:37PM -0600, tripolar wrote: $ playsound english.au /dev/dsp did work then I tried cd players again- both gnome kde cdplayers. each cd player picked up my music cd but played no sound. Is your CD player connected to your sound card? Do you have read access to the CD player device? - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/19wUUzgNqloQMwcRAitjAJwJnehfMUw4CuWOfp4PMLBJzqPGAwCgrGMj 8QGgm3VL9xvG0EdfKGT4K4A= =kL50 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound: loading of sound driver fails after reboot from Windows
On 10 Jun 2003 D. [EMAIL PROTECTED] wrote: --- Ben Kal [EMAIL PROTECTED] wrote: Hi folks, Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. [snip] Since this is the first that I saw this, have you tried to add your sound driver to /etc/modules . In my /etc/modules I have ac97_codec, soundcore, pci-scan, tulip all on their own line. That causes those modules to load at boot up. HTH Don Just tried it, but as I already expected, this is no cure. Look, the problem is not that Linux does not try to load module ymfpci: it tries very hard! I find dozens of failed attempts reported in /var/log/syslog and /var/log/messages, from the very start of the boot sequence, when the hotplug subsystem loads drivers for all devices present. The problem is that, with ymfpci, every attempt fails with the following sequence of messages, which is also the result of entering 'modprobe ymfpci' on the command line: PCI: Found IRQ 9 for device 00:09.0 ymfpci: YMF744 at 0xfedf8000 IRQ 9 /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o: init_module: No such device /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o: insmod /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o failed /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o: insmod ymfpci failed Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Somehow, Windows is to blame, for this *only* happens after a 'warm reboot' from Windows. After a power-on boot or a reboot from Linux there is only one line in the logs about ymfpci, effectively saying that the module has been loaded and is ready for its job. Ben -- B.F.M. Kal Anjelierstraat 1, 2014 TC Haarlem, Netherlands tel +31 23 5324909, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound: loading of sound driver fails after reboot from Windows
On 11 Jun 2003 Brian P.D. Smyth [EMAIL PROTECTED] wrote: On Mon, Jun 09, 2003 at 09:34:00PM +0100, Ben Kal wrote: On Mon, Jun 02, 2003 at 12:28:45AM +0100, Ben Kal wrote: Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. Thanks, you were the only one who had something useful to say on this. As no further reactions are forthcoming I consider this little thread closed with the following conclusions: - Windows (Windows 2000 at least, that's the variant on my laptop) somehow keeps a grip on the sound card even after it has been stopped, possibly by not releasing the IRQ; - switching to grub as boot manager may solve the problem; - otherwise there is nothing but a hard reboot if yow want sound in Linux. It has been a number of years since I had Windows and Linux running together but I do recall that I had to disable a bios setting that allowed the OS (Windows) to control IRQs (disable Plug Play OS). If you hard set the IRQs in the bios both Windows and Linux should use the same ones. Plug Play OS *is* disabled in the BIOS. The BIOS allows me to hard set IRQs and IO ports for only a few devices, the serial and parallel ports as far as I remember, not for the sound card anyway. But, hard set or not, the IRQ and other hardware settings for the sound card drivers *are* the same in Windows and Linux. I carefully checked that, and reported the values in my original message. So I don't think you just provided the key to a solution. Thanks for your follow-up though! Ben -- B.F.M. Kal Anjelierstraat 1, 2014 TC Haarlem, Netherlands tel +31 23 5324909, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound: loading of sound driver fails after reboot from Windows
--- Ben Kal [EMAIL PROTECTED] wrote: On 2 Jun 2003 Gary L. Dolan [EMAIL PROTECTED] wrote: On Mon, Jun 02, 2003 at 12:28:45AM +0100, Ben Kal wrote: Hi folks, Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. I remember having this problem, unfortunately I cannot remember how I corrected it. I used to boot linux with Loadlin. When I got this box (which is now a number of years old), this same problem began. It appeared that Windows had a problem releasing the IRQ, so the only solution was a hard reboot. I think the problem was cleared up when I switched to grub as a boot manager. Thanks, you were the only one who had something useful to say on this. As no further reactions are forthcoming I consider this little thread closed with the following conclusions: - Windows (Windows 2000 at least, that's the variant on my laptop) somehow keeps a grip on the sound card even after it has been stopped, possibly by not releasing the IRQ; - switching to grub as boot manager may solve the problem; - otherwise there is nothing but a hard reboot if yow want sound in Linux. Thanks again, Ben Since this is the first that I saw this, have you tried to add your sound driver to /etc/modules . In my /etc/modules I have ac97_codec, soundcore, pci-scan, tulip all on their own line. That causes those modules to load at boot up. HTH Don __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound: loading of sound driver fails after reboot from Windows
Ben Kal wrote: On 2 Jun 2003 Gary L. Dolan [EMAIL PROTECTED] wrote: On Mon, Jun 02, 2003 at 12:28:45AM +0100, Ben Kal wrote: Hi folks, Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. I remember having this problem, unfortunately I cannot remember how I corrected it. I used to boot linux with Loadlin. When I got this box (which is now a number of years old), this same problem began. It appeared that Windows had a problem releasing the IRQ, so the only solution was a hard reboot. I think the problem was cleared up when I switched to grub as a boot manager. Thanks, you were the only one who had something useful to say on this. As no further reactions are forthcoming I consider this little thread closed with the following conclusions: - Windows (Windows 2000 at least, that's the variant on my laptop) somehow keeps a grip on the sound card even after it has been stopped, possibly by not releasing the IRQ; - switching to grub as boot manager may solve the problem; - otherwise there is nothing but a hard reboot if yow want sound in Linux. Thanks again, Ben Ben, It has been a number of years since I had Windows and Linux running together but I do recall that I had to disable a bios setting that allowed the OS (Windows) to control IRQs (disable Plug Play OS). If you hard set the IRQs in the bios both Windows and Linux should use the same ones. Regards, Brian -- Registered Linux User #22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound: loading of sound driver fails after reboot from Windows
On 2 Jun 2003 Gary L. Dolan [EMAIL PROTECTED] wrote: On Mon, Jun 02, 2003 at 12:28:45AM +0100, Ben Kal wrote: Hi folks, Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. I remember having this problem, unfortunately I cannot remember how I corrected it. I used to boot linux with Loadlin. When I got this box (which is now a number of years old), this same problem began. It appeared that Windows had a problem releasing the IRQ, so the only solution was a hard reboot. I think the problem was cleared up when I switched to grub as a boot manager. Thanks, you were the only one who had something useful to say on this. As no further reactions are forthcoming I consider this little thread closed with the following conclusions: - Windows (Windows 2000 at least, that's the variant on my laptop) somehow keeps a grip on the sound card even after it has been stopped, possibly by not releasing the IRQ; - switching to grub as boot manager may solve the problem; - otherwise there is nothing but a hard reboot if yow want sound in Linux. Thanks again, Ben -- B.F.M. Kal Anjelierstraat 1, 2014 TC Haarlem, Netherlands tel +31 23 5324909, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound: loading of sound driver fails after reboot from Windows
On Mon, Jun 02, 2003 at 12:28:45AM +0100, Ben Kal wrote: Hi folks, Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. snip Same situation here ... Sony Vaio PCG-F490 with debian woody and kernel 2.4.20. -- Yuhanes Tjandra GPG Key: 1024D/A3AD4AF0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sound: loading of sound driver fails after reboot from Windows
Hi folks, Do some of you know more about the following inconvenience I have with sound on my Linux machine: sound works fine if I boot directly into Linux after power-on, and if I reboot from Linux back into Linux; sound does not work at all after rebooting into Linux from Windows. In Windows sound works under all circumstances. (Please don't tell me not to use Windows. I don't, but my children do). I have found that the immediate cause of the problem is that Linux is unable to load the driver for the sound card if Windows has been in use since the last power-on. Knowing this does not help much: attempts to load the driver with modprobe or insmod simply fail. This exact phenomenon is not described in the documentation about sound on my machine, nor could I find a problem story like this on the web. What I would like to know is: - can something be done about this, in Windows and/or Linux, or is it an inconvenience one has to live with? - who is to blame, Windows for leaving the sound card in a messy state or Linux for not being able to deal with the state of the card? I already know that: - one has to disable 'Plug and Play' in the BIOS; it IS disabled - one has to make sure that iomem, ioports and IRQ settings for the sound chip have to be the same in Windows and Linux; they ARE the same, as follows: iomem : FEDF8000-FEDF ioport: FCC0-FCFF ioport: FC8C-FC8F IRQ : 9 Some other specifics of my machine: make and model: Sony VAIO PCG-F807K (it is a laptop) kernel: Linux 2.4.20 Debian release: basically woody, but a lot of things upgraded to 'unstable' sound chip: YMF-744B| (especially X and GNOME) sound driver : ymfpci.o, dependent upon: ac97_codec.o The most revealing (error) messages are the following ones, written to /var/log/syslog during a 'reboot-from-Windows': from the 'hotplug' phase of booting: /etc/hotplug/pci.agent: pcimodules is scanning more than 00:00.0 ... insmod: Using /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/soundcore.o insmod: Symbol version prefix '' insmod: Using /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ac97_codec.o insmod: Using /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o insmod: /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o: init_module: No such device insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg insmod: /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o: insmod /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o failed insmod: /lib/modules/2.4.20-hetkukel-1/kernel/drivers/sound/ymfpci.o: insmod ymfpci failed /etc/hotplug/pci.agent: ... can't load module ymfpci /etc/hotplug/pci.agent: missing kernel or user mode driver ymfpci later on, when initializing PCI bus devices (device 00:09.0 is the sound card): kernel: PCI: Enabling device 00:09.0 ( - 0003) kernel: PCI: Found IRQ 9 for device 00:09.0 kernel: PCI: Setting latency timer of device 00:09.0 to 64 kernel: ymfpci: YMF744 at 0xfedf8000 IRQ 9 kernel: ymfpci_codec_ready: codec 0 is not ready [0x] Other sound-related error messages in various places look to me as merely being the consequence of the ac97_codec and ymfpci modules not being loaded. Any information on similar experiences or hints for further investigation will be appreciated. Regards, Ben Kal -- B.F.M. Kal Anjelierstraat 1, 2014 TC Haarlem, Netherlands tel +31 23 5324909, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sound but no sound
Sound is working in that I get gnome desktop sound events but other programs like xmms or mp3blaster or freeamp just hang. I'm current on testing (sid). Sound used to work properly so some upgrade changed something but I have no clue what. What do I have set wrong? Where do I check? -- Civilization is a limitless multiplication of unnecessary necessities. -- Mark Twain *KH* Rick Pasotto[EMAIL PROTECTED]http://www.niof.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound but no sound
On Wednesday 02 October 2002 09:38, Rick Pasotto wrote: Sound is working in that I get gnome desktop sound events but other programs like xmms or mp3blaster or freeamp just hang. I'm current on testing (sid). Sound used to work properly so some upgrade changed something but I have no clue what. What do I have set wrong? Where do I check? GNOME uses esound to allow multiple programs to send audio data. You need to enable esd support in these other programs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound but no sound
On Wed, Oct 02, 2002 at 09:46:47AM -0700, Sean 'Shaleh' Perry wrote: On Wednesday 02 October 2002 09:38, Rick Pasotto wrote: Sound is working in that I get gnome desktop sound events but other programs like xmms or mp3blaster or freeamp just hang. I'm current on testing (sid). Sound used to work properly so some upgrade changed something but I have no clue what. What do I have set wrong? Where do I check? GNOME uses esound to allow multiple programs to send audio data. You need to enable esd support in these other programs. How do I do that? Is that a gnome setting or does each individual program need to be told? I didn't spot 'esd' anywhere in the xmms preferences nor do I see anything in the gnome sound control panel. -- Education is an admirable thing, but it is well to remember that nothing that is worth knowing can be taught. -- Oscar Wilde Rick Pasotto[EMAIL PROTECTED]http://www.niof.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound but no sound
On Wednesday 02 October 2002 10:12, Rick Pasotto wrote: On Wed, Oct 02, 2002 at 09:46:47AM -0700, Sean 'Shaleh' Perry wrote: On Wednesday 02 October 2002 09:38, Rick Pasotto wrote: Sound is working in that I get gnome desktop sound events but other programs like xmms or mp3blaster or freeamp just hang. I'm current on testing (sid). Sound used to work properly so some upgrade changed something but I have no clue what. What do I have set wrong? Where do I check? GNOME uses esound to allow multiple programs to send audio data. You need to enable esd support in these other programs. How do I do that? Is that a gnome setting or does each individual program need to be told? I didn't spot 'esd' anywhere in the xmms preferences nor do I see anything in the gnome sound control panel. It is per app. In xmms look for the output plugin control. You may need to install a xmms-esd or xmms-esound package. I do not use esound (or GNOME) but I have seen it come up enough on this list to have learned the answer (-: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ECS K7S5A SIS7012 Linux Onboard Sound: Erfolg! (War: Sound unter Debian - und nun?)
Hallo Allerseits! nachdem ich nun noch einmal eine geraume Zeit mit dem Onboard Sound meines Elitegroup K7S5A Motherboards verbracht habe kann ich einen Erfolg verbuchen! Alle Versuche den SIS 7012 Chipsatz mit den Treibern von SIS selbst oder den ac97_codec und i810_audio des Kernels 2.4.18 waren ohne Erfolg. Erst als ich einen neuen Kernel gebaut hatte, der Sound als Modules enthielt kam ich langsam weiter: M Sound card support M Intel ICH (i8xx) audio support M OSS sound modules M MPU-401 support (NOT for SB16) Ansich sind die Module für i8xx und MPU-401 für den späteren Erfolg überflüssig, aber weil es so klappt schreibe ich den kompletten Weg auf. Nach dem Installieren des neuen Kernels incl. Lilo-Aufruf und Reboot habe ich mir die letzte Version des ALSA Soundpaketes als Sources geholt: alsa-driver-0.9.0rc3.tar.bz2 alsa-utils-0.9.0rc3.tar.bz2 alsa-lib-0.9.0rc3.tar.bz2 Zuerst alsa-driver entpackt, danach ./configure --with-sequencer=yes aufgerufen, anschliessend make install und ./snddevices umd die nötigen Devices zu erzeugen. Als Nächstes müssen einige Anpassungen in /etc/modules.conf gemacht werden. Da Debian das aber selbst mit dem modutils Paket verwaltet habe ich eine Datei /etc/modutils/alsa angelegt: # ALSA portion alias char-major-116 snd alias snd-card-0 snd-intel8x0 # OSS/Free portion alias char-major-14 soundcore alias sound-slot-0 snd-card-0 # OSS/Free portion - card #1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss Danach update-modules aufgerufen damit diese Einträge automatisch in der modules.conf landen. Nun wird das alsa-utils Paket entpackt, mit ./configure eingerichtet und mit make install installiert. Danach steht auch der benötigte amixer zur Verfügung mit dem man die per Default stummgeschalteten Sounddevices erst einmal aktiv schalten muss. Ehrlich gesagt bin ich aus man amixer nicht so richtig schlau geworden, auch vermisste ich einen Befehl um mal eben nur die Devices einzuschalten. Also habe ich einfach ein kleines Script benutzt: /usr/local/bin/alsa-on #!/bin/sh amixer -c 0 set 'Master',0 unmute amixer -c 0 set 'Master Mono',0 unmute amixer -c 0 set '3D Control - Center',0 unmute amixer -c 0 set '3D Control - Depth',0 unmute amixer -c 0 set '3D Control - Switch',0 unmute amixer -c 0 set 'PCM',0 unmute amixer -c 0 set 'Line',0 unmute amixer -c 0 set 'CD',0 unmute amixer -c 0 set 'Mic',0 unmute amixer -c 0 set 'Mic Boost (+20dB)',0 unmute amixer -c 0 set 'Video',0 unmute amixer -c 0 set 'Phone',0 unmute amixer -c 0 set 'PC Speaker',0 unmute amixer -c 0 set 'Aux',0 unmute amixer -c 0 set 'Capture',0 unmute amixer -c 0 set 'Mix',0 unmute amixer -c 0 set 'Mix Mono',0 unmute amixer -c 0 set 'External Amplifier Power Down',0 unmute Ja, das kann man in einer Schleife viel besser machen. Nachdem ich festgestellt hatte, das es nur die halbe Miete war und ich nun auch noch den Pegel für jeden Ausgang aufdrehen muss reichte es mir und ich nam das Konsolen-Util alsamixer, mit dem ich einfach alle verfügbaren Pegel auf 75% stellte. Ein kurzer Versuch mit aplay irgendein.wav ergab Sound! Ich war happy. Als User ging es wieder nicht, weshalb ich brutal einfach /dev/mixer und /dev/dsp mit chmod 666 allgemein öffnete. Alles wie gesagt quick dirty. Nächster Test ob ein als User gestartetes X11 mit Enlightenment auch Sound hat. Dazu in die ~/.xinitrc eingefügt: [...] esd -nobeeps /dev/null startx gemacht, in Enlightenment apply sound eingeschaltet und - nichts :-(. Aber immerhin keine Fehlermeldung. Da ich Gkrellm installiert habe, das IMHO genialste X11-Tool überhaupt, und in diesem wiederum ein Volume-Plugin habe ich in diesem gerade nachkonfiguriert: Mixer-Devices [X]Vol [X]PCM [X]CD Options [X] Mute all mixer devices we control [X] Open/close mixer device [X] Save volumes on exit und restore them on startup Nun noch die Schieberegler im Gkrellm-Volume-Plugin aufgedreht und voila: Sound! Unter X11 geht nun play oder aplay nicht mehr weil esd die /dev/dsp etc. exclusiv belegt. Das ist aber auch kein Beinbruch, stattdessen geht esdplay. Was fehlt noch: Das Ingangbringen des Midi-Teils. Dieser lässt sich im Bios explzit mit einem (beliebigen)IRQ und einer Portadresse von 0x300h oder 0x330h konfigurieren. Unter linux habe ich bisher aber noch nichts gefunden was daruaf aufsetzt. Während ich jetzt *.au. *.wav und mit mpg123 auch *.mp3 abspielen kann ergibt ein Versuch mit *.mid nur eine Fehlermeldung beim Versuch auf snd-rawmidi zu schreiben. Alle Tipps sind sehr willkommen. Grüsse Frank -- Mein GnuPG/PGP Public Key (DSS, 1024Bit): http://www.home.vrweb.de/fblatzheim/pgp_bkey.txt msg16600/pgp0.pgp Description: PGP signature
AudioWave 16 AISA sound card, and sound-card IDE in general
I'm buying an old 486 from a friend real cheap to use as a mail server. The IDE card in it can only handle two ide devices, the machine has two hard drives, an IDE cd-rom, and an IDE tape drive. THe latter two he's been running from the sound card ide interface ... is it possible to do this in Linux? I moved my cdrom on my other machine off my soundblaster and onto the main IDE controller, but that's not an option in this 486 because the IDE card is full. Also, the sound card is an Audiowave 16 AISP (made by sony). The audiowave web page (found via altavista) says that the newer version, the AudioWave PCI something-or-other, is SoundBlaster 16 compat. ... anyone tried using the Audiowave 16 AISP under linux? I don't really need it to do sound (although if it does, so much the better), but I'm going to need it for a while to do IDE stuff. Will -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | | http://www.cis.udel.edu/~lowe/ | |PGP Public Key: http://www.cis.udel.edu/~lowe/index.html#pgpkey| -- | You think you're so smart, but I've seen you naked | | and I'll prob'ly see you naked again ... | | --The Barenaked Ladies, Blame It On Me | -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]