HDTenEightyP/NetNews huggingface dataset:
From: alm@netcom.com (Andrew Moore)
Subject: ghostscript under 386BSD?
Date: Fri, 11 Sep 92 05:29:17 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

Ghostscript is part of the /etc distribution of 386bsd. I rebuilt it
using the default makefile (for epson device). But when invoked it dies
with diagnostic:

Initializing... Zget t_string 256 >= 256
Unrecoverable error: rangecheck in get
Operand stack:
    256 [...]

Before I attempt to wade through the code, I was hoping someone might
have fixed this.  Any ideas?  Anyone else successfully using ghostscript
under 386bsd?  Thanks.
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: chrisc@lmt.mn.org (Chris Cox  W0/G4JEC)
Subject: Boot problems on old 386/287 AMI system
Organization: LaserMaster Technologies, Minneapolis, MN
Date: Sat, 12 Sep 92 16:42:04 GMT

I have a fairly old 20MHz 386 system at home which has a '287 coprocessor
installed.

Last night, I tried an initial installation of 386BSD 0.0, however, I could
not get past the boot stage.

Specifically, after displaying the equipment configuration, and then inform-
ing me that it was switching the root to fd0a, the system hung.  I was able
to warm boot, so it was not locked tight.  The cursor was situated on the
following (blank) line after the message about switching to fd0a, 12 charac-
ter positions into the line.

The system configuration is:-
80386/20 no cache
80287/10
6MB RAM with Shadowing of ROM's disabled via setup.
AMI BIOS dated 15 Aug 88
Paradise Basic VGA
SMS/OMTI 1:1 MFM HDD/FDD controller
Wren II 36MB MFM drive
3.5" A: floppy
5.25" B: floppy
WD8003E ethernet
COM1 & COM2 (ususal config)
LPT1 at 0x378

I tried removing the WD8003e, and swapping the disk controller, however, the
results were identical.  I did NOT try disabling the 80287.

Will 386BSD boot on a machine which contains an 80287 coprocessor, or could 
this be a BIOS related problem?

Thanks for any help.

Chris
From: terry@uivlsisd.csl.uiuc.edu (Terry Lee)
Newsgroups: comp.unix.bsd
Subject: Re: Problem with OPTi?
Date: 8 Sep 92 17:42:09 GMT
Organization: Center for Reliable and High-Performance Computing, University of Illinois at Urbana-Champaign
NNTP-Posting-Host: uivlsisd.csl.uiuc.edu
Keywords: OPTi

In my previous post, I wrote:

>	Has anyone been able to get 0.1 to run on any 486 machine based on
>an OPTi chipset?  If so, are you using the 486SXWB or 486WB motherboard?
>I think I am experiencing bug BOOT009 in Nate Williams's bug list version 0.2,
>where all of the boot floppies lock up the system after displaying the initial
>copyright message (before listing any devices found).  I have an OPTi 486SXWB
>motherboard (486DX-33, 06/06/91 AMI BIOS).  Please, I really need help with
>this!  Also, if no one has found a fix, new buyers should be warned away from
>this motherboard (or chipset)!  Thanks.

	Thanks to all the netters who helped out!  Several wrote or posted to
confirm that 386BSD works fine with their OPTi chipset or motherboard.
Special thanks to Frank MacLachlan (fpm@crash.cts.com), who suggested the
patch (included below) that fixed the problem.  As it turns out, a delay was
needed in the probe routine just before the keyboard controller is reset.
Also, at the point where the boot appeared to be hanging, unplugging and
replugging the keyboard will allow the boot to proceed normally.  This way,
a working system can be set up (so the patch can be performed :-) ).

----------
Terry Lee
terry@uivlsi.csl.uiuc.edu
Newsgroups: comp.unix.bsd
From: adam@micromuse.co.uk (Adam Kerrison)
Newsgroups: comp.unix.bsd
Subject: Re: X386 install (/dev/vga)
Date: 7 Sep 92 08:36:11 GMT
Reply-To: adam@micromuse.co.uk
Organization: MicroMuse Ltd, London, UK

In article 7252@lib.tmc.edu, blile@thesis1.med.uth.tmc.edu (BUD W. LILE) writes:
>I'm posting this question for my roommate.
>
>He has installed X386 on his 386BSD system.   Created the configuration
>file.
> 
>When he tries to start X, he gets a message CONNOT OPEN /dev/vga!  
>
>What is this device, is it just a renamed console or what.  If its 
>a special device driver where is the source code?
> 
>Also, are there any good install intructions or does one go for broke or
>did he just miss them?
> 
>Please just post to the net as he does have RN access.
>
>thanks
>B lile
>University of Texas Medical School at Houston

I had this problem too. A friend of mine helped me to fix it. Just do:

mknod /dev/vga c 12 0

as root. This will create the device. Of course you have to have patched and 
rebuilt the kernel with the XSERVER option (at least thats what I did).

However, my X isn't running ... It gets into graphics mode then hangs (I have
an Orchid ProDesigner I (ET3000 based card 512K memory)). I have seen articles
on this on the net but I am still looking for the fix.

Hope this helps in some way.

Adam

---
===========================================================================
Adam Kerrison                  | Phone : +44 71 352 7774
Technical Support              | Fax   : +44 71 351 7834
MicroMuse Ltd                  | E-mail: adam@micromuse.co.uk
London SW10 0RN                | 
===========================================================================
"When you kill a man, you're a murderer. Kill many, and you're a conqueror.
Kill them all, you're a god !" - Think about it
===========================================================================
Newsgroups: comp.unix.bsd
From: karn@servo.qualcomm.com (Phil Karn)
Subject: Re: Fixed: Runs at 8MHz, Crashes at 33MHz, 386bsd
Organization: Qualcomm, Inc
Date: Fri, 11 Sep 1992 20:07:36 GMT

In article <1992Sep8.070731.21159@bernina.ethz.ch> torda@igc.ethz.ch (Andrew Torda) writes:
>Some time ago, I complained with the following problem:
>
>     At 8 MHz, my machine appears perfectly stable.
>     At 33 MHz, I get repeated trap type 12 panics.
[...]
>The most concrete suggestions were to either add wait states or buy
>faster memory. Couldn't add any more wait states, but I managed to
>swap 8Mb of 80ns simms for 70 ns simms.
>
>Instantly, I could rebuild kernels or run my little crash program
>which simply allocated ever increasing amounts of memory and scribbled
>through it.
>The peculiarity is that with the old memory, I had been able to run
>dos, windows in enhanced mode and even SCO unix.
>It would still be nice to know what the cause is and why 386bsd
>provokes the problem.

Very interesting. I've been having similar problems with my 486-50
(with 16 meg, Adaptec SCSI controller and NE-2000). A good way to
crash it is to go into one of the source trees and run make. Often I
couldn't get through half a dozen nroff's of man pages before a panic,
usually a message from vm_fault() that I interpret to be the kernel
dereferencing a bogus pointer. Sometimes it wouldn't even get through
the reboot before it would panic again. Applying every patch in sight
didn't seem to help the problem.

So, inspired by your note, I just tried hitting my machine's Turbo
switch, knocking its clock speed down to 10 Mhz (at least that's what
the display on the front panel says). And the machine now seems *much*
more stable. It's gotten through several source directories without
incident so far, albeit much more slowly.

One possible theory (stress *theory*): many modern PC chipsets provide
registers to control things like bus clock speeds, memory wait states,
etc. Much more convenient than the hardware jumpers on old motherboards.
Since these are usually set by the BIOS setup program and forgotten,
perhaps something in 386BSD is scribbling over them (or their CMOS
save areas) unintentionally? Going to faster memory, or slowing the
machine down, would let the machine run with these unintentionally
changed settings. This theory would also explain why the same machine
could run other systems at full speed without problem, because they
leave the control registers alone.

Comments?

Phil
From: randyc@soda.berkeley.edu (Yen-Pang Randy Chou)
Newsgroups: comp.unix.bsd
Subject: tip doesn't work, but /usr/distbin/tip does. Why?
Date: 14 Sep 1992 08:16:52 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
Distribution: world
NNTP-Posting-Host: soda.berkeley.edu

I just got a 9600 baud modem and tip doesn't seem to like it too much. 
Everytime I try to use it, it just hangs.  Strangely, the tip in 
/usr/distbin works.  If you know of any updates or patches for tip that
may fix this, please send me email.  Thanx!

---Randy
 
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: 386BSD PARTIAL PATCH KIT NOW AVAILABLE
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Tue, 15 Sep 1992 14:22:29 GMT

Terry:

It isn't obvious from what has already been posted, so I'll ask:

Is the serialization of patches done using a ``pre-requsites DAG'' as in
``patch16 requires patch3, patch8, and patch9 to have been already
applied'' or is it done by requiring patch0--patchN-1 to be applied before
patchN?  Or some other way?

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
From: allard@isi.edu (Dennis Allard)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Date: 11 Sep 92 22:29:06 GMT
Reply-To: allard@isi.edu (Dennis Allard)
Distribution: world
Organization: USC Information Sciences Institute
Keywords: newsgroup 386bsd news group

terry@cs.weber.edu (A Wizard of Earth C) writes:
> allard@isi.edu (Dennis Allard) writes:
> ... In the case of gigabyte networks, that place need not have
> >anything to do with 386bsd, ...except in so far as it deals
> >with 386bsd implementation issues.
> 
> How about BSD?  By the same argument, the place need not have anything to
> do with 386bsd except in so far as it deals with 386 implementation issues.
> 
> Sounds like an argument against moving away from comp.unix.bsd.

I didn't mean it to sound that way.  I happen to favor moving out of
comp.unix.bsd, based on my understanding of USENET convention and
newsgroup naming precedents (however limited my understanding of those
conventions may be).  I am not a militant on this issue, however.

I would point out that there are three semi-independent dimensions
(at least) which cause a newsgroup to exist.

1. Some newsgroups are roughly isomorphic to 'user communities'
centered around some system or concept.  This is an issue of social
togetherness.  It happens in nonelectronic life, too.  People at Apple
and people at IBM study networking, but do it seperately (in the pre
Pink era anyway :)).  They each form a distinct social group.  This is
what Lynne Jolitz (I think) is proposing for the 386bsd subgroups.
People who are together as concerns 386bsd *and* who want to also work
together on certain computer science problems, using 386bsd as a
social centrum.

2. Some newsgroups are explicitly devoted to a technical subject.

3. Some newsgroups are explicitly devoted to system administration
and implementation.

If I am interested in ppp, I subscribe to comp.protocols.ppp.  If I
want to see ppp run under 386bsd, I will follow any ppp thread I will
see under comp.os.386bsd.  In so far as I am starting to participate
in the 386bsd social community, I will monitor everything of interest
to me in comp.os.386bsd.

I am only arguing to be very careful about creating groups which
contain the cross product of reasons 2 and 3, while acknowledging that
reason 1 does naturally lead to such fragmentation.

My main point is that splitting 386bsd will not be easy, may not be
desirable, and should only occur without undue presciption.  As for
seperating 386bsd from bsd, it is already happening!.  Based, of
course, on the fact that the 386bsd user community has already copted
comp.unix.bsd as its forum.

Dennis
allard@isi.edu
Newsgroups: comp.unix.bsd
From: tgt@neon.ecn.purdue.edu (Conan the Librarian)
Subject: More on X386 1.2E 1.0.1 startup problems
Organization: Purdue University Engineering Computer Network
Distribution: usa
Date: Tue, 8 Sep 1992 04:58:13 GMT

Regarding my being unable to startup X386 1.2E on my system
(I get a blank screen and then nothing...apparently xinit is 
gagging) someone suggested that the 386bsd kernel packed with
the X386 1.2E 1.0.1 binaries on agate.berkeley.edu doesn't work.
Is this true?  If so, could someone either A) tell me where
I can get a kernel which will work with X386 or B) tell me
what the kernel problem is and where the patches are, so I
can attempt a kernel remake myself?

Lastly, is anyone going to place the X386 1.2E 1.0.2 binaries
in an archive, like on agate?  I keep hearing people say
"check the pub/incoming/X386 directory" but boys, there's
nothing there!

Thanks.

-tom
--
Tom Tobin				UUCP:     pur-ee!tgt	
Dept. of ChE				INTERNET: tgt@ecn.purdue.edu
Purdue University			Ma Bell:  home (317) 463-0189
W. Lafayette, IN 47907				  office "   494-4052 
Newsgroups: comp.unix.bsd
From: bdale@col.hp.com (Bdale Garbee)
Subject: Re: 386bsd -- The New Newsgroup
Date: Tue, 8 Sep 1992 20:35:03 GMT
Organization: HP Colorado Springs Division

wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
> 	comp.os.386bsd		(general questions and trivia)
> 	comp.os.386bsd.kernel	(discussion on kernel content/structure)
> 	comp.os.386bsd.windows	(ditto, on windowing systems like X)
> 	comp.os.386bsd.sharedlib (shared library and programming environment)
> 	comp.os.386bsd.net	(networking topics)
> 	comp.os.386bsd.bugs	(new bugs)
> 	comp.os.386bsd.ann	(announcements, fixes, additions)

Actually, I'd probably be more interested in seeing a single comp.os.386bsd
than in seeing a set of groups this fragmented.  Good threaded user interfaces
make keeping discussions together easy, and it takes less time and effort to
keep up with if it's all in one place...

But I'd be supportive regardless.

Bdale
Newsgroups: comp.unix.bsd
From: gottloeb@eel.dsd.trw.com (Jeffrey R. Gottloeb)
Subject: Re: ghostscript under 386BSD?
Organization: TRW, INC.
Date: Fri, 11 Sep 1992 18:41:07 GMT

In article <s-vn48f.alm@netcom.com> alm@netcom.com (Andrew Moore) writes:
>Ghostscript is part of the /etc distribution of 386bsd. I rebuilt it
>using the default makefile (for epson device). But when invoked it dies
>with diagnostic:
>
>Initializing... Zget t_string 256 >= 256
>Unrecoverable error: rangecheck in get
>Operand stack:
>    256 [...]
>
>Before I attempt to wade through the code, I was hoping someone might
>have fixed this.  Any ideas?  Anyone else successfully using ghostscript
>under 386bsd?  Thanks.
>-Andrew Moore <alm@netcom.com>


I noticed this problem too.  I believe is a compiler problem.  If
ghostscript is compiled without optimization and with debug, floating
point exceptions are generated.  I have tracked the problem as far as
when the setscreen command in gs_init.ps is being interpreted.

There is a notation in the PROBLEMS file for gcc that the compiler
generates bad code on a 386 for certain cases of floats.

I am trying to build gcc-2.2.2 on my system as we speak.  Perhaps this
will clear up the problem when i recompile ghostscript with it.


Jeff Gottloeb
gottloeb@gumby.dsd.trw.com
Xref: sparky comp.unix.bsd:5286 comp.windows.x:16318
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd,comp.windows.x
Subject: X386 patch
Date: 8 Sep 92 12:58:47 GMT
Organization: AIAI, University of Edinburgh, Scotland

I had a problem with X under 386BSD (on an Elonex 33MHz 386 with Genoa
SVGA) that the CRTC registers weren't being set, so the display was
completely trashed.  This turns out to be because the bit in CRTC
register 17 that prevents writing to CRTC registers 0-7 was set
(presumably the BIOS sets it when it's booted - I don't know why).
The solution is to clear this bit before setting the other registers.

Here's the patch:

*** ddx/x386/vga/vgaHW.c.orig	Mon Aug 26 20:43:24 1991
--- ddx/x386/vga/vgaHW.c	Tue Sep  8 12:51:48 1992
***************
*** 125,130 ****
--- 125,134 ----
    for (i=0; i<16; i++) { outb(0x3C0,i); outb(0x3C0, restore->Attribute[i]); }
    for (i=16; i<21;i++) { outb(0x3C0,i | 0x20);
  			 outb(0x3C0, restore->Attribute[i]); }
+ 
+   /* Ensure CRTC registers 0-7 are writable by clearing bit 7 of register 17 */
+   outw(vgaIOBase + 4, ((restore->CRTC[17] & 0x7f) << 8) | 17);
+ 
    for (i=0; i<24; i++) outw(vgaIOBase + 4,(restore->CRTC[i] << 8) | i);
    for (i=0; i<9;  i++) outw(0x3CE, (restore->Graphics[i] << 8) | i);

-- Richard
-- 
Richard Tobin,
AI Applications Institute,                                R.Tobin@ed.ac.uk
Edinburgh University.
Newsgroups: comp.unix.bsd
From: rcd@raven.eklektix.com (Dick Dunn)
Subject: Re: 386bsd -- The New Newsgroup
Organization: eklektix - Boulder, Colorado
Date: Thu, 10 Sep 1992 02:49:10 GMT

scs@iti.org (Steve Simmons) writes:
>The problem with `386bsd' is that the name is inherently confusing.  The
>casual reader will not be able to distinguish it from BSDI nor from the
>many other x86 commercial Unixes.

The names 386BSD and BSD/386 (the free system and the BSDI system) are
similar enough to the casual first-time reader to cause confusion regard-
less of a newsgroup name.  Better to have [a part of] the newsgroup name
precisely match what you're talking about--in this case, 386bsd.

I don't see any chance for confusing the name 386bsd with any of the "other
x86 commercial Unixes"--they're just "not BSD" enough to confuse anyone.

>I would strongly suggest forming comp.unix.freebsd...

Whatever direction it goes, I think it's time to get it out of the
comp.unix hierarchy.  There's always been this minor argument about the
inconsistency of comp.unix.* vs comp.os.<whatever-os-name>.*, but things
have stayed under comp.unix because of the inertia.  Consider USL's legal
maneuvering and their very strong desire not to have the word "UNIX"
associated with anything we'll talk about here.  Also consider that nothing
now sold under the UNIX trademark has any of the original important charac-
teristics of the UNIX system.  Really, comp.unix.* just doesn't fit.
-- 
Dick Dunn    rcd@raven.eklektix.com   -or-   raven!rcd    Boulder, Colorado
   ...intel happens!
Newsgroups: comp.unix.bsd
Subject: Help with 386BSD Kernel Recompile
From: <AI4CPHYW@MIAMIU.BITNET>
Date: Sunday, 13 Sep 1992 15:38:17 EDT
Organization: Miami University - Academic Computer Service

I have been trying to recompile the kernel with no luck.  I patched the
makefile, and carefully followed the instructions provided in the ROADMAP
file.  (config MACHINE cd to compile/MACHINE make depend, then make) The
make depend flies fine, but the make just kinda hangs.
 
I looked at the archives of the group and I see some others have been having
the same problem, but I haven't seen a definitive fix or patch or workaround.
I would appreciate it if someone could let me know how to fix this.
 
I will summarize via e-mail or to the net (if there is enough demand).
 
                      -Alec D. Isaacson
                       AI4CPHYW @ miamiu.acs.muohio.edu
                       isaacson @ rogue.acs.muohio.edu (NeXt Mail)
                       Miami University, Oxford, OH
-------------------------------------------------------------------------
This one is from Ohio, where we learned to dance the lambada.
                                     -Some lady in a Burger King Commercial
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: Re: network.... :-(
Date: 9 Sep 92 19:40:40 GMT
Organization: ICEM Systems, Inc.

In article <47333@shamash.cdc.com>, pbd@runyon.cim.cdc.com (Paul Dokas) writes:
|> I can't seem go get my machine to start up the network properly.
|> 
|> I have a generic 386-40 with a Western Digital ethernet card in it.
|> The card is recognized at boot time, but /etc/netstart doesn't ifconfig
|> the card.  So I typed in:
|> 
|>    /etc/ifconfig we0 inet 129.179.44.31 up netmask 0xffffff00 broadcast 129.179.44.255
|> 
|> and the machine starts putting this to my console:
|> 
|>    reject 65531reject65531reject65531.........
|> 
|> repeating every second or so.  I've read the FAQ and other instructions, but I
|> can't find any relevant info.  Any help is greatly appreciated!
|> 
|> BTW I've tried simplifying the ifconfig command by leaving off broadcast, netmask, and up
|> but I always get the reject65531 response.

Sorry about the vagueness of this message, but I was in a hurry and forgot some very
important stuff...

First of all, could this problem be caused because I've hooked up my ethernet
cable to the AUI connector on the card (a WD8003 BTW)?

If this is the problem, then how to I get it to recognize the AUI instead
of the BNC connector?

Also, as I just mentioned, my card is a Western Digital 8003.  Is this card
OK?  I seem to remember it being on the list of "OK" cards, but I could
very well be wrong.
-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/* we are realizing infinite possibilities in exchange for our soul */
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: 16550; 386BSD 0.2; Kernel-Book
Date: 15 Sep 1992 08:53:27 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <mav02545920811222413@encap.hanse.de>, mav@encap.hanse.de (Jan-Oliver Neumann) writes:
>     I have a  couple of questions  that hopefully haven't  been answered to
>     many times before:
> 
>     b) Is  there any estimate for  386BSD 0.2 ? When  will it be available,
>     what will be new/fixed ?

Somewhere in the release notes it says that the distribution sites are
supposed to carry the unofficial *directory* and the patches *directory and
contents* except that upto now there don't seem to be any *official* patches.

I'd say - forget about 0.2 until there's at least one official patch.

BTW while we're at it - is anybody working on a concept of upgrading 0.1 to
0.2 so that we don't go re-formatting and re-disklabelling and re-newfsing
and re-installing (once it actually happens) ? - Just a thought.

-Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: tri@niksula.hut.fi (Timo Rinne)
Subject: 386BSD #!/bin/csh
Reply-To: Timo.Rinne@hut.fi
Organization: Helsinki University of Technology
Distribution: comp
Date: 9 Sep 92 01:12:02

386bsd 0.1 doesn't seem to respect #! in beginning
of the shell scripts, Anyone knows why? Fixes?

-- 
  I Timo Rinne         I Cirion oy      I Working computer hardware is a lot I
  I Timo.Rinne@hut.fi  I PL 250         I like an erect penis: It stays up   I
  I tri@cirion.fi      I 00120 HELSINKI I as long as you don't fuck with it. I

     Hi! I am a .signature virus. Copy me into your .signature to join in!
Newsgroups: comp.unix.bsd
From: wolfy@ba.ncu.edu.tw (Jann-Yea Sue)
Subject: Re: zsh for 386bsd
Reply-To: wolfy@ba.ncu.edu.tw
Organization: Sun Microsystems, Inc.
Date: Tue, 8 Sep 1992 11:01:49 GMT



Newsgroups: comp.unix.bsd