I am trying to write a udev rule for my headset but i don't understand where i get the information to make the rule. I know i need to add
Code: RUN+="bash /home/luke-jennings/headset" at the end of it so the script i wrote runs. I don't know how to get any of the identifying info for the headset and which bits to use where. How do I get the information?
I'm trying to set my network interfaces so that they don't get random every boot.(eg assign eth0 to a network interface with a given MAC addr, and eth1 to the other one)I trew in a udev rule (in fact just modified the rules that was automatically generated and set the ethX in it) but the system ignores my udev rule.What am I missing ?Here is all the info :
Code: $cat /etc/udev/rules.d/70-persistent-net.rules # This file maintains persistent names for network interfaces.
On Ubuntu 10.04 I would like to setup udev to execute a backup script when a specific USB drive is inserted. Udev detects the USB drive, but my script is executed 7 times instead of just once. Can't figure out what's wrong.
My udev rules file:
Code: /etc/udev/rules.d# cat 20-stick.rules ACTION=="add", ATTRS{vendor}=="Kingston", ATTRS{model}=="DataTraveler G2 ", RUN="/usr/local/bin/sync.sh" Dummy backup script: connecting USB drive results in 7 times date written to /tmp/test code....
I'm running Ubuntu 9.10 (Karmic Koala) on a laptop and would like NumLock to automatically toggle depending on whether my USB keyboard is plugged in (numlock on) or unplugged (numlock off).
To accomplish this, I first installed the "numlockx" package. numlockx on and numlockx off works fine.
To hook into the device system, I thought I'd use udev. I have read "Writing udev rules", but I'm having trouble getting the udev rule to work.
First, here's an example of the dmesg output:
[20906.985102] usb 3-2: new low speed USB device using uhci_hcd and address 6 [20907.166403] usb 3-2: configuration #1 chosen from 1 choice [20907.192904] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/input/input20 [20907.193100] microsoft 0003:045E:00DB.000B: input,hidraw1: USB HID v1.11
The symlink part is fine but it does not appear to run the command when I plug the device in. I can run the command "/usr/local/bin/my_command" from the shell fine.
Code:
mount /dev/myusbstick_1 /media/TMPUSB && cryptsetup luksOpen /dev/md5 md5_crypt --key-file=/media/TMPUSB/key && vgscan && vgchange -ay && mount -a && umount /media/TMPUSB
What am I missing. I have tried +x in owner,group and other.By the way what does UDEV run as, I assumned +x on ROOT as that is the owner should be enough.
i need all my /media/* newly created by insertion of usb drives, chmodded 666.I tried some tips using various threads, but i failed.I'm on Slack 64 13.0.
I'm having some trouble with udev, in that it won't create me a symlink for the infrared device which is part of my Hauppauge Nova-TD-500 TV card.I've got the card installed, and for the most part working, but I want to have the infrared device on /dev/ir.I've created a rule in /etc/udev/rules.d/ called 55-dvb_usb_dib0700-ir.rules which contains this:
Code: SUBSYSTEM=="input", ATTR{name}=="IR-receiver inside an USB DVB receiver", RUN="/bin/date > /home/xbmc/foo", SYMLINK+="ir"
I'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
I have a netbook (MSI Wind U100 rebrand) that has one of those card readers built into the handrest. The thing is I've never used it once, and it keeps popping up in powertop as waking the cpu when it should just shut up and be quiet.Aside from breaking open the case and tearing it out, the immediate solution is to browse to /sys/bus/usb/devices/usb1/1-6/ and pipe 1 to the file remove. That disables it until system reboot or resume, at which point I have to do it all over again.
Code:
$ echo 1 | sudo tee /sys/bus/usb/devices/usb1/1-6/remove
Now I'd like to create an udev rule to make it not get initialized at all. A quick Google search found me this article on creating udev rules, and after toying about with the udevadm tool I managed to produce the attributes/properties of the device.
Code:
zorael@lethe:/sys/bus/usb/devices/usb1/1-6$ udevadm info -a -p $(pwd)
Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device.
I have a trayless SATA hotswap bay that is really terrific for quickly attaching and removing SATA hard drives. I'm trying to write a udev rule to create a symbolic link to the device node for the drive that is attached through the hotswap bay (/dev/bay -> /dev/sdX). This eliminates any ambiguity when performing destructive tasks (fdisk, etc). I'm running squeeze amd64. I've read through several tutorials and have it working somewhat. Here's the output of udevadm info for a drive attached via the hotswap bay.
Here is my udev rule DEVPATH=="/devices/pci0000:00/0000:00:11.0/host7/*", SUBSYSTEM=="block", SYMLINK+="bay%n"
This produces the desired behavior and gives me an fdisk-able device node. The problem I am having is that the "host" component of the DEVPATH varies from bootup to bootup. I'm just using on onboard SATA, host2-7, specifically host7. There is also onboard PATA, host0-1. It seems to just be random which "host"s are assigned to which controller. For example, the next time I boot the system, the onboard SATA will be host0-5 and the onboard PATA will be host6-7. In this simple case, I could just write 2 rules, one for each possibility and it would still be correct because of the different PCI addresses of the two controllers. But on systems with more SCSI (uh... libata, actually) controllers, a "host" file can point to different physical ports between bootstraps. This would be bad. Does anyone know of a way to write a rule to tie a device node to a specific physical SATA port on the motherboard/hba?
For example, can I write something to the effect: block all outbound UDP connections over port 53 except those going to IP 123.456.789. Or stated another way: Block outbound to port 53/udp NOT going to ip address 123.454.678Is it possible to do this? How would I write the argument?
Just wanted input for this script i have cobbeled together. Its not done yet. I am trying to think of ways to close up my outgoing while maintaining full functionality of my laptop ( irc, web stuff, a torrent or two, etc.) . Anyways, I have done some myself; as well as, pulling bits and pieces from other stuff out on the web. I am starting to wonder why i have to write a specific rule to check for spoofed packets if my default input is set top drop. wouldnt it be caught?
im using Debian (lenny) with 2.6.26 kernel, I'm trying to write udev rules in order to automount my usb pendrive, so I added this rules in udev:
SUBSYSTEM=="block", SUBSYSTEMS=="scsi",ATTRS{vendor}=="OTi ", ATTRS{model}=="Flash Disk ", NAME="penna128M",RUN="/usr/bin/ pmount /dev/penna128M"
I use pmount to install the device as normal user If i connect my device to the usb port I don't see nothing in /media/penna128M, BUT giving at the prompt cat /etc/mtab the last line is:
I just bought a USB hard disk and when I plug it in it gets mounted as owner root and group root. I tried writing a udev rule for it based on the following guide:Nothing seems to work, it always mounts as root. Slackware 13.1, KDE, Dell Optiplex GX280, Western Digital Passport USB 320 gig drive.I am a member of the plugdev group, so it seems to me a rule should not even be necessary.
Question (and Google results aren't making this clear): Ubuntu has both iptables & ip6tables installed. 1. If I set a rule in iptables, does that rule also apply to ipv6, or just ipv4?
2. If "no" to above, then it would be prudent to *also* set ip6tables rules as well if I want to maintain an active firewall, correct?
3. Does ip6tables rules have the same syntax and behavior (more or less) to iptables rules - i.e. can I just copy my iptables rules & change "iptables" to "ip6tables"?
4. Any gotchas or issues that I should be aware of?
I have the following problem. On Sytem/Preferences/Sound I pick output tab and change connector opiton from "Analog Speakers" to "Analog Outoput" and sound gone, after that i change it back, but sound don't come back.Microphone work file.
short version: My bluetooth headset keeps disconnecting.Full version:I'm using a 64-bit distro of 9.10 on a 1.6 GHz AMD Turion 64 laptop, with an external bluetooth dongle and a bluetooth headset. The dongle is recognized right off, the headset pairs perfectly through the bluetooth preferences panel, and sound redirects through the soundpreferences panel... For about 2 minutes. I know, it's odd, but every 2 minutes or so bluetooth disconnects from the headset. Sound shifts to the speakers, the applications don't miss a beat, and when I reconnect the headset through the bluetooth control it shifts right back to the headset. This happens regardless of other programs running. I tried it with no other applications running, and with a fairly heavy load, and it reoccurs.Here's the odd part: I had the CPU set on "Ondemand," to save battery power, but when I plugged in and shifted it to "Performance," it started happening ever 4 minutes or so...I've Googled around and found plenty about getting my headset to connect, but nothing about KEEPING it connected
I gotta say that Ubuntu 9.10 is a fantastic OS. I've been dual booting for about 4 years with Ubuntu and I want to scream to the world that Linux is finally a better OS than Mac or Windows. Having said that, I have an issue that I can't get around...
For some reason my USB headset is not being detected. I'm using the 32 bit version of Ubuntu 9.10 on a run-of-the-mill Intel-based desktop rig that I built myself. One of the mass-market programs that I still use is Skype so I can voice chat with friends and family - however, since the upgrade to 9.10 I can't get the mic to work (Plantronics USB headset - headset speakers work fine). The reason I can't get it to work is because the headset is not detected. The audio setting is set to "Analog Stereo Output" by default which does work perfectly in every other way.
What I want to do is hook up a mic to my computer and have the sound play through my bluetooth headset. Can this be done? I cant seem to figure out at all. It play fine through the computer speakers but nothing in BT. I have Ubuntu 10.04
So I'm trying to get my usb headset to work. Right now I can adjust the volume and mute using the buttons on the headset, but I can't get sound toplay through it or the microphone to work.When I go to System --> Preferences --> Sound I can see that there is a driver "USB PnP Sound Device" under the "Hardware" tab. When I go to the output tab and click on the "USB PnP Sound Device" then I just can't hear anything at all. I can adjust the volume with my headset regardless of whether I have "Internal Audio Analog Stereo" or "USB PnP Sound Device
I have a USB headset and coudn't get any sound. I had googled all around and had it working after setting the asound.conf file, but the following day when the system restarts it stoped bring sound. I have installing different packages (puse audio, padevchooser, pavucontrol, and asoundconf-gtk). The output of lsusb is the following:
[Code]...
what must i do. There is no sound in VLC or on firefox. I have already flash installed. I spent two days figuring out what I can do.
So I picked up a really cheap BT USB dongle (~$2) and can use the mic just fine but audio won't work. code...
I figure that I'm just overlooking something (I checked all the volume sliders and "mute" checkboxes I could find) or that I need to get a better BT dongle. Any thoughts?
I have Ubuntu 9.10, and am trying to get my headset to work with it. It's a USB headset, not a bluetooth headset. Anyway, the input is working. I switched my input from my internal mic to my USB one in my sound settings, and that fixed that. However, even if I set my output device to the USB, it still doesn't work. Does anyone have any advice? It works on Windows.
The headset is: Planet UP-100, Genius G-Talk Here's lsusb: Code: Bus 003 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
I'm attempting to record using Sound Recorder with my USB headset and i'm not being picked up. It's not the mic because I can use it while playing playstation.
I've been using a Freetalk USB Headset for a while on my Sony Vaio. It worked fine. Did a bit of travelling and used a different USB headset. Returned home, plugged in the Freetalk headset and find that Pulseaudio only sees the microphone part and not the speaker part. Using PAV Volume Control Configuration, against the Freetalk headset I only get the profile options of "Analog Mono Input" or "Off". When I first set it up, ages ago, I remember getting a load of options here and set the one for input and output. How to I get more options to set up the headset properly?
I just upgraded to ubuntu 10.04 and everything is ok except my USB Logitech Headset. The problem is that volume of the device is very low and I can't hear the music or any sound like I use to heard. Even if I increase the volume up to 100%, I still hearing the sound with a very low volume. But if I use the analog output of my sound card I can hear very well. I remember that i used to have this problem in ubuntu 9.10 but I fixed with a script that I found it in this forum, but I can't find it again.
:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 046d:0a01 Logitech, Inc. USB Headset Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Hi, I have a Creative HS-1200 headset. When I am listening to sound through it, and something makes a motion on screen(compiz, movie...really anything) then the sound is distorted. Like it takes a nanosecond pauses to redraw. This does not happen with my normal soundcard. Can anyone tell me how can I fix this?