[usonic]

or use a different distro, there are many to choose from that uses the dwc2 (USB 2.0) driver.

Which are those exactly? Debian or Redhat based are most preferable.
And supported by Rasberry PI 1 (for example Ubuntu is not).

[JasonH]

or use a different distro, there are many to choose from that uses the dwc2 (USB 2.0) driver.

Which are those exactly? Debian or Redhat based are most preferable.
And supported by Rasberry PI 1 (for example Ubuntu is not).

I would love to know as well. Even for RasperrbyPi2's. For what it is worth I have just noticed that Ubuntu snappy just looks like it has been refreshed for the Pi so I guess I should summon up the fortitude and experiment with that to see if it is any better? I am not sure what state plain "debian jessie" vs "raspberian jessie" differ for the pi as well.

In the end for my situation I just still use the standard usb-modeswitch which is installed in rasperian wheezy. (I haven't yet moved to Jessie since there are problems with Chromium on jessie. (https://www.raspberrypi.org/forums/view ... 9&p=751381, http://conoroneill.net/running-the-late ... erry-pi-2/ but apparently there is no hardware acceleration of Chromium with that...) In any case I should try usb-modeswitch with rasperian jessie but I haven't yet (it is on my list of things to do)

Instead to work around the problems I had with usb-modeswitch I used the method given here: http://raspberrypi.stackexchange.com/qu ... g-a-script

Then I have lots of watchdog scripts running which see if the modem didn't come up, and if it didn't then the pi is rebooted. I wish I could get this more stable but I have thrown oodles of time at it. I am kind of stunned it was so difficult. With the whole IOT and using Pi's as development embedded devices to communicate I would have imagined there would be some rock-solid way to basically use a 3G modem / communications somehow. I am yet to find it if there is and would love to know if I have missed something simple...

Thanks,
Jason

[Josh]

The problem can also be an insufficient power supply of USB devices on the Pi. There were reports giving hints that using a powered USB hub improved reliability.

http://www.draisberghof.de/usb_modeswit ... 158#p15158

[JasonH]

The problem can also be an insufficient power supply of USB devices on the Pi. There were reports giving hints that using a powered USB hub improved reliability.

http://www.draisberghof.de/usb_modeswit ... 158#p15158

Thanks. Actually initially we thought this was a / the problem as well. It turns out during the ongoing development of our units, that for a while now we have had a custom power supply in our units which have the included raspberry Pi's. Thus now we can control the power levels quite accurately. This has not solved the "intermittent-ness" of problem for us.

Josh, do you happen to know if there are changes in raspberian Jessie, re the USB handling / usb_modeswitch?

Thanks!
Jason