Subject: Re: VS3100 and the new snapshot kernel... (solved)
To: NetBSD/vax Mailing List <email@example.com>
From: Marc Gutschner <Marc.Gutschner@Frankfurt.NetSurf.DE>
Date: 12/06/1998 12:55:07
I think I've found the solution for my problems with the -current kernels
:-) I just compiled a new 'boot', converted it with 'mopa.out' to a
MOP-Format bootloader and - voila - the VS3100 likes me again :) I built the
bootloader with bootp/DHCP support - still have to try if it will work with
rpc/bootparamd, too. So it seems that my first thought about some new 'rain
dances' the bootloader does were just about right. Now I'll try to build a
kernel with SCSI support and see how well this will go...
thanks to all who replied,
Von: Matthew Hudson <firstname.lastname@example.org>
An: NetBSD/vax Mailing List <email@example.com>
Datum: Sonntag, 6. Dezember 1998 11:19
Betreff: Re: VS3100 and the new snapshot kernel...
>Having no troubles here on a VS3100/30. Actually this is
>the most stable kernel I've run. Not being familiar with
>disklabel, etc though I've not yet gotten the disks up.
>(I know its supposed to be broken, but it does recognize
>that the RZ23 is there, so I've been trying [and assuming
>the problem has been my ignorance of disklabel]).
>> > > I'm currently having some - uhm - bizarre problems with the current
>> > > kernels and my VS3100/m38. I compiled myself a kernel from -current
>> > > source sup'd one or two days ago. The compile itself went really
>> > > but as soon as I tried to boot, the kernel get's loaded and
>> > > bombs out with a 'RESTART SYS'
>> > Same here. On my VS3100/M38, latest snapshot, older bootloader which
>> > using rarp/bootparamd. Is the kernel expecting a BOOTP server? (Not
>> > it would explain the following troubles).
>> > -ESA0
>> > >> NetBSD/vax boot [980110 22:29] <<
>> > : /netbsd
>> > boot: client IP address: 10.3.250.106
>> > boot: client name: meme
>> > root addr=10.3.250.41 path=/export/meme/root
>> > 806876+44788+164520
>> > 85 RESTART SYS
>> > 84 FAIL
>> > 83 BOOT SYS
>> > [loops through the above boot attempts]
>> Okay, the MicroVAX II with DEQNA results in the following:
>> >>> b xqa0
>> >> NetBSD/vax boot [980311 22:57] <<
>> : /netbsd
>> boot: client IP address: 10.3.250.109
>> boot: client name: vaxzilla
>> root addr=10.3.250.41 path=/export/vaxzilla/root
>> 806876+44788+164520 start 0x8e4
>> ?06 HLT INST
>> PC = 800C5032
>> The VAXstation 2000 behaves the same as the VS3100.