o2 boot problem. Newbie ... I think I broke it :(
#1
o2 boot problem. Newbie ... I think I broke it :(
Hello lovely Irix people. I was a user if Irix 25+ years ago, working in VFX. I have an o2 which I dug out of the loft. It is to be used in a youtube video showing of some software that I haven't seen any video of. Anyways.... 

I was so close. 
I managed to get irix booting and all the software all working fine. I wanted to change the network settings in order to get some footage on the machine. I changed two things
1. network IP address (to one that would work on my local network)
2. I changed the exportfs file. I commented out a line as it seemed to point to an empty folder
On rebooting to take the new IP I get:

----
Unable to execute ==pci(0)scsi(0)disk(1)rdisk(0)partition(8)/der==sash: no such device
Unable to load boot file: no such device

Unable to boot; press any key to continue
----

hinv returns:
----
System: IP32
Processor: 300 Mhz R5000, with FPU
Primary I-cache size: 32 kbytes
Primary D-cache size: 32 kbytes
Secondary cache size: 1024 kbytes
Memory size: 256 Mbytes
Graphics: CRM, Rev C
Audio: A3 version 1
SCSI Disk: scsi(0)disk(1)
SCAI CDROM: scsi(0)cdrom(4)
----

printenv returns:
----
Autoload=yes
console=g
diskless=0
dbaud=9600
volume=80
sgilogo=y
TimeZone=PST8PDT
netaddr=192.168.86.84
monitor==h
SystemPartition===pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=n==pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadFilename=me==/unix
OSLoader=der==sash
crt_option=tion==1
ConsoleOut=video()
ConsoleIn=keyboard()
cpufreq=300
eaddr=08:00:69:0a:8a:6e
gfx=alive
videostatus=illegal_env_var
kername=[A[A[A[B
-----


Is my hard drive dead? Or did I break something.   Thanks in advance 

Andy T
theonlyandyt
O2

Trade Count: (0)
Posts: 4
Threads: 1
Joined: Dec 2022
Location: London
Find Reply
12-03-2022, 04:04 PM
#2
RE: o2 boot problem. Newbie ... I think I broke it :(
Some env variables seem to have wrong names/values:

monitor==h
SystemPartition===pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=n==pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadFilename=me==/unix
OSLoader=der==sash
crt_option=tion==1

Try changing them:

monitor=h
SystemPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadFilename=/unix
OSLoader=sash
crt_option=1

Good luck!
TruHobbyist
Developer

Trade Count: (0)
Posts: 195
Threads: 21
Joined: May 2018
Find Reply
12-03-2022, 04:33 PM
#3
RE: o2 boot problem. Newbie ... I think I broke it :(
(12-03-2022, 04:33 PM)TruHobbyist Wrote:  Hay TruHobbyist, thanks for the reply.   Do you know how do I change these variables? 
theonlyandyt
O2

Trade Count: (0)
Posts: 4
Threads: 1
Joined: Dec 2022
Location: London
Find Reply
12-03-2022, 06:58 PM
#4
RE: o2 boot problem. Newbie ... I think I broke it :(
Use setenv to change these variables:

setenv monitor h

You can also enter the command 'help' (without the quotes) at the PROM command monitor for more help on commands.
TruHobbyist
Developer

Trade Count: (0)
Posts: 195
Threads: 21
Joined: May 2018
Find Reply
12-03-2022, 07:17 PM
#5
RE: o2 boot problem. Newbie ... I think I broke it :(
Sorry fir the late reply. As Christmas approaches, time just disappears. Thanks for you insight. I have managed to fix the env variables. But unfortunately I still can't boot as I get a different error. 

Autoboot failed
pci(0)scsi(0)disk(1)rdisk(0)partition(8)/unix no such file or directory

So now....
printenv returns:


----

Autoload=yes

console=g

diskless=0

dbaud=9600

volume=80

sgilogo=y

TimeZone=PST8PDT

netaddr=192.168.86.84

monitor=h

SystemPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)

OSLoadPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)

OSLoadFilename=/unix

OSLoader=sash

crt_option=1

ConsoleOut=video()

ConsoleIn=keyboard()

cpufreq=300

eaddr=08:00:69:0a:8a:6e

gfx=alive
videostatus=illegal_env_var
----

which I think is all correct but.. I think it's missing a "kername"
any idea what that variable should be set to?
theonlyandyt
O2

Trade Count: (0)
Posts: 4
Threads: 1
Joined: Dec 2022
Location: London
Find Reply
12-12-2022, 12:50 PM
#6
RE: o2 boot problem. Newbie ... I think I broke it :(
partition(8) is the volume header: the OS loader sash lives there, but the kernel unix does not. It lives in the root partition (0).

SystemPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)
is correct, but OSLoadPartition should be
OSLoadPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(0)

you can simply run 'ls' from the PROM command line and you will see that /unix is not in partition(8).

You don't need to set kernname, it is automatically set by sash.

Personaliris O2 Indigo2 R10000/IMPACT Indigo2 R10000/IMPACT Indigo2 Indy   (past: 4D70GT)
robespierre
refector peritus

Trade Count: (0)
Posts: 640
Threads: 3
Joined: Nov 2020
Location: Massholium
Find Reply
12-12-2022, 05:29 PM
#7
RE: o2 boot problem. Newbie ... I think I broke it :(
(12-12-2022, 05:29 PM)theonlyandyt Wrote:  Hooray. Thanks Robespierre, that did the trick. Also thank you TruHobbyist. Now I have my old baby back.

Merry Christmas all

Smile
theonlyandyt
O2

Trade Count: (0)
Posts: 4
Threads: 1
Joined: Dec 2022
Location: London
Find Reply
12-18-2022, 06:51 PM


Forum Jump:


Users browsing this thread: 1 Guest(s)