On Thu, Apr 08, 1999 at 03:05:18PM -0400, d.r.stewart wrote:
> On  8 Apr 99 at 0:10, [EMAIL PROTECTED] wrote:
> > 
> > and COM2.  Your mouse is on COM1, since you mention that it's
> > reported as irq 4. So, the kernel sees the mouse.  One thing to
> > check would be /proc/interrupts to ensure that nothing else is
> > grabbing that interrupt.  If anything other than 'serial' is listed
> > there, you've got a conflict that you'll need to sort out.
> 
> here's the output of /proc/interrupts:
> 
> 0:   1309076     timer
> 1:         3371    keyboard
> 2:              0    cascade
> 4:            14 + serial
> 7:             0     plip1
> 8:             1 +  rtc
> 13:           1     math error
> 14:    36388 +  ide0
> 15           12 + ide1

Okay, that looks fine.  Didn't you mention that dmesg also saw a com2?  It
doesn't seem to be listed in /proc/interrupts.  Check your
BIOS/modem/whatever to make sure that it's not conflicting.

> > Is gpm running when you attempt to start X?  You might try killing
> > the gpm daemon and then attempting X.  I know it _used_ to conflict,
> > but I don't know whether that's true anymore.  To kill it, just use
> > '/etc/rc.d/init.d/gpm stop'.  Then try 'startx' to bring up X.  Any
> > better luck?
> 
> yes it was running. hmm, another set of lovely error msgs:
> 
> execve failed for /etc/X11/X  (errno 2)
> _X11TransSocketUNICConnect: Can't connect: Errno = 111
> giving up
> xinit: connection refused ( ernno 111): unable to connect to  X 
> server
> xinit: no such process ( errno 3) server error 

Okay, a couple of things.  First, the error that it's got there is about it
being unable to run X.  Check to make sure that /etc/X11/X links to your
specific X server in /usr/X11R6/bin/.
 
> restartd gmp
> same msg

Don't restart it, kill it.  (/etc/rc.d/init.d/gpm stop)
 
> > Drop a note back to the list with an update of what happened with
> > these tests, one of them SHOULD fix it, but if not, it'll narrow
> > down the problem.
> 
> this is starting to get fun here ;-). good thing i'm stubborn and 
> refuse to give up or is that becuz i've had enough of winbloat <g>.

Doesn't really matter at this point, does it?  :)
 
-- 
Steve Philp
[EMAIL PROTECTED]

Reply via email to