Re: [linux-audio-dev] regarding mobos and CPUs
What is the problem with JACK and AMD cpus? I haven't heard of one. Personally, I have an nvidia nforce2 motherboard which has worked fairly well for me. Taybin -Original Message- From: Dave Phillips [EMAIL PROTECTED] Sent: May 6, 2004 10:44 AM To: LAD Mail [EMAIL PROTECTED], LAU Mail [EMAIL PROTECTED] Subject: [linux-audio-dev] regarding mobos and CPUs Greetings: A client has asked me to get some opinions regarding AMD CPUs and recommended motherboards. He's planning to replace an SMP system that has apparently never worked quite right. He doesn't want another SMP mobo, and a friend is advising him to go with a uniprocessor system built around a recent AMD CPU. The recent JACK problem with AMD CPUs was a revelation for me: I'd never had any problems with AMD chips, but now I'm feeling reluctant to recommend them. Am I just being paranoid, or are there particular reasons to go with Intel instead of AMD ? My client is considering a P4 instead of the AMD, hence this infoquest... Also, what's a recommended motherboard ? Are there any mobos that should definitely be avoided ? TIA for any help you guys can proffer, it's much appreciated. Best regards, dp
Re: [linux-audio-dev] regarding mobos and CPUs
Taybin Rutkin wrote: What is the problem with JACK and AMD cpus? I haven't heard of one. Not so long ago a release of qjackctl in Planet C failed due to (IIRC) JACK getting compiled with an SSE call (or calls) that killed it completely on my Duron. The problem was simply and quickly solved, and I'm perhaps off-base accusing JACK but that's where the problem came from. Maybe it was a bad make ? Anyway, if it's the opinion of the LAD developers that AMD is OK then that's what I need to know. As I stated, I've had only that one difficulty with AMD and Linux audio software, so I think I'm just being paranoid. Best, dp
Re: [linux-audio-user] Re: [linux-audio-dev] regarding mobos and CPUs
On Thu, May 06, 2004 at 11:20:38 -0400, Dave Phillips wrote: Taybin Rutkin wrote: What is the problem with JACK and AMD cpus? I haven't heard of one. Not so long ago a release of qjackctl in Planet C failed due to (IIRC) JACK getting compiled with an SSE call (or calls) that killed it completely on my Duron. The problem was simply and quickly solved, and I'm perhaps off-base accusing JACK but that's where the problem came from. Maybe it was a bad make ? The modern AMD chips support SSE, and its not really the AMDs fault, its just that someone put some dodgy optimation code in the Makefile or auto*. - Steve
Re: [linux-audio-dev] regarding mobos and CPUs
Yes, that was just an autotools problem. It could have happened to a P4 if jack was built on an AMD box. It was more of a cross-compilation issue. Taybin -Original Message- From: Dave Phillips [EMAIL PROTECTED] Sent: May 6, 2004 11:20 AM To: The Linux Audio Developers' Mailing List [EMAIL PROTECTED], LAU Mail [EMAIL PROTECTED] Subject: Re: [linux-audio-dev] regarding mobos and CPUs Taybin Rutkin wrote: What is the problem with JACK and AMD cpus? I haven't heard of one. Not so long ago a release of qjackctl in Planet C failed due to (IIRC) JACK getting compiled with an SSE call (or calls) that killed it completely on my Duron. The problem was simply and quickly solved, and I'm perhaps off-base accusing JACK but that's where the problem came from. Maybe it was a bad make ? Anyway, if it's the opinion of the LAD developers that AMD is OK then that's what I need to know. As I stated, I've had only that one difficulty with AMD and Linux audio software, so I think I'm just being paranoid. Best, dp
Re: [linux-audio-dev] regarding mobos and CPUs
On Thu, 2004-05-06 at 07:53, Taybin Rutkin wrote: Yes, that was just an autotools problem. It could have happened to a P4 if jack was built on an AMD box. It was more of a cross-compilation issue. Yes, there is no problem with the AMD processors that I know of. This was a packaging problem triggered by the autotools problem. In essence the package itself was saying I can run on any i386 cpu so that apt/rpm was happily installing it on a Duron processor (which is compatible with the i386 instruction set). _But_ the contents of the package did not agree with the label and I did not catch that before releasing it :-) The executable itself had instructions that could _not_ execute in the Duron processor (but, for example, they would have worked fine on more recent AMD processors). So the program segfaulted on startup with an illegal instruction fault. Anyway, just to clarify things... -- Fernando -Original Message- From: Dave Phillips [EMAIL PROTECTED] Sent: May 6, 2004 11:20 AM To: The Linux Audio Developers' Mailing List [EMAIL PROTECTED], LAU Mail [EMAIL PROTECTED] Subject: Re: [linux-audio-dev] regarding mobos and CPUs Taybin Rutkin wrote: What is the problem with JACK and AMD cpus? I haven't heard of one. Not so long ago a release of qjackctl in Planet C failed due to (IIRC) JACK getting compiled with an SSE call (or calls) that killed it completely on my Duron. The problem was simply and quickly solved, and I'm perhaps off-base accusing JACK but that's where the problem came from. Maybe it was a bad make ? Anyway, if it's the opinion of the LAD developers that AMD is OK then that's what I need to know. As I stated, I've had only that one difficulty with AMD and Linux audio software, so I think I'm just being paranoid. Best, dp
Re: [linux-audio-user] Re: [linux-audio-dev] regarding mobos and CPUs
The modern AMD chips support SSE, and its not really the AMDs fault, its just that someone put some dodgy optimation code in the Makefile or auto*. ^^^ paul --p
Re: [linux-audio-dev] regarding mobos and CPUs
On Thu, May 06, 2004 at 10:44:13AM -0400, Dave Phillips wrote: [...] AMD CPUs are fine. This has been addressed elsewhere in the thread. You do need a good motherboard though. Also, what's a recommended motherboard ? Are there any mobos that should definitely be avoided ? I would definately avoid the ASUS A7S333, or anything else based on the SiS745 chipset. It has issues with interrupt routing and I could not get it to do anything even resembling realtime. I've had good results with the A7V600-X I replaced it with. The only downsides to this board are 1. the onboard audio sucks ass (but you weren't going to use it anyway, right? :) and 2. MIDI requires a dongle - if you have one from 10 years ago or something, the pinouts should be the same. Hope this helps, Jody
