9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Dennis D. Jensen" <dendecjen@yahoo.dk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] booting plan9 cd on thinkpad x23
Date: Sat, 13 Dec 2003 17:59:11 -0800	[thread overview]
Message-ID: <20031214015911.55259.qmail@web60501.mail.yahoo.com> (raw)
In-Reply-To: <200312090150.hB91oZfq024908@math.Princeton.EDU>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2072 bytes --]


--- John Stalker <stalker@Math.Princeton.EDU> wrote:
> You will need a
> plan9.ini which tells 9load where to find this
> kernel, but that
> is not a big problem.  It's after your kernel loads
> that the problems
> begin, since you don't have a plan9 userland.

Right.

I copied plan9-cd directly to win2k and before that to
its own partition. It turns out that win2k resides on
a fat32lba-disk, which is recognized by 9load, so I
didn't really need a particular dos-partition.

LD.COM doesn't work. I have tried many differenct
options, but it just doesn't start. I've tried booting
in dos-mode (failsafe).

When I boot from the plan9-cd it fails to find
9pcdisk, but I can tell where it resides on�the win2k,
but then it cannot find root of a kfs ("Root from:"
with default local!#S/sdC0/fs) and it cannot recognize
anything anymore, certainly not the graphic card
anyway. As you said: I cannot get past the kernel.

I've been experimenting, booting and rebooting all
afternoon and some of the night and am a little tired
now. I'll let things rest for a while unless somebody
has an idea how to continue.

> You will need
> to create
> enough of a plan9 userland under Win2k to get things
> rolling.
> This should be possible, but it may take a few tries
> to get it
> right.

The kernel seems to insist on loading a kfs-system
which I do not have yet: all things are on a
fat-partition. It looks like the classic problem of
the chicken and the egg: I cannot make any kfs before
booting plan9 which cannot boot before I have any
kfs... I don't know how to tell it where kfs (root)
is: It won't accept any of the variants of "local!..."
I've tried.

The kernel did recognize my NIC (e100/eepro100), the
cardbus and my usb! I've been reading up on the
manual-pages 9load(8) and plan9.ini(8), but I don't
know what to try next...

Thank you,
Dennis Decker Jensen


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree


  parent reply	other threads:[~2003-12-14  1:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 16:49 Dennis D. Jensen
2003-12-07 18:37 ` Russ Cox
2003-12-08 16:31 ` John Stalker
2003-12-08 23:46   ` Dennis D. Jensen
2003-12-09  1:50     ` John Stalker
2003-12-09  9:34       ` Dennis D. Jensen
2003-12-14  1:59       ` Dennis D. Jensen [this message]
2003-12-14  2:22         ` John Stalker
2003-12-14 15:29           ` Russ Cox
2003-12-14  4:34         ` boyd, rounin
2003-12-14 17:18           ` Dennis D. Jensen
2003-12-14 22:01             ` John Stalker
2003-12-16 14:20             ` John Stalker
2003-12-16 17:08               ` Dennis D. Jensen

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=20031214015911.55259.qmail@web60501.mail.yahoo.com \
    --to=dendecjen@yahoo.dk \
    --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).