Udev doesn't create sd* devices in /dev

Today I updated udev package and after it I can't start my system. The booting stops with the message about check filesystem manually. When I tried to do this I couldn't find any sd* devices in /dev. Kernel detects all drives and correspond files presents in /sys/block directory. I can make device files with mknod command using information from /sys.
How do I make udev to create device files in /dev?
Sorry for bad English.

I just found one more interesting thing. When I test udev rules by "udevadm test /block/sdb/sdb2" udev creates correct device files - /dev/disk/ dev/block and /dev/sd*. But at daemon mode - udevd --daemon it doesn't do anything!
Does anybody know how to fix this?

Similar Messages

[SOLVED] udev not creating gamepad device

I'm having trouble with an USB gamepad that actually is an Playstation controller adapter in Arch, I cannot use it in PCSX-Reloaded for instance.
Here's the output of lsusb when plugged:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 011: ID 0e8f:0003 GreenAsia Inc. MaxFire Blaze2
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0489:e036 Foxconn / Hon Hai
Bus 001 Device 004: ID 04f2:b32f Chicony Electronics Co., Ltd
The gamepad is correctly listed as Bus 003 Device 011 (GreenAsia Inc. MaxFire Blaze2). But I think udev is not creating the /dev/input/js0 device as it should (it works on my Slackware 14.0 box), as the output of ls /dev/input is:
by-id event1 event12 event3 event6 event9 mouse1
by-path event10 event13 event4 event7 mice
event0 event11 event2 event5 event8 mouse0
What should I do? Does other USB gamepads are configured automatically? Is my device too old/incompatible with Arch? Or is it a bug?
Last edited by lmello (2013-01-09 09:36:33)

I would be nice if you would share your solution so other members could benefit - even if it is a mistake or misconfiguration by yourself
My Dragonfire pad requires the "joydev" module, for example.
# modprobe joydev
EDIT
*** Thanks You were filling the void while I was typing ***
Last edited by satanselbow (2013-01-09 09:41:10)

/etc/crypttab doesn't create /dev/mapper/swap

I'm not lucky with encryption these days: keyfile on USB stick doesn't work ( http://bbs.archlinux.org/viewtopic.php?id=52507 ), so revert to the passphrase thing.
I had swap encryption working using the old rc.local way etc. now there's a new way... "SWAP" keyword inside /etc/crypttab and no rc.local changes, wonderful right? Wrong. It doesn't work, if you put (example)
swap /dev/sda3 SWAP -c aes-xts-plain -h whirlpool -s 512
inside /etc/crypttab and reboot, it doesn't create any /dev/mapper/swap device (so it can't swapon).
Where's the issue?
Last edited by ekerazha (2008-08-20 13:22:35)

dw wrote:
hi ekerazha.
i am playing around with system encryption a bit lately and i am experiencing exactly the same. my question. were you able to solve this?
No... maybe reverting to the "old" way (no SWAP keyword etc.)
Last edited by ekerazha (2008-08-23 16:36:41)

(SOLVED) uinput doesn't create "/dev/misc/uinput"

Hello !
After closely following the Wiimote connection guide for the third time, I decided to ask you gurus here on the forums about the issue.
The instructions say:
First you need to make sure to load the uinput module:
$ sudo modprobe uinput
You should have a device in /dev/misc/uinput now.
However, the "/dev/misc" folder NEVER gets created, even after a reboot with "uinput" placed in the modules section of the rc.conf.
Therefore later, when I try to make the Wiimote function as an input device (with the "wminput" command), it gives out the error:
"unable to open uinput".
Is this a kernel error?
Does anyone know a way around it?
I found this information about a similar problem being resolved by using mknod here:
https://bugzilla.redhat.com/show_bug.cgi?id=213854
To summarize, the idea of this bug on Redhat is:
module loads but device node is not created.
If created manually with mknod everything works fine.
Expected results:
udev should create the device node
Thank you for all your help in advance,
UFOKatarn
Last edited by UFOKatarn (2010-09-05 20:12:45)

Thanks for the tip!
All I had to do was to allow non-root users access to uinput.
For all that might be ssearching the forum and stumble upon the same problem, this is done like this:
1.)
create a new file in the folder /etc/udev/rules.d
I named it user.rules, but the name and/or its extension don't matter
2.)
paste the following line into it
KERNEL=="uinput", GROUP="wheel", MODE:="0660"
I think MODE:="0660" allows all users to use uinput, but I'm not sure.
Solely having my user in the "wheel" group and NOT having the "MODE:="0660" in the rule didn't allow my user to access uinput.
3.)
reboot
4.)
start the command "wminput" as a normal user
Regards,
UFOKatarn

[Solved] udev rules: serial for persistent device naming disappeared

Hello,
since the latest upgrade of udev and kmod I cant't mount my external e-SATA hard disk with my working udev rules.
This is my udev rule:
$ cat /etc/udev/rules.d/66-persistent_esata.rules
KERNEL=="sd?1", SUBSYSTEMS=="block", ENV{ID_SERIAL_SHORT}=="S1VSJ1LS301247", NAME="aluguard"
When plugged in, I could decrypt and mount it with "sudo cryptsetup luksOpen /dev/aluguard aluguard && mount /mnt/aluguard".
Since the update above I get "Device /dev/aluguard doesn't exist or access denied."
While I re-checked https://wiki.archlinux.org/index.php/Ma … _with_udev, I discovered, that the serial entry in the output of udevadm has vanished:
$ udevadm info -a -p $(udevadm info -q path -n /dev/sdg)
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.
looking at device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg':
KERNEL=="sdg"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{ext_range}=="256"
ATTR{removable}=="0"
ATTR{ro}=="0"
ATTR{size}=="1953525168"
ATTR{alignment_offset}=="0"
ATTR{discard_alignment}=="0"
ATTR{capability}=="50"
ATTR{stat}==" 96 24 762 780 0 0 0 0 0 780 780"
ATTR{inflight}==" 0 0"
ATTR{events}==""
ATTR{events_async}==""
ATTR{events_poll_msecs}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0':
KERNELS=="3:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{device_blocked}=="0"
ATTRS{type}=="0"
ATTRS{scsi_level}=="6"
ATTRS{vendor}=="ATA "
ATTRS{model}=="SAMSUNG HD103SI "
ATTRS{rev}=="1AG0"
ATTRS{state}=="running"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{iorequest_cnt}=="0xa2"
ATTRS{iodone_cnt}=="0x98"
ATTRS{ioerr_cnt}=="0xc"
ATTRS{evt_media_change}=="0"
ATTRS{queue_depth}=="31"
ATTRS{queue_ramp_up_period}=="120000"
ATTRS{queue_type}=="simple"
looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0':
KERNELS=="target3:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0/host3':
KERNELS=="host3"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0':
KERNELS=="0000:00:09.0"
SUBSYSTEMS=="pci"
DRIVERS=="ahci"
ATTRS{vendor}=="0x10de"
ATTRS{device}=="0x0554"
ATTRS{subsystem_vendor}=="0x1849"
ATTRS{subsystem_device}=="0x0554"
ATTRS{class}=="0x010601"
ATTRS{irq}=="23"
ATTRS{local_cpus}=="00000000,00000003"
ATTRS{local_cpulist}=="0-1"
ATTRS{numa_node}=="0"
ATTRS{dma_mask_bits}=="64"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{enable}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
What is the reason for this strange behaviour, and how can I get back the serial entry?
Thank in advance!
Last edited by indianahorst (2012-01-31 13:03:20)

$ udevadm info -q all -n /dev/sdg1
P: /devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
N: sdg1
S: disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1
S: disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1
S: disk/by-id/wwn-0x50024e900136a03e-part1
S: disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1
S: disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: DEVLINKS=/dev/disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1 /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1 /dev/disk/by-id/wwn-0x50024e900136a03e-part1 /dev/disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1 /dev/disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: DEVNAME=/dev/sdg1
E: DEVPATH=/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
E: DEVTYPE=partition
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_AAM=1
E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254
E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=0
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_PUIS=1
E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=194
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=194
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_FS_TYPE=crypto_LUKS
E: ID_FS_USAGE=crypto
E: ID_FS_UUID=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: ID_FS_UUID_ENC=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: ID_FS_VERSION=1
E: ID_MODEL=SAMSUNG_HD103SI
E: ID_MODEL_ENC=SAMSUNG\x20HD103SI\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_ENTRY_TYPE=0x83
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:00:09.0-scsi-3:0:0:0
E: ID_PATH_TAG=pci-0000_00_09_0-scsi-3_0_0_0
E: ID_REVISION=1AG01131
E: ID_SCSI_COMPAT=SATA_SAMSUNG_HD103SIS1VSJ1LS301247
E: ID_SERIAL=SAMSUNG_HD103SI_S1VSJ1LS301247
E: ID_SERIAL_SHORT=S1VSJ1LS301247
E: ID_TYPE=disk
E: ID_WWN=0x50024e900136a03e
E: ID_WWN_WITH_EXTENSION=0x50024e900136a03e
E: MAJOR=8
E: MINOR=97
E: PART_ENTRY_DISK=8:96
E: PART_ENTRY_NUMBER=1
E: PART_ENTRY_OFFSET=63
E: PART_ENTRY_SCHEME=dos
E: PART_ENTRY_SIZE=1953520002
E: SUBSYSTEM=block
E: UDEV_LOG=3
E: UDISKS_PARTITION=1
E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
E: UDISKS_PARTITION_NUMBER=1
E: UDISKS_PARTITION_OFFSET=32256
E: UDISKS_PARTITION_SCHEME=mbr
E: UDISKS_PARTITION_SIZE=1000202241024
E: UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg
E: UDISKS_PARTITION_TYPE=0x83
E: UDISKS_PRESENTATION_NOPOLICY=0
E: USEC_INITIALIZED=6897248001
OK, there is the serial.... but the problem persists - udev doesn't execute the rule and doesn't create /dev/aluguard.

[SOLVED]udev doesn't execute my custom rule

Here is my device info:
XSign rules.d # udevadm info -a -n /dev/sdb1
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.
looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1':
KERNEL=="sdb1"
SUBSYSTEM=="block"
DRIVER==""
ATTR{ro}=="0"
ATTR{size}=="15685569"
ATTR{stat}==" 240 1120 1906 320 0 0 0 0 0 320 320"
ATTR{partition}=="1"
ATTR{start}=="63"
ATTR{discard_alignment}=="0"
ATTR{alignment_offset}=="0"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb':
KERNELS=="sdb"
SUBSYSTEMS=="block"
DRIVERS==""
ATTRS{ro}=="0"
ATTRS{size}=="15685632"
ATTRS{stat}==" 255 1123 2050 330 0 0 0 0 0 330 330"
ATTRS{range}=="16"
ATTRS{discard_alignment}=="0"
ATTRS{events}=="media_change"
ATTRS{ext_range}=="256"
ATTRS{events_poll_msecs}=="-1"
ATTRS{alignment_offset}=="0"
ATTRS{inflight}==" 0 0"
ATTRS{removable}=="1"
ATTRS{capability}=="51"
ATTRS{events_async}==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0':
KERNELS=="8:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{rev}=="1.00"
ATTRS{type}=="0"
ATTRS{scsi_level}=="0"
ATTRS{model}=="USB SD Reader "
ATTRS{state}=="running"
ATTRS{queue_type}=="none"
ATTRS{iodone_cnt}=="0x1dd"
ATTRS{iorequest_cnt}=="0x1dd"
ATTRS{timeout}=="30"
ATTRS{evt_media_change}=="0"
ATTRS{max_sectors}=="240"
ATTRS{ioerr_cnt}=="0x2"
ATTRS{queue_depth}=="1"
ATTRS{vendor}=="Generic "
ATTRS{device_blocked}=="0"
ATTRS{iocounterbits}=="32"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0':
KERNELS=="target8:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8':
KERNELS=="host8"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0':
KERNELS=="1-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{bInterfaceClass}=="08"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1':
KERNELS=="1-1.1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1.1"
ATTRS{idVendor}=="090c"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="8"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="500mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="12345678901234567890"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="1264"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Silicon Motion, Inc."
ATTRS{removable}=="removable"
ATTRS{idProduct}=="6200"
ATTRS{bDeviceClass}=="00"
ATTRS{product}=="Generic USB2.0 card "
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="8087"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="6"
ATTRS{bcdDevice}=="0000"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="130"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="fixed"
ATTRS{idProduct}=="0020"
ATTRS{bDeviceClass}=="09"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="3"
ATTRS{bcdDevice}=="0308"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:1a.0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="26"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.8.3-2-ARCH ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:1a.0':
KERNELS=="0000:00:1a.0"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="23"
ATTRS{subsystem_vendor}=="0x17aa"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="ff"
ATTRS{device}=="0x3b3c"
ATTRS{uframe_periodic_max}=="100"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-7"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x2163"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
and rule:
XSign rules.d # cat 100-usb.rules
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{model}=="USB SD Reader", SYMLINK+="test_%n", OPTIONS+="all_partitions"
and the test:
XSign rules.d # udevadm test /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1
calling: test
version 198
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
=== trie on-disk ===
tool version: 198
file size: 5544030 bytes
header size 80 bytes
strings 1242254 bytes
nodes 4301696 bytes
load module index
Skipping overridden file: /usr/lib/udev/rules.d/80-net-name-slot.rules.
read rules file: /etc/udev/rules.d/01-razer-udev.rules
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/10-vboxdrv.rules
read rules file: /etc/udev/rules.d/100-usb.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-rfkill.rules
read rules file: /usr/lib/udev/rules.d/60-vboxguest.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
IMPORT found builtin 'usb_id --export %p', replacing /usr/lib/udev/rules.d/69-cd-sensors.rules:85
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/70-infrared.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /etc/udev/rules.d/80-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /etc/udev/rules.d/91-fingerprint-gui-upek.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-keyboard-force-release.rules
read rules file: /usr/lib/udev/rules.d/95-keymap.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
read rules file: /usr/lib/udev/rules.d/99-laptop-mode.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 49152 bytes tokens (4096 * 12 bytes), 20074 bytes strings
3343 strings (40625 bytes), 2291 de-duplicated (21604 bytes), 1053 trie nodes used
GROUP 6 /usr/lib/udev/rules.d/50-udev-default.rules:40
LINK 'disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' /usr/lib/udev/rules.d/60-persistent-storage.rules:43
LINK 'disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' /usr/lib/udev/rules.d/60-persistent-storage.rules:57
IMPORT builtin 'blkid' /usr/lib/udev/rules.d/60-persistent-storage.rules:70
probe /dev/sdb1 raid offset=0
LINK 'disk/by-uuid/1DFC8855338F968C' /usr/lib/udev/rules.d/60-persistent-storage.rules:76
LINK 'disk/by-label/Hacksign\x27s\x20Documents\x20Disk' /usr/lib/udev/rules.d/60-persistent-storage.rules:77
IMPORT 'udisks-part-id /dev/sdb1' /usr/lib/udev/rules.d/80-udisks.rules:84
starting 'udisks-part-id /dev/sdb1'
'udisks-part-id /dev/sdb1' [2444] exit with return code 0
handling device node '/dev/sdb1', devnum=b8:17, mode=0660, uid=0, gid=6
preserve permissions /dev/sdb1, 060660, uid=0, gid=6
preserve already existing symlink '/dev/block/8:17' to '../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fusb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1'
creating link '/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-label\x2fHacksign\x5cx27s\x5cx20Documents\x5cx20Disk'
creating link '/dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fpci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1'
creating link '/dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-uuid\x2f1DFC8855338F968C'
creating link '/dev/disk/by-uuid/1DFC8855338F968C' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-uuid/1DFC8855338F968C' to '../../sdb1'
ACTION=add
DEVLINKS=/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1 /dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk /dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/1DFC8855338F968C
DEVNAME=/dev/sdb1
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1
DEVTYPE=partition
ID_BUS=usb
ID_DRIVE_FLASH_SD=1
ID_FS_LABEL=Hacksign_s_Documents_Disk
ID_FS_LABEL_ENC=Hacksign\x27s\x20Documents\x20Disk
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_FS_UUID=1DFC8855338F968C
ID_FS_UUID_ENC=1DFC8855338F968C
ID_INSTANCE=0:0
ID_MODEL=USB_SD_Reader
ID_MODEL_ENC=USB\x20\x20SD\x20Reader\x20\x20
ID_MODEL_ID=6200
ID_PART_ENTRY_DISK=8:16
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_SIZE=15685569
ID_PART_ENTRY_TYPE=0x87
ID_PART_TABLE_TYPE=dos
ID_PATH=pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_1_1_0-scsi-0_0_0_0
ID_REVISION=1.00
ID_SERIAL=Generic_USB_SD_Reader_12345678901234567890-0:0
ID_SERIAL_SHORT=12345678901234567890
ID_TYPE=disk
ID_USB_DRIVER=usb-storage
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=Generic
ID_VENDOR_ENC=Generic\x20
ID_VENDOR_ID=090c
MAJOR=8
MINOR=17
SUBSYSTEM=block
TAGS=:systemd:
UDISKS_PARTITION=1
UDISKS_PARTITION_ALIGNMENT_OFFSET=0
UDISKS_PARTITION_NUMBER=1
UDISKS_PARTITION_OFFSET=32256
UDISKS_PARTITION_SCHEME=mbr
UDISKS_PARTITION_SIZE=8031011328
UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb
UDISKS_PARTITION_TYPE=0x87
UDISKS_PRESENTATION_NOPOLICY=0
USEC_INITIALIZED=7735553
It seems that 100-usb.rules doesn't be executed~
Am I anywhere wrong ?
Last edited by Hacksign (2013-04-09 02:15:13)

Pasted another example of my usb sd card reader.
there is no test_X symbol link in /dev/ directory after i un-pluged sd card reader and re-pluged it in on my computer
oh, I use systemd of course:
XSign rules.d # cat /boot/grub/menu.lst
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/root resume=/dev/sda7 ro vga=0x361 init=/usr/lib/systemd/systemd quiet
initrd /boot/kernel26.img
Hacksign wrote:
brebs wrote:You're mixing the hierarchy levels (i.e. subsystems) - can't do that. See working example.
no, I dont think I mixed te hierarchy level.
SUBSYSTEM=="input" matched '/devices/platform/i8042/serio1/serio2/input/input24/mouse2'
and
SUBSYSTEMS=="usb", ATTR{idVendor}=="1532",
matched its parent
and I'm so sorry that I pasted a wrong device tree...
sorry

UDEV rules for Xilinx FPGA devices

I recently purchased a Digilent Nexys3 FPGA board with a Xilinx Spartan 5 FPGA on it. I finally got around to finding some time to using it, and setting up the development environment under Arch linux.
After spending ages reading around about various problems and workarounds, I finally managed to get Xilinx ISE Webpack installed and working, as well as Digilent Adept software for downloading the designs to the development board. One issue still remains though. I am unable to download the designs to the FPGA as a normal user, but only as root.
I'm pretty sure this is a udev rules problem. Digilent supplies a rules file (attached below) which is supposed to grant permissions to all users to access the FPGA devices over USB. I placed this rule file under /etc/udev/rules.d, but I am still unable to access the devices as normal user due to the following error:
$ djtgcfg enum
libusb couldn't open USB device /dev/bus/usb/001/003: Permission Denied.
libusb requires write access to USB device nodes.
$
I believe that udev rules syntax changed since the last time I had a look at it, so maybe the supplied rules file still uses the old syntax? Any suggestions to fixing this rules file (attached below)?
# 52-digilent-usb.rules -- UDEV rules for Digilent USB Devices #
# Author: MTA #
# Copyright 2010 Digilent Inc. #
# File Description: #
# This file contains the rules used by UDEV when creating entries for #
# Digilent USB devices. In order for Digilent's shared libraries and #
# applications to access these devices without root privalages it is #
# necessary for UDEV to create entries for which all users have read #
# and write permission. #
# Usage: #
# Copy this file to "/etc/udev/rules.d/" and execute #
# "/sbin/udevcontrol reload_rules" as root. This only needs to be done #
# immediately after installation. Each time you reboot your system the #
# rules are automatically loaded by UDEV. #
# Revision History: #
# 04/15/2010(MTA): created #
# 02/28/2011(MTA): modified to support FTDI based devices #
# Create "/dev" entries for Digilent device's with read and write
# permission granted to all users.
SYSFS{idVendor}=="1443", MODE="666"
ACTION=="add", SYSFS{idVendor}=="0403", SYSFS{manufacturer}=="Digilent", MODE="666", RUN+="/usr/local/sbin/dftdrvdtch %s{busnum} %s{devnum}"
# The following rules (if present) cause UDEV to ignore all UEVENTS for
# which the subsystem is "usb_endpoint" and the action is "add" or
# "remove". These rules are necessary to work around what appears to be a
# bug in the Kernel used by Red Hat Enterprise Linux 5/CentOS 5. The Kernel
# sends UEVENTS to remove and then add entries for the endpoints of a USB
# device in "/dev" each time a process releases an interface. This occurs
# each time a data transaction occurs. When an FPGA is configured or flash
# device is written a large number of transactions take place. If the
# following lines are commented out then UDEV will be overloaded for a long
# period of time while it tries to process the massive number of UEVENTS it
# receives from the kernel. Please note that this work around only applies
# to systems running RHEL5 or CentOS 5 and as a result the rules will only
# be present on those systems.
Thanks!
-Igor
Last edited by UQ-igor (2011-12-24 03:56:10)

Try this
Use ATTR or ATTRS.
-SYSFS{idVendor}=="1443", MODE="666"
-ACTION=="add", SYSFS{idVendor}=="0403", SYSFS{manufacturer}=="Digilent", MODE="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"
+ATTRS{idVendor}=="1443", MODE="666"
+ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{manufacturer}=="Digilent", MODE="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"
+ATTR{idVendor}=="1443", MODE="666"
+ACTION=="add", ATTR{idVendor}=="0403", ATTR{manufacturer}=="Digilent", MODE="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"

Re-create audio devices

Sometimes sound stops working on my desktop, and I'm fairly certain that it's usually, if not always, correlated with usage of Flash. Regardless of the source of the problem, what would the easiest catch-all solution be to restore audio? Rebooting is an annoying last resort.
I would assume the simplest thing would be to destroy and re-create the existing sound devices (which would be simple to do in a script). What steps are required to do so? Is it as simple as reloading the appropriate modules?

test1000 wrote:
test1000 wrote:
I think it was lsof(fuser probably works aswell) /dev/audio/* that used to work fine to identify processes hogging the audio device(then you could just kill those), but with the .29 kernel/new alsa drivers, i don't know, it doesn't seem to contain the same devices so i don't know.
Either way, the "audio disappears" problem stopped occuring to me a couple of months ago with some update, might have been a flashplugin update.
B-Con wrote:
MarCustomized wrote:Yes, reloading the modules is the simplest and probably the only solution outside of rebooting. I've been meaning to write a script to do this, but I'm super lazy. If you write one, please share. tongue
Thanks for the confirmation.
No dissenting opinion?
You didn't say anything about re-creating sound devices. I took that as an alternative solution to the bigger problem, not an objection to the specific solution.

After partition using fdisk, i can not see the new device file (/dev/sdd1)

I used fdisk -l to partition /dev/sdd, use the entire disk as partition 1. it looks successful:
# fdisk -l /dev/sdd
Disk /dev/sdd: 10.7 GB, 10737418240 bytes
64 heads, 32 sectors/track, 10240 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x35e3e2c4
Device Boot Start End Blocks Id System
/dev/sdd1 1 10240 10485744 83 Linux
the problem: i don't see the device file /dev/sdd1. tried to delete it and partition again, the same.
also tried
- mknod b 8 70 /dev/sdd1, to manually create it, but when i use oracleasm createdisk DISK2 /dev/sdd1, the command won't recognize manually crated /dev/sdd1.
- reboot the server,
- "partprobe" command, no luck.
in addition, cat /proc/partitions seems including /dev/sdd1:
cat /proc/partitions
major minor #blocks name
8 16 292935982 sdb
8 0 143338560 sda
8 1 512000 sda1
8 2 142825472 sda2
252 0 25608192 dm-0
252 1 25608192 dm-1
252 2 62423040 dm-2
252 3 35012608 dm-3
252 4 20480000 dm-4
252 5 10240000 dm-5
252 6 4096000 dm-6
8 32 10485760 sdc
8 33 10484736 sdc1
8 48 20971520 sdd
8 49 20971504 sdd1
8 64 10485760 sde
8 65 10485744 sde1
any advice?
Thanks as alwasy!
Edited by: 943714 on Apr 25, 2013 10:55 AM

After you create a new partition, always verify it:
# fdisk -l /path/to/diskOnce that confirms the new partition, you must tell the kernel to re-read the partition table. Several ways to do this, depending on what your storage connection is. This often works:
# partprobe /path/to/mydiskThen check if the kernel sees the partition:
# grep /proc/partitions mydiskIf it does, you are done.

Back-up / Retrieve Files from an external hard drive that doesn't appear in Devices

Someone please help!
I am going to write the "history" from my disk utility repair here so that other's who copy and paste into search may find it:
(PLEASE SCROLL 13 ROWS DOWN)
Verify and Repair volume “Your Hard Drive Name”
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Keys out of order
Rebuilding catalog B-tree.
The volume could not be repaired.
Volume repair complete.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
Ok. I would really love to reformat this disk, but I have stuff on here from film school that I CAN NOT lose
Question:
How would I go about backing-up the disk if the image doesn't appear under devices? I went to the "Restore" tab/button, but I can not choose the hard drive in the first field. I could have sworn my hard drive was formatted for Mac, but I may have formatted it back to FAT32. I know the disk still functions because when it is powered on, it cycles with/without being connected to my MacPro, but after that, it will only cycle if connected (confirming connection). It does run again when I connect the firewire cable. Here is my equipment:
8-Core MacPro 16GB-Mem RAID
MacOSX 10.6.8 | 2 X 1TB Internal HDD
Aug-2008 15" MacBookPro
(That I used the Maxtor-External with mostly)
DEVICE IN QUESTION
500GB Maxtor One-Touch Plus
FireWire 400 6-pin Connection Bus (2 Ports)
Purchased in Early 2008 from Staples
I can fit the back-up on my 2nd HDD in my MacPro or in my other External:
2 TB G-Technology G-RAID External
1 x eSATA | 2 x FireWire 800 9-pin | 1 x USB 2.0
Self Powered DC-IN
I have had a nightmare searching for answers, so any options you might have would be tremendously helpful. I can't lose the data because I have everything I did during film school on there. That stuff is basically what you pay for when you go to film school, you pay to show what you can do and what equipment you have used. SAVE ME FELLOW APPLE PEOPLE!!!! We COMMAND, as well as CONTROL!
-RaphSai

Get Disk Warrior that will repair the problems without requiring that you reformat the drive - $99.00 on a bootable CD. Will not work on a FAT formatted drive.
You will need to use Drag and Drop to save your files by copying them from the bad drive to a good one.
To reprep the drive:
Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

Could not open the device file /dev/nvidia0

and yet:
[root@mythfe01 dev]# ls -alh nvid*
crw-rw-rw- 1 root root 195, 0 Mar 26 16:06 nvidia0
crw-rw-rw- 1 root root 195, 255 Mar 26 16:06 nvidiactl
and:
[root@mythfe01 dev]# lsmod | grep nv
nvidia 4083280 0
agpgart 28872 1 nvidia
but:
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(EE) NVIDIA(0): *** Aborting ***
I am using a homemade kernel, but i can't think of a reason why that would prevent things from working properly considering the module loaded ok.
Any thoughts?

Moo-Crumpus wrote:Do you use udev? Have a look if there is a ruleset for nvidia, I remember there was one. Afaik, nvidia should be owned by the video group - well, once it was, I am not up to date and have no arch machine with nvidia right now.
Could anyone specify how to do that? I have the exact same problem, although I use the default kernel that came with Arch.
NVIDIA: could not open the device file /dev/nvidia0 (Permission denied).
NVIDIA: Direct rendering failed; attempting indirect rendering.
[kristjans@myhost ~]$ cat /proc/driver/nvidia/cards/0
Model: GeForce 6200 TurboCache(TM)
IRQ: 22
Video BIOS: 05.44.02.52.00
Card Type: PCI-E
DMA Size: 39 bits
DMA Mask: 0x7fffffffff
[kristjans@myhost dev]$ ls -alh nvid*
crw-rw---- 1 root 27 195, 0 2007-10-06 19:10 nvidia0
crw-rw-rw- 1 root 27 195, 255 2007-10-06 19:10 nvidiactl
[kristjans@myhost dev]$ lsmod | grep nv
nvidia 6829684 40
i2c_core 20352 2 nvidia,i2c_piix4
agpgart 27224 2 nvidia,ati_agp
Last edited by KSiimson (2007-10-11 04:23:18)

QSynth doesn't create jack port.

I have a problem with QSynth - it doesn't create jack port, so i can't connect it to output. When i run fluidsynth from console it works properly - it creates output, I connect it to "system" port using QJackCtl and i can hear midi sound, but i really ned QSynth. Please help me.
Messages from QSynth:
15:11:57.027 Qsynth1: Creating synthesizer engine...
15:11:57.058 Qsynth1: Loading soundfont: "/usr/share/soundfonts/fluidr3/FluidR3GM.SF2" (bank offset 0)...
15:11:57.281 Qsynth1: Creating audio driver (jack)...
15:11:57.294 Qsynth1: Creating MIDI router (alsa_seq)...
15:11:57.295 Qsynth1: Creating MIDI driver (alsa_seq)...
15:11:57.296 Qsynth1: Creating MIDI player...
15:11:57.298 Qsynth1: Synthesizer engine started.
15:11:57.298 Qsynth1: fluid_synth_set_gain(0.97)
15:11:57.299 Qsynth1: fluid_synth_set_reverb(0.2,0.5,10,0.1)
15:11:57.299 Qsynth1: fluid_synth_set_chorus(3,1,0.3,8,0)
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
fluidsynth: prog 0 0 0
fluidsynth: prog 1 0 0
//............. some lines like above and bellow
fluidsynth: prog 14 0 14
fluidsynth: prog 15 0 15
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server
Last edited by dawidmt (2011-08-26 13:20:17)

Sorry about the necro, but did you ever figure this out? I'm running into the same issue. I think *something* is being written because when I do "efibootmgr -c blahblah", and then I do an efibootmgr -v afterward, I can see the device path that shows up in the verbose options. Then, when I reboot, I don't see the new boot option in the menu, and when I check again via a livecd (which boots via UEFI, by the way), efibootmgr -v shows "Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)" in the extra info next to the boot option I had previously created. That vendor and GUID seem to show up when there's no path, as I've googled it and have seen similar readouts that imply such based on the context of where I saw them.
Anyway, help.
Thanks.
-TJ

How do you create multile devices on on Windows Vista Computer?

How does one create multiple devices for the many ipod/ipad products in one household. Each serial number should have it's own device name!

Using the minor device number is what I would do if I was writing an ethernet driver for example. But all I want to do is if the user accesses device x it then calls routines via the xinfo streamtab - if device y is accessed then calls use the yinfo streamtab. It is usually a matter of registering the info structures with the system and then associating them with a device. Unfortunately Solaris seems to have :-
modlinkage -> modldrv -> x_ops -> cb_x_ops -> xinfo
which is all very well for device x
but how do you fit/ dev/y
into the picture.

Can't create aggregate device in SL

Just installed SL and i'm having problems with Audio MIDI Setup, i need to create a new aggregate device to use my mixer etc but when i click the + symbol, the new device will flash in the list and immediately disappear. Is this a bug or am i doing something wrong? This worked fine for me with the same setup in Leopard.

SOLVED!!!!! I spend about 5 hours one the phone with Cameron at AppleCare as well as some time on my own, and we FINALLY figured it out!
The important thing is that you can ONLY add aggregate devices from an admin account, but that may not be the only problem. It certainly wasn't in my case. So, here are the steps to follow:
1. Try adding/removing aggregate devices from an ADMIN account. If this works, you're good. If it doesn't, or if you're already on an admin account, try creating a new admin account.
2. If even a new admin account doesn't work, REINSTALL SNOW LEOPARD. If you just use the default install, it does an Archive and Install. It only takes about an hour, and you won't even notice OS X has been reinstalled except for the fact you'll have to reinstall the 10.6.1 update and any other misc. updates. Besides, it'll run a lot faster. It's so easy in fact that I'm going to start recommending you reinstall like this every couple months or so just to keep your Mac running in top condition.
3. NOW try creating aggregate devices from one or more admin account. It should work now. If it doesn't, then you have a different problem and I can't really help you much.
Hope this helps someone!

Error while creating a device.

Hi all,
I tried to create a device and when i click on save it is giving an ABAP dump as below.
The following error text was processed in the system M01 : CREATE DATA: The specified type is not a valid data type.
The error occurred on the application server wicomp05_M01_04 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: GET_USERS_FROM_CDS of program CL_SMMW_USER==================CP
Method: FETCH_USER_LIST of program /1BCWDY/005OX851WLQW549Y03TQ==CP
Method: IF_USER_SEARCH~FETCH_USER_LIST of program /1BCWDY/005OX851WLQW549Y03TQ==CP
Method: ONACTIONON_SEARCH of program /1BCWDY/005OX851WLQW549Y03TQ==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/005OX851WLQW549Y03TQ==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================CP
Method: DO_HANDLE_ACTION_EVENT of program CL_WDR_WINDOW_PHASE_MODEL=====CP
Method: PROCESS_REQUEST of program CL_WDR_WINDOW_PHASE_MODEL=====CP
Method: PROCESS_REQUEST of program CL_WDR_WINDOW=================CP
Is it any bug in the system?
I am currently on SP07 stack.
Please help me in resloving this.
Thanks and regards,
Rajesh

Hi Rohit,
We didnt applied any sap note after upgrading to SP07.if there any sap note for this error pls let me know.I read in some thread that we have to re generate the Data Object userdetails in the basis SC.
When i regenerated the satus becam red.
Please find the ST22 dump details.
root_profile_table = ls_cds_list-tablename . |
104
ENDIF.
105
106
ENDLOOP.
107
108
LOOP AT lt_mbo_segm_infm INTO ls_mbo_segm_infm .
109
110
CASE ls_mbo_segm_infm-sfld_orgname .
111
112
WHEN 'LOGIN_NAME' .
113
tbl_fld_login_nm = ls_mbo_segm_infm-sfld_name .
114
WHEN 'FIRST_NAME' .
115
tbl_fld_first_nm = ls_mbo_segm_infm-sfld_name .
116
WHEN 'LAST_NAME' .
117
tbl_fld_last_nm = ls_mbo_segm_infm-sfld_name .
118
WHEN 'LONG_NAME' .
119
tbl_fld_full_nm = ls_mbo_segm_infm-sfld_name .
120
121
ENDCASE.
122
ENDLOOP.
123
124
125
DATA : var1 TYPE bapiusname .
126
DATA: lt_tmp_ref TYPE REF TO data.
127
DATA: ls_tmp_ref TYPE REF TO data.
128
129
FIELD-SYMBOLS : <lt_tmp> TYPE ANY TABLE.
130
FIELD-SYMBOLS : <ls_tmp> TYPE any,
131
<area> TYPE any.
132
>>>>>
CREATE DATA lt_tmp_ref TYPE TABLE OF (root_profile_table).
134
ASSIGN lt_tmp_ref->* TO <lt_tmp>.
135
136
CREATE DATA ls_tmp_ref TYPE (root_profile_table).
137
ASSIGN ls_tmp_ref->* TO <ls_tmp>.
138
139
140
***Search based on the Importing Parameter - I_USER_NAME ******
141
lv_login_name = i_user_name .
142
lv_first_name = i_first_name .
143
lv_last_name = i_last_name .
144
145
wildcard_flag = ''.
146
REPLACE ALL OCCURRENCES OF '*' IN lv_login_name WITH '%'.
147
IF sy-subrc EQ 0.
148
wildcard_flag = 'X'.
149
ENDIF.
150
REPLACE ALL OCCURRENCES OF '*' IN lv_first_name WITH '%'.
151
IF sy-subrc EQ 0.
| 152| wildcard_flag = 'X'.
Thanks and regards,
rajesh

Udev doesn't create sd* devices in /dev

Similar Messages

Maybe you are looking for