Beaglebaord 5.19 15thApr ROM issues

Hi,

I “flashed” my Beagleboard -Xm with the latest 5.19, 15th Apr 12, development build today and all I now get on boot up is a blank screen with the hard disc light constantly on.

I do not see the initial start up banner announcing RISC OS and memory etc.

I have downloaded the image twice and flashed the card twice now all with the same results.

Returning to the previous 5.19 10th Apr 12 ROM image allows the Beagleboard to boot up correctly.

I have SCSI::4 as my boot up drive and no drive::0 attached.

Doug

Possibly a variant of this ?

Well it could be I suppose.

So what has changed between 10th April 12 and 15th April 12 ROM build?

I have MLO and u/boot files dated 19th April 11 and do not have a CMOS widget or battery backup, and hence the annoying message to say !Organizer has changed to BST each boot up.

I have the latest HardDisc image integrated as well, though !Printers seems to be broken in the the self exracting HardDick4download.

I’ve returned to 10th April 12 ROM for now as that works.

Doug

It looks like this is being caused by the busted version of MbufManager that got checked in – see here. Apart from a few performance improvements it doesn’t look like there have been any other user-facing changes made in the past week, so it’s probably best to stick with the 10th April ROM (or older) until MbufManager gets fixed.

With any luck, the OMAP3 development ROM, which gets uploaded via the autobuilder tomorrow morning will have fixed this issue.

I’ve just built two new OMAP3 ROM images, one including the fix for MbufManager that was put into CVS today.
The other was built without this mornings fix and without the update to MbufManager that was done on the 14/04/2012.

Neither ROM will boot, I’m just left with a blank screen.
So it looks like it’s something else is causing this issue.

The ROOL developer BB-xM with MbufManager 0.28 booted fine for me, and I copied ‘My Documents’ off my PC via LanManFS to give some mbufs an exercise, I think I’m reasonably up to date with CVS except for the dynamic area stuff which I’ve not picked up yet.

MbufManager 0.27 had 4 stack imbalances in it and should not be used. My bad.

MbufManager 0.26 has some StrongARM aggrevating code sequences in it, but would be OMAP3 safe.

FWIW, the code I fetched last night, after checking in the OS_ChangeDynamicArea changes, worked fine after I rolled back to MbufManager 0.26. I’m not sure why things wouldn’t be working for you Rob; is this the first time you’ve tried one of the SmartReflex ROMs? (forget that last bit – I see that the SmartReflex ROMs have been working fine for you)

There is every chance I messed something up!

I’ve tried the ROM that built last night and it works fine!
And what a difference in boot time, well done Jeffrey!!

Latest Beagle ROM , 17th Apr, works now and yes the boot up is far faster and my monitor now doesn’t sync/display anything until the boot sequence gets held up by the wait for a DHCP address.

Thanks for the improvement work must go to Jeffrey and also Sprow for sorting out the MBuf issue.

Only one minor negative point is that the 17th Apr self extracting Harddisc4 image is even more broken now with an incomplete version of !Printers and also !Maestro missing as well.

Ah, I have been “working on” (AKA breaking) the autobuilder over the past week or so. It wouldn’t surprise me if I’ve clobbered the HardDisc4 build in some way. I’ll check…