Thanks for the reply!
Gustin Johnson schrieb:
Michael Jarosch wrote:
Hi!
I've been using the stable 64studio-distro since it's out on a AMD
Athlon64 3000+ without any problems.
Now, I've bought an AMD Athlon64 X2 3800+ dualcore processor and jackd
won't run stable any more. I only changed the CPU, besides this I'm
using the same components with the same 2.6.21-1-multimedia-amd64 kernel
and the same jackd-configuration. When I start jackd, I get this output:
I have a 939 pin 4400+ X2 that works great with that kernel. Stable low
latency performance is possible.
I have an ASUS A8V Deluxe. So my socket's also 939. And I've also got a
RME HDSP 9652. It's true - I use low latency, but keep in mind: I used
to use a slower CPU without any problems with this configuration.
I hoped, that jackd in 64Studio stable is too old for reliably using a
dualcore CPU. But you're using nearly the same hardware! That's bad news
for me.
Unlike windows, logging out usually does not accomplish much in Linux.
Things you start in the X-environment is usually getting killed if you
restart X. ;)
Either;
A) jack is still running in the background, in which case running "lsof
|grep jack" should find the process. You can then kill it with the kill
command. You may need to use the -9 flag.
You're right. I should have killed jackd manually before rebooting.
Silly me: The log even says it!
16:51:44.973 killall jackd
zombified - calling shutdown handler
cannot send request type 7 to server
cannot read result for request type 7 from server (Datenübergabe
unterbrochen (broken pipe))
cannot send request type 7 to server
cannot read result for request type 7 from server (Datenübergabe
unterbrochen (broken pipe))
jackd: Kein Prozess abgebrochen
16:51:45.278 Post-shutdown script terminated with exit status=256.
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. I've had problems with
the proprietary nvidia-driver, which killed my USB-subsystem. But since
I switched to the nv-driver this silly behaviour stopped. Everything
works but jackd. But this is really the core application on this machine...
Maybe I'm trying to plug the sound-device into another PCI-slot. But if
this won't work, I've got a real problem.
Greetings!
Mitsch
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users
