On Jun 12 22:20:16, Otto Moerbeek wrote:
> On Tue, Jun 12, 2012 at 10:00:05PM +0200, Jan Stary wrote:
>
> > On Jun 12 21:27:18, Jan Stary wrote:
> > > On Jun 12 20:17:38, Jan Stary wrote:
> > > > > There is another problem now though:
> > > > > the booting sequence ends with
> > > > >
> > > > > bootpath /pci@f4000000/ata-6@d/disk@1:/bsd
> > > > > root device: _
> > > > >
> > > > > and that's where it stops, with '_' indicating the cursor.
> > > Also, I cannot actually type anything here.
> > >
> > > Could this be that the installed /bsd does not
> > > understand the DUID names in /etc/fstab?
> >
> > No, that's not it. I reinstalled yet again, using the old wd0.x
> > instead of DUIDs, but the boot of the installed /bsd fails
> > in the same way.
> >
> > > >
> > > > I can still boot from the cd, with
> > > >
> > > > boot /pci@f4000000/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd
> > > >
> > > > That boots fine, with the dmesg ending with
> > > >
> > > > bootpath /pci@f4000000/ata-6@d/disk@0:/5.1/macppc/bsd
> > > > root on wd0a (duid.a) swap on wd0b dump on wd0b
> >
> > What could be the difference between /5.1/macppc/bsd
> > that boots fine and the installed /bsd that fails as above?
> >
> > If I just copy /5.1/macppc/bsd to /bsd, it fails the same,
> > which puzzles me even more.
> >
> > The installed /bsd.rd boots fine - but that knows about
> > root being on rd0a in advance, right?
>
> If ofw is is confused about the paths the following two scenarios can
> happen:
>
> boot from cd: bsd gets an incorrect boot path from ofw that actually
> points to the hard disk, and (by acccident) you boot ok.
That's quite possibly what happens for me.
Thank you for the insight.
> boot from hd: bsd gets an incorrect boot path from ofw that points to
> nowhere, so you don;t boot ok.
Is there a way to unconfuse ofw and make it pass the right
boot path to the kernels it boots?
Not that I fully understand what a "bootpath" is.
The pre-last line of the dmesg of both my boot attempts
(from the CD, from the disk) seems to be the right path
to the kernel that is actually booting. It's the "root device"
where it gets stuck.
I guess I will need to learn more about ofw than I thought
I would need. Sigh, the horrors of macintosh.
> Now why you cannot type a boot path in response to the prompt I don't know.
It's like it doesn't even know about the keyboard being there.
Is that the booting kernel's problem, or is it an ofw problem?
Jan
