many happy returns !
has anyone seen my console ?
The collected works of thermionic
Hi,
I'm trying to do a network install on a clean (ex PC) disk in a Fuel (from FreeBSD) using 6.5.30 from supportfolio, and the rest from base, copied (using IRIX) to disk, and the copied over to the FreeBSD box.
I do have the CDs, and I do have a working CD drive in the Fuel, and I can do a CD install without any problem at all (which is how I copied the contents of the CDs) however I'm trying to learn how to do a network install, I like doing "bare metal" network installs
On the FreeBSD box I've started with two directory trees setup in /usr /tftpboot with just fx.64, sa, unix.IP35 and uni_0004.ip3 and /sgi_os_software with all of the copies of teh CDs (full set of from 6.5.14, copies of the overlays from 6.5.22 and copies of the downloaded 6.5.30)
I've setup dhcp, tftp (with -s /usr/tftpboot) and rsh (bootp and dhcp don't actually seem to be needed if you set netaddr, netmask, and srvaddr in the PROM
I can boot fx.64 and partition the disk
I can then boot sash
I can also boot uni_0004.ip3
but, it then complains about there being no file system, which is valid as mkfs hasn't been run.
If I try to run install and select a remote dir it produces the following error (debug is on) when trying to start the same version of SA that I can boot as above
Which again I'm guessing is to do with the fact that there isn't a filesytem on the disk.
I know I'm either probably doing something really stupid, or missing out a basic step, but I'm now at the can't see the wood for the trees stage on this and would really appreciate any help
Cheers
I'm trying to do a network install on a clean (ex PC) disk in a Fuel (from FreeBSD) using 6.5.30 from supportfolio, and the rest from base, copied (using IRIX) to disk, and the copied over to the FreeBSD box.
I do have the CDs, and I do have a working CD drive in the Fuel, and I can do a CD install without any problem at all (which is how I copied the contents of the CDs) however I'm trying to learn how to do a network install, I like doing "bare metal" network installs
On the FreeBSD box I've started with two directory trees setup in /usr /tftpboot with just fx.64, sa, unix.IP35 and uni_0004.ip3 and /sgi_os_software with all of the copies of teh CDs (full set of from 6.5.14, copies of the overlays from 6.5.22 and copies of the downloaded 6.5.30)
I've setup dhcp, tftp (with -s /usr/tftpboot) and rsh (bootp and dhcp don't actually seem to be needed if you set netaddr, netmask, and srvaddr in the PROM
I can boot fx.64 and partition the disk
Code: Select all
boot -f bootp()192.168.53.171:/fx.64 --x
I can then boot sash
Code: Select all
boot -f bootp()192.168.53.171:/sa(sash64)
I can also boot uni_0004.ip3
Code: Select all
boot -f bootp()192.168.53.171:/uni_0004.ip3
but, it then complains about there being no file system, which is valid as mkfs hasn't been run.
If I try to run install and select a remote dir it produces the following error (debug is on) when trying to start the same version of SA that I can boot as above
Code: Select all
bootpopen: ctlr 0, file 192.168.53.171://sa(sash64)
bootpopen: host 192.168.53.171, file //sa , member sash64
skipping BOOTP ...
TFTP: RRQ for file //sa to 192.168.53.171
after connect: tftp count 512, offset 0
bootpread: ctlr 0, buf c00000001324b100, count 4190
loading ELF structure at offset 0x21618 into memory at 0xc00000001324c200
bootpread: ctlr 0, buf c00000001324c200, count 9528
loading ELF structure at offset 0x32390 into memory at 0xc000000013242b00
bootpread: ctlr 0, buf c000000013242b00, count 6080
loading ELF structure at offset 0x33b50 into memory at 0xc000000013242b00
bootpread: ctlr 0, buf c000000013242b00, count 2928
loading ELF structure at offset 0x37ec0 into memory at 0xc00000001324e780
bootpread: ctlr 0, buf c00000001324e780, count 36360
err is 0x0
bootpclose: ctlr 0
tftpabort: TFTP send ERROR packet
list init 128c000 12ff654 73654
mrboot
source : bootp()192.168.53.171://sa(mr)
dest : dksc(0,1,1)
A 000: *** TLB Refill Exception on node 0
A 000: *** EPC: 0xc00000001fc47e58 (0xc00000001fc47e58)
A 000: *** Press ENTER to continue.
A 000: POD IOC3 Unc>
A 000: POD IOC3 Unc>
Which again I'm guessing is to do with the fact that there isn't a filesytem on the disk.
I know I'm either probably doing something really stupid, or missing out a basic step, but I'm now at the can't see the wood for the trees stage on this and would really appreciate any help
Cheers
has anyone seen my console ?
Hi,
I agree, but its not me selecting it :-)
I get the same result with 6.5.30 and 6.5.22
Full trace below
I agree, but its not me selecting it :-)
I get the same result with 6.5.30 and 6.5.22
Full trace below
Code: Select all
ALL DIAGS PASSED.
**** End System Configuration and Diagnostics Summary ****
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
Option? 5
Command Monitor. Type "exit" to return to the menu.
>> setenv DEBUG 1
>> exit
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
Option? 2
Installing System Software...
Press <Esc> to return to the menu.
1) Remote Directory 2)[Local CD-ROM]
*a) Local SCSI CD-ROM drive 4, on controller 1
Enter 1-2 to select source type, a to select the source, <esc> to quit,
or <enter> to start: 1
Enter the name of the remote host: 192.168.53.171
Enter the remote directory: /30
1)[Remote Directory] 2) Local CD-ROM
*a) Remote directory /30 from server 192.168.53.171.
Enter 1-2 to select source type, a to select the source, <esc> to quit,
or <enter> to start:
enter loadbin bootp()192.168.53.171:/30/sa(sash64)
ef0: 100 Mbits/s fullduplex
MII Control Reg = 0x3100
MII Status Reg = 0x786d
MII Adv Reg = 0x1e1
MII LpAdv Reg = 0x45e1
bootpopen: ctlr 0, file 192.168.53.171:/30/sa(sash64)
bootpopen: host 192.168.53.171, file /30/sa , member sash64
skipping BOOTP ...
TFTP: RRQ for file /30/sa to 192.168.53.171
get_rand returns 42628
arpresolve ip 192.168.53.171 -> ether 0:50:8b:4:e0:f0
after connect: tftp count 512, offset 0
bootpread: ctlr 0, buf c000000013202c80, count 5
loading 64 bit ELF
bootpread: ctlr 0, buf c000000013202c85, count 59
elfhdr is 0xc000000013202c80
loading Elf64 relocatable
about to read 0x380 bytes from ELF header at offset 0x40e90
loading ELF structure at offset 0x40e90 into memory at 0xc000000013241800
bootpread: ctlr 0, buf c000000013241800, count 896
adding up image size
imagesize = 0x1b4a3
imagesize = 0x1f67f
imagesize = 0x2058e
imagesize = 0x73655
alignment is 0x10 rounding addr up from 0xa80000000128c000 to 0xa80000000128c000
loading ELF structure at offset 0x40 into memory at 0xa80000000128c000
need to seek backward to offset 64 (currently at 266768).
Closing and reopening file
bootpclose: ctlr 0
tftpabort: TFTP send ERROR packet
MII Control Reg = 0x3100
MII Status Reg = 0x786d
MII Adv Reg = 0x1e1
MII LpAdv Reg = 0x45e1
bootpopen: ctlr 0, file 192.168.53.171:/30/sa(sash64)
bootpopen: host 192.168.53.171, file /30/sa , member sash64
skipping BOOTP ...
TFTP: RRQ for file /30/sa to 192.168.53.171
after connect: tftp count 512, offset 0
bootpread: ctlr 0, buf a80000000128c000, count 111764
ks[1].ks_raw == 0xa80000000128c000
alignment is 0x8 rounding addr up from 0xa8000000012a7494 to 0xa8000000012a7498
loading ELF structure at offset 0x1b4d8 into memory at 0xa8000000012a7498
bootpread: ctlr 0, buf a8000000012a7498, count 16853
ks[2].ks_raw == 0xa8000000012a7498
alignment is 0x8 rounding addr up from 0xa8000000012ab66d to 0xa8000000012ab670
loading ELF structure at offset 0x1f6b0 into memory at 0xa8000000012ab670
bootpread: ctlr 0, buf a8000000012ab670, count 3848
ks[3].ks_raw == 0xa8000000012ab670
alignment is 0x8 rounding addr up from 0xa8000000012ac578 to 0xa8000000012ac578
ks[4].ks_raw == 0xa8000000012ac578
loading ELF structure at offset 0x29e40 into memory at 0xc000000013242b00
bootpread: ctlr 0, buf c000000013242b00, count 34128
loading ELF structure at offset 0x205b8 into memory at 0xc00000001324b100
need to seek backward to offset 132536 (currently at 205712).
Closing and reopening file
bootpclose: ctlr 0
tftpabort: TFTP send ERROR packet
MII Control Reg = 0x3100
MII Status Reg = 0x786d
MII Adv Reg = 0x1e1
MII LpAdv Reg = 0x45e1
bootpopen: ctlr 0, file 192.168.53.171:/30/sa(sash64)
bootpopen: host 192.168.53.171, file /30/sa , member sash64
skipping BOOTP ...
TFTP: RRQ for file /30/sa to 192.168.53.171
after connect: tftp count 512, offset 0
bootpread: ctlr 0, buf c00000001324b100, count 4190
loading ELF structure at offset 0x21618 into memory at 0xc00000001324c200
bootpread: ctlr 0, buf c00000001324c200, count 9528
loading ELF structure at offset 0x32390 into memory at 0xc000000013242b00
bootpread: ctlr 0, buf c000000013242b00, count 6080
loading ELF structure at offset 0x33b50 into memory at 0xc000000013242b00
bootpread: ctlr 0, buf c000000013242b00, count 2928
loading ELF structure at offset 0x37ec0 into memory at 0xc00000001324e780
bootpread: ctlr 0, buf c00000001324e780, count 36360
err is 0x0
bootpclose: ctlr 0
tftpabort: TFTP send ERROR packet
list init 128c000 12ff654 73654
mrboot
source : bootp()192.168.53.171:/30/sa(mr)
dest : dksc(0,1,1)
A 000: *** TLB Refill Exception on node 0
A 000: *** EPC: 0xc00000001fc47e58 (0xc00000001fc47e58)
A 000: *** Press ENTER to continue.
has anyone seen my console ?
Code: Select all
tftpabort: TFTP send ERROR packet
thats just the end of the TFTP connection
and I've just fixed it
I was doing all of this over console, on a whim I plugged in a monitor, keyboard and mouse
and it worked perfectly
I'll put something on the wiki about this
in precis, "don't try and install on a clean disk on a fuel using the serial console, use a local keyboard and monitor"
has anyone seen my console ?
I thought that you labled the disk in fx not sash, did I miss something ?
It was interesting going through it. I did discover that there are quite a lot of environment variables you can set in the PROM. And certainly with a Fuel, you don't need a BOOTP server or DHCP server to do a network boot.
The TFTP setup was trivial. I've booted fx, sash and the miniroot from several TFTP servers, including (gasp) the Windows2003 one :-)
Getting RSH to work the way that inst wants it to though, is proving a little (a LOT) harder, I've got a nasty feeling that this will take a while.... FC6 just wasn't having any of it, FreeBSD6.1 also is proving difficult. I can RSH onto the server, but getting a remote command to work is proving harder. However from what I've seen of IRIX so far, its really not intended as a secured OS, its designed to be inside a secure environmet </flame>
What I would really like, would be a way of logging the on screen output from when I booted the miniroot on the console (not the serial console) to see if it is also installing it to "dksc(0,1,1)" (the raw disk) rather than to dksc(0,1,0) the XFS partition. Biut as it doesn't have a network interface at that point in time then it can't be redirected to syslog, and as there isn't a formatted disk then it can't go to disk, and as at the end of it it boots the miniroot, then I'm guessing that putting it into memory isn't going to work either. I'll just have to wait untill the Origin200 becomes free and try it on that.
It was interesting going through it. I did discover that there are quite a lot of environment variables you can set in the PROM. And certainly with a Fuel, you don't need a BOOTP server or DHCP server to do a network boot.
The TFTP setup was trivial. I've booted fx, sash and the miniroot from several TFTP servers, including (gasp) the Windows2003 one :-)
Getting RSH to work the way that inst wants it to though, is proving a little (a LOT) harder, I've got a nasty feeling that this will take a while.... FC6 just wasn't having any of it, FreeBSD6.1 also is proving difficult. I can RSH onto the server, but getting a remote command to work is proving harder. However from what I've seen of IRIX so far, its really not intended as a secured OS, its designed to be inside a secure environmet </flame>
What I would really like, would be a way of logging the on screen output from when I booted the miniroot on the console (not the serial console) to see if it is also installing it to "dksc(0,1,1)" (the raw disk) rather than to dksc(0,1,0) the XFS partition. Biut as it doesn't have a network interface at that point in time then it can't be redirected to syslog, and as there isn't a formatted disk then it can't go to disk, and as at the end of it it boots the miniroot, then I'm guessing that putting it into memory isn't going to work either. I'll just have to wait untill the Origin200 becomes free and try it on that.
has anyone seen my console ?
Hi,
The only change between failing on serial console, and working on the console, was changing where I was running it from.
When I used the console I went into the command monitor, did a "setenv debug 1" then went to "install software" and selected remote etc.
Cheers
The only change between failing on serial console, and working on the console, was changing where I was running it from.
When I used the console I went into the command monitor, did a "setenv debug 1" then went to "install software" and selected remote etc.
Cheers
has anyone seen my console ?
FreeBSD rshd is now working with inst :-) It needed several changes to /etc/pam.d/rsh to get it "open" enough.
Then a quick change of sh to ksh and inst can see the distributions, YAY !
removed the conflicts, typed go, and its doing its install!
I'm not going to bother with ipfilter, but its good to know its available.
I am still curious as to why it was failing with the TLB exception when running from the serial console.
Then a quick change of sh to ksh and inst can see the distributions, YAY !
removed the conflicts, typed go, and its doing its install!
I'm not going to bother with ipfilter, but its good to know its available.
I am still curious as to why it was failing with the TLB exception when running from the serial console.
has anyone seen my console ?
Hi PB
I'll fire up the FreeBSD box tomorrow (little to drunk to do it now), and go through some of my assorted notes to see what I did back then to get it working.
Cheers
I'll fire up the FreeBSD box tomorrow (little to drunk to do it now), and go through some of my assorted notes to see what I did back then to get it working.
Cheers
has anyone seen my console ?