9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gabriel Diaz <gabidiaz@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] problems booting a new install
Date: Fri, 26 Aug 2005 08:23:26 +0200	[thread overview]
Message-ID: <82c890d0050825232313828205@mail.gmail.com> (raw)
In-Reply-To: <009101c5a993$6a0905b0$e000a8c0@OBLIVIONDT>

[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]

Ok,

Now I can understand more :=)

First of all, the kernel you are using 9pcdisk is the one used to boot from 
the kfs image of the CD.

You should use the 9pcf kernel to boot a fossil terminal.

If you want vesa, look in the CD you downloaded for the correct kernel and 
put it in 9fat.
I can't remeber where are those kernels in the 9grid.de
<http://9grid.de>vesa right now, but a quick search in archives will
give you the answer i
think.

So, change your kernel to 9pcf and try booting again.

gabi

2005/8/25, Ezequiel Reyes <ezequiel.reyes@newhotel.co.cu>:
> 
> Hi,
> 
> > where you download your CD image?
> 
> > are you speaking about the vesa one provided in 9grid.de<http://9grid.de>
> ?
> 
> Yes, it is the vesa image, sadly, the standard would not work with my 
> nvidia
> GeForce4 and I couldn't find any info on the archives or the net of any 
> one
> being able to make it work with plan 9 or modify an entry in the vgadb to
> make it work. All I got was a black screen.
> 
> What kind of installation you done? (kfs or fossil or fossil+venti)
> 
> fossil, during instalation I was given [fossil, fossil+venti] with fossil 
> as
> default, there was no kfs option, I understand it is an old format of
> filesystem, but I did notice both, the demo system and the install system 
> on
> the CD used kfs when starting.
> 
> Do you see any error during install process?
> 
> no errors, all steps went fine, the only step that would fail was the last
> one, the boot setup process, since it offered floppy or plan9, I could not
> select the later since I have a dual booting system, the floppy failed
> trying to find the floppy need files on sdD1, which I don't have, it 
> didn't
> give me any choise to change the path to sdC1 which is my CD drive, that's
> is what I had been doing to get there, changing the path from sdD1 to sdC1
> every time it happened. So I gave it a ctrl-d and next came finish. I
> thought I would later be able to find and edit if needed the plan9.iniusing
> the demo system on the CD and with some advice so I did. There was a
> plan9.ini on 9fat but it was empty.
> 
> Where is the advice of the plan9.ini file edition ?
> 
> thread -> Re: [9fans] accesing a local fossil
> 
> Normally plan9.ini is generated automatically and works well, and normally
> you should done a fossil installation.
> 
> as I said, I did, there were no error on install, but later. I found the
> plan9.ini was empy (perhaps it would have been filled in the bootsetup 
> step
> of the instalation that I could not perform?)
> 
>

[-- Attachment #2: Type: text/html, Size: 2947 bytes --]

  reply	other threads:[~2005-08-26  6:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f9df42b7c5d3876bb2c68970a2c0425e@plan9.bell-labs.com>
2005-08-25  1:01 ` [9fans] complete control over our own website! Russ Cox
2005-08-25  1:02   ` Devon H. O'Dell
2005-08-25  6:48     ` Joseph Anthony Pasquale Holsten
2005-08-25 11:18   ` Sergey Zhilkin
2005-08-25 12:25     ` Gabriel Diaz
2005-08-25 14:26       ` [9fans] problems booting a new install Ezequiel Reyes
2005-08-25 14:42         ` LiteStar numnums
2005-08-25 15:20           ` Charles Forsyth
2005-08-25 15:34             ` Ezequiel Reyes
2005-08-25 16:24             ` LiteStar numnums
2005-08-25 15:42         ` Russ Cox
2005-08-25 15:49           ` Ezequiel Reyes
2005-08-25 15:59             ` Gabriel Diaz
2005-08-25 16:38               ` Ezequiel Reyes
2005-08-26  6:23                 ` Gabriel Diaz [this message]
2005-08-25 14:17   ` [9fans] complete control over our own website! Jason Gurtz

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=82c890d0050825232313828205@mail.gmail.com \
    --to=gabidiaz@gmail.com \
    --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).