Tag Info

New answers tagged

0

I've faced before same problem with non effective ignore_device. I couldn't figure out why then I always go with other solutions. Well, ignore_device removed with udev release 148. See release note or changelog If you noticed, all topics suggesting the use of it are old (~ 2009). A quick alternative is to use: ENV{UDISKS_PRESENTATION_HIDE}="1" (Ubuntu ...


1

So, I sorta solved this, and it was a PAIN to do. I reexamined the restrictions in my rules, and I changed functionality. Apparently, 12.04 doesn't honor the ignore_device option. So, I improvised and wrote an unmount script. Since there's only one functional USB port on these systems, we end up with the following, which I KNOW may break other things: ...


0

I had a similar problem: update-initramfs: deferring update (trigger activated) insserv: warning: script 'S85vpnagentd_init' missing LSB tags and overrides insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides insserv: There is a loop between service ondemand and procps if started insserv: loop involving service procps at depth 2 ...


6

For general use, If you would like to run your program for any USB storage. Use the driver for the rule match. Add a udev rules file sudo nano /etc/udev/rules.d/90-detect-storage.rules Add this rule ACTION=="add", DRIVERS=="usb-storage", DRIVER=="sd", RUN+="/pathto/yourprogram" If you want your program to distinguish the disks, so it runs different ...


0

Crate new rule file at /etc/udev/rules.d/ ie 70-new-rules Edit it with having code like (https://wiki.archlinux.org/index.php/Udev) define your custom rule definition. like specific serial device name etc.. you can follow below mention link. udev rules


5

You can use udev to run an albitrary command. To make it work, create a rule in /etc/udev/rules.d/: sudo nano /etc/udev/rules.d/my-usb-device.rules And enter: ACTION=="add", ATTRS{idProduct}=="XXXX", ATTRS{idVendor}=="YYYY", RUN+="/location/of/my/command" NOTE: The XXXX and YYYY values will be taken from lsusb output.


0

As answered elsewhere: https://unix.stackexchange.com/questions/119593/is-there-a-way-to-change-device-names-in-dev-directory The udev manpage says: NAME The name to use for a network interface. See systemd.link(5) for a higher-level mechanism for setting the interface name. The name of a device node cannot be changed by udev, only additional ...


1

I believe at least three things affect CRDA. First, as you already know, the file /etc/default/crda should have, in your case, one uncommented line: REGDOMAIN=DE Second, it is the module cfg80211 that is complaining in dmesg; let's try to fix it: sudo -i echo "options cfg80211 ieee80211_regdom=DE" > /etc/modprobe.d/cfg80211.conf exit Finally, ...


0

I changed the file /lib/systemd/system/udev-finish.service to include basic.target in its After-configuration, which seems to do the trick for me: [Unit] Description=Copy rules generated while the root was ro DefaultDependencies=no After=basic.target systemd-udevd.service systemd-udev-settle.service [Service] Type=oneshot RemainAfterExit=yes ...


0

You could try this enter settings, and then network, and then delete and turn of network, and then turn it on again and reboot, and if it dos not self set up a new network create one, and it might work, and remember to write down the ip, based and the mac adr, and the code for the security. (Wpa).


1

The original solution posted by Oli did not work for me, but it works after I changed the key numbers "0c022d" and "0c022e" to "c022d" and "c022e". I'm using a 4000 model, so I can't verify if the same change is needed for the 7000 model. To repeat Oli's answer, here is what I did: create a new file by running sudo nano ...


0

I found my answer right there: Huawei E3531: view signal strength? sorry for the question


0

Using lvdisplay, vgscan, vgremove as @user195059 suggests probably works, but they are in the lvm2 package which I no longer have installed. Instead I used $ sudo dmsetup info which showed "Name: unwantedDevice" of my unwanted /dev/mapper/unwantedDevice and "State: ACTIVE". I unmounted the device (from its menu in the Unity panel), then issued $ sudo ...



Top 50 recent answers are included