On Mon, Jul 12, 1999 at 02:39:26PM +0200, Edwin Hakkennes wrote:
> After lurking on the sgi-list for more than a year, I installed one of
> our indy's with hardhat. I couldn't get bootp working, so I copied the
> install kernel to the efs-root of the Irix (5.2?) disk, which proved a
> workable solution.
> I have a few questions:
> 1) The console uses 62 lines, but I can see only 47 of them using an
> Iiyama monitor. I also tried a genuine SGI monitor, which gives me all
> 62 lines. How can I set the number of lines?
You seem to be running the kernel shipping with Hard Hat which had problems
like this due different positioning of the gfx. Current kernels are
more like IRIX in that aspect.
> 2) How can I specify kernel options in the ARC firmware?
> I tried
> setenv -p OSLoadOptions "root=/dev/sdb1"
> printenv OSLoadOptions
> which gives
Run it like /vmlinux root=/dev/sdc1 or so.
> so this doesn't seem to work.
> Can I use rdev on i386 machine for this?
Yes, but it will not work ;-)
> 3) What is the prefered partitioning scheme. I would like to go back
> to one disk, with no IRIX installed. So the question is what partition
> types is the arc-firmware able to boot from? (iso,fat)
The volume header, EFS and BOOTP/TFTP.
If you're using IRIX's sash then you can also boot a kernel from XFS
or whatever else sash supports.
> Can we alternatively store the kernel in the disk-label? From within Linux??
I'm working on a tool to do this. Even better, on a bootloader which
will be able to read the kernel to launch from a ext2 filesystem.
For the time being you can use dvhtool under IRIX to do this.
> Is the following possible?
> sda1 20 MB /boot type=efs (or iso9660, or fat)
> sda2 100 MB / type=ext2
> sda3 whole disk? Is this necessary?
That whole disk partition thing is actually an IRIX-ism which wasn't
supposed to make it into Linux ...
> sda4 800 MB /usr type=ext2
> sda5 128 MB SWAP
> sda6 REST /data type=ext2
> Is linux capable of writing to an efs partition?
No, only reading and that only in current kernel versions.