Dreampi can be touchy, normal?

[jay_red]

I got my dreampi working yesterday, using a Raspberry 2 B board, and a "TRENDnet" 56k modem. When it works, it has no issues, but it seems sometimes I need to reboot the pi a couple times before the setup works. I can tell when it is going to work based on the lights on the modem, if the Link and Data lights are lit after it loads up, then it will work normally, if only the data light is lit, it will not answer the call and then I need to reboot it.

Once it is working, I can end calls and redial and it will work just fine. Today it took 3 tries before it would connect, and I am just wondering if this is normal behavior? I am running dreampi 1.2

[pcwzrd13]

It works consistently every time for me. I'm using a different modem and an original model B Raspberry Pi so there are some differences there. I would think it would have to be something to do with one of those two since everything would be identical on the software side. I will ask Luke to chime in one this and see what he thinks.

[-drez01-]

I had the same issue with a micro SD card. Sometimes it would say it was in read only mode and would not boot the script even if the lock switch was totally in the upright position. I switched to a full sized SD card and have not had an issue since. Seems the adapter or lock switch was touchy or faulty.

[jay_red]

I had the same issue with a micro SD card. Sometimes it would say it was in read only mode and would not boot the script even if the lock switch was totally in the upright position. I switched to a full sized SD card and have not had an issue since. Seems the adapter lock switch was touchy or faulty

The model 2 uses a micro sd slot so there is no lock switch on the card.

[pcwzrd13]

Did you look to see what it says on the screen when it's not working? I'm thinking it may be taking a long time to get an IP address from your router. It won't continue to boot until it gets an IP.

[jay_red]

Dreampi display is the same either way.

[pcwzrd13]

Dreampi display is the same either way.

I actually just found out that it will eventually give up on getting an IP. Next time you have the issue, see if the DHCPREQUEST output looks something like this and says "No DHCPOFFERS Received". If it does, then that means you're not getting an IP from your router.