OK I re-installed suse 7.3 from a clean start to perform a clean kernel upgrade. Now 
even 7.3 won't boot this is my config

#etc/fstab
# I put the whole of / on /dev/sdb as /dev/sda is a small internal disk
/dev/sdb1       /       ext2    defaults 1 1
/dev/sda1       /boot ext2      defaults 1 2
/dev/cdrom      /media/cdrom auto (etc.)
devpts  /dev/pts        devpts defaults 0 0
/dev/fd0        /media/floppy auto (etc.)
proc            /proc   proc defaults 0 0
/dev/sda2       swap    swap pri=42 0 0

By default SILO is installed in the Master Boot Record

/boot contains
System.map-2.2.20       fd.b    cd.b    first.b ieee32.b
old.b   second.b        silo.conf       siloftp.b       ultra.b
vmlinuz vmlinuz.config  vmlinuz.suse

#silo.conf
partition = 1
read-only
image=/vmlinuz
        label = linux
        root = /dev/sdb1
image=/vmlinuz.suse
        label = suse
        root = /dev/sdb1


When I boot with no arguments the error message is
ok boot
Boot device: /iommu/sbus/espdma@f,400000/esp@f,80000/sd@3,0
Can't find boot device


I'm thinking there could be something wrong with the partitioning I chose. Any help 
appreciated

Eivan Cerasi

-----Original Message-----
From: Bart Schelstraete [mailto:[EMAIL PROTECTED]]
Sent: 16 January 2003 17:55
To: CERASI Eivan
Cc: '[EMAIL PROTECTED]'
Subject: Re: [suse-sparc] Kernel upgrade from 2.2.20 to 2.4.19


CERASI Eivan wrote:

>I installed Suse 7.3 on a Sparc10 with silo in the Master Boot Record as I only run 
>Linux.
>
>On /dev/sda my partitions are /boot and swap (small internal disk). I put the whole 
>root directory on an external disk /dev/sdb
>
>On Suse FTP site I found an RPM package for kernel 2.4.19 in 
>pub/people/kukuk/SPARC/kernel. I selected the default one as I don't use SMP 
>(reserved for multiple processor configs). I thought this procedure would be 
>straightforward rather than recompiling a 2.4.x kernel.
>
>After installing the package with package manager, I can't reboot. The sparc can't 
>find the boot device and SILO doesn't start-up.
>
>I rebooted from CD-ROM in rescue mode and was able to mount the partitions. 
>Everything looks OK. In /boot, silo.conf exists, a new vmlinuz is there and a 
>System-2.4.19.map file.
>
>Anybody come across this before ?
>  
>

Can you tell use the exact error message that you're receiving?


rgrds,

       Bart


____
 
This message and any files transmitted with it are legally privileged and intended for 
the sole use of the individual(s) or entity to whom they are addressed. If you are not 
the intended recipient, please notify the sender by reply and delete the message and 
any attachments from your system. Any unauthorised use or disclosure of the content of 
this message is strictly prohibited and may be unlawful.
 
Nothing in this e-mail message amounts to a contractual or legal commitment on the 
part of EUROCONTROL unless it is confirmed by appropriately signed hard copy.
 
Any views expressed in this message are those of the sender.


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to