Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA756 ; Sun, 07 Feb 93 09:01:15 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw From: osynw@gemini.oscs.montana.edu (Nate Williams) Subject: Re: [386bsd] XFree88 Still Chewing [was Re: Does XFree86 work with patchkit 0.2?] Message-ID: <1993Feb6.170259.24702@coe.montana.edu> Keywords: n Sender: usenet@coe.montana.edu (USENET News System) Organization: Montana State University References: <51995@seismo.CSS.GOV> <1993Feb5.184620.26347@coe.montana.edu> <JKH.93Feb6114917@whisker.lotus.ie> Date: Sat, 6 Feb 1993 17:02:59 GMT Lines: 25 In article <JKH.93Feb6114917@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes: >It does work, but it also *loops* now (I.E. eats a lot of CPU time it >shouldn't be eating). > >This didn't begin happening until post 0.2. I even reloaded all the >386bsd sources from tape, reapplied patckit 0.2 and recompiled the >world from *scratch* just on the off-chance that some of my own >earlier hackery had caused it. Nope. No difference. That is because select no longer works in the com driver like it did before. The stock com "driver" needs to be updated because of a change Bill made in patch0061. Chris Demetriou's driver has been changed, and changes have been posted for the busmouse drivers, so it is fairly trivial. I would even do it today, but my ethernet board went belly up yesterday, and I can't logon to my computer, and the building is locked where it's at. Until the com driver gets updated, get Chris's driver. Nate -- osynw@terra.oscs.montana.edu | A hacker w/out a home. work: (406) 994-5991 | Keeper of the Unofficial 386BSD Bug Report home: (406) 586-0579 | Please send bugs and/or fixes you find.