[solved] udev/command/module/service

The story started here: https://bbs.archlinux.org/viewtopic.php?id=147745 The aim is to use LIRC with lirc_serial module. To get it these operations must take place in a given order:
- udev must name a serial port
- serial port must be freed from (built in) kernel serial driver with command 'setserial /dev/ttyS0 uart none'
- lirc_serial driver must be loaded
- lircd service must be started
I have tried to add 'setserial ...' command into udev rule (RUN+=), add lirc_serial module to /etc/modules-load and enable lircd service - all these under systemd - but needed sequence of operation takes place randomly only. Currently I use custom script which I start manually after booting (and, of course, it does work always):
~ $ cat `which mylirc.sh`
#!/bin/bash
/usr/bin/systemctl stop lircd.service
/usr/bin/rmmod lirc_serial
/usr/bin/setserial /dev/ttyS0 uart none
/sbin/modprobe lirc_serial
/usr/bin/systemctl start lircd.service
Can anybody suggest legal systemd/udev way to get needed sequence of operations?
Last edited by student975 (2012-09-02 14:29:47)

Have got solutions here: [email protected] - just use ExecStartPre:
~ $ cat /etc/systemd/system/lircd.service
[Unit]
Description=LIRC Daemon
After=network.target
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/lircd.conf
PIDFile=/run/lirc/lircd.pid
ExecStartPre=/usr/bin/setserial /dev/ttyS0 uart none
ExecStartPre=/sbin/modprobe lirc_serial
ExecStartPre=/bin/mkdir -p /run/lirc
ExecStartPre=/bin/rm -f /dev/lircd
ExecStartPre=/bin/rm -f /run/lirc/lircd
ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd
ExecStart=/usr/sbin/lircd -d $LIRC_DEVICE -P /run/lirc/lircd.pid -H $LIRC_DRIVER $LIRC_CONFIGFILE
ExecStopPost=/bin/rm -f /dev/lircd
ExecStopPost=/bin/rm -fR /run/lirc
[Install]
WantedBy=multi-user.target

Similar Messages

  • [Solved] Fails to load systemd-modules.service

    Kernel: 3.12.9-2-ARCH
    $ systemctl status systemd-modules.service
    systemd-modules.service
       Loaded: not-found (Reason: No such file or directory)
       Active: inactive (dead)
    Any ideas?
    Thanks!
    Last edited by hellolj (2014-02-21 11:17:50)

    WonderWoofy wrote:
    hellolj wrote:$ journalctl -b _PID=127
    Failed to parse relative boot ID number '_PID=127'
    Try this instead:
    $ journalctl -b 0 _PID=127
    The '-b' flag can optionally be given a negative number to indicate which boot you would like to be shown (for example, 'journalctl -b -1' will show you the previous boot).  So this way you are passing it that optional argument so that it knows for sure that the '_PID=127' is a new switch/argument*.
    * Not sure if it would be considered a switch or an argument since it acts like a switch but looks like an argument.
    Thanks for the explaination!!! ; Here is the output by executing the command:
    $ journalctl -b 0 _PID=127
    -- Logs begin at Tue 2014-02-11 07:50:17 CST, end at Fri 2014-02-21 16:24:44 CST. --
    Feb 21 22:06:02 arch-hp systemd-modules-load[127]: Inserted module 'vboxdrv'
    Feb 21 22:06:02 arch-hp systemd-modules-load[127]: Failed to find module 'vboxsf'
    Feb 21 22:06:02 arch-hp systemd-modules-load[127]: Failed to find module 'vboxvideo'
    Also, I reinstalled the virtualbox and host module packages, rebooted but didn't get it fixed
    $ pacman -Qs virtualbox
    local/virtualbox 4.3.6-3
    Powerful x86 virtualization for enterprise as well as home use
    local/virtualbox-guest-iso 4.3.6-1
    The official VirtualBox Guest Additions ISO image
    local/virtualbox-host-modules 4.3.6-4
    Host kernel modules for VirtualBox
    Last edited by hellolj (2014-02-21 06:12:41)

  • [SOLVED]mkinitcpio command not found!??

    Hello all,
    I receive the following when trying to rebuild the stock kernel:
    [taylor-unix@Legion Desktop]$ sudo mkinitcpio -p kernel26
    sudo: mkinitcpio: command not found
    [taylor-unix@Legion Desktop]$
    The same error occurs even after the re-installation of 'mkinitcpio'.
    I've had the same problem with 'hwdetect', regardless of whether I've reinstalled it.
    I seem to have commands that do not work on this system, like 'shutdown' for example.. 'shutdown: command not found'. Perhaps I've missed installing a crucial package?
    I need help..
    My sincerest thanks in advance.
    Last edited by edward.taylor89 (2010-11-10 17:39:46)

    Here as follows:
    mkinitcpio /etc/
    mkinitcpio /etc/mkinitcpio.conf
    mkinitcpio /etc/mkinitcpio.d/
    mkinitcpio /etc/mkinitcpio.d/example.preset
    mkinitcpio /lib/
    mkinitcpio /lib/initcpio/
    mkinitcpio /lib/initcpio/functions
    mkinitcpio /lib/initcpio/hooks/
    mkinitcpio /lib/initcpio/hooks/btrfs
    mkinitcpio /lib/initcpio/hooks/consolefont
    mkinitcpio /lib/initcpio/hooks/dmesg
    mkinitcpio /lib/initcpio/hooks/keymap
    mkinitcpio /lib/initcpio/hooks/memdisk
    mkinitcpio /lib/initcpio/hooks/net
    mkinitcpio /lib/initcpio/hooks/resume
    mkinitcpio /lib/initcpio/hooks/sleep
    mkinitcpio /lib/initcpio/hooks/udev
    mkinitcpio /lib/initcpio/init
    mkinitcpio /lib/initcpio/init_functions
    mkinitcpio /lib/initcpio/install/
    mkinitcpio /lib/initcpio/install/autodetect
    mkinitcpio /lib/initcpio/install/base
    mkinitcpio /lib/initcpio/install/btrfs
    mkinitcpio /lib/initcpio/install/consolefont
    mkinitcpio /lib/initcpio/install/dmesg
    mkinitcpio /lib/initcpio/install/dsdt
    mkinitcpio /lib/initcpio/install/filesystems
    mkinitcpio /lib/initcpio/install/fw
    mkinitcpio /lib/initcpio/install/ide
    mkinitcpio /lib/initcpio/install/keymap
    mkinitcpio /lib/initcpio/install/memdisk
    mkinitcpio /lib/initcpio/install/net
    mkinitcpio /lib/initcpio/install/pata
    mkinitcpio /lib/initcpio/install/pcmcia
    mkinitcpio /lib/initcpio/install/resume
    mkinitcpio /lib/initcpio/install/sata
    mkinitcpio /lib/initcpio/install/scsi
    mkinitcpio /lib/initcpio/install/sleep
    mkinitcpio /lib/initcpio/install/udev
    mkinitcpio /lib/initcpio/install/usb
    mkinitcpio /lib/initcpio/install/usbinput
    mkinitcpio /lib/initcpio/udev/
    mkinitcpio /lib/initcpio/udev/01-memdisk.rules
    mkinitcpio /lib/initcpio/udev/load-modules.sh
    mkinitcpio /sbin/
    mkinitcpio /sbin/mkinitcpio
    mkinitcpio /usr/
    mkinitcpio /usr/share/
    mkinitcpio /usr/share/man/
    mkinitcpio /usr/share/man/man5/
    mkinitcpio /usr/share/man/man5/mkinitcpio.5.gz

  • [solved] Large number of services enabled during first boot

    I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
    To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
    Any ideas as to what might be causing this?
    Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
    Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
    Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
    Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
    Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
    Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
    Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
    getty.target.wants:
    * [email protected]
    multi-user.target.wants:
    * [email protected]
    * iptables.service
    * remote-fs.target
    * sshd.service
    sysinit.target.wants:
    (none)
    Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
    default.target.wants:
    * systemd-readahead-collect.service
    * systemd-readahead-replay.service
    multi-user.target.wants:
    * dhcpcd.service * krb5-kpropd.service
    * fstrim.service * nscd.service
    * ftpd.service * rsyncd.service
    * gpm.service * systemd-journal-upload.service
    * ip6tables.service * systemd-networkd.service
    * krb5-kadmind.service * systemd-resolved.service
    * krb5-kdc.service
    sockets.target.wants:
    * krb5-kpropd.socket * systemd-journal-remote.socket
    * rlogin.socket * talk.socket
    * rsh.socket * telnet.socket
    * rsyncd.socket * uuidd.socket
    * sshd.socket
    sysinit.target.wants:
    * dm-event.service
    * systemd-timesyncd.service
    system-update.target.wants:
    * systemd-readahead-drop.service
    Explicitly installed packages:
    dhcpcd iputils procps-ng systemd-sysvcompat
    diffutils linux-grsec psmisc tar
    dnsutils logrotate reflector vim-systemd
    file mlocate rsync wget
    gradm mtr s-nail which
    grub openssh screen whois
    inetutils pacman
    Last edited by tazmanian (2014-09-10 23:11:42)

    +1.
    Here is the ports these services are listening:
    $ ss -tpl
    State      Recv-Q Send-Q                                                                                                       Local Address:Port                                                                                                           Peer Address:Port   
    LISTEN     0      128                                                                                                                      *:llmnr                                                                                                                     *:*       
    LISTEN     0      128                                                                                                                      *:ssh                                                                                                                       *:*       
    LISTEN     0      128                                                                                                                     :::llmnr                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::19532                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::tell                                                                                                                     :::*       
    LISTEN     0      128                                                                                                                     :::ssh                                                                                                                      :::*       
    LISTEN     0      128                                                                                                                     :::telnet                                                                                                                   :::*       
    LISTEN     0      128                                                                                                                     :::login                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::shell                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::rsync                                                                                                                    :::*       
    LISTEN     0      128                                                                                                                     :::git                                                                                                                      :::*

  • XML Publisher with Service Module - Service Request Reports -- URGENT

    Hi all ... any pointers/help/guidance with the problem listed below would be much appreciated.
    I'm working in the context of the Oracle Service Module & Service Request Reports.
    I'm required to configure the XML Publisher Responsibility seeded functionality with the service module reports.
    Listed below are the two reporting requirements that I'm considering , corresponding to the following seeded XMLP Responsibility seeded components:
    (I'm quoting an extract from the Oracle TeleService Implementation & User Guide here).
    Detailed Report
    Data Definition: Service Request Detail Definition (CS_SR_DETAIL_DEF)
    Corresponding Template: Service Request Detail Report Template (CS_SR_DETAIL_TMP.en)
    Template Description: Includes all of the available service request attributes including charges, the two descriptive flexfields, and extensible attributes.
    Summary Report
    Data Definition: Service Request Summary Definition (CS_SR_SUMMARY_DEF)
    Corresponding Template: Service Request Summary Report Template (CS_SR_SUMMARY_TMP_en)
    Template Description: Includes a subset of the detailed report attributes including the same charges information as the detailed report.
    When I log into the EBS >> XML Publisher Administrator Responsibility >> Service Application ... I find these seeded XMLP components, together with the preview data, downloadable templates & sample output.
    The question is:
    Where (responsibility/application/navigation/etc.) do I find the seeded EBS Service Reports to provide the expected XML input to the seeded XMLP Service Request Data Definitions & Templates????
    Notes ...
    I have found the following two reports, under the Service Application in EBS, set their output type to XML and viewed the output of the submitted request:
    - Service Request Detail Report
    - Service Request Summary Report
    ... but each of these two reports produce XML output of a different data model/structure to that expected by each of the corresponding seeded XMLP data-definitions/templates.
    Additionally, I cannot find any corresponding concurrent program definitions on the system with the same SHORT-NAME/CODE as the seeded XMLP data definitions themselves i.e. CS_SR_DETAIL_DEF and CS_SR_SUMMARY_DEF.
    Are the necessary reports not actually seeded within EBS? Do the seeded XMLP data definitions & templates require development of new Concurrent Programs from scratch to access the database tables and provide the necessary data/input, or am I missing something here??

    I am sure you found a solution to your problem. If not, to give a pointer to this issue, I guess these reports are gererated right from the service request screen and this definition is used there.This report can be generated from several places based on where you are within SR scree.
    Thanks
    Nagamohan

  • Creating Complex Datatypes in Application Module Service Interface

    HI All,
    I need to create the complex datatype as response in Application module service interface(Custom method).
    Is there any way to create it.
    I am able to create when i have simple datatype as response, Whereas the complex type is not able to create.
    Please give me some suggestion.
    Thanks
    Prabhat

    Hi
    I followed the below discussion and got the solution
    Create Web Services and return a complex type with ADF
    Thanks
    Prabhat

  • [SOLVED] Problem with modules and udev

    Hi everybody,
    I've been configuring Arch on my new laptop the last few days and today as I was going to perform the first backup, I noticed that my external HDD does not show up in /dev/ when I plug it in. I figured it could be a problem with udev and the fact that in my /etc/rc.conf I use MOD_AUTOLOAD="no" with an explicit list of MODULES generated with hwdetect (as suggested in the wiki).
    To "solve" this I just changed MOD_AUTOLOAD to "yes" and after a reboot everything worked fine.
    My questions are:
    1) Is it possible to keep that feature (udev detects usb drives and creates the corresponding /dev/sdX) while having MOD_AUTOLOAD="no" ? What is/are the appropriate module(s) I have to put in my MODULES array ?
    2) What other such "basic" MODULES could be very useful that hwdetect does not tell about.
    Sorry for any English mistakes (I'm not a native speaker) and thank you in advance for your help,
    yms
    Last edited by yms (2010-01-06 12:48:20)

    1) Thank you, it works perfectly.
    2) Yes I know the question is weird. The thing is I have no precise idea at the moment and I just wanted to know if there are other very widely used features such as the one described in 1) that hwdetect ommits and that has to be loaded in MODULES.
    Anyway, thank you very much, I consider this matter [solved]

  • [SOLVED] A custom systemd service doesn't execute a specific command

    I have made a custom service which should set screen brightness.
    file: /etc/systemd/system/backlight100.service
    [Unit]
    Description=Set screen brightness
    [Service]
    Type=oneshot
    ExecStart=/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness
    ExecStart=/usr/bin/beep
    [Install]
    WantedBy=multi-user.target
    (beep is there so I can know for sure that the script runs)
    The problem is, when I run "# systemctl start backlight100.service" I can hear the beep but it doesn't change the brightness. When I run "/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness" in terminal it does change the brightness... but not when I start or restart the service.
    Here's the output of systemctl status backlight100.service after starting it
    backlight100.service - Set screen brightness
    Loaded: loaded (/etc/systemd/system/backlight100.service; enabled)
    Active: inactive (dead) since Fri 2013-04-05 20:17:32 AMT; 3min 19s ago
    Process: 27698 ExecStart=/usr/bin/beep (code=exited, status=0/SUCCESS)
    Process: 27696 ExecStart=/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness (code=exited, status=0/SUCCESS)
    Apr 05 20:17:32 work systemd[1]: Starting Set screen brightness...
    Apr 05 20:17:32 work echo[27696]: 100 > /sys/class/backlight/intel_back...ss
    Apr 05 20:17:32 work systemd[1]: Started Set screen brightness.
    What am I doing wrong here? Any help appreciated.
    Last edited by axper (2013-04-05 18:35:24)

    msthev wrote:$ man systemd.service
    ExecStart=
    Note that this setting does not directly support shell command
    lines. If shell command lines are to be used they need to be passed
    explicitly to a shell implementation of some kind. Example:
    ExecStart=/bin/sh -c 'dmesg | tac'
    Thanks, changing ExecStart line to
    ExecStart=/bin/bash -c '/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness'
    solved the issue. Though I can recall seeing ExecStart lines with direct shell commands.
    Raynman wrote:
    You should look at tmpfiles.d.
    https://wiki.archlinux.org/index.php/Sy … rary_files
    I'll do that, thanks!

  • [SOLVED] systemd: create a service file that loads a kernel module

    Hi, I have a daemon that I want to convert to a service unit of systemd.
    The daemon tests if a module is loaded, and if not, modprobes it.
    I do not want to load that module at boot up, only if the service is launched.
    Is there a "proper" way to add something like RequiredModule=xxx to a service unit?
    Thanks!
    Last edited by Wasser (2012-09-03 08:58:02)

    Maybe simply run modprobe with ExecStartPre. The command succeeds even if the module was already loaded.

  • [SOLVED]udev: execute command on usb unplug (em28xx_dvb WinTV_HVR-900)

    Hi all.
    I've a known bug with a dvbt usb device.
    The problem is that if i unplug and replug it, em28xx_dvb module hangs in dvb_init() and a reboot is needed to use the device again.
    A manual workaround exists, it is sufficient to rmmod em28xx_dvb before replug the device again, but if i forgot it, i'm f*****
    So here comes a question:
    Does udev reacts to the unplug event? and if yes, how can i trigger the action of removing that module?
    I'm a little noob with udev rules, so please be patient and thanks!
    Last edited by kokoko3k (2011-05-17 11:52:33)

    I got it working; if anyone cares, here's the udev rule:
    ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_MODEL}=="WinTV_HVR-900", RUN+="/sbin/rmmod em28xx_dvb"
    ENV{ID_MODEL}=="WinTV_HVR-900" is the key, my previous attempts to use ATTR{product}=="WinTV HVR-900" failed because it seems that udev doesn't trig any event on device removal (works on device plug),
    while it does using id_model.
    -EDIT-
    If anyone uses this device, here's other tricks i made to make it work (without ir):
    #> cat /etc/modprobe.d/tv.conf
    options em28xx disable_ir=1
    #> cat /etc/udev/rules.d/50-WinTv.rules
    ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_MODEL}=="WinTV_HVR-900", RUN+="/sbin/rmmod em28xx_dvb""
    Before hibernation:
    # rmmod em28xx_dvb em28xx dvb_core tuner tvp5150 v4l2_common videodev videobuf_vmalloc videobuf_core tveeprom zl10353 ir_lirc_codec lirc_dev ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_core tuner_xc2028
    On resume from hibernation:
    # hwdetect --load-modules
    ...man, it wasnt 'easy'
    Last edited by kokoko3k (2011-05-17 12:08:16)

  • [SOLVED] [systemd] systed-module-load.service inactive (dead)

    Hello archers,
    I use VirtualBox and I'm tired of loading modules manually so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot. Well, easier said than done because it doesn't seem to work.
    Here's my virtualbox.conf:
    # modules relevant to VirtualBox
    vboxdrv
    vboxnetadp
    vboxnetflt
    and here's my systemctl status systemd-modules-load.service:
    systemd-modules-load.service - Load Kernel Modules
    Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
    Active: inactive (dead)
    start condition failed at Sun 2013-10-20 09:27:06 CEST; 6s ago
    none of the trigger conditions were met
    Docs: man:systemd-modules-load.service(8)
    man:modules-load.d(5)
    Looking forward to hearing from you.
    Last edited by robin92 (2013-10-20 11:10:55)

    robin92 wrote:so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot.
    Why not read the Wiki and follow the instructions?
    https://wiki.archlinux.org/index.php/VirtualBox
    Last edited by loafer (2013-10-20 08:06:04)

  • [SOLVED] udev rules: cannot run command

    I want to run a scipt everytime I plug in my external harddrive. I read the documentation and create a file called /etc/udev/rules.d/extern_hd.rules:
    SUBSYSTEMS=="usb", SYSFS{serial}=="33504D315647585A", SYMLINK+="ExternHD", RUN+="/root/scripts/test.sh"
    The symlink "ExternHD" gets created. The permissions of test.sh are rwxr-xr-x root root, but it never gets executed. What am I doing wrong?
    Last edited by Kei (2007-09-18 11:30:35)

    Solution was easy... Udev doesn't want to start anything from within /root, so I put a hardlink to /usr/local/bin/ and now everything works fine.

  • [SOLVED] udev rule no longer working

    I have a udev rule set up to automatically mount an ext4 filesystem when I plug a certain thumb drive in.  It was working fine until yesterday (probably due to updates).  Here is the rule, in file /etc/udev/rules.d/99-gfk.rules:
    KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", SYMLINK+="gfshare"
    ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mkdir /media/gfshare"
    ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mount -t ext4 -o ro,nosuid,nodev,noexec,noatime /dev/gfshare /media/gfshare"
    The symlink and the mkdir command are both working fine, but the mount command is not being run for some reason.  If I manually run the mount command it works fine.  Some possibly helpful output:
    # pacman -Qo $(which udevadm)
    /usr/bin/udevadm is owned by systemd 212-1
    # dmesg |tail -16
    [26458.120628] usb 7-1.3: new high-speed USB device number 7 using ehci-pci
    [26458.223059] usb-storage 7-1.3:1.0: USB Mass Storage device detected
    [26458.223825] scsi10 : usb-storage 7-1.3:1.0
    [26459.311607] scsi 10:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4
    [26460.834081] sd 10:0:0:0: [sdd] 15240576 512-byte logical blocks: (7.80 GB/7.26 GiB)
    [26460.834931] sd 10:0:0:0: [sdd] Write Protect is off
    [26460.834935] sd 10:0:0:0: [sdd] Mode Sense: 23 00 00 00
    [26460.835617] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.835621] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.839455] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.839460] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.860579] sdd: sdd1 sdd2
    [26460.867111] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.867115] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.867118] sd 10:0:0:0: [sdd] Attached SCSI removable disk
    [26461.041982] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null)
    # udevadm test /sys/bus/usb/devices/7-1.3
    calling: test
    version 212
    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.
    load module index
    timestamp of '/etc/systemd/network' changed
    timestamp of '/usr/lib/systemd/network' changed
    Parsed configuration file /usr/lib/systemd/network/99-default.link
    Created link configuration context
    timestamp of '/etc/udev/rules.d' changed
    Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
    read rules file: /usr/lib/udev/rules.d/10-dm.rules
    read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    read rules file: /etc/udev/rules.d/12-android.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/40-usb-media-players.rules
    read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
    read rules file: /usr/lib/udev/rules.d/50-firmware.rules
    read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    read rules file: /usr/lib/udev/rules.d/51-android.rules
    read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
    read rules file: /usr/lib/udev/rules.d/60-drm.rules
    read rules file: /usr/lib/udev/rules.d/60-keyboard.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-vboxdrv.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
    read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    read rules file: /usr/lib/udev/rules.d/69-libmtp.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-setup-link.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
    read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
    read rules file: /usr/lib/udev/rules.d/90-alsa-restore.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-udev-late.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
    read rules file: /etc/udev/rules.d/99-gfk.rules
    read rules file: /usr/lib/udev/rules.d/99-systemd.rules
    read rules file: /usr/lib/udev/rules.d/kino.rules
    rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
    10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
    IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/50-udev-default.rules:9
    IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:9
    MODE 0664 /usr/lib/udev/rules.d/50-udev-default.rules:37
    GROUP 1002 /usr/lib/udev/rules.d/51-android.rules:387
    MODE 0660 /usr/lib/udev/rules.d/51-android.rules:387
    RUN '/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers' /usr/lib/udev/rules.d/60-vboxdrv.rules:6
    PROGRAM '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' /usr/lib/udev/rules.d/69-libmtp.rules:1204
    starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'
    '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'(out) '0'
    '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' [24644] exit with return code 0
    IMPORT builtin 'path_id' /usr/lib/udev/rules.d/71-seat.rules:43
    RUN 'uaccess' /usr/lib/udev/rules.d/73-seat-late.rules:15
    handling device node '/dev/bus/usb/007/007', devnum=c189:774, mode=0660, uid=0, gid=1002
    preserve permissions /dev/bus/usb/007/007, 020660, uid=0, gid=1002
    preserve already existing symlink '/dev/char/189:774' to '../bus/usb/007/007'
    ACTION=add
    BUSNUM=007
    DEVNAME=/dev/bus/usb/007/007
    DEVNUM=007
    DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3
    DEVTYPE=usb_device
    DRIVER=usb
    ID_BUS=usb
    ID_DRIVE_THUMB=1
    ID_FOR_SEAT=usb-pci-0000_00_1a_7-usb-0_1_3
    ID_MODEL=DataTraveler_2.0
    ID_MODEL_ENC=DataTraveler\x202.0
    ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    ID_MODEL_ID=6545
    ID_PATH=pci-0000:00:1a.7-usb-0:1.3
    ID_PATH_TAG=pci-0000_00_1a_7-usb-0_1_3
    ID_REVISION=0100
    ID_SERIAL=Kingston_DataTraveler_2.0_1C6F654E4041ED601910053F
    ID_SERIAL_SHORT=1C6F654E4041ED601910053F
    ID_USB_INTERFACES=:080650:
    ID_VENDOR=Kingston
    ID_VENDOR_ENC=Kingston
    ID_VENDOR_FROM_DATABASE=Toshiba Corp.
    ID_VENDOR_ID=0930
    MAJOR=189
    MINOR=774
    PRODUCT=930/6545/100
    SUBSYSTEM=usb
    TAGS=:seat:uaccess:
    TYPE=0/0/0
    USEC_INITIALIZED=26452326568
    adb_user=yes
    run: '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 774 00 vboxusers'
    run: 'uaccess'
    unload module index
    Unloaded link configuration context
    # udevadm test /sys/bus/usb/devices/7-1.3:1.0
    calling: test
    version 212
    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.
    load module index
    timestamp of '/etc/systemd/network' changed
    timestamp of '/usr/lib/systemd/network' changed
    Parsed configuration file /usr/lib/systemd/network/99-default.link
    Created link configuration context
    timestamp of '/etc/udev/rules.d' changed
    Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
    read rules file: /usr/lib/udev/rules.d/10-dm.rules
    read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    read rules file: /etc/udev/rules.d/12-android.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/40-usb-media-players.rules
    read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
    read rules file: /usr/lib/udev/rules.d/50-firmware.rules
    read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    read rules file: /usr/lib/udev/rules.d/51-android.rules
    read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
    read rules file: /usr/lib/udev/rules.d/60-drm.rules
    read rules file: /usr/lib/udev/rules.d/60-keyboard.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-vboxdrv.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
    read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    read rules file: /usr/lib/udev/rules.d/69-libmtp.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-setup-link.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
    read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
    read rules file: /usr/lib/udev/rules.d/90-alsa-restore.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-udev-late.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
    read rules file: /etc/udev/rules.d/99-gfk.rules
    read rules file: /usr/lib/udev/rules.d/99-systemd.rules
    read rules file: /usr/lib/udev/rules.d/kino.rules
    rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
    10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
    IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11
    RUN 'kmod load $env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3/7-1.3:1.0
    DEVTYPE=usb_interface
    DRIVER=usb-storage
    ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    ID_VENDOR_FROM_DATABASE=Toshiba Corp.
    INTERFACE=8/6/80
    MODALIAS=usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00
    PRODUCT=930/6545/100
    SUBSYSTEM=usb
    TYPE=0/0/0
    USEC_INITIALIZED=452326811
    run: 'kmod load usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00'
    unload module index
    Unloaded link configuration context
    Last edited by bentglasstube (2014-04-03 20:51:36)

    I see.  That is somewhat aggravating but I will find another way to achieve what I wanted I suppose.
    Thank you.  Should I mark this is solved or unsolvable or something?  Sorry, I'm new to posting on these forums.
    Edit:  I was able to achieve what I wanted with udevil as recommended by the wiki.
    Last edited by bentglasstube (2014-04-03 20:55:45)

  • Issue with Qualcomm WWAN module service

    Hello,
    each time I shut down my T410, XP SP3, w/Qualcomm WWAN module, I get an application error caused by QDLService2KLenovo.exe
    I know this is the WWAN service, and of course if I stop it, the WWAN module is not working anymore.
    Any idea to fix this error?
    thanks,
    H.
    Solved!
    Go to Solution.

    Hi
    I know this may be an old subject but here is a workaround I recently got from Lenovo support.
    Change the Log On user for this Gobi service to Network services:
    - open Windows Services
    - select the Properties of following Service "Qualcomm Gobi 2000 Download Service (Lenovo)"
    - select "Log On" tab
    - select "This account:" and then "Browse..."
    - search on the local machine and search for "Network Service" and confirm
    - now the user should be "NT AUTHORITY\NetworkService"
    - leave both password fields empty
    - confirm all changes
    - restart the "Qualcomm Gobi 2000 Download Service (Lenovo)" Service 
    I solved this with a “one-liner” at the deployment of Windows XP:
    sc config QDLService2kLenovo obj= "NT Authority\Network Service"  password= notused

  • [solved]udev boot error - usb keyboard wont work in recovery shell

    i just hooked up an external drive for the first time to this system, i didnt do anything to it yet, except i went to run gdisk and realized it wasnt installed yet.  So i ran
    pacman -Syu gdisk
    from an SSh terminal, then when it was updating a package, cant exactly remember which one but i hitnk it was either kernel or udev, the ssh termilal appeared to disconnect becuause it lost its output.
    then i opened another terminal sshed in, and was able to run pacman -Syu again, which means the first update did finish, or the lockfile wouldnt have let me update a 2nd time i would think.  (note, the newly external hard drive was connected during all these events).  Something wierd happened here.It had files that needed updating, which i thought that would be rare since i just updated, unless it simply didnt finish, and the lockfile wasnt in place or something, then it finished updating successfully, and i was still remoted into a working SSH command line (i.e. didnt get kicked out this time).
    Now is where the fun begins.  i typed 'reboot', and the system appeared to reboot, but i wasnt able to shell in this time.  i connected the monitor to the system almost a minute later, and realized it was still shutting down, then when it rebooted i get an error message.
    running early hook [udev]
    Warning lib/modules/3.12.8-1-ARCH/modules.devname not found - ignoring
    runnign hook [udev]
    tiggering events
    Waiting 10 seconds for device /dev/sda2
    ERROR: device /dev/sda2 not found Skipping fsck
    Error unable to find root device /dev/sda2
    your being dropped to recovery shell
    [rootfs /]#
    NOW THE KEYBOARD DOESNT WORK, it only works in bios.  It stops functioning (the numlock light)  as soon as udev starts to initiate, which leaves me with no way to try to reupdate udev and the kernel again to see if i can fix it.
    all i could think of was to disconnect the external drive, that didnt help.  then i tried checking the USB settings in bios for any legacy options, it doesnt have them (Dell Optiplex), so i just made sure the USB boot was off and all ports enabled.
    Now im totally stuck short of a recovery disk. 
    any suggestions how i can just get the keyboard working and chroot into arch and update some package to fix it without having to jump through hoops to make a recovery disk while here at work with limited resources?
    Last edited by wolfdogg (2014-01-22 22:53:02)

    ok i found what happened, so far. 
    looking in /var/log/pacman.log i see a gap in the installs, a 2 minute gap, which is the time i rebooted and reran the install.
    at 9:25..  i was running an upgrade, and the last one in the minute of 9:25 is
    9:25[PACMAN] upgraded linux-firmware (20131013.7d0c7a8-1 -> 20131230.52d77db-1)
    this is where the shell got disconnected therefore i wasnt able to see what happened after this. 
    the the log continues at 9:27 minute, has to be when i rebooted and shelled back in and reran the upgrade, the log starts with
    9:27[PACMAN] upgraded linux (3.12.6-1 -> 3.12.8-1)
    so it appears that the shell got disconnected as it was upgrading linux-firmware (20131013.7d0c7a8-1 -> 20131230.52d77db-1)  .
    This begs the questions; Did the SSH shell get disconnected simply because the system was using those resources at the time?  i assume this.  the next question is, was it wrong to be upgrading via remote SSH shell then?  Or whats likely that happened here?
    Last edited by wolfdogg (2014-01-22 22:20:04)

Maybe you are looking for

  • I dont see apple tv in my itunes, how can I find it so that i sync it with apple tv

    I can not type in my itunes the code indicated by apple tv on tv screen in order to sync both

  • Updating Purchase Order

    Hello everyone, I have a business requirement to add a new custom field, at item level, in the Purchase Order transaction (ME21N/ME22N/ME23N). It is a char10 field. I have already created this new field, which is correctly updating the EKPO table. Bu

  • NETWORK OUT OF ORDER

    according to this http://btsc.webapps.blackberry.com/btsc/dynamickc.do?externalId=KB13324&sliceID=1&command=show&forwa... i should change the Network Send over.. but it doesnt say GPRS.. my phone only have options: ..circuit switched ..circuit switch

  • Retention periods same for the deletion and for archiving then deletion

    Hi, Is Retention periods same for the deletion and for archiving then deletion. Can we delete canceled messages directly in XI wihtout archiving them ? I want only deltion of messages from XI. Regards Sree

  • Binding troubleshooting

    Hi! I've been struggling with a bit of binding code - I'm making tabs, and I'm trying to get the content to change when a different tab is selected. The tab headers change so far, but the tab content doesn't. When a tab header is clicked on, the tab