My Kindle is not being recognised by Calibre

[robynmau]

Good Morning

My Kindle has stopped being recognised by Calibre, but Win7 is still seeing it. I found the debug in the advanced section. The script that came up is below:

Version: 0.8.36
USB devices on system:
[u'usb\\root_hub20&vid8086&pid1c26&rev0004',
u'usb\\root_hub20&vid8086&pid1c2d&rev0004',
u'usb\\vid_046d&pid_c517&rev_3820',
u'usb\\vid_046d&pid_c517&rev_3820&mi_00',
u'usb\\vid_046d&pid_c517&rev_3820&mi_01',
u'usb\\vid_05e3&pid_0605&rev_060;',
u'usb\\vid_1949&pid_0004&rev_0100',
u'usb\\vid_1bcf&pid_288a&rev_0318',
u'usb\\vid_1bcf&pid_288a&rev_0318&mi_00',
u'usb\\vid_8087&pid_0024&rev_0000',
u'usb\\vid_8087&pid_0024&rev_0000']
Drives detected:
(0) H:\ ~ \\?\STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_KINDLE&PRO D_INTERNAL_STORAGE&REV_0100#B008D0A112540LN8&0#{53 F56307-B6BF-11D0-94F2-00A0C91EFB8B}#{53F5630D-B6BF-11D0-94F2-00A0C91EFB8B}
Available plugins: EX124G

Looking for devices...

Devices possibly connected: None


Can someone please advise how I get my kindle back onto Calibre

Many thanks in advance

Cheers

Robyn

[kovidgoyal]

Go to preferences->plugins and re-enable the Kindle device plugins.

[robynmau]

Hey Kovid
Thanks so much for responding so quickly, I really appreciate it. All is good now!!!

Cheers

Robyn

[fbb]

Hi all,

As I just registered to this list I may experience some startup problems, but I, too, cannot access the Kindle device from calibre. Here's what I've done so far:

1. connect the Kindle:

2. I do not use auto-mounting, but my syslog shows the device is recognized:

Mar 26 18:48:28 localhost kernel: [38283.172124] usb 2-1: new high-speed USB device number 5 using ehci_hcd
Mar 26 18:48:28 localhost kernel: [38283.317444] usb 2-1: New USB device found, idVendor=1949, idProduct=0004
Mar 26 18:48:28 localhost kernel: [38283.317454] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 26 18:48:28 localhost kernel: [38283.317461] usb 2-1: Product: Amazon Kindle
Mar 26 18:48:28 localhost kernel: [38283.317467] usb 2-1: Manufacturer: Amazon
Mar 26 18:48:28 localhost kernel: [38283.317472] usb 2-1: SerialNumber: B01114071464AASX
Mar 26 18:48:28 localhost kernel: [38283.322516] scsi10 : usb-storage 2-1:1.0
Mar 26 18:48:29 localhost kernel: [38284.322409] scsi 10:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2
Mar 26 18:48:29 localhost kernel: [38284.333743] sd 10:0:0:0: [sdb] Attached SCSI removable disk

3. Unfortunately, the debug option tells me calibre can't connect to the device:

Version: 0.8.41
USB devices on system:
[['0x1d6b',
'0x2',
'0x302',
'Linux 3.2.0-2-686-pae ehci_hcd',
'EHCI Host Controller',
'0000:00:1d.7'],
['0x1d6b',
'0x1',
'0x302',
'Linux 3.2.0-2-686-pae uhci_hcd',
'UHCI Host Controller',
'0000:00:1d.0'],
['0x1d6b',
'0x1',
'0x302',
'Linux 3.2.0-2-686-pae uhci_hcd',
'UHCI Host Controller',
'0000:00:1d.2'],
['0x64e',
'0xa103',
'0x100',
'SuYin',
'Acer Crystal Eye webcam',
'CN0314-SN30-OV03-VA-R02.03.02'],
['0x1d6b',
'0x2',
'0x302',
'Linux 3.2.0-2-686-pae ehci_hcd',
'EHCI Host Controller',
'0000:00:1a.7'],
['0x1d6b',
'0x1',
'0x302',
'Linux 3.2.0-2-686-pae uhci_hcd',
'UHCI Host Controller',
'0000:00:1a.2'],
['0x1d6b',
'0x1',
'0x302',
'Linux 3.2.0-2-686-pae uhci_hcd',
'UHCI Host Controller',
'0000:00:1d.1'],
['0x1949', '0x4', '0x100', 'Amazon', 'Amazon Kindle', 'B01114071464AASX'],
['0x1d6b',
'0x1',
'0x302',
'Linux 3.2.0-2-686-pae uhci_hcd',
'UHCI Host Controller',
'0000:00:1a.1'],
['0x1d6b', '0x1',
'0x302',
'Linux 3.2.0-2-686-pae uhci_hcd',
'UHCI Host Controller',
'0000:00:1a.0'],
['0x147e', '0x1000', '0x33', 'TouchStrip', 'Fingerprint Sensor', '']]
Available plugins: ADAM ALEX ALURATEK_COLOR ANDROID ARCHOS7O AVANT AZBOOKA BAMBOOK
BLACKBERRY BOEYE_BDX BOEYE_BEX BOOQ BOOX COBY COOL_ER CYBOOK DBOOK E52
E71X EB511 EB600 EBK52 ECLICTO EDGE EEEREADER ELONEX ESLICK EX124G
FOLDER_DEVICE_FOR_CONFIG GEMEI GER2 HANLINV3 HANLINV5 ILIAD INVESBOOK
IPAPYRUS IREXDR1000 IREXDR800 IRIVER_STORY ITALICA JETBOOK
JETBOOK_MINI KINDLE KINDLE2 KINDLE_DX KINDLE_FIRE KOBO LIBREAIR
LUMIREAD MENTOR MOOVYBOOK N516 N770 N810 NEWSMY NEXTBOOK NOOK
NOOK_COLOR NUUT2 ODYSSEY ORIZON PALMPRE PDNOVEL PDNOVEL_KOBO PI2 PICO
PLAYBOOK POCKETBOOK301 POCKETBOOK360 POCKETBOOK360P POCKETBOOK602
POCKETBOOK701 PRS505 PRST1 README S60 SHINEBOOK SNE SOVOS SPECTRA
STASH SUNSTECH_EB700 SWEEX TECLAST_K3 THEBOOK TREKSTOR USER_DEFINED
VELOCITYMICRO WEBOS WEXLER

Looking for devices...
(6473, 4, 256, 'Amazon', 'Amazon Kindle', 'B01114071464AASX')
Detected possible device KINDLE2

Devices possibly connected: Kindle 2/3/4/Touch Device Interface,
Trying to open Kindle 2/3/4/Touch Device Interface ... failed
Opening of the following devices failed
<calibre.devices.kindle.driver.KINDLE2 object at 0xa5df12c>
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/devices/__init__.py", line 124, in debug
dev.open(det, None)
File "/usr/lib/calibre/calibre/devices/usbms/device.py", line 860, in open
self.open_linux()
File "/usr/lib/calibre/calibre/devices/usbms/device.py", line 615, in open_linux
%self.__class__.__name__)
DeviceError: Unable to detect the KINDLE2 disk drive. Either the device has already been ejected, or your kernel is exporting a deprecated version of SYSFS.


4. To be sure: the Kindle device is still attached to my computer. I also checked the kernel parameters, as per the advice given in the userguide and they were as intended:

grep SYSFS_DEPRECATED /boot/config-`uname -r`
# CONFIG_SYSFS_DEPRECATED is not set

grep CONFIG_SCSI_MULTI_LUN /boot/config-`uname -r`
CONFIG_SCSI_MULTI_LUN=y


5. Thinking that it might be a permissions-problem I tried to connect to the kindle using calibre as root, but this doesn't alter calibre's behavior


6. Following Kovid's suggestion to re-enable the kindle plugin didn't work either.

Additional info: My computer runs debian linux (wheezy [=testing]).


I'm running out of options. Any suggestion what to do next?

Thanks in advance for any input,
Cheers,

Frank.

[kovidgoyal]

Use the official calibre binary and not the debian package. Make sure you have a working install of udev and dbus on your system.

[fbb]

Hi Kovid,

Thanks for the quick reply. I downloaded and installed the `official' binary as you suggested. Udev and dbus are installed and afaik they're working OK. From the requirements listed at the download page: my glibc version is 2.13-27, python is at 2.7.2-10, and xdg-utils has also been installed.

Unfortunately, the behavior of calibre 0.8.44 is not different from the one offered by Debian, so it looks as though I'm still at square 1.

I appreciate your support; if you have any other suggestions (or maybe require additional information?) please let me know.

Cheers,

Frank.

[kovidgoyal]

That error indicates calibre is unable to find the kindle's device node in your sysfs filesystem. The only way that can happen that I know of is if your kernel has something non-standard about it. I suggest you use the connect to folder function in calibre unless you feel like debugging the issue, in which case the relevant code is find_device_nodes() in usbms/device.py and instructions for running calibre from source are under setting upa calibre development environment in the user manual.

[fbb]

Hi Kovid,

Thanks again for the reply.

I've at least managed to take one step ahead: it looks as though some specific mounting options are required. Right now I'm trying to access a Sony e-reader.

Unfortunately the manual doesn't tell me which mounting options are required, usbmount mounts the device:

mount -tvfat -orw,nosuid,nodev,shortname=mixed,dmask=0077,utf8=1 ,showexec,flush,uhelper=udisks /dev/sdb /media/usb1


and its books are shown.

However, its 'cardA' doesn't show up.Why not?

When I manually mount the vfat filesystems (using the commands

mount -tvfat -orw,nosuid,nodev,shortname=mixed,dmask=0077,utf8=1 ,showexec,flush,uhelper=udisks /dev/sdb /media/usb1

and

mount -tvfat -orw,nosuid,nodev,shortname=mixed,dmask=0077,utf8=1 ,showexec,flush,uhelper=udisks /dev/sdd1 /media/usb0


calibre does show a device and card A icon, but no books are displayed anymore. Neither for device1 nor for cardA. What I do get is a comm. failure with the following message:

'ascii' codec can't encode character u'\xeb' in position 60: ordinal not in range(128)

Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/device.py", line 82, in run
self.result = self.func(*self.args, **self.kwargs)
File "/usr/lib/calibre/calibre/gui2/device.py", line 340, in _books
cardalist = self.device.books(oncard='carda')
File "/usr/lib/calibre/calibre/devices/prs505/driver.py", line 199, in books
bl = USBMS.books(self, oncard=oncard, end_session=end_session)
File "/usr/lib/calibre/calibre/devices/usbms/driver.py", line 209, in books
for path, dirs, files in os.walk(ebook_dir):
File "/usr/lib/python2.7/os.py", line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
File "/usr/lib/python2.7/os.py", line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
File "/usr/lib/python2.7/os.py", line 284, in walk
if isdir(join(top, name)):
File "/usr/lib/python2.7/genericpath.py", line 41, in isdir
st = os.stat(s)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xeb' in position 60: ordinal not in range(128)

Unfortunately this doesn't help me much further in solving the problem: position 60 where? what is s in os.stat(s)? Where does it come from?


But at least I'm able to access the data now and epub files can be copied between the two devices. If I copy a book from usb0 to usb1, then umount usb0, the copied book nicely shows up in calibre's 'device' books. I wouldn't call that elegant, though, and I am still puzzled as to why calibre doesn't show the books when both devices are mounted...

So, maybe no longer at square 1, but not much farther than square 2. Any suggestions about how to proceed from here would be appreciated.

Cheers,

Frank.

[kovidgoyal]

1) Use the official calibre binary
2) Find all files/directories with non ascii characters in their names on your device and delete them.