Hi,
sorry that I omitted that. Yes, the Kobotouch driver is involved whenever I use calibre to copy books to the reader.
Here is what I have done today:
So, if I copy a very low number of books (1 in my experiments), nothing untoward happens. As soon as I copy a relevant number of books, an active KSM leads to a corrupted database.
If I copy a valid database file using the usb connection under KSM and then reboot without KSM, everything works fine. I have to trigger a scan with Nickel by plugging the reader in though to recognize new books copied to the device. Don't know how to do it directly.
If I copy 100 books under KSM and then again reboot without KSM to let Nickel scan the new books, it works fine as well (with the limitation of Nickel recognizing the new books only after another cycle of plugging and unplugging the reader).
Now, it seems that the process of copying the data itself works fine with KSM enabled, in KSM and in Nickel.
The subsequent scan of new books and the modification of the database does not work correctly with KSM enabled.
Important: Without KSM I can copy large numbers of books onto the reader without problems.
The next experiment could be to install fmon directly. Any recommendations about which package to use? And should I uninstall KSM first or is it enough to have it configured as never to run?
This way I could find out whether fmon works without problems. Earlier experiments showed already that KSM leads to problems even with fmon disabled.
Any other ideas what I should test? And how could I determine the KSM problem in more detail (without first having to understand the source)?
Cheers, Joe