| 1 |
This has happened to me with a few different external devices (USB |
| 2 |
keys, etc) on multiple computers, so it seems to be a generic problem. |
| 3 |
Right now, I have an HTC Desire HD with the smae problem... |
| 4 |
|
| 5 |
* Either hit {CTRL}{ALT}{F12} to switch to tty12 or else (as root) execute |
| 6 |
"tail -f /var/log/messages" |
| 7 |
|
| 8 |
* Attach a device to the PC's USB port, and you'll see a bunch of stuff |
| 9 |
spewing out. In my case, the last 3 lines are... |
| 10 |
|
| 11 |
Oct 7 20:50:23 localhost kernel: [114416.426175] scsi 26:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2 |
| 12 |
Oct 7 20:50:23 localhost kernel: [114416.426336] sd 26:0:0:0: Attached scsi generic sg3 type 0 |
| 13 |
Oct 7 20:50:23 localhost kernel: [114416.432119] sd 26:0:0:0: [sdc] Attached SCSI removable disk |
| 14 |
|
| 15 |
* If I try mounting /dev/sdc1 (either as ordinary user or root), it's |
| 16 |
not found |
| 17 |
* "fdisk -l" doesn't even see /dev/sdc |
| 18 |
|
| 19 |
***BUT*** |
| 20 |
|
| 21 |
* as root "fdisk /dev/sdc", and quit immediately |
| 22 |
|
| 23 |
and now "fdisk -l" sees /dev/sdc, and regular user can mount it. Has |
| 24 |
anyone seen this before... and more importantly, found a solution? |
| 25 |
|
| 26 |
-- |
| 27 |
Walter Dnes <waltdnes@××××××××.org> |
Archives