On 12/09/14 08:10, patrick keshishian wrote:
Hi,

I must be doing something wrong here and need some hints
to figure out what.

My attempts to burn macppc install56.iso to a CD seems to
produce un-bootable discs. I'm using cdrecord(1) to perform
the burns.

At the Open Firmware prompt I issue:

0 > boot cd:,ofwboot /5.6/macppc/bsd.rd

and that results in:

DISK-LABEL: read of block0 failed
ATAPI-DISK: open of DISK-LABEL failed can't OPEN: cd:,ofwboot
Can't open device or file
  ok
0 >

I went through four different burn attempts; one with Dec
7th snapshot. And three right now with Dec 8th one.

I tested with official 5.6 CD and that CD boots just fine.

This is how the image was burned to disc:

# cdrecord -v dev=/dev/rcd0c install56.iso
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent default
s.
Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd5.6) Copyright (C) 1995-2
[...]
BURN-Free is ON.
Turning BURN-Free off
Performing OPC...
Sending CUE sheet...
cdrecord: WARNING: Drive returns wrong startsec (0) using -150
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01:  218 of  218 MB written (fifo 100%) [buf  99%]  33.1x.
Track 01: Total bytes read/written: 228696064/228696064 (111668 sectors).
Writing  time:   75.670s
Average write speed  22.3x.
Min drive buffer fill was 97%
Fixating...
Fixating time:    3.591s
cdrecord: fifo had 3723 puts and 3723 gets.
cdrecord: fifo was 0 times empty and 1843 times full, min fill was 95%.
# echo $?
0

Note the "WARNING".

Also note that burning an amd64 image works just fine
(with same "WARNING" during cdrecord phase).

On a related note, how can base tools (cdio(1)?) be used
instead of cdrecord(1) (from ports) to burn these images
to disc?

Thanks in advance,
--patrick


Hi,

What happens when you hold the 'c' key during reboot?

If you mount the disks under a working system is ofwboot in the / ?

hth

Fred

Reply via email to