On Sun, Mar 23, 2003 at 10:55:56PM +0100, tarak wrote:
Chris Tillman wrote:
On Sun, Mar 23, 2003 at 01:42:16PM +0100, tarak wrote:
...
done that... screen still stays black.
here's a little list of what i did:
- rebooted with the installation disks
- chrooted to /target
- mounted proc-filesystem
- brought up network with ifup
- downloaded the patched first.b-file for g3's as linked on section
8.1 in the
installation manual with wget
- backuped the old one and placed the new one to its apropriate place
- run quik -v at the shell
- got back to dbootstrap and made system bootable
This re-runs quik. Should be all right, though,
since you have the new first.b in place.
- got back to the chroot-shell to change nvsetenv-settings to:
boot-device /pci/mac-io/ata0/ata-disk@0:2
(my root device is indicated as /dev/hda2 by dbootstrap)
This all sounds good. Do you get the same path with
ofpath /dev/hda2
another thing that I found out reading through the netbsd-pages: it
seems that one
can only boot hfs-filesystems, iso's from cd-rom's, hfs-floppy's and
something called
partition-zero from OpenFirmware 2.0.1. i wonder if that might be
the problem, too?
partition-zero is the strategy quik uses: better known as the boot
block.
here's the url:
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6/macppc/INSTALL.html#Available%20Boot%20Media
dbootstrap has created ext2fs on /dev/hda2. i thought that if i
would place everything
on an hfs-filesystem it would boot correctly? because it does boot
the floppy. kind of
simulation of a startdisk on the hard-disk? just an idea...
That shouldn't be necessary. The boot block is written to the
disk, not the file system.
I don't think you can make a root partition on an hfs file system,
either; though I've never tried it.