SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just finished upgrading to 12.2 and am having a problem with my custom udev rule. It's setup to create the mouse node at /dev/input/mx1000. The rule worked great under 12.1 but after the update to 12.2 the rule doesn't seem to be working. When I boot into X, the mouse doesn't work, and when I check /dev/input the mx1000 node is never created.
I have moved all of the 'new' config files over including rc.udev. The rule exists as /etc/udev/rules.d/10-local.rules. I saw in the CHANGES_AND_HINTS file that the rules folder moved, but from my understanding udev should still read the rules in /etc/udev/rules.d as well.
I know udev was updated to 135, so I suspected a syntax problem. I tried quite a few variations on the rule to see if I can get it to work, but so far I've had no luck.
If anyone has and ideas or can see a problem with my syntax let me know. Udev seems to be working ok - when I plug in a USB device it recognizes it and sets up the node. Im just not sure if the rule is incorrect or if udev isn't reading the rule file.
Dec 25 19:42:40 cloud kernel: usb 3-1: new low speed USB device using uhci_hcd and address 25
Dec 25 19:42:40 cloud kernel: usb 3-1: configuration #1 chosen from 1 choice
Dec 25 19:42:40 cloud kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input26
Dec 25 19:42:40 cloud kernel: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-1
Dec 25 19:42:40 cloud kernel: usb 3-1: New USB device found, idVendor=046d, idProduct=c50e
Dec 25 19:42:40 cloud kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 25 19:42:40 cloud kernel: usb 3-1: Product: USB Receiver
Dec 25 19:42:40 cloud kernel: usb 3-1: Manufacturer: Logitech
As far as the symlink, I replaced the "NAME=" line with SYMLINK+="input/mx1000". Upon restarting udev and pulling the dongle a symlink was created pointing to mouse1, however the link didnt work for my xorg.conf.
EDIT: At least now I know udev is matching the rule.
hi i have exactly the same problem here, from what i have understood the evdev driver needs a path to an event not to a device input node, i don't know why but with slackware 12.2 it's impossible to rename an event to a fixed name, i have tried a lot of rules and nothing works, i really don't have ideas on how to fix the problem a rule like this one should create a symlink to the mouse event but doesn't work