Member Avatar for Duki

Hey everyone,

I'm still trying to get my mouse to work properly in Fedora 6.0

I am using a razer diamondback mouse, and only 2 of the 9 buttons work.
I've looked at some of the conf.org file suggestions, but can't make heads or tails out of it.
could someone treat me like the ignorant user I am, and post a step by step guide to what I should do?

I have also submited a ticket to http://www.razerzone.com to ask for Linux drivers.

Thanks!
:mrgreen:

  • 3 Contributors
  • 4 Replies
  • 189 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Infarction

Dani AI

Generated

For : short, practical troubleshooting to figure out whether the Diamondback’s extra buttons are simply unmapped in X or not seen by the kernel at all. is right that an explicit X configuration can help; is also right that Fedora can auto-configure X, so an explicit file may be absent. The process below isolates the layer that’s failing and gives ways to map buttons once events are present.

Run these checks first (use sudo where needed):

# after plugging the mouse
dmesg | tail -n 50
lsmod | egrep 'hid|usbhid'

# list input devices and find the event node for the mouse
cat /proc/bus/input/devices

# if available, watch raw kernel events:
evtest /dev/input/eventN

# inside X, check button numbers:
xev
xinput --list
xinput --test <id>

If evtest shows distinct button events beyond left/right, the kernel is seeing them. In that case map them in X: use xmodmap to reorder pointer buttons or use xbindkeys / imwheel to bind button numbers to commands or actions. Example remap and starter for xbindkeys:

xmodmap -e 'pointer = 1 2 3 4 5 6 7 8 9'
xbindkeys --defaults > ~/.xbindkeysrc
# then edit ~/.xbindkeysrc to bind b:8, b:9 etc. to commands

If evtest only ever shows two buttons, the problem is kernel/HID level: verify usbhid is loaded, watch dmesg when plugging the mouse, and consider trying a newer kernel or searching for a device-specific driver/quirk. If X is auto-configured, generate a template X config (for example with Xorg -configure), enable the evdev input driver for the mouse, back up any files before changing them, and restart X. When asking for help include the exact dmesg output, /var/log/Xorg.0.log, the cat /proc/bus/input/devices listing, xinput --list, and evtest output so people can see which layer is failing.

Recommended Answers

All 4 Replies

Member Avatar for Duki

I don't have a Xorg.conf file...

It should be in /etc correct?

Member Avatar for John A

>I don't have a Xorg.conf file...
Every system has one, although it's not always installed in the same place. The most common place for it to be located is /etc/X11/xorg.conf, but if you can't find it, try searching your filesystem for it.

Basically Xorg.conf is responsible for configuration of essential computer peripherals, monitor, etc. Changing this file allows you to effectively reconfigure your mouse to take advantage of (nearly) all of its buttons.

Member Avatar for Infarction

Actually, I've heard Fedora has a new way of configuring X11 without an xorg.conf, but I don't know if it's out in FC6 or not (I think it's an optional package, or perhaps still in beta). FC7 will likely not have an xorg.config though, IIRC.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.