On Sun, Oct 15, 2000 at 02:15:23AM +0200, Guido Guenther wrote:
> Hi,
> with the following two patches (first against dvhtool, second against
> current cvs kernel) it's possible to boot the Indy from a local harddisk
> without the need of IRIX to install it in the volume header. Set
> setenv OSLoader linux
> and
> setenv OSLoadPartition /dev/sd(whatever)
> in the boot-prom and do a:
> dvhtool -d /dev/sda(whatever) --unix-to-vh (your_favorite_ecoff_kernel) linux
I just retried to put the stuff into the volume header wich worked:
I set this in the prom:
OSLoadFilename=vmlinux
OSLoadPartition=/dev/sda1
OSLoader=vmlinux
SystemPartition=scsi(1)disk(4)rdisk(0)partition(0)
when now typing "boot" i get
Unable to load scsi(1)disk(4)rdisk(0)partition(0)/vmlinux: no recognizable
file system on device.
Whereas this is correct - scsi(1) is the extern SCSI Bus on the Indigo2
and disk(4) is therefor /dev/sde
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
