Usable builds in the 5xx series on B2s?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Usable builds in the 5xx series on B2s?

Martin Langhoff
Aside from the memory-hogging notes -- are recent 5xx builds booting
for people with B2s? I've updated to the latest firmware and tested
with 539 and 540 (ext3) and they both hung during the boot process.
Not sure if it's some subtle PEBKAC at my end, or if they are just not
booting on B2s.

Anyone with a B2 working with recent builds can say?

cheers,.



m

Reply | Threaded
Open this post in threaded view
|

Usable builds in the 5xx series on B2s?

Noah Kantrowitz-2
I've got 539/Q2C18 on a B2 staring at me right now. It helps to throw  
a swapfile at it (mine is on a USB stick).

--Noah

On Aug 1, 2007, at 10:37 PM, Martin Langhoff wrote:

> Aside from the memory-hogging notes -- are recent 5xx builds booting
> for people with B2s? I've updated to the latest firmware and tested
> with 539 and 540 (ext3) and they both hung during the boot process.
> Not sure if it's some subtle PEBKAC at my end, or if they are just not
> booting on B2s.
>
> Anyone with a B2 working with recent builds can say?
>
> cheers,.
>
>
>
> m
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>


Reply | Threaded
Open this post in threaded view
|

Usable builds in the 5xx series on B2s?

Martin Langhoff
On 8/2/07, Noah Kantrowitz <kantrn at rpi.edu> wrote:
> I've got 539/Q2C18 on a B2 staring at me right now. It helps to throw
> a swapfile at it (mine is on a USB stick).

Thanks! I was already using Q2C18 and tested the 539 ext3 image - but
it's failing for me -- same error as 540. It says:

 Write protecting the kernel read-only: 570k
 mount: Mounting /dev/sda1 on /sysroot failed: no such device or address

And then a python traceback and what looks like the USB stick being
re-rediscovered - scsi and sda modules probe the USB stick and neds up
saying

 [sda] Attached SCSI removable disk


I press enter and I seem tp be in a python debugger. Control-D to exit
takes me to

  Kernel panic - not syncing: Attempted to kill init!

I just dd'd the image to the usb stick. Is that the correct procedure?

cheers,



martin

Reply | Threaded
Open this post in threaded view
|

Usable builds in the 5xx series on B2s?

C. Scott Ananian
Please use the devel_jffs image, either in tar form or on NAND.  The
ext3 images are emulator only at the moment; they should be renamed at
some point.
 --scott

--
                         ( http://cscott.net/ )

Reply | Threaded
Open this post in threaded view
|

Usable builds in the 5xx series on B2s?

C. Scott Ananian
On 8/2/07, C. Scott Ananian <cscott at cscott.net> wrote:
> The
> ext3 images are emulator only at the moment; they should be renamed at
> some point.

People seem to disagree with me on this point.  In any case, you can
edit boot/olpc.fth to disable the ramdisk as a temporary workaround;
I've added a pause to the ramdisk's mounting of /dev/sda1 which should
help your particular problem (which seems to be that your USB device
takes a while to initialize and register itself).
 --scott

--
                         ( http://cscott.net/ )

Reply | Threaded
Open this post in threaded view
|

Usable builds in the 5xx series on B2s?

James Cameron-2
In reply to this post by Martin Langhoff
540 booting fine for me on B2s, from NAND flash.

After starting just the Sugar Console and switching to the Terminal  
tab, free(1) shows 43Mb of memory available, of which 35Mb is cache.  
This is adequate for my radio range testing, but as others have said  
if you need to add swap then do so.