Kay Sievers [Fri, 29 Apr 2011 12:27:11 +0000 (14:27 +0200)]
configure: allow to enable/disable extras individually
- remove gobject introspection switch
- disable hid2hci by default (moved to bluez)
- disable action-modeswitch by default (will move to usb_modeswitch)
- disable edd_id by default (problems with disk signatures)
- disable legacy floppy by default (no more nasty device node hacks by default)
Michael Reed [Wed, 20 Apr 2011 18:25:16 +0000 (20:25 +0200)]
path_id: rework SAS device handling
Lun numbers < 256 are displayed as "lun-x". Lun numbers >= 256 use
the lun number format previously used in fibre channel by-path
links, 0xabcd012300000000. This lun numbering scheme is implemented
for sas, fibre channel, iscsi.
I want it to be clearly understood that this patch changes the
/dev/disk/by-path names for fc devices. Here is an example of the
change:
Old: pci-0000:0c:00.1-fc-0x204700a0b81130aa:0x00fa000000000000
New: pci-0000:0c:00.1-fc-0x204700a0b81130aa-lun-250
Kay Sievers [Wed, 13 Apr 2011 20:33:01 +0000 (22:33 +0200)]
udevadm: info --cleanup-db
Most of the udev database from initramfs should be deleted before
starting udev in the real root. udevadm: info --cleanup-db deletes
all database entries in /run/udev. Events that processed IMPORT{db},
or mark devices explicitely as persistent, will be excluded.
Martin Pitt [Mon, 4 Apr 2011 09:47:54 +0000 (11:47 +0200)]
Avoid spinning up CD on pressing eject button
When the CD tray door is locked and the hardware eject button is pressed, newer
kernels (2.6.38+) will send out a change event with a DISK_EJECT_REQUEST==1
property. Do not run cdrom_id and blkid in this case, as the media state and
contents does not change, and this only needlessly spins up the drive again
right before ejection.
Lee, Chun-Yi [Thu, 31 Mar 2011 10:01:05 +0000 (18:01 +0800)]
Add rule for Acer Aspire One ZG8 to use acer-aspire_5720 keymap
Acer Aspire One ZG8's bluetooth HW key emit 0xD9 scancode, it must map
to KEY_BLUETOOTH like Acer Aspire 5720. So, add rule for Acer Aspire One
ZG8 use acer-aspire_5720 keymap.
Tested on Acer Aspire One ZG8 netbook.
Signed-off-by: Lee, Chun-Yi <jlee@novell.com> Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
David Zeuthen [Wed, 30 Mar 2011 12:11:03 +0000 (08:11 -0400)]
Run ata_id on non-removable USB devices
If a USB device is marked as removable, it is often a SATA/PATA disk
in an enclosure (note that flash card readers and usb storage sticks
are always marked as removable). In this case, try running ata_id
(which sends ATA commands wrapped in SCSI ATA PASS THROUGH commands)
to get information about the disk. If this fails, just fall back to
running usb_id since it could be the device isn't an ATA device at
all or the device doesn't have a SAT layer.
This extra information is nice to have as it indicates if it is
suitable to send e.g. SMART commands to the disk, whether the disk
supports power management and so on. Additionally, the VPD and serial
number returned by ata_id is usually more accurate as it stems from
the disk itself instead of the enclosure.
Set hostname to <eeepc>.
Found ordering cycle on sysinit.target/start
Walked on cycle path to systemd-tmpfiles-setup.service/start
Walked on cycle path to local-fs.target/start
Walked on cycle path to fedora-storage-init.service/start
Walked on cycle path to fedora-wait-storage.service/start
Walked on cycle path to udev-settle.service/start
Walked on cycle path to udev.service/start
Walked on cycle path to udev.socket/start
Walked on cycle path to sysinit.target/start
Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
Kay Sievers [Mon, 28 Mar 2011 23:14:53 +0000 (01:14 +0200)]
systemd: do not enable udev-settle.service by default
This barrier service is usually not enabled by default. If enabled,
it acts as a barrier for basic.target -- so all later services will
wait for udev completely finishing its coldplug run.
It might be enabled just unconditionally, or pulled-in on-demand by
broken or non-hotplug-aware services that assume a fully populated
/dev at startup.
Kay Sievers [Mon, 28 Mar 2011 12:34:05 +0000 (14:34 +0200)]
libudev: make valgrind happy
Warning: noted but unhandled ioctl 0x641e with no size/direction hints
Syscall param socketcall.setsockopt(optval) points to uninitialised byte(s)
at 0x6A30BAA: setsockopt (syscall-template.S:82)
by 0x4E36E1C: udev_monitor_filter_update (libudev-monitor.c:347)
by 0x4E36ED8: udev_monitor_enable_receiving (libudev-monitor.c:373)
by 0x8A9E68E: I830ScreenInit (intel_driver.c:838)
by 0x42EE9E: AddScreen (dispatch.c:3890)
by 0x471561: InitOutput (xf86Init.c:738)
by 0x422C18: main (main.c:205)
Location 0x7ff0000c2 is 2 bytes inside local var "filter"
declared at libudev-monitor.c:256, in frame #1 of thread 1
Uninitialised value was created by a stack allocation
at 0x4E30860: ??? (in /lib64/libudev.so.0.10.0)
Seth Forshee [Thu, 24 Mar 2011 15:33:54 +0000 (16:33 +0100)]
keymap: continue reading keymap after invalid scancodes
Reading of keymaps is aborted when EINVAL is returned from EVIOCGETKEYCODE.
Scan codes are not always continuous ranges of values starting at 0, so this
can result in not getting the full keymap for a device. Instead, continue
processing if EINVAL is returned.
Kay Sievers [Wed, 23 Mar 2011 15:40:23 +0000 (16:40 +0100)]
systemd: bind udev control socket in systemd and split udev.service
We should bind the udev socket from systemd, so we are sure
that the abstract namespace socket is always bound by a root
process and there is never a window during an update where
an untrusted process can steal our socket.
Also split the udev.service file, so that the daemon can be
updated/restarted without triggering any coldplug events.
Kay Sievers [Wed, 23 Mar 2011 00:41:25 +0000 (01:41 +0100)]
udevd: use facility == LOG_DAEMON when writing to /dev/kmsg
Syslog wants to distinguish the sorce of messages. We should
indicate that this is a userspace message (LOG_DAEMON) and not
a kernel message (LOG_KERNEL).
Martin Pitt [Fri, 18 Mar 2011 13:45:42 +0000 (14:45 +0100)]
input_id: Cover key devices which only have KEY_* > 255
We previously only tested the "key" capabilities for keys between 0 and 255 to
determine ID_INPUT_KEY. If there are none, also check for keys in the upper
block (KEY_OK/0x160 to KEY_TOUCHPAD_OFF/0x214).