On Jun 11 19:54:21, Miod Vallat wrote:
> > I understand that "hd" and "cd" are just devaliases; in my case,
> >
> > hd /pci@f4000000/ata-6@d/disk@0
> > cd /pci@f4000000/ata-6@d/disk@1
> >
> > Does that mean that those device aliases are somehow mixed up?
>
> Well, given the dmesg says...
>
> > cd0 at scsibus0 targ 0 lun 0: <MATSHITA, DVD-R UJ-825, DAND> ATAPI 5/cdrom
> > removable
> > wd0 at wdc1 channel 0 drive 1: <ST9808211A>
>
>
> ... I'd say they are.
>
> > Obviously, I would like to boot the /bsd I installed on disk.
> > Isuppose this is an Open Firmware problem rather then an OpenBSD
> > problem. Namely, Idon't know how to address the harddisk I installed
> > on from within open firmware. Can someone enlighten me please?
>
> Try:
> setenv boot-device /pci@f4000000/ata-6@d/disk@1:,ofwboot
setenv boot-device /pci@f4000000/ata-6@d/disk@1:,ofwboot
boot
MAC-PARTS: bad partition can't OPEN: /pci@f4000000/ata-6@d/disk@1:,ofwboot
Can't open device or file.
According to devalias, the above cevice is aliased to 'cd'.
So running this is equivalent to running
boot cd:,ofwboot
- right? It fails the same way.
I guess I need to understand how the ofwboot works.
This is my first ppc machine, so please bare with me.
During the installation, when I select MBR partitioning,
two partitions get created: a 1MB DOS partitition at the
beginning of the disk, and one big OpenBSD coverning the rest.
What is the role of this MSDOS partition? It is flagged bootable in fdisk
- is that intended? Is this where the 'ofwboot' file is supposed to be found?
It doesn't seem to really be an msdos partition: I cannot fsck_msdos it
or mount_msdos it. Could this be my problem?
Thank you for your time
Jan
