From: "John O'Donnell" <johnnyo@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: /proc/cpuinfo incomplete for AMD 386DX 40?
Date: Thu, 27 Jun 2002 06:06:18 -0400 [thread overview]
Message-ID: <3D1AE39A.9000200@mindspring.com> (raw)
Please CC my address as I do not belong to the list. TIA
I am just curious.
I have a file/web server that I updated with Slackware 8.1. It runs
virtual web hosts, DynDNS, PPPoE, NFS, NAT and some other minor services.
This is an AMD 386 40Mhz with a 387 co-processor add-on and 32MB RAM.
It is functioning fine but I was poking around /proc/cpuinfo and it
says:
root@juanisan:/proc# cat cpuinfo
processor
: 0
vendor_id
: unknown
cpu family : 3
model
: 0
model name : 386
stepping
: unknown
fdiv_bug
: no
hlt_bug
: no
f00f_bug
: no
coma_bug
: no
fpu
: yes
fpu_exception
: no
cpuid level : -1
wp
: no
flags
:
bogomips
: 5.17
Is there any harm in Linux not identifying stuff like the manufacturer.
I dont know if the i386 supports any extensions that would show up in
the flags field. Think the bogomips is right?!?
Hey it runs GREAT and I love this old box I bought piece by piece when
it was new :-) Like I said ... I was just curious.
I have not met a box Linux hasn't liked yet :-)
BTW it took half a day to compile 2.4.18 but It chugged away without a hitch!
Linux juanisan 2.4.18 #1 Wed Jun 12 19:29:12 EDT 2002 i386 unknown
TIA
Johnny O
--
=== Never ask a geek why, just nod your head and slowly back away.===
+==============================+====================================+
| John O'Donnell | |
| (Sr. Systems Engineer, | http://johnnyo.home.mindspring.com |
| Net Admin, Webmaster, etc.) | E-Mail: johnnyo@mindspring.com |
+==============================+====================================+
next reply other threads:[~2002-06-27 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 10:06 John O'Donnell [this message]
2002-06-27 13:26 ` /proc/cpuinfo incomplete for AMD 386DX 40? Zwane Mwaikambo
2002-06-27 14:11 ` Sean Neakums
2002-06-27 19:42 ` Willy Tarreau
2002-06-27 21:53 ` John O'Donnell
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=3D1AE39A.9000200@mindspring.com \
--to=johnnyo@mindspring.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.