*BSD News Article 9922


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA6808 ; Fri, 15 Jan 93 10:35:59 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!gatech!usenet.ins.cwru.edu!agate!boulder!ucsu!rintintin.Colorado.EDU!galbrait
From: galbrait@rintintin.Colorado.EDU (GALBRAITH JOHN)
Subject: Re: Still more XFree86 problems
Message-ID: <1993Jan7.210505.10226@ucsu.Colorado.EDU>
Sender: news@ucsu.Colorado.EDU (USENET News System)
Nntp-Posting-Host: rintintin.colorado.edu
Organization: University of Colorado, Boulder
References: <51098@shamash.cdc.com>
Date: Thu, 7 Jan 1993 21:05:05 GMT
Lines: 38

In article <51098@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
>I'm still having problems with XFree86.  When ever I run 'startx'
>or 'xinit' or 'X386 :0' the X server starts up, puts the screen
>into graphics mode (not clear) and just hangs.

   << much stuff deleted.  Impressive debugging, BTW  >>

>BTW, my problems might be due to the com ports that I have in my system.
>Here is a section of my config file:
>
>  device          com1    at isa? port "IO_COM1" tty irq 4 vector comintr
>  device          com2    at isa? port "IO_COM2" tty irq 3 vector comintr
>  device          com3    at isa? port 0x3e8 tty irq 4 vector comintr
>  device          com4    at isa? port 0x2e8 tty irq 3 vector comintr
>
>com1 and com2 are on a multi-io board (ide, fd, 2serial, 1parallel, 1game)
>and com3 and com4 are on a serial io card.  Com3 is a 16450, and com4 is
>a 16550.  They are all found and configured correctly at boot time.  My mouse
>is on com1 and my ascii terminal is on com3.
>
>Again, any help is greatly appreciated!
>-- 
>#include <std.disclaimer>
>#define FULL_NAME                          "Paul Dokas"
>#define EMAIL                              "pbd@runyon.cim.cdc.com"
>/*            Just remember, you *WILL* die someday.             */

I tried configuring more than one serial port in this way also, and it hangs
due to an interrupt conflict, I think.  The solution is to use a new com 
driver that can share interrupts.  One was written called com-multiport by 
Chris Demetriou (cgd@berkeley.edu).  I could not get it to work myself,
but it was probably due to my own cluelessness more than the driver.  I
forgot where I found it, but it was nowhere exotic.

john galbraith
galbrait@rintintin.colorado.edu