Quote:
|
Originally Posted by rivviepop
Every now and then when I plug in my Pearl, it seems to not present itself to the system as a mass storage device; if I pull out the cable and wait a few seconds, then plug it back in it usually starts working.
Obviously it can be a kernel/usb bug but I really don't know but I can share the following observations:
- on FC6 if the device is set to Yes, it happens a lot more. If set to Prompt, it almost never happens
- on FC5 it seems to happen almost all the time, but every now and again it'll work as expected on first-plug
I don't think it's bcharge related as I don't even have that installed on the FC5 workstation (at work). My only thought is if it's in Prompt mode (regarding FC6) that might slow down the process enough that the kernel can catch up or whatnot.
Happening to anyone else, you folks on Ubuntu and SuSE?
|
I sometimes get the same thing.
I really think they've changed they way they (RIM) handle USB connections. Back when I had a 7100, I could easily connect that through VMWare and run App loader, sync, backups, etc. with no problem. Can't do it with the Pearl. The only thing I have managed to do is occasionally connect as a mass storage device, and run into the same symptoms you do, on both Ubuntu and SUSE (well, the SUSE laptop was stolen, so now it's just Ubuntu
) I'm sure it has something to do with the fact that you can now connect as mass storage device, whereas pre-Pearl days you couldn't.
R.
==