Contents of /boot and /etc/yaboot.conf
Here's the yaboot.conf:
## yaboot.conf generated by debian-installer
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
boot=/dev/hda2
device=/pci@80000000/mac-io@10/ide@20000/disk@0:
partition=4
root=/dev/hda4
timeout=100
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
enablecdboot
image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
image=/boot/vmlinux.old
label=old
read-only
initrd=/boot/initrd.img.old
And /boot. Notice that there's no initrd.img symlink. I thought there was earlier, but I was obviously mistaken.
drwxr-xr-x 2 root root 4096 2005-01-20 03:23 .
drwxr-xr-x 22 root root 4096 2004-12-16 01:07 ..
-rw-r--r-- 1 root root 39983 2005-01-18 23:32 config-2.6.8-20050118
-rw-r--r-- 1 root root 40069 2004-10-03 07:15 config-2.6.8-powerpc
-rw-r--r-- 1 root root 1024 2004-10-28 13:46 first.b
-rw-r--r-- 1 root root 4800512 2004-12-16 01:44 initrd.img-2.6.8-powerpc
lrwxrwxrwx 1 root root 24 2005-01-20 03:23 initrd.img.old -> initrd.img-2.6.8-powerpc
-rw-r--r-- 1 root root 44336 2004-10-28 13:46 second.b
-rw-r--r-- 1 root root 944303 2005-01-19 03:48 System.map-2.6.8-20050118
-rw-r--r-- 1 root root 942649 2004-10-03 08:13 System.map-2.6.8-powerpc
lrwxr-xr-x 1 root root 22 2005-01-19 18:51 vmlinux -> vmlinux-2.6.8-20050118
-rw-r--r-- 1 root root 3966579 2005-01-19 03:48 vmlinux-2.6.8-20050118
-rw-r--r-- 1 root root 3964695 2004-10-03 08:13 vmlinux-2.6.8-powerpc
-rw-r--r-- 1 root root 1290162 2005-01-19 03:48 vmlinux.coff-2.6.8-20050118
lrwxr-xr-x 1 root root 21 2004-12-16 01:44 vmlinux.old -> vmlinux-2.6.8-powerpc
This is the only difference in kernel config:
chrisd@blueberry:/boot$ diff config-2.6.8-20050118 config-2.6.8-powerpc
314a315
> # CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
321a323
> # CONFIG_AIC79XX_BUILD_FIRMWARE is not set
So I don't quite understand why an initrd image wasn't created, nor how I can create one myself to get my new kernel booting. Any suggestions?
Reply to: