Re: Input lockup problem

2003-01-31 Thread Mike M
On Friday 31 January 2003 16:30, nate wrote: > Michael Mueller said: > > I tried commenting out the whole Generic Mouse section in XF86Config-4. > > I get no mouse control at all and I must telnet in to uncomment the > > section and init 6 the box. > > what about keyboard control? CTRL+ALT+BACKSP

Re: Input lockup problem

2003-01-31 Thread nate
Michael Mueller said: > I tried commenting out the whole Generic Mouse section in XF86Config-4. I > get no mouse control at all and I must telnet in to uncomment the section > and init 6 the box. what about keyboard control? CTRL+ALT+BACKSPACE should kill the X server. Not sure if your using a

Re: Input lockup problem

2003-01-31 Thread Michael Mueller
On Friday 31 January 2003 15:00, nate wrote: > Mike M said: > > I am running vanilla Debian 3.0, KDE 2.2, and KDM. This system locked > > its input twice since I built it in December last year. Today, when it > > happened, I tried to telnet in but the box would not respond to a ping. > > perhaps

Re: Input lockup problem

2003-01-31 Thread Michael Mueller
On Friday 31 January 2003 14:59, Mark Laird Copper wrote: > I don't think your problem is the mouse. To see this paste your "server > layout" section to the head of your /etc/X11/XF86config-4 file and > delete the "Generic Mouse" line. At least this eliminated the mouse > errors from my log but n

Re: Input lockup problem

2003-01-31 Thread Mark Laird Copper
I don't think your problem is the mouse. To see this paste your "server layout" section to the head of your /etc/X11/XF86config-4 file and delete the "Generic Mouse" line. At least this eliminated the mouse errors from my log but not my lock-up problems. MC On Fri, Jan 31, 2003 at 12:45:58PM -0

Re: Input lockup problem

2003-01-31 Thread nate
Mike M said: > I am running vanilla Debian 3.0, KDE 2.2, and KDM. This system locked its > input twice since I built it in December last year. Today, when it > happened, I tried to telnet in but the box would not respond to a ping. perhaps it's a driver bug? see this: http://xfree86.desiato.