Kindle 2 HAL support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HAL |
Fix Released
|
Medium
|
|||
hal-info (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: hal-info
When I connect my Kindle 2 via USB, HAL recognizes it as a USB mass storage device. It does not recognize it as an ejectable volume, however.
Kindle support (as a media player) was added to HAL in https:/
It seems a bit strange to me to classify the Kindle as a portable audio player - it certainly can play media, but so can PDAs (and the Kindle seems more like a PDA to me). Perhaps, given all the new ebook reader devices already out there and soon to be released, a new category may be needed. But as I am pretty unfamiliar with HAL, I cannot adequately evaluate the ramifications of these classifications. :) And since the Kindle 1 is supported by HAL as a media player, so I have added Kindle 2 support as a media player.
Rather than mess with any of the Kindle 1 stuff, I added a different match for the Kindle 2. The Kindle 2 needs to be ejected and not just unmounted (umounting it does nothing about the message on the Kindle that it needs to be ejected from the computer before being used - the Kindle remains in USB drive mode), and I am not sure if that is the case with the Kindle 1.
tags: | added: patch-forwarded-upstream |
Changed in hal: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
tags: |
added: patch-accepted-upstream removed: patch-forwarded-upstream |
Changed in hal: | |
importance: | Medium → Unknown |
Changed in hal: | |
importance: | Unknown → Medium |
Hmm... ok, this patch is probably not very useful. :( With this 10-usb- music-players. fdi change, I can eject the Kindle just fine, and the Kindle leaves USB drive mode, but I then get the following error on my screen (not on the Kindle):
Cannot eject volume
There was an error ejecting the volume or drive.
org.freedesktop .Hal.Device. UnknownError: An unknown error occured.
There doesn't SEEM to be a problem besides this error dialog, but I'm not sure how to interpret the hal.log.
I'm including the output from lshal, from running hald in debugging/verbose mode, and a snippet of my kern.log.
After I rebooted, I stopped hald, and then hald in non-daemon debug mode. Then I plugged in my Kindle 2, got the output from lshal, and ejected (via gnome-applets' disk-mounter applet) the Kindle. Then I stopped the debug-mode hald. The kern.log snippet is from about when I rebooted.