Tag Info

New answers tagged

3

As per struct usb_device: urbnum number of URBs submitted for the whole device where URB stands for USB Request Block. An URB consists of all relevant information to execute any USB transaction and deliver the data and status back. See also: Kernel Documentation USB Urbs


11

If a USB flash device and USB cdrom is connected then only difference that I can find out is their kernel driver. Both uses the common usb and usb-storage kernel module but in addition to that CD-ROM uses sr module while USB uses the sd module. Based on this info, you can write UDEV rule


0

You can find it in /sys/class/net directory. it it Symbolic link to other file in /sys/device/../../, following is my virtual machine (linux kernel 3.10) output. And you can use command udevadm info <filename> to look over its attribute lrwxrwxrwx. 1 root root 0 Apr 3 13:38 ens33 -> ../../devices/pci0000:00/0000:00:11.0/0000:02:01.0/net/ens33


0

I had a similar problem bringing a USB cellular modem online with consistent numbering in a system along with other USB tty devices vying for /dev/ttyUSB* numbers. In my case it was a EuroTech ReliaCELL 10-20-32 with the Telit chipset. I solved the problem using some ideas from here, ending up with the following excerpt in my .rules: SUBSYSTEMS=="usb", ...


0

The question already has an accepted answer, but I decided to share my variation of the solution provided by derobert. My requirements were slightly different - in addition to providing "incrementing" index numbers to new devices - I wanted reacquire index numbers that were given up by devices that have been removed from the system. The udev rule for ...


1

HAL is defunct and no longer used in modern distros. ACPI is a specification for how the bios and kernel interact relating to system hardware enumeration and power management. udev is a daemon that is notified by the kernel when hardware changes, such as when you plug in a new disk drive, and may take actions such as detecting what filesystems are on the ...


1

I assume you're referring to a btrfs raid1 filesystem created on top of two block devices created with something like mkfs.btrfs -L Raid1 -d raid1 /dev/sd* /dev/sd* Reproduced this setup locally (based on Funtoo instructions from here): $ dd if=/dev/zero of=/tmp/btrfs-vol0.img bs=1G count=1 $ dd if=/dev/zero of=/tmp/btrfs-vol1.img bs=1G count=1 $ sudo ...



Top 50 recent answers are included