[Top] [All Lists]


Subject: Clue-Gap
From: Dan Pinkard <>
Date: Mon, 20 Jul 1998 00:31:11 -0500 (CDT)
Either a lack of indy-clue, irix-clue, or possibly even linux-clue has
made the install process slow goings for me. If you can tell me where I
went wrong, or what I'm missing, I'll thank you. 

I'm booting with 
boot bootp():/tftplinux/vmlinux 

which sucessfully pulls the kernel and boots. The tftpboot directory has
been populated with the hardhat tarball and will actually get me into the
installer. I have also gotten it to work by copying vmlinux to the root
irix partition and booting from dhcp in the kernel. It needs nfsroot= but
works fine.

In either case, once I'm in, it cannot get past the fdisk screen. After
choosing done on fdisk it immediately dumps the kernel info and I'm left
with a very unresponsive machine.

I'm thinking that it is likely due to a poorly partitioned drive... Using
dsk0d4s1 and dsk0d4s7 as linux partitions I first used the old redhat 5.0
installer for the irix mke2fs and fscke2fs and remade dsk0d4s7. I
decided to follow through and let the installer dump the cpio image into
dsk0d4s7. After several reboots I realized it would get farter running
boot vlinux.2.1.99 root=/dev/sdc2 than anything else, but it, too, froze,
asking for some init level. I assume it only needs to be passed as a boot
param, so I moved on. (The goal was to verify the name of the partition,
not to boot into the old installer)

Again, the hardhat installer did not make it past the fdisk screen. 

Next I rebooted and used the hardhat installer to refdisk it all myself.
Quite nice.. worked fine, but it didn't make it beyond the fdisk screen.

At any rate, What can I salvage of this situation? Where did I most likely
go wrong, and what can I/we do to better answer this question for next

Thanks... d.p.

<Prev in Thread] Current Thread [Next in Thread>