From: Michael Thompson <mickey@berkeley.innomedia.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: mickey@berkeley.innomedia.com (Michael Thompson)
Subject: G3/IDE/BootX/2.3.49 woes
Date: Wed, 15 Mar 2000 23:16:39 -0800 (PST) [thread overview]
Message-ID: <200003160716.XAA19499@berkeley.innomedia.com> (raw)
I've got a B/W G3. I am able to boot 2.2.15 using bootX 1.2b3
without any problems.
However, with 2.3.49, the IDE controller doesn't seem to
be generating interrupts.
The controller (CMD646) is recognized, the drives are
identified.
I can see that irq 26 has been assigned to the device, and
this irq is enabled.
The controller's MRDMODE register (0x71) is initialized to
0x00, so it should be generating interrupts.
However, no interrupts are received from the device.
Could this be an interrupt routing issue?
Can someone let me know how I can boot linux on a G3
using OpenFirmware instead of bootX? Maybe I will
have better luck with OFW.o
Thanks very much!
-Michael Thompson
mickey@berkeley.innomedia.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-03-16 7:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200003160716.XAA19499@berkeley.innomedia.com \
--to=mickey@berkeley.innomedia.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).