Main and memory card memory swapped when connected to Pocketbook 90x Pro

[Marius B. Kotsbak]

Device informations:

http://wiki.mobileread.com/wiki/PocketBook_901
http://wiki.mobileread.com/wiki/PocketBook_Pro_902
http://wiki.mobileread.com/wiki/PocketBook_Pro_903

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: calibre 0.8.8+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Mon Jan 23 10:27:27 2012
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, user)
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SourcePackage: calibre
UpgradeStatus: Upgraded to oneiric on 2011-10-17 (98 days ago)

[Marius B. Kotsbak (mariusko)]

Debug device detection logs for Pocketbook 903 Pro:

Version: 0.8.8
USB devices on system:
[['0x525', '0xa4a5', '0x324', 'PB', 'PocketBook', '3230204E6F76'],
 ['0x1d6b',
  '0x2',
  '0x300',
  'Linux 3.0.0-14-generic ehci_hcd',
  'EHCI Host Controller',
  '0000:00:1d.7'],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.3'],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.0'],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.1'],
 ['0x424', '0x2504', '0x1', '', '', ''],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.2'],
 ['0xa81', '0x205', '0x10', 'CHESEN', 'PS2 to USB Converter', '']]
Available plugins: ADAM ALEX ALURATEK_COLOR ANDROID ARCHOS7O AVANT AZBOOKA BAMBOOK
BLACKBERRY BOEYE_BDX BOEYE_BEX BOOQ BOOX COOL_ER CYBOOK DBOOK E52 E71X
EB511 EB600 EBK52 ECLICTO EDGE EEEREADER ELONEX ESLICK
FOLDER_DEVICE_FOR_CONFIG GEMEI GER2 HANLINV3 HANLINV5 ILIAD INVESBOOK
IPAPYRUS IREXDR1000 IREXDR800 IRIVER_STORY ITALICA JETBOOK
JETBOOK_MINI KINDLE KINDLE2 KINDLE_DX KOBO LIBREAIR LUMIREAD MENTOR
MOOVYBOOK N516 N770 N810 NEWSMY NEXTBOOK NOOK NOOK_COLOR NUUT2 ORIZON
PALMPRE PDNOVEL PDNOVEL_KOBO PICO POCKETBOOK301 POCKETBOOK360
POCKETBOOK360P POCKETBOOK602 POCKETBOOK701 PRS505 README S60 SHINEBOOK
SNE SOVOS SPECTRA STASH SUNSTECH_EB700 SWEEX TECLAST_K3 THEBOOK
TREKSTOR USER_DEFINED VELOCITYMICRO WEXLER

Looking for devices...
 (1317, 42149, 804, 'PB', 'PocketBook', '3230204E6F76')
  Detected possible device POCKETBOOK602

Devices possibly connected: PocketBook Pro 602/902 Device Interface,
Trying to open PocketBook Pro 602/902 Device Interface ... OK
Main memory: '/media/disk/'
Total space: (1966800896L, 999120896L, 0)

--------------------

Main memory is mounted at /media/Pocket903 and the /media/disk detected as main memory is really the memory card.

[Kovid Goyal (kovid)]

Removed from calibre. If you want to open a bug against calibre, you need to install the official calibre binary, not the Ubuntu package and post the debug output from that.

[Marius B. Kotsbak (mariusko)]

Installed the official binary 0.8.36 and the e-reader is still identified as Pocketbook 602. Debug info:

Version: 0.8.36
USB devices on system:
[['0x525', '0xa4a5', '0x324', 'PB', 'PocketBook', '3230204E6F76'],
 ['0xa5c',
  '0x200a',
  '0x1',
  'Broadcom',
  'Bluetooth USB Dongle',
  '2035B0000001'],
 ['0x409', '0x58', '0x100', 'NEC Corporation', 'USB2.0 Hub Controller', ''],
 ['0x1d6b',
  '0x2',
  '0x300',
  'Linux 3.0.0-14-generic ehci_hcd',
  'EHCI Host Controller',
  '0000:00:1d.7'],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.3'],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.0'],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.1'],
 ['0x41e', '0x4036', '0x100', 'Creative Labs', 'WebCam Live!', ''],
 ['0x46d', '0xc00c', '0x620', 'Logitech', 'USB Mouse', ''],
 ['0x5e3', '0x606', '0x702', '', 'USB2.0 Hub', ''],
 ['0x1d6b',
  '0x1',
  '0x300',
  'Linux 3.0.0-14-generic uhci_hcd',
  'UHCI Host Controller',
  '0000:00:1d.2']]
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...
 (1317, 42149, 804, 'PB', 'PocketBook', '3230204E6F76')
  Detected possible device POCKETBOOK602

Devices possibly connected: PocketBook Pro 602/902 Device Interface,
Trying to open PocketBook Pro 602/902 Device Interface ... OK
Main memory: '/media/disk/'
Total space: (1966800896, 999120896, 0)

and device/memory card is still wrong.

[Marius B. Kotsbak (mariusko)]

And here is the information under "Get information to setup the user defined device" for 903 Pro:

USB Vendor ID (in hex): 0x0x525
USB Product ID (in hex): 0x0xa4a5
USB Revision ID (in hex): 0x0x324

Copy these values to the clipboard, paste them into an editor, then enter them into the USER_DEVICE by customizing the device plugin in Preferences->Plugins. Remember to also enter the folders where you want the books to be put. You must restart calibre for your changes to take effect.

[Kovid Goyal (kovid)]

The pocketbook 602/901/902 and 903 share the same usb ids. Dont ask me why pocket book is stingy with usb ids. So they have the same driver in calibre. As for the main memory and card being swapped, calibre assumes that the drive with the lower disk number is the main memory. The PocketBook is presumably reporting that sd card as the device with the lower disk number. On linux that translates to the device node. You will find that the device node mounted at /media/disk is lexicographically before the device node mounted at /mdeia/PocketBook.

[Fabrice Coutadeur (fabricesp)]

As explained by upstream, this is normal. Closing as invalid.

[Marius B. Kotsbak (mariusko)]

It is probably the device and not the mount point that decides which is the main memory and SD card. I tried renaming the SD card label to "SDPOCKET903" so that they are mounted as:

/dev/sdd on /media/SDPOCKET903
/dev/sde on /media/Pocket903

Now "Pocket903" should be before "SDPOCKET903" so I guess it is the lower device "sdd" that decides this.

Anyway, even though they share the same USB ID and possibly the other USB properties, the device can be detected by the device label "Pocket903" and special handling added, so that the bug is in fact fixable.

My problem using Calibre with the device is that the main memory is probably hiding all system files so that I only see the documents added by Calibre on the SD card, and a lot of system files in the internal memory (using the SD card button).

Are there any workarounds to solve this? What about setting up udev rules with symlink with the correct ordering?

[Kovid Goyal (kovid)]

It is the device node, see where I said: "On linux that translates to the device node. You will find that the device node mounted at /media/disk is lexicographically before the device node mounted at /mdeia/PocketBook." That means /dev/sd*. I dont actually understand your problem. If you have system files showing up, just ignore them, they dont hurt you in any way.

[Marius B. Kotsbak (mariusko)]

Sure, the main problem is that my existing books on the SD card (under device memory in Calibre) does not show up., since they are not in the "books" directory (a workaround is to move all books in there, which can be smart anyway) .

I tried changing to "location_code": "A" in driveinfo.calibre on the SD card and let it be "main" in the main memory, but it did not have any effect.

[Kovid Goyal (kovid)]

Drive identification is based solely on device node, there's no other way to
influence it. Move your files to "books" that's the simplest solution.