Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Help, XDM failure to load Keyboard Module in 2.6.10r5
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
eaZy
n00b
n00b


Joined: 19 Aug 2004
Posts: 16
Location: Sydney

PostPosted: Wed Jan 19, 2005 12:26 pm    Post subject: Help, XDM failure to load Keyboard Module in 2.6.10r5 Reply with quote

I have some problems about upgrading my kernel from 2.6.8-r3 to 2.6.10-r5:

I have followed this gentoo guide (Kernel Upgrade) completely:

http://www.gentoo.org/doc/en/kernel-upgrade.xml

and no issues there during the whole time of configuring, installing and compiling.

I have however automerged the files during "etc-update".

Now I was still in my 2.6.8-r3 then and I configured my grub.conf for my newly installed 2.6.10-r5 and rebooted - and then the problem came.

First, I could not go into gnome anymore - this was expected as my nvidia module will have to be linked again to the new kernel I just installed. So while in command prompt I logged in as root successfully and emerged
Code:
nvidia-kernel
and
Code:
nvidia-glx
hoping that after that things will be fine.

Well sort of, except i got graphics after emerging them and i rebooted. However it was not gnome, it seemed like something like plain xdm (with only xterms available)

So I emerged gnome AND xorg-x11 again - thinking I mite have done something stupid merging files while in etc-update earlier.

At that time I also upgraded all my system modules by typing:

emerge -Upd system

Anyhow after all that, I have now hit a wall.

Upon loading XDM - there are 3 errors which disable me to launch gdm and gnome:

Code:

(EE) Failed to load module "Keyboard" (module does not exist, 0)
(EE) No Input driver matching `Keyboard'
No core keyboard

Fatal server error:
failed to initialize core devices
...

xdm error (pid 7305): IO Error in XOpenDisplay
xdm error (pid 7301): Display :0 cannot be opened


Now the same is said for my Xorg.0.log:

Code:

(EE) Failed to load module "Keyboard" (module does not exist, 0)
...
(EE) No Input driver matching `Keyboard'


Does anyone know what is wrong??! Or have I missed something when I tried to upgrade my kernel?

PS: I tried typing startx after all this while in command prompt (after failing to load gdm) it says Command not found. 8O

Also im still using my old xorg.conf file for my 2.6.10-r5 since I didnt do any merging of files after emerging nvidia-kernel and nvidia-glx.


Last edited by eaZy on Wed Jan 19, 2005 12:35 pm; edited 3 times in total
Back to top
View user's profile Send private message
eaZy
n00b
n00b


Joined: 19 Aug 2004
Posts: 16
Location: Sydney

PostPosted: Wed Jan 19, 2005 12:27 pm    Post subject: Reply with quote

My Xorg.conf:

Code:

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)
#
#

     FontPath   "unix/:-1"

#    FontPath   "/usr/share/fonts/100dpi/"
#    FontPath   "/usr/share/fonts/75dpi/"
#    FontPath   "/usr/share/fonts/artwiz"
#    FontPath   "/usr/share/fonts/baekmuk"
#    FontPath   "/usr/share/fonts/CID/"
#    FontPath   "/usr/share/fonts/corefonts/"
#    FontPath   "/usr/share/fonts/cyrillic/"
#    FontPath   "/usr/share/fonts/encodings/"
#    FontPath   "/usr/share/fonts/freefonts/"
#    FontPath   "/usr/share/fonts/local/"
#    FontPath   "/usr/share/fonts/misc/"
#    FontPath   "/usr/share/fonts/sharefonts/"
#    FontPath   "/usr/share/fonts/Speedo/"
#    FontPath   "/usr/share/fonts/terminus/"
#    FontPath   "/usr/share/fonts/ttf/"   
#    FontPath   "/usr/share/fonts/TTF/"
#    FontPath   "/usr/share/fonts/ttf-bitstream-vera/"
#    FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/ukr/"
#    FontPath   "/usr/share/fonts/unifont/"
#    FontPath   "/usr/share/fonts/util/"
   
# 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 Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc101"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"   "xorg"
    Option "XkbModel"   "microsoft"
    Option "XkbLayout"   "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier   "Mouse1"
    Driver   "mouse"
    Option "Protocol"    "IMPS/2"
    Option "Device"      "/dev/psaux"
    Option "Buttons" "5"
    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 xorg.conf 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  "Samsung SyncMaster 955DF"

# 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   30-85

#    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-160

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     "vga"
# 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 xorgconfig:

Section "Device"
    Identifier  "NVIDIA GeForce3 Ti500"
    Driver      "nvidia"
    Option    "UseEdidFreqs" "true"
    Option    "DigitalVibrance" "100"
    Option    "RenderAccel" "true"
    Option    "NoLogo" "true"
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      "NVIDIA GeForce3 Ti500"
    Monitor     "Samsung SyncMaster 955DF"
    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
Back to top
View user's profile Send private message
steve_d555
Guru
Guru


Joined: 07 Nov 2004
Posts: 458
Location: Belmont, Massachusetts

PostPosted: Wed Jan 19, 2005 1:54 pm    Post subject: Reply with quote

I'm going to assume you are using Xorg-6.8.0 and say that there is no such thing as a Keyboard driver it has been changed to "kbd"

Code:

    Identifier   "Keyboard1"
    Driver   "Keyboard"


Should be
Code:

    Identifier   "Keyboard1"
    Driver   "kbd"


--Steve
Back to top
View user's profile Send private message
eaZy
n00b
n00b


Joined: 19 Aug 2004
Posts: 16
Location: Sydney

PostPosted: Wed Jan 19, 2005 10:12 pm    Post subject: Reply with quote

Ok thanks mate!! I will try to change it now!

Keep u updated
Back to top
View user's profile Send private message
eaZy
n00b
n00b


Joined: 19 Aug 2004
Posts: 16
Location: Sydney

PostPosted: Wed Jan 19, 2005 10:35 pm    Post subject: Reply with quote

It all works now!! Thanks alo! :P
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
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