From: Apurva Mehta <apurva@gmx.net>
To: 9fans@cse.psu.edu
Subject: [9fans] panic exeption/interrupt 14
Date: Thu, 19 Jun 2003 08:42:09 +0000 [thread overview]
Message-ID: <pan.2003.06.19.06.16.54.702234@gmx.net> (raw)
I have searched the archives of this group and while there are many
reports of this problem, there seems to be no solution that is usable
by me..
OK, I have installed plan9 on my second hard disk (primary slave). It
is a 3 GB hard disk which I have partitioned into a 2.3 GB first
primary partition and a 700 MB second primary partition (This is the
one plan9 is installed on).
I have not created an install floppy disk, I just installed directly from
the boot cd. In the last part of the installation, when it asked me to
choose a method to boot plan9, I tried to create a boot
floppy. However, that failed with the message to the tune of 'Cannot
create on non-floppy something/cdboot.' Where 'something' is a string
I cannot remember.
My bios is capable of booting from a slave disk, so I am tempted to
set the boot method to 'plan9'. However, I am weary that it may write to
the MBR of my first hard disk (on which GRUB is installed). I want it
to install to the MBR of my second hard disk. Where will it install?
Getting back to the installation. Since I had no options, I pressed
CTRL+D and quit the installation. I then set my BIOS to boot from my
second hard disk (Magically, the plan9 partition was set as the boot
partition. I verified this from '# /sbin/fdisk -l /dev/hdb' on
linux). So I see the plan9 boot messages and get pleased. Then I get
the infamous 'panic exception/interrupt 14'.
There is nothing more to be done so I reboot. I cannot try the
suggestions of adding
"*nousbprobe=1
*noetherprobe=1"
to my plan9.ini file as I do not have write access to such a file
anywhere. What should I do to get plan 9 working?
Thanks,
- Apurva
next reply other threads:[~2003-06-19 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 8:42 Apurva Mehta [this message]
2003-06-19 15:36 ` [9fans] " Rob Ristroph
2003-06-19 15:53 ` boyd, rounin
2003-06-19 18:48 ` [9fans] " Russ Cox
2003-06-20 8:39 ` Douglas A. Gwyn
2003-06-20 15:58 ` Apurva Mehta
2003-06-20 16:11 ` Russ Cox
2003-06-20 17:05 ` Apurva Mehta
2003-06-20 17:11 ` Russ Cox
2003-06-20 17:50 ` Apurva Mehta
2003-06-20 17:13 ` andrey mirtchovski
2003-06-20 17:51 ` Apurva Mehta
2003-06-23 8:57 ` Douglas A. Gwyn
2003-06-19 18:49 ` Russ Cox
2003-06-20 11:25 ` Apurva Mehta
2003-06-20 16:27 ` Russ Cox
2003-06-20 17:03 ` Apurva Mehta
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=pan.2003.06.19.06.16.54.702234@gmx.net \
--to=apurva@gmx.net \
--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).