blob-cvs-commit

latest blob CVS problems

[Abraham vd M. <ab...@2d...>]

Hi!

I see blob is bootable again after Erik fixed the Makefile, but now blob
doesn't want to boot my linux kernel anymore. It just does this each time:

------------< snip <------< snip <------< snip <------------
blob> boot

Starting kernel ...

Uncompressing Linux........................................ done, booting
the k.
------------< snip <------< snip <------< snip <------------

And get stuck there. Any ideas?

--=20

Regards
 Abraham

QOTD:
	"Just how much can I get away with and still go to heaven?"

__________________________________________________________
 Abraham vd Merwe - 2d3D, Inc.

 Device Driver Development, Outsourcing, Embedded Systems

  Cell: +27 82 565 4451         Snailmail:
   Tel: +27 21 761 7549            Block C, Antree Park
   Fax: +27 21 761 7648            Doncaster Road
 Email: ab...@2d...         Kenilworth, 7700
  Http: http://www.2d3d.com        South Africa

Re: latest blob CVS problems

[Erik M. <J.A...@it...>]

On Wed, Feb 27, 2002 at 11:54:54AM +0200, Abraham vd Merwe wrote:
> I see blob is bootable again after Erik fixed the Makefile, but now blob
> doesn't want to boot my linux kernel anymore. It just does this each time:
> 
> ------------< snip <------< snip <------< snip <------------
> blob> boot
> 
> Starting kernel ...
> 
> Uncompressing Linux........................................ done, booting
> the k.
> ------------< snip <------< snip <------< snip <------------
> 
> And get stuck there. Any ideas?

Back out Tim's patches (in your sandbox) and see if that solves the
problem. I guess it will because I don't expect the kernel to be able
to boot with ATAG_INITRD put on a flash address (because there probably
isn't a logical-->physical address mapping so early in the boot
process).


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty
of Information Technology and Systems, Delft University of Technology,
PO BOX 5031, 2600 GA Delft, The Netherlands  Phone: +31-15-2783635
Fax: +31-15-2781843  Email: J.A...@it...
WWW: http://www-ict.its.tudelft.nl/~erik/

Re: latest blob CVS problems

[Tim R. <Ti...@Ri...>]

This would not have any effect until the initrd is accessed, no? That
happens after most all of the kernel text is displayed.

Erik Mouw wrote:
> 
> On Wed, Feb 27, 2002 at 11:54:54AM +0200, Abraham vd Merwe wrote:
> > I see blob is bootable again after Erik fixed the Makefile, but now blob
> > doesn't want to boot my linux kernel anymore. It just does this each time:
> >
> > ------------< snip <------< snip <------< snip <------------
> > blob> boot
> >
> > Starting kernel ...
> >
> > Uncompressing Linux........................................ done, booting
> > the k.
> > ------------< snip <------< snip <------< snip <------------
> >
> > And get stuck there. Any ideas?
> 
> Back out Tim's patches (in your sandbox) and see if that solves the
> problem. I guess it will because I don't expect the kernel to be able
> to boot with ATAG_INITRD put on a flash address (because there probably
> isn't a logical-->physical address mapping so early in the boot
> process).
> 
> Erik
> 
> --
> J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty
> of Information Technology and Systems, Delft University of Technology,
> PO BOX 5031, 2600 GA Delft, The Netherlands  Phone: +31-15-2783635
> Fax: +31-15-2781843  Email: J.A...@it...
> WWW: http://www-ict.its.tudelft.nl/~erik/
> 
> _______________________________________________
> blob-cvs-commit mailing list
> blo...@li...
> https://lists.sourceforge.net/lists/listinfo/blob-cvs-commit

-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.

Re: latest blob CVS problems

[Tim R. <Ti...@Ri...>]

Ok, my patch that I thought worked did not really, as it was loading
initrd from ram. I changed most systems back to loading from ram. idr
and shannon are set to no load a ramdisk at present. I'll debug further
why initrd from flash does not work.

Update from cvs and try again. Should work now.

Sorry.

Tim Riker wrote:
> 
> This would not have any effect until the initrd is accessed, no? That
> happens after most all of the kernel text is displayed.
> 
> Erik Mouw wrote:
> >
> > On Wed, Feb 27, 2002 at 11:54:54AM +0200, Abraham vd Merwe wrote:
> > > I see blob is bootable again after Erik fixed the Makefile, but now blob
> > > doesn't want to boot my linux kernel anymore. It just does this each time:
> > >
> > > ------------< snip <------< snip <------< snip <------------
> > > blob> boot
> > >
> > > Starting kernel ...
> > >
> > > Uncompressing Linux........................................ done, booting
> > > the k.
> > > ------------< snip <------< snip <------< snip <------------
> > >
> > > And get stuck there. Any ideas?
> >
> > Back out Tim's patches (in your sandbox) and see if that solves the
> > problem. I guess it will because I don't expect the kernel to be able
> > to boot with ATAG_INITRD put on a flash address (because there probably
> > isn't a logical-->physical address mapping so early in the boot
> > process).
-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.

Re: latest blob CVS problems

[Stefan E. <ste...@el...>]

On Wed, Feb 27, 2002 at 11:39:37AM -0700, Tim Riker wrote:
> Ok, my patch that I thought worked did not really, as it was loading
> initrd from ram. I changed most systems back to loading from ram. idr
> and shannon are set to no load a ramdisk at present. I'll debug further
> why initrd from flash does not work.
> 
> Update from cvs and try again. Should work now.
> 
> Sorry.
> 

Hmmm, I just checked out a fresh CVS version of blob and my kernel
still does not boot. It works with the pre2 CVS version.

Any more ideas?

LOAD_RAMDISK is set to 1

I'll poke around a little ...

Stefan