[arch-general] hal has lost its mind again.

David C. Rankin, J.D.,P.E. drankinatty at suddenlinkmail.com
Sun May 17 04:51:10 EDT 2009

On or about Sunday 17 May 2009 at approximately 03:16:26 David C. Rankin, 
J.D.,P.E. composed:
> Listmates,
> 	On my laptop, automounting of usb drives and mmc/sd cards were working
> fine, now I get the "...mount.removable no <-- (action, result)" Full error
> dialog:
> http://www.3111skyline.com/download/Archlinux/bugs/hal-mount.removable.jpg
> 	The system configures the drives or cards just fine, it just will not
> create the directory under /media to allow access. It is really ironic
> because the drives/cards are fully accessible under "media:/". So, nothing
> in "/media", but OK in "media:/".
> 	I am concerned that changes made
> in /etc/hal/fdi/policy/20-ntfs-config-write-policy.fdi to allow NTFS mounts
> messed something else up. The file contains:
> <deviceinfo version="0.2">
> 	<device>
> 		<match key="volume.fstype" string="ntfs">
> 			<match key="@block.storage_device:storage.hotpluggable" bool="true">
> 				<merge key="volume.fstype" type="string">ntfs-3g</merge>
> 				<merge key="volume.policy.mount_filesystem"
> type="string">ntfs-3g</merge> </match>
> 		</match>
> 	</device>
> </deviceinfo>
> 	which is straight from the wiki. The everything log contains the
> following:
> May 17 02:50:23 alchemy kernel: tifm_core: MMC/SD card detected in socket
> 0:1 May 17 02:50:23 alchemy kernel: mmc1: new SD card at address e624
> May 17 02:50:23 alchemy kernel: isa bounce pool size: 16 pages
> May 17 02:50:23 alchemy kernel: mmcblk0: mmc1:e624 SD02G 1.89 GiB
> May 17 02:50:23 alchemy kernel: mmcblk0: p1
> May 17 02:55:20 alchemy hald: mounted /dev/mmcblk0p1 on behalf of uid 0
> May 17 03:06:54 alchemy kernel: ACPI: EC: missing confirmations, switch off
> interrupt mode.
> 	I don't know if the ACPI kernel message is evidence of the problem, but I
> included it just in case. I am slowly trying to make friends with hal/dbus,
> but I could use any help you can give in sorting this out. Thanks.

	Another interesting note. When I inserted the card, there was no entry 
created in /media. Now 10 minutes later after I have been copying the photos, 
etc., the mount of /dev/mmcblk0p1 has *appeared* mounted on /media/disk? Huh?

	I can't tell you when it appeared, but I can tell you that for at least 4-5 
minutes. So why the initial error and why the magical appearance after the 
error telling me it wasn't going to be mounted? What to check for more info?

David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339

More information about the arch-general mailing list