| View previous topic :: View next topic |
| Author |
Message |
shazbotus
n00b
Joined: 28 Jun 2003
Posts: 24
Location: Duke Univ.
|
 Posted: Sun Jun 29, 2003 9:20 pm Post subject: X starts, keyboard and mouse freeze (UPDATE) must see fix |
 |
|
Ok when I start X, my mouse and keyboard freeze, but now that I set up aewm++ i was at least able to get into it. I watched the clock and that actually changed, so the computer wasnt frozen. However, the mouse and keyboard were completely worthless. I couldnt do anything with them. I have read a lot of other threads regarding nvidia drivers, but since the screen didnt freeze, i dont think thats the issue now.
I have a ps/2 mouse and keyboard and the keyboard is set to normal 101key and i would think that would at least work even if the mouse didnt. Well, neither of them do anything and I am getting frustrated. Im so close to a usable system with a gui.
It seems as if so many others in the forums are having these issues, but nobody can get an answer, or at least I am not seeing people responding like "w00t, it works now, thanks". So...any advice and definite fixes for this?
my XF86Config file
| Code: |
# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
# Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "D1025TM"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5-82.0
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-120
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "nv"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "XFX GeForce4 Ti 4200 128MB"
Driver "nvidia"
#VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "XFX GeForce4 Ti 4200 128MB"
Monitor "D1025TM"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
|
Last edited by shazbotus on Sun Jun 29, 2003 10:41 pm; edited 4 times in total |
|
| Back to top |
|
 |
marter
n00b
Joined: 29 Jun 2003
Posts: 37
|
|
| Back to top |
|
|
shazbotus
n00b
Joined: 28 Jun 2003
Posts: 24
Location: Duke Univ.
|
| Posted: Sun Jun 29, 2003 10:36 pm Post subject: fixed? |
|
|
| WOW, check out what I found. This could be the long lost fix for many Gentoo users and noobs that are confused. Go here. I am currently compiling gnome, but this could be our fix finally. At least it sounds reasonable and seems to be the problem I am experiencing.[/url] |
|
| Back to top |
|
|
marter
n00b
Joined: 29 Jun 2003
Posts: 37
|
| Posted: Sun Jun 29, 2003 11:10 pm Post subject: Re: fixed? |
|
|
| shazbotus wrote: | | WOW, check out what I found. This could be the long lost fix for many Gentoo users and noobs that are confused. Go here. I am currently compiling gnome, but this could be our fix finally. At least it sounds reasonable and seems to be the problem I am experiencing.[/url] |
interesting i will read this, but right im in installing it on my dell laptop
im following the install guide from gentoo.org its still going though the emerge xfree
the onbored video is ati i think rage mobility |
|
| Back to top |
|
|
shazbotus
n00b
Joined: 28 Jun 2003
Posts: 24
Location: Duke Univ.
|
| Posted: Tue Jul 01, 2003 2:38 pm Post subject: |
|
|
| I finished compiling gnome, and now I tried that fix and put in the options "IgnoreDisplayDevices" "DFP, TV" and "ConnectedDisplay" "CRT" but now when X would used to load but my mouse and keyboard froze, now my monitor also turns off and mouse and keyboard still freeze. Why are so many people having this problem and yet nobody seems to have an answer to it. Can somebody try to lead me through this...I am an ubernoob. TIA |
|
| Back to top |
|
|
shazbotus
n00b
Joined: 28 Jun 2003
Posts: 24
Location: Duke Univ.
|
| Posted: Tue Jul 01, 2003 2:42 pm Post subject: |
|
|
| Ok, i took those options back out and X will at least start and i can see fluxbox, its just that my mouse and keyboard will not do anything still. So, it seems I have narrowed it down to mouse and keyboard, both in PS/2. I have enabled lots of mice devices in the kernel and keyboard is not exactly a default one, but it works in the console, so even with a generic keyboard driver, i would think it would work. The only difference it has from a normal keyboard is the power/wake up/standby buttons. And I did try the ACPI keyboard choice. Maybe I will just let the computer sit there and see if it is just hanging. |
|
| Back to top |
|
|
aethyr
Veteran
Joined: 06 Apr 2003
Posts: 1085
Location: NYC
|
| Posted: Tue Jul 01, 2003 3:21 pm Post subject: |
|
|
shazbotus, why are you installing more software (gnome) on top of xfree when it's not currently working as it is?
If I was you, I would have stopped directly after the xfree installation, and not installed anything else until I got my mouse and keyboard working. It makes it a lot harder to get stuff working when you throw in more variables.
Anyways, I'll give you the advice I was going to give you before I read that part:
First, get rid of your XF86Config. I'm not sure how you generated yours, but I'd read over the Desktop Configuration Guide again:
http://www.gentoo.org/doc/en/desktop.xml
There's fairly explicit instructions on how to setup XFree86 in that guide. Also, looking at the documentation on xFree86.org I saw this little bit: | Quote: | | ...there are three ways to create a basic X server configuration file for XFree86 4.3.0. One is to run the xf86config utility. Another is to run the xf86cfg utility. The third option is to use the new -configure X server option: |
I'd follow those instructions and see where that gets you. Note that you're instructed to test the setup along the way (with `cat /dev/mouse` and starting X before you even install a window manager).
If that doesn't work, I'd do some more serious testing.
Again starting with no configuration file, I'd start with just a keyboard (no mouse plugged in) and setup X with just a keyboard (no mouse). I'd start X and see if I can get my keyboard to respond (should be able to type in xterm). If that works, then it's just a matter of getting your mouse to work. Since you said you keyboard worked outside of X, I'd assume that there's some problem between your keyboard and mouse in X. Which leads me to think that you set up your mouse incorrectly (what brand/model of mouse do you have?).
Anyways, spend some time reading through the instructions before you install more software, it'll save you headaches in the long-run. |
|
| Back to top |
|
|
shazbotus
n00b
Joined: 28 Jun 2003
Posts: 24
Location: Duke Univ.
|
| Posted: Tue Jul 01, 2003 3:49 pm Post subject: |
|
|
| I have a Logitech Optical Mouse (it is usb, but I am using the PS/2 adapter for simplicity and because I need the USB ports until I get a USB Hub). Also, I used xf86config like it said in the Desktop config guide. |
|
| Back to top |
|
|
shazbotus
n00b
Joined: 28 Jun 2003
Posts: 24
Location: Duke Univ.
|
| Posted: Tue Jul 01, 2003 4:03 pm Post subject: |
|
|
Holy COW!?!?!? I changed a few things in my BIOS and now the bloody thing works. The things I changed had to do with USB legacy support, but I am not even using USB for my connections. I also turned off the onboard midi and gameport, maybe that opened an IRQ or something that was necessary, maybe I will go back and test to find what it was exactly, but see...my setup was correct aethyr...no need to bash me. But I also understand, you would have no way of knowing how my BIOS was configured, and I should heed your advice in general for later troubleshooting. Im just happy it works.
Ok after doing several reboots and narrowing down the exact bios setting that was messing it all up, it ended up being the onboard MIDI. I had turned off the onboard audio a while back when I got my SB Live card, but the MIDI onboard is bad. It was taking IRQ 5 and could only be switched to IRQ 5, 10, or 11 and those other two were taken by my network cards, so MIDI had to go. And, now my mouse and keyboard, and GENTOO LINUX work.
Last edited by shazbotus on Tue Jul 01, 2003 4:15 pm; edited 1 time in total |
|
| Back to top |
|
|
aethyr
Veteran
Joined: 06 Apr 2003
Posts: 1085
Location: NYC
|
| Posted: Tue Jul 01, 2003 4:08 pm Post subject: |
|
|
shazbotus, sorry if I came across harsh, it's just difficult enough to troubleshoot some problems, and it makes it harder when someone's installed 20 extra packages on top of it ;)
But yea, in general it's best to takes things slow and in an orderly fashion, i.e. get one thing working before moving onto another.
Glad to hear your setup is working, I'll have to file this one away in memory in case I run across anyone with a similar issue. ^_^ |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
