On Wed, Sep 13, 2000 at 10:13:43PM -0400, Zephaniah E. Hull wrote:
On Wed, Sep 13, 2000 at 10:00:06PM -0400, [EMAIL PROTECTED] wrote:
snip
I also resolved mouse issues I had by changing the repeat_type value in
/etc/gpm.conf to "raw" ... /dev/gpmdata was causing erratic behavior
before
On Wed, Sep 13, 2000 at 10:13:43PM -0400, Zephaniah E. Hull wrote:
On Wed, Sep 13, 2000 at 10:00:06PM -0400, [EMAIL PROTECTED] wrote:
snip
I also resolved mouse issues I had by changing the repeat_type value in
/etc/gpm.conf to raw ... /dev/gpmdata was causing erratic behavior
before
On Tue, 12 Sep 2000 at 16:03:53 -0700, Marc Martinez [EMAIL PROTECTED] wrote:
Load "/usr/X11R6/lib/modules/extensions/libglx.so"
You were absolutely right -- replacing "glx" with the above
did the trick. I don't know why I missed this, as I got 4.0.1
working on a different debian box
On Wed, Sep 13, 2000 at 10:00:06PM -0400, [EMAIL PROTECTED] wrote:
snip
I also resolved mouse issues I had by changing the repeat_type value in
/etc/gpm.conf to "raw" ... /dev/gpmdata was causing erratic behavior
before (gpm's fault, not X). So now gpm and X get along well, so
everything
On Wed, 13 Sep 2000, Zephaniah E. Hull wrote:
Repeat in what gpm calls ms3 and what X calls IntelliMouse.
Unless you really LIKE shooting yourself in the foot.
That worked also (ie, same result as type "raw" in gpm.conf and "IMPS/2"
in XF86Config) ... I assumed that repeat type "imps2"
Though in bad taste, I'll reply above but leave the message intact
below.
In all protocols except ms3/IntelliMouse X4 attempts to communicate with
the mouse, trying this into a fifo is, err, a bad idea, largely because
X4 gets it right back as if it was sent by the mouse, resulting in the
On Tue, 12 Sep 2000 at 16:03:53 -0700, Marc Martinez [EMAIL PROTECTED] wrote:
Load /usr/X11R6/lib/modules/extensions/libglx.so
You were absolutely right -- replacing glx with the above
did the trick. I don't know why I missed this, as I got 4.0.1
working on a different debian box
On Wed, Sep 13, 2000 at 10:00:06PM -0400, [EMAIL PROTECTED] wrote:
snip
I also resolved mouse issues I had by changing the repeat_type value in
/etc/gpm.conf to raw ... /dev/gpmdata was causing erratic behavior
before (gpm's fault, not X). So now gpm and X get along well, so
everything works
On Wed, 13 Sep 2000, Zephaniah E. Hull wrote:
Repeat in what gpm calls ms3 and what X calls IntelliMouse.
Unless you really LIKE shooting yourself in the foot.
That worked also (ie, same result as type raw in gpm.conf and IMPS/2
in XF86Config) ... I assumed that repeat type imps2 would be
Though in bad taste, I'll reply above but leave the message intact
below.
In all protocols except ms3/IntelliMouse X4 attempts to communicate with
the mouse, trying this into a fifo is, err, a bad idea, largely because
X4 gets it right back as if it was sent by the mouse, resulting in the
erratic
On Sat, 9 Sep 2000 20:57:16 -0700, Josh Carroll [EMAIL PROTECTED] wrote:
I just recently updated to the phase2 debs (version4), and all I get is
sig11 constantly, at random times. Sometimes as soon as I start X,
sometimes no for almost an hour. It varies, but it NEVER stays resident
more
On Sat, 9 Sep 2000 20:57:16 -0700, Josh Carroll [EMAIL PROTECTED] wrote:
I just recently updated to the phase2 debs (version4), and all I get is
sig11 constantly, at random times. Sometimes as soon as I start X,
sometimes no for almost an hour. It varies, but it NEVER stays resident
more
On Tue, Sep 12, 2000 at 05:57:51PM -0400, [EMAIL PROTECTED] wrote:
FWIW, I've been using the phase1 debs of X4.0.1 with the 0.9.4 NVidia
drivers on a GeForce2, and haven't had any sig11's -- but the server hangs
(and the displacy is garbled, have to reboot blindly) if the line
#Load
Josh, I have two main thoughts. First, try to do something like compile
your kernel (when running in a text console :) to make sure your memory
isn't running beyond its limits. If you can compile kernels fine, then
you probably have fine memory. :)
I was getting signal 11s when I had my sync
Josh Carroll wrote:
I just recently updated to the phase2 debs (version4), and all I get is
sig11 constantly, at random times. Sometimes as soon as I start X, sometimes not
for almost an hour. It varies, but it NEVER stays resident more than an hour or
two. This is really annoying, and I'm not
Josh, I have two main thoughts. First, try to do something like compile
your kernel (when running in a text console :) to make sure your memory
isn't running beyond its limits. If you can compile kernels fine, then
you probably have fine memory. :)
I was getting signal 11s when I had my sync
16 matches
Mail list logo
