9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] installing plan9
Date: Tue, 16 Jan 2001 09:43:12 +0000	[thread overview]
Message-ID: <aeb.979597694@news.cwi.nl> (raw)
In-Reply-To: <20010115104812.E8786199E4@mail.cse.psu.edu>

I wrote:

>> the plan9 boot messages show that plan9 gets the ne2000 irq wrong
>> and assumes irq 9 instead of 3. After adding "irq=3" in plan9.ini I get
>>
>> i8259enable: irq 3 shared but not level
>> intrenable: couldn't enable irq 3, tbdf 0xffffffff for ether0

rsc@plan9.bell-labs.com (Russ Cox) answers:

> Add "eia1=disabled" to plan9.ini, and then the serial driver
> won't grab IRQ3 for its own uses.

Thanks! This works.


Second question.
Before getting this answer, I had installed plan 9 by first installing
a small Linux system, getting the plan 9 distribution to a local disk,
and installing from there. Afterwards, floppy boot worked, but LILO
boot failed.

Given this answer, I discarded the 60MB partition with the distribution
(plan9.9gz) and reinstalled via ethernet. This time both floppy boot
and LILO boot worked. Interesting.

Why did booting via LILO fail the first time? The error message was

	Bad format or I/O error
	Press almost any key to reboot...

given by the plan 9 boot sector.
I see 3 differences between the first and the second time:
 (i) during 2nd installation I had asked for a plan9 boot
(apparently all this does is make the partition active;
it gave an error message that the action was useless because
the installation was on the second, not the first IDE disk)
 (ii) the second time the installation was on the first partition,
the first time on the second one (both primary)
 (iii) the first time there was already a nonempty partition on
the disk; the second time plan 9 fdisk was the only one to write
something in the partition table. Linux assigns this disk a geometry
CHS=1057/16/63. Plan 9 wrote a table as if the geometry was 528/16/63.
A bug in plan9 fdisk? Could this influence booting?


So far about the question why booting via LILO failed the first time.
(This installation is not yet usable - in particular the video mode
does not really allow one to do anything useful - so I cannot yet
read the sources.)

Andries


  reply	other threads:[~2001-01-16  9:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 10:48 Russ Cox
2001-01-16  9:43 ` Andries Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06 17:50 [9fans] Installing plan9 Brad Davis
     [not found] <20040206154802.1583.14574.Mailman@psuvax1.cse.psu.edu>
2004-02-06 16:57 ` antiallergic
2004-02-06 17:20   ` andrey mirtchovski
2004-02-06 17:38   ` Jim Choate
2004-02-06 18:07     ` michael h. collins
2004-02-06 18:24       ` Jim Choate
2004-02-06 20:42         ` michael h. collins
2004-02-05  7:37 antiallergic
2004-02-11 18:27 ` Alberto Cortés
2001-01-15 10:01 [9fans] installing plan9 Andries Brouwer
1998-05-10 16:39 [9fans] Installing plan9 jim
1998-05-10 16:24 miller
1998-05-10 13:32 jim
1998-05-07  9:43 miller
1998-05-06 12:36 Franklin
1998-05-05 20:46 Franklin
1998-04-22  2:11 Kevin

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=aeb.979597694@news.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --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).