LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-05-2006, 09:09 PM   #1
toshi_satlite_p35
LQ Newbie
 
Registered: Jul 2006
Posts: 13

Rep: Reputation: 0
USB Logitech Wireless Mouse


Just installed slack now I am having problems getting the logi wireless mouse running.

here is my xorg.conf 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.

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 "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"

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

# Option "XkbDisable"

Option "XkbRules" "xorg"
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/mouse"

# 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 "Mouse1"
# Driver "mouse"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "IMPS/2"
# Option "Emulate3Buttons" "off"
# Option "ZAxisMapping" "4 5"
# 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 - 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 40-150

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 "** ATI Radeon (generic) [radeon]"
Driver "radeon"
#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 "** ATI Radeon (generic) [radeon]"
Monitor "My Monitor"
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

You guys have to help me :'( it is starting to look like I am strength training my right forearm for the masturbation olympics by using the laptop mouse pad.
 
Old 07-05-2006, 11:25 PM   #2
toshi_satlite_p35
LQ Newbie
 
Registered: Jul 2006
Posts: 13

Original Poster
Rep: Reputation: 0
:'( Still no reply, I have already setup up madwifi and the ati drivers. I am just waiting on this usb mouse and I will be smooth sailing.

I know somebody who is full of genius can help me out. I beg of you!
 
Old 07-06-2006, 12:04 AM   #3
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Quote:
Originally posted by an impatient rule breaker
I am having problems getting the logi wireless mouse running.
How should that rodent run?

Perhaps you need to "cat" him to get him to run. In a terminal issue "man cat" and see if there's cheese.

Now, if you'd be so kind as to review the LQ Rules, you will read
  • While almost every question does get an answer, we cannot guarantee a response. If your thread does not receive any responses, it will automatically be bumped twice.

Perhaps we could get Jeremy to amend that rule to explicitly state that you must wait 24 hours.

Since you're new to this world, there's two other links you should :

How To Ask Questions The Smart Way

Posting and You

After thoroughly studying those two items, you'll know how to tell us what doesn't work about your mouse. With the commented items in your xorg.conf file, I'd say his tail is stuck in the cat's mouth.
 
Old 07-08-2006, 05:08 AM   #4
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
toshi,

how are you physically pluggin it in? usb or ps/2.

logitech wireless do work with default slack 10.2 so long as you have the connection established to the receiver and the base, e.g the little button under the mouse and the button on the reciever.

what did you tell slackware when you installed?

if anything rerun 'pkgtool' then 'setup' and then 'mouse' in console and tell it what you got, then reboot and see.

posting your xorg dont mean much becuase it could be wrong for what you got. okay.
 
Old 07-08-2006, 11:35 AM   #5
toshi_satlite_p35
LQ Newbie
 
Registered: Jul 2006
Posts: 13

Original Poster
Rep: Reputation: 0
I already figured it out

I plugged it in by usb, but now I just can't seem to get all my seven buttons working now? Well I searched the forums and bookmarked something relevant to that topic but have not tackled that project yet.

I am just happy now my mouse is working!
 
Old 07-08-2006, 06:15 PM   #6
toshi_satlite_p35
LQ Newbie
 
Registered: Jul 2006
Posts: 13

Original Poster
Rep: Reputation: 0
It is okay, I already have my mouse working!!! Now I need to configure it to make all seven of the Logitech wireless usb mouse to work. I searched the forums and have discovered a relevant topic but have not had the motivation to jump to it.
 
Old 07-08-2006, 06:23 PM   #7
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
go over to linux-gamers.net they have a project there called "lomoco" that is a program that will let you get higher than "400dpi" assuming your mouse does higher than 400dpi.

also, you need to check out this thread here on the forums, it uses a program already installed on slackware to map your fancy buttons, it's called "xmodmap"

the thread is located at :

http://www.linuxquestions.org/questi...d.php?t=108737

bye for now.
 
Old 07-08-2006, 08:39 PM   #8
toshi_satlite_p35
LQ Newbie
 
Registered: Jul 2006
Posts: 13

Original Poster
Rep: Reputation: 0
Yes, thank you! I wish you many great travels in the future
 
Old 07-09-2006, 07:59 PM   #9
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
I've looked and read but can't figure out what is meant by "400dpi" for a mouse. Having been a photographer and graphic artist for a number of decades, I only know dpi=dots per inch.
 
Old 07-09-2006, 08:30 PM   #10
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
A "close" analogy (e.g. example) would be:

Imagine that the sensor on the mouse is taking photo's of your mouse pad at reporting it back to the pc.

The higher the dot pitch would yeild less empty voids that the computer needs to "guess" where your mouse is at a particular moment.

For example, many photo programs as you know use an algorythm know as "linear" or "bicubic" when you increase/decrease the size or the dot-pitch of a photo. the computer basically looks at surrounding pixels and assumes the color in the voids and uses that.

It's pretty much the same for a mouse. Now the mouse really knows at a factor of times two where the mouse really is.

If you look at the contol settings in KDE you'll notice it has a setting for "accuracy" by default is 4 pixels. Using an 800 dpi mouse that value can be reduced for a greater tolerance.

A high resolution mouse is great for touching up photos' like in the gimp. You get greater degree of precision when zooming in and adding/fixing pixels on high resolution photos.

Gamers love it as it tracks their mouse position for greater precision.

It's interesting to point out that on the KDE web-site, they mention "the higher dpi makes the mouse move twice as fast," and this is a gross over-statement and mis-understanding to be honest.

There is another factor too, called polling rate, which is the 'bus-frequency' or times/second that the mouse is being sampled, not to complicate matters. Linux is really nice, as you can effectively hack your usb port like gamers do in windows, and you get a real sweat performance. Unfortunately, you must be sure nothing else is plugged in to your ports like a scanner, printer,etc as you can fry them.

hope all this helps.
 
Old 07-09-2006, 08:38 PM   #11
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Thanks for the explanation, especially that last paragraph.

My scanner isn't supported in Linux, and the driver HP gives for the printer only goes to 600x600 dpi. So those are two things I must have Windoze for atm, and I would not want to fry them in Slackware just for the mouse. Plus I have like 10 other USB devices.

And to apply your analogy to GIMP ...

GIMP is like a 40 dpi photo, whereas Photoshop is like a 4800 dpi photo. So I'm using Windoze (mostly in Slackware under QEMU) for Adobe InDesign and Photoshop, for my scanner, and for printing photos.
 
Old 07-10-2006, 02:10 AM   #12
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
You know Chinaman, you mentioned a good point about the "gimp".

Now I've been playing with it in slackware, and I've noticed that it has a really hard time working with high dpi "layers".

For example, if I have a layer 4" x 6" photo, and want to layer it to add some effects, my layers being 600dpi...wow, gimp get's really slow, and crashed 2x on me.

So I'm saving as I go. Probably going to try and put the swap for gimp on a different hard drive and see.

Oh by the way, changing the dpi of your mouse to 800 dpi (assuming that your mouse can handle it) will not affect your USB ports at all.

But if you do "hack" your USB port to increase the "polling rate" then yeah, you really have to be sure to have everything else out of the usb ports...every one of them. Just a mouse only.

But that is what the pro gamers are doing I hear, tho I never took their pc's apart to be certain LOL
 
Old 08-28-2006, 08:06 AM   #13
Vincent_Vega
Member
 
Registered: Nov 2003
Location: Jacksonville, FL
Distribution: Slackware & Arch
Posts: 825

Rep: Reputation: 31
So you got it working but didn't bother to document just how you did it?? It's people like you, toshi satlite p35, who do this forum no good at all. It's fitting that you didn't get that lightening-fast reply you think you deserve.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Logitech USB Wireless Mouse not working anymore linda Linux - Hardware 4 05-08-2008 04:40 AM
Usb Keyboard Logitech Lx700 (wireless) and mouse t_surf Linux - Hardware 1 03-13-2005 07:57 PM
XBox Debian and Logitech wireless USB mouse problems gimphboi Linux - Hardware 4 04-15-2004 09:15 AM
Logitech Optical Wireless wheel usb mouse 1kyle Linux - Hardware 0 03-07-2004 05:14 PM
USB Wireless Logitech Mouse Issue During GRUB bootloading screen jambeck Linux - Hardware 0 10-09-2002 11:29 PM


All times are GMT -5. The time now is 01:04 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration