[RC5] Dual P3 1.2GHz not automatically typed.
Colin L. Hildinger
colin at ionet.net
Sun Mar 17 13:03:51 EST 2002
The Tulatin core is newer than the newest client, therefore it is not
recognized by the client. I would assume that an updated revision of dnetc
would be required to recognize the new core PIII's and Celerons.
----- Original Message -----
From: "Christopher Hicks" <chicks at chicks.net>
To: "RC5 list" <rc5 at lists.distributed.net>
Sent: Sunday, March 17, 2002 10:08 AM
Subject: [RC5] Dual P3 1.2GHz not automatically typed.
> I've searched the web site several ways and I've dug through some of the
> mailing list archives and I know this has been discussed on the mailing
> list before, but.....
> What should I do when automatic processor type detection fails? I'm
> getting the message:
> Automatic processor type detection did not
> recognize the processor (tag: "6547:46B1")
> on a Dual P3 1.2G box.
> The box has been acting a bit weird, so I wanted to use d.net to see if
> there was anything wrong with the processors. With it not detecting the
> processors it's going to be hard to compare it to any of the benchmarks on
> file. :-( Any ideas or suggestions? Has anyone seen that processor tag
> If anyone whas experience/advice on getting Linux to work on a SuperMicro
> rack server I'd love hear about it. It's a SuperServer 6021H with 1G of
> "Outside of a dog, a man's best friend is a good book.
> Inside of a dog, it's too dark to read." - Groucho Marx
> To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
> rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5