Hi there, The Palm LifeDrive and T|X have a "Drive Mode" functionality that exposes the onboard FAT32 partitions as USB drives. However, Palm's idea of what constitutes a FAT32 partition is a bit... weak. ;) Below are Matthew Garrett's insights on the filesystem probe failure from the hal list; he suggested I get in touch with the udev developers. I've made an image of a newly-formatted partition and posted it at http://launchpadlibrarian.net/19129151/sdb1.img.bz2 and the Ubuntu bug with more info can be found at https://bugs.launchpad.net/ubuntu/+source/hal/+bug/81219. It's unfortunately not enough to format the partition with mkdosfs or fsck it into compliance; the device will "fix" the partition at some point in the future rendering it unmountable again. (Thought you can force-mount it with a -t vfat.) ----- Forwarded message from Matthew Garrett <mjg59@xxxxxxxxxxxxx> ----- From: Matthew Garrett <mjg59@xxxxxxxxxxxxx> To: Matt Behrens <matt@xxxxxxxx> Subject: Re: LifeDrive and T|X not seen by hal Ok. The following things appear to be causing the failure: 1) The FAT signature in bytes 510 and 511 isn't present. This causes the code to bail. 2) The FAT32 signature in the fsinfo block isn't present. This causes the code to bail. 3) The loop looking for the root dir appears to jump out past the code that sets the filesystem label. This results in it ignoring the UUID and filesystem name. You probably need to get in touch with the udev developers to get this fixed - I'm not sure which of these checks could result in false positives unless care is taken. Once libvolume_id is fixed hal should just work. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ hal mailing list hal@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/hal ----- End forwarded message -----
Attachment:
signature.asc
Description: Digital signature
