Gustin Johnson wrote: > Ralf Mardorf wrote: > >> Hi Michael :) >> >> "Problems with a dual core on 64studio stable" >> >> The killall jackd issue has nothing to do with the distro, I'm using >> Suse too and some other people are using Arch, Sidux and other distros too. >> >> > killall jackd is not really the problem. This is only a vague > description of a symptom. If you want a problem fixed, you will have to > do better at reporting a problem. Simply shouting from the rooftops > does not accomplish much. > > >>> Still, this is not the main problem. Just changing the CPU shouldn't >>> break jackd. I wonder, if there's something wrong with the CPU or the >>> motherboard. On the other hand, I haven't experienced any problems >>> with other applicaions such as Thunderbird or Firefox. >>> >> You, a lot of other people and I have that killall jackd problem. >> Independent if they are using "good" Intel only stuff or like me a "bad" >> ASUS M2A-VM HDMI" with an "AMD BE-2350 (Socket AM2, Athlon X2 >> Dual-Core)" or stuff like that. >> >> > He does not have the same hardware as you. In fact he is using the > older AMD 939 pin based CPUs which is also what I am using in addition > he is using the same sound card as me. There is very little that your > hardware has in common with the original poster. > > Also, you only ever provided anecdotal evidence. I am also a part of > the Ubuntu Studio lists, and I do not see the epidemic that you report. > You bought badly supported hardware in spite of advice to the contrary. > Take responsibility for your own actions. > > >> All that is reported well by several people to the "right" people. Some >> > > "right" people? It does not matter what aspect of life we are talking > about, you need to give the right info to the right people. > > >> other Linux people and me, we are still using Linux for all day work, >> but we have given up Linux multimedia and we are fine with Windows XP >> pro for multimedia. >> > > Sorry to hear that, but then the question needs to be asked, what are > you doing posting here? You did not provide any useful information at > all. > >> The only thing I can imagine, that might solve the trouble for you, is >> to take a look if there was a problem by your BIOS for your new CPU. >> Maybe there is an update for your BIOS that solved this. >> >> > We have not heard back from the original poster, so I have no idea what > the state of things are. I have almost identical hardware that is > working quite well for me, and if he needs help we should be able to > provide it. >
Hi Gustin :) I hope he will reply with the solution how he solved the problem. Keep in mind that "the same hardware" seldom is "the same hardware", there are different releases of "the same" CPUs and "the same" mobos. The killall jackd error is a problem for many people and only a few with this problem were able to get jackd stable and this is reported by many people very detailed. If people don't reply back, this might be, because they report such a bug to the jack dev list or something else, so we should wait for a reply. Other people might change to Windows and other people might have solved it, but do not report back the solution to the community. Gustin, you should search by Google for the error he got and you'll see, that the killall jackd error is something that a lot of people, using different hardware, have got. It's no help to ignore that and to blame me, because I'm writing something that is unpleasant. Cheers, Ralf > >> The Mozilla applications, OOo, GIMP and lots of other stuff is fine for >> me too, I "only" get this killall jackd too. I wasn't able to solve this >> from April 2008 to December 2008 and before I had other Linux multimedia >> troubles from November 2003 to April 2008 with another mobo and another CPU. >> >> Since January 2009 I'm using Windows for multimedia and I don't have any >> serious troubles. The only trouble I have is, that I sometimes have to >> restart my sequencer, because recorded MIDI data will have delay, if I >> won't do this. Anything else is fine and also the quality of Reverbs and >> Synth is much better, latencies are smaller etc. ... and no crashes. >> >> > I switched to Linux for all these same reasons. I doubt that the > latencies are better but I am not here to debate you on this. In the > future though, it is usually a good idea to back up your claims with > actual data. > > >> I guess you should use your old CPU again, if you like to go on with >> Linux for multimedia. If you were fine with it, why did you changed it? >> There seems to be a high risk, that if hardware that's fine with Linux >> completely wrecked, you won't get new hardware, that will be fine with >> Linux for multimedia too. >> >> I hope that some day that "killall jackd" problem will be taken serious >> by the Linux community. I couldn't notice that for the last month. >> >> > First you did not accurately describe a problem that needs to be fixed. > Second, I have always been impressed with how "serious" open source > developers are with regards to creating *quality* software. I am sorry > that you did not have the same experience as me, but unless you have an > actual question or something useful to share, you will accomplish > nothing except getting a few people angry. > > Best of luck, > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
