View Single Post
Posts: 12 | Thanked: 4 times | Joined on Nov 2009
#281
Originally Posted by too View Post
Weird problem....

g_nokia is always the "first" module for usb connection that is
loaded at boot. g_file_storage is loaded if user chooses file
storage when usb cable is plugged...

... which brings to first question: does file storage mode work
as expected ?

Second thing is to try first select g_ether, then plug usb cable
and when pc suite/mass storage requester appears, tap
outside of the dialog and see if it crashes again.

I just tested against linux: first chose g_ether. Then configured
usb0 interface, plugged cable and chose g_nokia (which doesn't
do anything when g_ether is chosen). No problem with connection.

Software version (see product information in settings window)
3.2010.02-8

We also test reqularly with windows ... and I just asked my
colleaque about crashing -- she tested yesterday with windows
and did not get a crash.

I wonder what kind of message from usb could crash the
device (or is it about signal levels that comes via the port)...
You could also try using another usb port and/or another
machine to lessen the change that there is some problem
with hardware ?

Also, what is your windows system and anything you can
tell how it sees the usb hardware (driver info). That information
could be useful.
Hi,
it's been some time since I have discovered this issue and have been fiddling with the phone + notebook a bit. The original issue is described here:
http://talk.maemo.org/showpost.php?p...&postcount=214

The results of my experiments are following:
1. Yes, file storage mode and pc suite mode works both well, I have not noticed single trouble.
2. When I connect after loading g_ether, it takes a second longer, but the device crashes the same way.
3. I have tried other USB ports on the same machine - same restarts always.
4. I have tried different computer also with windows and it works, loading g_ether doesn't trigger restart. So there is probably nothing wrong with my N900.
5. I managed to corrupt the "Linux USB Ethernet Gadget/RNDIS" device created on my computer the way that windows could not load/enable the device properly when I connect the phone with g_ether loaded. In that case the device appears in the device list marked with yellow exclamation mark saying that the registry settings are corrupted. When done this N900 in half of the occasions does not restart however message pops-up on N900 side saying that the charging is not possible due to insufficient power level and in the other half of occasions the device restarts.

Update: I managed to connect via externally powered USB hub. So there must be something wrong with power levels in my computer's USB ports. It somehow interferes with the charging over USB and causes N900 to restart.

Update 2: OK, so the powered USB hub was just a coincidence. I finally figured out what is causing the trouble. Not a HW / USB ports problem .. it is my VPN software (AT&T network client) what is causing this. Whenever I am connected with this VPN software and try to connect N900 via USB to the computer, when I load g_ether it causes N900 to restart. So obviously there must be some kind of bug in g_ether which triggers the restart. When I load g_ether Windows is via plug&play enabling the RNDIS gadget device, but there is this virtual network adapter (AGN virtual network adapter) used by the VPN SW and if it is enabled at that time something goes nasty and probably the sequence of USB commands is not as expected by g_ether .. that's what I am thinking. The virtual adapter is some kind of a filter network device which sits in between the network adapter and the windows TCP/IP stack. When I am connected with g_ether and then start the VPN SW, this virtual adapter is becoming enabled and this causes immediate restart of N900.

I'm posting here since the original questions went here though it is not MADDE / MAD Developer related - that is obvious now. Any hints / suggestions to help understand the root cause are welcome :-)

Thanks for your hints!

Last edited by flyskyhigh; 2010-06-30 at 08:27.