Forum › Forums › New users › New Users and General Questions › Kindle and Other NTFS partition is not detecting
Tagged: partition detection
- This topic has 27 replies, 3 voices, and was last updated Dec 31-7:46 am by fan1999.
-
AuthorPosts
-
December 23, 2018 at 5:37 am #14550Moderator
caprea
::First I would try to reboot without the device connected
After reboot connect the kindle and then open calibre and let only calibre try to mount it.
with dbus-launch calibre- This reply was modified 4 years, 4 months ago by caprea.
December 23, 2018 at 6:00 am #14552Moderator
caprea
December 23, 2018 at 6:24 am #14553Memberfan1999
December 23, 2018 at 6:46 am #14554Anonymous
::Probablyyou‘re missingthe wholeone part of Debian mtp stack.Further reading that might help:
https://forums.linuxmint.com/viewtopic.php?t=155634
https://www.mobileread.com/forums/showthread.php?t=173261
https://android.stackexchange.com/questions/38304/how-do-i-mount-a-kindle-fire-10-2-6-on-my-linux-computerDecember 24, 2018 at 6:13 am #14583Moderator
caprea
::The above libmtp are installed by default on antiX.
Furthermore you could install mtp-tools and jmtpfs. I’m not sure if this is the problem, though.
If I were in your shoes I also would try different usb-ports -cords , booting with the kindle, without and so on.
Calibre has kind of backed in mount- and mtp- mechanism, it also doesn’t like if the device is already mounted by another program and if there are two usb-devices like another phone.It maybe also worth a try to go into the settings of calibre and try the connect/share button, and choose connecting with a folder.
Even if this is not necessary for other OS like you wrote, on antiX it may is
It also seems in time to be neccesary to open calibre with dbus-launch calibre.I still hope there will be someone else with a kindle.
December 27, 2018 at 6:38 am #14646Memberfan1999
::Output :
Even Calibre and machine is not detecting the Kindleroot@shiva:~# sudo apt-get install libmtp-common
Reading package lists… Done
Building dependency tree
Reading state information… Done
libmtp-common is already the newest version (1.1.13-1).
libmtp-common set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@shiva:~# sudo apt-get install python=pymtp
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Version ‘pymtp’ for ‘python’ was not found
root@shiva:~# sudo apt-get install python-pymtp
Reading package lists… Done
Building dependency tree
Reading state information… Done
Recommended packages:
python-id3
The following NEW packages will be installed:
python-pymtp
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.0 kB of archives.
After this operation, 64.5 kB of additional disk space will be used.
Get:1 http://mirror.0x.sg/debian stretch/main amd64 python-pymtp all 0.0.6-1.1 [13.0 kB]
Fetched 13.0 kB in 0s (14.9 kB/s)
Selecting previously unselected package python-pymtp.
(Reading database … 182534 files and directories currently installed.)
Preparing to unpack …/python-pymtp_0.0.6-1.1_all.deb …
Unpacking python-pymtp (0.0.6-1.1) …
Setting up python-pymtp (0.0.6-1.1) …
root@shiva:~# sudo apt-get install mtp-tools
Reading package lists… Done
Building dependency tree
Reading state information… Done
mtp-tools is already the newest version (1.1.13-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@shiva:~# sudo apt-get install libmtp9
Reading package lists… Done
Building dependency tree
Reading state information… Done
libmtp9 is already the newest version (1.1.13-1).
libmtp9 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@shiva:~# sudo apt-get install libmtp-doc
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following NEW packages will be installed:
libmtp-doc
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 375 kB of archives.
After this operation, 3,542 kB of additional disk space will be used.
Get:1 http://mirror.0x.sg/debian stretch/main amd64 libmtp-doc all 1.1.13-1 [375 kB]
Fetched 375 kB in 3s (115 kB/s)
Selecting previously unselected package libmtp-doc.
(Reading database … 182548 files and directories currently installed.)
Preparing to unpack …/libmtp-doc_1.1.13-1_all.deb …
Unpacking libmtp-doc (1.1.13-1) …
Processing triggers for man-db (2.7.6.1-2) …
Setting up libmtp-doc (1.1.13-1) …
root@shiva:~# sudo apt-get install libmtp-dev
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following additional packages will be installed:
libusb-1.0-0-dev
Recommended packages:
libusb-1.0-doc
The following NEW packages will be installed:
libmtp-dev libusb-1.0-0-dev
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 123 kB of archives.
After this operation, 384 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirror.0x.sg/debian stretch/main amd64 libusb-1.0-0-dev amd64 2:1.0.21-1 [72.7 kB]
Get:2 http://mirror.0x.sg/debian stretch/main amd64 libmtp-dev amd64 1.1.13-1 [50.6 kB]
Fetched 123 kB in 0s (156 kB/s)
Selecting previously unselected package libusb-1.0-0-dev:amd64.
(Reading database … 182764 files and directories currently installed.)
Preparing to unpack …/libusb-1.0-0-dev_2%3a1.0.21-1_amd64.deb …
Unpacking libusb-1.0-0-dev:amd64 (2:1.0.21-1) …
Selecting previously unselected package libmtp-dev:amd64.
Preparing to unpack …/libmtp-dev_1.1.13-1_amd64.deb …
Unpacking libmtp-dev:amd64 (1.1.13-1) …
Setting up libusb-1.0-0-dev:amd64 (2:1.0.21-1) …
Setting up libmtp-dev:amd64 (1.1.13-1) …
root@shiva:~# sudo apt-get install libmtp-dbg
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following NEW packages will be installed:
libmtp-dbg
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 291 kB of archives.
After this operation, 328 kB of additional disk space will be used.
Get:1 http://mirror.0x.sg/debian stretch/main amd64 libmtp-dbg amd64 1.1.13-1 [291 kB]
Fetched 291 kB in 1s (166 kB/s)
Selecting previously unselected package libmtp-dbg:amd64.
(Reading database … 182781 files and directories currently installed.)
Preparing to unpack …/libmtp-dbg_1.1.13-1_amd64.deb …
Unpacking libmtp-dbg:amd64 (1.1.13-1) …
Setting up libmtp-dbg:amd64 (1.1.13-1) …
root@shiva:~# sudo apt-get install libmtp-common
Reading package lists… Done
Building dependency tree
Reading state information… Done
libmtp-common is already the newest version (1.1.13-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@shiva:~# gmtp
Detect: No raw devices found.December 27, 2018 at 8:00 am #14648Moderator
caprea
::OK. You installed a lot, nobody said but anyway not jmtpfs
sudo apt-get install jmtpfsPlease with your kindle connected post the output of
sudo mtp-detectand
lsusbAlso did you try to go into the settings of calibre and try the connect/share button, and choose connecting with a folder ?Like I said above calibre does not like , if another program already mounted your kindle, so do this directly after booting, without trying anything else for connecting to your kindle.
Before posting the output from the terminal, you could do us a favor, and click on the code button, before and after the output. This will make it much easier to read.
December 27, 2018 at 9:07 am #14650Anonymous
::I’ve no idea what spooks here but, there may be many different (and even trivial) reasons when it doesn’t work.
Examples:
1. jmtpfs –> fs == File System
2. “Go to preferences->plugins and re-enable the Kindle device plugins.”
3. “Use the official calibre binary and not the debian package. Make sure you have a working install of udev and dbus on your system.”
4. “… couldn’t recognise my Kindle Fire HD device, but as soon as I replaced the USB cable with another generic one (might have been my original white Kindle Paperwhite one) it worked fine…”
December 28, 2018 at 1:06 am #14669Memberfan1999
::root@shiva:~# mtp-detect
libmtp version: 1.1.13Listing raw device(s)
No raw devices found.
root@shiva:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b3aa Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 0489:e062 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@shiva:~# sudo mtp-detect
libmtp version: 1.1.13Listing raw device(s)
No raw devices found.December 28, 2018 at 7:19 am #14679Anonymous
::Bus 003 Device 002: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite
At least it got recognized from the system.
Did you try all from #14650?
December 29, 2018 at 7:34 am #14714Memberfan1999
::Did you try all from #14650?
Yes tried not mounted after that also.the same issue persists
December 29, 2018 at 8:07 am #14715Moderator
caprea
::This is a usable How To , worth a try.
https://ubuntuforums.org/showthread.php?t=2226702It’s for phones but among the users who have had success are also kindle owners
If you read through the posts you’ll see that some only had to do the first two or four steps, so please do it step by step and try to see if it’s enough already.
In step 4 you will be instructed to edit the /lib/udev/rules.d/69-mtp.rules,
On antiX you need to edit the /lib/udev/rules.d/69-libmtp.rules instead.In step 5, you will probably have to create a file /etc/udev/rules.d/51-android.rules.
But maybe the first steps are enough anyway.If you stumble at any point, feel free to ask.
Even if you succeed with the How To, you’re probably gonna have to make the changes again, when libmtp get’s updated.
It’s likely possible to work around that, by copying files to another place, though.First of all fingers crossed.December 31, 2018 at 7:46 am #14854Memberfan1999
::My badness its not working
root@shiva:~# mtp-detect
libmtp version: 1.1.13Listing raw device(s)
No raw devices found.
shiva@shiva:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b3aa Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 0489:e062 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -
AuthorPosts
- You must be logged in to reply to this topic.