Re: Why no Cyrix patch in 2.1.
Byron Faber (byron@morticia.PHYSICS.ColoState.EDU)
Thu, 09 Jan 1997 21:54:24 -0700
> >> I've adapted the current cyrix patch (for the 2.1.7) to
> >> the current kernel 2.1.20. I hope that Linus merge the
> >> cyrix patch to the next kernel.
> >
> >(patch removed).
> >
> >Quick question:
> >
> >I'm just curious who out there using the patch has gotten VSPM to work, and
> >what chip revisions you have? Maybe motherboard as well.
> >
>
> Cyrix (IBM actually) 6x86 P150+ overclocked to a P166+. Currently kernel
> 2.1.17 + Cyrix patch (adjusted to patch cleanly to 2.1.17). Every Cyrix
> option enabled, including power down on halt and VSPM. The motherboard is
> a Triton II VX board. Works without flaw. Haven't had a single problem at
> all, even overclocked. Here's my /proc/cpuinfo for chip info.
>
> processor : 0
> cpu : 586
> model : 6x86 2x Core/Bus Clock
> vendor_id : CyrixInstead
> stepping : 1 rev 7
> fdiv_bug : no
> hlt_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid : yes
> wp : yes
> flags : fpu
> bogomips : 133.53
>
>
> Thanks,
> Roy
Somebody else noted this, and it seems to be true somewhat:
My /proc/cpuinfo reads the same as above except I have
wp : no
My board is a Triton II Hx. I've played with the bios settings in some rather
vane attempt to see if this would change 'wp'.
Ironically enough, my stepping is 1 rev 7 as well. (P166+).
Does anybody have any ideas on what could cause this? Could it be the
motherboard chipset?
Damn Damn Damn.
Byron
--
#!/usr/local/bin/perl -- -pwcracker-in-3-lines-of-perl-plus-disclaimer
$u{$p[1]}=$p[0] while(@p=getpwent);while(<>){chop;foreach $c (keys %u)
{printf "u=%s p=%s\n",$u{$c},$_ if(crypt($_,$c) eq $c);}} # Use: pwc dict ...