From: Bart Trojanowski <bart@jukie.net>
To: Ishikawa <ishikawa@yk.rim.or.jp>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: "uname -p" prints unknown for Athlon K7 optimized kernel?
Date: Sat, 14 Apr 2001 16:20:23 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0104141618440.13302-100000@localhost> (raw)
In-Reply-To: <3AD92D3B.EBBFC504@yk.rim.or.jp>
BTW this is also the case for AMD-K6-3 and I would imagine all other AMD
processors.
B.
On Sun, 15 Apr 2001, Ishikawa wrote:
> Hi,
>
> On my athlong K7 optimized kernel prints "unknown" fir oricessir type.
> (I have not realized what this "unknown" stood for until today.)
>
> #uname -p
> unknown
> #uname -a
> Linux duron 2.4.3 #2 Fri Apr 6 04:38:35 JST 2001 i686 unknown
>
> It would be nice to have the processor name printed.
>
> Is this kernel configuration procedure issue or
> `uname` problem?
>
> # which uname
> /bin/uname
> # file /bin/uname
> /bin/uname: ELF 32-bit LSB executable, Intel 80386, version 1,
> dynamically linked (uses shared libs), stripped
> # uname --version
> uname (GNU sh-utils) 2.0
> Written by David MacKenzie.
>
> Copyright (C) 1999 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is
> NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> #
>
>
>
>
>
> -
> 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/
>
--
WebSig: http://www.jukie.net/~bart/sig/
next prev parent reply other threads:[~2001-04-14 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 5:10 Ishikawa
2001-04-14 20:20 ` Bart Trojanowski [this message]
2001-04-15 5:38 ` joker
2001-04-15 13:57 ` Heinz Diehl
2001-04-15 15:55 ` Mr. Shannon Aldinger
2001-04-15 17:43 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2001-04-14 21:04 xcp
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=Pine.LNX.4.33.0104141618440.13302-100000@localhost \
--to=bart@jukie.net \
--cc=ishikawa@yk.rim.or.jp \
--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®