From: Chris Jantzen <chris-parisc@maybe.net>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] C180 questions
Date: Mon, 24 Jun 2002 01:00:59 -0700 [thread overview]
Message-ID: <20020624080059.GA31627@maybe.net> (raw)
So I have a new (to me) C180 and nearly everything is hunky-dory. Huge grats
to all the kernel/debian hackers! I have a few questions, though.
When I insert a PCI card, I get the dreaded firmware halt. The serial number
on this box is low enough that it could have PCI bugs that I've read about
on the net. Is this still repairable? Can it be worked around in software/
firmware? (Firmware 5.2, FWIW) I'm assuming that not only is the original
warranty long expired, that it wouldn't have transferred anyways. I have
a request in to HP support, I was just curious if this has been
encountered by anyone here before/recently.
I apologize that this is not directly Linux-related. This seems to be the
most active group working on machines near this vintage, and I fear
HP may reject my request for support based on not running HP-UX. Thanks
for any input! (And thanks again for a smashing job on the arch port. I've
got sparc, mips, powerpc, and ia32 all lying around the house, and I must
say the hppa install was the cleanest yet.)
BTW-Probably a FAQ and not that I intend to run it any time soon, but
how mature is the 64-bit in 32-bit firmware configuration? Does it
require a slightly different toolchain, or does binutils-hppa build
32 and 64-bit without a hitch?
--
chris jantzen kb7rnl =-> __O
Insert witty comment here. _`\<,_
http://www.maybe.net/ (*)/ (*)
next reply other threads:[~2002-06-24 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 8:00 Chris Jantzen [this message]
2002-06-24 19:22 ` [parisc-linux] C180 questions Grant Grundler
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=20020624080059.GA31627@maybe.net \
--to=chris-parisc@maybe.net \
--cc=parisc-linux@lists.parisc-linux.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