From: Voicu Liviu <pacman@mscc.huji.ac.il>
To: David Ford <david+hb@blue-labs.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Unknown CPU
Date: Fri, 16 Jan 2004 12:42:22 +0200 [thread overview]
Message-ID: <4007C00E.3040603@mscc.huji.ac.il> (raw)
In-Reply-To: <40083E96.3020109@blue-labs.org>
Hi,
You have the same CPU like me.
I have the EPox mobo and I had this issue.
If your bios ver is not 10/17/2003 then update it from the net.
David Ford wrote:
> I've an unknown cpu (athlon xp) in my machine. What data do I need to
> collect so the kernel knows what it is?
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 10
> model name : Unknown CPU Type
> stepping : 0
> cpu MHz : 1837.618
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
> bogomips : 3629.05
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-01-17 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 19:42 David Ford
2004-01-16 10:42 ` Voicu Liviu [this message]
2004-01-16 19:59 ` Dave Jones
2004-01-16 19:59 ` Joel Jaeggli
2004-01-16 20:58 ` David Ford
2004-01-16 22:44 ` Craig Bradney
2004-01-16 23:42 ` David Ford
2004-01-16 23:37 James Lamanna
2004-01-16 23:43 ` Craig Bradney
[not found] <1eIsb-5BX-23@gated-at.bofh.it>
[not found] ` <1eJob-6so-13@gated-at.bofh.it>
[not found] ` <1eKX6-7RO-35@gated-at.bofh.it>
[not found] ` <1eLT3-nm-19@gated-at.bofh.it>
2004-01-18 23:27 ` Lenar Lõhmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4007C00E.3040603@mscc.huji.ac.il \
--to=pacman@mscc.huji.ac.il \
--cc=david+hb@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®