Messages in this thread | | | Date | Fri, 30 Jun 2006 15:17:13 +0200 | From | DervishD <> | Subject | usb-storage device wrongly seen as "write protect is on" |
| |
Hi all :)
I'm having a problem with an usb-storage device (namely a Inovix IMP65 MP3 player): when I plug it and I try to mount it, the sd_mod driver sees it write protected, so I cannot mount it read-write.
If I remount it as read-write (as root, of course), I have success and I can use the device normally, being able to write to it without problems. If, instead, I manually unload sd_mod and load it again, then this time the device is NOT seen as write protected (the sd_mod driver says that "write protect is off").
All this happens using kernel 2.4.32. If using Ubuntu kernel 2.6.15, the same problem happens, but Ubuntu probes the device twice and the second time the "write protect is off" message appears. It mounts the device "ro", anyway. I've tested with two different USB ports, an ALi 2.0 (driver EHCI+OHCI) and a builtin VIA686 (driver UHCI) with the same results.
If I plug the device with the write protect switch on (that is, the device IS *really* write protected), the sd_mod driver sees it as "write protect is off" and I can mount it "rw"... but I cannot write anything!
The same device works OK in WinXP without any driver (well, with the default USB disk driver), so I'm not sure if the problem is on the device (in fact, it works OK after remounting "rw" by hand or manually reloading sd_mod) or in the kernel drivers (which I find very unlikely, since similar Inovix players work as-is).
If you need more information, feel free to ask, and if this is a known issue I will very happy if you could point me to the appropriate place. I've googled a bit with no success...
Thanks a lot in advance.
Raúl Núñez de Arenas Coronado
-- Linux Registered User 88736 | http://www.dervishd.net http://www.pleyades.net & http://www.gotesdelluna.net It's my PC and I'll cry if I want to... RAmen! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |