Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!munnari!bruce!goanna!cidam!dsb
From: dsb@cidam.rmit.oz (David Burren [Athos])
Newsgroups: comp.os.minix
Subject: Re: MINIX on HP Vectra???
Message-ID: <2466@cidam.rmit.oz>
Date: 5 Sep 88 00:47:50 GMT
Article-I.D.: cidam.2466
References: <590001@hpsad.HP.COM>
Organization: RMIT Mech & Prod Eng, Melbourne, Australia.
Lines: 36

In article <590001@hpsad.HP.COM>, mikef@hpsad.HP.COM (Mike Ferrara) writes:
> Does anybody out there have minix running on an HP Vectra?
> We've got a vectra ES/12 and a plain old vectra, (AT compatibles) neither
> of which will boot the minix 1.2 for AT/512K distribution from Prentice-Hall.
> During the boot, I get as far as the first menu, so I can fsck disks, and
> start loading the root file system, but upon the first disk access, I get
> the error:
> 
> unexpected trap vector >=16 This may be due to accidentally including
> a non-MINIX library routine that is trying to make a system call.
> pc=0x154 text+data+bss=0x900
> 
I had similar problems when getting Minix first running on my AT-clown. It
can run at four speeds, 6 or 12 MHz, with 0 or 1 wait-states. At any speed
above 6 MHz 1 wait, it would work perfectly until just after the
"RAM disk loaded" message, when it would get an unexpected trap. If I booted
at that speed and then switched to any higher speed, it would get the
unexpected trap message at the next command. I found that although the machine
appeared to continue working, attempts to mount filesystems caused it to hang.
As for the addresses it reported, they were different at each speed. (I can't
at the moment remember exactly what they were).

I've "fixed" this temporarily by removing the controller for my tape drive
(a Sysgen QIC-File 60). At the moment it's running at top speed without a
hitch (although it doesn't want to know about my hard-disk, which is another
problem altogether). I'm trying to get a tech manual for the tape drive to
investigate changing interrupt lines or somesuch.
I know some other people here at RMIT who were getting unexpected traps until
they changed the interrupt used by their mouse interface.

Does the Vectra use any unusual interrupts?

-----------------------------------------------------------------------
David S. Burren	(Athos)			ACSnet: dsb@cidam.oz
					UUCP:	...!uunet!munnari!cidam.oz!dsb
					ARPA:	dsb%cidam.oz@uunet.uu.net