Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

On Mon, 25 Apr 2005, 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.

This is a regular Intel 233MHz cpu, as far as I know.  Is there something 
in dmesg that would tell me more?

233MHz Intel MMX stepping 03

The 350MHz has an AMD K6 3D in Super Socket 7 and mplayer gets the same 
error messages (both BL2 and BL3).
CPU:  AMD AMD-K6(tm) 3D processor stepping 0c

> > 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.

Maybe our 600MHz will work too, since his is that speed.  We replaced six 
bulging capacitors in something given us to recycle.

> > > > 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.

Another incentive to get it put together this year.  It is rather large 
and is occupying the only comfortable chair in my apartment.  But if 
350MHz won't do it, this older board probably won't either.

Perhaps Stephen Clement can compile for something slower and PI.

I will also try the Compaq 475MHz which works with Realaudio but not with 
its own onboard video chip in linux.

> > 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?

I fixed it.  I had copied over a file from another computer and it was 
insmodding the wrong ethernet module.  This is unrelated to having to push 
the cable in sometimes - user error.

> David

Sindi