last go before giving up
charlie allom
if anyone has gotten BSD going on a 3400 before, could they please contact
me?
im pretty certain the alias 'cd:0' doesn't exist, and should be really
either 'atapi', 'ata1' or 'bay-ata'.
i read somewhere that for OF 2.0.1 i should be using 'alias:partition' and
skip the file name (ofwboot.xcf)
can anyone verify?
last chance: anyone in the melbourne (australia) area that can lend me a
floppy drive bay froma 5300/3400 so i can boot from that?
appreciated.
c.
--
cha...@rubberduck.com
Melbourne, Australia
http://rubberduck.com/ - PGP available
Henry B. Hotz
>im pretty certain the alias 'cd:0' doesn't exist, and should be really
>either 'atapi', 'ata1' or 'bay-ata'.
Can't help you here, but I trust you can compare the aliases to the
full device tree and figure out what you want. If the drive has an
activity light you can confirm your guess as to the device at least.
>i read somewhere that for OF 2.0.1 i should be using 'alias:partition' and
>skip the file name (ofwboot.xcf)
This is true if you have used the installboot program to wipe out the
Apple partition map on the drive and install the bootxx program.
This process doesn't work on new Mac's where a partition of 0 means
the first understandable filesystem partition. On older Mac's (like
the 3400 I presume) partition 0 means load the boot blocks.
Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h.b....@jpl.nasa.gov, or hbh...@oxy.edu
charlie allom
should get an app to scan the scsi just to make sure.
thanks for this, i have anew lease of life now i know someone has a clue.
=)
--
cha...@rubberduck.com
Melbourne, Australia
http://rubberduck.com/ - PGP available
charlie allom
i think i might have the right way of entering the boot device, but maybe
i have the wrong .xcf file ..
would anyone be so kind as to tarzip the files from boot.fs for me?
ive been searching for a bsd machine that has a floppy for ages now!
c.
Henry B. Hotz
>i think i might have the right way of entering the boot device, but maybe
>i have the wrong .xcf file ..
>
>would anyone be so kind as to tarzip the files from boot.fs for me?
Actually the stuff is already available. Look in
<ftp://ftp.netbsd.org/pub/NetBSD/arch/macppc/snapshot/20000620-1.5/ins
tallation/>
There are only three files in the floppy image: bootxx, which is
useless, ofwboot.xcf, which is in that directory, and netbsd, called
netbsd.ram.gz in that directory. The last is a compressed kernel
which includes a built-in memory disk that includes the installboot
program.
Bootxx is only useful if installed directly on the target disk by
that program. I suspect that any other files you might want from the
floppy image are actually inside that memory disk image inside the
kernel. If you actually need them then it would be easier to extract
them from the main distribution tarballs.
Most likely what you want is a way to load ofwboot.xcf so it can load
netbsd.ram.gz. If you have a way to do that then you hopefully can
use a similar method to have ofwboot.xcf load the real /netbsd kernel
on your real target installation.
charlie allom
a rather friendly queenslander helped me out last night on #netbsd ;)
i might try that scsi HDD trick, with the snapshot files.. i should have
enought stuff to play with for the next few days.
everyone seems to be talking about OF right now, and it's all helpful,
seeing where othjers go wrong as well. =)
cheers.
Bill Studenmund
> At 12:21 AM -0400 7/17/00, charlie allom wrote:
>
> >i read somewhere that for OF 2.0.1 i should be using 'alias:partition' and
> >skip the file name (ofwboot.xcf)
>
> This is true if you have used the installboot program to wipe out the
> Apple partition map on the drive and install the bootxx program.
> This process doesn't work on new Mac's where a partition of 0 means
> the first understandable filesystem partition. On older Mac's (like
> the 3400 I presume) partition 0 means load the boot blocks.
That's not what I understood. AFAIK the meaning of partition 0 hasn't
changed - the system will still boot off of a bootable (driver) partition.
The problem as I understood it was that the definition of a bootable
driver partition changed, and that our bootable driver partition doesn't
fit the new paradime,
Take care,
Bill
Henry B. Hotz
I'd trust your understanding more than mine.
However I'm sure I've heard that you can now (G4) just put
ofwboot.elf on a regular HFS partition and boot it where in OF 1.0.5
that would not work. So there has been a change of some kind.
There is an explicit check in ofwboot (or was that bootxx) for the OF
version and if it's >= 3 then it strips off the partition number from
the boot device. If it's less then it explicitly puts a :0 onto it
IIRC. At least one of those two anyway.
Bill Studenmund
> I'd trust your understanding more than mine.
>
> However I'm sure I've heard that you can now (G4) just put
> ofwboot.elf on a regular HFS partition and boot it where in OF 1.0.5
> that would not work. So there has been a change of some kind.
I think that would always work (though xcoff, not elf). We just didn't
want to have to use a boot partition we didn't support, and which wouldn't
be root. We wanted the /netbsd once you're up and running (the one in your
root partition) to be the one you used to boot.
> There is an explicit check in ofwboot (or was that bootxx) for the OF
> version and if it's >= 3 then it strips off the partition number from
> the boot device. If it's less then it explicitly puts a :0 onto it
> IIRC. At least one of those two anyway.
I'm very unsure about that code. I don't think we really handle partitions
at all well in ofwboot.
Take care,
Bill
Henry B. Hotz
a 1-line EMACS editor. You get out with c-x,c-c. C-n, c-p, c-k seem
to do what you would expect.
How do you save your changes so they stick through a power cycle? (I
don't mean a MacOS boot, just a normal power cycle.)
Alternatively, how do I insert a new-line into nvramrc inside boot variables?
Background:
I've demonstrated that if I use system disk I always get a "no active
package" error followed by a crash while loading the netbsd kernel
from ofwboot. If I turn off nvramrc then the machine boots normally
but I have all the problems people know about with OF 1.0.5 (unstable
screen initialization, and can't boot directly from disk on
power-up). This seems to be true with the patches that boot
variables puts (leaves?) in nvramrc as well, but at least it has a
user interface to edit the contents, sort-of.
Parag Patel
>
>How do you save your changes so they stick through a power cycle? (I
>don't mean a MacOS boot, just a normal power cycle.)
After getting out with Control-C (just Control-C), type "nvstore" at the
ok prompt. Believe it or not, an emacs-style editor is required by
IEEE-1275. Silly me, I made SmartFirmware's full-screen before
catching on to the one-line approach. :)
Some other commands that are useful include "nvquit" to discard the
contents of the edit buffer, "nvrun" to execute the buffer, "nvalias"
and "nvunalias" to automatically add/remove device aliases from nvramrc.
Hope this helps.
-- Parag Patel
Henry B. Hotz
>Hope this helps.
Enormously.
Thanks!
Now if I can just figure out what needs to be changed to make it work. . .
Henry B. Hotz
to have gotten things working.
What I did was delete everything from nvramrc. Then I put in two
lines from system disk which may or may not be needed, harmful, or
who knows. I don't know forth. The lines are:
hex
: $E device-end ;
Then I put in both of the patches on our web page: the video
settling time one and the wBoot delay one.
I have load-base set to 6C0000, boot-command to wBoot, boot-device to
scsi-int/sd@0:0, boot-file to netbsd, use-nvramrc? to true,
auto-boot? to true.
I've power cycled the machine a couple of times and it comes up into
NetBSD properly. The screen still looks like hell around the edges,
but the screen patch never did seem to fix that all the way for me,
and I want this as a server anyway.
Now I suppose I have to ruin all this stuff in order to get back into
MacOS so I can set the reboot after power failure bit in the power
controller. <*sigh*>