9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geerten kuiper <geerten@bart.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] some problems
Date: Sun, 26 Aug 2001 22:04:37 +0200	[thread overview]
Message-ID: <3.0.1.32.20010826220437.008bb790@pop.bart.nl> (raw)

I have my basic install up and running, using Nick Waples' nvidia enabled
kernel, and now I'm trying to add printer, networking etc.

Problem 1 happens when I add "ether0=type=elnk3" to plan9.ini. On reboot,
ip/ipconfig (from termrc) reports a DHCP timeout, then nothing. Only way
out (as far as I can tell) is contr-alt-del or powerswitch. (The NIC is a
3c905B-TX, connected to another system through a crossover cable (no hub).
The other system isn't currently running. I don't really want to use DHCP
anyway, maybe I should edit the ndb before activating the NIC ??)

Problem 2 happens when I remove "*nomp=1" from plan9.ini. On reboot both
CPU's are activated, but the system hangs, with error:
mpintrenable: multiple enable irq 15, tbdf 5000000
intrenable: couldn't enable irq 15, tbdf 0xC007100 for sd1 (53c8xx)
(My SCSI-controller is 53c1010, dual channel. Both channels share interrupt
15 in single CPU mode without ill effects.)

Problem 3 happens after either of the previous ones: I revert to the
original plan9.ini, but any subsequent reboot still hangs after the line:
ndb/dns: can't read my ip address
Also in these cases there is a long delay two lines earlier, between:
"kfs...boot: nop..." and "time...".
Maybe this is caused by some corruption of the 9fat partition, because the
only way I have found to fix this is by booting from the install floppy and
rerunning bootsetup, thus reinitializing the 9fat partition.

I hope someone can help me.

Geerten



             reply	other threads:[~2001-08-26 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 20:04 geerten kuiper [this message]
2001-08-26 21:04 ` Martin Harriss
2001-08-29  9:04   ` geerten kuiper
2001-08-27  3:48 jmk
2001-08-29 13:47 Russ Cox

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=3.0.1.32.20010826220437.008bb790@pop.bart.nl \
    --to=geerten@bart.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).