I'm sorry -- I've probably done something wrong earlier, and then tried to mount the device as "readonly" to be on the safe side, and that seems to have been the source of my problems later. After generating the usbmon reports (relying on shell history), I noticed the "-o readonly" in the command and the "...bad option, " in the error message, tried without it, and it worked. There still is something weird here -- HAL doesn't seem to realize the device is there, but that's probably not a kernel issue. I've attached the usbmon output of successful connect-mount-ls-umount-disconnect on 2.6.32 for completeness. I apologize sincerely for wasting your time, Shai. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html