You are not logged in.
Hi folks, I've run into an issue that appears to be hal related (though I really have no idea, policykit, polkit, hal, etc, all confuse the hell out of me). Hal doesn't detect usb devices. I insert the device, and it's detected by the kernel, and a device node is created:
Insert:
# dmesg
usb 1-8: new high speed USB device using ehci_hcd and address 10
usb 1-8: configuration #1 chosen from 1 choice
scsi15 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 10
usb-storage: waiting for device to settle before scanning
scsi 15:0:0:0: Direct-Access 0.00 PQ: 0 ANSI: 2
sd 15:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
sd 15:0:0:0: [sdc] 7897088 512-byte logical blocks: (4.04 GB/3.76 GiB)
sd 15:0:0:0: [sdc] Write Protect is off
sd 15:0:0:0: [sdc] Mode Sense: 00 00 00 00
sd 15:0:0:0: [sdc] Assuming drive cache: write through
sd 15:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
# lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 010: ID 1307:0165 Transcend Information, Inc. 2GB/4GB Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
HAL, however, doesn't see it:
[root@pinkwater kdm]# lshal -m
Start monitoring devicelist:
-------------------------------------------------
(plug, unplug, plug, unplug -- nothing)
I also verified that the number of devices seen by lshal doesn't change at all. Using KDE4.4 on a fully up to day system if that matters at all. What am I missing?
Last edited by Snarkout (2010-03-01 13:56:15)
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
Looks like this was my fault. A while back I reinstalled udev because of some issues I was having with it, and had moved my old /etc/udev dir to a backup location. Apparently I needed a udev rule with the following in it:
# pass all events to the HAL daemon
RUN+="socket:@/org/freedesktop/hal/udev_event"
now things appear to be working. What's odd is this had *definitely* been working since then - I hadn't even upgraded to kde4.4 till a week or two after I messed with udev. My WAG would be that some change in policykid/polkit/polkit-1 requires this missing rule. I did verify that if I remove the rule, doing a forced reinstall of hal produces the rule, so that would have been the best solution.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline