From: Grant Grundler <grundler@puffin.external.hp.com>
To: "Bryan W. Headley" <bheadley@interaccess.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: C110 question
Date: Tue, 02 Oct 2001 11:33:05 -0600 [thread overview]
Message-ID: <200110021733.LAA07820@puffin.external.hp.com> (raw)
In-Reply-To: Message from "Bryan W. Headley" <bheadley@interaccess.com> of "Tue, 02 Oct 2001 09:50:59 CDT." <3BB9D453.3050308@interaccess.com>
Bryan,
In general, questions like this will get better answers from
the parisc-linux mailing list - see http://lists.parisc-linux.org/.
I'll take a first whack at it though.
"Bryan W. Headley" wrote:
> Grant,
>
> Am still having issues getting my poor C110 to boot up.
> Doesn't read the boot CDROM worth a darn even after I "palo" the iso
> image -- which is probably not necessary, but what the hey?
The ISO image you downloaded has palo in it. Running palo with the
ISO image is either going to fail (best case, do no harm) or trash
the ISO image (worst case). I would guess the latter.
Make sure the md5sum output for the ISO image matches what's posted
on the website you got the ISO from.
> When I rboot
> the lifimage, it doesn't seem willing to send the console to the serial
> port nor is it willing to put stuff on the console, either.
When booting, answer Y to "interact with IPL" question with yes.
You have "manually" boot from the PDC prompt (aka BOOT_ADMIN prompt)
in order to get that question.
Then you can verify "console=ttyS0" parameter is set.
Disconnecting the keyboard should force the console output
to the serial port.
Oh - and several workstations may have issues with serial port numbering.
Ie what's labeled port A on the back may be seen as ttyS1 by parisc-linux.
Some of that has been fixed with newer kernels.
You would need to build a newer kernel and boot it via bootp.
This isn't as simple as it sounds...perhaps wait until a new
ISO is published.
> Anyway, it tries to boot (silently) and does things with the hard disks
> (I know not what), but...
>
> The drives are hanging off of a FWSCSI controller. I'm right in thinking
> that the support for that is still not there, right?
In general the SCSI driver for Zalon works. The problem is with
IO MMU support for devices below anything other than the first IO MMU.
> I'm wondering if I
> should go through the old Mach4 source and try to glom over the FW
> support... Whose toes do I step on if I try to do that; who should I
> handshake with?
I dunno. I've only looked at the mach sources once for 712 stuff.
> If you know a good "secret handshake" command to give at the iplboot to
> make the kernel send it's console messages to to STI or ttyS0, that'd be
> appreciated.
It's not secret - search for "console=" in the mail archives.
> Oh, and I upped the puppy to 256 Mb, but I doubt that confuses it too
> much (eek! The memory map is not floating to the "last 32K" or
> something, is it?)
no. 256MB isn't that much at all. I'm running 2GB in my c3k
and once had as much as 4GB in the c3k.
> I get this puppy up, I get to bring up the 735/99, and then figure out
> what HP means, we can use STI to be the basis of the X driver...
XF86 is mostly working for B180 and 712's from reports on p-l mailing list.
If you have Vis-EG (normal built-in) graphics, it might work for
C110 as well since it's not using IO MMU (afaik).
grant
next parent reply other threads:[~2001-10-02 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BB9D453.3050308@interaccess.com>
2001-10-02 17:33 ` Grant Grundler [this message]
2001-10-04 15:27 ` [parisc-linux] Re: C110 question Thomas Bogendoerfer
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=200110021733.LAA07820@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=bheadley@interaccess.com \
--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