Meka[ni] wrote:
My problem is that I'm having a CPU related problem with mplayer. I recently swapped out my Athlon XP 1600 CPU for an Athlon XP 2000. Once I did that mplayer quit working. It was crashing immediately with an "Illegal instruction" message. Further fiddling with command line arguments got mplayer to give me some hints about being compiled with one CPU but run with another, and the like.
Further debugging has found that if I comment out the unset command and change the CFLAGS variable in make.conf to march=athlon, instead of march=athlon-xp, and re-compile mplayer, mplayer will then run correctly on this machine (but not with the best optimizations of course). For some reason I can not find anything else that doesn't work just fine with athlon-xp compiler optimizations.
I have not had time to replace the XP 1600 and recompile mplayer to see if it auto-detects that CPU as an athlon xp or an athlon-4 or an ?
hoping someone will point out what I've missed so that I don't have to open up the box and start messing with hardware.
Try editing /proc/cpuinfo. There are all the information you need for CFLAGS (line starting with "flags :"). Compare CFLAGS and those flags and ... good luck. :o)
Here's a "cat" of /proc/cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 2000+
stepping : 0
cpu MHz : 1659.627
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips : 3316.12
I must admit, I don't know if the "flags" choice is missing anything or not. The only thing that looks possibly off is the cpu MHz. I know the MHz on A XP cpu is less than the model #, but I didn't think it was that much lower.
-- [EMAIL PROTECTED] mailing list
