silo and new kernel issue in lenny & squeeze
Hello list!
This is my first post, although I follow the discussions here since some time already.
First at al, I'm a sparc noob.
I own an Ultra10 where I've installed somehow Etch with installation cd some years ago (kernel 2.6.18). Then I've upgraded to lenny and than to Squeeze. Both releases with a new kernel, Squeeze provides the 2.6.32.
Well, since my first upgrade to Lenny, I've never been able to run a new kernel, only the old 2.6.18 works. I've upgraded the kernel during the upgrade of debian, and silo.conf has been automatically modified to load the new kernel (some years ago the one of lenny, some months ago the one of squeeze). When I boot the ultra10 with a new kernel, for ex 2.6.32, openboot loads, than at the prompt should appear SILO, but what I get is SI and nothing more. As I've told before, with old 2.6.18, it works (by the way, is there a way to chose the kernel to boot among those available in silo.conf, in a way similar to that of grub - lilo?)
Now I think that silo can't load the second stage of the kernel, but I'm not sure about this. I don't know how to solve this problem which now is even worse because without kernel 2.6.32 the new udev does not work too!
My Ultra 10 has 2 ide hd, primary and secondary masters, cdrom on sec slave; it's configured with a separate boot partition on hda1 (yes, I use the old good way!), and then a sw raid 1 with 1 logical group and 3 logical volumes: the first lv is for root partition, the second for /var and the third for /home
Here's my silo.conf:
root=/dev/mapper/myvolumegrp_vg-root_lv
partition=1
default=LinuxOLD
read-only
timeout=100
#append="video=atyfb:off mem=512m rootdelay=15"
append="mem=512m"
#append="rootdelay=20"
image=/vmlinuz
label=Linux
initrd=/initrd.img
image=/vmlinuz.old
label=LinuxOLD
initrd=/initrd.img.old
The content of /boot:
lrwxrwxrwx 1 root root 1 24 ago 2008 boot -> .
-rw-r--r-- 1 root root 43670 5 mag 2009 config-2.6.18-6-sparc64
-rw-r--r-- 1 root root 56854 13 giu 18.49 config-2.6.26-2-sparc64
-rw-r--r-- 1 root root 71962 14 giu 16.04 config-2.6.32-5-sparc64
lrwxrwxrwx 1 root root 1 24 ago 2008 etc -> .
-rw-r--r-- 1 root root 1024 26 ago 2010 fd.b
-rw-r--r-- 1 root root 512 26 ago 2010 first.b
-rw-r--r-- 1 root root 1024 26 ago 2010 generic.b
-rw-r--r-- 1 root root 692 26 ago 2010 ieee32.b
lrwxrwxrwx 1 root root 27 9 lug 16.09 initrd.img -> initrd.img-2.6.32-5-sparc64
-rw-r--r-- 1 root root 6309396 29 set 2009 initrd.img-2.6.18-6-sparc64
-rw-r--r-- 1 root root 6309670 8 ago 2009 initrd.img-2.6.18-6-sparc64.bak
-rw-r--r-- 1 root root 7443312 19 giu 15.22 initrd.img-2.6.26-2-sparc64
-rw-r--r-- 1 root root 10628547 9 lug 16.58 initrd.img-2.6.32-5-sparc64
lrwxrwxrwx 1 root root 27 9 lug 16.58 initrd.img.old -> initrd.img-2.6.18-6-sparc64
-rw-r--r-- 1 root root 7704 26 ago 2010 isofs.b
drwx------ 2 root root 12288 24 ago 2008 lost+found
-rw-r--r-- 1 root root 7680 24 ago 2008 old.b
-rw-r--r-- 1 root root 78336 10 lug 16.40 second.b
-rw-r--r-- 1 root root 287 10 lug 17.10 silo.conf
-rw-r--r-- 1 root root 262 10 lug 12.02 silo.conf.copia
-rw-r--r-- 1 root root 76387 26 ago 2010 silotftp.b
-rw-r--r-- 1 root root 886778 5 mag 2009 System.map-2.6.18-6-sparc64
-rw-r--r-- 1 root root 1106679 13 giu 21.11 System.map-2.6.26-2-sparc64
-rw-r--r-- 1 root root 1444949 14 giu 16.04 System.map-2.6.32-5-sparc64
-rw-r--r-- 1 root root 512 26 ago 2010 ultra.b
lrwxrwxrwx 1 root root 24 9 lug 16.09 vmlinuz -> vmlinuz-2.6.32-5-sparc64
-rw-r--r-- 1 root root 1482166 5 mag 2009 vmlinuz-2.6.18-6-sparc64
-rw-r--r-- 1 root root 1728006 13 giu 21.11 vmlinuz-2.6.26-2-sparc64
-rw-r--r-- 1 root root 2200826 14 giu 16.03 vmlinuz-2.6.32-5-sparc64
lrwxrwxrwx 1 root root 24 9 lug 16.57 vmlinuz.old -> vmlinuz-2.6.18-6-sparc64
Then I would like to ask you for help to solve this issue which is quite serious for me, assuming that my ultra10 runs several services, and every downtime to reset the old setup causes me a gastritis. I'm pretty sure that because I'm a sparc noob I'm missing something in the boot process. I've red some (old) documentation about it, but didn't find a solution.
Thank you for the help
urodelo
Reply to: