summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-discuss/attachments/20111130/29fa27a1
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-discuss/attachments/20111130/29fa27a1')
-rw-r--r--zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment-0001.html43
-rw-r--r--zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment.html43
2 files changed, 86 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment-0001.html b/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment-0001.html
new file mode 100644
index 000000000..56e785a23
--- /dev/null
+++ b/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment-0001.html
@@ -0,0 +1,43 @@
+<br><br><div class="gmail_quote">On Wed, Nov 30, 2011 at 2:14 PM, Renaud (Ron) Olgiati <span dir="ltr">&lt;<a href="mailto:renaud@olgiati-in-paraguay.org">renaud@olgiati-in-paraguay.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
+On Wednesday 30 Nov 2011 09:39 my mailbox was graced by a message from<br>
+<div class="im">Alejandro López who wrote:<br>
+<br>
+&gt; &gt; Since last night the automounting through USB of a Kindle on my desktop<br>
+&gt; &gt; (mageia 1/KDE) mounts it as Read Only, making it impossible to load books<br>
+&gt; &gt; from the computer.<br>
+<br>
+</div><div class="im"> &gt; This usually happens when the filesystem is corrupted. Try a fsck on it.<br>
+<br>
+</div>root@localhost:/home/ron # fsck /dev/sdc1<br>
+Reclaimed 88 unused clusters (720896 bytes).<br>
+Free cluster summary wrong (352493 vs. really 352666)<br>
+1) Correct<br>
+2) Don&#39;t correct<br>
+? 1<br>
+Leaving file system unchanged.<br>
+/dev/sdc1: 481 files, 47608/400274 clusters<br>
+<br></blockquote><div> </div><div>Why did fsck leave the file system unchanged if you said 1 (Correct)? Did it somehow misunderstood what you wanted? You could maybe try with the option -p to automatically fix any problem it finds, and avoid the question. Unluckily I have no other idea.<br>
+<br>Alejandro.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">root@localhost:/home/ron # dmesg<br>
+2:1:1: usb_set_interface failed<br>
+usb 1-4.2: new high speed USB device using ehci_hcd and address 25<br>
+usb 1-4.2: New USB device found, idVendor=1949, idProduct=0004<br>
+usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br>
+usb 1-4.2: Product: Amazon Kindle<br>
+usb 1-4.2: Manufacturer: Amazon<br>
+usb 1-4.2: SerialNumber: B008A0A012250P0E<br>
+scsi18 : usb-storage 1-4.2:1.0<br>
+2:2:1: usb_set_interface failed<br>
+scsi 18:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2<br>
+sd 18:0:0:0: Attached scsi generic sg3 type 0<br>
+sd 18:0:0:0: [sdc] 6410688 512-byte logical blocks: (3.28 GB/3.05 GiB)<br>
+sd 18:0:0:0: [sdc] Write Protect is off<br>
+sd 18:0:0:0: [sdc] Mode Sense: 0f 00 00 00<br>
+sd 18:0:0:0: [sdc] Assuming drive cache: write through<br>
+sd 18:0:0:0: [sdc] Assuming drive cache: write through<br>
+ sdc: sdc1<br>
+sd 18:0:0:0: [sdc] Assuming drive cache: write through<br>
+sd 18:0:0:0: [sdc] Attached SCSI removable disk<br>
+2:1:1: usb_set_interface failed<br>
+2:2:1: usb_set_interface failed<br>
+<div class="im"><br></div></blockquote><div><br>Do you have any old log file to verify whether this &quot;usb_set_interface failed&quot; message also happening when your kindle was correctly mounted in read-write mode?<br>
+<br> <br></div></div><br>
diff --git a/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment.html b/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment.html
new file mode 100644
index 000000000..56e785a23
--- /dev/null
+++ b/zarb-ml/mageia-discuss/attachments/20111130/29fa27a1/attachment.html
@@ -0,0 +1,43 @@
+<br><br><div class="gmail_quote">On Wed, Nov 30, 2011 at 2:14 PM, Renaud (Ron) Olgiati <span dir="ltr">&lt;<a href="mailto:renaud@olgiati-in-paraguay.org">renaud@olgiati-in-paraguay.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
+On Wednesday 30 Nov 2011 09:39 my mailbox was graced by a message from<br>
+<div class="im">Alejandro López who wrote:<br>
+<br>
+&gt; &gt; Since last night the automounting through USB of a Kindle on my desktop<br>
+&gt; &gt; (mageia 1/KDE) mounts it as Read Only, making it impossible to load books<br>
+&gt; &gt; from the computer.<br>
+<br>
+</div><div class="im"> &gt; This usually happens when the filesystem is corrupted. Try a fsck on it.<br>
+<br>
+</div>root@localhost:/home/ron # fsck /dev/sdc1<br>
+Reclaimed 88 unused clusters (720896 bytes).<br>
+Free cluster summary wrong (352493 vs. really 352666)<br>
+1) Correct<br>
+2) Don&#39;t correct<br>
+? 1<br>
+Leaving file system unchanged.<br>
+/dev/sdc1: 481 files, 47608/400274 clusters<br>
+<br></blockquote><div> </div><div>Why did fsck leave the file system unchanged if you said 1 (Correct)? Did it somehow misunderstood what you wanted? You could maybe try with the option -p to automatically fix any problem it finds, and avoid the question. Unluckily I have no other idea.<br>
+<br>Alejandro.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">root@localhost:/home/ron # dmesg<br>
+2:1:1: usb_set_interface failed<br>
+usb 1-4.2: new high speed USB device using ehci_hcd and address 25<br>
+usb 1-4.2: New USB device found, idVendor=1949, idProduct=0004<br>
+usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br>
+usb 1-4.2: Product: Amazon Kindle<br>
+usb 1-4.2: Manufacturer: Amazon<br>
+usb 1-4.2: SerialNumber: B008A0A012250P0E<br>
+scsi18 : usb-storage 1-4.2:1.0<br>
+2:2:1: usb_set_interface failed<br>
+scsi 18:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2<br>
+sd 18:0:0:0: Attached scsi generic sg3 type 0<br>
+sd 18:0:0:0: [sdc] 6410688 512-byte logical blocks: (3.28 GB/3.05 GiB)<br>
+sd 18:0:0:0: [sdc] Write Protect is off<br>
+sd 18:0:0:0: [sdc] Mode Sense: 0f 00 00 00<br>
+sd 18:0:0:0: [sdc] Assuming drive cache: write through<br>
+sd 18:0:0:0: [sdc] Assuming drive cache: write through<br>
+ sdc: sdc1<br>
+sd 18:0:0:0: [sdc] Assuming drive cache: write through<br>
+sd 18:0:0:0: [sdc] Attached SCSI removable disk<br>
+2:1:1: usb_set_interface failed<br>
+2:2:1: usb_set_interface failed<br>
+<div class="im"><br></div></blockquote><div><br>Do you have any old log file to verify whether this &quot;usb_set_interface failed&quot; message also happening when your kindle was correctly mounted in read-write mode?<br>
+<br> <br></div></div><br>