9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jim mckie jmk@plan9.bell-labs.com
Subject: [9fans] Plan9 on ADM \b\b\b\b\b\b\bMD K6
Date: Sun, 26 Apr 1998 12:55:32 -0400	[thread overview]
Message-ID: <19980426165532.G7gyHA62O0rOwjYlb5UjJRRhIDO-mXLfvAvK4bUO9Zw@z> (raw)

it seems to have gotten quite far though your startup rc script
(cpurc or termrc?), look to see what happens next and if there's
something there depends on the hardware. you should be able to
do ^T^Tp to print out the process table, does the keyboard echo?

has anyone fixed the timing loop calculation in clock.c for the
non-intel chips? what does the CPU identification print on system
startup?

--jim

------ forwarded message follows ------

>From cse.psu.edu!owner-9fans Sun Apr 26 11:07:03 EDT 1998
Received: from plan9.bell-labs.com ([135.104.8.6]) by plan9; Sun Apr 26 11:07:03 EDT 1998
Received: from cse.psu.edu ([130.203.3.50]) by plan9; Sun Apr 26 11:07:02 EDT 1998
Received: from localhost (majordom@localhost) by cse.psu.edu (8.8.8/8.7.3) with SMTP id LAA24046; Sun, 26 Apr 1998 11:06:57 -0400 (EDT)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Sun, 26 Apr 1998 11:06:50 -0400
Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.7.3) id LAA24013 for 9fans-outgoing; Sun, 26 Apr 1998 11:06:46 -0400 (EDT)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from vega.aichi-u.ac.jp (vega.aichi-u.ac.jp [202.16.124.3]) by cse.psu.edu (8.8.8/8.7.3) with ESMTP id LAA24009 for <9fans@cse.psu.edu>; Sun, 26 Apr 1998 11:06:25 -0400 (EDT)
Received: by vega.aichi-u.ac.jp (8.8.5+2.7Wbeta5/3.6W)
	id AAA29500; Mon, 27 Apr 1998 00:14:59 +0900 (JST)
Received: by ar.aichi-u.ac.jp (NX5.67f/NX3.0S)
	id AA06201; Mon, 27 Apr 98 00:09:46 +0900
Date: Mon, 27 Apr 98 00:09:46 +0900
From: Kenji Arisawa <ar.aichi-u.ac.jp!arisawa>
Message-Id: <9804261509.AA06201@ar.aichi-u.ac.jp>
To: cse.psu.edu!9fans
Subject: [9fans] Plan9 on ADM \b\b\b\b\b\b\bMD K6
Sender: cse.psu.edu!owner-9fans
Reply-To: cse.psu.edu!9fans
Precedence: bulk

Hello 9fans!

I am now trying to install Plan9 on my new hardware to upgrade
my Plan9 system.
The hardware is,
	Mother Board:
	Gigabyte	GA-586SG
	with Award Modular BIOS v4.52PG
	CPU: AMD K6/233MHz
My concern was that Plan9 can run on K6, so I tested the hardware
using the harddisk that has been used as Plan9 terminal.
I removed scsi and ethernet configuration from plan9.ini to make
the situation simple.
The new hardware shows the following messages:
	init: starting /bin/rc
	controller not in /lib/vgadb
	...
	/bin/dossrv 20: Serving #s/dos
and then stopped to show any more messages.
We should see the prompt "term%" if succeed.
Probably it is hanged up.
I know how to configure /lib/vgadb.
My questions are:
1. Does anyone succeed on K6?
2. What posibility should I take into consideration?

Thanks,

Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp




             reply	other threads:[~1998-04-26 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-26 16:55 jim [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-04-26 15:09 Kenji

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=19980426165532.G7gyHA62O0rOwjYlb5UjJRRhIDO-mXLfvAvK4bUO9Zw@z \
    --to=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).