View Single Post
Old 08-25-2017, 10:25 PM   #17
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,491
Karma: 28005164
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Given that this device line is discontinued, I'm not particualrly interested in spending time on it myself. But I'm happy to provide guidance on how to fix it yourself. The problem is likely the read-only launcher partition being detected as the main memory. On windows this is filtered by windows_filter_pnp_id

Linux has no equivalent mechanism, that I am aware of, anyway.

The relevant function you will need to play with is find_device_nodes() in usbms/device.py

WINDOWS_MAIN_MEM is a red herring, it is not used for anything in modern calibre.
kovidgoyal is online now   Reply With Quote