Gaudenz Steinlin wrote:


Unfortunately I was unable to actually achieve the installation, because yaboot.conf can't be written -- sid the error message. It's perhaps due to my 800k bootstrap partition non being HFS formatted.


parse error :-) What is the exact error message of yaboot-installer.

It's as I said: non HFS formatted

But I have some news that can help:

-1- I was able to chroot to the just installed / partition.

chroot /target /bin/bash
mount -t proc proc /proc


-2- Then I ran ofpath /dev/sda6 and the answer was clear: SBP-2 unsupported.


So the culprit is clearly ofpath lacking fw support.

However I was able to setup my bootstrap partition by manually supplying OF path with this command:

-3- mkofboot -b /dev/sda4 -o ed0:4

( ed0 is my short OF path name, actually it is a permanent devalias I made in OF to save huge amount of typing and typing errors )

At least d-i should let experts supply OF path when problems arise.

-4- Now I boot fine from my bootstrap partition.

But it's not the end of the story:

-1- I don't know how to resume d-i after this second manual setting.
-2- I don't know what should be yaboot.conf at the end of d-i process to ensure success of second-stage install
-3- Worse: the vmlinux kernel just installed is not as the one of d-i : it relies on modules to support ieee1394
-4- So there is a classical chicken-egg issue, normally solved by initrd.
-5- I can't go further, because I can't hack initrd=root.bin: both systems lack the loop support that I'd need to customize inird, and I'm not able to handle ext2 disk images from within MacOS X.


That's all

Merci, DankeschÃne.

---





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to