Middle Scroll Mouse Button

one of the first things i noticed when using linux is that i couldn't use my middle scroll button.

does anyone know how to fix this

i'm running madrake 9.0

#59978

In your /etc/X11/XF86Config file, look for the mouse section:

# Identifier and driver

Identifier "Mouse1"

Driver "mouse"

Option "Protocol" "IMPS/2"

Option "Device" "/dev/input/mice"

Option "ZAxisMapping" "4 5"

It should look something like that.

1. Make sure you use the IMPS/2 protocol

2. Add that Option "ZAxisMapping" 4 5" to yours, like mine is.

You have to be root when editing it. And your config might have a (-4) after XF86Config, some do.

Restart and enjoy your scroll wheel.

Also, you may want to update to Mandrake 9.2, its come out I believe.

#59995

in the mandrake install you should of choose a scrollwheel mouse option at the begining as thats how i got mine to work with mandrake

-bolero

#60000

Originally posted by contrasutra@Sep 28 2003, 05:01 AM

In your /etc/X11/XF86Config file, look for the mouse section:

# Identifier and driver

                                                                                                                       

    Identifier  "Mouse1"

    Driver      "mouse"

    Option "Protocol"    "IMPS/2"

    Option "Device"      "/dev/input/mice"

    Option "ZAxisMapping" "4 5"

It should look something like that.

1. Make sure you use the IMPS/2 protocol

2. Add that  Option "ZAxisMapping" 4 5" to yours, like mine is.

You have to be root when editing it. And your config might have a (-4) after XF86Config, some do.

That's why I hesitate to try Linux! :D

I mean, I've grown up with DOS and I'm not afraid of the command line or Windows Registry, but having to do all this in order to have my mouse work properly... too much, isn't it? :(

#60005

You don't always. Most distros enable it by default. Only the hardcore distros like Slackware or Gentoo dont. Hell, even ArchLinux enables it by default.

What idicula encountered was a BUG. Yes, Linux has those too.

And wait a second. Editing ONE line in a SIMPLE configuration file is hard? I can edit that file faster than you can click through your GUI.

People equate text --> Hard. Its not, in MOST cases, its easier.

DOS was crap. UNIX is brilliant. People who have only used DOS don't know how great the commandline/text configs are.

Now the Windows Registry, dont get me started on that. That is the most incoherent POS I have ever seen.

#60007

You are absolutely right, but... aren't you being a little over-protective about Linux? :D

#60008

slack 9.1 is the first linux distro i have used that let the middle button on my laptop work properly as a scroll. it might be gnome that is doing it though, i need to test more

#60015

Originally posted by Ken@Sep 28 2003, 01:24 AM

You are absolutely right, but... aren't you being a little over-protective about Linux? :D

If I don't overprotect it, who will? :blink:

#60078

I will ;)

I got my scroll-button working in Gentoo Linux, but i had to get som help to make it good :P

It is not so very hard to get things right, if you just try. Like asking on the internet, or IRC, is a very good thing to do :)

Remember to never give up ;)

#60138

Originally posted by contrasutra@Sep 28 2003, 02:15 AM

DOS was crap. UNIX is brilliant. People who have only used DOS don't know how great the commandline/text configs are.

Now the Windows Registry, dont get me started on that. That is the most incoherent POS I have ever seen.

contra:

A big fat AMEN is in order. Frankly, I've argued with many people dozens of times why *nix is better than DOS...they never want to admit it.

And the registry sucks you know what... It's so freggin' bloated!

#60219

ps -ef |grep dos.exe | awk '{print $2}' | xargs kill -9

#60441

Originally posted by Telmo@Sep 29 2003, 01:48 PM

ps -ef |grep dos.exe | awk '{print $2}' | xargs kill -9

sudo rm -r Telmo

:P

#60447

@Taha

cat /dev/null > /boot/vmlinuz;reboot :baby: :ninja:

@all

comparing DOS to UNIX is like comparing a calculator to a PC, they both can do math

contra, Taha knows that I am joking... I hope.

#60451

Just a warning:

Dont do what Telmo said to do. Unless you don't like your kernel.

#60458

Originally posted by contrasutra@Sep 29 2003, 03:08 PM

Just a warning:

Dont do what Telmo said to do. Unless you don't like your kernel.

:P

That would be kinda funny ;)

#60491

Actually, the fun thing to do (and no permanent damage) is:

yes > /dev/mem

Watch all the pretty colors :P

#60495

Originally posted by contrasutra@Sep 29 2003, 05:07 PM

Actually, the fun thing to do (and no permanent damage) is:

yes > /dev/mem

Watch all the pretty colors :P

Hum...you mean the actual word "yes" sent to the mem device...?

Interesting :)

I'll have to do that when I get home to my box!

:)

Hey that gives me an idea. To clear your mem:

cat /dev/null > /dev/mem

:D

#60503

That would clear your kernel too. ;)

#60506

Originally posted by contrasutra@Sep 29 2003, 05:48 PM

That would clear your kernel too. ;)

Putting "nul' into mem would clear your kernel?

You mean it would clear it off the *active* memory, but it wouldn't actually affect the file, right?

Maybe I misunderstood you.

Wouldn't typing "yes" then also clear the kernel?

(my assumption to both these answers is yes)

#60509

"yes" doesnt clear anything.

It continuously writes to your memory until it gets completly full. Fun things happen.

#60522

"yes" actually it writes "command not found" to /dev/mem because /dev/mem is a device holding a virtual image of your system memory when you write something to it you are basically overwriting with junk whatever is in memory at that moment. kernel, modules, etc, etc, etc.

yes > /dev/mem and cat /dev/null > /dev/mem are basicalle the same they both cause the same effect.

other fun things to do at the keyboard....

nohup rm -rf /* &;clear

for i in `seq 1 99999999`;do nohup find . -name s &;done

DISCLAIMER: I can't be blame if you are not smart enough not to run those things in your system.

#60528

Originally posted by Telmo@Sep 29 2003, 07:27 PM

"yes" actually it writes "command not found" to /dev/mem because /dev/mem is a device holding a virtual image of your system memory when you write something to it you are basically overwriting with junk whatever is in memory at that moment. kernel, modules, etc, etc, etc.

yes > /dev/mem and cat /dev/null > /dev/mem are basicalle the same they both cause the same effect.

other fun things to do at the keyboard....

nohup rm -rf /* &;clear

for i in `seq 1 99999999`;do nohup find . -name s &;done

DISCLAIMER: I can't be blame if you are not smart enough not to run those things in your system.

:lol:

Someone, somewhere is going to run some of those commands :)

#60572