blk_update_request: I/O error, dev sdc, sector 5518040 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 blk_update_request: I/O error, dev sdc, sector 5517968 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 blk_update_request: I/O error, dev sdc, sector 5517880 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 blk_update_request: I/O error, dev sdc, sector 5517816 op 0x0:(READ) flags 0x80000 phys_seg 1 prio class 0 blk_update_request: I/O error, dev sdc, sector 5517784 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 sd 4:0:0:0: tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s usb 3-10: USB disconnect, device number 2 usb usb3-port10: disabled by hub (EMI?), re-enabling. Lot of PAM messages that have no links to our problems. sd 4:0:0:0: Attached SCSI removable disk sd 4:0:0:0: Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: Power-on or device reset occurred usbcore: registered new interface driver uas usbcore: registered new interface driver usb-storage usb-storage 3-10:1.0: USB Mass Storage device detected usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-10: New USB device found, idVendor=2237, idProduct=4223, bcdDevice= 1.10 usb 3-10: new high-speed USB device number 2 using xhci_hcd Here are the lsusb and dmesg output in the second case: when the reader is visible from the computer: I suspect an hardware problem with my reader. Looking at dmesg I see some error message. However any attempt to access it close the connection from the computer side: the device is kind of "ejected". If I reboot the computer with the Reader plugged, I can see it with Thunar and Calibre detect the device. The reader is not mounted: it's not appearing in Thunar, Calibre can't see it, no mounting point corresponding appear in mount output. However in most of the case nothing happen. dmesg show a connection on a USB port with no error message. From the computer side now the lsusb command see perfectly the Reader, its number. When I plug the reader via the USB cable, the reader ask to be connected (or not) with the computer.I accept and then the reader show the message "you are connected blablabla". In fact both OS are up-to-date (Kobo OS on the reader and Arch on the computer). I suspect an hardware problem on the reader. My problem is to connect the reader to my computer. Well for reading book and so it's works as expected. Make sure the latest fixes are installed.I have a Kobo EPub reader that works perfectly. But, MS have released updates since that fix this. And this was the problem with Window 10 Anniversary Edition. If not, there is nothing calibre can do because it is relying on OS functions to access the device. Hi, I am using a Kobo Aura H2O and using calibre and after updating my windows 10 to aniversary edition, calibre cannot read my database in sd card in my kobo and showed this error message in calibreĮRROR: Error: Error communicating with deviceĬantOpenError: unable to open database fileįile "site-packages\calibre\gui2\device.py", line 88, in runįile "site-packages\calibre\gui2\device.py", line 506, in _booksįile "site-packages\calibre\devices\kobo\driver.py", line 1694, in booksįile "site-packages\calibre\devices\kobo\driver.py", line 161, in device_database_connectionĬantOpenError: CantOpenError: unable to open database fileĬan Windows see the device properly? By that I mean does it assign a drive letter and let you browse the drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |