From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Date: Tue, 25 Jul 2000 05:07:45 -0400 [thread overview]
Message-ID: <200007250907.FAA19833@cse.psu.edu> (raw)
Hello,
Thank you for your quick reply.
>Are you running on a recognised CPU and the speed is correct?
CPU speed shown from 9pcfs is correct. I have added a patch by forsyth.
>the (tivial) DOS driver doesn't understand the layout of your
>floppy -this can happen if the FAT filesystem was made
>by a system we haven't catered for in the code.
The floppy is created using Plan9 pc/bootfloppy that is rewritten
following Russ.
------ pc/bootfloppy ------
#!/bin/rc
if(! ~ $#* 2) {
echo 'usage: bootfloppy /dev/fd0disk plan9.ini'>[1=2]
exit usage
}
if(! test -f $2) {
echo $2 does not exist >[1=2]
exit noplan9.ini
}
mkdir /tmp/bootfloppy.$pid
cp $2 /tmp/bootfloppy.$pid/plan9.ini
dd -bs 512 -count 1 < /dev/zero >/tmp/bootfloppy.$pid/plan9.nvr
disk/format -b /386/pbs -f -d $1 /386/9load /tmp/bootfloppy.$pid/*
rm -rf /tmp/bootfloppy.$pid
-------------------------------
9pcfs is copied using Windows98 because I have never succeeded in
copying file when I did on Plan9.
By the way, I will classify bellow what I can do or not.
1. pc/bootfloppy --- works fine
2. cp diskimage /dev/fd0disk --- works ( but not fine )
3. cp file n/a:/file --- always results in destruction
>Remake the fileserver kernel with 'chatty' defined as non-zero in
>dosfs.c and let's take a look at the output plus a hex dump of
>block 0 of the floppy.
The result is:
getclust0 @ 0
getclust seek addr 0
getclust read addr 0
can't read block
can't read boot block
panic: can't init dos dosfs on fd.
Eric said:
>well, i can say i've seen this one before. i have two AMD K6-3-400
>boxes, both obtained at about the same time, with two different
>motherboards.
And Okamoto:
>Mime works for K6/200 is ASUS TX97-E motherboard
The PC are:
GA-5AX with K6-2/300
ASUS P5A-VM with K6-2/350
Bus clock 100MHz makes a trouble?
By the way, I tried the boot disk to a PC with celeron/466.
The result was fine. It was straight until I got the "Config:" message.
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~2000-07-25 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 9:07 arisawa [this message]
2000-07-26 2:03 ` [9fans] Eric Dorman
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=200007250907.FAA19833@cse.psu.edu \
--to=arisawa@ar.aichi-u.ac.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).