Morning all
Success! Yee ha!
Early stages however I am VERY pleased to report I have managed to get
this PE1950 to boot.
I will publish the full configuration details and a copy of working
kernel as soon as I have everything tabulated and sorted out. However
for those who want to move forward and don't want to wait here is the
fix.....
I tried to use YAIRD on my spare development PC to generate the
initrd.img. I copied it to the PE and booted however it died as it was
looking for an IDE drive! Gave up on that idea.
I then rescue booted the PE using Etch 2.6.8
Go through menu till the drives are selected (mine were partitioned and
the system installed previously )
F2 to new shell
mkdir /target mount /dev/sda1 /target chroot /target mount
/sys mount /proc
Deleted the initrd.img files in /boot
added ...........
ramdisk = /usr/sbin/mkinitrd.yaird into kernel-img.conf
cd /boot
:/~# yaird /boot/initrd.img-2.6.15-1-486 2.4.15-1-486
All being well you should get a new initrd.img-2.6.15-1-486
Reboot
The plan is from here on to get a fully customised PE 2.6.1* kernel
working (I have 2.6.15 going so this is a good place to start)
I found a lot of stuff whilst researching this and will publish the
main bits later. However the breakthrough was the following: Huge thanks
to Arnau and Florian for the tip.
http://lists.us.dell.com/pipermail/linux-poweredge/2006-February/024823.html
> Sometimes it helps to use mkinitrd.yaird to build the initrd (instead of
> the default mkinitrd). You can try to install the package "yaird" and
> put the following line in /etc/kernel-img.conf:
>
> ramdisk = /usr/sbin/mkinitrd.yaird
>
> (see "man mkinitrd.yaird")
>
> Then do a dpkg-reconfigure of your linux-image-2.6.15-xxx and see if
> that gives you a working initrd.
>
> Regards,
> Florian
>
>
I hope this will help somebody.
--
Arnau
_______________________________________________
yoper-dev mailing list
[email protected]
https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
