Re: New World G4 installation (next)
> > Hello,
>>
>> I'm sorry to ask so silly question on the list for booting Linux. I hope
>> this is the last time for the installatin process.
>>
>> I've now the possibility to choose Linux in the choices proposed when I
>> keep the key "alt" pressed during startup.
>
>Very likely, it will preswent the menu without the need to hold the
>alt/option key.
For the moment, yaboot doesn't let me any choice, it try to start and stop when it doesn't find the kernel.
>
>> For doing that , I used :
>>
>> mkofboot --boot /dev/hdb2 -m/usr/lib/yaboot/ofboot --root /dev/hdb14
>--partition 14
>>
>> when I fall in Yaboot, it is looking for the image (the vmlinux file). it
>writes :
>>
>> boot: <NULL>
>> Loading kernel:...
>> Image not found... try again
>> boot:
>>
>> I tried to give the vmlinux path with --image option in mkofboot. As I see
>> that vmlinux was in /target/, il put --image /target/vmlinux. But nothing
>> better happened.
>>
>
>I think there are 2 issues.
>
>#1, /target/ is the path within the install program _only_. Linux mounts all
>volumes within one directory structure, and within the installer your root
>directory is actually a RAM disk. /target is where the system you are
>installing is mounted, within that RAM disk directory structure, for the
>duration of the installation. But when you want to actually boot into your
>new installation, there will be no more /target because your new
>installation will be the root of the directory structure.
>
>So, everything under /target under the installation system is under just /
>in your newly installed system.
>
>#2, I don't think the symlink /vmlinux which is placed in your new system by
>the installer is recognized by the bootloader. That is probably a bug which
>should be fixed. In any case, I and others have had success by editing the
>yaboot.conf and making the image=/boot/vmlinux-2.2.19. You might also get
>the same results by including the same --image= option in your mkofboot
>command. (it works because that's the actual kernel location and name for
>the Debian 2.2r3 installation).
All that you say here seems logical and correct. But unfortunately, I don't manage to find a good solution.
I'v found that the path of my kernel was : /boot/vmlinux-2.2.18pre21 (perhaps that I haven't the last version). The logical link "vmlinux" points to the right pass.
I tried to add --image option, I tried to give boot path when prompted by yaboot... it never find it. I now understand why Benjamin Kite put the kernel on the bootstrap partition. I don't want to do such special things. So does anyone has another experience that can help me for this problem ?
Alain Paschoud
Reply to: