Baslinux mailing list

[Stephen Clement <s.clement AT sympatico.ca>]

David Moberg wrote:

> ----- Original Message -----
> From: "sindi keesan" <keesan AT sdf.lonestar.org>
>
>  
>
> > > > I tried it in BL2.  mplayer file.wav. It wants font.desc
> > > >        
> > > Can you add >stdo 2>stder to the end of the command, and post
> > > the stdo and stder files here please?
> > >      
> > While using mpe123 I typed mplayer file.wav >stdo 2>stder.
> > It told me 'illegal instruction'
> >    
>
> It looks like a processor incompatibility.
>
>  
>
> > stdo:  (standard output to screen?)
> >    
>
> Just a name I chose. The > redirection redirects stdout to
> a file, of course, 2> redirects stderr, too.
>
>  
>
> > MPlayer 1.0pre5-2.95.3 (C) 2000-2004 MPlayer Team
> >
> > CPU: Intel Pentium MMX P55C 349.3 MHz (Family: 5, Stepping: 3)
> >    
>
> It looks like a Celeron chip to me. It will need a different
> MPlayer binary which can handle it. I will try to build one.
> I am hoping that either I or Stephen Clemente will figure out
> how.
>  
Funny enough, I've been working on getting MPlayer to compile this 
evening, and it doesn't seem to want to compile for me, unfortunately. 
I'll notify the list once I manage to get a working MPlayer package.

>  
>
> > Detected cache-line size is 32 bytes
> > CPUflags:  MMX: 1 MMX2: 0 3DNow: 0 3DNow2: 0 SSE: 0 SSE2: 0
> > Compiled for x86 CPU with extensions: MMX
> >
> > Reading config file /usr/etc/mplayer/mplayer.confReading config 
> > file /root/.mplayer/config
> > Reading /root/.mplayer/codecs.conf: Reading 
> > /usr/etc/mplayer/codecs.conf: Using built-in default codecs.conf.
> >
> >
> > stder:  (error messages?)
> > : No such file or directory
> > Can't open '/root/.mplayer/codecs.conf': No such file or directory
> > Can't open '/usr/etc/mplayer/codecs.conf': No such file or directory
> >
> >    
> >
> > > > Maybe your BL3 has something mine does not.  Has anyone else tried
> > > > your mplayer yet?
> > > >        
> > > Not to my knowledge.
> > >      
>
> I posted that right before Ron Clarke reported.
>
>  
>
> > It worked for Ron.  Ron, do you have i686?
> >    
>
> Yes, he does. Actually, a P3, which IIRC is an i786.
>
>  
>
> > > > > It may need a PII. I can't figure out how to make it work on CPUs older
> > > > > than the machine I compiled it on. I first compiled it on a P4, but then
> > > > > it wouldn't work on my P2. So I recompiled it on my P2.
> > > > >          
> > > > Mine is a 233 MHz PI.  I have a 350MHz machine with super socket 7
> > > > - is that still a PI?
> > > >        
> > > No. It should be a PII, or Celeron or PPro at worst.
> > >      
> > We have a PPro under construction too, 200MHz with dual cpus.  Why 
> > is this better than a 233MHz PI? 
> >    
>
> Well, dual CPUs can provide approximately twice the speed on applications
> designed to take advantage of it. Also, the PPro has a more efficient
> architecture, which also improves performance.
>
>  
>
> > The 350MHz which is still together has an AMD-K6 3D processor.  My 
> > ethernet is not working this week so I can't easily test it right 
> > now. Won't ping.  I made sure the cables were pushed in at both 
> > ends. What else might I try to diagnose the problem?  It has always 
> > been finicky.
> >    
>
> Are there any patterns to its operation? Does it only work in certain
> conditions?
>
> David
>  
I'd like to comment that if you ./configure with the --target=i386-linux 
option it will work on older processors (I think).

Thanks,

Stephen Clement