linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Garcia <jpgarcia@execpc.com>
To: Tim Wojtulewicz <Tim.Wojtulewicz@NAU.EDU>
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: setpramboot problems
Date: Mon, 17 Apr 2000 18:52:10 -0500	[thread overview]
Message-ID: <38FBA3AA.3864AAA0@execpc.com> (raw)
In-Reply-To: 38FB9AF7.4E541642@dana.ucc.nau.edu


Tim Wojtulewicz wrote:
> I'm having a small problem wit h SetPRAMBoot.  This is most likely an error on my
> part (doh!).  I used it to set the boot PRAM so I could boot back to macos.  The
> values I used were 2 0 0 9.  I'm thinking this is /dev/hda9.  Is this incorrect?
> Anyways,  I tried to use the zap-PRAM keys to reset the thing, but it doesn't
> recognize that I'm holding them down, and just boots directly back to linux.
> Tried to boot from a cd, computer ignores that I'm holding C down.  System is a
> Pismo Powerbook, Linux PPC 2000, with Ben's 2.2.15-pre14 kernel.  Any ideas?

yaBoot is probably what you use on a pismo, which is an OF booter.  setpramboot
might not effect that.  I think 'C' might be another of the MacOS ROM things,
like the PRAM boot value.  Using OF directly can bypass the ROM, but im not sure
exactly how yaBoot works.  Though a few issues have popped up with setpramboot.

This weekend, I got my hands on some other systems.  I found that the linux
kernel maps NVRAM differently on NewWorld systems (OF >= 3.0), which includes
the 101/lombard.  As a result, the 4 bytes setpramboot modifies are in a
different location.  What the kernel does also seems to break nvsetenv.  using
hexdump on /dev/nvram, the PRAM boot location is on line 0x1370 with oldworld,
and 0x1220 with newworld if i recall correctly.  Any kernel maintainers know why
this happens?  (running Paul's 2.2.15pre17, dmesg lists where various nvram
sections are mapped, so the kernel knows that the address is different)

Regarding setpramboot, its definitely still a work in progress.  I still have
yet to figure out the meaning of the code when the bus is scsi.  the ata setting
makes sense, but the SCSI setting is still cryptic.  fyi, even if scsi, 'System
Disk' still only changes those 4 bytes, so a simple cut and paste of known
correct values would work.  Maybe I should put a hexcode option in the
/etc/pramtab.

I might have a chance update setpramboot this weekend.

Thanks.

--
Joseph P. Garcia      jpgarcia@execpc.com      jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate                      Student Employee - Systems Programmer
University of Wisconsin - Madison                            UW Lidar Group

"Did you ever notice how the Chinese Abacus, with 2 '5' beads and 5 '1'
beads, is perfect for hexidecimal math?"

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

  reply	other threads:[~2000-04-17 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-02  2:30 PRAMBoot Selector - update Joseph Garcia
2000-04-17 23:15 ` Tim Wojtulewicz
2000-04-17 23:52   ` Joseph Garcia [this message]
2000-04-18  9:29     ` setpramboot problems Benjamin Herrenschmidt
2000-08-17 11:11       ` Can't find nvtool? " Vladimir Simonov
2000-08-17 11:24         ` Martin Costabel

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=38FBA3AA.3864AAA0@execpc.com \
    --to=jpgarcia@execpc.com \
    --cc=Tim.Wojtulewicz@NAU.EDU \
    --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).