PDA

View Full Version : Tandy Xenix SUPERVISOR TRAP 4 Panic



NeXT
January 5th, 2013, 12:36 PM
Finally had the chance to try out my Xenix disks with the MC68000 board in my Model II.

http://i11.photobucket.com/albums/a166/ballsandy/Computer%20related/CRW_7786.jpg
http://i11.photobucket.com/albums/a166/ballsandy/Computer%20related/CRW_7777.jpg
http://i11.photobucket.com/albums/a166/ballsandy/Computer%20related/CRW_7782.jpg

Not sure if it's a ROM compatibility issue or if one of the many hacks to the boardset is acting up. I have no documentation so I ahve no clue what a Trap 4 panic is.

tingo
January 5th, 2013, 01:07 PM
Wow, I didn't know that a 68k board existed for this machine. Very cool!
I found a manual (http://www.tenox.tc/docs/tandy_using_xenix_320.pdf) for Xenix 3.2.0, it says this:

"Supervisor trap d
panic: trap in sys
The 68000 cpu has generated a TRAP number while executing kernel or device driver code. This message is preceded with an information dump describing the trap. Hardware or system inconsistency. fatal."

Not sure it is helpful.

NeXT
January 5th, 2013, 01:38 PM
I had a feeling it was hardware. Yeah, I discovered tenox after I posted. The Operations Guide states that the first thing you have to do is format your disk/hard drive with DISKUTIL. Unless I'm mistaken I do believe xenix wouldn't be happy if it doesn't have a filesystem to mount.
So I have a Seagate ST-225 attached to a Type 4 hard disk controller (http://fjkraan.home.xs4all.nl/comp/trs80m2/SingleST412Interface.jpg) on my system because according to the Tandy Folk that should work. (and I was talking more about here on the forums last year) (http://www.vintage-computer.com/vcforum/showthread.php?30099-TRS-80-Model-II-disk-controller-with-alternate-drives)
http://i11.photobucket.com/albums/a166/ballsandy/Computer%20related/CRW_7789.jpg
Now, the error map fell off my '225 years ago so I just skipped the mapping part.

http://i11.photobucket.com/albums/a166/ballsandy/Computer%20related/CRW_7790.jpg
I doubt the drive is bad. I have to be doing something wrong.

tingo
January 9th, 2013, 02:17 PM
Perhaps diskutil doesn't accept an empty media error map?
Did you try just entering one entry for the media error map? The first line of the example perhaps?

NeXT
January 9th, 2013, 02:32 PM
Tried another drive that DID still have an error map with it and no, this is either a configuration or controller issue.
Of course, it would be nice if I could confirm that the Type 4 controller works with Xenix 1.03.