HAL doesn't detect my cdrom(s)

Chris Burel chrisburel at gmail.com
Sun Apr 12 22:40:41 PDT 2009


...After much trial and error, I tried installing hal 0.5.12rc1, which seems
to have fixed the problem.  Now I get 143 devices listed by hal-devices
instead of 5.

On Sun, Apr 12, 2009 at 2:34 AM, Chris Burel <chrisburel at gmail.com> wrote:

> It looks like this goes all the way up to udev.  I don't get any uevent
> when I insert a cd in either of my drives.
> > udevadm monitor --env
> monitor will print the received events for:
> UDEV the event which udev sends out after rule processing
> UEVENT the kernel uevent
>
> and then nothing.  If I manually mount (assuming it's a data cd), then the
> uevent occurs.  But seeing as I want to play an audio cd, I can't just
> manually mount it.
>
> Is there an option in the kernel to send uevents on cd insert?  Or does
> udev/hal have to probe for those events?
>
>
> On Sat, Apr 11, 2009 at 3:56 PM, Chris Burel <chrisburel at gmail.com> wrote:
>
>> I suppose I should mention that I'm using
>> HAL 0.5.11
>> dbus 1.2.4, built Dec 4 2008, so that's before the permissive branch was
>> released.  I don't really know the details of the split in dbus.
>>
>> Should I try hal 0.5.12rc1?
>>
>>
>> On Sat, Apr 11, 2009 at 1:58 PM, Chris Burel <chrisburel at gmail.com>wrote:
>>
>>> ~$> hal-find-by-property --key 'block.device' --string '/dev/sr0'
>>> --verbose
>>> Found 0 device objects with string property block.device = '/dev/sr0'
>>> ~$> hal-find-by-property --key 'block.device' --string '/dev/sr1'
>>> --verbose
>>> Found 0 device objects with string property block.device = '/dev/sr1'
>>> ~$> hal-find-by-property --key 'block.device' --string '/dev/cdrom'
>>> --verbose
>>> Found 0 device objects with string property block.device = '/dev/cdrom'
>>>
>>> ~$> cat /proc/sys/dev/cdrom/info
>>> CD-ROM information, Id: cdrom.c 3.20 2003/12/17
>>>
>>> drive name:             sr1     sr0
>>> drive speed:            40      40
>>> drive # of slots:       1       1
>>> Can close tray:         1       1
>>> Can open tray:          1       1
>>> Can lock tray:          1       1
>>> Can change speed:       1       1
>>> Can select disk:        0       0
>>> Can read multisession:  1       1
>>> Can read MCN:           1       1
>>> Reports media changed:  1       1
>>> Can play audio:         1       1
>>> Can write CD-R:         0       1
>>> Can write CD-RW:        0       1
>>> Can read DVD:           1       1
>>> Can write DVD-R:        0       1
>>> Can write DVD-RAM:      0       0
>>> Can read MRW:           0       1
>>> Can write MRW:          0       1
>>> Can write RAM:          0       1
>>>
>>> This has been driving me crazy.  It manifests itself in that the
>>> kio_audiocd slave for kde crashes, which I traced back to Solid, which comes
>>> back to HAL.  The only hal devices I get are these:
>>> ~$> hal-device | grep ': udi ='
>>> 0: udi = '/org/freedesktop/Hal/devices/computer_drm_r300_card0'
>>> 1: udi = '/org/freedesktop/Hal/devices/computer'
>>> 2: udi = '/org/freedesktop/Hal/devices/acpi_PWRF'
>>> 3: udi = '/org/freedesktop/Hal/devices/acpi_PWRB'
>>> 4: udi = '/org/freedesktop/Hal/devices/acpi_CPU1'
>>> 5: udi = '/org/freedesktop/Hal/devices/acpi_CPU2'
>>>
>>> I have tried to follow the directions for configuring HAL:
>>> My user is a member of the halusers group
>>> I have the files
>>> /etc/dbus-1/system.d/halusers.conf
>>> /etc/hal/fdi/policy/no-fixed-drives.fdi
>>> I have installed gnome-volume-manager-2.24.1
>>> I don't have /etc/hal/fdi/policy/user-options.fdi
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/blfs-support/attachments/20090412/3d14b8d8/attachment.html>


More information about the blfs-support mailing list