neil@olympic.oz (Neil Murray) (11/11/88)
Greetings, a small group friends and I in Australia have put
together an ICM3216 system and we have some questions we wish to put to other
ICM owners, particularly those who run BSD, from University of Toronto.
- At every bootup we get a "Warning should run interleaved swap >= 2Mb"
message (we have 4Mb), some investigation has shown that it comes from the
rc file command 'swapon -a'. Is there anyway of getting rid of this message,
we only have 1 drive so we can't create a second partition, and what does it
mean? Is it just a recommendation relating to performance or something more?
- What manual set (paper) should be used. The man pages make references
to the VAX manuals or ARE the VAX man pages. Would therefore the VAX manuals
be of use, particularly in relation to configuring/regenerating the OS.
- It seems we have an incomplete/wrong set of config files for the
system. If I rebuilt the O.S. using the supplied files without any changes
whatsoever we got a large list of missing modules spat out at link time.
If we use the left over makefile already on the system (ie: dont do a config)
I can built the vmunix program. After some poking around it seems the config
files are missing a line or something that means to insert $(KERNLIB) in the
generated makefile. Is this the same experience that others have had?
- We had to rebuild the operating system so we could include some
changes to the tc.c file, the tape handler, so it would run with an Adaptec
ACB3530 (?) controller instead of an Emulex controller. We have managed to
do this sucessfully, so if any one else wants the mods I could post them to
this group. We don't have the Adaptec controller working in QIC-11
mode yet, only QIC-24.
- I noticed we have the chat daemon chatd but no user chat program
is this intentional? Also there was no cpio.
- We are having problems with the battery backed real time clock
at most boot ups we have messages about file dates being more recent than the
clock dates and messages about losing 86400 seconds (24 hours), occasionally the
console sees "RTC: reset" popping up. Anybody know what causes this or where
to start looking? We do have the power fail line hooked up as recommended
to save the battery rtc as the power fails. Some tests have shown that if the
system is left off for several days the battery rtc is incrementing the
time/date but at a slow rate (I think). Example: Shutdown system on Sunday with
the correct time and date set. One week later the date is showing Wednesday and
the time is wrong as well.
- Is there any likelyhood of obtaining the source code to the Z-80's
eprom in the ICM3216 (its an 8k 2764), has anyone disassembled it?
Finally its a shame the Portland Development group never got to
release the ethernet board that plugged onto the MINIBUS.
--
Neil Murray (R&D Dept) ACSnet: neil@olympic.oz
Olympic Amusements, ARPA: neil%olympic.oz@uunet.uu.net (?)
Victoria, Australia, 3169. UUCP: {uunet,mcvax,ukc}!munnari!olympic.oz!neil
... I own Mot, Intel, and NSC based systems - I'm either unbiased or indecisive