I had this before and ran it down.  I was running an authentic AMD
'586; this was identified by rpm as a 486. RPM is the problem

Now I've two K6/2s  also, and investigated a little, being a hardware head.
Kernel notes make clear the K6 is an i686. Use --nodeps with rpm and forget it
until you crash - that's my advice.
-- 
        Regards,


        Declan Moriarty




Applied Researches - Ireland's Foremost Electronic Hardware Genius

        A Slightly Serious(TM) Company

Good judgement comes from experience;   experience comes from bad judgement.




On Wed, 28 Mar 2001, [EMAIL PROTECTED] wrote:
> ummmmm.... The K6 should be recognized as an i686. The Pentium 60-233mmx,
> Cyrix 6x86/MX, and AMD K5 were all i586 type processors. The PPro 150-200,
> P2/3, and K6/6-2 would be considered i686.
> 
> Chubby Vic <[EMAIL PROTECTED]>@linux-mandrake.com on 03/28/2001 10:10:58
> AM
> 
> Please respond to [EMAIL PROTECTED]
> 
> Sent by:  [EMAIL PROTECTED]
> 
> 
> To:   [EMAIL PROTECTED]
> cc:
> Subject:  WAIT!! STOP!! Re: [expert] DON'T USE --ignorearch!!!
> 
> 
> Stop, Mandrake!!!
> You can't do that!!
> 
> I still have a AMD K6 I need you guys to leave the i586
> rpms IN the installation!!
> 
> and I don't have the money to just go get a new i686 machine.
> 
> 
> Please do not exclude the i586 rpms from newer versions.
> 
> I want to stay with Mandrake, I would hate to change dists again.
> 
> 
> On Tuesday 27 March 2001 01:28 am,  so spoke Digital Wokan:
> > Someone tell that to the people who let the d*** i686 packages into
> > MandrakeFreq.
> >
> > Benjamin Sher wrote:
> > > Dear friends:
> > > I just an expert opinion on the --ignore command in rpm installations.
> > > E.g.
> > > #rpm -Uvh --ignorearch RealPlayer8.xxx.rpm
> > > My friend STRONGLY advises AGAINST using this command. He says that
> > > trying to get around the "different architecture" error message in this
> > > case is a hug mistake that will wipe out libraries and wreak havoc.
> > > So, do NOT use the --ignorearch way of installing an rpm file.
> > > Benjamin

Reply via email to