* Booting an Indigo2
@ 1999-06-17 18:39 Mike Hill
1999-06-17 19:23 ` Thomas Bogendoerfer
1999-06-17 19:54 ` Andrew R. Baker
0 siblings, 2 replies; 5+ messages in thread
From: Mike Hill @ 1999-06-17 18:39 UTC (permalink / raw)
To: linux
Sorry, this looks familiar. Here's what I get in my serial console:
PROMLIB: Total free ram 65839104 bytes (64296K,62MB)
CPU: MIPS-R4000 FPU<MIPS-R4000FPC> ICACHE DCACHE SCACHE
Loading R4000 MMU routines.
CPU revision is: 00000430
Primary instruction cache 8kb, linesize 16 bytes)
Primary data cache 8kb, linesize 16 bytes)
Secondary cache sized at 1024K linesize 128
Linux version 2.2.1 (root@binkley) (gcc version egcs-2.90.27 980315
(egcs-1.0.2 release)) #4 Wed Jun 16 22:03:59 EDT 1999
MC: SGI memory controller Revision 3
calculating r4koff... 0007a203(500227)
Console: colour dummy device 80x25
zs0: console input
Console: ttyS0 (Zilog8530)
Calibrating delay loop... 49.87 BogoMIPS
Memory: 60952k/196140k available (1120k kernel code, 2188k data)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5
SGI Zilog8530 serial driver version 1.00
tty00 at 0xbfbd9830 (irq = 21) is a Zilog8530
tty01 at 0xbfbd9838 (irq = 21) is a Zilog8530
DS1286 Real Time Clock Driver v1.0
streamable misc devices registered (keyb:150, gfx:148)
RAM disk driver initialized: 16 RAM disks of 4096K size
loop: registered device at major 7
wd33c93-0: chip=WD33c93B/13 no_sync=0xff no_dma=0 debug_flags=0x00
setup_args=,,,,,,,,,
Version 1.25 - 09/Jul/1997, Compiled Jun 16 1999 at 22:16:18
scsi0 : SGI WD93
scsi : 1 host.
sending SDTR 0103013f0csync_xfer=2c Vendor: SGI Model: SEAGATE
ST31200N Rev: 9278
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2077833 [1014 MB] [1.0 GB]
sgiseeq.c: David S. Miller (dm@engr.sgi.com)
eth0: SGI Seeq8003 08:00:69:07:c9:47
IP-Config: Got BOOTP answer from 192.168.1.6, my address is 192.168.1.95
Partition check:
sda: sda1 sda2 sda3 sda4 sda5 sda6
Looking up port of RPC 100003/2 on 192.168.1.6
Looking up port of RPC 100005/1 on 192.168.1.6
Root-NFS: Server returned error -13 while mounting /usr/src/installfs
VFS: Unable to mount root fs via NFS, trying floppy.
request_module[block-major-2]: Root fs not mounted
VFS: Cannot open root device 02:00
Kernel panic: VFS: Unable to mount root fs on 02:00
Oops: 0000
$0 : 00000000 1004fc01 00000001 00000001
$4 : 8812f604 00000000 00000000 00000000
$8 : 1004fc00 1000001f 1004fc01 00000000
$12: 881101a0 00000030 00000000 abf3b000
$16: 88159fa0 8833fe30 8800a2a0 8bfff938
$20: a8747590 9fc4a744 00000000 9fc4a744
$24: 00000000 00000000
$28: 8833e000 8833fe10 9fc4a88c 880f57b4
epc : 880f51f8
Status: 1004fc02
Cause : 00000808
Process swapper (pid: 1, stackpage=8833e000)
Stack: 9fc4a88c 880f510c 0000000a 0000013d 20000800 8bf27000 880f57b4
880f5780
1004fc01 00000000 881101a0 00000030 00000000 abf3b000 00000000
1004fc01
00000000 8812fc9c 8814f7cc 00000000 1004fc01 1004fc00 0000fc00
ffff00ff
1004fc01 00000000 881101a0 00000030 00000000 abf3b000 00000000
8bf27000
8800a2a0 8bfff938 a8747590 9fc4a744 00000000 9fc4a744 00000000
00000000
00000037 ...
Call Trace: [<880f510c>] [<880f57b4>] [<880f5780>] [<881101a0>] [<881101a0>]
[<8800a2a0>] [<8802952c>] [<880295d4>] [<880f9270>] [<880fb690>]
[<8800a2a0>] [<880f15b0>] [<8800a2a0>] [<8800a2a0>] [<8800a2b0>]
[<88029c0c>] [<880f6778>] [<8800ff6c>] [<8800ff5c>]
Code: 24630001 ac820078 ae030000 <8ce50010> 8ce20000 00c02021 0040f809
02203021 8e020000
Aiee, killing interrupt handler
...and here's the hinv output:
Iris Audio Processor: version A2 revision 1.1.0
1 100 MHZ IP22 Processor
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
CPU: MIPS R4000 Processor Chip Revision: 3.0
On-board serial ports: 2
On-board bi-directional parallel port
Data cache size: 8 Kbytes
Instruction cache size: 8 Kbytes
Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
Main memory size: 64 Mbytes
EISA bus: adapter 0
Integral Ethernet: ec0, version 1
Integral SCSI controller 1: Version WD33C93B, revision D
Integral SCSI controller 0: Version WD33C93B, revision D
Disk drive: unit 1 on SCSI controller 0
Graphics board: GR3-XZ
My external hard drive doesn't seem to be detected (but that's okay, IRIX
doesn't like it either).
Mike
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Booting an Indigo2
1999-06-17 18:39 Booting an Indigo2 Mike Hill
@ 1999-06-17 19:23 ` Thomas Bogendoerfer
1999-06-17 19:54 ` Andrew R. Baker
1 sibling, 0 replies; 5+ messages in thread
From: Thomas Bogendoerfer @ 1999-06-17 19:23 UTC (permalink / raw)
To: Mike Hill, linux
On Thu, Jun 17, 1999 at 02:39:40PM -0400, Mike Hill wrote:
> Sorry, this looks familiar. Here's what I get in my serial console:
do you think so ?
> Root-NFS: Server returned error -13 while mounting /usr/src/installfs
> VFS: Unable to mount root fs via NFS, trying floppy.
your Indigo isn't able to mount the NFS root. According to linux/nfs.h
the error is NFSERR_ACCES.
> request_module[block-major-2]: Root fs not mounted
so it tries to use the floppy drive. But since there is no driver in the
kernel, it tries to load the module for it, which fails.
> VFS: Cannot open root device 02:00
> Kernel panic: VFS: Unable to mount root fs on 02:00
no root filesystem, no fun.
Or do I miss something ?
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Booting an Indigo2
1999-06-17 18:39 Booting an Indigo2 Mike Hill
1999-06-17 19:23 ` Thomas Bogendoerfer
@ 1999-06-17 19:54 ` Andrew R. Baker
1 sibling, 0 replies; 5+ messages in thread
From: Andrew R. Baker @ 1999-06-17 19:54 UTC (permalink / raw)
To: Mike Hill; +Cc: linux
On Thu, 17 Jun 1999, Mike Hill wrote:
> Sorry, this looks familiar. Here's what I get in my serial console:
>
[lots of stuff that looks OK clipped]
> Root-NFS: Server returned error -13 while mounting /usr/src/installfs
> VFS: Unable to mount root fs via NFS, trying floppy.
This is the only problem, which points back to an error on the NFS server
that is giving out the root filesystem. I get a similar error on my
Indigo2 at home, but not on the one I have in my office. I am planning on
upgrading my home bootp/root NFS server to see if that makes it go away.
I haven't found any details on the specific NFS errors though, so I can't
intepret it for you.
[more stuff clipped]
> My external hard drive doesn't seem to be detected (but that's okay, IRIX
> doesn't like it either).
This is on my todo list. The SCSI driver only detects one (the internal)
controller. This is fine and dandy on the Indy 'cause it only has one
SCSI controller. The Indigo2 has two, so the driver needs to be modified
to detect (and access) the second one. I plan on doing this as soon as I
get my home box up and running.
-Andrew
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Booting an Indigo2
@ 1999-06-17 20:22 Mike Hill
0 siblings, 0 replies; 5+ messages in thread
From: Mike Hill @ 1999-06-17 20:22 UTC (permalink / raw)
To: 'Thomas Bogendoerfer', linux
> -----Original Message-----
> From: Thomas Bogendoerfer [SMTP:tsbogend@alpha.franken.de]
> Sent: Thursday, June 17, 1999 3:23 PM
> To: Mike Hill; linux@cthulhu.engr.sgi.com
> Subject: Re: Booting an Indigo2
>
> On Thu, Jun 17, 1999 at 02:39:40PM -0400, Mike Hill wrote:
> > Sorry, this looks familiar. Here's what I get in my serial console:
>
> do you think so ?
>
I found similar messages in the list archive, one from Chad (on his Indy)
and one from Andrew, but no specific conclusions. Thanks for the
interpretation.
Mike
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Booting an Indigo2
@ 1999-06-17 20:34 Mike Hill
0 siblings, 0 replies; 5+ messages in thread
From: Mike Hill @ 1999-06-17 20:34 UTC (permalink / raw)
To: 'Andrew R. Baker'; +Cc: linux
Therefore if I were to connect my Indy Linux drive internally in the
Indigo2, I might be able to boot the kernel locally?
Thanks,
Mike
> -----Original Message-----
> From: Andrew R. Baker [SMTP:andrewb@uab.edu]
> Sent: Thursday, June 17, 1999 3:54 PM
> To: Mike Hill
> Cc: linux@cthulhu.engr.sgi.com
> Subject: Re: Booting an Indigo2
>
> This is on my todo list. The SCSI driver only detects one (the internal)
> controller. This is fine and dandy on the Indy 'cause it only has one
> SCSI controller. The Indigo2 has two, so the driver needs to be modified
> to detect (and access) the second one. I plan on doing this as soon as I
> get my home box up and running.
>
> -Andrew
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~1999-06-17 20:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-06-17 18:39 Booting an Indigo2 Mike Hill
1999-06-17 19:23 ` Thomas Bogendoerfer
1999-06-17 19:54 ` Andrew R. Baker
-- strict thread matches above, loose matches on Subject: below --
1999-06-17 20:22 Mike Hill
1999-06-17 20:34 Mike Hill
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.