SGI Indigo2 Impact Netboot Kernel ip28-r10k-20050530.img - Boots SGI Indigo2 Impact R10000 (IP28) Kernel Version: 2.6.12-rc5 Kernel Build Date: 30 May 2005 Kernel CVS Date: 29 May 2005 Features (Not a Full List): Loopback Networking Serial Console SCSI Disk/Tape/CD RAID 0/1/4/5/6/1+0/Linear Supported Filesystems: EFS Ext2 Ext3 ISO9660 JFS NFS ReiserFS shmfs/tmpfs SMB UDF XFS Root Image: Embedded into Kernel Image >>> How to boot (On Serial Console): bootp(): root=/dev/ram0 console=ttyS0, where is usually 9600 for most machines, unless changed by editing the 'dbaud' parameter in the PROM Monitor. 38400 is a good, safe value. !!! NOTE !!! This image should be more stable than the previous netboot. It's based off the 2.6.12-rcX line of kernels, and I've personally been running a 2.6.12-rc2 kernel for 17 days at the time of this writing. That does not mean you will see the same level of uptime. As always, YMMV. !!! WHAT TO DO IF THE SYSTEM OOPSES !!! In the event you get an oops from using this image, I'd like to know about it. For those unaware, an oops is similar to a kernel panic in that it typically locks up the machine. The difference is that it will generally print a rather big block of semi-undecipherable text conatining addresses and other pertinent data. Modern 2.6 kernels do the translation for you and thus, the use of the 'ksymoops' utility is not normally needed. In the event of an oops, simply email me the block of text (copy + paste from your favourite serial client) along with what you were doing at the time, and if possible, the last few commands you typed before the oops (or whatever the machine was doing. I'll see to it that this data gets to the individual responsible for making this port a reality, in the hopes he is able to make some sense out of it and possibly correct any problems. For reference, the System.map file is provided again (even though this is likely not needed). It is named ip28-r10k-20050530.sysmap.bz2