Keyboard unrecognized prior to startx

To start off, I have an Apple Extended Keyboard II that I scrounged out of a closet back home. It's connected via USB through one of these.
So this weird setup is functional in the BIOS and in the bootloader (GRUB2), but once I get to Arch's login prompt its input is no longer recognized.
I can hook up a regular keyboard (USB) and log in, then after I startx and load Cinnamon the Apple keyboard works great. In fact I can switch to another virtual terminal and then log in. If I press caps lock on the normal keyboard at the (initial) Arch login the Apple keyboard's light comes on, so it is powered and presumably recognized as a keyboard.
I feel like I'm missing something key in Arch's boot process. Thanks for any help.
Notes:
I used this keyboard for the Arch installation process.
Mobo: GA-Z77-UD5H
I can say this setup works fully in Windows and OS X on the same hardware.

Thanks for the help.
Before startx
dmesg
lsusb -v
lsmod
After startx
dmesg
lsusb -v
lsmod
diffs
dmesg
lsusb was the same
lsmod
So, I see the iMate device listed in the dmesg output both before and after. The diff content all seems to be graphics related so that's no use.

Similar Messages

  • Keyboard is Unrecognized

    I have had this happen on both of my 2 iMacs, and was wondering what is the problem and if there is a fix. I bought an iMac 20" G5 Rev B this summer for my son to take to college, and after registering and booting up, it popped up a window that said "Keyboard Unrecognized" or similar with a "Next" button. On the next screen is a sideways picture of a keyboard and a request to press the key just to the right of the left shift key (Z on a US keyboard). When I pressed the key, it gave a message that I had pressed a key on the "build-in" keyboard (actual spelling) and it asked me to press a key on the "external" keyboard. We somehow got past this on the 20" iMac (I don't remember if we just closed the window or what) and it never came back. I just bought a second 17" refurb iMac (also Rev B) and it is now giving the same error. This happened on both 10.4 (as shipped) and after upgrading to 10.4.3 via Software Update. I tried closing the window, but it gives the same error every time that I start up the machine. What is this telling me? How do I get out of this?
    Mac mini 1.42Ghz/80GB/512MB Mac OS X (10.3.9) iPod Nano 4GB (Black)
    Mac mini 1.42Ghz/80GB/512MB Mac OS X (10.3.9) iPod Nano 4GB (Black)
    Mac mini 1.42Ghz/80GB/512MB   Mac OS X (10.3.9)   iPod Nano 4GB (Black)

    I used to have a 1.5ghz 15" Powerbook and I used a Mathias Tactile Pro Keyboard on it (which I now use on my iMac iSight).
    With that machine I was always getting alerted by the Keyboard Assistant's window whenever I logged out and like you I faithfully went through the steps of the exercise of getting the keyboard recognized. After a number of times, I got gave up on this and just ignored it. The best way of dealing with it is just click the red "Go AWAY!" button on the top left of the window or type Command/W to dismiss the window without doing anything. You will not suffer any typing errors if you just make it go away without going through the steps the Keyboard Assistant wants to take you through.
    Griff

  • Installing new aluminum keyboard

    I'm due to receive a new aluminum keyboard this afternoon and I've got a Mac Pro running 10.4.10.
    Questions:
    1.Should I apply the new 1.2 keyboard update prior to swapping my old keyboard for the new or install the update and then swap the keyboards.
    2. With the new keyboard do I need to re-run the bootcamp 1.4 update or will the update (1.4, already installed) pick the new keyboard up for my bootcamp/xp drive?

    "I just tried this. Go into System Preferences -> Display. Turn off Automatically adjust brightness as ambient light changes. Now move the Brightness slider right and left, left and right. Turn on Automatically adjust brightness as ambient light changes. When I changed it from far left to right then left again it was ok."
    Hey, thanks for the tip Neil. I was trying to figure out why my computer would dim and then get brighter. It would keep changing after every little thing i'd do. Honestly, it was freakin annoying.

  • Keyboard Modifier toggle from command to Control for Leopard

    Hi guys I have this script working after a bit of tweaking and the script was originally posted by Lance Ball long ago for Tiger and was for users with a Pc Keyboard. I am swapping control and command for pure gaming preferences; Unfortunately, The script will not work when the Keyboard Shortcuts menu has been opened last in system preferences, would anyone know how to slightly tweak this applescript so that it selects the keyboard button prior?
    -- Utility script to switch keyboard mapping for Command and Control keys.
    -- Author: Lance Ball & tweaked by Beau Parkes for Snow Leopard
    -- Open System Preferences
    tell application "System Preferences"
    activate
    set current pane to pane "com.apple.preference.keyboard"
    end tell
    tell application "System Events"
    -- If we don't have UI Elements enabled, then nothing is really going to work.
    if UI elements enabled then
    tell application process "System Preferences"
    get properties
    -- Open up the Modifier Keys sheet
    click button "Modifier Keys…" of tab group 1 of window "Keyboard"
    tell sheet 1 of window "Keyboard"
    -- get the text of the 3rd pop up button
    click pop up button 5
    click menu item "Apple Internal Keyboard / Trackpad" of menu 1 of pop up button 5
    set commandKey to value of pop up button 3
    -- looks like we're in default mode. Swap the keys
    if commandKey ends with "Control" then
    click pop up button 3
    click menu item 4 of menu 1 of pop up button 3
    click pop up button 1
    click menu item 2 of menu 1 of pop up button 1
    else
    -- We're in PC keyboard mode. Swap back to the defaults
    click button "Restore Defaults"
    end if
    -- close the sheet
    click button "OK"
    end tell
    end tell
    tell application "System Preferences" to quit
    else
    -- UI elements not enabled. Display an alert
    tell application "System Preferences"
    activate
    set current pane to pane "com.apple.preference.universalaccess"
    display dialog "UI element scripting is not enabled.
    Check \"Enable access for assistive devices\""
    end tell
    end if
    end tell
    Thanks guys, Im excited to hear how I can improve the code.
    Beau Parkes

    Hi, Beau Parks. Welcome to this forum.
    The following version of your script (tested with Mac OS X 10.6.2) should do what you are asking for:
    --BEGINNING OF SCRIPT
    --Optional part:
    tell application "System Events" to set UI_enabled to UI elements enabled
    if not UI_enabled then
    display dialog "This script utilizes the built-in Graphic User Interface Scripting architecture of Mac OS X which is currently disabled." & return & return & "Do you want to activate GUI Scripting by selecting the checkbox “Enable access for assistive devices” in the Universal Access preference pane?" buttons {"Cancel", "OK"} default button 2 with icon 0
    tell application "System Preferences"
    activate
    reveal pane id "com.apple.preference.universalaccess"
    end tell
    return
    end if
    --Main part:
    tell application "System Preferences"
    reveal anchor "keyboardTab" of pane id "com.apple.preference.keyboard"
    tell application "System Events" to tell window "Keyboard" of process "System Preferences" -- GUI Scripting
    click button "Modifier Keys…" of tab group 1 -- open up the Modifier Keys sheet
    tell sheet 1
    click pop up button 5 -- the first button from the top
    click menu item "Apple Internal Keyboard / Trackpad" of menu 1 of pop up button 5
    if (value of pop up button 3 ends with "Control") then -- we're in default mode
    click pop up button 3 -- Control Key
    click menu item 4 of menu 1 of pop up button 3 -- Control Key --> Command Key
    click pop up button 1 -- Command Key
    click menu item 2 of menu 1 of pop up button 1 -- Command Key --> Control Key
    else -- we're in PC keyboard mode; swap back to the defaults
    click button "Restore Defaults"
    end if
    click button "OK" -- close the sheet
    end tell
    end tell
    quit
    end tell
    --END OF SCRIPT
    Message was edited by: Pierre L. (I removed a link to a web page)

  • IS IT EVEN POSSIBLE TO UPGRADE TOUCHSMART TX2 1274nr TO WINDOWS 7??? Many issues!

    Please...any expert have advice on upgrading the Touchsmart TX2-1274nr model from Vista Home Premium to Windows 7 Home Premium using the HP upgrade kit?
    I have had several HP help chats since I bought this touchsmart model, and I've only had it for a little over a week and a half.  And, it seems the HPOP chat does not allow me to type my sentences out fully...always cuts me off and chops up my sentences.  Plus, it seems the agents that "help me" never seem to understand ANYTHING I am asking.  This is quite frustrating, irritating and perplexing.
    I tried for the first time to upgrade yesterday, and I did not understand the compatibility report.  First, it says to update the "KEYBOARD FILTER" prior to upgrade.  I searched the computer and nothing comed up, so I have no idea WHAT EXACTLY this is so I can update the driver.  Secondly, it recommends uninstalling 11 programs...6 of which are games (which is fine).  However, it recommends uninstalling the ATI INSTALLER MANAGER and ATI CONTROL CENTER.  This is another VERY CONFUSING and VAGUE recommendation.  This is because only the ATI INSTALLER MANAGER is listed in Programs & Features list.  When you try to uninstall, it becomes confusing as to does one remove ALL ATI COMPONENTS...and, if not, how do you removed just the CCC and the INSTALLER MANAGER.  I managed to get the CCC uninstalled, by performing and "custom" uninstal of the ATI INSTALLER MANAGER in the Prgrams & Features list, but the INSTALLER MANAGER still remains on the computer.
    These problems proved for me confusing.  So, I go yet again to HP Help chat and the "tech" was NOT HELPFUL.  A little sarcastic & vague and just kept saying follow the onscreen instructions.  The instructions have me confused, which is why I was asking so WINDOWS 7 INSTALLED CORRECTLY.
    So, I went to another forum and asked for help.  I was advised that the Keyboard Filter most likely meant it was referencting the N-Trig DuoSense Digitizer, and I was provided the link to the manufacturer's site to download the Windows 7 compatible drivers.  HOWEVER, I could not find out why the compatibility report kept telling me to update the "Keyboard Filter" prior to upgrading.
    So, I ended up removing all on the compatibility report suggested removals prior to upgrading EXCEPT the KEYBOARD FILTER DRIVER UPDATE & the ATI INSTALLER MANAGER.
    I performed the full UPGRADE anyway.
    Sure enough, when all was said and done, after the "UPGRADE" it seemed my system was running noticably SLOWER THAN when it had Vista.  Secondly, I LOST MY TOUCHSCREEN ability.  So, I went back to the link the 3rd party forum person recommended for the N-Trip DuoSense Digitizer Windows 7 drivers...and the touchscreen function returned.  However, I KEPT LOSING MY INTERNET CONNECTION.  Well, my wifi apeared to show a full wireless connection to our home network, but I would open up internet explorer and it would load my home page.  I was able to maybe retain my internet explorer connection for a miunute or 2, and then no matter what website I enetered or link  I clicked...NOTHING.  It would just keep indicating it was loading but minutes would pass and nothing would happen.  Plus, the windows system in general seem to be running slower.
    So, I am highly irritated & upset over this.  And all my searching and researching on HP site and others seem to not giver SPECIFIC AND CLEAR ANSWERS to any of these issues.  WHY?????  Am I the only one to have ALL THESE ISSUES? This morning, I ended up performing a F11 Windows recovery back to Vista Home Premium.  What should I do? 
    Please, if anyone has had similar problems, sound off.  Moreover...PLEASE if you have updated your Touchsmart TX2-1274nr SUCCESSFULLY....PLEASE...PLEASE...ADVISE me as to how I may accomplish the same!
    I thank any advice/suggestions any of you may have in advance.  Kindly, Jimmyb30ohio

    I have the TX2 1012NR and its can upgrade just fine!  Here is a few recommendations "only if u have the HP Upgrade program disks"
    If you have them you can install a clean copy and delete everything... Do not use the use me first disk included because it prompts you to install an older BIOS....  Just use the windows 7 upgrade disk and start the process.  The clean install clears your entire drive but does not void your warranty!   When you use the use me first disk after the install it actually loads everything else needed to get you up in running.  The touchscreen driver and the HP Mediasmart programs will have to be downloaded from the HP support site.  Once again its recommended that if there were any programs installed delete them do not try to update them!  This causes issues and countless errors.  Specifically with touchscreen drivers etc uninstall them before installing the ones from HP support.  I found this was not the easy way to do it but the best way...  I also recommend that when doing any sort of BIOS update that you remove your Battery and leave it connected to a power cord only!  Last but not least if you really mess up and its under warranty... Send it to HP they will set it back up to factory defaults under Windows Vista with the more up to date BIOS installed.  I hope my information helps! Sure you might loose some programs but in the end your computer runs faster and smoother because all the programs installed are made for Windows 7....  Also they did release the Touch Pack for download from the Microsoft website here is a link telling more about the features and benefits and how to get it as it is a totally free download... 
    http://windowsteamblog.com/windows/b/windows7/archive/2009/05/27/introducing-the-microsoft-touch-pac...
    Microsoft Link for download:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=b152fadd-82e4-4ddb-a46a-aebe49944428&displa...

  • Dinovo edge Mac edition

    Hey there, First and foremost I'm running on MAC OS X 10.5.8.
    since updating to 10.5.8 I've found that at random times my Logicrap dinovo edge keyboard tends to start messing up. The 0 key produces a variety of different letters and symbols and 4 at a time. Or it'll open documents as if shift+o was being held. E, and G are also unusable. Than again - randomly this will stop throughout the day. I've tried everything from resetting the connection - rebooting my mac, repairing (twice) the devices.
    This only happened AFTER the update to 10.5.8.
    Furthermore - a friend is having a similar issue with his wireless aluminum mac keyboard. Prior to the update his battery would last at least a week. Now a day to a day in a half.
    Any support would be amazing.

    Hello,
    I'm not sure if this is a Mac problem or a problem with the Logitech DiNovo for Mac keyboard, but I am having the same problem after 4 months without an issue.
    The "o" key generates "Option+o" (which opens an open file dialog) and it also toggles the caps lock. Other screwy keys are d and f. They generate a bunch of gibberish.
    I have tried contacting Logitech support but . . . they do not accept email support, their support phone number is disconnected, and they do not answer forum posts. Is there anything I can do on my Snow Leopard iMac to debug this issue to see if it is a Keyboard issue or a Snow Leopard issue? I did not experience this problem prior to my update to Snow Leopard, now my ~ $200 logitech keyboard is worthless.

  • Can't type credentials via Hyper-V Manager

    So I'm RDP'd into a VM that I run RSat tools on and having a slight issue.
    I created a new VM through this VM in Hyper-V manager. Then I start the VM and am doing a PXE boot.
    Everything is working fine until I get to the credentials screen before I can install the OS and I cannot type anything. The keyboard worked prior to this screen and the mouse still works.
    I even tried LMIR into the RSat VM and still am not able to type into the newly created VM. Any ideas what is going on? It's preventing me from continuing until I get physically to the location to enter the credentials.

    I have a feeling that you fall into this due to your version of WinPE:
    http://blogs.technet.com/b/jhoward/archive/2013/10/29/hyper-v-generation-2-virtual-machines-part-4.aspx
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • 2012 MBP extremely hot out of bag while turned off

    My mid-2012 MBP was extremely hot when I pulled it out of my bag at work this morning. I never transport it while asleep, but I was in a hurry when I was leaving, so I thought at first that perhaps I had failed to shut down completely before closing it, but upon checking the console log, it appears to have shut down at 9:34 when I turned it off and not had any activity until I booted up at 11:45. Whatever it was doing while off, it discharged approximately 50% of the battery. What kind of parties is my computer throwing in my backpack?! Has anyone else encountered this sort of behavior?

    Yes, it's been running at normal temp since turning it on, but I am fairly certain that it was off. I was concerned that it was perhaps asleep, so I attempted to wake it through keyboard use prior to powering up, to no effect. Upon startup, it went through the usual boot up, rather than waking from sleep. The battery is my suspect as well, though it claims to be in reasonably good shape, status normal, it is already down to  6327 mAh capacity after a disappointing 190 charge cycles. Going to calibrate and reset SMC and then see what it has to say for itself.

  • [SOLVED] startx: no keyboard/mouse after upgrade

    Hello,
    After an upgrade during which X was upgraded to 1.16 the keyboard and mouse stopped working after using startx. When I start X with startx as root the keyboard and mouse work.
    After the upgrade I made a .xinitrc like in the wiki article about xinitrc and I copied /etc/X/xinit/xserverrc to ~/.xserverrc
    Any help would be appreciated.
    Thanks!
    Last edited by basdi (2014-09-15 17:13:45)

    Hey,
    Thanks for your answer.
    I start X using startx and this .xinitrc in my home directory:
    #!/bin/sh
    #~/.xinitrc
    # Executed by startx (run your windows manager from here
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    xrdb /merge ~/.Xresources
    setxkbmap de
    # Here awesome is kept as default
    # no va: session=${1: -awesome}
    case $session in
    awesome) exec awesome;;
    fluxbox) exec startfluxbox;;
    # No known session, try to run it as command
    # no va *) exec $1;;
    *) exec awesome;;
    esac
    I created the .xinitrc after this wiki article
    https://wiki.archlinux.org/index.php/Xinitrc
    I tried it without the .xserverrc in the home directory and  it is the same. I read that in a forum. But probably it is not necessary because the behaviour is the same...
    Before the upgrade,  I started X using xinit, but now using xinit I get the error :
    (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
    And I read on a forum that I should use startx.
    I'm not running as root. I try to run X as a normal user. When I run it as root it works.
    In the boot messages from systemd journal I see these messages:
    systemd-logind[642]: Failed to connect to system bus: No such file or directory
    systemd-logind[642]: Failed to fully start up daemon: No such file or directory
    systemd-logind[675]Failed to connect to system bus: No such file or directory
    systemd-logind[675]: Failed to fully start up daemon: No such file or directory
    Sorry I don't really know what to look for in the logs...
    I have a nvidia card and I use the proprietary drivers and Bumblebee.

  • My laptop keyboard is having problems. I took it if to change my bottom case it worked fine prior and then after just the power key worked. I cleaned everything nothing is bent in the cable. now my power key is not working

    Hi my keyboard is not working I took off the bottom case to change it prior my keyboard was fine and after just the power key worked. I checked everything no portions were bent and it plugged in good. I tried to turn it on this morning and now the power key doors not work??

    Back up all data.
    Triple-click anywhere in the line below to select it:
    pmset -g assertions
    Copy the selected text to the Clipboard (command-C).
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V).
    Post any lines of output that appear below what you entered — the text, please, not a screenshot.

  • Keyboard spec characters doesn't work when startx...

    When i launch Xorg by startx as a user,  the RALT+letters don't display the special characters, like >#&@@{}đĐ[] (i use 105 buttons qwertz keyboard, hungarian layout).
    If i launc X with a DM, or starx as root, everything is ok.
    in the .xinitrc only the "startkde" stands...

    i reinstalled archlinux from scratch...it solved all my problems.
    i hate this way of solving problems anyway
    i could't realised what was wrong...

  • After uploading iOS7 on the 4s,can't increase the volume of keyboard clicks, actually can't find a volume control, there was a control prior to the upload, any suggestions folks?

    After uploading iOS7 on the 4s lost the ability to control the keyboard click volume, there is not the same volume control that was there prior to the download.
    Has anyone else encountered this? If so and anyone has a solution I would be very greatful.
    Thank you.

    I have the same problem.  There used to be a volume control for the keyboard clicks.  That's no longer an option.  In Settings > Sounds, there is only the option to turn keyboard clicks on/off, but no volume level option. 
    Very frustrating when typing in a quite place.  I used to be able to turn the volume low so I could just barely hear it but no one else could.

  • Must use Step Input Keyboard prior to using midi controller? When I attempt to use my midi keyboard conteoller for step input, it won't work unless I input the first note in each track via the Step Input Keyboard. This doesn't seem right...

    When I try to use my midi controller keyboard for step input, it won't work unless I input the first note in each track via the Step Input Keyboard.. What am I doing wrong?
    Logic Studio 9.1.7, OS X 10.7.5

    Hi
    Playhead in the right place?
    CCT

  • HT1349 iPhone 4s has totally locked up with black screen.  No buttons respond. Prior to this trying to initiate a text message, the onscreen keyboard would not respond.  tried other functions which led to overall black screen, no response to any buttons

    iPhone 4s has locked up with no response to any buttons.  First occurrence on a 1+ month old iPhone

    Have you tried a very basic troubleshooting step well-outlined in the User Guide called reset?  Hold the on/off switch and the home button togeter (usually around 30 seconds) and don't let go until you see the Apple logo.
    I highly recommend reading the User Guide to learn about other general troubleshooting steps.

  • New install, when I startx, nothing moves

    I installed arch on an old laptop.
    I installed xorg and fluxbox.
    when I startx, the keyboard and touchpad do nothing. I have to reboot.
    here is xorg.conf:
    # File generated by xorgconfig.
    # Copyright 2004 The X.Org Foundation
    # 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 X.Org Foundation 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 X.Org Foundation 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 X.Org Foundation.
    # Refer to the xorg.conf(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"
    Load "glx"
    Load "freetype"
    Load "synaptics"
    # 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 font modules
    # Load "type1"
    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 "ServerFlags"
    Option "AutoAddDevices" "False"
    EndSection
    Section "Files"
    # 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 "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    # FontPath "/usr/share/fonts/TTF"
    # FontPath "/usr/share/fonts/Type1"
    # FontPath "/usr/lib/X11/fonts/local/"
    # FontPath "/usr/lib/X11/fonts/misc/"
    # FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/Type1/"
    # FontPath "/usr/lib/X11/fonts/TrueType/"
    # FontPath "/usr/lib/X11/fonts/freefont/"
    # FontPath "/usr/lib/X11/fonts/75dpi/"
    # FontPath "/usr/lib/X11/fonts/100dpi/"
    # The module search path. The default path is shown here.
    # ModulePath "/usr/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 <Ctrl><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 <Ctrl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    # Option "DontZap"
    # Uncomment this to disable the <Ctrl><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 "kbd"
    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" "pc105"
    # 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" "pc105"
    # Option "XkbLayout" "us"
    # Option "XkbVariant" ""
    # Option "XkbOptions" ""
    # Option "XkbDisable"
    Option "XkbRules" "xorg"
    Option "XkbModel" "latitude"
    Option "XkbLayout" "us"
    EndSection
    Section "InputDevice"
    Identifier "SynapticsTouchpad"
    Driver "synaptics"
    Option "AlwaysCore" "true" # send events to CorePointer
    #Option "Device" "/dev/input/mice"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "SHMConfig" "false" # configurable at runtime? security risk
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5300" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4200" # y coord bottom
    Option "FingerLow" "25" # pressure below this level triggers release
    Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "MaxTapTime" "180" # max time in ms for detecting tap
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "MinSpeed" "0.10" # speed factor for low pointer movement
    Option "MaxSpeed" "0.60" # maximum speed factor for fast pointer movement
    Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
    Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
    EndSection
    # Core Pointer's InputDevice section
    Section "InputDevice"
    # Identifier and driver
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "Auto" # Auto detect
    Option "Device" "/dev/input/mice"
    # Mouse-speed setting for PS/2 mouse.
    # Option "Resolution" "256"
    # Baudrate and SampleRate are only for some Logitech mice. In
    # almost every case these lines should be omitted.
    # Option "BaudRate" "9600"
    # Option "SampleRate" "150"
    # Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
    # horizontal wheel to buttons 6 & 7. Change if your mouse has more than
    # 3 buttons and you need to map the wheel to different button ids to avoid
    # conflicts.
    Option "ZAxisMapping" "4 5 6 7"
    # Emulate3Buttons is an option for 2-button 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 "My Monitor"
    # 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 - 64.3
    # 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-60
    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 "** NeoMagic (generic) [neomagic]"
    Driver "neomagic"
    #VideoRam 2048
    # Chipset "NM2160"
    # IOBase 0xfea00000
    # MemBase 0xfd000000
    # VideoRam 2048
    # DacSpeed 90
    # Option "linear"
    # Option "nolinear"
    # Option "sw_cursor"
    # Option "hw_cursor"
    # Option "no_accel"
    # Option "intern_disp"
    # Option "extern_disp"
    # Option "mmio"
    # Option "no_mmio"
    # Option "lcd_center"
    # Option "no_stretch"
    # 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 "** NeoMagic (generic) [neomagic]"
    Monitor "My Monitor"
    DefaultDepth 24
    Subsection "Display"
    Depth 8
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 16
    Modes "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 24
    Modes "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 "USB Mouse" "CorePointer"
    InputDevice "SynapticsTouchpad" "SendCoreEvents
    EndSection
    # Section "DRI"
    # Mode 0666
    # EndSection

    Redroar wrote:
    Edit: foolish me. I thought I had read your entire xorg.conf, and yet missed the very obvious top. Should've known better. I think it's time to go to sleep.
    Edit2: maybe unfoolish me. You have 2 ServerFlags sections. I don't know, maybe get rid of the big spanning one that has loads of comments in it. I wonder if the AutoAddDevices thing simply isn't getting read because of a syntax error?
    That worked!
    Thanks.

Maybe you are looking for