Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!noiro.acs.uci.edu!ucivax!ucla-cs!ucla-mic!scott From: scott@pita.cns.ucla.edu (Scott Burris) Subject: 386BSD: bus mice, S3 X11 driver, NFS, and dump Message-ID: <1992Jun29.125958.20044@mic.ucla.edu> Nntp-Posting-Host: pita.cns.ucla.edu Reply-To: scott@pita.cns.ucla.edu (Scott Burris) Organization: UCLA Campus Network Services Date: 29 Jun 92 12:59:58 PDT Lines: 41 I was up very late Satuday night working on an S3 driver for Pace's X11R5 port to 386BSD (until the 7.4 earthquake hit, but that's another story) and I've found that there's no bus mouse driver. Does anyone know what the interface to the bus mouse looks like or can you point me to some book or documentation somewhere? I had to borrow a serial mouse from another machine (I'm using an STB WIND/X which is an S3 based board with a built in bus mouse). Given that the S3 technical manual is a model of clarity, I've so far managed to get the driver to put some light on the screen, with some black dribbles sprinkled around for emphasis. When I get it fixed, I'll post it to the net. My intention is for 2 phases. The first (and easy) phase is to get the driver to just function properly as a SVGA. The second (much harder I think) phase will be to start using some of the GUI acceleration hardware. Has anyone done any kind of a study of X11 as far as what kinds of graphics operations would benefit most from this? On the subject of NFS operations hanging, how many patches are there on the net for NFS? I've installed the authentication fixes (vfs__bio.c) and the magic "if the length is negative, set it to 0" patch. Any others? I'm still encounting hangs when trying to use tar on 386BSD to dump a Novell fileserver accessed via NFS using Son of Stan's Server to a SCSI DAT tape using Pace's SCSI driver (you don't really want to ask me why I'm doing this....) Lastly, I foolishly tried using dump again last night and clobbered my /usr filesystem. I put in the *filesystem fix and set the number of slaves to 1. Still get the bad disk label message. I suppose these changes made thing marginally better because the previous time I trashed the root filesystem and had to reconstruct things from floppy. At least I was still able to boot this time. Anyone heard if there's a new date for release 0.1? I think we need to get back to a common code base -- I no longer have any idea if my kern_execve.c file looks anything like anyone elses any more :-) -- ---------- Scott Burris UCLA Campus Network Services cnetslb@oac.ucla.edu (213) 206-4860 - OR - scott@pita.cns.ucla.edu