From: Kiyoshi MATSUI <kmatsui@t3.rim.or.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Cannot boot with kfs error
Date: Sat, 7 Jun 2003 02:13:37 +0900 [thread overview]
Message-ID: <20030607021337.0e381ce3.kmatsui@t3.rim.or.jp> (raw)
In-Reply-To: <20030505005647.6015e0ce.kmatsui@t3.rim.or.jp>
A sequel to the story of kfs i/o error at Plan9 bootstrap.
I upgraded the machine, including CPU (K6/200MHz => AthlonXP/2.0GHz),
motherboard and memory. I added a new IDE hard drive. I am still using,
however, the old ncr53C875 SCSI card.
I tried again to install Plan9 on one of the SCSI drives only to get
again the kfs i/o error at booting.
Then I installed on the IDE drive. Plan9 booted successfully!
Maybe my SCSI system has some instabilities. Maybe the Plan9's SCSI
driver has some short-comings to cope with the problem?
Anyway, I can use Plan9 now. A problem, however, remains -- long pause
of 10 minutes in booting process.
I have edited /rc/bin/termrc as follows.
***************
*** 53,59 ****
case NCR* 'AT&TNSX'* generic* _MP_* 'alpha apc'*
for(i in H w f t m v L S P U '$' 裡)
/bin/bind -a '#'^$i /dev >/dev/null >[2=1]
! for(disk in /dev/sd??) {
if(test -f $disk/data && test -f $disk/ctl)
disk/fdisk -p $disk/data >$disk/ctl >[2]/dev/null
for(part in $disk/plan9*)
--- 53,61 ----
case NCR* 'AT&TNSX'* generic* _MP_* 'alpha apc'*
for(i in H w f t m v L S P U '$' 裡)
/bin/bind -a '#'^$i /dev >/dev/null >[2=1]
! echo 'testing /dev/sdC?' # [1] Appears promptly
! for(disk in /dev/sdC?) {
! echo testing $disk # [2] Appears 10 minutes later
if(test -f $disk/data && test -f $disk/ctl)
disk/fdisk -p $disk/data >$disk/ctl >[2]/dev/null
for(part in $disk/plan9*)
***************
[1] appears promptly, but [2] appears 10 minutes later. Why?
When I edited the '/dev/sdC?' to '/dev/sdC0', rio started promptly and
the screen went black out displaying only an arrow cursor. Why? The
machine has only one IDE drive i.e. /dev/sdC0, neither /dev/sdC1 nor
/dev/sdC2.
Whether probe ethernet or not makes little difference of 10 minutes
pause. Speed of CPU also makes little difference.
Anyway, I am used to wait Plan9's bootstrap reading the Plan9 documents
on another machine's Linux.
kmatsui
prev parent reply other threads:[~2003-06-06 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030430160006.21083.98722.Mailman@psuvax1.cse.psu.edu>
2003-05-01 14:07 ` Kiyoshi MATSUI
2003-05-01 14:11 ` Russ Cox
2003-05-02 11:04 ` FJ Ballesteros
2003-05-04 15:56 ` Kiyoshi MATSUI
2003-05-05 7:49 ` Fco.J.Ballesteros
2003-05-05 9:22 ` okamoto
2003-06-06 17:13 ` Kiyoshi MATSUI [this message]
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=20030607021337.0e381ce3.kmatsui@t3.rim.or.jp \
--to=kmatsui@t3.rim.or.jp \
--cc=9fans@cse.psu.edu \
/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).