Booting, next round ;-)
Martin Husemann
my mac 4400/200. It has OF 2.0.2 and internal IDE disk and atapi CD.
I would prefer to boot this machine over the network (I have other NetBSD
machines which could serve it), best case would be pressing "N" when turning
it on to netboot NetBSD and doing nothing to drop into MacOS.
But I would take any method that gets NetBSD up at all.
What I tried was: put the boot.fs from the latest snapshot onto a disk and
boot that via
boot fd:0
This resulted in the "CLAIM failed" error described in the FAQ; trying it
again did not help. Then I created a DOS floppy with ofwboot.xcf, ofwboot.elf
and netbsd.gz on it. And tried
boot fd:1,ofwboot.xcf
This successfully loaded ofwboot, which tried to read "netbsd" and failed
(obviously, it wouldn't fit on the disk). So at the "Boot:" prompt I entered
Boot: netbsd.gz
but that didn't work too:
/netbsd.gz: File not found
/fd/netbsd.gz: File not found.
I tried any combination of path names I could dream of and none worked.
So I tried booting from internal hard disk by putting ofwboot.xcf and
netbsd on the root of my hard disk. Tried to boot that via
boot hd:ofwboot.xcf
which resulted in the machine booting to MacOS.
Next try: boot from CD.
I downloaded the iso image from the ftp site and tried
boot cd:ofwboot.xcf
Same result as with harddisk.
I created my own CD, same result. I tried other names for the CD, like:
boot ata/atapi-disk@0:0,ofwboot.xcf
which was answered with:
bad partition number, using 0 no bootable HFS partition
Last try was network:
boot enet
didn't do anything (the DHCP server did not see any query).
In the meantime I learned how to use OF as a calculator - but I'd rather
run NetBSD on this machine ;-)
Any hints?
Martin
Martin Husemann
see if I can make any sense of this filename syntax game...
> Well, you'll need bootp before dhcp will do much good. Probably tftp
> would be good too. Check the diskless HOW-TO
> (http://www.netbsd.org/Documentation/network/netboot/), though I'm
> not sure how up to date it is. (The basic mechanics should be there,
> at least.)
Well, I'm netbooting other machines, so I think I'll manage that part. But
the FAQ is not quite clear: on one place it says "all machines support
netbooting", in some other place it says "Older machines don't".
Maybe it's just refering to the "N" key and I misunderstood it. I didn't
see anything looking like an ethernet card in dev / ls, but it worked from
MacOS (so I know it's there).
I'm confused by the dhcpd vs. bootp thing: IMHO dhcp is just the modern
version of bootp and dhcpd will answer bootp queries too. I'll do a tcpdump
and check, maybe the easy way is just a step away...
Martin
Henry B. Hotz
>What I tried was: put the boot.fs from the latest snapshot onto a disk and
>boot that via
>
> boot fd:0
You probably know this, but you did copy boot.fs with SunTar right?
I have had good luck with the dated images. I think the February one
is what I'm using now.
>This resulted in the "CLAIM failed" error described in the FAQ; trying it
>again did not help. Then I created a DOS floppy with ofwboot.xcf, ofwboot.elf
>and netbsd.gz on it. And tried
>
> boot fd:1,ofwboot.xcf
>
>This successfully loaded ofwboot, which tried to read "netbsd" and failed
>(obviously, it wouldn't fit on the disk). So at the "Boot:" prompt I entered
>
> Boot: netbsd.gz
>
>but that didn't work too:
Try boot "fd:1,ofwboot.xcf -a" so it gets to the prompt before
getting any errors. Then you can enter netbsd.gz with no leading /.
I'm suspicious that OF doesn't clean up properly after errors, and
that there may be bugs in the filesystem code that might trace
through directory trees.
Also there's no use having ofwboot.elf on the disk if you need to use
the .xcf version.
>Last try was network:
>
> boot enet
>
>didn't do anything (the DHCP server did not see any query).
I presume you saw the netbooting HowTo.
>In the meantime I learned how to use OF as a calculator - but I'd rather
>run NetBSD on this machine ;-)
I've certainly had fun with OF. You can dev to various nodes in the
device tree and try .properties and words to see what's there.
Doesn't tell you how to actually use the defined words though.
Good luck.
Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h.b....@jpl.nasa.gov, or hbh...@oxy.edu
Henry B. Hotz
>Thanks for your hints, I'll have to dig through the OF docs at apple and
>see if I can make any sense of this filename syntax game...
>
> > Well, you'll need bootp before dhcp will do much good. Probably tftp
> > would be good too. Check the diskless HOW-TO
> > (http://www.netbsd.org/Documentation/network/netboot/), though I'm
> > not sure how up to date it is. (The basic mechanics should be there,
> > at least.)
>
>Well, I'm netbooting other machines, so I think I'll manage that part. But
>the FAQ is not quite clear: on one place it says "all machines support
>netbooting", in some other place it says "Older machines don't".
>Maybe it's just refering to the "N" key and I misunderstood it. I didn't
>see anything looking like an ethernet card in dev / ls, but it worked from
>MacOS (so I know it's there).
I think that may be the case. Even OF 1.0.5 macs have an enet
devalias and will try to do something when you type 'boot enet:'.
Now is your ethernet on the motherboard? If not it needs to be a
card with OF support in its prom or you're out of luck for booting.
Martin Husemann
No, "dd" on a NetBSD/i386 machine :-)
> Try boot "fd:1,ofwboot.xcf -a" so it gets to the prompt before
> getting any errors. Then you can enter netbsd.gz with no leading /.
> I'm suspicious that OF doesn't clean up properly after errors, and
> that there may be bugs in the filesystem code that might trace
> through directory trees.
That's a good think to try tomorrow as first thing when I enter the buero.
Thank's for your advise!
Martin
Martin Husemann
> card with OF support in its prom or you're out of luck for booting.
Never opened that case, yet. I guess it's not on the mainboard, so I'd be
out of luck here. I see dev / ls list two unspecified PCI devices, have
to look those up in sys/dev/pcidevs.
Martin
Bill Studenmund
> Thanks for your hints, I'll have to dig through the OF docs at apple and
> see if I can make any sense of this filename syntax game...
Note the syntax kinda changed between versions.
> Well, I'm netbooting other machines, so I think I'll manage that part. But
> the FAQ is not quite clear: on one place it says "all machines support
> netbooting", in some other place it says "Older machines don't".
> Maybe it's just refering to the "N" key and I misunderstood it. I didn't
> see anything looking like an ethernet card in dev / ls, but it worked from
> MacOS (so I know it's there).
I think the older ones support net booting, but not "N" as a way to
netboot. Also, the older machines need XCOFF versions of ofwboot, which
1.5 is the first release to include.
> I'm confused by the dhcpd vs. bootp thing: IMHO dhcp is just the modern
> version of bootp and dhcpd will answer bootp queries too. I'll do a tcpdump
> and check, maybe the easy way is just a step away...
Check if you have an enet alias. You mentioned that the ethernet card
might not be on the motherboard.
Here's my dhcpd.conf from the i386 which is the dhcpd server:
option arp-cache-timeout 300;
subnet 10.0.0.0 netmask 255.255.0.0 {
option routers 10.0.0.1;
option domain-name-servers 10.0.0.1;
option domain-name "home-net.something-special.net";
range dynamic-bootp 10.0.0.100 10.0.0.119;
}
host tanis {
fixed-address 10.0.0.2;
hardware ethernet 00:05:02:4e:49:3d;
filename "ofwboot.xcf";
next-server 10.0.0.1;
server-name "10.0.0.1";
option root-path "/y5/mount";
option host-name "tanis";
}
I'll probably renumber the internal net soon. :-) Oh, and that is of
course not the real domain-name. Bit I'm running dns on the gateway
machine, and have local DNS for the home machines.
I'm not sure if all of the variables are needed.
Take care,
Bill