[Simh] Panic while attempting to boot a NetBSD ISO

Sun Feb 7 09:21:18 EST 2016

Just to confirm latest git src (MicroVAX 3900 simulator V4.0-0 Beta
git commit id: 1cd89258) also works fine for me.

Another random thought, can you confirm you can read the contents of
the ISO image OK outside of simh? It should have an ISO9660 partition
of 1331200.

[I *hate* to be of those who ends up sending two emails when they
should just have waited and sent one, but I've never built simh
outside of pkgsrc before and didn't know if it would Just Work.... It
Did :)]

David

On 7 February 2016 at 14:12, David Brownlee <abs at absd.org> wrote:
> On the offchance it helps I've attached my config for booting NetBSD-7
> on the stock simh-3.9.0nb4 from pkgsrc, and a boot via 'b dua1'. Maybe
> if you posted your .simh file and the output again we might be able to
> work out whats up? I could also try the latest git source to see if my
> config still works there...
>
> % cat netbsd-7.0.simh
> load -r /usr/pkg/share/simh/ka655x.bin
> set cpu 256m
> set rq0 ra90
> at rq0 netbsd-7.0.ra90
> set rq1 cdrom
> at rq1 NetBSD-7.0-vax.iso
> set rq2 ra92
> at rq2 pkgsrc.ra92
> at xq0 wm0
> boot cpu
>
> # simh-vax netbsd-7.0.simh
>
> VAX simulator V3.9-0
> libpcap version 1.3.0
> Eth: opened OS device wm0
>
>
> KA655X-B V5.3, VMB 2.7
> Performing normal system tests.
> 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
> 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
> 08..07..06..05..04..03..
> Tests completed.
>>>>b dua1
> (BOOT/R5:0 DUA1
>
>
>
>   2..
> -DUA1
>   1..0..
>
>
>>> NetBSD/vax boot [1.11] <<
>>> Press any key to abort autoboot 4
> getdisklabel: no disk label
> nfs_open: must mount first.
> open netbsd.vax: No such file or directory
>> boot netbsd
> getdisklabel: no disk label
> nfs_open: must mount first.
> 3098208+172992 [229904+219992]=0x38cb9c
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
>     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
>     The NetBSD Foundation, Inc.  All rights reserved.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>     The Regents of the University of California.  All rights reserved.
>
> NetBSD 7.0 (GENERIC.201509250726Z)
> MicroVAX 3800/3900
> total memory = 255 MB
> avail memory = 243 MB
> kern.module.path=/stand/vax/7.0/modules
> mainbus0 (root)
> cpu0 at mainbus0: KA655, CVAX microcode rev 6 Firmware rev 83
> lance at mainbus0 not configured
> uba0 at mainbus0: Q22
> dz1 at uba0 csr 160100 vec 304 ipl 17
> mtc0 at uba0 csr 174500 vec 774 ipl 17
> mscpbus0 at mtc0: version 5 model 3
> mscpbus0: DMA burst size set to 4
> uda0 at uba0 csr 172150 vec 770 ipl 17
> mscpbus1 at uda0: version 3 model 3
> mscpbus1: DMA burst size set to 4
> qe0 at uba0 csr 174440 vec 764 ipl 17: delqa, hardware address 08:00:2b:aa:bb:cc
> rlc0 at uba0 csr 174400 vec 160 ipl 17
> rl0 at rlc0 drive 0: RL01, drive not loaded
> rl1 at rlc0 drive 1: RL01, drive not loaded
> rl2 at rlc0 drive 2: RL01, drive not loaded
> rl3 at rlc0 drive 3: RL01, drive not loaded
> ts0 at uba0 csr 172520 vec 224 ipl 17: TS11
> ts0: rev 0, extended features enabled, transport offline
> mt0 at mscpbus0 drive 0: TK50
> mt1 at mscpbus0 drive 1: TK50
> mt2 at mscpbus0 drive 2: TK50
> mt3 at mscpbus0 drive 3: TK50
> ra0 at mscpbus1 drive 0: RA90
> racd0 at mscpbus1 drive 1: RRD40
> ra1 at mscpbus1 drive 2: RA92
> rx0 at mscpbus1 drive 3: RX50
> ra0: size 2376153 sectors
> racd0: size 1331200 sectors
> ra1: size 2940951 sectors
> rx0: attempt to bring on line failed:  unit offline (not mounted) (code 3, subco
> de 1)
> boot device: racd0
> root on racd0a dumps on racd0b
> root file system type: cd9660
> [...]
>
> On 7 February 2016 at 04:40, Gregg Levine <gregg.drwho8 at gmail.com> wrote:
>> Hello!
>> Same problem as before, again with the proper location for the CD as
>> the VAX emulation knows its there. The routines start as before then
>> at the prompt I enter boot dua1:. Then the simulation escapes back to
>> prompt for itself rather then a VAX prompt and that's where I'm stuck.
>>
>> Oh and this is all happening with the code retrieved from GIT about
>> now. I'm going to update the store and start all over again. (Building
>> them.)
>> -----
>> Gregg C Levine gregg.drwho8 at gmail.com
>> "This signature fought the Time Wars, time and again."
>>
>>
>> On Sat, Feb 6, 2016 at 11:26 PM, Gregg Levine <gregg.drwho8 at gmail.com> wrote:
>>> Hello!
>>> Okay I've tried again to bring things up. This time remembering to
>>> give it dua1: at the prompt instead of something else. It promptly
>>> complained. I'll try one more time this time with the image in the
>>> same directory as the boot script. I've also commented out the
>>> firmware blob since you've commented that its already included.
>>> -----
>>> Gregg C Levine gregg.drwho8 at gmail.com
>>> "This signature fought the Time Wars, time and again."
>>>
>>>
>>> On Sat, Feb 6, 2016 at 7:59 AM, Mark Pizzolato <Mark at infocomm.com> wrote:
>>>> On Friday, February 5, 2016 at 10:07 PM, Gregg Levine wrote:
>>>>> Hello!
>>>>> That's just it Mark. They aren't empty ones. I've downloaded three
>>>>> separate ISO images, 5.1.3 and then 5.1.4 and finally 5.1.5 and placed
>>>>> them in their own directories.
>>>>>
>>>>>
>>>>> You mean that the selection of what to create is bollixed? It was
>>>>> supposed to create an empty disk image. Now what it says here: "RQ1:
>>>>> creating new file", it was suppose to use RQ0 for that.
>>>>> I suspect something is definitely wrong there.
>>>>
>>>> That was my point.  Meanwhile, Wilm Boerhout <wilm at boerhout.nl>
>>>> points out the reason why the simulator halted (you tried to boot
>>>> from DUAL instead of DUA1).  Given the 'RQ1L creating new file',
>>>> you'll get a different failure message trying to boot from an empty disk.
>>>>
>>>> Looking ahead.  I said that your attempt to connect XQ to wlan would
>>>> Probably be a problem when you get that far.  For NetBSD you're
>>>> only interested in IP and none of the other DEC LAN protocols, so
>>>> 'attach xq NAT:' will probably meet your needs.
>>>>
>>>>> Right now the computer is running Windows. The stuff for all of that
>>>>> is on a different disk, and I'll need to switch back.
>>>>
>>>> All this stuff works on Windows also.  :-)
>>>>
>>>>
>>>>> I'll report more when that is happening.
>>>>> -----
>>>>> Gregg C Levine gregg.drwho8 at gmail.com
>>>>> "This signature fought the Time Wars, time and again."
>>>>>
>>>>>
>>>>> On Sat, Feb 6, 2016 at 12:31 AM, Mark Pizzolato <Mark at infocomm.com>
>>>>> wrote:
>>>>> > On Friday, February 5, 2016 at 9:15 PM, Gregg Levine wrote:
>>>>> >> Hello!
>>>>> >> Okay here goes, I'm following these instructions:
>>>>> >> https://www.netbsd.org/ports/vax/emulator-howto.html
>>>>> >
>>>>> > Well, the commands outlined at this link say:
>>>>> >         load -r /usr/pkg/share/simh/ka655x.bin
>>>>> >         set cpu 64m
>>>>> >         set rq0 ra92
>>>>> >         at rq0 netbsd.dsk
>>>>> >         set rq1 cdrom
>>>>> >         at rq1 /path/to/vaxcd.iso
>>>>> >         at xq0 name-of-network-interface-on-host
>>>>> >         boot cpu
>>>>> >
>>>>> >> And I'm getting this response:
>>>>> >> MicroVAX 3900 simulator V4.0-0 Beta        git commit id: f03bae6c
>>>>> >> sim> do netbsd-boot
>>>>> >> RQ1: creating new file
>>>>> >
>>>>> > This message suggests that:
>>>>> >         at rq1 /path/to/vaxcd.iso
>>>>> > isn't actually pointing at the CDROM image, but has created a new empty
>>>>> disk image file
>>>>> >
>>>>> >> libpcap version 1.4.0
>>>>> >> Eth: opened OS device wlan0 - No description available
>>>>> >
>>>>> > OK so far, but I think you'll eventually have trouble using a Wireless Device.
>>>>> That won't matter for now.
>>>>> >
>>>>> >> KA655-B V5.3, VMB 2.7
>>>>> >> Performing normal system tests.
>>>>> >> 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
>>>>> >> 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
>>>>> >> 08..07..06..05..04..03..
>>>>> >> Tests completed.
>>>>> >> >>>boot dual:
>>>>> >> (BOOT/R5:0 DUAL
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>   2..
>>>>> >> ?41 DEVASSIGN, DUAL
>>>>> >> HALT instruction, PC: 00000C1A (MOVL (R11),SP)
>>>>> >> sim>
>>>>> >
>>>>> > Booting from an empty CDROM image isn't likely to get too far...
>>>>> >
>>>>> >> The script I wrote follows what it says on the site, except for the CD-ROM
>>>>> >> file, and the network device, and the BIN file it needs.
>>>>> >
>>>>> > The "load -r ..." command isn't necessary anymore.  The ROM image is built
>>>>> in to the binary, but what you did shouldn't be bad.
>>>>> >
>>>>> > - Mark
>>>>
>> _______________________________________________
>> Simh mailing list
>> Simh at trailing-edge.com
>> http://mailman.trailing-edge.com/mailman/listinfo/simh