From: "Joseph N. Hall" <joseph@5sigma.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: pcmcia enet on pb2400 (more info)
Date: Mon, 06 Dec 1999 10:56:02 -0700 [thread overview]
Message-ID: <MailDrop1.2d7j-PPC.991206105602@perlfaq.com> (raw)
The attempt to boot is dying during the pcmcia memory probe. I
am using the following in config.opts:
> include port 0x0-0xfff
> include memory 0x90000000-0x90ffffff
Both slots are filled. I get a single high beep and then a crash.
The above configuration is reported to work with pcmcia-cs-3.0.8
LinuxPPC R4 + 2.2.1 kernel on a pb2400 (confirmed with a Japanese
user). It appears that I am using 2.2.6-15a from the 1999 Q3 RPM.
Is this broken? If so, what should I try next?
RSVP to the address below or joseph@5sigma.com for more info.
Thanks,
-joseph
--
Joseph N. Hall, 5 Sigma Productions mailto:" <joseph> "@5sigma.com
Author, Effective Perl Programming . . . . . http://www.effectiveperl.com
Perl Training . . . . . . . . . . . . . . . http://www.perltraining.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-12-06 17:56 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=MailDrop1.2d7j-PPC.991206105602@perlfaq.com \
--to=joseph@5sigma.com \
--cc=" <joseph> "@5sigma.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).