hello

for the hell of it, maybe try 1.5.1 or 1.4.2.. who knows, the generic install
kernel might have a problem with it. 
when it drops to the chevron after configuring the scsi adaptor,  does it 
probe the scsi bus yet? The disk shouldnt make a difference. 
to see all settings in the prom, give the command printenv.
the proms on the decstations were pretty simple, though.. 
also, to force the serial console , remove the graphics card, just to make
things simpler while troubleshooting... 

isildur

> I'm trying to install NetBSD 1.5.2 on a DECstation 5000/240 with the prom
> version which does not work for tftp booting. So I went for the diskimage
> solution and used a Sparcstation IPX running NetBSD to write the image to a
> disk. The DECstation starts to boot the kernel just fine, but then hangs after
> recognizing "scc0". Thinking it might be a problem with the framebuffer
> support, I turned on the serial console and indeed it gets a bit farther, by
> recognizing the SCSI controller, but right after that it throws me into the
> ">>" prompt.
> 
> I'm quickly running out of ideas. I still have the option of booting from
> CD-ROM, although I don't think that will make much difference. I know that
> others are successfully running NetBSD on the 5000/240, that's why I'm still
> trying.
> 
> Ideas on what might be going wrong:
> 
> 1. I did not have any disks available with the old 50 pin connector, only a
> 4.5GB wide SCSI Seagate. I used a converter to be able to connect the disk to
> the box. As far as I can see from the boot messages available around the
> internet, the next thing after the SCSI controller is recognzied should be the
> disks. So I might try replacing the disk (I have an old 200MB Maxtor ready,
> should be enough for the test) and see if that makes it work.
> 
> 2. Support for some other machine in the kernel is causing the problem when
> run on the 5000/240. Is this possible at all? Would somebody be willing to
> compile me a 1.5.2 INSTALL kernel with everything not needed on the 5000/240
> removed? I'll then throw it into the miniroot and try again.
> 
> 3. Some weird setting in the PROM. I'll try to use the reset jumper to reset
> the PROM settings to the defaults.
> 
> 4. I have broken hardware.
> 
> Any other ideas?
> 
>