[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: silo error code



Hi
Thank you for the answer
What do you exactly mean for "valid initrd images for each kernel"?
They have been generated automatically during new kernel upgrade, I didn't play with them, how can I check? By the way the older 2.6.26 wasn't working too, I got the same silo error.
Here is the content of my /boot, if it can help:

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    71962 16 gen 19.49 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 2011 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 10656009 29 gen 15.10 initrd.img-2.6.32-5-sparc64
lrwxrwxrwx 1 root root 27 9 lug 2011 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  2011 second.b
-rw-r--r-- 1 root root      287 10 lug  2011 silo.conf
-rw-r--r-- 1 root root      262 10 lug  2011 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  1447232 16 gen 19.49 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 2011 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  2200963 16 gen 19.48 vmlinuz-2.6.32-5-sparc64
lrwxrwxrwx 1 root root 24 9 lug 2011 vmlinuz.old -> vmlinuz-2.6.18-6-sparc64


I'm a newbie in sparc, and I really don't know why the newest kernels aren't working. I'm pretty sure a new complete installation of squeeze would work, with kernel 2.6.32 too, but so far I can't, because the ultra is running several services and a new installation would be painful.
Thanks
urodelo


On Sun, 26 Feb 2012 18:06:11 +0100, Patrick Baggett <baggett.patrick@gmail.com> wrote:

I have an Ultra 10 using the "testing" repo and I've got Linux 3.2.0 on it
and it works fine. I also was able to get 2.6.32 to work fine from the
repo...not really sure what to tell you. Are you sure the initrd images are
valid for each kernel?

Patrick

On Sun, Feb 26, 2012 at 8:28 AM, urodelo <urodelomutante@yahoo.com> wrote:

Hello
On my sparc ultra 10 with squeeze, when I boot kernel 2.6.32 (the latest
in the repo) silo prompt shows the error code SI . If I boot old 2.6.18 it
boots fine.
What does exactly mean that silo error? How can I solve this problem?

My system has separate /boot 93MB
/ is mounted on /dev/mapper/foobar_vg-root_vl (I use raid + lvm)
etc etc...

silo.conf:

root=/dev/mapper/foobar_vg-**root_vl
partition=1
default=LinuxOLD
read-only
timeout=100
append="mem=512m"
#append="rootdelay=20"

image=/vmlinuz
       label=Linux
       initrd=/initrd.img

image=/vmlinuz.old
       label=LinuxOLD
       initrd=/initrd.img.old


I'm trying to understand what has happened with the new kernel since a
long time, but I still haven't found the solution
Thanks
urodelo

--
用斯斯!


--
To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.**debian.org<debian-sparc-REQUEST@lists.debian.org>
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Archive: http://lists.debian.org/op.**waaiiaejc5w9q6@navi.nerv<[🔎] op.waaiiaejc5w9q6@navi.nerv">http://lists.debian.org/[🔎] op.waaiiaejc5w9q6@navi.nerv>




--
用斯斯!


Reply to: