Message-Id: <p05001900b93ed716623f@[192.168.1.2]> Date: Tue, 25 Jun 2002 19:32:33 -0700 From: John Koenig <jfkoenig@vipb.com> Subject: [suse-sparc] openboot, SILO issue
[pls excuse if this went to the list twice, I am receiving list traffic recently but seem to have missed this one message (mine!)... (maybe because the machine I am having this problem is also my mail server <grin>)
#####
Hi,
I have a nagging problem that I would love to find resolution for...
In openboot on a Ultra 10, I watch the auto-boot mechanism proceed after the ram check and fail with a message:
+-----------
| ok Boot device: /pci@1f,4000/scsi/disk@0,0:c File and args:
| ok Trap 3e
| ok
|
+--
I check my openboot variables with printenv after a cold boot and they are:
boot-command = boot linux
auto-boot? = true
boot-device = linux
And I have a devalias such that
linux /pci@1f,4000/scsi/disk@0,0:c
##
Why after getting the Trap 3e can I manually type: "boot linux"
+--
| ok
| ok boot linux
| ok Boot device: /pci@1f,4000/scsi/disk@0,0:c File and args:
| ok SILO
|
| LINUX BOOTS!
+-----------
ok boot linux
and everything works?
#####
Can anyone help me not autoboot successfully instead of the
error string "Trap 3e" ?
:)
thx
J
PS: So maybe I should just rely on a boot floppy?
PPS: My patitions look like this:
/dev/sda4 7690488 4400304 2899524 61% /
/dev/sda1 47409 4126 40835 10% /boot
shmfs 65112 0 65112 0% /dev/shm
and of course since this is a Sun Labelled SCSI disk sda3 is the "whole disk" access point, so to speak. Anybody know the correct semantics to describe that?
-- To unsubscribe, e-mail: suse-sparc-unsubscribe@suse.com For additional commands, e-mail: suse-sparc-help@suse.com
This archive was generated by hypermail 2.1.0 : Wed Jun 26 2002 - 04:33:45 CEST