search for: udev_log

Displaying 8 results from an estimated 8 matches for "udev_log".

2013 May 15
8
[Bug 64645] New: Massive corruption
...E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10000000000000 0 E: MODALIAS=input:b0019v0000p0001e0000-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=3821882 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1 N: input/event1 E: BACKSPACE=guess E: DEVNAME=/dev/input/event1 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1 E: DMI_VENDOR=Dell Inc. E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00...
2012 Feb 06
8
Cdrom on Linux domU PV
I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without
2010 Apr 29
24
[Bug 27905] New: DVI monitor is blank - DVI detected as Display Port ?
...2 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section "Device" Identifier "n" Driver "nouveau" EndSection udev information: P: /devices/platform/i8042/serio0/input/input0/event0 N: input/event0 S: char/13:64 S: input/by-path/platform-i8042-serio-0-event-kbd E: UDEV_LOG=3 E: DEVPATH=/devices/platform/i8042/serio0/input/input0/event0 E: MAJOR=13 E: MINOR=64 E: DEVNAME=/dev/input/event0 E: SUBSYSTEM=input E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_SERIAL=noserial E: ID_PATH=platform-i8042-serio-0 E: XKBMODEL=pc105 E: XKBLAYOUT=fr E: XKBVARIANT=lati...
2005 Dec 06
1
RE: Hotplug scripts not working... xen/ia64 domU stoppedworking
...if6.0 UDEV [1133883396] add@/devices/xen-backend/vif-6-0 HOME=/ PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add DEVPATH=/devices/xen-backend/vif-6-0 SUBSYSTEM=xen-backend SEQNUM=1206 PHYSDEVBUS=xen-backend XENBUS_TYPE=vif XENBUS_PATH=backend/vif/6/0 XENBUS_BASE_PATH=backend/vif XENBUS_FRONTEND_ID=6 UDEV_LOG=3 UDEV [1133883396] online@/devices/xen-backend/vif-6-0 HOME=/ PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=online DEVPATH=/devices/xen-backend/vif-6-0 SUBSYSTEM=xen-backend SEQNUM=1208 PHYSDEVBUS=xen-backend PHYSDEVDRIVER=vif XENBUS_TYPE=vif XENBUS_PATH=backend/vif/6/0 XENBUS_BASE_PATH=backend/vif...
2004 Jun 07
2
run-init warning
Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa
2018 Oct 30
0
Fw: Re: [SPDK] VM boot failed sometimes if using vhost-user-blk with spdk
...o: "storage performance development kit" <spdk at lists.01.org> Cc: centos at centos.org, qemu-discuss at nongnu.org Subject: Re: [SPDK] VM boot failed sometimes if using vhost-user-blk with spdk I enable debug of systemd-udevd by changing guest's /etc/udev/udev.conf to this: udev_log="debug" and regenerate initramfs. Then, we can get more message about this issue. I select some useful messages from /run/initramfs/rdsosreport.txt: systemd-udevd[199] probe /dev/vdb raid offset=8 systemd-udevd[199] no db file to read /run/udev/data/+virtio:virtio1: No such systemd...
2014 Jul 18
2
Anyone using CentOS 6 on PC104 stacks?
...Has 6 dropped support for ISA somehow? Any ideas on what might be wrong or where to start debugging? I have tried: Setting selinux to permissive (there was a udev issue in 6.0 where this was needed) Removing quiet and RHGB from the boot, so I can see what is going on In /etc/udev/udev.conf set udev_log="debug", but this seems to just information overload, AND It never stops at the same set of messages. Even booted with udevtrace. Syslog has not started, so there is nothing in /var/log/messages Moved /etc/udev/rules.d/* to /etc/udev/rules.distro/ so that rules created at install time,...
2009 Nov 13
1
Xorcom Astribank udev issue in Ubuntu 9.10
...eems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger --attr-match=idVendor=e4e4 --action add UDEV [1258155881.753357] add /devices/pci0000:00/0000:00:1a.7/usb1/1-1 (usb) UDEV_LOG=7 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-1 SUBSYSTEM=usb DEVNAME=/dev/bus/usb/001/009 DEVTYPE=usb_device DRIVER=usb DEVICE=/proc/bus/usb/001/009 PRODUCT=e4e4/1141/ffff TYPE=0/0/0 BUSNUM=001 DEVNUM=009 SEQNUM=1516 ID_VENDOR=Xorcom_LTD ID_VENDOR_ENC=Xorcom\x20LTD ID_VENDOR_ID=e4e4...