Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Xorg 7.1 Udev Symlinks ??
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
hollowsoul
n00b
n00b


Joined: 29 Feb 2004
Posts: 31

PostPosted: Fri May 26, 2006 9:07 pm    Post subject: Xorg 7.1 Udev Symlinks ?? Reply with quote

Currently using xorg 7.1 and was tryin to make a custom udev rule for usb mouse

Code:
BUS="usb", SYSFS{manufacturer}=="Logitech", SYSFS{product}=="USB-PS/2 Optical Mouse",  NAME="input/%k", SYMLINK="input/MX510"


All seems to work @ first. I use /dev/input/event0 ( event? = based on order kernel detects at first ). Plug out mouse replug in mouse several times to be safe and works. Usb Mouse remains as /dev/input/event0.

Now i try /dev/input/MX510 since its basicly a symlink with a static name should make it easier to add conf's for multiple mice and move around etc. However Xorg refused to start due to fact it doesnt like it for some reason.

Does anyone know of away to get xorg to use the symlink (for evdev driver for usb mouse) without dying on me plz.
^^^^^^^^^^^^


Below = extracts of xorg.0.log

(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 0.0.0, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6

(II) evdev brain: Rescanning devices (1).
(EE) PreInit returned NULL for "Mouse1"

(WW) No core pointer registered
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain)
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc/pc(pc105)+pc/gb" };
xkb_geometry { include "pc(pc105)" };
(II) evdev brain: Rescanning devices (2).
No core pointer

Fatal server error:
failed to initialize core devices
Back to top
View user's profile Send private message
Voltago
Advocate
Advocate


Joined: 02 Sep 2003
Posts: 2584
Location: userland

PostPosted: Fri May 26, 2006 10:19 pm    Post subject: Reply with quote

I'm using this rule to connect to several USB mice:
Code:
#USB mouse
KERNEL=="event*", SYSFS{bInterfaceProtocol}=="02", SYMLINK="input/usbmouse"

(for udev-087)
As for your X.org issue, I'm not sure if it isn't an xorg.conf problem rather than an device node/symlink problem: In your ServerLayout session, there has to be at least one InputDevice with the "CorePointer" attribute set.
Back to top
View user's profile Send private message
hollowsoul
n00b
n00b


Joined: 29 Feb 2004
Posts: 31

PostPosted: Fri May 26, 2006 10:50 pm    Post subject: Reply with quote

Below is xorg conf in question
Downgraded atm to xorg-server-1.0.2-r4 and same with x11-drivers 1.0xxx so i can use nvidia driver atm
Same problem using nv driver & xorg-server 1.1 & x11-drivers 1.1xxx

If i use /dev/input/event0 = works
If i use /dev/input/MX510 = error

Have seen on net peep use udev SYMLINKS for xorg so wonderin what i have done wrong or is this a known bug i not aware of



Code:
# 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(5x) 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 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.


# 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/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/local/"
#    FontPath   "/usr/share/fonts/Speedo/"
#    FontPath   "/usr/share/fonts/TrueType/"
#    FontPath   "/usr/share/fonts/freefont/"

# The module search path.  The default path is shown here.


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   "kbd"

# 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"    "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 "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"


    Option "XkbModel"   "pc105"
    Option "XkbLayout"   "gb"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier   "Mouse1"
    Driver   "evdev"
    Option "Device"      "/dev/input/MX510"
#     Option "Name" "Logitech MX510"

# 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  "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   30-70

#    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 GeForce"
    Driver      "nvidia"
#    Option      "RenderAccel" "true"
#    Option      "AllowGLXWithComposite" "true"
#    Option      "NoLogo" "true"
    #VideoRam    262144
    # 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      "NVIDIA GeForce"
    Monitor     "My Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "800x600"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024"
        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

Section "Extensions"
    Option "Composite" "true"
EndSection

Back to top
View user's profile Send private message
Headrush
Watchman
Watchman


Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World

PostPosted: Sat May 27, 2006 12:40 am    Post subject: Reply with quote

Try adding the CorePointer option to the InputDevice Section.

Here is my udev rule and xorg.conf which works perfectly with my Logitech MX510.
Code:
BUS="usb", SYSFS{idVendor}="046d", SYSFS{idProduct}="c01d", NAME="input/%k", SYMLINK="input/MX510", GROUP="kdemouse", MODE="664"

You can use lsusb to find the vendor and product IDs. (I think easier than using the longer descriptive properties.
Code:
Section "InputDevice"
        Identifier  "Logitech MX510"
        Driver      "evdev"
        Option      "Device"        "/dev/input/MX510"
        Option      "CorePointer"
EndSection
Back to top
View user's profile Send private message
Fran
Guru
Guru


Joined: 29 Feb 2004
Posts: 530
Location: Coruña (Spain)

PostPosted: Sat Jun 03, 2006 8:30 pm    Post subject: Reply with quote

Same problem here (and same mouse). I always used a symlink to eventX, but with xorg-7.1 it doesn't work.


@Headrush:
Are you using xorg-7.1? Adding Option "CorePointer" didn't help.
Back to top
View user's profile Send private message
irondog
l33t
l33t


Joined: 07 Jul 2003
Posts: 715
Location: Voor mijn TV. Achter mijn pc.

PostPosted: Sat Jun 03, 2006 8:56 pm    Post subject: Reply with quote

/usr/share/man/man4x/evdev wrote:
At this time ONLY /dev/input/event<N>, where <N> is an integer, are matched against the Option "device" string. Other strings are invalid.

/dev/input/my_bloody_event_device used to be a valid device string in 7.0, but that isn't the case anymore. 7.1 uses a different way to distinct event devices from each other. You should use Option "Name" now instead of udev tricks and remove the line with Option "device" "/dev/input/mx510"

The new evdev driver has advantages:
No udev rules are required to make Xorg 7.1 working with evdev.
So, remove your udev rules and edit /etc/X11/xorg.conf. Remove the "device" Option string (this is not needed anymore) and add a "name" Option string.

Code:

Section "InputDevice"
        Driver          "evdev"
        # From /proc/bus/input/devices
        Option          "Name" "Logitech USB-PS/2 Optical Mouse"
        Identifier      "Mouse0"
        Option          "Buttons" "7"
        Option          "ZAxisMapping" "4 5"
EndSection


The second advantage of the new evdev driver is, that you won't need any xmodmap tricks anymore for your mouse buttons to behave in a usable way! :) :) :)
_________________
Alle dingen moeten onzin zijn.
Back to top
View user's profile Send private message
Fran
Guru
Guru


Joined: 29 Feb 2004
Posts: 530
Location: Coruña (Spain)

PostPosted: Sat Jun 03, 2006 9:33 pm    Post subject: Reply with quote

irondog wrote:
...

Thanks, it worked :)
Back to top
View user's profile Send private message
galilette
n00b
n00b


Joined: 17 Jan 2005
Posts: 22

PostPosted: Sun Jun 04, 2006 7:34 am    Post subject: Reply with quote

hi guys

in case you haven't found out, the evdev(4x) manual missing in xorg 7.0 is available now in 7.1 and this is the related portion:
Quote:

Option "Device" "string"
Specifies the device note through which the device can be
accessed. At this time ONLY /dev/input/event<N>, where <N> is
an integer, are matched against this this field.

This option uses globbing.
Please note that use of this option is strongly discouraged.


Option "Name" "string"
Specifies the device name for the device you wish to use.
The device name is generally the only consistent identifier for
devices that are commonly unplugged and plugged back into dif-
ferent ports.
A list of currently plugged in devices and associated device
names can be obtained by typing "cat /proc/bus/input/devices"
,
the "Name" field is the value you want for this option.
This option uses globbing.
Back to top
View user's profile Send private message
ferg
Guru
Guru


Joined: 15 Nov 2002
Posts: 458
Location: Cambridge, UK

PostPosted: Sat Sep 09, 2006 3:36 pm    Post subject: Reply with quote

Hi,

I could only get this to work using "Dev Name" as an option, rather than "name":

Code:
Section "InputDevice"
    Identifier   "Mouse1"
    #Driver   "mouse"
    Driver   "evdev"
    Option "Protocol"  "evdev"
    Option "Dev Name" "Logitech USB RECEIVER"
    Option   "ZAxisMapping"  "11 12 10 9"
    Option   "Buttons"   "12"
    Option   "Resolution"    "800"
    Option   "CorePointer"
EndSection


Confused the hell out of me for a while :-)

Cheers
Ferg
_________________
Climb up it, kayak down it + make sure it runs on GNU/Linux
"cease to exist, giving my goodbye, drive my car into the ocean,
you think I'm dead, but i sail away, on a wave of mutilation!"
Back to top
View user's profile Send private message
R. Bosch
Apprentice
Apprentice


Joined: 07 Jun 2004
Posts: 184
Location: NL

PostPosted: Fri Sep 22, 2006 7:12 am    Post subject: Reply with quote

ferg wrote:
Hi,

I could only get this to work using "Dev Name" as an option, rather than "name":

Code:
Section "InputDevice"
    Identifier   "Mouse1"
    #Driver   "mouse"
    Driver   "evdev"
    Option "Protocol"  "evdev"
    Option "Dev Name" "Logitech USB RECEIVER"
    Option   "ZAxisMapping"  "11 12 10 9"
    Option   "Buttons"   "12"
    Option   "Resolution"    "800"
    Option   "CorePointer"
EndSection


Cheers
Ferg


Note of warning which I ran into:
With "Dev Name" My keyboard became 'wonky'. No more arrow key, Page-up bacame '/' and so on. Barely workable.
The "Name" option works better for me :)

Thanks for this thread ;)
Was having udev issues as well
_________________
Greetings / Met vriendelijke groet,

R. Bosch
Back to top
View user's profile Send private message
ferg
Guru
Guru


Joined: 15 Nov 2002
Posts: 458
Location: Cambridge, UK

PostPosted: Fri Sep 22, 2006 7:48 am    Post subject: Reply with quote

thanks.

I'm just using evdev (well actually not at the moment, but that's another story!!) for mouse only. I heard there were issues getting it to run with the keyboard!!

Cheers
ferg
_________________
Climb up it, kayak down it + make sure it runs on GNU/Linux
"cease to exist, giving my goodbye, drive my car into the ocean,
you think I'm dead, but i sail away, on a wave of mutilation!"
Back to top
View user's profile Send private message
R. Bosch
Apprentice
Apprentice


Joined: 07 Jun 2004
Posts: 184
Location: NL

PostPosted: Sun Sep 24, 2006 2:31 pm    Post subject: Reply with quote

ferg wrote:
thanks.

I'm just using evdev (well actually not at the moment, but that's another story!!) for mouse only. I heard there were issues getting it to run with the keyboard!!


Maybe because of Case sensitivity? I saw that earlyer you wrote "name" instead of "Name". :roll:

If the good people who are working on other drivers convert their driver to match this one (this feature) we can do away with devicenames in udev/dev alltogether. Just show the user a listing of devices during installation and away you go 8)

Gues that was the general idea?
_________________
Greetings / Met vriendelijke groet,

R. Bosch
Back to top
View user's profile Send private message
ferg
Guru
Guru


Joined: 15 Nov 2002
Posts: 458
Location: Cambridge, UK

PostPosted: Sun Sep 24, 2006 3:10 pm    Post subject: Reply with quote

R. Bosch wrote:
ferg wrote:
thanks.

I'm just using evdev (well actually not at the moment, but that's another story!!) for mouse only. I heard there were issues getting it to run with the keyboard!!


Maybe because of Case sensitivity? I saw that earlyer you wrote "name" instead of "Name". :roll:


I generally am a rubbish typer, and crap speller! I should put a disclaimer in my sig :-)

Actually I've completely forgotten why I am not using evdev :-) I upgraded Xorg, and it stopped working. Not got around to wondering why!! I should do though, as I think I've got dependent on the scroll wheel for web browsing now!!!!

Cheers
Ferg
_________________
Climb up it, kayak down it + make sure it runs on GNU/Linux
"cease to exist, giving my goodbye, drive my car into the ocean,
you think I'm dead, but i sail away, on a wave of mutilation!"
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments 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