Re: XFree install problem: keyboard/mouse event hell
On Wed, Oct 30, 2002 at 10:26:22AM +0100, Fritz Jetzek wrote:
> Hi,
>
> I have been trying to install XFree86 4.2.1. on a beige G3. The
> server starts up alright but mouse and keyboard interaction are
> borked: pressing any key results in lots of characters per key
> press, the characters do not match the key pressed. Clicking mouse
> buttons results in equally many events which result in menu dialogs
> popping up a dozen times and closing again (I start with gdm). Is
> there an easy fix to this? I still use the old Xpmac server 3.3
> which works quite alright (but I need the GLX extension which the
> old server does not support).
Well, I am running the Woody XFree86 4.1 on a beige G3, but it has
been a while since I set it up, and I forget some of the details.
First, it works with both Woody kernels (2.2 and 2.4), so that is not
exactly a problem. What *is* a problem is that you are using an old
kernel that sends ADB keycodes instead of using the "new input layer".
You should look at the notes on that at the powerpc port page on the
Debian website.
If I'm guessing right, the simplest solution to your problems may be
to upgrade to the Woody 2.2 kernel, and then run the Woody XFree86
4-1. A copy of my XF86Config-4 is attached, but you'll need to make
some modifications. (I installed a USB card, and mainly use a USB
mouse, though my ADB mouse is working too. They both go through gpm.
Also, it sounds as though you are getting a working video mode, so you
should use that and delete my fiddling with the video modes.)
Alternatively, you can proceed with getting XFree86 working with your
current kernel. I'm going to make some comments about this because it
is interesting, but it is probably better avoided unless you have some
strong reason to stay with your current kernel. The main danger is
that you get stuck in an unusable X and reboot the machine, which is
not good for the filesystems. So start by finding a clean way to kill
X. In your situation, there *is$ a weird three-key version of
CTL-ALT-DELETE, which you can work out from that web page (but I
forget what it is). Alternatively, you can "chvt 1", but that
requires root privileges in the default setup. Another trick: write a
little shell script to get you out, and give it a name like "aa" that
you can figure out how to produce despite the mangled keycodes. Thus,
if you start X as root, and "aa" is either a script or aliased to
"chvt 1", you have an escape method.
While you are still struggling, "killall gdm" may be a good idea. It
does not kill a running X, but it prevents X from being automagically
restarted.
To actually fix the keycodes, I think you can use "xmodmap"
from within Xpmac to save what it thinks are the keycodes, then load
that file into the other X.
--
John (MacPhail)
### BEGIN jrm SECTION
#
# Define modes for "Macintosh Color Display" based on results of xvidtune.
# The "640x480" modeline will override the default VESA 640x480.
Section "Modes"
Identifier "MCD Modes"
Modeline "640x480" 31.50 640 676 740 852 480 481 484 512 -hsync -vsync
EndSection
# for this to be accessible, insert a line
# UseModes "MCD Modes"
# into the Monitor section for the Macintosh Color Display.
#
### END jrm SECTION
### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make changes
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
# dpkg-reconfigure xserver-xfree86
# as root. Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.
Section "Files"
FontPath "unix/:7100" # local font server
# if the local font server has problems, we can fall back on these
FontPath "/usr/lib/X11/fonts/misc"
FontPath "/usr/lib/X11/fonts/cyrillic"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Type1"
FontPath "/usr/lib/X11/fonts/Speedo"
FontPath "/usr/lib/X11/fonts/100dpi"
FontPath "/usr/lib/X11/fonts/75dpi"
EndSection
Section "Module"
Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "pex5"
Load "record"
Load "speedo"
Load "type1"
Load "vbe"
Load "xie"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "macintosh"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection
Section "Device"
Identifier "ATI 3D RAGE GT"
Driver "ati"
BusID "PCI:0:18:0"
Option "UseFBDev" "true"
EndSection
Section "Monitor"
Identifier "Macintosh Color Display"
HorizSync 28-50
VertRefresh 43-75
UseModes "MCD Modes"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI 3D RAGE GT"
Monitor "Macintosh Color Display"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "640x480"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection
Section "DRI"
Mode 0666
EndSection
### END DEBCONF SECTION
Reply to: