linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Henry Worth <haworth@ncal.verio.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Some small progress on PowerBook 2000 (Pismo - 102)
Date: Thu, 02 Mar 2000 22:31:06 -0800	[thread overview]
Message-ID: <38BF5C2A.9A6FCADD@ncal.verio.com> (raw)



I've been able to get the LinuxPPC 2000 lite image to boot to a ramdisk
shell on
a PowerBook 2000. Used a USB keyboard and Bootx 1.2b3 with the 'redhat'
bootparm
to boot to the text-based installer. When the first installer window
appears it
does take input and a ^z goes to the ramdisk shell (continuing the
install fails
when trying to mount the CDROM).

One other factor that I need to confirm really makes a difference, is
that after
seeing kmsgs about unsupported frame buffer, I set the LCD depth down to
256 colors.
I need to retry and see if this really matters.

I have been able to mount an HFS partition to /mnt, just had to wait for
a
screenful of "hda: lost interrupt messages" to go by. I'm currently
attempting to
write the kmsgs to that partition (any secrets I need to know?). I'll
post it
if a file actually gets written, otherwise I'm willing to manually
transcribe and post interesting kmsg and /proc entries, let me know what
may be usefull. This weekend
I'll look into activating the eth0 interface to dump data.

Are there any bootparms that would be useful for reconfiguring the ide
i/f
to polled I/O or perhaps persuading the kernel to use the ADB keyboard
(it is
recognized in the boot messages)? Any alternate ram-disk images that may
be
more usefull for debugging?

BTW, booting from the LinuxPPC 2000 Lite cd image (Mar. 1 version) fails
with
a can't find yaboot.conf message.

Henry

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-03-03  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-03  6:31 Henry Worth [this message]
2000-03-03  8:47 ` Some small progress on PowerBook 2000 (Pismo - 102) Henry Worth

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=38BF5C2A.9A6FCADD@ncal.verio.com \
    --to=haworth@ncal.verio.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).