My touchscreen "LG Display LGD-MultiTouch" will be recognized sometimes as /dev/input/event0 and sometimes as /dev/input/event3. How to hardcode /dev/input/event0 using udev and xorg.conf?
How to hardcode/fix a udev roule for /dev/input/event0?For example my touchscreen device jumped after restart, sometimes will be recognized as input3 and sometimes as input0.
I have just bought a DVB-T usb dongle to watch some TV. The software I'm using is vdr, which has to be started through the /etc/init.d/vdr service. I have created a udev script that executes the service on device insertion. It works nicely, however now when I boot up the computer it takes ages to get to desktop. I believe it is because of the WAIT_FOR part. But without this part, the service starts too soon because the usb dongle has been inserted but the firmware has not finished loading. Can someone point out an alternative way to do it? The script is here [URL].
I am using a 3rd party kernel driver that does not support udev properly. When I was using wheezy I placed the required device files in /lib/udev/devices.
The udev in jessie does not appear to support this. Is there any way to have udev create these device files or will I have to create then using a script at boot-up?
my thinkpad Edge 11 has some problems with the touchpad and the trackpoint, so i want to permanently disable the touchpad, but not the TrackPoint. Both are PS2 devices.
I am using Debian testing i386. Just upgraded to 2.6.39-2-686-pae. After reboot, and ever since, I am getting warning: WARNING: Could not find hdaps input device (No such file or directory). You may be using an incompatible version of the hdaps module. Falling back to reading the position from sysfs (uses more power). Use '-y' to silence this warning.
I am working on an embedded system, which is an USB MSC device that supports some vendor specific scsi commands. I am using FC10 laptop as USB host for testing, and it runs some small apps based on sg3. All has been well for ~ a week. The FC10 laptop is able to communicate with the device and retrieve data. Suddenly, starting from today, the laptop is not able to properly detect the device. When plugged-in, the MSC device is detected as input device (I thought). This is observed from "dmesg" output and changes in "/dev/input/".The device under development is running at full speed. When I connect to winXP, no problem. A windows file explorer pops up, showing the content of the drive.Also, the FC10 has no problem with other USB flash drive (high speed).
I have a Linux server that runs the Sybase DB. Sybase suggests using character devices to access raw devices rather than O_DIRECT to block devices, or cooked FS's. So, I went ahead and configured /etc/sysconfig/rawdevices as such:
This works fine. I set 'chkconfig rawdevices on' and all is well. I read that this method is deprecated and went about trying to accomplish the same via Udev rules. I already use udev rules in /etc/udev/rules.d/60-raw.rules to set permissions on these devices, i.e. ACTION=="add", KERNEL=="raw*", OWNER=="sybase", GROUP=="sybase", MODE=="0660"
That works fine. I even set symbolic links: KERNEL=="raw1", SYMLINK+="vg01/rtempdb" KERNEL=="raw2", SYMLINK+="vg01/rtestdb1" KERNEL=="raw3", SYMLINK+="vg01/rfakedb2"
But I cannot seem to get the actual device creation piece to work within udev (it only works using rawdevices). I've tried: ACTION=="add", KERNEL=="vg01/tempdb", RUN+="/bin/raw /dev/raw/raw1 %N"
No errors, but nothing happens. The device just doesn't create. I've also tried doing it by passing major and minor numbers. Is it possible to get all of this into udev rules or am I stuck with rawdevices? I'm also utterly confused as to the future of rawdevices... the raw man page said it was deprecated, and now at v5.5 it has that piece taken out. Also RHEL 5.3 dropped support for rawdevices in initscripts only to add itback in 5.4. I'm an admin, not a DBA, so I cannot say if this is a bad or good way, only that it is the way the vendor supports and recommends, so it is the way that I must go... just trying to make it work as "un-deprecated" and cleanly as possible.
Having finally made the switch from Windows (7 Professional) to Linux (Fedora 13) on my laptop, I'm now trying to get all my devices working, specifically an Olympus VN-4100PC Digital Voice Recorder. I've installed odvr and it works in root, but not as a normal user. The installation instructions say: odvr *requires* access to the user-space USB interface.
It is recommended to place "41-odvr.rules" into "/etc/udev/rules.d" or setup your own udev rules rather than running odvr as root. After changing udev rules, don't forget to run "udevcontrol reload_rules" and to replugin your DVR. Again, root privileges are required unless udev is properly setup. The file "41-odvr.rules" (designed for Ubuntu) has the following content: SUBSYSTEM=="usb", SYSFS{idVendor}=="07b4", SYSFS{idProduct}=="020d", ACTION=="add", GROUP="audio", MODE="0664"
I tried just doing what it said and copying it to "/etc/udev/rules.d" but it didn't seem to work. Looking at other files, I then changed it to: SUBSYSTEM=="usb", ATTR{idVendor}=="07b4", ATTR{idProduct}=="020d", ACTION=="add", GROUP="audio", MODE="0664"
And now if I do "ls -l /dev/bus/usb/002", I get: crw-rw-r--. 1 root audio 189, 134 Oct 15 01:21 007
Which seems to suggest that it is running the "41-odvr.rules" file, since lsusb gives: Bus 002 Device 007: ID 07b4:020d Olympus Optical Co., Ltd Digital Voice Recorder VN-240PC
But odvr still doesn't work as a normal user, giving: Failed to open Olympus device: couldn't claim interface
I need to prevent udev from creating the /dev/v4l/by-path/* and /dev/v4l/by-id/* files upon connecting my webcam. The problem is that Kopete doesn't want to display the video if these files are present. It works fine if I remove them, but I'd rather not have them created in the first place, since they seem to be completely useless anyway.
My co-workers and I are trying to develop a USB device, which uses an FTDI chip as a USB-serial controller. The thing is, we would ideally like to set a custom idVendor and idProduct on the FTDI chip. The problem occurs that when we set custom idVendor and idProduct values, udev(7) loads the "usb" driver. If we leave the idVendor and idProduct values to their originals, udev(7) loads the "ftdi_sio" driver. The whole reason for the custom idVendor and idProduct values is so that I can (hopefully) write a udev(7) rule to map that particular device to a specific entry in /dev. Is there a way to write a udev(7) rule so that you can forcefully load a particular driver for a device? Is there something else that could be done to get a similar result?
how udev rules work to create device files. Following is what I did for that: Up on plugging in my phone (sony w800i), I am getting a device file 'devcdc-wdm0' created. I just tried to figure out the rule which is responsible for the creation of this particular file.
I searched in 'etcudev ules.d' and 'libudev ules.d' for the string 'cdc-wdm' to find that rule. But I am not getting any hits in that search. Could any one help me out in this one.
On my debian lenny OS I have an external usb hard disk I would like to automount it at boot. So I edited the /etc/fstab file in order to automount /dev/sdb1. It worked without problem. Then I recompiled the kernel and, as consequence, /dev/sdb1 changed to /dev/sdc1. I started playing with udev in order to match the now called /dev/sdc1 and to change its name in /dev/maxtor (being maxtor the brand of the hard disk). Obviously I edited also /etc/fstab: /dev/sdb1 is now /dev/maxtor.
The boot automount doesn't work anymore. On the boot sequence I can read the message "Mounting local filesystem...mount: special device /dev/maxtor does not exist FAILED". But when I log into the system I can run the command "mount /dev/maxtor /mnt/maxtor" and it works! So, IMHO, my udev rule is correct otherwise also the manual mount wouldn't work, right? I have to tell to udev to create /dev/maxtor BEFORE the boot automount process.
I tried to delete my udev rule and to edit /etc/fstab changing /dev/maxtor in /dev/sdc1 (the name udev gave to my hard disk after kernel recompile, before was /dev/sdb1) and it didn't work: on boot process I always see the "Mounting local filesystem...mount: special device /dev/sdc1 does not exist Failed". Then I tried to change /dev/sdc1 in /dev/sdb1 in /etc/fstab and to reboot with the old original kernel and int this way it works. With my compiled kernel, the OS seems to have lost the capacity to detect my device node correctly.
Some times I boot up, and udev has labelled what is usually eth0 as eth1. Of course, my rc.inet1.conf is configured for seeing internet at eth0, so no connection, quite obviously. Then I reboot and the device label is back to "eth0". Actually I'm still not able to get connected, even at eth0, despite my nameservers being OK, and the default route gateway being all OK. PS. I have a static ip address.
I have a Kore Controller from Native Instruments [URL] using it as a sound card on Fedora 12. Its input knobs are supported by Linux, too, but they are pretty useless for me.It came out that these input knobs send mouse movements from time to time, letting my mouse pointer jumping to the upper left corner of the screen.
So I want to disable the knobs, i.e. I want X to not interpret these "knob actions" as mouse movements. What is the best way to achive this? Can I disable it somewhere in HAL configuration or do I have to modify xorg.conf? And how do I do this?Simply plugging out the Kore Controller is not an option for me because I use it as sound card.
I just bought an M-Audio Keystation 49e off of craigslist and I'm at a bit of a loss on where to start to use it as an input device for muse or rosegarden.
Everything seems setup, but I'm at a loss on how to use it in the applications. It doesn't have any sound synthesis abilities on the keyboard, it's just an input device. Without the keyboard I usually go this route:
jackd -R -d alsa & timidity -Oj -iA & rosegarden
And midi events output sounds and all that jazz. I'm wanting to input notes / record from the keyboard. But still output all sounds in the aforementioned manner. If I could get those to happen while I record that would help a bunch. Maybe it's just too late in the day for me to wrap my brain around it at the moment.
Long story short - on my laptop, touch pad is recognised as PS/2 mouse. Everything works (moving, clicking, dragging, vertical scroll). But I often accidental click the pad while typing.Synaptic driver recognises it as ALPS glide point it seems (synclient -m 1 gives me back only x,y difference for the gestures, but X,Y coordinates are always 0,0) - so then I get everything right including disabling mouse on keyboard input - but scrolling doesn't work So I came up with 2 possible ideas - which I don't know how to do/test:1. Perhaps there is a way to disable mouse input while typing without synaptics drivers?2. Create a dummy input device (mouse), and tie synaptics driver to it. Add another input device in xorg.conf to point to the real touch pad as PS/2. And make the synaptics disable "real mouse" by enabling GuestMouseOff option.
I need to set the default input device to be the microphone on my webcam for when I skype, but it seems to keep resetting itself, so I keep going in and changing it.
I am right clicking the volume icon and going into Sound Prefs -> Input, and selecting the camera.
How do I stop it from forgetting this and resetting it?
I am trying to record a video clip, using my webcam, but sound synchronisation is always poor. I have used Cheese, UCView and VLC. One possible cause is explained in the reply to this question, but I am not an expert. In desperation, I now want to try ffmpeg. The ffmpeg documentation gives the following example
Code: ffmpeg -f oss -i /dev/dsp -f video4linux2 -i /dev/video0 /tmp/out.mpg My system has no /dev/dsp, but does have /dev/snd with these files Code: $ ls /dev/snd
I am trying to record a video clip, using my webcam, but sound synchronisation is always poor. I have used Cheese, UCView and VLC. One possible cause is explained in the reply to this question, but I am not an expert. In desperation, I now want to try ffmpeg. The ffmpeg documentation gives the following example
Code: ffmpeg -f oss -i /dev/dsp -f video4linux2 -i /dev/video0 /tmp/out.mpg I want to use alsa, not oss, but need to know the alsa input device name (/dev/dsp is created by loading the oss modules). By running alsamixer, I have nutted out that /dev/snd/controlC0 refers to the HDA Intel sound card, ~controlC1 is my USB webcam and ~controlC29 is the microphone built in to my notebook, but these are control devices, not inputs.
[Code]...
However, that does not explain which device is the mic built in to the laptop: by my calculation, it should be pcmC0D1c, but there is no such device. In /proc/asound/card0/pcm0c/ I have directories for sub0 and sub1, which I am guessing relate to the mic jack and inbuilt mic respectively. Do two physical mics share one logical device somehow? I am starting to really confuse myself, if you haven't guessed that already.
I think my question boils down to "How do I record a video clip on Fedora 14 using ffmpeg?", but I am specifically interested in knowing how to specify each of the alsa sound input devices for my system.
When X.org boots up, Synaptics touchpad works well. But when I remove the module it falls back to /dev/input/mice and don't use normal driver even when touchpad is available again.
Xorg.0.log: ... (II) XINPUT: Adding extended input device "Synaptics Touchpad" (type: TOUCHPAD) (--) Synaptics Touchpad: touchpad found # { rmmod psmouse && echo mem > /sys/power/state && modprobe psmouse; } (WW) : No Device specified, looking for one... (II) : Setting Device option to "/dev/input/mice" ...
How to tell X.org to try it's InputDevice again (without restarting X server)? rmmod psmouse is needed to prevent crashing of Acer Extensa 5220 when resuming from suspend-to-ram. Found answer myself: Doing xinput set-int-prop "Synaptics Touchpad" "Device Enabled" 8 1 after reloading the kernel module reloads touchpad. Now suspend-to-ram works OK.
I have installed Lynx and want to use two X servers at the same time. Each server has its own ServerLayout section in xorg.cong. The first ServerLayout Section has AutoAddDevices enabled, so that new input devices are added automatically. The second ServerLayout has AutoAddDevices disabled, and one InputDecice pointing to /dev/input/mouse3. That way, this mouse is the only input decive affecting the second X instance.
Unfortunately, this mouse is also controlling the first server (due to AutoAddDecives). Can anyone tell me how to disable this? I want every input device to be added to the first server, except this mouse. In earlier versions of ubuntu, I used a hal rule to make hal ignore this mouse. So it was not added to the first server. Now that hal is not used by lynx anymore, I don't know how to do this. I have already read some things about udev and the xorg.conf.d folder.
I use a USB webcam with a built in microphone. It works fine, but every time I plug it in I have to go to sound properties and select it as the input device. There are no other input devices present on my system. Since it's the only one there, is there any way to get it to automatically select when I plug it in? If not, I think that would be good functionality to add. Does anyone know who or what team to contact about that?
No audio input device can be found in sound preference>input but in sound preference>hardware>it shows the input webcam recorder device.
When I use
Code: alsamixer
onto terminal it shows this
and also i checked cable device and everything. And it was working till I last hour. I rebooted computer then there's some problem, I haven't change anything before or after rebooting.
I'm using FFADO on JACK in order to use my firewire device (M-Audio Profire 610) and I seem to have the opposite issue as others who have similar problems. Everything starts up fine, and I can record audio into Ardour using my inputs, but I can't get any output from any of my 8 line outs.
I've checked the connections using QjackCtl, and I tried to route audio from another program (Audacious) but I can't seem to pull audio out of the device (or the computer won't send my device audio?).
I can't use my line-in/microphone jack. In system-management-sound input tab there is no input device listed, and the input controls are grayed-out. sudo lshw -C sound produced:
description: Audio device product: N10/ICH 7 Family High Definition Audio Controller vendor: Intel Corporation physical id: 1b
I have a bluetooth usb dongle which I cannot get to work. I start kbluetooth. The icon in system tray is blue (not grey). Right click on it -> Device Manager -> New The wizard starts. It sees my Palm, but then says: "Sorry your Bluetooth Device does not support input Service". I don't know what to do. Opensuse 11.3 kde 4.5 kbluetooth 0.4.2-10.5
