9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installation Problems
Date: Wed, 13 Mar 2002 09:48:35 -0500	[thread overview]
Message-ID: <f6d40718935ddc20fcbeb01d842291da@plan9.bell-labs.com> (raw)

Inil is printed by the ATA driver when the interrupt routine is called
but the driver does not have an outstanding request. This is really a debug
message, and is arguably not correct as the interrupt routine can indeed be
called when there is nothing to do if the IRQ used by the ATA controller is
shared with some other device. However, the default IRQs used by the ATA
controller (14 and 15) are seldom shared with anything else. If you have
that situation try to separate the ATA controller onto its own IRQ. E.g.
if it a graphics card you can quite often disable the need for an IRQ in
the BIOS setup, and Plan 9 currently doesn't make use of graphics interrupts.

On Wed Mar 13 05:33:11 EST 2002, eternal_failure@lycos.com wrote:
> Hello.  Recently I found a link to plan-9 and after reading about it for 
> awhile, decided it sounded powerful and worthwhile to experiment with. 
> Unfortunately, I seem to be getting strange error messages during 
> installation.  Before it starts decompressing the filesystem, it leaves 
> a huge string of: "Inil20+Inil20+Inil20+... repeatedly, for a few 
> screens.  after it loaded rio, it all looked good, but after I type in 
> pickdisk, a huge string of Inil20/59+Inil20/59... came up in the middle 
> of the screen in a different font at the top of the screen.  I managed 
> to select the disk, but when asked about the mbr, it printed more of the 
> message covering the entire screen, and I am unable to read whats going 
> on.  Does anyone know what these messages mean?  My system is a Duron 
> 800 on an Asus A7V, 256 megs of ram.  I tested a few video cards and all 
> had thet strange messages, but the only one to get into Rio was a 
> Diamond Stealth 64 2001.  I also have a Netgear FA310TX and SoundBlater 
> AudioPCI which I tried disabling but the errors still came up.  Has 
> anyone had the same problems, or know how to remedy this?  thanks


             reply	other threads:[~2002-03-13 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 14:48 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-13 10:05 rob pascual
2001-12-05  9:56 [9fans] installation problems josh d
2001-12-05 14:09 ` Matt Senecal
2001-12-05 14:31 ` Sam Ducksworth
1999-01-27  9:15 [9fans] Installation Problems forsyth
1999-01-26  6:56 
1997-09-25 15:04 FRANKLIN
1997-09-25 13:43 Markus
1997-09-25 13:32 rsc
1997-09-25 12:50 FRANKLIN

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=f6d40718935ddc20fcbeb01d842291da@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.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).