Quote:
Originally Posted by TCDNV
Can you tell me anything from these results?
|
What you copied/pasted shows that your Kindle is auto-mounting just fine, and you have plenty of available space on the Kindle to store files. I have a "demo" directory because I am logged in as a user named "demo". You are logged in as a user named "tcd", which is why you have a "tcd" directory as opposed to my "demo" directory. All of this is perfectly normal and expected.
Your directory listing (the output of the "ls -al" command you ran) is different than mine. But that just indicates that we have different models of Kindle, or different firmware. The fact that you get "reasonable looking" output is all I was trying to establish. The output from your "mount" command indicates that you Kindle is mounted in "rw" mode (read-write), which is what you want.
In a nutshell: everything looks good on your computer/Kindle connection based on the output from your commands. Now, why your file manager is complaining about your Kindle is a bit of a mystery.
We can get more information if you do this:
Immediately after plugging your Kindle into the USB port of your computer, run the command:
Then cut-n-paste the output of that command into your reply to this thread.
On some Linux installations, you may get an error if you try to run the dmesg command. That error might look something like this:
Code:
$ dmesg | tail -100
dmesg: read kernel buffer failed: Operation not permitted
If you see this error, add the word "sudo" before dmesg, like this:
Code:
sudo dmesg | tail -100
Normally this will ask you for your password. This will be the password that you enter when you login as user name "tcd". Most likely, when you installed Mint, you told it to to automatically login user tcd without asking for a password. If you indeed installed it this way, I hope you remember the password you set for user tcd, despite you rarely needing to use it.
Anyway, hopefully you will be able to run the dmesg command and post it's output for us to look at. dmesg will dump out a LOT of text if you run it plain, which is why I have you piping the output to the tail command ... so we only see that last 100 lines of what dmesg dumps out. This is also why I said to run dmesg immediately after you plug in your Kindle, so you don't run other commands and pollute the dmesg output with other messages that come later than the Kindle being plugged in (we want the Kindle stuff to be in the most recent 100 lines that we asked for with "tail").