device-owners Digest, Vol 5, Issue 21

[Daniel Hembree]

I was having the same sort of problems. Following the most recent 
advice, wiping the kernel and the rootfs, I installed the latest uImage 
and the 1117 qtopia  rootfs. I believe I got that at 
http://buildhost.automated.it/CM2007.2/?M=D, but I can't seem to connect 
to that site today to confirm. I had to connect to the device with ssh 
and issue an " /usr/sbin/alsactl -f /etc/gsmhandset.state restore ". 
After that I was able to get and place calls.  I am still unable to get 
openmoko's rootfs to connect with the network.

> Richard Reichenbacher wrote:
>   
>> 7150 wrote:
>>     
>>> Richard Reichenbacher wrote:
>>>  
>>>       
>>>> 7150 wrote:
>>>>    
>>>>         
>>>>> I seem to have a problem.
>>>>>
>>>>> I have tried several images lately and none will run -- including
>>>>> Qtopia.
>>>>>
>>>>> I've tried the factory reset.
>>>>>
>>>>> The machine boots and stops at the openmoko splash screen with a neat
>>>>> little "Please wait..." message.
>>>>>
>>>>> Can someone point me in the correct direction.
>>>>>
>>>>> Thanks!!
>>>>>           
>>>> <snip>
>>>>         
>
> Hello Richard and Clare and group.
>
> I tried the new Qtopia image (as of 11/16). It starts nicely, although
> it does not make or receive calls.  I think I need to have a filing
> system with builds that I know will do one thing or another. I'm
> serious. That way I can be a bit more efficient as I try to get my "sea
> legs" on this device. It is good to see that my issues are not all still
> "pilot error".
>
> I wonder if it would be good to have a "tester" wiki page (or group of
> such pages) where the functional status of various images and builds,
> OpenMoko, Qtopia, Android, whatever -- with links to those specific
> builds -- could be described in a uniform way. One could try a build and
> record the pass-fail results af a set of simple and standard tests in a
> tabular format. Perhaps that would be a way in which those less able to
> write wizardly code could help advance projects? What 5-10 things would
> wizardly developers like tested by a larger group?
>
> 1. Starts and runs
> 2. Makes call
> 3. Receives a call
> 4. Sound works
> 5. Sound controls work
> 6. Power management works
> 7. You get the idea
>
> It might also reduce the number of messages like mine on the list. I
> don't know if I get shot at for creating such a wiki page without asking.
>
> George
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 17 Nov 2007 17:37:00 +0000
> From: Andy Powell <openmoko at automated.it>
> Subject: Re: Please wait...
> To: device-owners at lists.openmoko.org
> Message-ID: <200711171737.01307.openmoko at automated.it>
> Content-Type: text/plain;  charset="iso-8859-1"
>
> On Saturday 17 November 2007 03:44, Lorn Potter wrote:
>
>   
>> Qtopia should timeout after 2 minutes, so you can access the
>> applications . We have had problems with some sim cards, and of course
>> usim cards. We just fixed a few things on Friday and it seems those sims
>> we were having problems with, now work more reliably.
>>
>>     
>
> I dunno about this. I've not had a good build since before 15th - either non 
> booting (incomplete boot) or booting to where it searches for the network / 
> sim where it sits for(;;)
>
> Builds prior to this worked fine with my sim.
>
> Andy / ScaredyCat
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 17 Nov 2007 19:31:13 +0000
> From: "andy selby" <andyfrommk at googlemail.com>
> Subject: Re: Please wait...
> To: device-owners at lists.openmoko.org
> Message-ID:
> 	<27183a390711171131p33eaa273y47ce7b1ff5d7708a at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 17/11/2007, 7150 <linux.1 at litenverden.com> wrote:
>   
>> The machine boots and stops at the openmoko splash screen with a neat
>> little "Please wait..." message.
>>     
>
> Have you tried erasing the rootfs and kernel?
> What I think is happening is the neo is loading the rootfs and reading
> past the end of the installed image then it gets confused as it is
> then reading the end of a previously installed rootfs.
> Go into u-boot on your neo and type on your pc
> screen /dev/ttyACM0
> then type
> nand erase rootfs
> nand erase kernel
>
>
>
> ------------------------------
>
> _______________________________________________
> device-owners mailing list
> device-owners at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/device-owners
>
>
> End of device-owners Digest, Vol 5, Issue 21
> ********************************************
>
>